To validate a side project idea before you build, talk to five people who already have the problem, one at a time, for about 20 minutes each. Ask about the last time the problem happened, what they use today, and what they have already paid or tried. Do not pitch your idea. Log each call in the same sheet within ten minutes, then score the five together. If at least three describe the same job, name a real workaround and give you a costly signal (a referral, a test slot on their calendar, or money), build a thin slice. If the pain is real but points at a different job or a narrower group, pivot and run five more. If you hear only compliments, stop. The whole loop fits in 14 evenings around a day job.
Last updated: Nov 16, 2026
Most employed builders do the same expensive thing: they spend three months of evenings shipping a side project, then discover nobody wanted it. The code was fine. The screenshots looked sharp. The problem was never real enough for anyone to pay, switch, or even reply.
You do not need a survey panel or a poll to avoid that. You need five real conversations before you build. Not five “what do you think of my idea?” pitches. Five structured chats with people who already feel the pain, who will tell you what they pay for today, what they hate about it, and whether they would try something else.
This guide covers who to ask, how to get them on a call, a 20-minute script, a log sheet, blunt go / pivot / stop rules, an illustrative worked example, and a 14-day sprint. It also covers what the research on interview sample sizes says about the number five, because “five” is a starting batch, not a magic number.
Why should you validate a side project idea with conversations first?
Because the most common way products die is building something the market does not need, and that failure is visible long before launch if you ask the right people. In its March 2026 analysis of 431 venture-backed startups that shut down since 2023, CB Insights found poor product-market fit cited in 43% of the 385 cases where a failure reason could be identified. Two-thirds of those product-market-fit failures were early-stage companies that never found a market.
Those were funded companies with teams. A side project has fewer evenings to burn and no investor to absorb the loss. A conversation costs you 20 minutes. A wrong build costs you a season.
Conversations also beat the alternatives at this stage. A landing page tells you whether a headline gets clicks, not why. A survey tells you what people say they would do. A conversation, run well, tells you what they already did, which is the thing that predicts what they will do next.
Are five conversations really enough to validate an idea?
Five is enough to make a first decision and small enough to finish while you hold a job. It is not proof, and the research says so plainly. Here is what the studies people usually quote actually found:
Study | What it found | What it means for your five calls |
|---|---|---|
Griffin & Hauser, The Voice of the Customer (1993), office-equipment data | One one-hour, one-on-one interview surfaced about 33% of customer needs; two surfaced 51%; four surfaced about 72%. One two-hour focus group did about as well as two individual interviews (50% vs 51%). | Talk to people one at a time. A group chat or a panel is not more efficient. |
Griffin & Hauser (1993), 30-customer study | 30 interviews produced 220 distinct needs; 20 interviews found over 90% of them. The authors estimate 20 to 30 interviews find 90 to 95% of needs. | Five calls will not find every need. They will find the loud, repeated ones. |
Guest, Bunce & Johnson, How many interviews are enough? (2006) | Across 60 interviews, 34 of the 36 high-frequency codes (the building blocks of their themes) had appeared after the first 6; 35 after 12. Saturation came by 12. | If your interviewees are a tight, similar group, the main pattern shows up early. |
Nielsen Norman Group, How many participants for a UX interview? (2021) | Five interviews are often too few for exploratory research; start with 5 or 6 and keep going while you are still learning new things. | Treat five as batch one. If answers are scattered, run a second batch before you decide. |
Two practical rules fall out of that. First, keep the group narrow: “freelance bookkeepers with 10 to 30 clients” saturates far faster than “small businesses.” Second, analyse after every call, not after all five. If calls four and five still bring brand-new pains, you are not done.
What counts as a validation conversation (and what does not)?
A conversation is a live talk, by video, phone, or coffee, with one person who matches (or closely proxies) your intended customer. Twenty minutes. You ask about their world. You take notes. You do not demo your half-built app.
It is not:
A Google Form with twelve multiple-choice questions
A post asking “would you use this?”
Friends saying “sounds cool, I’d use that”
Likes on your announcement post
You talking for fifteen minutes while they nod
Rob Fitzpatrick, who wrote The Mom Test, boils the method down to three rules, summarised on his Indie Hackers podcast episode: talk about their life instead of your idea, ask for specifics from the past instead of opinions about the future, and talk less, listen more. On the same episode he describes two full-time years of customer conversations before his startup went under anyway, because he was asking the wrong way. Volume does not rescue bad questions.
The reason past behaviour matters so much: intentions are a weak stand-in for action. Paschal Sheeran’s review of intention–behaviour studies (2002) pooled 422 studies with 82,107 participants and found intentions explained an average of 28% of the variance in behaviour. In health studies (exercise, screening), a median 47% of people who intended to act did not. That research is not about software, but the gap is the same one you hit when a friend says “I’d totally use that.”
Who should you talk to when validating a side project?
Ideal: people already paying for an ugly alternative, such as spreadsheets, agencies, bloated SaaS, manual ops, or a virtual assistant. They have budget language. They have scars. They will not pretend a problem is interesting if it is not expensive.
Good proxies when you cannot reach the exact buyer yet:
Operators one step away: freelancers, agency PMs, community mods who serve your target customer daily
Recent switchers: people who just left Tool A for Tool B; they remember the decision
Cold-but-relevant: someone who posted about the pain in a Slack, Reddit, or niche forum in the last 90 days
Skip: your spouse (unless they are the buyer), your engineer friends who “would build that,” and anyone who only knows you as “the founder with the side project.” Nice people optimise for your feelings. Buyers optimise for their Tuesday.
How do you get five people to agree to a call this week?
List ten to fifteen people from communities you already belong to, plus anyone who posted about the problem recently. Send a short, specific ask that is obviously not a sales pitch:
“I’m researching how [role] handles [job], not selling anything. I saw your post about [specific thing]. Could I ask you a few questions for 20 minutes this week?”
What makes it work: you name their situation, you name the time cost, and you promise no pitch (then keep that promise). Send ten asks before you aim for five calls; some people will ignore you, and that is normal. Book the first three before you overthink the list, and offer two concrete time slots instead of “whenever suits.”
Lunch breaks and early mornings work for most people with jobs, including you. A 20-minute call fits where a one-hour “coffee chat” does not.
What should you ask in a 20-minute validation conversation?
Open with context, then get out of the way. Adapt the words; keep the order.
0:00–0:02 — Frame
“Thanks for the time. I’m trying to understand how people like you handle [job] today. I’m not pitching a product. Mind if I take notes?”
0:02–0:07 — Problem in their words
“Walk me through the last time [job] went wrong or took too long.” Follow with: “How often does that happen?” and “What does it cost you when it does?” Cost can be hours, missed revenue, stress, or actual dollars; capture whatever they name.
0:07–0:12 — Current workaround
“What do you use today?” Spreadsheet, tool, person, ignoring it. “What do you hate about that?” “What have you already tried that failed?” Listen for switching costs and “good enough” inertia.
0:12–0:17 — Willingness to pay or switch
Do not ask “Would you pay $29/mo for my idea?” Ask: “If something fixed [specific pain] without [annoying part of current workaround], what would you need to see before you’d try it?” Then: “Have you paid for anything in this area in the last year? Roughly what?” Past payment beats hypothetical enthusiasm.
0:17–0:20 — Closing signal
“Who else should I talk to who feels this weekly?” Referrals from people in pain are gold. If they offer an intro, write the name down before you hang up.
Optional last question if the chat is going well: “If I built a thin version that only did [one job], would you try it for two weeks and tell me what’s broken?” A yes with a calendar hold is stronger than a compliment.
Most bad interviews fail on question wording. Swap these:
Instead of asking | Ask | Why |
|---|---|---|
“Would you use an app that…?” | “When did this last happen? What did you do?” | Future hypotheticals invite polite yeses |
“Is this a big problem for you?” | “What did it cost you last month, in hours or money?” | Forces a number instead of a feeling |
“How much would you pay?” | “What do you pay for this today, if anything?” | Past spend is behaviour; a price guess is not |
“Do you like this idea?” | “What have you already tried to fix it?” | Real pain usually has a failed fix attached |
“Would you recommend it?” | “Who else has this problem? Could you introduce us?” | An intro costs them something; a promise does not |
How do you log answers so you can compare them?
Open a spreadsheet. One row per conversation. Columns that matter:
Who: role, company size if relevant, how you found them
Job / pain (their words): quote fragments, not your summary
Frequency + cost: weekly? monthly? hours or money
Current workaround: tool + what they hate
Past spend: yes/no + rough amount
Switch trigger: what they’d need to see
Try thin version?: yes / soft / no
Referral offered?: yes/no
Your one-line takeaway: written within 10 minutes of hanging up
Do not wait until Sunday to “process” notes. Memory edits toward the story you wanted. Ten minutes after each call, fill the row while their phrasing is still sharp. Add one more column after call three: “new pain not heard before?” If that column is still filling up at call five, you have not hit a pattern yet.
How do you score five conversations: go, pivot, or stop?
Five conversations will not prove product-market fit. They will tell you whether to spend the next month of evenings building. First, rank what each person gave you by what it cost them:
Signal | What it cost them | How to count it |
|---|---|---|
“Cool idea” / “let me know when it’s live” | Nothing | Ignore |
Detailed story of the last time it went wrong | A few minutes of memory | Evidence the pain exists |
Named workaround they hate, or past spend | Money or hours already sunk | Evidence the pain is expensive |
Introduction to a peer with the same problem | Their reputation | Strong |
Calendar hold to test a thin version | Their time | Strong |
Pre-order, deposit, or paid pilot | Their money | Strongest |
Then apply blunt rules:
Go (build a thin slice): At least 3/5 describe the same job in similar words, name a real workaround, and show past spend or clear willingness to try a thin version. At least 2 offer a referral or agree to test. Pain sounds frequent, not theoretical.
Pivot (change the job or customer, not the colour palette): People care, but about a different job than you assumed. Or the pain is real for a narrower group. Rewrite the one-job sentence and run five more with the new target; do not “add features” to paper over a fuzzy job.
Stop (park the idea): Compliments without workarounds. “Interesting” with no past spend and no try-commitment. Five different pains. Or everyone says the spreadsheet is annoying but “fine.” Annoying-but-fine does not fund nights and weekends.
Guardrails: if all five were friends-of-friends in your industry bubble, treat “go” as soft and get two more from colder channels. If someone says they’d pay but refuses a follow-up, count that as soft, not yes. Never let one enthusiastic call outweigh four shrugs. If you land on pivot and are unsure which kind, this guide on deciding whether to pivot and what kind of pivot to make breaks down the options.
When you later need honest product reactions (not idea validation), use the same bluntness you’d bring to brutal feedback from makers before a public launch. Praise is cheap; specifics are not.
What does a five-conversation validation look like in practice?
Illustrative example (made up to show the method; not a real product or real interviews). Priya is a backend developer with a day job. Her idea, “Chasewren,” sends polite automatic reminders to freelancers’ clients when an invoice is overdue. Her one-job sentence: “Freelancers waste hours chasing late invoices.” She books five calls in nine days:
# | Who | Pain in their words | Workaround / past spend | Costly signal |
|---|---|---|---|---|
1 | Freelance designer (found in a Slack) | “Two or three late invoices a month, I hate the awkward email” | Calendar reminders; invoicing app already sends nudges | None |
2 | Freelance copywriter (posted on Reddit) | “I rewrite the same chase email every time” | Saved email template; no spend | Soft yes to try |
3 | Agency ops manager (proxy) | “Invoices are fine. Getting receipts out of staff and clients every month is the nightmare” | Bookkeeper spends hours chasing; agency pays for it | Intro to their bookkeeper |
4 | Freelance developer (friend of a friend) | “Annoying but fine” | Built-in reminders in invoicing tool | None |
5 | Bookkeeper with 14 small-business clients (recent switcher) | “Month-end is me chasing clients for missing receipts” | Pays an assistant for part of the chasing; tried two apps and dropped both | Calendar hold to test + two referrals |
Scoring: only calls 1 and 2 describe invoice chasing, and neither shows spend; call 4 is annoying-but-fine. That fails “go.” But calls 3 and 5 describe a different job, chasing clients for receipts, with money already being spent and the two strongest signals in the whole sheet. That is a textbook pivot: new one-job sentence (“Bookkeepers lose month-end days chasing clients for receipts”), new target group, five more calls starting with the two referrals. Priya writes zero code in those 14 days and saves herself an invoice-reminder app that her best interviewees already get free inside their invoicing tools.
What is the 14-day nights-and-weekends validation sprint?
Goal: five conversations logged, a decision written down, and, if go, one thin experiment designed. Not a production app.
Day 1–2 (one evening): Write one target-customer sentence + one job sentence. List 15 outreach targets. Send 10 asks.
Day 3–4: Book the first three calls. Build the empty log sheet. Practise the script once out loud (yes, really).
Day 5–10: Run conversations (lunch breaks, early mornings, one weekend block). Log each row the same day. Ask for referrals at the end of every call.
Day 11: Hit five completed rows (or six if one was a misfit). Do not wait for the perfect fifth.
Day 12: Score go / pivot / stop with the rules above. Write three sentences: decision, evidence, next thin step.
Day 13–14: If go, define the thinnest test (landing page + waitlist, concierge, or a manual “done-for-you” week), not your dream architecture. If pivot, rewrite the customer and job sentences and schedule the next five. If stop, archive the sheet and pick a different job. Do not keep building in secret.
If your thin test is a page, a fake door test with a pass/fail threshold set in advance keeps you honest about what counts as interest. Tag the link you send to each interviewee and each community with the free UTM link builder (for example one source for interviewees and another for each community), so your analytics show whether the people who said yes on a call actually clicked and signed up, or whether strangers did.
Protect two evenings for talking, not coding. The whole point of this sprint is to earn the right to build later.
What are the most common validation traps?
Friends who are nice: They want you to feel supported. Buyers want their Tuesday fixed. Weight stranger and proxy calls higher.
Building while “researching”: Opening the repo mid-sprint is how you invent confirmation bias. Talk first; scaffold after the decision.
Treating likes as validation: Applause is not a workaround, a budget, or a try-commitment.
Pitching instead of listening: If you spent more than three minutes describing your idea, you ran a pitch, not a conversation.
n=1 hero story: One excited person is a case-study candidate, not a market.
Survey theatre: Fifty anonymous form responses with no follow-up path usually teach less than five live chats.
Too wide a target: Five calls across five different kinds of customer give you five anecdotes, not a pattern. Narrow the group, then talk.
What should you do after a go decision?
A green light from five conversations means “build something thin and stay in contact with those people,” not “disappear for eight weekends.” Keep the same sheet. Add a column for “showed thin version / reaction.” Cut the build to what fits your real calendar with a side project MVP scoped to weekend-sized blocks, and show each version to the people who gave you a calendar hold first.
When you are ready to find people who will actually pay while you keep the day job, use a concrete outreach loop like finding paying customers for a side project without quitting your job.
And when a tiny version works for a handful of people, resist the Product Hunt countdown clock. A quiet soft launch with real users beats a loud day with strangers, the same idea as soft-launching quietly before Product Hunt day.
Side projects die from silence more often than from bad code. Write the job. Book the chats. Log the answers. Decide go, pivot, or stop, then act like you meant it. When you are ready to put a thin version in front of other builders, browse what’s shipping on SideHunt, and show up with notes from real conversations, not just a polished landing page.
Frequently asked questions
How many customer interviews do you need to validate an idea?
Start with five to six from one narrow group and analyse after each call. Research on interview saturation found most major themes appear within the first six interviews of a similar group and nearly all within twelve, while finding 90 to 95% of all needs took 20 to 30 in one classic study. For a go / pivot / stop decision on a side project, five is a reasonable first batch; run another five if answers are scattered.
Can I validate a side project idea without talking to anyone?
You can collect weaker signals (search demand, forum complaints, a landing page with a waitlist), and they are useful alongside conversations. But they tell you that people click, not why or whether they already pay to solve it. If you truly cannot reach anyone with the problem, that is itself a warning about how you will sell the product later.
Should I show my idea or a prototype during validation calls?
Not until the last few minutes, if at all. Once you pitch, people get polite and the conversation turns to your solution instead of their problem. Spend the call on their past behaviour, then ask at the end whether they would test a thin version for two weeks.
What if everyone says they love the idea?
Treat it as no data. Check the sheet for workarounds, past spend, referrals, and calendar holds. If none of those appear, the praise is politeness, and the intention research is clear that saying you will do something is a poor predictor of doing it.
Is a waitlist or landing page signup enough validation?
It is a weak-to-medium signal: an email address costs very little to give. Use it after conversations to test whether your message lands with strangers, and treat paid pilots, deposits, or repeated use of a thin version as the stronger proof.