Can you explain the difference between validating a product and validating an idea?

Idea validation tests whether anyone wants the thing — measured with a landing page, paid ads, and a conversion threshold against strangers. Product validation tests whether the built thing actually delivers — measured with usage, retention, NPS, and churn against real customers. Idea validation runs before any code is written; product validation runs after a working product is in users' hands. Different questions, different methods, different success criteria.

What is the process for validating an idea for a new product or service in an industry where similar products exist?

The existence of competitors is good news — it removes the "is there a market" risk. The remaining risk is whether your specific angle resonates. Run a landing page that names the wedge (your differentiator vs incumbents), drive €150–€250 of paid traffic from two channels, and look for conversion above your category benchmark. If you can't find a clean wedge, the idea isn't differentiated enough — that's the result, and it's a useful one.

Is it beneficial to have a minimum viable product (MVP) as the first product after validating a startup idea?

Yes — but only after idea validation, and only if the MVP is the smallest thing that delivers on the page promise. The point of an MVP is product validation: does the built thing retain users, get used weekly, generate referrals? If you skip idea validation and go straight to MVP, you're using the most expensive method to answer the cheapest question.

What's the difference between idea validation and market research?

Market research describes a market — size, segments, trends, competitors. Idea validation tests a behavioural commitment from a real person, with their attention or money on the line. Market research can tell you the TAM is €4B; idea validation tells you whether 5% of clickers will hand over an email. The first is a desk exercise. The second is an experiment. You need both, but they answer different questions.

Where does offer validation fit between idea and product validation?

Offer validation sits between the two and tests whether people want this specific version — pricing, packaging, scope. It uses pre-sales, design partner programs, or paid pilots to convert "do they want it?" into "do they want it at €49/mo with these three features?". Skipping it is why some founders ship a product that gets signups but no payments.

Validating an Idea vs Validating a Product: What's the Difference?

Two different questions, two different tests, and founders use the same word for both.

We've had this exact conversation more times than we can count. A founder says they've "validated their idea" — they have 80 beta users, retention is okay, NPS is 32. Another founder says they've "validated their idea" — they ran a landing page test, got 6% conversion across 800 visitors, killed the project, started over.

Both used the same word. Neither used it the same way.

The first founder did product validation: they built a thing and watched whether it got used. The second did idea validation: they tested whether anyone wanted the thing before it existed. The confusion isn't academic — it costs founders months and tens of thousands of euros every year.

Idea validation answers "do they want it?" — tested with a landing page and paid ads, before code. Product validation answers "does the built thing work?" — tested with usage and retention, after code. They are sequential, use different methods, and have different success criteria. Mixing them up is the most common — and most expensive — mistake in early-stage product work.

Idea validation, defined

Idea validation is the test you run before you build. The question is binary in spirit: would a stranger, with no relationship to you, hand over something of value (an email, a deposit, a calendar slot) in response to a promise the product hasn't kept yet?

The mechanics are well-rehearsed at this point:

Method: a landing page that describes a single, sharp offer. Headline, three benefits, one CTA.
Traffic: €150–€250 of paid ads from two channels (Reddit + Meta, or Meta + Google Search).
Time: 10–14 days, 800–1,500 unique visitors per channel.
Success criteria: a pre-committed conversion threshold. 5%+ for a B2C waitlist. 1.5%+ for a €5–€20 pre-payment. 2%+ for a B2B "book a 15-min call". Consistent on both channels.
Cost: €200–€400 all-in, including ad spend and a basic page tool.

What idea validation does not measure: whether the product is good. Whether users retain. Whether they'll pay long-term. None of that. Idea validation measures one thing — initial interest from strangers in response to a stated promise.

That's a feature, not a limitation. The whole point is to find out, cheaply, whether the promise resonates. If it doesn't, no amount of product polish fixes that.

Product validation, defined

Product validation is the test you run after you build. The question shifts: now that the thing exists and a small number of people are using it, does the behaviour match what we expected?

The mechanics are different, and they take longer:

Method: deploy the smallest real version of the product to a small cohort of real users (waitlist signups, design partners, early customers).
Traffic: not the relevant input — usage and retention are.
Time: 30–90 days minimum. Some signals (long-term retention, referrals) need 6+ months.
Success criteria: weekly active usage above a threshold (often 30–40% of signups), 4-week retention above 25–35%, churn below 5–7% per month for paid SaaS, NPS in the +30 to +50 range, and — the strongest signal of all — unpaid word of mouth.
Cost: the cost of building, plus the operational cost of supporting early users. Orders of magnitude more than idea validation.

Product validation can clear when idea validation didn't. We've seen it happen — a founder skips the landing page test, builds anyway, finds 30 people who genuinely use the product weekly. That's a real signal. It's also a far more expensive way to learn what €200 of ad spend would have told them in two weeks.

Product validation can also fail when idea validation passed. A great waitlist doesn't guarantee a great product. The thing the page promised has to be deliverable, and the built version has to actually deliver it. Idea validation buys you the right to spend the next 4–6 weeks building. It does not guarantee the build will work.

The in-between: offer validation

There's a step most frameworks skip, and it lives between idea and product validation. We call it offer validation.

Idea validation tells you they want something in this space. Offer validation tells you they want this specific version — at this price, with this scope, in this packaging. It's the difference between "I'd use a tool that does X" and "I'll pay €49/month for the version that does X with three specific features I need".

The methods that fit here:

Pre-sales. Take real money for the unbuilt product via Stripe Payment Links or Gumroad. Even €10 deposits are a 100x stronger signal than a free signup.
Design partner programs. Offer the first 5–10 customers a discount in exchange for weekly feedback calls. They commit before the product is finished.
Paid pilots. For B2B, a 90-day paid pilot at €100–€500/month tells you whether the offer makes economic sense to the buyer.

Offer validation is what catches the "they signed up, but they won't pay" trap. We've watched founders build a product because their waitlist had 1,200 signups, only to find out at launch that nobody wanted to pay €19/month for the version they'd built. Offer validation would have surfaced that in week three, not month four.

The order matters: idea → offer → product

Picture three gates the idea has to pass through, in order. Each gate gets more expensive to run, and answers a sharper question.

Gate one is idea validation. €200, two weeks, paid traffic against a stated promise. Out the back of gate one comes either a clean kill (cheap, useful) or a green light to spend more money learning more.

Gate two is offer validation. €0–€2,000, two to four weeks, real money or real commitments from a small group. Out the back of gate two comes either a refined offer (price, scope, audience locked in) or a re-scope decision before any building starts.

Gate three is product validation. The cost of building plus 30–90 days of operating an early version. Out the back of gate three comes either a product that earns the right to grow, or a real, painful, expensive lesson about what didn't carry over from the page promise.

The flow looks like this: a noisy bucket of raw ideas drops into gate one, and 60–80% of them get filtered out cheaply. The survivors enter gate two, where another 30–50% get re-scoped or killed. The ones that make it to gate three are the ones worth the build cost. Skipping gates one and two doesn't make you faster — it just shifts the cost of being wrong from €200 to €20,000.

The cost of mixing them up

We see two failure modes constantly, and they're symmetrical opposites.

Failure mode one: skip idea validation, try to fix it with product validation. The founder builds for three months, launches to crickets, and spends the next six months "iterating on retention" on a product that nobody wanted in the first place. Retention work can't fix demand. If the underlying promise doesn't resonate with strangers, no amount of onboarding tweaks, NPS surveys, or feature additions will conjure demand into existence. We've watched founders sink €30–€80k of runway into "product fixes" for a problem that was actually upstream — they should have run a €200 idea-validation test 90 days earlier.

Failure mode two: clear idea validation, skip product validation, assume the work is done. The founder runs a clean €200 test, gets 6% conversion across two channels, builds for six weeks, ships, and assumes the waitlist will convert because the validation said so. Two months in, weekly usage is at 8%, retention is collapsing, and they don't know why. The page promised something the product can't deliver — and they didn't check whether the build was matching the promise until it was too late. Idea validation buys the right to build; it doesn't guarantee the build will work.

Both failures come from treating "validation" as a single event. It's three events. They run in order. They answer different questions.

A comparison table

The differences in one place:

Dimension	Idea validation	Offer validation	Product validation
Question	Do they want it?	Do they want this version?	Does the built thing work?
When	Before any code	Before final scope	After shipping
Method	Landing page + paid ads	Pre-sales, design partners, paid pilots	Usage analytics + retention cohorts
Success metric	Conversion threshold (5% B2C waitlist, 1.5% pre-payment, 2% B2B call)	Real money committed by 5–20 people	Weekly active 30%+, 4-week retention 25%+, NPS +30
Time	10–14 days	2–4 weeks	30–90+ days
Cost	€200–€400	€0–€2,000	Build cost + ops
Fails when	Strangers don't convert	Signups won't pay	Users don't come back

How LemonPage fits

LemonPage is built for the first gate — idea validation. Page generation, ad-channel setup, conversion tracking, kill-criterion notes, all compressed into a 14-day workflow under €250. Once an idea clears that gate, you graduate to offer and product validation, which use different tools and different timelines. The gates are sequential. Skipping the first one is what sends most pre-launch projects to the graveyard.

Mix up these three gates and you spend a year solving the wrong problem. Run them in order and the wrong problems get cheap.