I build software that actually ships.
A studio of one. Fixed scope, fixed price, real dates. No discovery phases that discover nothing — brief on Monday, live by a Friday you can name.
Three ways to get online.
Things that went live.
How the work works.
Fixed scope, fixed price.
We agree what "done" means before we start. No hourly meter, no scope creep dressed up as discovery. You know the number and the date on day one.
One person, end to end.
The person you brief is the person who writes the code. Nothing gets lost in a handoff because there isn't one.
Ship weekly, not eventually.
Something real lands in your hands every week. You steer with working software in front of you, not slide decks about it.
Plain language.
No synergy, no delight, no "leveraging." I'll tell you what I'm building, why, and what it costs — in words you'd use yourself.
Two slots open for Q3.
Tell me what you're building. I'll tell you the price and the date.
Start a projectHow does fixed price actually work?
We scope it together first and agree what "done" means. Then I quote one number and one date — no hourly meter, no change orders for things we already wrote down.
What if the work runs over?
That's my risk, not yours. The price and date are fixed on day one; if I underestimated, I absorb it. You pay what we agreed.
How soon can we start?
Two slots are open for Q3 2026. Once a slot is yours, something real lands in your hands every week until it's live.
What do you build with?
TypeScript, Go, and Postgres, mostly — boring, proven tools that someone else can pick up later without a treasure map.
What if it's not a fit?
I'll tell you honestly and fast — usually the same day — and point you somewhere better if I can. No drawn-out sales process either way.