# The Customer Interview Playbook Turn conversations into positioning, roadmap, and revenue 13 min read Customer Discovery For Founders & Operators Most founders know they should talk to customers. The hard part is not scheduling the call. It is asking questions that do not lead the witness, hearing the painful truth, and converting messy notes into a sharper product bet. This playbook gives you the question set, recruiting scripts, synthesis method, and worked example for running interviews that change what you build. 5 Core questions 12 Interviews per round 3 Signal categories 1 Next product bet ## In this playbook ## Why most customer interviews fail Customer interviews fail when founders treat them like permission slips. They describe the product, wait for the prospect to say “interesting,” then write “validated” in a Notion doc. Nothing useful happened. The founder collected encouragement, not evidence. Good interviews are not about asking whether someone wants your idea. They are about reconstructing the last time the person felt the pain, what they tried, what it cost them, and why existing alternatives were not good enough. ### The rule that saves the call Ask about yesterday, not the future. “Would you use this?” creates polite fiction. “Walk me through the last time this happened” creates observable evidence. ## The five-question spine You can run a useful customer interview with five questions. The discipline is asking follow-ups instead of pitching. 1. When did this last happen? Forces the conversation into a real event instead of a generic opinion. 2. What triggered it? Reveals the moment when pain becomes urgent enough to act. 3. What did you do next? Shows the current workaround, budget, owner, and switching cost. 4. What was annoying, expensive, or risky? Separates mild inconvenience from pain that can support a product. 5. What would have made it easier? Opens the door to desired outcomes without handing them your solution. ## How to recruit the right people A weak interview with the right person beats a polished interview with someone outside the buying path. Before you recruit, define the behavior that qualifies someone for the call. ### Recent pain They dealt with the problem in the last 30 days. ### Real workaround They currently spend time, money, reputation, or focus to manage it. ### Decision proximity They can buy, influence, or block the solution. ### Recruiting message ``` Hey {{name}} - saw you mention {{specific trigger}}. I am researching how {{specific people}} handle {{painful workflow}}. Not pitching anything. Could I ask you 5 questions about the last time this happened? 20 minutes, happy to send back the patterns I find. ``` Keep the promise honest. If you say you are not pitching, do not pitch. The goal is to earn a candid story, not force a demo. ## The 30-minute interview flow 1. **Set the frame** 2 min “I am trying to understand the workflow, not sell you anything. I may interrupt to get specific because details matter more than opinions.” 2. **Reconstruct the last instance** 8 min Ask when it happened, who was involved, what triggered it, and what they did first. Push for sequence: then what, then what, then what. 3. **Quantify the cost** 7 min Ask what it cost in time, money, delay, risk, or embarrassment. If they cannot quantify it, ask what else did not happen because of it. 4. **Map alternatives** 7 min Ask what they tried, what they rejected, what they still tolerate, and who else gets pulled into the workaround. 5. **Test language, not the product** 4 min Repeat their pain back in your words. If they correct your wording, write down the correction. That is landing page copy. 6. **Ask for the next door** 2 min “Who else deals with this more often than you do?” Warm intros compound faster than cold lists. ## How to separate signal from politeness Do not score interviews by enthusiasm. Score them by evidence of past behavior. ### Strong signal They recently experienced the pain, tried a workaround, can name a concrete cost, and ask how to stay involved. ### Medium signal They recognize the problem but describe it as periodic, delegated, or annoying rather than urgent. ### Polite noise They say the idea sounds useful but cannot remember the last time it happened or what they did about it. ## Turn notes into decisions Notes are not the artifact. Decisions are. After each batch of 8 to 12 interviews, sort observations into three columns. ### Repeated pain Same trigger, same emotional language, same workaround. ### Buying path Who owns the pain, who pays, and who blocks adoption. ### Product bet The smallest change that would remove the highest-cost step. ### Synthesis prompt ``` After this interview batch, we believe: 1. The sharpest ICP is {{specific segment}}. 2. Their urgent trigger is {{specific event}}. 3. Their current workaround is {{tool/process/person}}. 4. The cost is {{time/money/risk}}. 5. The next product or positioning bet is {{decision}}. 6. We will know we are wrong if {{tripwire}}. ``` ## Worked example: narrowing an ICP ### The setup A solo founder is building a lightweight reporting tool for agencies. The first positioning is broad: “client reporting without spreadsheet chaos.” Twelve interviews produce three different stories. 1. **Generalist agencies** 4 calls They like the idea but already tolerate messy reporting with account managers and templates. Pain is real, urgency is low. 2. **Paid ads agencies** 5 calls Pain spikes every Monday when clients ask why spend changed. Current workaround: screenshots, CSV exports, and two hours of manual commentary per account. 3. **SEO agencies** 3 calls Reporting is slower but less urgent. Clients expect monthly cadence, and the workaround is already baked into retainers. ### Decision The founder narrows the ICP from agencies to paid ads agencies managing 10+ client accounts. The landing page lead changes from “clean client reports” to “answer Monday spend questions before your clients ask them.” The product bet becomes weekly anomaly notes, not prettier dashboards. ## Copy/paste scripts and templates ### Opening script ``` Thanks for making time. Quick frame: I am not here to pitch. I am trying to understand how this actually works today. I will ask mostly about the last time it happened. If I ask for specifics, it is because details are more useful than opinions. ``` ### Follow-up after a strong interview ``` This was incredibly useful - especially the part about {{specific quote}}. I am going to synthesize this with a few other conversations. If I build a rough version focused on {{specific pain}}, would you be open to reacting to it for 15 minutes? ``` ### Interview note format ``` Person / segment: Trigger: Last occurrence: Current workaround: Cost: Exact phrases: Alternatives mentioned: Buying path: Strength of signal: strong / medium / weak Decision this should influence: ``` The output of a good interview cycle is not a giant research deck. It is a clearer ICP, sharper copy, a smaller product bet, and one measurable tripwire for whether the bet worked.