Customer Discovery Call Template for Better Product Interviews

Discovery calls are for evidence, not approval

Customer discovery goes wrong when the interviewer needs the idea to be right. Questions become leading, vague encouragement sounds like demand, and the call ends with a list of features the participant says they might use someday.

A useful discovery call starts with one hypothesis and looks for evidence that could confirm or weaken it. The participant describes the last time the problem occurred, shows the current workflow, explains what they tried, and names what the problem costs. The interviewer spends less time explaining and more time following specific details.

The agenda below is a guide, not a script. Follow an unexpected answer when it reveals real behavior, then return to the sections needed to compare this interview with the others.

The agenda (copy-paste this)

Duration: 45–60 minutes

Format: One interviewer leads; one person owns follow-up questions; avoid presenting the product until the research portion is complete

Section 1 — Goal and hypothesis (before the call)

Research goal: what decision will this interview inform?
Hypothesis: "We believe [person] struggles to [job] because [cause], resulting in [cost or consequence]."
Evidence that would support the hypothesis:
Evidence that would weaken it:
One topic this call will not try to answer:

Section 2 — Warm-up (5 min)

Tell me about your role and what you are responsible for
How does this area of work fit into a normal week?
Who else is involved when this work happens?

Section 3 — Problem exploration (10–15 min)

Tell me about the last time this problem happened
What triggered it?
What did you do first, and what happened next?
Where did you lose time, confidence, money, or control?
How often does this happen?
Who else feels the consequence?
What happens if you leave it unchanged for six months?
What have you tried, and why did that fall short?

Section 4 — Current-workflow walkthrough (10–15 min)

Please share your screen and walk me through the real workflow from start to finish
Which tools, documents, handoffs, and workarounds are involved?
Where do you switch context or copy information by hand?
Which step needs judgment, approval, or help from someone else?
Show me the artifact you use today, if it is safe to share
What did you leave out because it feels too obvious or messy to explain?

Section 5 — Magic-wand question (5 min)

If you could change one part of this workflow tomorrow, what would change?
What would become possible after that change?
What must stay the same?
How would you know the new workflow was better?

Section 6 — Willingness-to-pay probes (5–10 min)

What does this problem cost today in time, lost revenue, risk, or outside services?
Have you paid for a tool, contractor, or internal project to address it?
Who owns the budget for solving it?
What would need to be true for this to become a funded priority?
What competing priority would this displace?
What buying, security, or implementation step would slow a decision?

Section 7 — Wrap-up and next step (5 min)

Summarize what you heard and ask the participant to correct it
Ask permission for one follow-up question by email
Agree on any artifact, introduction, or second interview they offered
Owner and date for each follow-up:
Would a later concept review be useful? Yes / No / Maybe, and why

Note-capture table

Moment or question	Exact quote	Observed behavior or artifact	Interpretation to test	Follow-up

What generic discovery templates miss

Generic interview guides often provide a long question bank without saying what evidence each question should produce. The interviewer races through prompts, the participant answers in generalities, and the notes contain opinions instead of a recent example that another researcher can examine.

The second problem is mixing observation with interpretation. "Their handoff takes 30 minutes" may be an exact quote, a timed observation, or the researcher's guess. Those sources carry different weight. A note-capture table keeps the participant's words, visible evidence, and the team's interpretation separate.

Many templates also ask "Would you pay for this?" and accept yes as pricing evidence. A polite answer costs the participant nothing. Current spending, the cost of the problem, budget ownership, urgency, and a concrete buying process reveal more than a hypothetical purchase promise.

Finally, the current-workflow walkthrough is usually optional. It should be central. Watching someone navigate three tools and a spreadsheet can contradict ten minutes of polished explanation, and that contradiction is often the most useful finding in the call.

How Pavleur handles this

Pavleur records the conversation while the interviewer stays present. The interviewer can maintain eye contact, listen for contradictions, and ask a precise follow-up instead of trying to type every sentence before the participant moves on.

Exact quotes remain retrievable from the transcript, so the research team can check the words behind a summary before turning a pattern into a product decision. When the participant shares their current workflow, Pavleur preserves screenshots with the surrounding discussion. The spreadsheet, dashboard, or sequence of tools remains part of the evidence instead of becoming "participant showed process" in the notes.

The resulting report gives the team a reviewable call record while the note-capture table keeps interpretation explicit. See Pavleur for product managers or compare meeting capture options.

Related templates

Carry validated needs into a live opportunity with the sales call notes template.
Revisit customer goals and evidence over time with the quarterly business review template.
Align the team once discovery becomes a project with the project kickoff agenda.