Core concepts
Six ideas that make
MVPs work.
Every successful MVP is built on the same conceptual foundation. These six ideas separate founders who ship and learn from founders who build and hope.
Hypothesis-driven development
Every MVP starts with a belief — about the user, the problem, and the solution. The product exists to test that belief. Without a clear hypothesis, the MVP is just a small product with no strategy behind it.
Minimum scope, maximum quality
The word minimum refers to scope — fewer features, one user type, one workflow. The word viable means the quality must be high enough for real users to get real value. You are building fewer things, not building things badly.
Build-measure-learn
The lean startup loop. Build the smallest product that tests the hypothesis. Measure real user behaviour — signups, activation, retention, conversion. Learn from the data. Each cycle produces better decisions than the last.
Critical path thinking
The shortest sequence of actions from signup to value delivery. That path is your MVP. Everything on it gets built. Everything not on it gets deferred. This is the most effective scoping tool available.
Commercial viability testing
An MVP is not a free trial. If the product will charge users, the payment flow is part of the MVP. You are not just testing whether people will use the product — you are testing whether they will pay for it.
Evidence-based iteration
After launch, every decision is driven by data. What do users actually do? Where do they drop off? What do they ask for? The second version is better because it is built on evidence, not assumption.
Applied
How these concepts
shape a real build.
Abstract concepts are useless without application. Here is how each concept translates into concrete decisions during an 8-week MVP build at Wall & Fifth.
01
Week 1: hypothesis becomes scope
The hypothesis statement defines what gets built. "Freelancers will pay £20/month for combined invoicing and project tracking" tells us the user (freelancers), the core features (invoicing, project tracking), and the commercial model (£20/month subscription).
02
Weeks 1–2: critical path becomes design
We map the critical path — sign up, create project, log time, generate invoice, get paid. Those five actions become the user flow. Every screen serves one of those actions. Nothing else makes it into the design.
03
Weeks 3–6: minimum scope becomes code
Only the critical path gets built. No admin dashboard, no analytics, no team features, no integrations. One user type, one workflow, production-grade code. Clean, scalable, well-documented.
04
Weeks 7–8: commercial viability becomes real
Stripe subscription billing integrated. Pricing page designed. Upgrade flow tested. The product launches with the ability to charge — because the whole point is testing whether people will pay.
Myths
Common MVP misconceptions.
- "MVP means low quality" — wrong. MVP means low scope. The code should be production-grade. The interface should be clear. What is minimum is the feature count, not the standard.
- "An MVP is a prototype" — wrong. A prototype is a clickable design with no functionality. An MVP is working software with real code, real data, and real users.
- "You can validate with a landing page" — partially wrong. A landing page validates interest. It cannot validate whether people will use and pay for the product. An MVP does both.
- "MVPs are only for startups" — wrong. Established businesses use MVPs to test new products, services, and revenue streams without committing to a full internal build.
- "Build fast, fix later" — wrong. Build focused, measure carefully, improve based on evidence. Speed comes from scope discipline, not from cutting corners on quality.
Going deeper
Advanced MVP concepts.
Beyond the six core concepts, experienced founders apply additional principles:
- Activation metric — the single user action that predicts retention. Find it, optimise for it, and everything else follows.
- North star metric — one number that defines product health. For a SaaS MVP, it might be weekly active users or monthly recurring revenue.
- Cohort analysis — measuring behaviour by signup cohort rather than in aggregate. Did users who joined in week 2 retain better than week 1? That tells you whether your changes are working.
- Feature flags — shipping features to a subset of users first. Test the impact before rolling out to everyone.
- One-way vs two-way doors — one-way decisions (tech stack, architecture) should be made carefully. Two-way decisions (copy, pricing, feature order) should be made fast and changed if wrong.
These concepts become relevant after launch — during the transition from MVP to full product. During the initial build, the six core concepts are sufficient.
FAQ
Questions people usually have before the next step feels obvious.
What are the core MVP concepts?
Hypothesis-driven development, minimum scope with maximum quality, build-measure-learn, critical path thinking, commercial viability testing, and evidence-based iteration.
What does minimum viable mean?
Minimum scope — fewest features, one user type. Viable — must work well enough for someone to use it and get value. Not minimum quality.
What is the build-measure-learn loop?
Build the smallest product, measure user behaviour, learn from data. Repeat. Each cycle produces better decisions.
What is critical path thinking?
Identifying the shortest user journey from signup to value. Build only that path. Defer everything else.
Related pages
Apply the concepts
Understand the ideas.
Build the product.
Tell us what you are building. We will apply these concepts to your product and deliver an MVP in 8 weeks.