MVP: how to validate an idea without burning through your budget

Most startups don’t fail because the product is badly built. They fail because nobody wanted it. That’s exactly what an MVP is for: finding out as early as possible, and with the smallest possible investment, whether your idea solves a real problem that someone is willing to pay for.

What an MVP really is

MVP stands for Minimum Viable Product. But the most important word isn’t “product.” It’s learning.

An MVP isn’t the budget version of your complete idea. It’s the smallest experiment that lets you test the riskiest assumption in your business. Sometimes it’s an app. Far more often, at the start, it’s something much simpler.

Let’s take an example. If your hypothesis is “restaurant owners would pay to manage bookings from a single app,” the first question isn’t how to build the app. It’s this: do restaurant owners really feel this problem? And do they feel it enough to change their habits and pay?

Before the code: validate the problem

Before you invest in development, spend two or three weeks talking to the people you want to serve.

The right interviews

Set up 20–40 conversations with potential customers. Don’t pitch your idea: ask about their lives. How do they solve the problem today? How much time or money do they lose to it? What have they already tried?

The questions to avoid are the ones that ask for an opinion about the future, like “Would you use an app that…?” Almost everyone will say yes just to be polite. Useful questions are about the past and about concrete behavior.

The signals to look for

A problem is worth solving when:

• people bring it up without you prompting them;
• they’ve already tried to solve it, perhaps with spreadsheets or makeshift workarounds;
• they already spend time or money on it;
• they ask you when the solution will be ready.

Choose a single metric

Every experiment needs a clear question and a number that measures it. Before you start, write down:

1. The hypothesis, for example “at least 10% of visitors will leave their email to join the waitlist.”
2. The metric, in this case the sign-up rate.
3. The success threshold, the number above which you keep going and below which you change course.

Setting the threshold in advance is essential. Afterward, it’s far too easy to convince yourself that any result is “promising.”

Three low-cost MVP formats

The landing page with a waitlist

A page that describes the solution as if it already existed, with an invitation to sign up. Paired with a small ad campaign, it tells you within days whether the message resonates and how much it costs to acquire a lead. It costs a few hundred euros.

The manual service

Deliver the outcome your product promises by doing everything by hand, behind the scenes. If your app is meant to create personalized meal plans, start by creating them yourself and sending them by email. You’ll discover what customers really want before you automate anything.

The clickable prototype

An interactive prototype, built in a few days, looks like a real app but has nothing behind it. It’s perfect for testing the user flow with real users and for showing your vision to investors.

The best MVP is the one that gives you the most reliable answer for the least money.

The most common mistakes

In years of working with startups, we’ve seen the same mistakes come up again and again.

• Building too much. Every extra feature stretches the timeline and muddies the results. If it doesn’t help test the hypothesis, it can wait.
• Falling in love with the solution. The goal is to solve a problem, not to bring your idea to life at any cost.
• Asking friends and family. They love you, and that’s exactly why they aren’t a reliable sample.
• Ignoring price. If no one has ever paid, you haven’t validated the business yet. Try to sell, even as a pre-sale.
• Not setting a deadline. An experiment with no end date turns into a never-ending project.

When it’s time to build

You’re ready to develop a true MVP, meaning a working product, when you have three pieces of evidence in hand: a problem confirmed by dozens of conversations, a group of people waiting for the solution and at least one concrete signal that they’re willing to pay.

At that point, build only the core of the product: the one feature that solves the main problem, done well. Everything else can wait for the next version, guided by data from your first users.

That’s exactly the path we follow in our Startup Studio: validation, MVP, launch and growth, one step at a time, with every decision based on the numbers. If you have an idea and want to know whether it has a market, let’s talk. We’ll help you turn it into a concrete plan before you spend a single euro on development.