How to Validate a Product Idea Before You Build

What validation really means

Validation is not asking friends if your idea sounds good. It’s gathering evidence that a specific customer has a painful problem and will pay to solve it. Roughly seven in ten ideas fall apart the moment you test them against real people - and building takes months while validating takes days.

The validation framework

Validate the problem first. Before any solution, confirm the problem is real and painful enough that people already try to solve it some other way.
Talk to 10–15 real customers. Not friends. Look for the same problem described, unprompted, in their own words.
Test willingness to pay. Interest is cheap. Ask for a deposit, a pre-order, or a letter of intent. Money is the only honest signal.
Pressure-test the idea in writing. Make the customer, problem, and value concrete before you build (next section).

Validate on paper first

Before a landing page or a prototype, there’s an even cheaper test: writing the launch story. The Working Backwards method makes you draft the press release and FAQ as if the product already shipped. Vague answers surface instantly - if you can’t name the customer or the value in a paragraph, you’ve found the gap before spending an engineering hour.

Why writing beats building

A PR/FAQ catches the three killers - a fuzzy customer, a soft problem, and a benefit that doesn’t beat the status quo - in a document instead of in production. It’s the highest-leverage validation you can do in an afternoon.

Signals vs. noise

Signal: customers describe the problem before you do, and ask when they can pay.
Noise: “That’s a cool idea” with no follow-through.
Signal: people already hack together a workaround today.
Noise: enthusiasm only from people who’ll never be customers.

FAQ

How do I validate a product idea?

Validate the problem before the solution: confirm a specific customer has a painful problem, test whether they'll pay to solve it, and pressure-test the idea in writing before building. Most ideas fail one of these - and it's far cheaper to learn that on paper than in code.

How many customer interviews do I need?

Usually 10 to 15 is enough to see a pattern. If eight or more describe the same painful problem in their own words, you have a real signal worth pursuing.

What's the cheapest way to validate an idea?

Writing. A Working Backwards PR/FAQ forces you to make the customer, the problem, and the value concrete in an afternoon - exposing weak ideas before you spend a dollar building.

Does a landing page validate an idea?

Partly. A landing page with a clear offer tests interest and messaging, but real validation requires evidence of willingness to pay - a deposit, a pre-order, or a signed letter of intent.

Pressure-test your idea in minutes

Turn your idea into a PR/FAQ and a scored verdict - see whether it holds up before you build. Free to start.

Start your PR/FAQ

Design by The Resonance | Powered by GPC – The AI Transformation Company

Working Backwards is an independent tool from The Resonance. It is not affiliated with, endorsed by, or sponsored by Amazon.com, Inc., Working Backwards LLC, or the authors or publisher of Working Backwards: Insights, Stories, and Secrets from Inside Amazon. Amazon, Kindle, Prime, Alexa, and AWS are trademarks of Amazon.com, Inc. or its affiliates, referenced only to describe the methodology’s origin. All other trademarks belong to their respective owners.