011 week
Scope and cut
We split the feature list into build-now and build-later with you, and write the scope down.
MVP Sprint
A working product in front of real users in six to ten weeks, with a written scope, a clean codebase, and everything handed over.
The buyer question this answers: Can I validate this in weeks, not months?
Who this is for
- A founder with funding and a clear idea, and no engineering team yet.
- A company testing a new product line before committing a budget to it.
- A team that needs something real to show customers or investors by a date.
Phase by phase
Reference timings for a typical engagement. The written scope gives you the dates for yours.
- 023–5 days
Architecture
Data model, API contract, and infrastructure plan, then the repository is set up with CI.
- 033–5 weeks
Core build
The build-now features, shipped to a staging URL every week with a demo.
- 041 week
Hardening
Tests on critical paths, error tracking, a performance pass, and a security review.
- 053–5 days
Launch
Production deployment, DNS, monitoring, and the handover.
- 062 weeks
Support window
We fix anything we built that breaks, at no charge.
The stack for this workflow
- Next.js
- TypeScript
- Python or Node.js
- PostgreSQL
- Cloudflare or AWS
- GitHub Actions
- Playwright
- Sentry
What could go wrong
Every build has risks. These are the ones we plan for on this kind of project, and what we do about each.
The scope grows during the build.
How we handle itEverything new goes on the build-later list unless you choose to swap something out. The date holds because the list does.
A third-party service does not do what its documentation says.
How we handle itIntegrations are spiked in the first week of the build so surprises appear early, when there is still room to change course.
Users react differently from the plan.
How we handle itStaging is live from week two, so real feedback shapes the build rather than arriving after it.
Cost model: Fixed scope
The scope is written before we start, so a fixed price and date are honest. If we estimated wrong, that is our problem.
No prices on this page. The scope phase ends with a written quote for your project.
From the blog
- The three architecture decisions that are expensive to reverseMost early technical decisions can be changed later at reasonable cost. Three cannot. How to recognise them, and how to make them well in the first week.
- How to hand over a codebase so a team can run itOwnership is a clause; handover is the work that makes it real. The checklist we run at the end of every engagement so your team can run the system without us.
- How long does an MVP take? Six to ten weeks, if you cutThe honest answer to how long an MVP takes, what decides whether it is six weeks or six months, and the one activity in the first week that determines the rest.
Questions we get asked
What if we need more than ten weeks?
Then it is not an MVP yet. The scope phase exists to cut it down to one, and the build-later list becomes the roadmap for the next engagement.
Can we change our mind mid-sprint?
Yes, by swapping something of similar size out. Adding without removing moves the date, and we tell you by how much before you decide.
What do we own at the end?
Everything: repositories, infrastructure configuration, documentation, designs, and IP. It is yours from the first commit.
Is the code good enough to keep building on?
Yes. An MVP is small, not sloppy. Tests, CI, and a clean structure are part of the scope because they make the next ten weeks faster.
Tell us what you are building.
We reply within one business day with how we would build it, what it would cost, and which engagement model fits.
- 01Tell us what you are building
A short form or an email. No deck required, and "not sure yet" is a fine answer.
- 02A call with an engineer
Within one business day. Technical questions get technical answers, from the person who would build it.
- 03A written scope and quote
Fixed price where the scope is defined. The document is yours whether or not you go ahead.