The Early Pricing Question: Discovery Drills

Chapters
Why does the early pricing question break discovery calls?
Because when a team has never agreed on a first response, each rep improvises a different one under pressure. Two failure modes dominate. The rep deflects — "it depends on a lot of factors, can we come back to that?" — and then deflects again when the buyer repeats the question. Or the rep panics and names a point number with no scope behind it, which becomes the ceiling for every later conversation.
A rep who parks the question twice teaches the buyer that price is a subject the seller cannot discuss honestly. Everything after that is filtered through that judgment. The buyer stops volunteering scope detail because they now read discovery as a delay tactic rather than a path to a real number.
The common counter-argument is that strong reps handle a pricing question on discovery calls best by improvising, and that an agreed first response makes the team sound canned. We disagree on the first part and take the second seriously. Rehearsal is what makes improvisation safe. When the opening three moves are automatic, the rep's attention is free for the branch — the tone, the follow-up, the thing the buyer actually meant. Reps who improvise from zero are not being creative; they are being caught flat and buying time with words.
So the fix is not a longer pricing policy document. It is one response, drilled to automaticity, with rubric rows a manager can verify from the transcript.
TL;DR
When a buyer asks what it costs early, run one rehearsed response: acknowledge the question on your first turn, give a defensible range with the driver that moves it, then trade for the scope detail that narrows it. The early pricing question is not an interruption to discovery — it is a trade you can price. Drill the response until it is automatic, score it from the transcript, and re-run any rep who hedges instead of answering or names a point number they cannot defend.
- Hedging on the first turn reads as evasion; a bare number reads as a commitment you will be held to.
- One agreed first response: acknowledge, range with a named driver, trade for scope.
- Score four observable rows from the transcript, not the manager's impression of poise.
- Rehearse the three real follow-ups: budget pushback, per-seat demand, and silence.
- Run a 15-minute paired drill with a stated pass bar and a scheduled re-run when failed.
The one first response to drill
Three moves, in order: acknowledge, range, trade. Acknowledge means you answer the question as a question worth answering, in one short sentence, with no hedging preamble. Range means you give real numbers with the driver that moves them. Trade means you ask for the scope detail that narrows the range — and you say why you are asking.
Here is the line to rehearse verbatim, with your own brackets filled in: "Fair question — I'll give you a number. For teams shaped like yours it usually lands between [low] and [high] per year. What moves it inside that range is [driver]. How many [units] are you running today?"
A range with a named driver is defensible; a point price offered before scope is a guess the buyer will hold you to. The driver matters as much as the endpoints. If your range is wide, the driver explains the width and the buyer gets a reason to help you narrow it. If a rep can state the range but not what moves it, the rep is reciting, not answering.
Set the terms of the trade out loud. "I can tighten that to a real number once I know [scope detail] — want to do that now, or later in the call?" That names what you need, why you need it, and gives the buyer a clean way to decline. A stall you can hear is more useful than a polite yes you cannot price.
Then return to discovery with the question you would have asked anyway. Keep the pricing exchange short; the point is to answer it and move, not to open a negotiation.
What rubric rows should a manager score from the transcript?
Four rows, all observable in the words. Score the transcript, not the impression: a rubric row that cannot be verified from the words is not a rubric row. Poise, confidence, and executive presence are not rows — they are conclusions you draw after the rows are marked.
Talk/listen ratio is worth reading alongside these rows, but read it as an input to investigate. A rep who talks through the whole pricing exchange is usually justifying the range instead of trading for scope. Open the transcript at that moment and check which one it was before you coach anything.
Mark each row pass or fail. Partial credit hides the rep who does two moves well and never trades.
| Rubric row | Pass looks like this in the transcript | Fail looks like this |
|---|---|---|
| Acknowledge on the first turn | Direct sentence committing to give a number, no preamble | "It really depends" with no commitment to answer |
| Defensible range with a driver | Low and high stated, plus at least one named driver of the spread | Point number with no assumption, or no number at all |
| Trade for scope | A specific question asking for the detail that narrows the range | Rep moves on, or asks a generic discovery question unrelated to price |
| Return to discovery | Next question continues the planned discovery sequence | Call becomes a pricing negotiation for the remaining time |
The three follow-ups that actually happen
In our experience, buyers respond to a range in a handful of recognizable ways, and we recommend drilling these three. Drill a first response to each, then let reps improvise the rest of the branch.
"That's more than we budgeted." Do not discount and do not defend the range. Find out what number they were carrying and what it was based on, because a budget figure built from a competitor's quote is a different problem than one built from last year's line item. A Sandler negative reverse is the precise tool here: soften into the resistance — "it may be that this is bigger than what you set aside; should we stop the pricing thread and see whether the problem is even worth that?" — so the buyer argues the case themselves. If your team discounts reflexively at this moment, drill it separately with our budget objection handling guide.
"Just give me a per-seat number." Give it. Refusing a direct, answerable question costs more than the number does. Bound it with the assumption out loud: "At [count] seats on [tier], it's [figure] per seat per month — that assumes [assumption]. Change the assumption and the per-seat number moves." Then trade: ask which seat count they are actually planning for.
Silence. We read silence after a price range as buyer arithmetic rather than rejection, and the rep who rushes to fill it often ends up discounting. Hold it. When you speak, check rather than concede: "What's your reaction to that range?" That question is scoreable. "I know that sounds like a lot, and there's flexibility" is a self-inflicted discount and should be marked a fail.
Keep the inventory small. Three branches drilled to automatic beats a twelve-page objection matrix nobody rehearses.
The 15-minute pricing conversation drill
We recommend a 30-minute coaching block: 5 minutes setup, 15 minutes drill, 10 minutes debrief. Budget roughly 10 minutes beforehand to pick the scenario from a live deal and choose the rubric row — prep is real work and pretending otherwise is why programs stall.
Setup: name the persona, the deal shape, and the moment. The buyer asks what it costs before scope has been established. Run the exchange live, then run it again with a different follow-up branch. A solo price question roleplay works on the same structure if your practice tool produces a scored transcript. In XL Roleplay, each session is recorded, timed, and transcribed, the rep is scored against your own rubric, and flags in the report link back to the exact moment in the transcript.
Pass bar: all four rubric rows pass on a single attempt. The rep acknowledges on the first turn, states a range with at least one named driver, asks a question that trades for the scope detail, and returns to the planned discovery sequence. Any point number offered without a stated assumption fails the range row.
A failing attempt sounds like this: "Ah, good question. Honestly it really depends on a lot of factors, and I'd hate to quote you something wrong before I understand your situation properly. Can we park that and come back at the end?" That fails the first row on the spot. In the field it usually gets worse — the buyer repeats the question, the rep parks it again, and the pricing conversation now happens from behind.
Debrief: one behavior only. Ask the rep to self-diagnose first — "where in that exchange did you stop answering?" — then render your verdict on that one moment. A drill without a pass bar is a conversation, and a failed drill without a scheduled re-run is a note nobody reads. Re-run rule: a failed attempt is re-run inside the same week, same scenario, different follow-up branch, and the re-run is scheduled before the debrief ends. Our debrief guide has the full script.
How do you keep the drill from dying after week one?
Put it on the calendar as a protected coaching block that is separate from pipeline review. Deal reviews will eat this drill every time, because a stuck deal is urgent and a pricing reflex is merely important. The block survives as a recurring commitment or it does not survive.
Read the results per rep per scenario, never as one blended discovery score. Track the price-question rows per rep per scenario; a blended discovery score hides the rep who hedges every time. One rep may pass on the mid-market persona and fail whenever the buyer goes silent. That is a specific, drillable gap, and it disappears the moment you average it.
Then attach the rows to a gate. Passing the pricing exchange on two named personas is a reasonable prerequisite for solo discovery calls, alongside the rest of your discovery exit criteria. Time in role is not evidence. A scored transcript is.
Be honest about scope. This drill certifies one exchange. It does not certify negotiation, deal-desk approvals, or renewal pricing — those are separate scenarios with separate pass bars. Trying to cover them all in the same fifteen minutes produces feedback covering too many issues at once, which reps discount and forget.
Frequently asked questions
Should a rep ever refuse to give a number on a discovery call?
Rarely. If you genuinely cannot price the shape of the deal, say so plainly and commit to a date for the number rather than parking the question. Silence about price is read as evasion, not discipline.
What if our pricing is genuinely custom and we have no range?
Then build ranges by deal shape before you drill anything — segment, seat band, and tier. If your team cannot state a defensible range for the three most common shapes, that is a pricing problem, not a coaching problem.
Does an agreed first response make reps sound scripted?
It can, if reps memorize words instead of rehearsing the three moves. Drill the structure — acknowledge, range, trade — and let each rep phrase it in their own language. Score the moves, not the wording.
Who plays the buyer in the paired drill?
A peer works if the peer commits to one branch and plays it straight rather than going easy. A manager or an AI persona gives you a scored transcript, which matters when the result feeds a certification gate.
How many times should a rep re-run a failed attempt?
Re-run until all four rubric rows pass on a single attempt. If a rep fails the same row three sessions running, stop drilling and check whether they can state the range and its driver at all — that is a knowledge gap, not a reflex gap.