What I build for founders

How to pick one

The four overlap more than the labels suggest. Plenty of projects start as an MVP sprint and grow into one of the others once there are real users to argue with. A web app often turns out to be mobile-first, because that is where the people using it actually are. If you cannot tell which one you need, that is normal — a single call is usually enough to work it out, and it costs you nothing to find out.

What does not change is how the work runs. One call to agree what we are building, what we are deliberately skipping, and what it costs. Screens you can click and question, signed off before I write any code. A working build every week in a shared chat, so you never have to read a status report to find out where things stand. Then launch, and I stay on through the first weeks of real use — the part where you find out what people actually do with it.

Two shapes of engagement sit underneath all four. A quick build: one to two weeks, fixed price, agreed before anything starts. Or a full product: six to ten weeks, scoped and priced up front. Either way you own the code and the design outright when it ships — no retainer required to keep your own software running, and nothing locked to a platform you cannot leave.