Decision Maker Objection: First Response Drill

Why the decision maker objection needs one agreed answer

When a buyer says I need to run this by my boss, the deal has just gained a stakeholder the rep has never spoken to. An unprepared rep tends to respond with relief or with pressure. Relief sounds like Of course, take your time, and the deal then waits on a forwarded email the rep never sees. Pressure sounds like What would it take to get this done without them?, and the champion stops returning calls.

Both replies are improvised under stress, and both are usually learned on live pipeline. Live pipeline is the most expensive classroom a sales org can choose. Each fumbled attempt costs a real opportunity. It teaches the rep only that the moment felt bad, not what to say instead.

We treat the objection as a disclosure, not a brush-off. The buyer has just told you the decision process includes someone else. In the next few sentences, the rep has to convert that disclosure into a name, an agenda, and a meeting. Practice that conversion in scored roleplay first, where a miss costs nothing but a re-run.

A buyer who mentions a boss has handed you the decision process; the rep's only job is to turn the disclosure into access.

What should the agreed first response say?

It should acknowledge the check-in, ask who the other person is, ask what they will want to know, and propose meeting together, in that sequence. Here is a first response we recommend teams adopt or adapt.

Rep: Makes sense, most teams bring someone else in at this point. Who will you run it by, and what's their role in the decision? Then: When you walk them through it, what do you expect they'll ask first? Then: Rather than you carrying my answers secondhand, would it help if we all got on a short call? I can bring the pieces they'll care about.

The sequence matters. Asking for the meeting before learning who the person is sounds like an attempt to go around the champion. Asking what the boss will ask before proposing the call gives the rep a reason for the meeting that serves the champion: the champion will not be stuck fielding questions they cannot answer.

Write the agreed line into your objection library next to the buyer phrasings your team actually hears, and change it only when scored transcripts show it failing. Agreed does not mean memorized word for word. The rep must hit each move; the phrasing can flex to fit the buyer.

The first response asks who the stakeholder is, asks what they will ask, then proposes meeting together.

Score it against exit criteria, not impressions

A manager should be able to grade the attempt from the transcript alone, without having watched the roleplay. Each criterion below is evidence the buyer said out loud. A pass requires all of them. The rep's sense of the buyer's mood counts for nothing.

Talk/listen ratio belongs on the scorecard as a diagnostic. If a failed attempt shows the rep talking through most of the exchange, investigate whether they pitched instead of asking. Do not make it the pass bar; a rep can listen well and still never ask for the meeting.

If the transcript cannot show the stakeholder's role, their likely questions, and a booked meeting, the attempt failed.

Shouldn't strong reps just improvise the answer?

No for the first response, yes for everything after it. The opposing view deserves a fair hearing. Experienced reps read the room, and a scripted line delivered to a senior buyer can sound canned. Some of your best closers have never used a script and handle authority on instinct.

The problem is that instinct is invisible and uneven. Listen for the failure pattern in your own recordings: the objection arrives late in a good call, the rep relaxes, and the default reply is No problem, just let me know. Good authority objection handling depends on the opening move being there when attention is lowest. A drilled first response removes that failure. It does not remove judgment.

After the first response has done its work, the branches genuinely need improvisation. The boss might sign, advise, or route to procurement. The champion might reveal the boss already favors another option. Strong reps handle those branches from understanding, and they handle them better when the opening is automatic and their attention is free for listening.

If a strong rep's own phrasing hits every exit criterion, pass the attempt. The standard is the behavior, not the words.

Rehearse the first response until it is automatic so attention stays free for the branches that genuinely need improvisation.

Tie the score to your economic buyer row

A roleplay built around economic buyer access is only as useful as the row it is graded against. The drill should certify the behavior your methodology already asks for, in its vocabulary. If your team qualifies deals with MEDDIC or MEDDPICC, the relevant row is Economic buyer: the person with final authority over the spend.

Be precise about what MEDDIC does. It is a qualification checklist. It lists Economic buyer as a field the deal must qualify on; it does not teach the rep how to ask. The drill supplies the conversation skill, and MEDDIC supplies the standard. The boss a champion mentions is not automatically the economic buyer, so your first exit criterion requires the rep to learn the person's role, and your MEDDIC row requires confirming whether that person signs. Our MEDDPICC exit criteria guide covers how to write that row.

Load your call stages and rubric before any session is scored, so the coaching note cites your playbook rather than generic advice. Reps rationally discount feedback graded against someone else's standard. Disclosure: XL Roleplay, which publishes this blog, scores sessions against the organization's own methodology. A recorded peer roleplay graded on a shared rubric row can certify the same behavior.

MEDDIC tells the rep the economic buyer must be confirmed; the drill teaches the sentence that confirms the economic buyer.

Debrief one moment, then schedule the re-run

Isolate the moment the buyer said I need to run this by my boss and nothing else. Play back the rep's reply. Ask the rep first: Which exit criterion did you hit, and which did you miss? Let them answer before you give a verdict.

Then name one behavior. If the rep skipped the stakeholder's questions, that is the coaching point, even if their tone also drifted and they talked too long. Stacking corrections produces a rep who remembers the list and changes nothing. End the debrief with a date: the re-run happens in the next session, same scenario, same rubric row.

We recommend a 15-minute 1:1 built around the flagged moment, held in addition to the pipeline 1:1 and never folded into it. Deal reviews absorb any coaching time that is not protected on the calendar. The roleplay debrief guide has a full script.

A debrief that corrects more than one behavior produces a rep who remembers a list and changes nothing.

The drill to run this week

Setup. Spend about 10 minutes beforehand picking a live deal where a champion has mentioned a boss, and choose the rubric row you will grade. A format that works: the session runs 30 minutes, with 5 minutes of setup, 15 minutes of drilling, and 10 minutes of debrief.

Buyer brief. The buyer is a director who likes the solution, has not yet told their VP, and says I need to run this by my boss when asked about next steps. If the rep asks, the boss is the VP of Finance, who will want to know how the cost compares to current spend. The buyer agrees to a joint call only if the rep gives a reason that helps the director.

Pass bar. Every exit criterion appears in the transcript: the stakeholder's role, at least one question they will ask in the buyer's words, and an agreed joint meeting. We recommend requiring passes on two consecutive attempts before the rep uses the line on live deals.

A failing attempt sounds like this: Totally understand. Want me to send over a summary you can share with them? I'll follow up later this week. The rep never learned who the boss is or what they will ask, and handed the selling to someone without the answers. A failed attempt is re-run in the next session on the same scenario, not marked complete.

A drill counts as passed only when the transcript shows the behavior; completion without a pass is a re-run, not a result.