MVP in a week
Five working days from a scoped idea to a deployed product with real users able to sign in and use it. Fixed scope, fixed price, agreed before anyone writes code.
| Engagement | 7 days · fixed scope |
|---|---|
| Built for | Founders proving an idea |
| Price | Quoted on scope |
A deployed product
Running on your own cloud account, with authentication, a database and the core flow working end to end. Not a prototype and not a clickable mockup.
The source code
A conventional, tested repository you own outright, with a README that explains how to run it and how it is laid out.
Your infrastructure
Provisioned in your accounts, under your billing, with the deploy pipeline already wired up. Nothing is hosted on our side.
A written next step
What we would build second, what we deliberately left out, and which parts will need rework if the idea takes off.
What a week actually buys
Most ideas die in the gap between a pitch deck and something a person can log into. A week of focused work closes that gap: at the end of it you have a URL, real users can sign up, and the core promise of the product works.
That is enough to do the things a deck cannot. Show it to customers, put it in front of an investor, run a paid ad at it and see whether anyone converts, or discover cheaply that the idea needs to change.
How the week runs
Day one is scope. We cut the idea down to the single flow that proves it. This is the day that decides whether the rest works, so it gets a real conversation rather than a form.
Days two to five are the build. Coding agents run in parallel across the codebase while we review and correct their output continuously. You get a working deploy at the end of each day, so you are never waiting until Friday to find out what happened.
Day six deploys to your infrastructure. Your cloud account, your domain, your billing.
Day seven is handover. Documentation, a walkthrough, and an honest note on what to build next.
When to pick something else
A week does not fit every problem, and we would rather tell you now.
- If the product needs a mobile app in the stores, budget for the review cycles as well as the build.
- If it depends on integrating with an enterprise system you do not control, the integration will set the pace, not us.
- If nobody on your side can make a decision within a day, the format falls apart. It runs on fast answers.
Is a week really enough?
For one sharp flow, yes. The constraint that makes it work is scope: we agree on the single thing that proves the idea and build that properly, rather than half-building ten features. If your idea needs more, we will say so before you pay.
What happens if it slips?
The scope is fixed at the start and the price with it. If we misjudge the estimate that is our problem, not yours, and we finish the agreed scope anyway.
Will the code be throwaway?
No. Coding agents produce conventional code and tests quickly, so there is no speed argument for cutting corners. Several products that started as one of these builds are still running on that original codebase.
Who owns it?
You do, from day one. The repository, the cloud account and the domain are yours. There is no licence, no hosting lock-in and no retainer required afterwards.
What do you need from me?
About two hours on day one to settle scope, then a daily review of what shipped. If you cannot make the reviews, the week takes longer.
Tell us the one thing it has to do.
If it's sharp enough to prove in a week, we'll say so and give you a date. If it isn't, we'll tell you that too, along with what we'd build first instead.