A discovery call template for the answers between the lines.

Discovery fails when it's a questionnaire. This template is a listening framework — the questions are there to make the prospect talk, not to fill boxes.

Use this on first real conversations with a prospect. Leave the call with four things: a real pain, a real decision process, a real timeline, and a reason they'll take the next meeting. Fill it in after — on the call, listen.

Discovery Call — Template

Situation

  • How do they handle this today? ("Walk me through what happens when…")
  • What prompted them to take this call now?
  • Who else lives with this problem?

Pain

  • What's the current approach costing — time, money, misses?
  • What happens if they do nothing? (The real competitor is usually status quo)
  • Their words for the problem — quote them, you'll reuse the phrasing

Decision

  • Who signs, who influences, who can kill it
  • What does their buying process actually look like?
  • Timeline — and what event is driving it (renewal, launch, quarter-end)

Fit & budget signal

  • Have they bought something like this before? What did that cost?
  • What would make this a slam-dunk vs a no? Ask directly.

Next step

  • A specific next meeting with a specific purpose — booked before you hang up
  • What you'll send before then (and by when)
  • Who else should be in the room next time

Capture the call where it actually happens

The best discovery calls happen at lunch, on-site, on a walk — places a call-joining bot can't reach. Fluent records the room, then produces the notes: the pain in the prospect's own words, the decision process they described, the commitments made on both sides. You run the conversation; the template fills itself in.

Fluent for sales reps

Questions

How long should a discovery call be?

Twenty-five to forty minutes. Shorter and you're skimming; longer and you should have booked a demo. End early if you get what you need — it signals confidence.

Should I demo on a discovery call?

No — one screen-share teaser at most. Discovery is about their world; the demo is the next meeting. Mixing them usually produces neither.

Run the call, not the keyboard.

Fluent captures discovery wherever it happens — the notes write themselves.

See Fluent pricing