The Feature List Is Lying to You
Every client starts with a feature list that’s twice as long as it needs to be. 47 features, 12 integrations, 6 user roles. The total estimate comes back at EUR 200,000 and 9 months. Sticker shock follows.
But here’s what nobody asks: which of those 47 features actually solve the core problem?
Usually, it’s 5-8 of them. The rest are nice-to-haves, future ideas, and features borrowed from competitor products your users don’t care about.
This is the MVP question. Not “how do we build less?” but “how do we learn faster?”
What an MVP Actually Is (and Isn’t)
An MVP is the smallest version of your product that delivers value to real users and generates feedback you can learn from. Not a prototype. Not a demo. Working software with real users.
It’s not a crappy version of the full product. A good MVP does fewer things but does them well. Think of it as version 1 that solves one problem completely rather than ten problems poorly.
The term gets abused. Agencies use “MVP” to mean “the first phase of the contract.” That’s not an MVP. That’s phase 1 billing.
When to Start with an MVP
Your idea is unvalidated. If you haven’t proven that people will use (or pay for) your product, building the full version is gambling. An MVP at EUR 40,000-80,000 tests the hypothesis. A full build at EUR 200,000 bets the company on it.
You’re replacing a manual process. If the current process involves spreadsheets, email chains, and sticky notes, even a basic custom tool is a massive improvement. You don’t need all the bells and whistles.
Just the core workflow, automated.
Your budget is constrained. An MVP costs 30-40% of a full build. Launch it, prove ROI, then use the results to justify the investment for phase 2. We’ve seen this work repeatedly with SMB clients.
You’re entering a new market. When you don’t fully understand user behavior yet, building everything is premature. Ship the MVP, watch how people actually use it, then build what they need.
When to Skip the MVP
Your requirements are clear and stable. If you’ve been running a process for years and know exactly what software you need, an MVP adds unnecessary iteration. Build it right the first time.
Compliance demands a complete solution. Regulated industries often can’t deploy partial solutions. If your software handles healthcare data or financial transactions, half-built isn’t an option.
You’re rebuilding an existing system. If you’re replacing a legacy tool that 200 people use daily, an MVP that covers 30% of features won’t cut it. Users need parity (or close to it) before they’ll switch.
The Cost Math
A typical full build for an SMB project: EUR 100,000-250,000 over 6-12 months. A typical MVP: EUR 30,000-80,000 over 2-4 months.
But the real savings aren’t in the build cost. They’re in what you learn.
One SaaS startup built a EUR 45,000 MVP for a project scheduling tool. User testing revealed that their core assumption (users wanted drag-and-drop scheduling) was wrong. Users wanted automated scheduling. They pivoted before spending another EUR 150,000 on the wrong product.
If they’d built the full product first, that pivot would have cost EUR 200,000 instead of EUR 45,000. Discovery through building beats discovery through guessing.
How to Define Your MVP Scope
Ask three questions.
What is the one problem this software must solve? If you can’t answer in one sentence, your scope is too broad.
What is the minimum feature set that solves it? List every feature you want. Now cross off everything that isn’t required to solve the core problem. What’s left is your MVP.
How will you measure success? “People like it” isn’t measurable. “50% of users complete the core workflow without assistance” is. Define success before you build.
The Phase Model
Most custom software projects follow a three-phase pattern.
Phase 1 (MVP): Core workflow, 5-8 features, 2-4 months. Launch to a small user group.
Phase 2 (Expand): Add features based on real usage data. Integrations, reporting, additional user roles. 2-4 months.
Phase 3 (Optimize): Performance tuning, advanced features, scaling. Ongoing.
This model manages risk. Each phase proves value before the next one starts. If phase 1 doesn’t deliver results, you’ve spent EUR 50,000, not EUR 200,000.
For more on budgeting, see what custom software actually costs. And for help defining your requirements, read how to write a software requirements document.
Not sure whether to go MVP or full build? Let’s figure it out together. We’ll scope both options and give you a clear comparison so you can decide with confidence.
