Product validation vs market validation — what's the difference

Two different questions, constantly conflated

“We validated our idea” usually collapses two distinct questions into one confident statement: does this specific market want to solve this problem (market validation), and does this specific product solve it well (product validation)? Conflating them leads founders to build a beautifully executed product for a market that doesn't actually want it, or to abandon a genuinely wanted solution because an early prototype was rough.

Market validation — does anyone want this solved?

Market validation tests demand independent of your specific solution. It asks: is this a real, urgent, recurring problem for a definable group of buyers, and are they currently spending time or money trying to solve it? You can validate a market before you've built anything — competitor research, customer interviews, and search-demand data all inform market validation without a single line of product code.

Signals of strong market validation: buyers actively searching for solutions, existing (even imperfect) competitors with revenue, and buyers who describe the pain unprompted in interviews.

Product validation — does this specific solution work?

Product validation tests whether your specific approach actually solves the problem well enough that buyers prefer it to alternatives. This requires something to test — a prototype, an MVP, or at minimum a detailed mockup — and it's measured by usage, retention, and willingness to pay for your specific implementation, not the category in general.

Signals of strong product validation: users complete the core workflow without confusion, they return without being prompted, and they choose to pay rather than churning to a free alternative.

Why the order matters

Market validation should come first, because it's far cheaper to test and it determines whether product validation is even worth attempting. A team that skips straight to product validation (“let's build an MVP and see if people like it”) risks spending months building something well before discovering the underlying market doesn't actually want it solved badly enough to pay.

The reverse mistake also happens: teams validate a huge, obvious market need, then assume any reasonable product will succeed — and get outcompeted by a team that validated the market identically but built meaningfully better product execution.

A practical sequencing

1. Market validation first: customer interviews, competitor mapping, search-demand checks — establish that the problem is real and urgent before building anything.
2. Cheap product validation:a landing page, a clickable prototype, or a manual “concierge” version delivered by hand — test whether your specific approach resonates before investing in a real build.
3. Full product validation: a working MVP tested with real usage, retention, and payment data from actual customers in your validated market.

Where structured scoring fits

A structured idea validator like Skip or Ship primarily assesses market-validation signals — demand, competition, buyer clarity, monetisation realism — since these can be evaluated from a description alone, before any product exists. It complements, rather than replaces, product validation once you have something real to test.