How do you decide whether to push for a close or give the prospect more time?

Two paths out of the same moment, and what each actually costs

Every deal reaches a point where the seller has said everything worth saying and the prospect has not signed. From there, only two moves exist, and they are not symmetric.

Pushing means applying structured pressure toward a decision: sending the contract, naming a date, attaching an expiring term, or asking a closing question that forces a yes or a no. Its virtue is that it converts uncertainty into information. A push that fails still tells you something true — you learn the deal was never real, and you recover the forecast slot and the hours. Its cost is relational. A push aimed at someone who genuinely needs time reads as pressure, and pressure at the wrong moment converts a slow yes into a fast no. It also burns your remaining leverage. You can only credibly say "this offer expires Friday" once. If Friday passes and you extend, you have taught the prospect that your deadlines are decorative, and every future date you name is discounted.

Giving time means deliberately delaying the ask while keeping the deal alive. Its virtue is that it lets internal processes finish — security reviews, legal redlines, the budget meeting that happens on the first Tuesday of the month. Many deals stall for reasons that have nothing to do with you and everything to do with a queue you cannot see. Its cost is drift. Deals decay. A pipeline record with no dated next step has a way of aging into the "no decision" bucket, which is the most common loss in complex B2B sales — not losing to a competitor, but losing to inertia. Time also imports risk you did not have before: reorgs, budget freezes, a champion who takes another job, a new priority that outranks yours.

The asymmetry matters. A bad push costs you one deal. A bad pause costs you one deal *plus* the weeks of capacity you spent nursing it, plus the forecast credibility you spent carrying it. That argues for a bias toward forcing decisions earlier — but only where the decision can actually be made. Pushing a prospect who lacks authority to say yes produces neither a close nor clean information; it produces an evasion, which is the worst outcome of the three.

There is a third option most sellers refuse to name: qualifying out. Not pushing, not pausing — closing the record as lost and reinvesting the hours. When both gates fail repeatedly and no new information arrives across two cycles, this is usually the correct answer, and treating it as a failure rather than a decision is how RevOps teams end up with pipelines that look three times healthier than they are.

The gates that decide it

The decision is not a feeling. It resolves to a small number of factual checks, and each one is either answered or it is not.

Authority. Have you had a direct conversation with the person who can approve the spend? Not a champion relaying that "leadership is on board" — an actual conversation with the actual approver. If your only channel is a champion, you cannot push, because there is no one on the other end with the standing to say yes. What you can do is push the *champion* — not toward signature, but toward an introduction. "What would make it easy for you to get fifteen minutes with your VP and me?" is a legitimate close on a different object.

Budget. Is there money allocated, or is there enthusiasm? These feel identical in a discovery call and behave nothing alike. Allocated means someone can name the line, the fiscal period, and roughly the number. Enthusiasm means everyone agrees the problem is real. Deals die in the gap between the two more often than they die on price. Test it plainly: "If we agreed on everything today, whose budget does this come out of, and is it already sitting there?" Hesitation is your answer.

Open objections. Is there any unresolved concern held by anyone with veto power? Security, procurement, legal, IT, and finance all hold vetoes they rarely announce. A stakeholder who has stopped responding is not neutral; silence in a buying process is a soft objection you have not surfaced yet. Pushing does not resolve it — it routes around it, and the objection returns during signature as an unexplained delay.

Momentum direction. Are things getting more concrete or less? Concrete looks like: new people joining calls, questions shifting from "what does it do" to "how would we roll it out," a security questionnaire arriving, someone asking about implementation timelines. Abstract looks like: the same questions re-asked, meetings rescheduled, the champion's language moving from "we" to "I." Direction beats absolute position — a deal that is 40% qualified and accelerating is a better push candidate than one that is 70% qualified and cooling.

The gates run in order for a reason. Authority is first because failing it invalidates everything downstream — a perfectly budgeted, objection-free deal with no approver contact is still unpushable. Budget is second because it is the most commonly assumed and least commonly verified. Objections are third because they are solvable, unlike the first two, which are structural.

The numbers that make each option pay

The push-versus-pause call is ultimately an allocation question: is another hour on this deal worth more than an hour on the next one? A few concrete frames make that tractable.

Cost of a carried deal. Take a rep on a $150K total package. Fully loaded with benefits, tooling, and management overhead, that is roughly $200K a year, or about $100 an hour against a 2,000-hour year. A deal in late stage typically consumes two to five hours a week — calls, prep, internal reviews, follow-up, forecast defense. Carry that deal for a quarter and you have spent 26 to 65 hours, or $2,600 to $6,500 of capacity, before any revenue exists. On a $40K ACV deal at a 30% real probability, expected value is $12,000. Spending $6,000 of rep time to chase it is a poor trade when the same hours could open two new opportunities. On a $400K deal at the same probability, the arithmetic inverts entirely and patience is obviously correct. Deal size should change your patience threshold by roughly an order of magnitude, and most teams apply the same follow-up cadence to a $20K deal and a $500K one.

Stage age as a signal. Every team should know its own median days-in-stage for won deals. If closed-won deals historically spend 18 days in "negotiation," a deal sitting there at day 60 is not a slow winner — it is statistically a different kind of deal. Once a record passes roughly two to three times the won-deal median for its stage, the honest move is either a decision-forcing conversation or a downgrade. Carrying it at full probability is a forecast error, not optimism.

Engagement decay. Response latency is the most underrated leading indicator available, and it costs nothing to track. A prospect who answered in four hours during evaluation and now takes four days has not gotten busier; the deal has fallen down their priority list. A useful rule: if reply time has tripled from its baseline over three consecutive exchanges, treat the deal as cooling regardless of what the last call sounded like. Stakeholder count moving the wrong way — three people on calls, then two, then one — is the same signal in a different register.

The expiring-term math. Discounts get used as push mechanisms far too casually. A 10% discount on a $100K deal costs $10,000 of margin, and if it recurs annually across a three-year term, the real cost is closer to $30,000 in contract value. That is worth spending only if the discount genuinely changes the decision date — which it does when the prospect has a real internal deadline, and does not when they simply have not decided. A better exchange asks for something in return: a longer term, a case study commitment, a faster payment schedule, a reference call. Trading value for value preserves your price integrity; giving value for speed teaches buyers to wait you out, and that lesson spreads across accounts in the same industry faster than most sellers expect.

Pause economics. A structured pause is cheap if it is genuinely structured — a dated calendar hold and one substantive touch costs maybe 30 minutes. An unstructured pause costs far more, because it does not end. It generates weekly forecast conversations, monthly "any update?" emails, and a pipeline record that distorts every capacity plan built on top of it. The expensive thing is not waiting; it is waiting without a termination condition.

Concentration risk. One more number worth watching at the RevOps level: what share of a rep's forecast sits in deals older than the stage median? Above roughly a third, the rep is not managing a pipeline, they are managing a backlog, and the correct intervention is a forced-decision sweep rather than more coaching on any individual deal.

Running the play, step by step

Knowing which path to take is half of it. Executing either one badly produces the same outcome as choosing wrong.

Executing a push. Set it up before you make it. A push that arrives unannounced feels like pressure; a push the prospect helped design feels like a plan. Two or three calls before you intend to close, build the sequence out loud: "Walk me through what happens between agreeing in principle and a signed contract on your side — who touches it, how long does each step take?" You now have a mutual timeline the prospect authored, which means the eventual push references their commitment rather than your quota.

When you push, be explicit and single-threaded. One ask, one date, one owner. "I'd like to get this signed by the 20th so implementation starts before your fiscal close — can we agree to that, or is there something in the way?" That phrasing does real work: it names a date, gives a reason grounded in *their* interest, and explicitly invites the objection. The invitation matters more than the deadline. A push that only accepts yes gets polite deferrals; a push that makes "here's what's blocking us" an equally acceptable answer gets truth.

If the answer is no, do not immediately discount. Ask what would need to be true. Price is the objection people give when they do not want to explain the real one, and dropping price in response to a fake objection resolves nothing while costing margin.

Executing a pause. Three components, all non-optional. First, name the blocker in writing — "you need the security review complete, which your team estimated at two weeks." Written blockers are testable; vague ones are not. Second, put a real calendar invite on a real date with a real agenda, accepted by both sides before the call ends. A pause without a booked meeting is an abandonment. Third, define what changes at that meeting: either the blocker is cleared and you move to close, or it is not and you reassess. Two consecutive pauses with no new information is a qualify-out, and saying that out loud early — "if this is still stuck in July, I'd rather we both stop spending time on it" — is disarming rather than aggressive. It signals you value their time, and it frequently produces the real blocker on the spot.

Between the pause and the re-engagement, send one thing of genuine value with no ask attached. Something that helps them make the internal case: a comparable implementation, a rollout plan, a one-page summary the champion can forward. The goal is to arm the champion, not to remind the prospect you exist.

Where RevOps owns this. Individual judgment does not scale, so the operations layer should make the right call the easy one. Require a next-step date on every open opportunity past discovery, and expose a report of records that lack one — that single field, enforced, eliminates most silent drift. Publish stage-age benchmarks from your own closed-won history so "this is taking too long" becomes a number instead of an argument. Add a required close-reason picklist that separates "lost to competitor" from "no decision" from "no budget," because those three demand completely different fixes upstream and collapsing them hides the actual problem. Build a stalled-deal view that keys on next-step date passing rather than on last-activity date, since a rep logging a "sent follow-up email" task keeps a dead deal looking alive indefinitely.

Upstream effects worth noticing. Chronic push-versus-pause ambiguity is usually a qualification defect wearing a closing costume. If reps repeatedly reach late stage without economic-buyer contact, the entry criteria for that stage are wrong, not the reps. Tightening a single gate — no opportunity advances past a defined stage without a named, contacted approver — cuts late-stage stalls more than any closing technique. The same logic applies downstream: deals pushed hard and closed with heavy discounts tend to churn at higher rates and expand less, because the buyer never fully bought. Pairing win rate with first-year retention by close-reason tells you whether your pushing is producing revenue or producing renewals problems for someone else, and that pairing is one of the higher-leverage reports a RevOps function can build.

Adjacent scenarios that follow the same logic. Renewals invert the default — silence from an existing customer close to a renewal date is far more dangerous than silence from a new prospect, because the clock runs against you automatically, so bias hard toward forcing the conversation early. Expansion deals inside a happy account usually deserve more patience, since the relationship absorbs the wait and the budget cycle genuinely governs the timing. Small transactional deals should be pushed far earlier than instinct suggests: below roughly $15–20K ACV, the deal cannot support a long consultative cycle, and the fastest path to a real answer is the correct one. And partner-sourced deals need the authority gate applied to the *partner's* access, not yours — a partner who cannot get you in front of the approver is not a channel, they are a referral.

Related questions

What if the champion insists they can sign it themselves?

Verify rather than accept. Ask what their approval limit is and who signs contracts at that value. Champions frequently overestimate their authority in good faith. If the number checks out, treat them as the economic buyer; if it does not, you have just found the missing stakeholder without accusing anyone.

Does an expiring discount ever work?

It works when the prospect has a real reason to move by that date and the discount removes a genuine obstacle. It fails, and damages credibility, when it substitutes for a decision they have not made. Never extend an expired deadline without changing the terms — extending it for free proves the deadline was theater.

How many times can you pause the same deal?

Twice, generally. After a second pause with no new information — no new stakeholder, no cleared blocker, no changed timeline — the pattern is telling you something the prospect will not say directly. Move it to a long-cycle nurture and reclaim the forecast slot rather than carrying it at full probability.

Is "let me think about it" a no?

Usually it is an unstated objection. The useful response asks what specifically they want to think through. A prospect with a real consideration will name it; one who is deflecting will stay vague. That distinction, not the phrase itself, is the signal worth reading.

Should the manager make this call instead of the rep?

The rep should make it, with the manager auditing the pattern rather than individual deals. If a rep systematically pushes too early or never at all, that is a coaching conversation about tendencies. Overriding deal-by-deal removes the feedback loop the rep needs to calibrate.

FAQ

How do you push without damaging the relationship?

Push toward a decision, not toward a yes. The phrasing that preserves relationships makes "no" and "here's the blocker" fully acceptable answers alongside "yes." Sellers damage relationships when they push repeatedly after receiving an answer, or when the urgency is transparently theirs rather than the buyer's. One clear, well-reasoned ask with a stated rationale almost never costs goodwill — most buyers appreciate the directness.

What is the single strongest signal that a deal is ready to close?

The prospect starts asking implementation questions unprompted — onboarding sequencing, who administers it, what the first 30 days look like. That shift indicates they have mentally moved past evaluation into planning. It is a stronger indicator than verbal enthusiasm, because it reveals where their attention actually is rather than what they think you want to hear.

How long should a structured pause last?

Match it to the blocker, not to a default cadence. A security review that takes three weeks gets a three-week pause. A monthly budget meeting gets a pause to the day after that meeting. Arbitrary intervals like "two weeks" signal that you are following a process rather than tracking their situation — and prospects notice when a follow-up lands on a date that means nothing to them.

What do you do when the economic buyer will not take a meeting?

Treat it as diagnostic information rather than a scheduling problem. An approver who will not spend twenty minutes on a purchase they are supposedly about to authorize is telling you the priority is lower than your champion believes. Ask the champion directly what it would take, and if the answer is "they just trust me," verify the approval limit before forecasting the deal.

Should the forecast category change when you decide to pause?

Yes — that is most of the point. A deal you have chosen to pause is not committed, and leaving it in commit to avoid an awkward pipeline review is how forecasts lose credibility. Moving it down is the honest reflection of the decision you just made, and doing it promptly protects the number more than defending it does.

How does this change for very short sales cycles?

Compress everything and bias toward pushing. When a deal is meant to close in under 30 days, a pause of any length is a meaningful share of the cycle, and the authority and budget gates usually resolve in one or two conversations. In transactional motions, the fastest route to a definitive answer is nearly always the right one — ambiguity costs more than a lost deal.

Sources

• Gartner — B2B Buying Journey
• Harvard Business Review — Sales
• MIT Sloan Management Review
• McKinsey — Growth, Marketing & Sales insights
• Salesforce — Sales resources
• HubSpot — Sales Blog
• SaaStr
• Forrester — Sales research

Related on PULSE

• [What question should I ask a high-performing rep to push them toward advanced negotiation skills?](/knowledge/cg0831)
• [How do you decide which reps to coach first?](/knowledge/cg0007)
• [How do you coach a rep to talk less and listen more on calls?](/knowledge/cg0122)
• [How do you coach reps to book more meetings from cold outreach?](/knowledge/cg0027)
• [Can you give an example of a reflective question that helps a salesperson realize they are over-engineering solutions?](/knowledge/cg0862)
• [How do you give async coaching feedback that lands?](/knowledge/cg0185)