SHORT ANSWER
Build an MVP by picking one job a specific user will pay to have done, designing the single shortest flow that completes it, and shipping only that. Validate demand before building — interviews plus a paid or committed signal. Build in four to six weeks with off-the-shelf infrastructure, launch to a narrow group, and measure whether they complete the job and come back.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
Most first products fail on scope, not on code. Teams build six half-features instead of one that finishes a job.
An MVP exists to produce evidence. If it cannot change your mind about the business, it is not an MVP — it is a version one.
One sentence: who, what outcome, in what situation. If it needs two sentences, the scope is already too wide.
Ten to fifteen problem interviews plus a commitment signal — a deposit, a signed pilot, a waiting list with real intent.
Map entry to outcome in the fewest steps. Every screen that does not sit on that path is out of scope for v1.
Managed auth, managed database, hosted AI models. Custom infrastructure at MVP stage is capital spent on the wrong risk.
Twenty to fifty users who match the profile exactly. Track activation, time-to-value and week-four return.
Persevere, pivot the job, or stop. Set the thresholds before launch so the decision is not emotional.
FROM EXPERIENCE
A typical first scope arrives with onboarding, dashboards, team accounts, notifications and reporting. Cutting to one flow — sign in, complete the job, see the result — usually removes 70% of the build and none of the learning.
At Wocal the version that mattered was the one that did a single thing end to end. Everything on the roadmap around it could wait, and most of it never needed building.
Four to eight weeks for most software MVPs with modern tooling. Longer usually means the scope was never cut.
No. AI-assisted build tools and a fractional product partner can get a first version live without an in-house engineer.
Where possible, yes. Payment is the cleanest validation signal there is.
IN SHORT
Done-for-you six-week build from validated idea to live product.
Read moreThe practical route from scoped idea to a live first release.
Read moreFree estimate of what your MVP will cost and how long it will take.
Read moreA validated, instrumented first product in front of real users.
Idea to MVP in six weeksTHE FRAMEWORK
MORE ANSWERS
A focused software MVP costs roughly £5,000–£15,000 built with AI-assisted tooling and a small scope, £20,000–£50,000 with a freelance or agency team, and £60,000–£120,000 for a complex or regulated product. The main cost driver is scope, not day rate: every extra flow adds design, build, testing and support cost. Budget 20% for post-launch iteration — that is where the learning is.
Build an AI MVP by choosing one task where being right 80% of the time is still useful, wrapping a hosted model rather than training your own, and designing the interface around correction — users must be able to see, edit and accept output. Set an evaluation set before launch, measure task success and human-override rate, and only consider fine-tuning once the workflow itself is proven.
A focused MVP goes from idea to launched product in six to twelve weeks: one to two weeks of discovery and validation, four to six weeks of build, one to two weeks of pilot and fixes. Complex, integrated or regulated products take four to nine months. Delays almost always come from scope changes and slow decisions, not from engineering speed.