SFS_11Startup Foundation System™ 2–3 weeks (planning); 12 weeks (build)

MVP Strategy & Planning

Define what to build first. Prioritise ruthlessly. Choose the right build approach.

Why it matters

Most MVPs are too big, too slow, or too pretty. We choose the right MVP type (Wizard-of-Oz, concierge, single-feature, smoke-test), apply Riskiest-Assumption Tests, and prioritise with RICE — so the MVP tests the riskiest hypothesis first, not the easiest.

Scope covered

Reforge MVP-type selection (Wizard-of-Oz / concierge / single-feature / smoke-test / functional)

Riskiest-Assumption Test (RAT) per hypothesis

RICE prioritisation (Reach × Impact × Confidence × Effort)

MoSCoW filter (Must / Should / Could / Won't)

12-week MVP build roadmap

Build-vs-buy framework per component

How we run it

Our methodology

A senior-led delivery sequence — not a template dump. Each phase is operated with your team, not handed over as a deck.

1
MVP hypothesis & success criteria
Week 1
Lock the riskiest assumption the MVP must validate and the explicit success / kill criteria.
2
Scope & feature prioritisation
Week 1–2
Apply Now / Next / Later prioritisation; cut to the smallest version that meaningfully tests the hypothesis.
3
Build plan & resourcing
Week 2–3
Sequence the 12-week build plan with team, vendors and weekly demo cadence; lock dependencies.
4
12-week build & weekly review
Build phase
Operate the build with weekly demo, fortnightly customer test and a kill-switch at week 6.
5
Validation read-out
Post-build
Read-out validation results against success criteria; decide persevere / pivot / kill with the board.