The coffee-stained beginning
Picture this: it’s late, there’s a chipped mug by your elbow, and you’ve got an idea that won’t let you sleep. You’re tempted to polish a pitch deck, but something nudges you to do the unglamorous thing—talk to ten people first. Not to convince them. To hear them. The kitchen-table version of you nods, opens a blank page, and makes a list of names.
By the third conversation, you notice a pattern: people keep describing the same awkward workaround. By the sixth, the problem has edges. By the tenth, you can repeat their words by heart. You didn’t sell a thing. Somehow, you now know what to build—or what to gracefully abandon.
The plan in one glance
- Goal: gather stories, not opinions; evidence, not applause.
- Ratio: aim to listen 90% and speak 10%.
- Rule: no pitching, no demos, no “would you buy this?”
- Focus: recent behaviors, costs, and workarounds.
- Ending: ask for two intros, not a sale.
The 10-person loop
- Write 15–20 names who live with the problem or sit next to it.
- Send a short, specific outreach message (no links or decks).
- Book 20 minutes; record only with permission.
- Run the script below; take timestamped notes.
- Ask for two introductions.
- Summarize what you heard and share it back in one paragraph.
- Repeat until you’ve spoken with 10 people.
The message that gets replies
Keep it human and precise. You’re not selling; you’re learning.
Hi [Name]—I’m exploring how [people like you] handle [specific job/problem]. You came to mind because [true, specific reason]. Could I borrow 20 minutes for a few questions about your recent experience? No pitch—just learning. If helpful, I’ll share a short summary of what I hear across folks.
The call flow, minute by minute
- 0:00–0:01 Thanks and consent. “Okay to take notes? If you’d rather not, I won’t record.”
- 0:01–0:03 Context. “I’m exploring how people handle [job]. No sales—just trying to understand what’s hard and what already works.”
- 0:03–0:05 Who are you? “What does a typical week look like when [job] shows up?”
- 0:05–0:12 One recent story. “Can you walk me through the last time you did this, step by step?”
- 0:12–0:16 Alternatives and costs. “What did you try? What did it cost in time, money, or stress?”
- 0:16–0:18 Impact and stakes. “What happens if this keeps being annoying for six months?”
- 0:18–0:20 Wrap and intros. “Who else should I talk to who’s wrestled with this recently?”
Questions you’ll actually ask
Warm-up
- “When does this problem tap you on the shoulder?”
- “Who else gets pulled in when it appears?”
Recent story prompts
- “Tell me about the last time—where were you, what kicked it off?”
- “What did you do first? Then what?”
- “Where did it slow down or go sideways?”
Workflow and workarounds
- “What tool or doc did you open first?”
- “What’s the hack you’re not proud of but still use?”
- “When do you give up and do it manually?”
Costs and thresholds
- “How do you notice it’s become expensive—time, money, reputation?”
- “What’s the ‘enough is enough’ moment?”
Alternatives and decision dynamics
- “What have you tried, and why did you stop?”
- “Who has veto power on changing how you do this?”
- “What would have to be true for you to switch?”
Value without selling
- “If a solution removed the top two headaches you mentioned, how would you know it worked?”
- “What budget or category would that live under, if any?”
- “What’s a small, safe first step you’d be comfortable with, in theory?”
What to say when they ask about your idea
People get curious. Keep it short and bounce the ball back.
I’m exploring whether there’s a clearer way to handle [job] for folks like you. I don’t have anything to sell today—your recent experience is the most helpful thing. Given what you just said, where does this bite the hardest?
What you’re listening for
- Repeated phrases across calls (“I always end up exporting to CSV”).
- Concrete triggers (“end of month,” “client handoff,” “audit week”).
- Hidden costs (overtime, churn, errors, lost momentum).
- Existing spend and substitutes (consultants, manual time, clunky tools).
- Switching constraints (compliance, approvals, migration fear).
- Language you can quote verbatim later.
A tiny notes template
- Person and role: [ ]
- Recent story date/time: [ ]
- Steps they took: [ ]
- Workarounds and tools: [ ]
- Costs (time/money/stress): [ ]
- Trigger and “enough is enough” moment: [ ]
- Decision helpers/haters: [ ]
- Two referrals they suggested: [ ]
- Exact quotes to keep: [ ]
Follow-up in three lines
Thanks again for the time today. Here’s what I heard in one paragraph: [summary]. If anyone else comes to mind who’s wrestled with this recently, an intro to two people would help a lot. I’ll circle back with a short rollup of patterns I’m hearing.
Run the loop this week
- Today: list 15–20 names and send outreach to the first 10.
- Tomorrow: run 4 calls; update your notes template after each one.
- Next day: run 6 calls; share a one-paragraph rollup with everyone who helped.
A quick story from the other side of the table
Imagine your future customer, late at night, wishing the spreadsheet would just behave. They try three tabs, a copy-paste, and a silent prayer. They’re not waiting for a pitch; they’re waiting to not feel silly or behind. When you show up as a listener, you’re already useful. That’s how trust starts—and trust is how truth shows up.
How you’ll know you’re ready to build
- You can describe the problem in their words without peeking at notes.
- At least 7 of 10 told the same core story with the same trigger.
- You’ve mapped the switching constraints and who needs to say yes.
- You can point to an existing spend or measurable cost you’d reduce.
- You have five intros that keep the learning going.
Wrap it up your way
When you finish your tenth chat, pause. Jot what surprised you, the line you can’t stop hearing, and what you’ll try next. If it helps, capture it on your own blog or in your notes—start for free with the Jaopaya Framework and keep the momentum while the stories are fresh. The mug will still be chipped, but your next step will feel a lot less wobbly.
