← GuidesStrategy8 min read
How to Validate a Business Idea Before You Build It
Listen to customers, find the pattern that keeps repeating, and pre-sell an offer before investing in it.
01 · The problem
Most people never find out what customers will pay for
Many businesses never systematically identify the problem customers will pay to solve. They make an educated guess, invest in building it and discover the gap after launch.
Two real conversations
"I'd pay for a mastermind."
One person told me straight up he'd pay to be in a group with other people working on the same thing. Not a course. Not a call. A room.
"I'd pay for information."
Another said he'd pay for information. Give him the knowledge, organized, so he can go do it himself.
Same topic, two completely different products. If I'd guessed, I'd have been right for one and wrong for the other.
The thing to sell is usually the thing people keep telling you they need, or clearly don't understand.
02 · The method
Watch what people actually spend time on
Don't trust what people say they want as much as what they do: what they read, reply to and react to.
Watch
What do they read, reply to, save, react to and ask about?
Log
Write every signal down. Same table, every time.
Pattern
Once a week: what theme keeps coming back?
Test
Turn the theme into a small offer and pre-sell it.
The three signals that matter most
What they keep asking Repeated questions
The same question from three different people is a product. They're telling you where they're stuck.
What they engage with Time and attention
Which posts get saves, replies and long reads? Which page do people stay on? Attention is a vote.
What they don't understand Confusion = opportunity
"I don't get how this works." "I've tried everything." That gap is what people pay to close.
03 · Where the signal is
Ten places to listen
You already have most of this. You're just not writing it down.
| Source | What to look for |
|---|---|
| DMs and texts | "How do you…", "can you help me with…". Gold. |
| Calls and in-person chats | What they bring up before you ask. What they complain about. |
| Reviews, yours and competitors' | Why they came, what surprised them, what they wish was different. |
| Comments | Questions under posts, "need this," tagging friends. |
| Story replies and polls | Which topics get people to actually reply. |
| Your FAQs | The questions you're tired of answering are the ones people need most. |
| Search terms | Search Console queries and your site search: their exact words. |
| Time on page | Which pages hold attention in Google Analytics, and which get skipped. |
| Saves and shares | A save means "I want this later." A share means "this is about me." |
| What they buy | Your sales history: what sells, what gets added on, what gets rebooked. |
04 · Ask without leading
Good questions vs. bad questions
Most customer interviews produce polite answers rather than useful ones. "Would you buy this?" "Sure." Then no one buys.
| Bad (leading) | Good (past behavior) |
|---|---|
| "Would you buy a guide on X?" | "Last time you tried to fix X, what did you do?" |
| "Don't you think X is a big problem?" | "What's the hardest part about [area] for you right now?" |
| "Would you pay $___ for this?" | "Have you ever paid for help with this? Was it worth it?" |
| "Do you like my idea?" | "What have you already tried? What didn't work?" |
| "Would this be useful?" | "When did this last come up? What happened?" |
"Would you pay for…" isn't banned. It's just weak on its own, because people are nice. Ask it last, after you've heard about their real behavior, and then make it real: "I'm opening 10 spots. Want one? It's [price]." A deposit tells you more than any yes. This is the core idea of Rob Fitzpatrick's The Mom Test, which is worth reading in full.
05 · The tracker
One simple table, every signal
Spreadsheet, Airtable, notes app, whatever. Same columns every time. One row per signal.
| Date · person | Theme | What they asked · pain · pay signal |
|---|---|---|
| [date] · Client A | [theme] | Asked how to [x] · frustrated it keeps happening · has paid for [y] before |
Willingness-to-pay signals, weakest to strongest
| Signal | What it means |
|---|---|
| "That's cool" | Nothing. Polite. |
| Saves, asks follow-up questions | Interest. Worth tracking. |
| Already paid someone else for it | Real money has moved for this problem before. |
| Asks "how much?" or "can I book?" | Strong. They're ready to buy. |
| Joins a waitlist, pays a deposit, pre-orders | Strongest. This is validation. |
06 · Find the theme
15 minutes a week to spot the pattern
One signal is a story. The same signal five times is a pattern. Pick a day, open your tracker, and:
- Group this week's rows by theme. Give the same thing one name.
- Count how many times each theme came up, and from how many different people.
- Check the pain: "nice to have" or "this keeps me up at night"?
- Check the pay signals: which theme has the strongest?
- Pick one theme to watch next week, or to test if it's already strong.
A real theme
Comes up again and again, from different people, with real pain and some sign they'd spend money or time on it.
A false theme
One loud person. Or something only you care about. Or a topic people like but would never pay for.
Consistency is the tell. Find the theme that won't go away.
07 · Test it
Turn the theme into a test offer
Don't build the whole thing first. Make the smallest version you could sell, and sell it before it exists.
Info product
A guide, checklist or short video series. For "I'd pay for information" people.
Group or mastermind
A small group that meets regularly. For "I want people working on this with me" people.
Service
You do it for them. For "I don't want to learn it, just fix it" people.
Package
A bundle around one outcome. For "I want the full result" people.
Validate with pre-sales or a waitlist
- Write one paragraph: who it's for, the problem, what they get, when, and the price.
- Send it to the people in your tracker who raised that theme. Post it once.
- Ask for something real: a deposit, a pre-order, or at least a waitlist signup.
- Set a goal before you start, like the number of spots that makes it worth it. Hit it? Build it. Miss it? Learn why.
08 · Worked example
A local spa: a hypothesis, not a fact
How the method looks at a local spa. No real data here, just the structure. The point is to find out instead of guessing.
Starting guess Hypothesis A
"Clients want a guide on a healthier body and no back pain."
Competing guess Hypothesis B
"Clients actually want to know how to keep their face looking young."
How to find out 4 weeks of listening
The front desk logs every client question. One story poll and one post per topic; compare replies and saves, not likes. Read reviews and DMs for repeated words. Check which service pages hold attention and which services get rebooked.
Then test Whichever wins
Open a waitlist for a short guide or a small workshop on the winning theme. Signups and deposits decide, not opinions.
⌘ · Copy-paste prompts
Let AI find the pattern
Below are customer messages, reviews and comments for my [business]. Group them into themes. For each theme give: how many times it appears, a few exact quotes, the underlying pain, and any sign they'd pay (already paid for it, asked the price, asked to book). Rank by strength. Don't invent anything not in the text.
[paste, names removed]Here is my signal tracker (date, person, what they asked, theme, pain, pay signal). Merge duplicate themes, count unique people per theme, and tell me the one theme with the strongest mix of frequency, pain and pay signals. Then tell me what I still don't know about it.
[paste table]I want to learn whether my customers have a real problem with [topic]. Write 8 questions about their past behavior, not future intentions. No leading questions, no pitching. Then add 3 follow-ups to dig deeper.Newsletter
Get new guides by email.
New guides and articles when they’re published. No spam, and you can unsubscribe anytime.