Customer discovery doesn’t need to be complicated
Let’s be real: most founders aren’t scheduling 30 perfect interviews with a research plan and a spreadsheet taxonomy.
You’re going to events. You’re doing coffee chats. You’re talking to 10–15 people fast. That’s not wrong—that’s how momentum happens.
The problem is what comes next:
- the conversations blur together
- the last conversation “wins”
- you don’t know who you heard things from (buyer vs user, small team vs bigger team, etc.)
- discovery doesn’t roll forward into GTM—it resets
This post is not about over-optimizing your process. It’s about doing discovery the founder way without losing signal.
The minimum viable system (3 minutes, works anywhere)
Before you start talking to people, set yourself up with the smallest possible structure:
1) One learning goal
Pick a single thing you’re trying to learn right now.
Example: “What do founders struggle with in early validation, and what actually worked?”
2) Two attributes (one Person, one Company)
Just enough to filter later:
- Person: Role (user / manager / buyer / influencer)
- Company: Stage or size (pick one and stick with it)
3) One sentence after each convo
Right after the chat, write:
“Biggest pain was ___ because ___.”
That’s it. No heavy process. Just enough to prevent learning from evaporating.
A simple 10-minute discovery conversation (works at events or on calls)
Now you need a format that’s fast, non-awkward, and consistent—whether you’re standing at a meetup or on Zoom.
You don’t need to announce “I’m doing a customer discovery interview.”
You can just say:
“I’m exploring a problem space—mind if I ask a couple quick questions?”
Then run this:
A) Context (1 minute)
- “What do you do?”
- “What kind of team/company are you in?”
(This maps to your two tags: Role + Context.)
B) Last time (4 minutes)
- “When was the last time you dealt with [problem]?”
- “What triggered it?”
- “What did you do next?”
C) Current solution (4 minutes)
- “How do you handle it today?”
- “What’s annoying about that?”
- “What have you tried and abandoned?”
D) Close (1 minute)
- “If this got solved, what would change?”
- “Is there anyone else you think I should talk to?”
You’re not pitching. You’re collecting reality.
The 10-minute debrief (use Takeaways + Opportunities + Themes)
You don’t need a “research day.” You just need a quick debrief that turns fast conversations into something you can reuse.
Right after the event (or the next morning), do this:
1) Capture 2-3 Takeaways (2 minutes)
Skim your notes and add short, concrete bullets—one per signal you’d be comfortable repeating.
- Keep them specific (not “they liked it”)
- Write them in “what happened / what they do / what they struggle with” language
Good takeaway examples
- “Still narrowing ICP from general ecommerce → wants a sharper niche.”
- “Found first customers by targeting the smallest revenue accounts first.”
- “Bought leads cheaply at scale; used it to test outreach fast.”
2) Add 2–3 Opportunities (3 minutes)
Now translate what you heard into possible actions—not a roadmap, just “what this suggests we could build/test.”
For each opportunity:
- write it as a simple “tool / workflow / experiment” idea
- optionally mark priority (Low/Medium/High) if that helps you move
Good opportunity examples
- “Tool to help users identify ICP based on market signals.”
- “Upload a lead list and filter companies closest to prior wins.”
- “Event-mode capture: add quick insights without full notes.”
3) Tag each item to a Theme (3–4 minutes)
This is the part that prevents “the last convo wins.”
Create or reuse a few themes (2–6 is plenty) and assign each takeaway/opportunity to one theme:
- “ICP narrowing”
- “Customer acquisition tactics”
- “Validation workflow”
- “Tools + process gaps”
- “Pricing / willingness to pay”
If you don’t want to think about themes yet, let AI propose them:
- click AI Insights / AI Grouping Proposal
- review the suggested groupings
- rename any theme labels that feel off
- confirm and you’ve got a clean themes board
4) Quick scan (1 minute)
Look at your themes board and ask:
- Which theme has the most items?
- Which theme showed up across different people/contexts?
- Which theme is most relevant to who you’re building for?
That’s it. You’ve turned event chaos into a structured snapshot you can build on.
Why this works (without overcomplicating it)
- Takeaways keep it fast and factual
- Opportunities turn learning into action
- Themes make patterns visible and reduce recency bias
- Optional AI grouping gives you structure without a heavy manual affinity mapping session
Where Intervool fits
You can do all of this using Intervool.
Intervool is for the moment when you don’t want your learning to evaporate:
- capture fast conversations without ceremony
- tag who you talked to (role + context)
- group what you heard into themes
- see patterns by attribute (what’s true for who)
- turn themes into a prioritized ideas list you can defend
- keep the thread as discovery becomes GTM
Quick checklist
Before the event
- one learning goal
- general questions
During the event
- 10–15 fast conversations
- 60-second notes after each
After
- 10-minute debrief: repeated pains, 1 surprise, 2–3 themes, “for who”
