customer-interview-guide
/customer-interview-guide
Use this skill when you want to learn from customers or prospects in a structured interview: \"write customer interview questions\", \"voice of customer research\", \"why did customers buy\", \"jobs to be done interviews\". Plans who to interview, writes a guide that uncovers the buying story (the trigger, the alternatives, the decision, the outcome) without leading questions, and turns the transcripts into themes, buyer language and changes for messaging, ICP and product. Produces an interview guide, a recruit message and a synthesis template.
- Author
- prosyo-ai ↗
- Repository
- gtm-skill ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when you want to learn from customers or prospects in a structured interview: \"write customer interview questions\", \"voice of customer research\", \"why did customers buy\", \"jobs to be done interviews\". Plans who to interview, writes a guide that uncovers the buying story (the trigger, the alternatives, the decision, the outcome) without leading questions, and turns the transcripts into themes, buyer language and changes for messaging, ICP and product. Produces an interview guide, a recruit message and a synthesis template.
Triggers from the description
Original author description
Use this skill when you want to learn from customers or prospects in a structured interview: \"write customer interview questions\", \"voice of customer research\", \"why did customers buy\", \"jobs to be done interviews\". Plans who to interview, writes a guide that uncovers the buying story (the trigger, the alternatives, the decision, the outcome) without leading questions, and turns the transcripts into themes, buyer language and changes for messaging, ICP and product. Produces an interview guide, a recruit message and a synthesis template.
How it works
- Inputs
- The play
- What good looks like
- Rules
- Example prompts
SKILL.md preview
--- name: customer-interview-guide description: "Use this skill when you want to learn from customers or prospects in a structured interview: \"write customer interview questions\", \"voice of customer research\", \"why did customers buy\", \"jobs to be done interviews\". Plans who to interview, writes a guide that uncovers the buying story (the trigger, the alternatives, the decision, the outcome) without leading questions, and turns the transcripts into themes, buyer language and changes for messaging, ICP and product. Produces an interview guide, a recruit message and a synthesis template." license: MIT metadata: title: Customer interview guide category: research tags: "Founders, Marketing, Sales Leaders, Customer Success" author: prosyo version: "1.0.0" keywords: "customer interview questions b2b, voice of customer research, jobs to be done interview guide, claude customer research skill, buyer interviews" inputs: "What you want to learn, Customers or prospects to interview, Product and ICP" outputs: "Interview guide, Recruit message, Synthesis of themes and buyer language" --- Use this when messaging, ICP or roadmap decisions rest on guesses. Ten good interviews with recent buyers usually reveal more than a hundred survey responses. ## Inputs - The decision the research should inform (positioning, ICP, pricing, a feature). - Who to talk to: recent buyers (last 90 days) are best; also recent churns and lost deals. - What you already believe, written down, so you can test it. ## The play ### 1. Recruit the right people Recent buyers remember the story. Aim for 8 to 12 interviews across segments. Recruit with a short, honest ask: > Hi Maya, you started with us last month. Could I ask you 20 minutes of questions about how you decided? No sales pitch, just learning. As thanks, <a small, appropriate gesture>. ### 2. Ask about the story, not opinions Follow the timeline of the purchase: 1. **Before**: "What were you doing before? What was annoying about it?" 2. **Trigger**: "What happened that made you start looking then?" 3. **Search**: "What else did you look at? What did you almost choose?" 4. **Decision**: "What made you pick this? Who else had a say? What almost stopped it?" 5. **After**: "What's different now? What would you miss if it disappeared?" Read [references/interview-guide.md](references/interview-guide.md) for the full guide with follow-ups and the synthesis template. ### 3. Avoid leading questions Not "Would you say our reporting saved you time?" but "What happened the last time you needed a report?" Ask for specific past events, not hypothetical future behaviour. ### 4. Capture the exact words Record (with permission) and pull verbatim quotes. The buyer's phrases are the raw material for headlines, emails and battlecards. ### 5. Synthesise into decisions Group findings into triggers, alternatives, decision criteria, objections and outcomes. A theme needs 3+ interviews. Each theme ends with a recommended change. ## What good looks like - Interviewees do most of the talking and tell stories with specific moments. - The synthesis includes surprises, not just confirmation. - Buyer phrases end up in the next round of copy. - The common mistake is turning the interview into a demo or a satisfaction survey, which produces polite praise and no insight. ## Rules - MUST get permission before recording and anonymise quotes unless the person agrees otherwise. - MUST ask about past events, not hypothetical opinions. - NEVER sell during a research interview. - NEVER present a single interview as a pattern. ## Example prompts - "Write a customer interview guide to find out why our last 20 customers bought." - "Here are 9 interview transcripts. Synthesise themes and buyer language for our homepage." - "Write a recruit email for interviews with customers who churned last quarter."
Files in this package (2)
- SKILL.md 4 KB
- references/interview-guide.md 2 KB
Versions
The database has no other skills named customer-interview-guide.
Database snapshot: 13.11.2026 · package version 013afe309cf5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90customer-research
Run evidence-led B2B customer and buyer research that produces a recruiting plan, interview guide, buying timeline, Jobs-to-be-Done forces map, quote repository, and decision-ready insight brief. Use when a team is guessing about buyer triggers, ICP, positioning, messaging,… - 100customer-interviews
Designs customer interviews and turns the transcripts into decisions. Produces an interview guide plus a synthesis (forces of progress, jobs, pathways, opportunities) you can paste into a doc. Use for 'customer interviews', 'discovery calls', 'JTBD', 'switch interview', 'who… - 100customer-discovery
Plan customer discovery interviews, write non-leading questions, and analyze notes into evidence. Use when a founder needs to talk to customers, is preparing an interview script, has notes to synthesize, or needs discovery evidence for an application or grant. - 100create-interview-guide
Generate a Mom Test interview guide with warm-up, core, and closing questions when the user asks to prepare for customer interviews, user research, or discovery calls - 100customer-interview
Plans and scripts customer discovery interviews using The Mom Test. Use when a user wants to plan a customer interview, write discovery interview questions, build an interview script, generate Mom Test questions, or talk to users about a problem. Produces a non-leading question… - 100customer-interview-synthesis
Use when the user has done, or is doing, customer or buyer interviews and wants to turn the notes into something a persona, a positioning statement or a roadmap can rest on - or wants to know whether they have done enough interviews. Also use when the user mentions customer…