MVP in a week
Seven days from a scoped idea to a deployed product that real users can sign in to and use. One flow, built properly, in your own cloud account. Scope and price are fixed before any code is written; an overrun is our cost.
| Engagement | 7 days · fixed scope |
|---|---|
| Built for | Founders proving an idea |
| Price | Quoted on scope |
A deployed product
Running in your own cloud account, with authentication, a database and the core flow working end to end. Not a prototype, 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 to build second, what we deliberately left out, and which parts need rework if the idea takes off.
What you can do at the end of the week
Put a real product in front of real people. At the end of the week you have a URL, users who can sign up, and the core promise of the product working.
That does what a pitch deck cannot. Show it to customers, put it in front of an investor, run a paid ad at it and see who converts, or learn cheaply that the idea needs to change.
What happens on each of the seven days?
You see a working deploy at the end of every build day, so nothing waits until the final day.
Day one: scope. We cut the idea down to the single flow that proves it. This decides whether the rest of the week works, so it is a real conversation rather than a form.
Days two to five: build. Coding agents work in parallel across the codebase while we review and correct their output continuously.
Day six: deploy. Your cloud account, your domain, your billing.
Day seven: handover. Documentation, a walkthrough, and a written recommendation for what to build next.
When a week is the wrong format
- The product needs a mobile app in the stores. Budget for the review cycles as well as the build.
- It depends on an enterprise system you do not control. That integration sets the pace.
- Nobody on your side can make a decision within a day. The format runs on fast answers.
Is a week really enough?
For one flow, yes. We agree the single thing that proves the idea and build that properly, instead of half-building ten features. If your idea needs more than a week, you hear that before you pay anything.
What if you don't finish in a week?
An overrun is our cost. Scope and price are fixed on day one, and we finish the agreed scope at the agreed price.
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 still run on that original codebase.
Who owns it?
You do, from day one. The repository, the cloud account and the domain are yours. No licence, no hosting lock-in, no retainer required afterwards.
What do you need from me?
About two hours on day one to settle scope, then a short daily review of what shipped. Miss the reviews and the week gets longer.
Tell us the one thing it has to do.
Send a few lines on the idea. Within one business day you get a start date and a fixed price, or the smaller first version we would build instead.