One feature
$4,000fixed
1 week
Login and the one action that proves your idea works. For testing demand before you spend more.
Fixed-price MVP studio · built with Claude Code
Working software in two weeks. The price is fixed.
For founders who were quoted three months and $40,000. You sign a one-page spec, I build it, and it goes live on your domain in ten working days.
10 working days
- D1Scope call, written spec
- D2You sign, pay half
- D3Data and screens on staging
- D4The core flow
- D5Payments and login
- D6You review staging
- D7Fixes, your sign-off
- D8Live on your domain
- D9Handover: repo and video
- D1030-day fix window starts
Who this is for: founders with a deadline — a pilot customer, a demo day, a launch date — who need a web app with login, payments and one core flow, and who want the price in writing before anything is built.
Three packages. Priced by scope, never by the hour.
Each timeline below is drawn to scale. Most founders pick the core product; the other two show where it sits.
Core product
Main package$8,000fixed
2 weeks
Login, payments, a dashboard and one core user flow. A product your first customers can sign up for and pay.
Core plus two
$12,000fixed
3 weeks
The core product plus two integrations, such as a calendar or an email tool.
Same terms for all three. Half books your start date. Half is due when you sign off staging. Five small changes are included — wording, colors, a field, a label, an email.
For comparison: a typical web-app MVP is quoted at $25,000–$50,000 (SpeedMVPs, 2026) and takes two to four months (Helpware, March 2026).
Watch a build, start to finish.
The core flow, the payment, the dashboard — and the clock. No slides.
How the ten days run.
One build at a time. The next start date is the day after handover.
-
Day 1
A 20-minute scope call, then a written spec
Who your first user is, the one thing they must be able to do, and your deadline. I write it down as a one-page spec: users, the core flow, screens, data, integrations, and what is not included.
-
Day 2
You sign the spec and pay half
That books your start date. Nothing is built before both.
-
Days 3–5
I build on staging, one piece a day
Data model and screens, the core flow, then payments and login. Every piece gets its own preview link you can click.
-
Days 6–7
You review staging and sign it off
I fix what doesn't match the spec. The second half is due at your sign-off. Nothing goes live before it.
-
Days 8–9
Live on your domain, then handover
Day 8 it's live with real payments. Day 9 you get the repo, a walkthrough video and a list of every account.
The one-feature package runs the same steps in one week; core plus two takes three.
What you own, and what I won't build.
Your code, your accounts, from day one
I build in your GitHub, your Vercel, your Supabase and your Stripe — accounts in your name, with me added as a collaborator. On day 30 I leave all of them and confirm it in writing.
The 30-day fix window. For 30 days after handover, anything the spec says works and doesn't gets fixed free, with a reply within one working day. Anything else is a change: quoted before it's built.
- Vercel Pro (hosting)
- $20/mo + $20 for my seat until day 30
- Supabase Pro (database, logins)
- $25/mo from launch
- Stripe (payments)
- per-sale fees only
Builds I turn down
- Native iOS or Android apps
- Marketplaces that pay out to sellers
- Anything that holds health records or moves customer money
- Training AI models
- Migrating data from an old system
- Custom design systems
- Work paid in equity instead of money
Two weeks can't carry the compliance work those need. If yours is one of them, I'll say so on the call.
Builds shipped.
What each one does, the package, and the days it took. Shown only with the founder's permission.
The first client builds appear here after handover, with each founder's written permission.
Questions founders ask first.
What if I want something that isn't in the spec?
Then it's a change. I quote it with a price and a date, you decide, and it's built after launch — never squeezed into the ten days. Five small changes are already included.
Who owns the code?
You do, from the first commit. It lives in your GitHub, runs on your Vercel and Supabase, and takes payments into your Stripe. I'm a collaborator on your accounts until day 30, then I leave.
How can a fixed price hold?
The spec is short and signed, I build one product at a time, and every build starts from a tested starter with login and payments already working. Claude Code does the typing; I do the scoping, the review and the testing. You pay for the scope, not for my hours.
What does it cost to run after launch?
Vercel Pro at $20 a month (plus $20 for my seat until day 30), Supabase Pro at $25 a month from launch, and Stripe's per-sale fees. All billed to you directly, so nothing stops if we stop working together.
What happens after the 30 days?
You own everything and I've left your accounts. If you want more, we write a new spec and it gets its own fixed price — or you hand the repo to any developer. It's a standard Next.js codebase with a README.
Tell me who your first user is.
And the one thing they must be able to do. In 20 minutes you'll know the package, the price and what isn't included.