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
Yes—**keep #5 and make it the centerpiece.** Most of the others either lead participants toward your hypothesis or invite opinions that won’t reliably predict behavior. Your goal tomorrow is to learn **how freelancers handle late payments today, what it costs them, and what they’ve already done to address it**—not whether they like your app. ## Review of your questions | # | Assessment | Better version | |---|---|---| | **1. “Don’t you find it frustrating…”** | Leading: assumes both frustration and a problem worth solving. | “When that invoice became overdue, what did you do?” Then: “What, if anything, was difficult about that?” | | **2. “How often do you send invoices?”** | Useful context, but anchor it to a concrete period. | “How many invoices did you send last month? How many, if any, were paid after the due date?” | | **3. “Would you pay $15…”** | Hypothetical willingness to pay is weak evidence. It also introduces your solution too early. | “What tools or services do you currently pay for to manage invoices or collect payments? What do they cost?” | | **4. “Our app sends automatic reminders…”** | A pitch that invites polite approval rather than discovery. | “What reminders, if any, went out for that invoice? How were they sent, and how did you decide what to say?” | | **5. “Tell me about the last invoice…”** | **Strong.** Specific, past behavior, open-ended. | Keep it. Add: “Walk me through it from the due date until payment—or where things stand now.” | | **6. “On a scale of 1 to 10…”** | Leading and too broad. Disliking admin doesn’t establish a need for payment chasing. | “Last week, roughly how much time did you spend following up on unpaid invoices? What did that involve?” | # Freelancer Late-Payment Interview Script **Duration:** 25–30 minutes **Purpose:** Discovery, not a product pitch.
Show the rest (115 more lines)
### Research objectives — align before tomorrow Use these as working objectives: - Understand how often late payments occur and their consequences. - Learn the actual follow-up workflow, including tools and people involved. - Identify existing workarounds, spending, and attempts to improve the process. - Understand when freelancers want control over client communication. **Decision this informs:** Whether late-payment follow-up is a problem worth pursuing, for which freelancers, and which parts might be appropriate to automate. **Assumptions to test—not state to participants:** Late payments create meaningful costs; current approaches leave gaps; freelancers are comfortable delegating some client communication. ## 1. Opening — 2 minutes > “Thanks for speaking with me. We’re learning how freelancers manage invoicing and payments. This isn’t a sales conversation—there are no right or wrong answers, and we’re interested in what actually happens in your work. We have about 30 minutes; does that still work?” If recording: > “Would you be comfortable with me recording this for research notes? It’s fine if not.” ## 2. Context — 4 minutes - “Tell me a little about your freelance work and the clients you work with.” - “How do you usually bill clients?” - “How many invoices did you send last month? How many, if any, were paid after the due date?” - “What tools do you use for invoicing and payments?” **If they haven’t had a late payment:** Don’t force the premise. Explore their most recent invoice and what helps payments arrive on time. That’s useful counterevidence. ## 3. Reconstruct a recent late payment — 10 minutes > “Tell me about the most recent invoice that wasn’t paid by its due date. Walk me through what happened.” Follow the story rather than reading every probe: - “What were the payment terms, and roughly how much was the invoice?” - “How did you notice it was overdue?” - “What did you do first?” - “What happened next?” - “What tools or methods did you use?” - “How did you decide when to follow up and what to say?” - “Was anyone else involved?” - “Did you get paid? How long after the due date?” If comfortable and practical: > “Could you walk me through a reminder or the tools you used, with client details hidden?” ## 4. Consequences, workarounds, and priorities — 7 minutes - “What, if anything, was difficult about that experience?” - “Roughly how much time did you spend dealing with it?” - “What effect, if any, did the delay have on your work or finances?” - “How typical was that compared with other invoices?” - “What have you tried to make this process easier? What happened?” - “Have you looked for a tool or service to help? Walk me through the last time.” - “What do you currently spend on those tools or services?” - “How do you tell whether your current process is working well?” **If they mention automatic reminders or delegation:** - “Tell me about the last time you used that.” - “What did you let the tool or person handle, and what did you keep control of?” - “Were there clients you handled differently? What happened?” **If they haven’t used either:** - “Have you ever decided not to send a follow-up? Tell me about that occasion.” This explores relationship concerns without assuming they exist. ## 5. Wrap-up — 3 minutes - “What haven’t I asked that matters to how you get paid?” - “Who else would you suggest I talk to—perhaps someone who handles this differently?” - “May I contact you if we have a follow-up question?” Thank them and explain any genuine next steps. ## Interviewer reminders - **Don’t show or pitch the app during this discovery conversation.** If you later test the concept, treat that as a separate activity. - Aim to listen about 80% of the time. - Probe with “Can you give me a specific example?”, “What happened next?”, and “Tell me more about that.” - Notice strong emotions, then ask about the event behind them. - Treat compliments and hypothetical purchase promises as opinions—not demand. - Separate **late-payment pain** from **follow-up pain**: chasing may be easy even when waiting for money is painful. - Capture cases where the current process works well, not just supporting evidence. ## Note-taking template ```markdown # Freelancer Late-Payment Interview Notes Participant: [Name / ID] Date: Freelance work / client types: Invoice volume / payment terms: Key Jobs: [What they’re trying to accomplish] Recent Example: [Specific invoice and timeline] Current Solution: [Tools, manual steps, people involved] Biggest Pain: [If any; include a direct quote] Impact: [Time, money, cash flow, client relationship] Desired Outcome: [Their definition of success] Existing Investment / Willingness-to-Pay Evidence: [Actual spending, purchases, searches, or switching attempts; keep hypothetical statements separate] Communication Boundaries: [What they delegate vs. control] Surprise Finding / Counterevidence: Observed Facts / Quotes: Our Interpretation: [Keep separate from facts] Follow-up: ``` **If you change only one thing tonight: replace the opinion questions with “Tell me about the last time…” and follow the actual sequence of events.**
without
Yes—your list has a strong starting point in **question 5**. The main improvement is to ask about **recent behavior and real consequences**, rather than invite agreement with the problem or reactions to your app. ### Review of your questions | # | Feedback | Better version | |---|---|---| | 1 | “Don’t you find…” leads people toward agreeing that chasing payments is frustrating. | “How do you handle invoices that aren’t paid by their due date?” | | 2 | Useful context, but frequency alone won’t tell you how significant late payment is. | “Roughly how many invoices have you sent in the past three months? How many were paid after the due date?” | | 3 | Hypothetical willingness to pay is weak evidence—people can say yes without committing. | “What tools or services have you used to manage invoices and follow-ups? What do they cost?” Test your proposed price separately, ideally through a real purchase or pilot decision. | | 4 | Introducing your solution early can bias the rest of the conversation. | First ask: “What have you tried to make payment follow-up easier? What worked, and what didn’t?” Save your concept for the end. | | 5 | **Keep this.** It’s specific and grounded in an actual event. | Add probes: “When did you notice? What did you do next? What happened after that?” | | 6 | “Hate” is loaded, and general admin frustration doesn’t establish a payment-chasing problem. | “Thinking about last month, roughly how much time did you spend following up on payments? What else, if anything, did it affect?” | ### A ready-to-use interview guide **Opening** > “We’re learning how freelancers manage invoices and payment follow-up. I’m interested in what actually happens in your work—there are no right answers.” 1. **“Tell me briefly about your freelance work and the clients you typically work with.”** 2. **“Walk me through how you invoice a client, from finishing the work to receiving payment.”**
Show the rest (26 more lines)
3. **“In the past three months, roughly how many invoices did you send? How many were paid late?”** 4. **“Tell me about the most recent invoice paid after its due date.”** - What were the payment terms? - When did you notice it was late? - What did you do next? - How did the client respond? - How was it resolved? 5. **“What effect, if any, did that delay and follow-up have on you or your business?”** - Probe for time, cash flow, and client relationships *after* their initial answer. 6. **“How do you keep track of unpaid invoices and decide when to follow up?”** 7. **“What have you tried to improve that process? What worked and what didn’t?”** - What do you currently pay for? - If they haven’t tried anything: “What has kept you from changing the process?” 8. **“Can you tell me about a time you chose not to follow up on an unpaid invoice?”** - What drove that decision? 9. **“What, if anything, would you change about your current process?”** **Optional concept discussion—only at the end** > “We’re exploring a tool that automatically follows up on overdue invoices.” Then ask: - “Where, if anywhere, would that fit into the process you described?” - “What concerns would you have?” - “What would you need to control or approve before a reminder went out?” **For tomorrow:** prioritize the late-invoice story over getting through every question. Ask “What happened next?” more often than “Would you use this?” If someone rarely has late payments or already handles them easily, treat that as useful evidence—not something to overcome.

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.