Design a customer-interview study and turn transcripts into messaging.
Who to talk to, a non-leading interview guide, and how to turn transcripts into positioning and messaging inputs.
Inside: The interview slate, the non-leading guide, and transcripts-to-positioning.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it helps you pick a representative slate by segment, stage, and outcome instead of just the friendly accounts.
paste interview transcripts and the skill pulls themes, quotes, and language patterns back out.
pairs the qualitative interviews with quantitative validation of what you heard.
This was built for a B2B team running win, loss, and positioning interviews with their own customers. Set these to your stack:
The point of the study is your customers' words. The skill will never invent a quote or attribute a finding to someone who did not say it.
| Set this | What it is | Default / Example |
|---|---|---|
| GOAL | what the study must answer | why they buywhy they churnhow they describe us |
| SEGMENTS | who you sample across | by sizeindustryuse caseoutcome |
| SAMPLE_SIZE | how many interviews | 8 to 15 for qualitative saturation |
| RECRUIT_SOURCE | where the slate comes from | CRMcustomer listwarm intros |
| GUIDE_LENGTH | interview length | 30 to 45 minutes |
| TRANSCRIPT_SOURCE | where recordings or notes live | your notes tool or call recorder |
| VALIDATION | how you confirm the themes | a follow-up surveyoptional |
Everything the skill does, in full.
Takes a research goal and builds the whole study: who to interview and why they are the right people, a non-leading interview guide, the questions that get past the polite answer to the real one, and a method for turning the transcripts into positioning and messaging you can use. It designs and structures the research. It does not sit in the interviews for you.
- 1Who to talk to (representative, not convenient)
Pick a slate that can actually answer the GOAL, sampled across the SEGMENTS that matter. If you only interview happy, engaged customers, you learn why happy people are happy. Include the ones who churned, the ones who almost did not buy, the quiet ones. Name why each type is in the sample.
- 2The interview guide (do not lead the witness)
Write open questions that let the customer tell their story before you steer it. Start broad ("walk me through how you ended up looking for something like this"), then follow their thread. The rule of the guide is that it collects their language, not confirmation of yours.
- 3Questions that avoid leading
The craft is in the wording. "What did you love about the product?" plants the answer. "What happened right before you decided to buy?" lets them tell you. The skill flags leading questions, double-barreled questions, and yes-or-no traps, and rewrites them to open the story. Ask about behavior and specific moments, not opinions and hypotheticals.
- 4Run and capture
Keep the interviewer quiet and curious: ask, then let silence do the work. Capture verbatim language, the exact words for the problem, the alternatives, the moment of decision. Record or take clean notes, because the quotes are the deliverable, not your paraphrase.
- 5Transcripts into positioning and messaging
Turn the raw transcripts into inputs: recurring problems in the customer's words, the language they use (which becomes your copy), the alternatives they weighed (which becomes your competitive frame), and the moment and trigger that made them buy (which becomes your positioning). Every theme is backed by real quotes, counted across interviews, never a single loud voice generalized into a finding.
- The sample includes more than the happy, convenient accounts. Churned and near-miss voices are in it.
- Every question in the guide is open and non-leading. The skill flags and rewrites any that plant an answer.
- Every theme is backed by verbatim quotes and a count of how many interviews support it.
- No invented quotes, no findings attributed to people who did not say them.
CUSTOMER RESEARCH DESIGN · positioning study (illustrative) Goal: how do buyers describe the problem in their own words, and why us over the rest. Slate (12 interviews): 4 recent buyers · 3 long-time customers · 3 churned · 2 near-misses (chose a competitor) Guide (35 min), opening questions: 1. Walk me through what was going on right before you started looking. 2. What had you tried before this? (not: "why didn't other tools work?") 3. Tell me about the day you decided. What tipped it? Flagged + rewritten: "What do you love about us?" -> "When has it clearly paid off?" Analysis output (from transcripts): Theme Support Verbatim "manual + slow" 9/12 "I was doing it by hand every Friday" Trigger = new hire 5/12 "we grew and it just broke" Chose us for X 7/12 their words, pulled straight from the call Positioning inputs: lead with the Friday-by-hand pain, in their language, not ours. Next move: connect the CRM to build the churned + near-miss slate you cannot get from memory.
Where an operator takes this next.
The read is step one. Here's where an operator takes it once the manual version proves out.
You built the read once; now it runs itself.
Connect Salesforce so every future study auto-generates a representative sample across segment and outcome, not just whoever's easiest to reach.
Point a scheduled Claude task at your notes tool monthly and refresh the theme list as new interviews land, so messaging tracks live language instead of a study that ages out.
Push the top qualitative themes into a quick survey tool to confirm the pattern holds beyond 6 interviews before it becomes the homepage headline.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.