The .NET software you need, delivered and kept running.
Software development consulting, specializing in cloud-native .NET on Azure: the application, the infrastructure under it, and the pipeline that ships it. On cloud accounts in your name.
Tell me what you need built or fixed, and I'll tell you where I'd start.
Who this is for
A business with .NET software to build or to run.
-
You have developers and nobody owns the cloud
The application is somebody’s job. The Azure account, the pipeline, and the release are nobody’s.
-
You have the work and no engineer
A build waiting to start, a feature list nobody has time for, or a codebase whose author has left.
What gets left until last - Building it is the half everyone plans for.
The other half decides whether it survives its first real week.
Releasing is manual, and somebody dreads it
It goes out by hand, at night, from one person’s laptop, and there is no way to put it back.
Nobody owns the cloud account
It was clicked together once, by somebody who has since moved on. What is running, who has access, and why the bill is what it is are all questions nobody can answer.
Test and production have drifted apart
What passed in test says nothing about what will happen live, so every release is a guess dressed up as a process.
There is work and no engineer
A build waiting to start, a framework two versions past support, or a codebase whose author has left and nobody wants to open.
Every one of these is a job somebody has to do. On a small team it is usually nobody’s, until the week it is everybody’s.
Tell me what you need built or fixed, and I'll tell you where I'd start.
What I do - The application, and everything under it.
Hiring a developer and an infrastructure specialist separately means somebody has to explain each one’s work to the other, and that somebody is usually you. This covers both.
The application
New builds in C# and .NET, features on a codebase you already have, framework upgrades that are years overdue, and cross-platform mobile in .NET MAUI. Written to be handed back: documented, tested, in your repository.
The infrastructure
Azure described in Terraform rather than clicked together, so an environment is something you can create again. Networking, databases, secrets in Key Vault, access control, and what each of it costs written down.
The way it ships
Build and release pipelines in Azure DevOps: it builds on every change, the tests run, and a release goes out the same way every time and can be put back. Then something watching it, and someone to call when it breaks.
Every engagement is quoted. Scope varies too much for a price list, and a published number would only ever describe the smallest job.
How an engagement works - Simple, clear, no surprises.
Four steps from your first message to work running in production: a free review, then milestones you approve and pay for one at a time.
Tell me what you need
Book the free review or send a message. You leave with a fixed quote and nothing owed.
I read what you have
The first milestone, billed up front. A written plan: what has to happen, what it will cost to run, and how long it takes. Quoting the rest blind is how a fixed fee turns into an argument.
I build it
The middle milestones. The code, the infrastructure, the pipeline, or all three. You see it on a private test address only you and I can see before anything is live.
You get the keys
The last milestone. It goes live, and I hand over a written record of every account, password, and security setting, with a walkthrough. Everything runs in accounts you own, so nothing depends on me still being here.
Proof - Read the work before you talk to me.
Most consultants ask you to take the quality on trust until the invoice arrives. Here is the actual output, in public.
A real handover document
What a client receives at the end: every account, every setting, every decision and why it was made. Published in full, anonymized, so you can judge the standard of the writing before you hire the writing.
A recent project
A small practice had an internal application that worked and had never been deployed properly. I rebuilt how it runs: who can sign in, what each person can reach, and where the data sits, on Azure accounts in their name.
I finally feel like I actually own my app.
Software I run myself
UnityPay and Albie are on the App Store and Google Play, and I operate both: the releases, the infrastructure, the support address. Whatever I would ask you to run, I already run, and I hear about it when it breaks.
An engineer who starts from your business, not the code.
I’m Will, a software engineer with an MBA from The Ohio State University. I build software the person running the business can operate, and a project has gone well when it solves your problem, not when the code runs.
Learn more about meTwenty minutes, and nothing to prepare.
Tell me what you need built or fixed, and I'll tell you where I'd start.