Most founders skip validation, build for six months, and learn the painful lesson at launch. This is the shortest path through it: eight steps you can work through in a couple of focused weeks, with a clear decision at the end.
What you'll have when you're done
- A one-sentence description of the idea sharp enough to test.
- Notes from real customer conversations — not friends being polite.
- A clear riskiest assumption and a cheap test to challenge it.
- A signal — paid, committed, or scheduled — that someone wants this.
- A written persevere / pivot / kill decision with a re-check trigger.
Write the idea in one sentence
Force the idea down to a single sentence: who it's for, what painful job it does, and how it's different from what they use today. If you can't, the idea isn't sharp enough to validate yet.
- One target customer, named specifically (not 'small businesses').
- One painful job-to-be-done.
- One sentence explaining why today's workaround isn't good enough.
Map the customer and their current workaround
Before talking to anyone, write down what you believe is true about the customer's day, the moment the pain shows up, and what they reach for now. This becomes the hypothesis you'll test, not the answer you'll defend.
- A day-in-the-life sketch of the target user.
- The exact trigger moment when the pain happens.
- The current tool, spreadsheet, person, or hack they use instead.
Run 5–10 customer-discovery interviews
Interview people who match your target customer, not friends being polite. Ask about the last time the problem happened, not whether they'd buy a hypothetical product. You're listening for emotion, frequency, and money already being spent.
- 5–10 conversations with people in the target segment.
- Past-tense questions ("tell me about the last time…") not hypotheticals.
- Notes on: frequency, severity, current spend, and the words they use.
Map the competitive landscape and gaps
List direct competitors, indirect alternatives, and the do-nothing option. The interesting answer is rarely "no one does this" — it's usually "five tools do part of this badly." That gap is your wedge.
- 3–5 direct competitors with what they're great at and where they fall short.
- The do-nothing / spreadsheet / Slack-channel alternative most people actually use.
- One sentence on the gap you'd own.
Surface the riskiest assumption
Every idea has one assumption that, if wrong, kills it. Usually it's a demand assumption ("people will pay for this") or a delivery assumption ("we can build it for under X"). Name it explicitly before you build anything.
- A written list of the top 5 assumptions the idea depends on.
- The single assumption most likely to be wrong.
- A cheap test you could run this week to challenge it.
Run a landing-page or smoke test
Put up a one-page site that describes the product as if it exists, with a clear call to action — waitlist signup, pre-order, or "book a call." Drive a small amount of targeted traffic (ads, communities, outreach) and measure intent, not vanity.
- A landing page with one clear value proposition and one CTA.
- A traffic source where your target customer actually hangs out.
- A conversion metric you decided on before launching the page.
Get a signal of willingness to pay
Free signups are easy and misleading. You need someone to put something at risk — money, a deposit, a calendar slot, a public commitment. Without that, you've validated curiosity, not demand.
- At least one form of paid or costly commitment from a target user.
- A price point tested in conversation, not pulled from competitor pages.
- A written reason the buyer chose to commit, in their own words.
Decide: persevere, pivot, or kill
Validation isn't a green light — it's a decision point. Compare what you learned against the assumption you started with. Then commit to one of three moves and write down what would change your mind later.
- A one-paragraph summary of what you learned vs. what you assumed.
- An explicit decision: persevere, pivot, or kill — and why.
- The metric or event that would cause you to revisit the decision.
Common questions
How long should validation take?
Two to four focused weeks for most ideas. If it's stretching past six weeks, you're usually researching to feel safer rather than running a real test — pick the riskiest assumption and ship a test this week.
How many customer interviews are enough?
Five to ten is usually enough to spot patterns. You're not aiming for a statistical sample — you're aiming to hear the same pain, in the same language, from people who match your target.
Is a landing-page signup good enough validation?
On its own, no. A free email signup tells you the headline was interesting, not that anyone will pay. Pair it with at least one costly commitment — a deposit, a paid pilot, or a booked call.