Requirements that are vague on paper, made real in production

This is the work of designing data models, wiring up integrations, handling edge cases, and shipping something the business can rely on daily. Backend services in C#/.NET, Azure Functions, Dynamics 365 customizations, Power Platform builds — the full lifecycle, not just the interesting parts.

I'm comfortable owning a platform end-to-end: architecture decisions, the integrations nobody wants to touch, and the operational details (logging, retries, audit trails) that decide whether a system survives contact with real users.

Built for Azure Government

I've done this at scale inside Azure Government (GCC), on a platform serving hundreds of users at 99.9% uptime. That environment comes with real constraints — compliance requirements, approval chains, and the kind of bureaucratic friction that slows down less experienced contractors. I know how to move carefully inside it and still ship:

  • Managed Identity authentication — no credentials stored in code or configuration.
  • Row-level Dataverse security — each team's data scoped to exactly the people who should see it.
  • Full audit trails on data pipelines, built in from the start rather than bolted on after an incident.

For a concrete example of this in production, see the Bulk Dataverse Import Pipeline case study: 40,000 individual API calls reduced to roughly 40 batched requests, with a complete per-row audit trail.

Engagement

Project-Based or Retainer

Scoped project work for a defined build, or an ongoing retainer for ongoing Azure/Dynamics/Power Platform needs. Either way, you get direct communication and an architect who owns the outcome, not just the ticket.

Location

Boise, Idaho · Remote-Friendly

Based in Boise, Idaho, working with Idaho businesses and government teams as well as remote clients nationwide. Azure Government work can be done fully remote within the required compliance boundaries.

Technologies: C# · .NET · Azure Functions · Azure DevOps · Dynamics 365 · Power Platform · Dataverse · SharePoint · Managed Identity · SQL Server

Have a platform that needs to hold up?

Tell me what you're building or what's currently fragile, and I'll be direct about whether I'm the right fit.