How Long Does an MVP Take to Build?

A focused UK MVP often ships in roughly 4, 8 or 12 weeks once scope is locked - four for a thin one-workflow proof, eight for a sellable lean product, twelve when billing, roles or a second integration sit in the cut. Those bands need ready owners and no third-party freezes; agent-assisted delivery compresses Build (the 5x / half-cost framing in our build-time data), not the politics of deciding what “minimum” means. Below: what each band ships, what stretches the calendar, and why week zero still decides the rest.

The short answer: MVP timelines by scope (4 / 8 / 12 weeks)

Band	Typical calendar	What usually ships
4 weeks	Thin proof	One primary workflow, basic auth, thin admin, enough instrumentation to learn
8 weeks	Lean sellable MVP	Core journey polished enough to charge or pilot; one payment path or deliberate delayed billing; basic roles
12 weeks	Heavier lean cut	Billing depth, richer admin, a second integration, or multi-role permissions that survive a real team

These are scope shapes, not stopwatch theatre. A “4-week MVP” with three personas, SSO and a CRM sync is a 12-week brief in costume.

In UK product shops, lean SaaS-shaped MVPs commonly land in roughly 8-16 weeks when owners are ready; our agent-assisted Build compresses implementation inside a fixed band after Blueprint, which is how 4- and 8-week cuts become honest for the right scope. Discovery waits and vendor access still sit outside that compression - method in the build-time dataset. Money siblings: SaaS development cost UK, app development cost UK. Hub: SaaS platforms.

How much does an MVP cost to build?

MVP cost sits with scope: for UK SaaS pricing bands and how we quote after Blueprint, see SaaS development cost UK.

Can you build an MVP in a month?

Yes, when the cut is genuinely one workflow, owners decide in days not weeks, and integrations are absent or already contracted - a calendar month is a scope choice, not a slogan. If “in a month” secretly means billing, three roles and a CRM sync, you are buying a false start.

What actually stretches an MVP schedule

Code is rarely the villain. Calendars blow up on:

Decisions. Unowned product calls (“do we need orgs on day one?”) idle seniors while agents wait. Mastery is forcing the cut in week zero, not polishing screens nobody prioritised.

Integrations. Sandbox access, credential delays and expired staging keys. One clean integration can burn a week of coordination even when the code is short.

Content and data. Seed catalogues, legal copy and sample documents arrive late. Agents cannot invent your pricing PDF.

Access and politics. Committee approvals and stakeholders who only reply on Fridays. None of that 5x’s.

Scope creep dressed as clarity. “While you’re in there” turns 8 weeks into 16. Outside Blueprint means priced and scheduled first - fixed change scopes priced before work starts.

Treat stretches as Map risks, not week-six surprises.

What belongs in an MVP (and the features that can wait)

What should an MVP include?

An MVP should include one primary workflow, auth for the people who use it, enough admin to operate day one, instrumentation to see behaviour, and a deliberate payment or pilot path - nothing else earns a place by sounding impressive.

In:

• The job-to-be-done path end to end (happy path plus the failure that will actually happen)
• Roles you truly need on day one (not the org chart fantasy)
• Thin admin: disable a user, edit a record, see obvious errors
• Analytics or event logs you will look at
• A way to take money or a written decision to delay billing for a pilot cohort

Out until later:

• Multi-tenant enterprise packaging
• Perfect design systems with every component variant
• Secondary personas “for the roadmap slide”
• Native apps when a solid web MVP teaches the same lesson cheaper
• Automation theatre that has no owner for exceptions

If a feature does not teach you whether users will pay or return, it can wait. That discipline is what makes a 4- or 8-week band real.

How agent-assisted delivery changed our timelines

We direct coding agents under senior architecture, taste and release authority - the same pattern described in what is agentic AI and measured in AI-accelerated delivery. On compressible Build work (CRUD, scaffolding, tests, repetitive UI inside a system) we frame throughput at 5x versus our own pre-agent baseline, landing comparable implementation at roughly half a traditional bench cost. Harden, discovery judgement and third-party waits do not get the same multiplier.

What that means for MVP calendars in practice:

• Boilerplate that used to burn senior days now drafts under review, so 4-week proofs stop being fantasies for thin scopes
• Design-to-code moves faster once tokens exist; inventing a visual system from nothing still takes human taste
• Rework drops when Blueprint is honest - agents amplify a clear cut and also amplify a muddy one
• Public timeline claims stay at category level; named week-by-week case tables need a scoped, approved project behind them

Est 2005, 350+ projects - agents changed throughput; they did not remove the need for someone to say no.

Week zero: why discovery up front shortens everything after

Week zero is where you kill the wrong build. A short product discovery workshop locks the primary workflow, the out-list, risks and a commercial band before anyone writes production code. Skipping it to “save time” is how you discover in week five that billing was non-negotiable all along.

What week zero should leave you with:

• A written MVP cut (in / out)
• Named owners and decision SLA
• Integration list with access status
• Acceptance checks you can demo against
• A timeline band that matches the cut, not the pitch deck

Map and Blueprint are not theatre. They are the reason an 8-week promise survives contact with a real backlog.

---

A 4-, 8- or 12-week promise is honest only when the out-list is written and owners decide in days. Lock that cut under SaaS platforms.