skills / research

interview-script

what it does

Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Can you check my interview questions before I start talking to freelancers tomorrow?”

Source material given with the request

We're exploring a tool that chases late invoice payments for freelancers. 1. Don't you find it frustrating to chase clients for late payments? 2. How often do you send invoices? 3. Would you pay $15 a month for an app that chases late payments automatically? 4. Our app sends automatic reminders to clients. What do you think of that? 5. Tell me about the last invoice that was paid late. What happened? 6. On a scale of 1 to 10, how much do you hate doing admin work?
with the skill
# Review of your interview questions Only #5 is a good question as written. #2 is fine with a tweak, and the other four would give you misleading data. | # | Verdict | Problem | Fix | |---|---|---|---| | 1 | Rewrite | Leading and closed. It tells them what to feel, and they'll say "yes, so frustrating" to be agreeable. | "Tell me about the last time a client paid you late. What did you do?" | | 2 | Tweak | Fine, but vague. People estimate badly. | "Walk me through the last few invoices you sent. How many in the past 3 months? How did each get paid?" | | 3 | Cut | Hypothetical future behavior plus a price pitch. People say yes to "would you pay" and then don't. | Ask about current spend: "What do you pay for today to manage invoices or payments? Have you ever paid for something to get paid faster?" | | 4 | Cut | It's a pitch, and it invites compliments ("sounds cool!"), which are noise. | "What have you tried to get paid faster? How did your clients react?" | | 5 | Keep | Specific, past-tense, and story-based. This is your best question. | Add follow-ups (below). | | 6 | Cut | Leading, and a 1-10 "hate" score tells you nothing actionable. | "Which admin tasks do you tend to put off? When did you last put one off, and what happened?" | ## Follow-ups to add to #5 - "What happened next?" - "How late was it, and how much was the invoice?" - "How did you follow up? How long did that take?" - "What did it affect, such as rent, other bills, or your stress level?" - "How did you feel about reminding them?" - "Did it change how you work with that client?"
Show the rest (40 more lines)
## What's missing - **Existing solutions.** FreshBooks, QuickBooks, Wave, and PayPal already send reminders. Ask what they use now and why it does or doesn't work. - **Relationship risk.** Many freelancers avoid chasing because they fear damaging the client relationship. This could decide whether your product works, so explore it without leading: "How do you decide when and how to follow up?" - **Frequency and severity.** How often are payments late, by how much, and what does it cost them? A freelancer with one late invoice a year isn't your customer. - **Workarounds.** Calendar reminders, spreadsheets, and templated emails all show real pain. - **Screening.** Confirm they've had a late payment in the last 6 months, or you'll get opinions instead of experience. ## Suggested flow (about 30 min) 1. **Opening (2-3 min):** "I'm here to learn, not sell. No right or wrong answers. OK to record?" 2. **Context (5 min):** "Tell me about your freelance work. What does a typical week look like?" Then Q2. 3. **Core (15-20 min):** - Q5 with follow-ups - "What tools or methods did you use to follow up?" - "What's the hardest part of getting paid?" - "What have you tried to fix this? What happened?" - "What does a good payment process look like for you?" - "What do you spend on this today, in time or money?" 4. **Wrap-up (3-5 min):** "Anything I didn't ask that matters?" and "Who else should I talk to?" Don't mention your product or its price during the interview. If they ask what you're building, say "I'll tell you at the end." ## Note-taking template ``` Participant: [Name / ID] Date: Key Jobs: [What they're trying to accomplish] Current Solution: [What they use today] Last late payment: [Amount / how late / what they did] Biggest Pain: [Their #1 frustration, in their words] Relationship concerns: [Fear of chasing clients?] Desired Outcome: [What success looks like] Willingness to Pay: [Current spend in time/money, past attempts to solve it] Strong emotions: [Where and about what] Surprise Finding: Follow-up: ``` Listen for specific stories, workarounds, and money or time already spent. Treat compliments and "I'd totally use that" as noise. If you tell me the interview length and who you're recruiting, such as solo designers versus consultants, I can tailor the full script.
without
Your list mixes a few good questions with several that will give you misleading answers. Most of the problems are the ones the book *The Mom Test* warns about: leading questions, hypotheticals, and pitching too early. ## Question by question **1. "Don't you find it frustrating to chase clients for late payments?"** ❌ Rewrite This is leading. It tells people the answer you want, and most will agree to be agreeable. It also assumes the problem exists for them. → *"Walk me through what happens when a client doesn't pay on time."* **2. "How often do you send invoices?"** ✅ Keep It's factual and about past behavior. Use it early as a warm-up. Add "How many are typically paid late?" to size the problem. **3. "Would you pay $15 a month for an app that chases late payments?"** ❌ Cut or replace Hypotheticals about future behavior are unreliable. People say yes to be polite, and saying yes costs them nothing. → *"What do you currently use to manage invoices, and what does it cost?"* → *"Have you ever paid for or tried something to solve this?"* Later in the call, test commitment instead: ask for a follow-up call, an intro to another freelancer, or a spot on a waitlist. **4. "Our app sends automatic reminders. What do you think of that?"** ❌ Cut, or move to the very end This is a pitch, and people will give you polite feedback like "sounds cool!" It also anchors the rest of the conversation. If you do show it, do it last and ask: *"What would stop you from using something like this?"*
Show the rest (30 more lines)
**5. "Tell me about the last invoice that was paid late. What happened?"** ✅ Best question on your list It's specific, about the past, and open-ended. Make it your centerpiece and plan follow-ups: - "What did you do next?" - "How long did it take to get paid?" - "How did you feel about reaching out?" - "What did it cost you, in money, stress, or time?" **6. "On a scale of 1 to 10, how much do you hate doing admin work?"** ❌ Replace It's leading, it's about admin in general rather than your problem, and a number doesn't tell you what they do about it. → *"What parts of running your freelance business do you like least? What do you do about them?"* ## What's missing - **Current workarounds:** QuickBooks, FreshBooks, and Wave already have automatic reminders. Ask *"What have you tried for this? Why did you stop, or why didn't it work?"* If they never tried existing tools, that's a big finding. - **Relationship risk:** Many freelancers don't chase hard because they fear annoying clients. Automated reminders could feel impersonal or risky to them. Ask *"How do you decide how firmly to follow up with a client?"* - **Severity:** How much money is stuck, and how often? If late payments are rare or small, this may be a minor pain. - **Closing questions:** *"Who else should I talk to?"* and *"Is there anything I should have asked but didn't?"* ## Suggested flow 1. Background: what they do, how they invoice, how often (Q2) 2. The last late payment story (Q5) with follow-ups 3. How they handle it now, and what they've tried 4. What it costs them and how often it happens 5. Optional: show the idea and ask what would stop them from using it 6. Ask for a referral or follow-up as a commitment signal Aim to talk about 20% of the time. If you find yourself explaining the product, steer back to their experience. I can also draft follow-up probes for each section, or a short script for the opening of the call.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 1 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
churned-customers

“We're calling customers who cancelled our meal-planning app in the last 60 days. Write the questions we should ask them.”

fix-leading-questions

“Can you check my interview questions before I start talking to freelancers tomorrow?”

nurse-handover-15min

“I only get 15 minutes with each nurse at shift change. I want to understand how they hand over patient information between shifts. Keep the script short.”

vet-reminders-30min

“I'm interviewing independent vet clinic owners next week about how they handle appointment reminders. I get 30 minutes with each. Can you write me an interview script?”

warehouse-hypotheses

“Write an interview guide for warehouse managers that tests these beliefs without tipping them off to what we hope to hear. Also give my colleague something to take notes on during the calls.”

Install

Download the .zip and unzip it. Put its files, in a folder named interview-script, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.