TranskribatorTranskribator
Discovery call questions: a guide built from real conversations
B2B sales

Discovery call questions: a guide built from real conversations

Develop discovery questions from call transcripts to uncover context, goals, current processes, impact, criteria and decision makers.

The Transkribator team5-minute read
SOURCEDISCOVERY BEFORE THE DEMOTrigger: why now?Process: how it workstodayImpact: where thingsbreak downCriteria: what a solutionmust doFROM WORDS TO RESULTS
Working with a real recordingIllustrated training exampleTemplate to copy
B2B sales

Discovery helps you understand the situation

“Do you need automation?” suggests an easy answer. It tells you little about the process and can quickly turn into a product demo. A good discovery call helps both sides see whether there’s a problem to solve and a reason to continue.

Transcripts of previous calls show which questions elicited examples and which led only to yes or no. Use them to improve the guide and keep private customer details out of training materials.

Workflow

Go from an event to decision criteria

  1. Start with the trigger

    Ask what happened and why it matters now. That distinguishes an active problem from general interest.

  2. Understand the current process

    Ask for a recent example: who starts the work, what they hand off, where they check it and how the task ends. Take time to understand the steps before mentioning features.

  3. Ask about consequences and previous attempts

    What happens when the process fails? What have they tried and why wasn’t it enough? Discuss a real case instead of asking the customer to imagine the future.

  4. Clarify how a decision will be made

    Ask who will be involved and what constraints, time frames and criteria apply. This helps both sides assess fit and prepare a relevant demo.

Worked example

Discovery call about recording meeting outcomes

This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.

Excerpt from a training recording · 12:40
After a team meeting, the coordinator pulls decisions from notes by hand. If the email doesn’t go out that day, people start asking what they need to do.

Useful follow-ups: “Walk me through the last time this happened.” “What does the coordinator look for?” “Who reviews the result?” “What counts as a finished email?” These questions reveal the process.

A weak follow-up: “Want us to automate that?” It proposes a solution before you understand the limits of the problem. The case is fictional.

Trigger: whynow?EventProcess: howit works todayFactsImpact: wherethings break downCost of the problemCriteria: whatthe solution must doNext step
The guide moves from a real event to conditions you can verify before taking the next step.
PurposeOpen questionWhat to probe
TriggerWhat changed before you started looking?A specific event
ProcessHow did it go the last time?Steps and participants
ImpactWhat happened because of the delay?Observable consequence
CriterionHow will you know it’s better?Verifiable result
Ready-to-use template

Discovery call guide

Use the purpose of each section to guide the call and follow up on detailed answers.

Template for your workSelect and copy
Purpose of the call and time available:
Trigger — what changed and why now:
Recent example of the current process:
Participants and handoffs:
Main difficulty:
Consequences:
What they already tried:
Criterion for a good outcome:
Constraints and risks:
Who is involved in the decision:
A next step useful to both sides:
What remains unknown:
Check the result

Check your questions against call recordings

  • Questions don’t suggest the desired answer.
  • There’s a prompt for a recent, specific example.
  • The guide covers consequences and criteria.
  • The demo leaves time for discovery.
Past callsStrong and weak questionsGuidePurpose of each sectionConversationA specific processNext stepFit for both sides
Use transcripts to improve questions based on what people actually say.
Frequently asked questions

A closer look

How many questions do we need?

There’s no fixed number. Cover the main topics and leave room to follow up. Five questions about a specific case can reveal more than a list of twenty.

When should we show the product?

Once you know the task and what would make a demo relevant. Sometimes the right outcome is to recognize a poor fit or set up a separate demo.

Keep working with the recording