MVP and market validation: how to start

The most costly risk for a startup is not building badly: it is building something no one wants. The MVP and market validation serve exactly this purpose — discovering whether there is demand while spending as little as possible, before investing months and capital. Here is how to start with method.

What an MVP really is

MVP stands for Minimum Viable Product: the simplest version of the product capable of producing real learning about the market. It is not a “poorly made” product, but an essential one, reduced to the function that solves the core problem.

The common mistake is confusing the MVP with the first complete version. The MVP does not have to please everyone: it must answer a precise question — do people have this problem and are they willing to pay to solve it? Everything that does not help answer it is, for now, superfluous.

Before building: validate demand

Much validation can be done without writing a line of code. Some tools:

Interviews with potential customers: not “would you like it?”, but “how do you solve this problem today? how much does it cost you?”. Questions about the past reveal real behaviour; questions about the future gather courtesies.
Landing page with a clear proposition and a call to action: you measure how many people leave their email or click.
Preorders or letters of intent: the strongest signal is someone putting time or money on the line.
“Manual” MVP: you deliver the service by hand behind the scenes before automating it. You learn a great deal with minimal investment.

The goal is to gather evidence of demand, not convenient reassurances.

The metrics that matter

To validate is to measure. Some useful metrics in the early stages:

Conversion rate: how many people take the desired action relative to how many see it.
Retention: do those who try the product come back to use it? Retention is the most honest signal of real value.
Willingness to pay: declared interest and money spent are different things.
Acquisition cost relative to customer value: even rough estimates help understand whether the model can work.

Beware of vanity metrics: followers, newsletter subscribers or downloads do not pay salaries. Watch the numbers that indicate economic behaviour.

Build to learn, not to impress

Every version of the MVP should test a hypothesis. Frame it in a verifiable way: “if we offer X to this segment, at least Y% will convert”. Then measure and decide: persevere, correct or abandon. This cycle — build, measure, learn — is what distinguishes those who advance by evidence from those who advance by opinion.

Define in advance what you consider a success. Without a threshold, any result can be interpreted as positive, and validation loses its meaning.

When the MVP becomes a product

When the demand signals are solid — customers who come back, who pay, who recommend — it is time to invest in the more complete version. At that point the traction gathered also becomes your best argument before an investor: you are not telling an idea, you are showing proof. The transition is not a switch but a progression: functions are added one at a time, checking that each one genuinely increases retention or willingness to pay, rather than weighing the product down without reason.

Frequent mistakes

Building too much before speaking to a single customer.
Seeking confirmation instead of seeking the truth.
Stopping at vanity metrics.
Not setting in advance what counts as validation.
Falling in love with the solution to the point of ignoring contrary signals.

How we help you

At SIH ONE we support founders in the early stages: setting up hypotheses, designing experiments, reading the metrics and preparing for capital once traction is achieved. Reducing risk before scaling is the most efficient way to use time and resources.

Do you want to validate your idea with method before investing? Talk to the Ventures division.