Contents

You can validate a product idea before development through conversations with potential customers, a landing page with a price and sign-up button, doing the service by hand instead of automating it, and selling before launch. The goal is evidence that the problem exists, people will pay to solve it and you can reach them. All of this costs far less than a first product version.

Here are the validation methods, how to tell a hypothesis is confirmed and the common traps.

What exactly should be validated before development?

Validate three hypotheses before development: people really have the problem, they will pay to solve it, and they can be reached at a reasonable cost. Product features and design are secondary at this stage — if any of the three fails, no implementation will save the product.

Hypothesis Question How to test
Problem Does it hurt, and how often Interviews, studying how people cope today
Value and price Will they pay, and how much Pre-orders, a priced landing page, manual sales
Channel Can customers be acquired affordably Test ads, partnerships, communities
Solution Does your approach solve the problem A prototype, delivering the service by hand

We covered how product economics depend on price and acquisition cost in SaaS unit economics.

How do you interview potential customers?

Interview people about their past experience, not a hypothetical future: how they solve the problem today, what it costs, what annoys them. "Would you buy this?" almost always gets a polite "yes" that means nothing.

Rules for a good interview

  1. Ask about specific cases: "Tell me about the last time this happened".
  2. Find out what they have already tried and what it costs them in time and money.
  3. Do not pitch your idea at the start, so you do not lead the answers.
  4. Look for problems that repeat across different people, not one vivid opinion.
  5. Do at least 10–15 interviews in one segment before drawing conclusions.

A strong signal is that someone already pays for an awkward solution or spends lots of time on the problem. A weak one is "it would be great if someone built this".

A person holding a light bulb Photo: Unsplash

Which experiments are cheaper than development?

Experiments that imitate the product or do its job by hand are cheaper than development: a landing page with a price and sign-up form, pre-orders, a manual service, a no-code prototype. They test demand in days or weeks instead of months.

Popular formats:

  • a priced landing page — a product description, a plan and a "Request access" or "Pre-order" button; measure conversion from ads;
  • a manual service — you do by hand what the product will later do, for the first customers;
  • a no-code prototype — forms, spreadsheets, builders and automations instead of development;
  • selling before launch — a contract or prepayment from first customers;
  • a clickable prototype — testing whether flows make sense to users.
Example landing page experiment
Hypothesis: small coffee shop owners will pay $19 a month
            for automatic stock tracking
Experiment: a priced landing page + ads to the target audience, 2 weeks
Success criteria: at least 3% of visitors sign up,
                  at least 5 calls confirm willingness to pay
Decision: success → manual pilot with 5 shops; failure → revisit price or segment

How do you know the idea is validated?

An idea is validated when success criteria set in advance are met: people sign up, agree to a pilot and, above all, pay. Define the criteria before the experiment — otherwise any result can be declared a success.

Reliable signals:

  • customers pay or prepay;
  • customers come back on their own and ask when the product will be ready;
  • in a manual pilot, customers use the solution regularly;
  • acquisition cost in test channels fits the economics.

Unreliable signals are likes, "notify me at launch" sign-ups and friends' compliments.

What should you do after successful validation?

After successful validation, move to a minimum viable product that automates what was proven and nothing more. The interview and experiment results become the basis of requirements, which makes the next stage noticeably faster and cheaper.

The order:

  1. Record the conclusions: segment, problem, price, channels.
  2. Describe first-version scenarios based on what you did by hand.
  3. Go through a design stage — see the discovery phase explained.
  4. Build the MVP — budget and timelines in how much an MVP costs.
  5. Keep measuring: activation, retention, payments.

In short

  • Before development, validate the problem, willingness to pay, the acquisition channel and the solution.
  • Interview people about their past experience, not hypothetical purchases.
  • A priced landing page, manual service and pre-launch sales cost a fraction of development.
  • Set success criteria before the experiment; the best signal is payment.
  • After validation, build an MVP of only what was proven.

FAQ

  • Won't someone steal the idea if I talk about it?

    The risk is small: value lies in execution, not the idea. It is far more dangerous to spend months building something nobody needs because you never discussed it with anyone.

  • How long does validating an idea take?

    Usually from a few weeks to a couple of months: interviews, one or two landing page or manual service experiments and analysis. That is far faster and cheaper than building a first version.

  • What if validation does not confirm the idea?

    That is a result too: you saved the development budget. Work out which hypothesis failed — changing the segment, price or problem framing and running a new experiment often helps.