Pavone

Discovery Call Scorecard

Think of your last discovery call. Tick only what genuinely happened — the gaps are the point.

What actually happened?

Your score

Be honest rather than generous — a scorecard you pass by rounding up tells you nothing. The gaps are what make the next call better.

What a discovery call is for

Discovery is the call where you find out whether there is a deal. Not whether the buyer is friendly, not whether they liked what they saw, but whether there is a problem they will pay to fix, someone who can pay for it, and a reason to do it now rather than next year. Everything after discovery is built on what you learned here, which is why a weak discovery call does not fail on the day. It fails in month three, when the proposal meets a stakeholder you never heard of.

Most reps leave discovery feeling it went well because the conversation was pleasant. The scorecard above exists to replace that feeling with seven yes-or-no questions. It is deliberately harsh. A call that scores 55 on it is a normal call, and a normal call is one that usually does not close.

Use it within an hour of hanging up, while you still remember what was actually said rather than what you wish had been.

The seven items and why they are weighted the way they are

The weights are not arbitrary. Pain and impact carry 40 of the 100 points between them because without them nothing else matters: a deal with no quantified problem has no engine. Process and people carry 30 because that is where qualified deals go to die. The last three are habits that separate good reps from average ones but will not by themselves rescue a call.

  • Pain in their words (20). The buyer named a specific problem without you suggesting it. "Our dispatcher spends every morning on the spreadsheet" counts. "Yes, scheduling is a bit of a pain" in response to your leading question does not.
  • Quantified impact (20). You turned the pain into a number: hours, money, missed jobs, people at risk of quitting. If you left without one, you have nothing to put against your price.
  • Cost of doing nothing (10). You asked what happens if this stays as it is for another year. The answer tells you whether inertia is an acceptable option for them, because inertia is who you are really competing with.
  • Decision process (15). You know the steps between "we like it" and a signed contract, and who owns each: security review, legal, procurement, budget cycle.
  • Everyone who has to agree (15). You asked who else gets a say, and who could stop it. The second half of that question is the useful one.
  • They talked more than you (10). Roughly 60/40 in their favour. If you spoke for most of the call, the other six boxes are probably ticked on assumption.
  • Next step with a date (10). A calendar entry, with the right people invited, agreed before you hung up. "I'll send some info" is not a next step.

What a strong discovery call sounds like

Here is how a call that scores 85 or above tends to run. The buyer is a head of operations; the rep sells scheduling software.

Opening: set the agenda, then stop talking

"Thanks for the time. I'd like to spend most of this understanding how scheduling works for you now and where it hurts, and if it makes sense I'll show you a couple of things at the end. Does that work? Great. So walk me through what happens when a job comes in." Forty seconds from the rep, then a process question. Process questions are easy to answer honestly, and the pain shows up in the answer without being asked for.

Pain and impact: follow the thread

Buyer: "It goes into a spreadsheet and Sam, our dispatcher, works out who can take it." Rep: "How long does that take Sam on a normal day?" Buyer: "Most of the morning, honestly." Rep: "And on a bad day?" Buyer: "If someone is off sick, all day. Last month we double-booked someone and two customers were left waiting." Rep: "What did that cost you? Not just the call-out, the whole thing." Buyer: "Probably a day of Sam's time to sort out, and one of those customers has not booked since."

The rep has pain in the buyer's words, a time cost, a churn cost and a named person at risk. Four questions.

Consequence, process, people

"If nothing changes, what does next winter look like?" Then: "Say you decided this was worth fixing. What would actually have to happen for it to get signed off? Who else would want a say, and is there anyone who could block it?" Buyer: "Finance would need to approve anything over 20k, and IT will want to look at it. My director would need to be comfortable." Now the rep knows the threshold, two gates, and the person above the champion.

Close: a date, not a promise

"Based on what you have told me, the double-booking and Sam's mornings are the two things I'd want to show you. Could we get thirty minutes next Tuesday with you and, ideally, your director, so I am not asking you to relay it? I'll send the invite now." A booked slot with the right people, agreed on the call.

The question to ask for each item

Most low scores come from asking a closed or leading version of the right question. The buyer answers the question you asked, so the wording decides what you get.

What you needAsk thisNot this
Pain in their wordsWalk me through how that works today.Are you struggling with scheduling?
Quantified impactWhen that happens, what does it cost, roughly?That must be expensive, right?
Cost of doing nothingIf this is the same in twelve months, what happens?You need to fix this soon, don't you?
Decision processWhat would have to happen between liking this and signing it?Are you the decision-maker?
Everyone who agreesWho else would want a say, and who could block it?Who else should I send this to?
Next stepCan we put thirty minutes in for Tuesday with your director?Shall I send some information over?

Mistakes that score 55

  • Starting with the company overview. Five minutes of slides sets the pattern for the call: you talk, they listen, and the pain never surfaces.
  • Accepting adjectives as impact. "It's a nightmare" is pain. It is not a number. Ask what the nightmare costs, every time.
  • Hearing the pain and pitching immediately. The buyer mentions double-booking and the rep says "that is exactly what we fix". The thread is dropped and the impact never gets quantified.
  • Asking "are you the decision-maker?". Everyone says yes. Ask who else has a say and who could block it.
  • Running a demo because they asked. "Can you just show me?" at minute ten is a request to stop discovering. Show one thing, then go back to questions.
  • Ending with "I'll send over some information". A call that ends without a date in the calendar has ended.
  • Scoring the call on feel. The friendliest calls are often the weakest ones, because neither side pushed.

Using the scorecard with your team

A scorecard is most useful when the score is compared, not just recorded. Four ways to use this one beyond a single call.

  • Score the same call twice: once yourself, once by your manager from the recording. The items you disagree on are the items you are being generous about.
  • Track the weakest item across ten calls, not the total. A rep who always misses decision process has one habit to fix, not seven.
  • Use it in deal reviews. A deal with a 45 on discovery and a commit forecast is a conversation to have, and the gap item is the next call's agenda.
  • Score first calls from new hires in their first month. The pattern usually shows up by call five, and it is cheaper to fix then than after a lost quarter.

The scorecard cannot ask the questions for you

Everyone agrees, reading this, that you should ask what the double-booking cost. On the call, with a buyer who has been friendly and is now checking the time, the question feels pushy, and the rep says "well, I can see how that would be a problem" instead. That is the gap on nearly every low-scoring card, and it is a confidence gap, not a knowledge gap.

The way through is to ask it until it feels normal. Pavone puts you on a discovery call with an AI buyer who gives short answers, says "it's a bit of a pain" and waits, then scores the call on the same seven items you see above, so you can see whether you actually quantified the impact or just nodded at it. Ten practice calls before your next real one makes the harsh question routine.

Frequently asked questions

What makes a good discovery call?

The buyer describes a specific problem in their own words, you quantify what it costs them, you understand how a decision gets made, and you leave with a booked next step. Missing any of those is where deals stall.

What should you cover on a discovery call?

Current situation, where it breaks, what that costs, who is affected, how a decision would get made, and what happens next. Product comes later — discovery is for learning, not presenting.

How do you know if a discovery call went well?

Not by how positive it felt. Judge it on whether you left with quantified pain, a mapped decision process, and a date in the calendar. Friendly calls with none of those are the ones that quietly die.

How long should a discovery call be?

Usually 30 to 45 minutes. Long enough to get past surface answers, short enough that the buyer does not feel interrogated — and you should be listening for most of it.

What questions should you ask on a discovery call?

Start with process, not pain: "Walk me through how that works today." Then follow the thread: "How long does that take?", "What happens on a bad day?", "What did that cost you?", "If nothing changes, what does next year look like?". Finish with "What would have to happen for this to get signed off, and who could block it?".

How many questions should you ask on a discovery call?

Roughly 11 to 14 across a 30 to 45 minute call, and most of them should be follow-ups to what the buyer just said. Fewer than that and you were probably pitching; many more and the buyer feels interrogated. The count matters less than whether each answer got one more "and then what?".

Should you demo on a discovery call?

Not as the main event. If the buyer asks to see it, show one thing that relates to the pain they just described, then go back to questions. "Can you just show me?" at minute ten is usually a request to stop being asked things, and a full demo at that point turns discovery into a presentation.

What is the difference between a discovery call and a qualification call?

In practice they are the same call looked at from two angles. Qualification asks whether the deal can close: budget, authority, timing. Discovery asks what the buyer's problem actually is and what it costs. A good discovery call answers both; a bad one answers neither and feels pleasant.

How do you quantify a buyer's pain on a discovery call?

Ask for the number directly after they describe the problem: "When that happens, what does it cost, roughly?". If they do not know, help them build it: how often, how many people, how long each time, and what it is worth in money. "A day of Sam's time twice a month" is a number; "it's a nightmare" is not.

How do you end a discovery call?

Summarise the two or three things you heard, propose a specific next step with the right people in it, and book it before you hang up: "Could we get thirty minutes next Tuesday with you and your director? I'll send the invite now." A call that ends with "I'll send some information" has no next step.

How do you prepare for a discovery call?

Learn enough about the company to skip the questions their website answers, write down three open questions about their current process, and decide what a good outcome looks like before you dial. Preparation is what lets you listen; a rep who is thinking about the next question is not hearing the answer to this one.

Start practicing in minutes

AI Roleplays for any scenario

  • Build a roleplay from your scenario
  • Practice with AI, voice to voice
  • Get instant, structured feedback after practice
  • Free to start — no credit card required