Customer Interview Kit — Script, Notes & Synthesis Template

Purpose

This kit helps you run short, focused customer interviews that surface real pains, priorities, and buying signals — not polite opinions. Use it to discover problems customers care enough about to pay to solve, learn the language they use, and convert interview evidence into testable offer hypotheses.

Before You Start — Quick Checklist

• Define the specific target persona (role, context, industry, situation).
• Recruit 5–15 relevant people (early learning comes fast; patterns appear with 8–12).
• Schedule 20–40 minute conversations; ask permission to record or take notes.
• Use a neutral interviewer (avoid stakeholders who already have solutions to sell).
• Print or open this script; test your recording tool and audio quality.

Recruiting & Consent Script (copyable)

Recruiting message (email/DM): "I'm talking to a few people who [short persona description — e.g., freelance designers who sell to startups]. I'd love 20–30 minutes to learn about how you handle [problem area]. This is no sales call — I'm just learning. If you can help, what's a good time?"

Consent script to start the call: "Thanks for taking the time. I’m trying to understand how people like you handle [problem area]. This is just a learning conversation — I won’t try to sell you anything. Is it okay if I record so I don't miss details? I’ll keep your answers confidential and may quote short anonymized excerpts internally. Any questions before we start?"

Interview Roadmap (20–35 minutes)

1. Warm up & context (3–5 min)
2. Work/Process walkthrough (5–8 min)
3. Problem exploration and impact (7–10 min)
4. Current solutions and tradeoffs (3–6 min)
5. Willingness to pay / decision behavior (3–5 min)
6. Close & next steps (1–2 min)

Twenty Non‑Leading Questions (grouped and copyable)

Tip: ask these in your own words and follow natural threads. Pause, listen, and ask “Can you tell me more?” or “How did that happen?”

Warm‑Up & Context

1. Can you describe a typical day when you do [relevant task]?
2. What are the top 2–3 things you’re trying to accomplish in that role or situation?
3. When was the last time you felt frustrated or stuck doing that work?

Problem Discovery

4. Can you walk me through a recent example when that frustration happened?
5. What did you do next when that problem showed up?
6. How often does this happen (daily/weekly/monthly)?
7. What is the most annoying or costly part of the problem?
8. What happens if you ignore or postpone dealing with it?

Current Solutions & Tradeoffs

9. What are you using now to cope with this problem?
10. How well does that solution work? Can you give an example?
11. What do you dislike about your current approach?
12. Have you tried other options? Why did you stop or switch?

Purchase & Decision Behaviour

13. If you wanted something better, what would make you try it?
14. Have you ever paid for something to solve this? What did you pay for and why?
15. Who else would be involved in making a purchase decision like that?
16. What would make you say yes to a new product or service right now?

Closing & Priorities

17. If you could change one thing about how you handle this, what would it be?
18. Is this a problem you want to solve in the next 3 months, 6 months, or is it low priority?
19. Who else should I talk to who deals with this problem?
20. Would you be willing to try a short prototype or let us follow up with a brief test? (yes/no)

Red Flags — Things That Produce Misleading Signals

• Leading or confirmatory questions: avoid "Would you pay for X?" without context.
• Social desirability: interviewee guesses what you want to hear.
• Hypotheticals: "Would you use..." is weaker than asking about real past behavior.
• Convenience bias: recruiting only friendly contacts or extreme users.
• Small‑sample false confidence: a single enthusiastic person isn't evidence of market fit.

Transcription & Tagging Template (copyable)

After each interview, capture these fields for rapid analysis. Use spreadsheet columns or your notes app.

• Interview ID — Date — Persona — Minutes
• Key Quote (verbatim short quote that captures the pain)
• Problem Summary (1 line)
• Frequency (how often it happens)
• Impact (time/money/stress/other)
• Current Solution (short)
• Willingness Evidence (paid, tried trial, asked vendor, budget exists)
• Signals of urgency (planning to change soon, budget allocated, high pain)
• Follow‑up actions / referrals

One‑Page Synthesis Template — Turn Notes into an Offer Hypothesis

Use one page per theme (not per interview). Keep it evidence‑driven and short.

Header

Theme title (e.g., "Small studios waste time on file delivery") — Date — Synthesizer

1) Problem Statement

Single sentence describing the core problem in customer words.

2) Evidence Summary

• Number of interviews mentioning this: X of Y
• Representative quotes (2–3 short verbatim quotes)
• Frequency & context details (when it happens, who’s involved)

3) Impact

Explain cost to customer: time lost, revenue missed, stress, compliance risk, etc. Use concrete examples from interviews.

4) Current Workarounds & Why They Fail

Short list of existing approaches and their tradeoffs.

5) Willingness to Pay Signals

• Who has paid or budget authority?
• Evidence (paid, trial, vendor searches, expressed willingness to spend $X)

6) Offer Hypothesis

Brief description of a minimum viable offering, target persona, and the key value promise in customer language.

7) Riskiest Assumptions

List 2–4 assumptions that must be true for this offer to work (e.g., customers will pay $X, switching cost is low, technical feasibility).

8) Next Tests / Experiments

1. Rapid experiment (e.g., landing page + ad / calendar test / concierge call)
2. Prototype to validate core value (concierge service or simple prototype)
3. Pricing test (pick 2 price points and measure conversion)

Analysis Grid (copyable table)

Use this to roll up multiple interviews into a quick visual that highlights frequency and buying signal.

Columns: Problem | Mentions (#) | % of interviews | Intensity (1–5) | Current Solution | Willingness Evidence | Strong Quotes

Practical Interviewing Tips

• Be curious; silence is your friend — wait longer than feels natural after a question.
• Ask for concrete recent examples; avoid hypotheticals unless you then probe for past behavior.
• Record (with permission) and summarize within 24 hours while details are fresh.
• Use exact customer wording for your value statements and marketing copy.
• Look for converging evidence across people, not one compelling story.

When You’re Done — Quick Synthesis Workflow

1. Tag every interview using the transcription template.
2. Run an affinity grouping (physical sticky notes or digital board) to find recurring problems.
3. Create one‑page syntheses for the top 3 themes and list riskiest assumptions.
4. Design the smallest experiments to test those assumptions and prioritize by learning velocity and cost.

Appendix — Example One‑Line Offer Hypothesis

For freelance designers who lose hours sharing files and checking versions: "A shared file‑delivery tool that automatically versions files and posts change notes so you and your clients stay aligned — saves 2+ hours per project." Next test: set up a calendar page offering a 15‑minute demo and measure signups at two price points.

Closing

This kit is intentionally practical and evidence‑focused. Use the scripts and templates as a starting point; adapt language and probes to your domain. The real value is in repeated conversations, careful tagging, and turning patterns into concrete experiments.