MVP: why shipping small and fast saves you money
What you lose by trying to ship everything at once
I've seen this scenario dozens of times. A company invests 12 to 18 months of development, mobilises teams, commits a significant budget — and launches a product that users don't adopt as expected. Not because the team was lacking. Because no one had tested the idea against the real market before building everything.
This is what's known as the "big bang" effect, or the development tunnel: you start from a vision, you build in isolation, and at launch you discover that your initial assumptions were partially wrong. At that point, fixing things is very expensive — in time, money, and team energy.
Across 45 projects delivered with Twenty, this scenario recurs regularly among organisations that had both the resources and the expertise. The problem isn't competence: it's method.
MVP: what it really is (and what it isn't)
MVP stands for Minimum Viable Product. But the word "minimum" often creates confusion.
An MVP is not:
- a mockup or a demo that pretends to work
- a cut-rate product thrown together hastily
- an incomplete version you're embarrassed to show
An MVP is: the simplest possible product that allows you to validate a real hypothesis with real users, under real conditions.
Put differently: it's a product that actually works, but only covers the essential features needed to address your target audience's number-one problem. Everything else is deferred — not abandoned, just postponed until you have proof it's worth building.
"A good MVP is not a simplified product. It's a product focused on what matters most."
Why it's the most cost-effective way to launch
The financial logic is straightforward: the longer you wait before testing your product in the market, the greater your budgetary risk.
Consider two scenarios:
Scenario A — You invest €200,000 over 14 months to deliver a complete product. At launch, you discover that the core feature doesn't convince users. You need to rethink the architecture. Additional cost: €60,000 and a 4-month delay.
Scenario B — You invest €60,000 over 4 months to deliver an MVP focused on the key feature. You test it with 50 real users. Their feedback shows you what works and what needs adjusting. You iterate with confidence. Total budget to reach the same level of maturity: €150,000, in 10 months.
Scenario B costs less, takes less time, and above all — you never built something nobody wanted.
At Twenty, we have measured that this approach reduces delivery time by an average of 30% on projects where it is applied from the outset.
Validated learning: measure to decide
What changes everything with an MVP is moving out of "assume" mode and into "measure" mode.
Once the MVP is in production, you don't ask "do people like it?" — you look at what they actually do:
- How many users return after the first session?
- Which feature do they use first? Which do they ignore?
- At what point do they drop off the journey?
This data replaces opinions and gut feelings. It allows you to prioritise the next developments on a factual basis, not on internal convictions.
This is exactly what we did with School Run, the gamified mental arithmetic app co-founded in 2018. We didn't try to ship everything in the first release. We launched a simple version, measured engagement, and iterated — 20+ successive versions, each driven by real usage data. The result: the app climbed to 4th place on the Google Play Store in its category, present in 8 countries, with a team of 6 people. That wasn't the result of a perfect vision from day one. It was the result of repeated learning cycles.
How we define the scope of an MVP
This is often the hardest question for a founder or executive. There's a natural tendency to want to include "just one more feature" — and that's understandable, because you believe in your product.
Here is the method we apply at Twenty to frame the scope:
1. Formulate the core hypothesis What is the central promise of your product? Not all the promises — the main one. "Our application helps logistics teams reduce order-picking errors."
2. Identify the minimal journey that proves this promise What is the shortest path a user must take to experience this value? Everything that isn't on that path is out of scope for the MVP.
3. List what you're deferring — not abandoning A clear backlog of "phase 2" features reassures stakeholders and structures the future roadmap. Nothing is lost; everything is planned.
4. Define success metrics before you launch Before putting the MVP into production, align on the metrics that will validate (or invalidate) the hypothesis. Without this, you risk interpreting results through your own biases.
On Jarvis, our fleet-management SaaS, and Liveco, the rural-delivery application built in React Native, we applied exactly this logic. Tight scopes at the start, rapid iterations, decisions based on real usage.
The impact on your budget and your organisation
Shipping an MVP doesn't just mean going faster technically. It changes the way you commit resources and make decisions.
On budget: you only invest the "phase 2" budget if phase 1 validates the hypothesis. This is sequential, conditional funding — far healthier than betting everything on an untested vision.
On teams: short cycles (4 to 8 weeks per iteration) keep motivation and focus high. Teams see their work go live quickly, which strengthens engagement.
On risk: you make mistakes on small amounts, not large budgets. And when you make mistakes, you learn something useful for what comes next.
Shipping fast means failing cheaper — and learning faster than your competitors.
With 11 years of experience managing complex projects — at Chanel, Allianz Trade, Air Liquide, MGEN, and others — I have seen that organisations delivering in small iterations consistently pull ahead of those waiting until everything is finished. At Allianz Trade, a project governance model redesigned from scratch increased delivery quality by 40% in six months. Not with more resources — with a better method.
In summary
A well-built MVP is:
- A real product, not a demo
- Focused on a core hypothesis to validate
- Shipped quickly to test against market reality
- Tracked with metrics agreed upon in advance
- The foundation of a roadmap driven by data, not intuition
It's not a way of doing things "worse." It's the smartest and most cost-effective way to build a product that lasts.
Let's talk about your project
You have a product idea or a digital project to launch, and you're wondering where to start, how to frame the scope, or what it will cost?
At Twenty, we support executives and product teams to structure, launch, and scale their projects — with the rigour of a large organisation and the proximity of a trusted partner.
Reach out directly:
- WhatsApp: +33 6 34 42 50 56
- Email: contact@twentyconsultancy.com
A first 30-minute conversation is often enough to clarify the essentials.