Work with me
Taking clients now. Utah, working remote.
I build and run the pieces that make your systems talk to each other. Order pipes, billing flows, fulfilment hand-offs, and the integration nobody on the team wants to own.
Fixed scope, fixed price, and you know the number before I start.
What it costs
The integration fix
Something in your order flow is dropping. A webhook that never arrived, a duplicate charge, a fulfilment step somebody now does by hand every morning.
I capture the live traffic, replay it until the failure happens on demand, and find the cause.
What you get
A written finding: what is breaking, why, and what it takes to put right. If the fix belongs in your system, the finding is enough for whoever maintains it. If the piece is past saving, I will quote replacing it as a service I build and run, and you are free to say no.
Terms
Fixed price, one to two weeks.
What I need from you
Read access to the failing system and someone who can answer questions about it.
Quoted on the call
The integration build
You know what the flow should do and nobody has built it. An order pipe from the store to the floor, a billing setup that bills correctly, a fulfilment hand-off that stops being a person with a spreadsheet.
I build it end to end on my stack, connect it to what you already run, and put it live where I can watch it. You see it working in staging before it touches a customer.
What you get
The service running, the tests that prove it, the runbook, and the code in your repository.
Terms
Fixed scope, fixed price, two to four weeks. The scope is written down before I start, and anything outside it is quoted separately rather than absorbed quietly.
What I need from you
Someone who can decide, API access to the systems it must talk to, and one afternoon at the start to walk me through how the work actually happens today.
Quoted on the call
The senior quarter
Some months you need a senior pair of hands rather than a project. An API that needs finishing, a billing system nobody wants to touch, a deploy that only works when one particular person runs it.
A set number of hours a week inside your codebase, month to month. You decide what I point at, and you can change your mind at the start of any month.
What you get
The work, the commits, and a short written note each week on what moved and what I would do next.
Terms
Month to month, thirty days notice either way. No minimum term, because a retainer that traps you is one you resent by month three.
What I need from you
Repository access, someone to review and merge, and a standing half hour each week so we are not managing by ticket.
Quoted on the call
Hourly
For work outside a package, quoted before it starts.
$180 an hour
Hosting
Your service on my cluster: TLS, backups, patching, and platform faults answered the next business day.
Quoted on the call
Hosting and care
Hosting plus a set amount of care each month for small changes and questions, more billed at the hourly rate.
Quoted on the call
How I build
I build on one stack and I keep it. .NET and TypeScript, running on Kubernetes I already operate. Your Shopify, your Stripe account, your ERP, your fulfilment provider: those stay where they are. I build the piece that is missing and connect it to what you already run.
That is why the estimates hold. I am not learning your framework on your budget, and I am not guessing at how it will behave in production, because it runs where everything else I build runs.
What that means for you:
- It ships in weeks, because I have built this before on the same tools.
- You do not hire anyone to keep it running. I host it and maintain it on a monthly plan.
- It does not go stale between projects, because I am in this stack every week.
If what you need is work inside an existing codebase in another language,
I am the wrong person, and I will tell you that on the first call rather than three weeks in.
Hosting and care
It runs on my cluster. I patch it and I keep backups. Anything broken gets a response the next business day, and I tell you in advance when I am away.
I am one person, not a rota.
If you need somebody on call through the night, I am not that, and I would rather say so now than during an outage.
Exit
You are not stranded if I stop. The runbook ships with the project and I keep it current, so it is already in your hands the day you need it.
If you decide to leave, ask in writing and within ten business days you get the code, the infrastructure as code, the data and the runbook. That costs nothing.
Standing it back up in your own accounts is work, so it is billed at my hourly rate, and the first eight hours are included.
What I have built
Webhook capture and replay, signed pipes and rooms for AI agents. The product this site is built around.
The comic
A strip written and reviewed by two AI agents in a signed room, published only on the reviewer’s signed proceed. The pipeline is the point.
The blog
Dev logs on building by directing AI agents, and fiction from the Crimson Rocket.
Northern Utah
I am in Tremonton, and I will come to you.
If you are in Box Elder, Weber, Davis or Cache county, I would rather stand where the work happens than read a diagram of it. Most of what breaks in an order flow is obvious in ten minutes on site and invisible on a call.
Write to me@spill.coffee or use the form below.
Start a project
Tell me what is broken or what you want built. This form runs on FlurryPORT: your message is captured, kept, and reaches me within seconds. Or write to me@spill.coffee.
Sent. It is in my inbox now, and you will hear from me within one business day.
That did not send. Email me instead at me@spill.coffee.
Built with
.NET 10 and EF Core on SQL Server. ASP.NET minimal APIs. TypeScript, Vite and Tailwind on the front. Azure Kubernetes, OpenTofu and Azure DevOps underneath. Stripe, Shopify, Printify and MCP where they are needed.