Services
Twenty years of .NET work across integrations, migrations and custom builds. The problems below are the ones that show up repeatedly. If yours isn't listed, describe it anyway.
Development
Building systems from scratch and fixing the ones that need it.
Custom Application Development
Greenfield .NET applications built to spec and shipped. Web applications, internal tools, workflow systems and data platforms. Designed for the team that inherits it to maintain without needing the original developer in the room.
Stack: ASP.NET Core, C#, SQL Server, React, Azure
Project Rescue
Projects that stalled, shipped wrong or lost the developer who understood them. Assessment of what exists, a realistic plan to get to working software and execution against that plan. Without the six-week discovery phase that produces a deck instead of code.
Stack: .NET, SQL Server, Azure, whatever the project is already running on
System Integrations
Connecting systems that don't talk to each other. API integrations, data pipelines, event-driven architecture and the sync logic that keeps records consistent across platforms. Includes the monitoring layer that tells you when something breaks before users do.
Stack: .NET, REST APIs, Azure Service Bus, Azure Functions, SQL Server
Legacy System Migrations
The application built in 2007 that still runs something critical. Structured migration plans that move data, preserve history and cut over without a weekend of outages. Includes .NET Framework to .NET 8+ upgrades for applications that can't stay on an unsupported runtime.
Stack: .NET Framework to .NET 8+, SQL Server, Azure, data migration tooling
Infrastructure
Azure architecture and the work that gets systems running reliably in the cloud.
Azure Cloud Architecture
Architecture design and migration from on-premises or underspecified cloud deployments. App Service, Azure SQL, Azure AD and the security and identity configuration that IT and compliance require before anything moves. Includes the operational setup that makes a deployment maintainable after handoff.
Stack: Azure App Service, Azure SQL, Entra ID, Key Vault, API Management
Integration Architecture
Organizations accumulate systems over years. Connecting them reliably requires more than point-to-point API calls. Event-driven patterns, durable messaging, data consistency across systems and the observability layer that surfaces failures before they become incidents.
Stack: Azure Service Bus, Azure Functions, .NET, SQL Server, REST & SOAP
Leadership
Senior architect embedded in the work. Technical direction, AI strategy and the engineering judgment that keeps a project on track.
Technical Leadership
Senior architect embedded in a team or leading a build from the top. Architecture decisions, technical planning and code review ownership for projects that need someone thinking about the whole system, not just the next ticket. For teams that have developers but lack senior engineering direction, and for greenfield builds that need architectural ownership from day one.
Engagement types: fractional tech lead, embedded architect, project oversight, team augmentation
AI Integrations
Wiring AI capabilities into existing .NET systems. RAG pipelines that query internal data, document processing workflows and LLM API integration into line-of-business applications. Built to the same reliability and observability standards as any other integration — not a prototype that works in a demo and breaks in production.
Stack: Azure OpenAI, OpenAI API, Semantic Kernel, .NET, SQL Server, Azure Functions
Not sure which fits?
Describe the system and what's broken or missing. I'll tell you what the work actually involves.
Start the conversation