GuidesCustomer discovery
Customer discovery interviews: A 30-minute script for founders
Recruit the right people, ask about a real recent event, and turn discovery interviews into an actionable product decision.
- 00–05 min
- Set the context
- 05–15 min
- Reconstruct one real event
- 15–22 min
- Find the workaround and cost
- 22–27 min
- Identify the buyer
- 27–30 min
- Agree on a follow-up
A working agenda for the interview script in this guide.
What you’ll do
- Recruit one specific role that encountered the problem recently.
- Walk through a real event and capture the trigger, workaround and cost.
- Look for repeated evidence and a buyer who will make a concrete commitment.
Pick one question that can change what you build
A discovery call is easiest to run when you know what decision it should inform. Suppose you are considering a tool for collecting subcontractor documents. Start with a question such as whether small commercial contractors spend enough time chasing missing documents to pay for a better handoff. That is narrow enough to find the people doing the work and compare their answers.
Recruit a small first batch of people with the same responsibility who dealt with the issue recently. Talk to a person who does the work and, when different, the person who approves purchases. Five interviews are a practical starting batch for learning where to look next. They do not give you a representative market estimate.
A script you can use on the call
Introduce the work in one sentence, then explain that you want to understand their process. Ask permission before recording and offer a note-taking option. Save any product pitch until after they’ve described the last real example. YC’s Startup School guidance focuses on learning from current and potential users, and distinguishes the conversation from a prototype session.
- Minutes 0–5. What are you responsible for, and when did you last have to do this?
- Minutes 5–15. Walk me through that case. What triggered it, what happened next, and where did you have to wait?
- Minutes 15–22. What did you try to make it easier? What did the workaround cost in time, cash or delays?
- Minutes 22–27. Who needed the result? Who can authorize paying for a better process?
- Minutes 27–30. Is there another person I should talk to, or a version of the workflow you could show without sharing private information?
Probe the detail that changes your interpretation
If someone says the process is painful, ask them to reconstruct the last time it occurred. A monthly delay that holds up an invoice has a different consequence from an annoyance they encounter once a year. Ask what happened when they did nothing. The answer helps you tell whether the job is urgent or simply unpleasant.
If they say they would use a product, ask about the closest thing they have already tried. What did they pay? What made them stop? In a separate follow-up, a basic prototype lets you watch how they try a task. Y Combinator recommends observing people work through a concrete action and describe what they are thinking. That observation answers a different question from an interview about the existing job.
Turn notes into a decision
Make one row per interview and record the customer role, trigger, last occurrence, workaround, consequence, budget owner and any evidence you saw. Keep observations separate from your hypotheses. For example, a two-day invoice delay is an observation if the participant describes the actual dates. A prediction that the finance director will pay for faster collection is a hypothesis until you test it.
Compare the rows by workflow, then pick one next step. If several contractors describe the same missing document, offer a small trial on one project and ask for a real commitment such as time with the document owner or a paid pilot. If the stories vary widely, narrow the audience and interview another batch before deciding which problem to solve.
Tools for this article
FounderTools is a referral partner for tools marked “Affiliate link.” If you sign up or buy through one of these links, we may earn a commission or credit.
TallyAffiliate linkScreen for a recent example of the problem before inviting someone to an interview.
Cal.comAffiliate linkGive qualified interviewees a short booking link with a dedicated discovery-call schedule.
CastmagicAffiliate linkTranscribe an interview with the participant’s permission and check quotes against the recording.
Sources
2 references- How to Talk to Users
Y Combinator Startup School