What single question should a sales manager ask during a ride-along to evaluate a rep’s ability to handle objections?

The parking lot moment that exposes everything

Picture a mid-market deal in its third meeting. Your rep has been working a revenue platform opportunity for eleven weeks. Today's meeting had six people on the call: the VP of Sales who sourced the project, a director of sales ops who has been the day-to-day contact, a finance analyst who joined twenty minutes late, an IT architect who asked exactly two questions and then went silent, the champion's peer from marketing, and someone whose title nobody caught. The meeting ended warmly. Everyone said the demo looked good. The VP asked for a proposal by end of week.

You are in the car afterward. This is the highest-signal ten minutes you will get with this rep all quarter, and most managers waste it on "how do you think that went?" — a question that reliably produces "pretty good, I think they're into it." That answer tells you nothing about the rep's ability to handle objections, because nothing has been objected to yet. That is precisely the point. The objections that kill deals rarely arrive as objections. They arrive as silence, as a scheduling delay, as a question about data residency asked once and never repeated, as an analyst who takes notes but never speaks.

So instead you ask the single question: which person in that room is most likely to kill this deal, what is their real objection, and what did you hear today that tells you so?

Watch what happens. A rep who cannot handle objections will say something like "honestly I think we're in good shape" or "maybe procurement, they always slow things down." Both answers are the same answer: I do not know, and I have not been listening for it. A rep who can handle objections will say something closer to "the IT architect. He asked about our SSO implementation, I gave a two-sentence answer, and he didn't follow up — which means either he got what he needed or he decided we're not worth pushing on. Given he also didn't ask about anything else in a forty-minute technical demo, I think he'd already formed a view before the call. I want to get him alone before the proposal goes out."

That second answer is not better because it is more confident. It is better because it is falsifiable. The rep has made a claim about a specific human being, grounded it in an observable event, and proposed an action that will confirm or disconfirm it within days. That is what objection handling actually is at the senior level — a hypothesis-and-test loop about what individual people are worried about — and it is almost entirely invisible in a role-play, which is why the ride-along is the only place you can reliably see it.

The reason this framing matters more now than it did five years ago is that the surface area for hidden objections has expanded. Buying groups for meaningful B2B software purchases routinely run six to ten people, and research from Gartner and others has consistently found that a large share of considered purchases end in no decision rather than a competitive loss. No-decision outcomes are objection outcomes. Nobody said no. Somebody, somewhere in the group, quietly declined to advocate, and the deal starved. A rep who only handles objections that are spoken aloud to their face is structurally unable to prevent that outcome. The ride-along question is designed to find out whether your rep operates one layer deeper than the spoken objection.

There is an adjacent version of this worth knowing about, because ride-alongs are not the only place the skill shows. The same question, reframed slightly, works after a demo, after a technical validation call, and — with the tense changed — after a loss. "Who killed it, what was their objection, what did we hear that we ignored?" Post-loss, the question stops being diagnostic and starts being archaeological, which is less useful for coaching because hindsight contaminates the answer. Ask it live, in the car, with the meeting still warm, and you get the rep's actual working model rather than a reconstruction.

How the question actually works on the rep's thinking

The question does three jobs at once, and it is worth understanding the mechanism because it explains why smaller variants of the question fail.

It forces specificity of target. By demanding a person rather than a topic, you break the rep out of category-level thinking. "Price" is not an objection; it is a bucket. The CFO's objection to price is a payback-period objection. The champion's objection to price is a political-capital objection — they have to defend the number to their boss. The IT lead's objection to price is usually not about price at all, it is about implementation labor that shows up on their team's roadmap. When a rep says "price," they have told you they are handling a bucket, and bucket-handling produces bucket-quality responses: discounts, ROI decks, generic case studies. Naming a person forces the rep to select a motive, and motive is where actual handling begins.

It forces evidence. The second clause — what did you hear today that tells you so — is the part most managers drop, and dropping it destroys the question. Without it, the rep can free-associate. With it, the rep must connect their claim to something that actually happened in the room: a question asked, a question conspicuously not asked, a hesitation, a glance, a "we'd have to see," an ask for a document they already have. Evidence-grounding is a trainable skill and it is directly measurable. A rep who consistently cites specific in-room moments is running a live model of the buying group. A rep who consistently cites generalities ("companies like this usually worry about...") is running a template.

It forces a move. The natural follow-up — so what are you going to do about it before the proposal goes out? — converts diagnosis into action. This is where you learn whether the rep can actually handle the objection or only spot it. Plenty of thoughtful reps can identify the blocker and then propose nothing, or propose something passive like "I'll mention it in the follow-up email." Handling means changing the shape of the deal: getting a one-on-one with the skeptic, bringing a solutions engineer to a side call, offering a scoped pilot that de-risks the specific worry, or arming the champion with a one-pager written for the skeptic's boss.

The mechanism has a useful side effect for RevOps: the answers are structured enough to log. If your managers ask the same question in every ride-along and record three fields — named stakeholder, evidence cited, action proposed — you accumulate a dataset that tells you which reps are pattern-matching and which are actually diagnosing, long before it shows up in win rates. It also tells you, in aggregate, which stakeholder types your team systematically ignores. If forty ride-along notes across eight reps almost never name a security or compliance stakeholder, you have found a team-wide blind spot that no individual coaching conversation would have surfaced.

One more mechanical note. The question is deliberately singular. Managers tend to want a battery — how did discovery go, did you cover the metrics, what's the next step, who's the economic buyer. Batteries produce compliance answers. The rep works down your list and gives you the response each item is fishing for. A single unexpected question, asked once, with genuine silence after it, produces a real answer because there is no script for it. Protect the singularity. If you must ask more, ask the follow-up ("what's your move?") and then stop.

When to ask it, and what good looks like on a scale

Timing first, because it changes the answer you get.

Ask in the first five to ten minutes after the meeting ends, while the rep still has the room in working memory. Waiting until you are back at the office — even ninety minutes later — degrades the answer noticeably, because the rep has begun narrating the meeting to themselves and the narration smooths over exactly the awkward moments you want them to notice. If you are doing a virtual ride-along, ask within two minutes of the call dropping, before they open their next tab.

Do not ask during the meeting. Some coaching frameworks suggest a mid-meeting whisper channel; in practice this splits the rep's attention at the worst possible time and teaches them that you are evaluating rather than observing. The ride-along works because the rep runs their own call. Stay silent, take notes on specific moments, and hold the question for the debrief.

Frequency: one ride-along per rep every two to three weeks is a reasonable cadence for a manager with six to eight direct reports, which works out to roughly two to three ride-alongs per week of manager time. Below one a month, you lose the trendline — you cannot tell improvement from a good day. Above one a week per rep, you start distorting the rep's behavior; they begin selling to you.

Here is a scoring rubric that is specific enough to be consistent across managers. Score each of the three components separately rather than giving one blended number, because the coaching action differs entirely depending on which component failed.

Target specificity (0–3). 0: names no one, or names "them" / "the company." 1: names a role category ("procurement," "IT"). 2: names a specific individual. 3: names a specific individual *and* correctly places them in the decision structure — who they report to, what they can block versus merely delay, whether they are a veto or an influence.

Evidence quality (0–3). 0: no evidence, or pure intuition presented as fact. 1: general pattern from other deals. 2: something specific from an earlier interaction in this deal. 3: something specific from *today's* meeting, including negative evidence — what the person conspicuously did not do.

Action quality (0–3). 0: no action, or "I'll follow up." 1: a passive action — send content, mention it in an email. 2: an active action that creates a new interaction with the right person. 3: an active action that also anticipates the objection's second order — what happens if the side call confirms the worry, and what the fallback is.

A composite of 7 or higher out of 9 is a rep you can trust to run complex multi-stakeholder deals with light supervision. A 4 to 6 is the common middle: they see the room but do not yet convert observation into deal mechanics. Below 4 and the problem is usually upstream of objection handling — it is discovery. You cannot diagnose a stakeholder you never qualified.

Track the composite across five or more ride-alongs before you draw conclusions about a rep. Single observations are noisy; a rep who scores a 3 on a routine renewal call and an 8 on a competitive new-logo deal is not inconsistent, they are appropriately allocating attention. Look at the trend and at the ceiling — the best score a rep has ever produced tells you more about their capability than the average does.

A note on stakeholder counts, because it calibrates expectations. In a typical mid-market software deal you should expect the rep to be tracking four to seven named people. Enterprise deals commonly run eight to twelve. If your rep can name only two people in a deal that has been open for three months and carries a six-figure value, the objection-handling conversation is premature — the deal is single-threaded and the real risk is not an objection, it is the champion changing jobs.

Sales cycles have also stretched in most B2B categories, and longer cycles mechanically increase the number of chances for a quiet objection to metastasize. A concern that would have been surfaced and resolved in a six-week cycle has time to become an entrenched position in a nine-month one. This is the practical argument for asking the question early and often rather than saving it for late-stage deal reviews: by the time a deal reaches forecast scrutiny, the objection has usually already done its damage.

What to ask instead, and when the single question is the wrong tool

The single question is not universally superior. It is the best default for evaluating objection handling on a live multi-stakeholder deal, and there are several situations where a different question will teach you more.

When the rep is new (under about ninety days). Asking a new rep to name the likely deal-killer produces a guess, and then you spend the debrief correcting a guess instead of building a foundation. For new reps, ask instead: "Walk me through everyone who was in that room and what you know about what each of them cares about." You are testing coverage, not diagnosis. Move to the single question once they can reliably populate the map.

When the deal is transactional. In a two-call, sub-$15K, single-decision-maker sale, there is no committee and the deal-killer question collapses to "the buyer." Here a better question is: "What did they say that you took at face value, and should you have?" Transactional objection handling is mostly about not accepting the first stated reason — "we're happy with our current tool" is almost never the actual reason.

When you are evaluating rebuttal skill specifically. Sometimes you genuinely do want to know whether the rep can respond well in the moment to a spoken objection. The ride-along question does not test that. For rebuttal mechanics, a structured role-play or a review of recorded call segments is a better instrument, because you can control the objection and compare reps against an identical stimulus. Use ride-alongs for discovery-of-objection, controlled exercises for response-to-objection. Conflating the two is the most common design error in coaching programs.

When the rep is defensive by disposition. Some strong reps hear "who is going to kill this deal" as an accusation that the deal is bad. If you get defensiveness, reframe without softening: "I'm not doubting the deal — I'm asking who we haven't won over yet." Same question, different frame, and it usually unlocks a real answer.

Here are the main alternative instruments and what each actually measures.

The trade-off worth naming explicitly is comparability versus realism. Role-plays give you a controlled stimulus, so you can rank eight reps against the same objection — genuinely useful for hiring calibration and for promotion decisions. Ride-alongs give you unrepeatable, non-comparable, but authentic data. Most managers over-index on one or the other. The healthy pattern is ride-alongs as the primary weekly instrument and one controlled exercise per month to keep a comparable baseline.

There is a resourcing trade-off too. A ride-along costs the manager the full length of the customer meeting plus travel plus debrief — call it two to three hours for an in-person visit, forty-five minutes for a virtual one. Recorded call review costs fifteen minutes if you skip to the flagged moments. If your managers carry ten or more reps, ride-alongs at a useful cadence simply do not fit in the calendar, and the honest answer is to reduce span of control or accept a lower-fidelity instrument. Pretending both are possible is how coaching programs quietly die.

Where this goes wrong, and how to keep it from going wrong

Turning the question into a quiz. The most common failure. The manager asks, the rep answers, and the manager immediately says "actually I think it's the CFO." You have now taught the rep that the question has a right answer stored in your head, and every future answer will be an attempt to guess it. Sit with their answer. Ask what would confirm or disconfirm it. If you disagree, say what you observed and let them reconcile the two accounts themselves.

Asking it in front of the customer or a peer. Any audience turns the answer into a performance. Ask it one-on-one, in the car or on a private call.

Accepting "procurement" as an answer. Procurement is the deal-killer of last resort for reps who have not found the real one. Occasionally it is genuinely true — a hard vendor consolidation mandate is a real objection with a real owner. Usually it is a placeholder. Push once: "What specifically will procurement push back on, and who told you that?"

Confusing a stall with an objection. "They said they need to think about it" is not an objection, it is the absence of one. When a rep offers a stall as their answer, they have skipped the diagnostic step entirely. The follow-up is: "Think about what, and who is doing the thinking?"

Only asking on deals that are going badly. If the question only appears when you are worried, reps learn that being asked is a signal of distrust and they start managing the answer. Ask it on the healthy deals too — on a deal you are confident about, the answer is often the most interesting, because a rep who cannot name a single risk on a strong deal is not paying attention to the quiet people.

Letting the answer die in the car. The debrief is worthless if the action never happens. Whatever move the rep proposed, write it down and check it at the next one-on-one. Two or three cycles of "you said you'd get the architect on a call — did you?" establishes that the question has consequences, and the quality of answers rises accordingly.

Scoring inconsistently across managers. If you have multiple frontline managers, their ride-along notes are only comparable if they are scoring against the same rubric. Run a calibration session: have three managers independently score the same recorded debrief and compare. Divergence of more than one point on any component means the rubric needs sharpening before the data means anything.

Treating the question as a substitute for stakeholder mapping. The question evaluates whether the rep has a model. It does not build one. If your team is systematically single-threaded, the fix is upstream — a required stakeholder map in the CRM at a defined stage gate, reviewed in pipeline inspection. RevOps owns that; the ride-along question just reveals whether the map is real or theater.

Over-instrumenting it. A manager once turned this into a nine-field form the rep filled out after every call. Response quality collapsed within a month. The power of the question is that it is conversational and unexpected. Log three fields afterward, from the manager's memory, not the rep's keyboard.

A last adjacent thought. The same diagnostic transfers cleanly to customer success and renewals, where the hidden-objection problem is arguably worse because the relationship's warmth masks it. Ask a CSM after a quarterly business review: "Who in that room would not renew us if it were their call alone, and what did you hear that tells you so?" Churn, like no-decision, is usually a quiet objection nobody handled. The skill you are evaluating is the same skill.

Related questions

Should I ask this on every ride-along or vary it?

Ask the same question every time. Consistency is what creates a comparable trendline per rep and a comparable dataset across the team. Vary the follow-ups, not the core question.

What if the rep names someone who wasn't in the meeting?

That is usually a strong answer, not a dodge. Absent stakeholders — a CFO who never attends, a security reviewer who appears at contract stage — are among the most common deal-killers precisely because nobody is selling to them.

Does this work for virtual ride-alongs?

Yes, and arguably better, because the rep cannot read your face during the call. Ask within two minutes of the call ending. Keep your camera on and stay quiet after asking.

How does this differ from a deal review question?

Deal reviews assess the deal; ride-along debriefs assess the rep. Same information, different purpose. Do not let the debrief drift into forecast negotiation — that changes the rep's incentive to answer honestly.

What if the rep is right and I was wrong about the room?

Say so plainly. Nothing improves answer quality faster than a manager who visibly updates on a rep's read of a meeting.

FAQ

What exactly is the single question, in one line?

"Which specific person in that room is most likely to kill this deal, what is their real objection, and what did you hear today that tells you so?" Follow it with one and only one follow-up: "So what's your move before the next touchpoint?"

Why a hidden objection rather than the objection the customer actually raised?

Spoken objections get handled — they are visible, and reps are trained on them. The objections that end deals are usually the ones nobody voiced, which is why so many considered purchases end in no decision rather than a loss to a competitor. Evaluating a rep only on spoken objections misses the failure mode that costs the most revenue.

My rep gives a great answer every time. Is the question still useful?

Raise the difficulty rather than dropping the question. Ask about second-order influence: who does the skeptic listen to, and are we selling to that person? Or ask them to name the objection they are *least* equipped to handle in the account. A ceiling-finding version keeps the instrument useful for strong reps.

How do I keep this from feeling like an interrogation?

Silence and stakes. Ask once, then stop talking — do not fill the pause or offer multiple-choice options. And make clear by your reaction that a "here's what worries me" answer is rewarded, not punished. Reps hide risk from managers who treat risk as bad news.

Should the answer be logged in the CRM?

Log a short note in the manager's own coaching record: named stakeholder, evidence, proposed action, and whether the action happened. Do not push it into the rep's required CRM fields — the moment it becomes a mandatory form, it becomes compliance text and the signal disappears.

Can this question evaluate a rep who mostly runs inbound or self-serve deals?

Partly. In shorter, lower-stakeholder motions, reframe it as: "What reason did they give, and what do you think the real reason is?" The underlying skill — refusing to accept the first stated objection at face value — is the same, but the committee framing does not apply.

Sources

• Gartner — B2B Buying Journey research
• Harvard Business Review — The New Sales Imperative
• Harvard Business Review — The End of Solution Sales
• Gong Labs research library
• Sales Management Association
• RAIN Group research and insights
• MIT Sloan Management Review — sales topic archive
• McKinsey — Growth, Marketing & Sales insights

Related on PULSE

• [What's the right interview signal for sales coaching ability?](/knowledge/q33)
• [What is the best question to ask during a ride-along to prompt real-time self-correction?](/knowledge/q14374)
• [How should a 2027 sales manager design ride-along sessions?](/knowledge/q12595)
• [What single question can a manager ask to prompt a rep to build a stronger multi-threaded relationship within an account?](/knowledge/q14424)
• [What is the most effective question to ask after a discovery call to evaluate qualification quality?](/knowledge/q14363)
• [What is the single best question to ask after a lost deal to prompt reflection without blame?](/knowledge/q14353)