How do you coach a rep to handle a prospect who says they need to 'check with the team' indefinitely

The two paths a rep can take when the committee stall appears

There are only two real responses to "I need to check with the team," and reps default to the wrong one roughly every time. Understanding the trade-off between them is the entire coaching lesson.

Path A — the accept-and-follow-up path. The rep says "Absolutely, take your time — I'll follow up next week," sends a recap email, and puts a task in the CRM. This feels polite, low-friction, and respectful of the buyer's process. It is also how deals die silently. The rep has handed all control of the timeline to a person who has no obligation to return it, and has no visibility into what happens inside the room where the actual decision gets made. The follow-up cadence that results is the familiar death spiral: a check-in email at day 3, a "just circling back" at day 10, a "wanted to bump this to the top of your inbox" at day 21, and a closed-lost at day 90 with the reason field set to "no decision." The rep's forecast stays inflated the whole time because nothing ever explicitly says no.

Path B — the earn-the-room path. The rep treats the deferral as new information about the buying committee rather than as an answer, and immediately works three questions: *who* is on the team, *what* specifically they need to evaluate, and *when* they meet. The goal is not to prevent the internal conversation — that conversation is legitimate and unavoidable in almost every B2B purchase over a few thousand dollars. The goal is to get the rep, or at minimum the rep's materials in a form the champion can actually defend, into that conversation. Path B ends the call with either a calendar invite that includes at least one new name, or an explicit, dated commitment tied to a known internal meeting.

The trade-off is real and worth naming honestly for the rep. Path A costs nothing in the moment and preserves the warm feeling of the call. Path B introduces friction, and a small percentage of prospects will find it pushy — particularly in cultures or industries where consensus-building is slow and hierarchical. But Path A's cost is deferred and enormous: a pipeline stuffed with deals that will never close, a forecast the RevOps team can't trust, and a rep whose activity metrics look fine while their close rate quietly collapses. The coaching position is that Path B is correct in nearly all cases, and the rep's job is to execute it with enough warmth that it doesn't read as pressure.

A third pseudo-path deserves mention only to be dismissed: the hard-close reaction, where the rep responds to the stall with a discount, a deadline, or a "what would it take to sign today." This converts a process problem into a trust problem. The prospect isn't stalling on price; they're stalling because they genuinely cannot sign alone, or because they don't want to say no. Discounting into a committee stall teaches the buyer that waiting produces concessions, which guarantees the next stall lasts longer.

Reading which stall you're actually looking at

"Check with the team" is a single sentence covering at least four distinct underlying situations, and the correct rep response differs for each. Coaching a single scripted rebuttal fails because it treats all four as the same object. Teach the rep to diagnose first.

The real committee. The prospect genuinely is one of five or seven people who must agree, and they cannot sign alone. This is the most common case in mid-market and enterprise, and it is not an objection at all — it's a description of reality. Response: map the committee, arm the champion, request the room.

The soft no. The prospect has decided against you but doesn't want the confrontation of saying so. "I need to check with the team" is the most socially available exit in B2B. Response: give them permission to say no. "It's completely fine if this isn't a fit right now — I'd rather know than keep chasing you." A surprising number of prospects will tell the truth when the truth is made cheap, and the rep gets the pipeline hygiene benefit immediately.

The unconvinced champion. The prospect likes the idea but can't articulate the business case well enough to defend it internally, and knows it. They're not stalling on the committee — they're stalling on their own preparation. Response: build the internal case *with* them. This is where the rep's most valuable work happens and where most reps do nothing.

The no-authority contact. The rep has been talking to someone who was never going to be able to buy, and the "team" is actually one person above them who has not heard of the deal. Response: qualify honestly, and treat the contact as a coach rather than a buyer — but stop forecasting the deal at its current stage.

The diagnostic question that separates these fast is deliberately simple: *"Help me understand — is this a case where the group weighs in and you make the call, or does the group actually decide together?"* The answer sorts a real committee from a no-authority contact in one exchange. A follow-up — *"What's your read on how they'll react?"* — separates the unconvinced champion from the soft no. If the prospect can't predict the room's reaction, they haven't thought about it, which means the deal is earlier than the rep believes.

Concrete numbers behind each path

Coaching sticks better when it comes with arithmetic the rep can check against their own pipeline. Use the rep's real CRM data rather than borrowed benchmarks — the point is that they see the pattern in their own numbers.

The follow-up decay curve. Have the rep pull every deal in the last two quarters where the last logged activity was an unanswered follow-up email after a "check with the team" call. In most reps' pipelines, the pattern is stark: response rates on unprompted follow-ups drop sharply after the second attempt, and deals that go two full weeks without a prospect-initiated reply almost never revive on their own. The rep doesn't need an industry statistic — they need to count their own. Ask them to produce three numbers: how many deals entered this state, how many closed-won, and the median days those deals sat in-stage. The third number is usually the one that lands.

The forecast inflation cost. A rep carrying, say, eight deals in "check with the team" limbo at an average deal size of $24,000 is showing $192,000 of pipeline. If historically two of eight close, the honest number is $48,000. The gap is what the RevOps team is trying to eliminate, and it's why stage-exit criteria matter more than stage names. Have the rep compute their own personal conversion rate out of this specific state — not the team average, theirs — and apply it. Most reps have never done this and are genuinely surprised.

The multi-threading differential. The single most useful internal metric to build is win rate by number of contacts engaged on the deal. Pull two cohorts from the CRM: deals where only one contact ever had a meeting or email exchange, versus deals where three or more did. In practically every B2B org that measures it, the multi-threaded cohort wins at a meaningfully higher rate and closes faster. This is the number that converts a coaching opinion into a policy, because it survives the rep's objection that "my champion said they'd handle it internally." Build it once in RevOps, publish it by segment, and refer to it in every pipeline review.

Time-to-decision anchoring. Teach the rep to ask directly: *"When these decisions have gone well in the past here, how long did they typically take from this point?"* The prospect's own answer becomes the timeline the rep manages against — and it's far more defensible than a rep-invented deadline. If the prospect says "usually about three weeks," then a 45-day silence is a fact both parties agreed was abnormal, and the rep can raise it without being pushy: "You mentioned these usually take about three weeks — we're at six now. What changed?"

The activity budget. Set an explicit ceiling on unpaid pursuit. A workable rule: after the deferral, the rep gets three touches over 14 days, each carrying something new (a case study relevant to a named stakeholder, an ROI model, an answer to a specific objection raised in the room). If none produces a prospect-initiated reply, the deal moves to a nurture track and out of the committed forecast. This isn't giving up — it's refusing to let one deal consume the attention that three fresh opportunities deserve. Reps who protest this rule usually have one deal they've emotionally over-invested in, which is itself the coaching conversation.

The language that actually moves a committee stall

The rep needs specific sentences, not principles. Principles get nodded at in a coaching session and forgotten by the next call. Give them a small number of lines, drilled in role-play until they sound like the rep and not like a script.

To secure the room. *"That makes complete sense — decisions like this shouldn't be made by one person. What I've found is that when I try to explain the technical side secondhand, it never lands as well. Would it be worth me joining for fifteen minutes of that conversation, so your team can ask me directly rather than routing everything back through you?"* The mechanism here is that the rep positions the ask as reducing the champion's workload, not increasing their exposure. Champions decline meetings that make them look dependent; they accept meetings that make them look prepared.

To arm the champion when the room is genuinely closed. Some internal meetings will not admit a vendor, and that's a real constraint, not an excuse. Then: *"Understood — that's an internal conversation. Let me make sure you're not walking in empty-handed. What's the hardest question you expect to get in that room, and who's most likely to ask it?"* The rep then builds a one-page answer to precisely that question, addressed to that person, and sends it before the meeting. This is dramatically more effective than a generic recap deck.

To get a real date. *"When does the group meet next?"* is better than "when can I follow up?" because it anchors on a real calendar event the prospect can't invent. If there's no scheduled meeting, that's diagnostic — a decision with no meeting attached is a decision nobody has prioritized. Follow with: *"And after that meeting, what's the realistic next step if it goes well?"* This forces the prospect to describe a process, and process descriptions are much harder to fabricate than vague optimism.

To close the loop before hanging up. *"So I've got Tuesday the 14th for your ops review, and you'll come back to me by Thursday either way — even if the answer is 'not now.' Fair?"* The phrase *"even if the answer is not now"* is the load-bearing part. It makes silence a broken promise rather than an ambiguous outcome, and gives the rep clean footing to follow up on Friday.

To handle the repeat deferral. When the same stall arrives a second time, the rep must name it without accusation: *"I want to check my own read here. We talked three weeks ago, then two weeks ago, and both times it came back to needing more time with the team. That usually means one of two things — either this isn't a priority right now, which is completely fine, or there's a concern in that room I haven't addressed. Which is closer?"* Offering two acceptable answers, one of which is a graceful exit, gets truth far more often than a single pointed question does.

What to never say. Ban the passive-aggressive follow-up entirely — "just checking in," "bumping this up," "did you see my last email," and any variation that carries no new information. Every touch must contain something the prospect didn't have before. If the rep can't think of anything new, that's a signal to pause the sequence, not to send an emptier email.

Implementation: sequencing the coaching and the RevOps scaffolding

Coaching language without process support decays in about two weeks. The rep reverts under quota pressure, and the manager blames the rep. Sequence the change so behavior and system reinforce each other.

Week one — diagnose, don't prescribe. Pull call recordings and find three where the deferral appeared. Listen with the rep and stop the recording at the exact moment the stall lands. Ask what they were thinking. Almost always the honest answer is "I didn't want to push." That admission is the opening; a rep who has named their own avoidance is coachable, and a rep who has been handed a script is not. Do not introduce new language in this session.

Week two — install the language, drill it. Introduce four or five lines maximum. Role-play each one three times, with the manager playing a difficult prospect who deflects the first ask. The rep must practice the *second* ask, because the first one gets declined constantly and untrained reps fold immediately. Record the role-play so the rep hears their own tone — most reps discover they sound apologetic, which is what makes the ask land as pressure rather than partnership.

Week three — change the CRM so the old behavior is impossible to hide. This is where RevOps carries the load. Add required fields on any opportunity past discovery: number of contacts engaged, name and title of the economic buyer, date of the next internal decision meeting. Make stage advancement conditional on a named second contact. Not advisory — blocked. Reps optimize for what the system requires, and a coaching conversation that isn't backed by a field requirement is a suggestion.

Week four — instrument the exceptions. Build a report of open opportunities with exactly one engaged contact and no scheduled next step, sorted by amount. This is the standing agenda for pipeline review. The conversation shifts from "how's the Acme deal?" — which invites optimistic narrative — to "Acme has one contact and no date; what's the plan this week?" Same deal, completely different conversation.

Ongoing — protect the honest close-lost. The most common failure mode of this whole program is that reps learn to game it by scheduling a meaningless meeting to satisfy the field requirement. Counter it by making closed-lost cheap. If a rep disqualifies a deal early with a clear reason, that should be recognized in pipeline review as good judgment, not as a miss. Where compensation or contests reward pipeline volume, they will actively fight this program — check that first, because incentives beat coaching every time.

A note on the champion's incentives. A champion who won't put the rep in the room is often protecting something: their own standing, an internal political dynamic, or the fact that they oversold the rep on their influence. The rep should assume good faith and ask directly — *"Is there a reason it'd be awkward for me to join? I'd rather know the dynamic than step into it blind."* Prospects answer this honestly more often than reps expect, and the answer usually reveals whether the deal is real.

What good looks like after the change

Set expectations for what success actually resembles, because the first visible effect of this coaching is often a *smaller* pipeline, and an unprepared manager will read that as failure and reverse course.

Within about a month, expect the rep's opportunity count to drop as stalled deals get honestly disqualified. Stage-to-stage conversion should improve because the deals that remain have more than one engaged human attached to them. Average days-in-stage should compress for the deals that survive, since they now have real dates rather than open-ended follow-up loops. Forecast accuracy — the metric RevOps actually cares about — improves last, typically after a full sales cycle has passed through the new criteria.

The behavioral tell that the coaching landed is unglamorous: the rep starts ending calls with a specific date and a specific name, and starts saying "not yet" in pipeline review instead of "still working it." A rep who volunteers that a deal isn't real has internalized the point. A rep who keeps producing optimistic narrative in review has not, regardless of how well they perform in role-play.

Watch for two regressions. The first is meeting theater — the rep books a fifteen-minute call with a random second contact purely to clear the CRM gate. Audit a sample of those meetings; if the second contact never speaks and never appears again, the gate is being gamed. The second is over-application, where a rep starts pushing for the room on tiny transactional deals where a single buyer genuinely can sign. Scale the rigor to deal size; requiring three threads on a $3,000 renewal wastes everyone's time and teaches the rep the process is bureaucratic rather than useful.

Finally, accept that some prospects will stall indefinitely no matter how well the rep executes. The goal was never to eliminate that outcome — it was to find out fast, stop paying for it with rep attention, and keep it out of the forecast.

Related questions

How long should a rep wait before disqualifying a stalled deal?

Tie it to the prospect's own stated timeline rather than an arbitrary count. If they said decisions usually take three weeks, disqualify or downgrade at roughly double that with no prospect-initiated contact. Absent a stated timeline, three value-carrying touches over 14 days is a reasonable ceiling.

What if the champion refuses to introduce anyone else?

Ask directly why it would be awkward — the answer is diagnostic. A champion protecting a genuine political dynamic will explain it; one who oversold their influence will deflect. Either way, arm them with a written answer to the hardest question they expect in the room.

Does this coaching apply to transactional deals under $5,000?

Scale it down. Single-buyer transactional deals rarely have a real committee, so "check with the team" there is usually a soft no. Offer the graceful exit early rather than building a multi-threading plan the deal size can't justify.

Which CRM fields matter most for catching this pattern?

Contacts engaged (count of humans with a logged two-way interaction), economic buyer name and title, and date of next scheduled step. The first two catch single-threading; the third catches open-ended stalls. Make stage advancement conditional on all three.

Should the rep offer a discount to break a committee stall?

No. The stall is a process constraint, not a price objection. Discounting teaches the buyer that waiting produces concessions, extends the next stall, and converts a solvable sequencing problem into a permanent margin problem on renewal.

FAQ

Is "check with the team" always a stall?

No, and coaching that treats it that way produces pushy reps. In most mid-market and enterprise purchases it's an accurate description of how the organization buys. The problem isn't the internal conversation — it's the rep's absence from it and the lack of any date attached to it. Treat the sentence as new information about the buying committee, then work the three questions: who, what, and when.

How do I coach a rep who's afraid of sounding pushy?

Reframe the ask as reducing the champion's workload rather than increasing pressure. Record role-plays so the rep hears their own tone — most discover they sound apologetic, and apologetic delivery is precisely what makes a reasonable request land as pressure. Drill the second ask specifically, since the first gets declined routinely and untrained reps fold immediately.

What should the rep send between the deferral and the internal meeting?

Something addressed to a named person answering a specific anticipated objection — not a generic recap deck. Ask the champion what the hardest question in that room will be and who will ask it, then build a one-page answer to exactly that. Every touch must carry new information; ban "just checking in" entirely.

How do we stop reps from gaming the multi-threading requirement?

Audit a sample of second-contact meetings. If the second contact never speaks and never appears again, the gate is being gamed. Make honest close-lost cheap and recognized in pipeline review, and check whether any contest or comp element rewards raw pipeline volume — incentives beat coaching every time.

What does RevOps own in this versus the sales manager?

RevOps owns the scaffolding: required fields, stage-exit criteria, the single-contact exception report, and the win-rate-by-contacts-engaged analysis that makes the case empirically. The manager owns diagnosis from call recordings, language drilling, and the weekly pipeline conversation. Neither works alone — language without field requirements decays in about two weeks.

Will pipeline shrink after implementing this?

Almost certainly, and that's the expected first effect. Stalled deals get honestly disqualified, opportunity counts drop, and stage-to-stage conversion improves because surviving deals have multiple engaged contacts. Forecast accuracy improves last, typically after a full sales cycle passes through the new criteria. Warn leadership before starting so the dip isn't misread as failure.

Sources

• https://hbr.org/2017/03/the-new-sales-imperative
• https://www.gartner.com/en/sales/insights/b2b-buying-journey
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://www.challengerinc.com/blog/
• https://blog.hubspot.com/sales/sales-objection-handling
• https://corporatevisions.com/blog/
• https://www.rain.group/blog
• https://hbr.org/2012/07/the-end-of-solution-sales

Related on PULSE

• [How do you coach a rep to handle a prospect who only wants to talk to their internal procurement team](/knowledge/cg1056)
• [How do you coach a rep to handle a prospect who says "just send me some information](/knowledge/cg1029)
• [How do you handle a prospect who says they need to 'think it over' after your pitch?](/knowledge/cg0933)
• [How do you coach a rep to handle a prospect who wants to bypass procurement entirely](/knowledge/cg1074)
• [How do you coach a rep to handle a prospect who demands a discount for multi-year commitments](/knowledge/cg1069)
• [How do you coach a rep to handle a prospect who demands a discount before seeing value in 2027](/knowledge/cg1057)