What's the right way to handle "we're going with the incumbent" when you've spent 4 months on a deal in 2027?
Curated byKory White · Fractional CRO · Maryland
Quality
Certified
Accept the decision cleanly, then convert four months of access into intelligence: ask for a 20-minute debrief, capture the incumbent's renewal date and the specific gaps you found, and schedule a re-entry roughly 60–90 days before that renewal. Never discount to reverse it. Losses to incumbents are timing losses far more often than capability losses.
What it is and why it matters
"We're going with the incumbent" is the most common way a long enterprise cycle ends, and it is structurally different from every other loss. It is not a "no" to your product. It is a "not enough" against a switching cost the buyer already knows how to live with. The incumbent has installed integrations, trained users, absorbed budget into a line item nobody re-argues each year, and — critically — a set of internal people whose credibility is tied to that original decision. You spent four months arguing capability. They spent three years accumulating inertia.
The reason this matters for RevOps and not just for the individual rep is that this loss shape produces bad data if you let it. Most CRMs collapse it into a single closed-lost reason picklist value: "Competitor." That value is nearly useless. It tells you nothing about whether the deal was winnable, whether the buyer was using you to negotiate a better renewal, or whether the incumbent's contract expires in four months or thirty-four. Three quarters of "lost to competitor" records in a typical pipeline are actually four or five distinct loss types wearing the same label, and you cannot fix a mix you cannot see.
Consider what four months actually bought you. You have probably had six to twelve meetings. You know who signs, who blocks, what their fiscal year does, which two workflows genuinely hurt, and roughly what they pay today. That is a discovery asset most reps would spend a full quarter and thousands of dollars in SDR time to rebuild from cold. If you close the opportunity, mark it lost, and move on, you have effectively deleted that asset. The right way to handle this moment is to treat the closed-lost record as the beginning of a documented, dated, re-entry motion rather than the end of a sales cycle.
There is a second-order reason too. How you behave in the ninety seconds after hearing the news is the single cheapest brand impression your company will make on that account. Buyers talk. The person who ran this evaluation will run another one somewhere else within a few years — B2B buyer tenure in a given seat is often shorter than the contract they just signed. A rep who argues, sulks, or immediately escalates to a manager for a "save" gets remembered as a vendor to avoid. A rep who says "understood, I think that's a defensible call given where you are, can I ask two questions so I don't waste your time next year" gets remembered as someone worth calling. That asymmetry costs nothing to capture.
The adjacent version of this scenario is worth naming, because the playbook transfers: losing to "we're building it internally," losing to "no decision," and losing to a procurement-mandated renewal are all inertia losses. The buyer chose the path with the lowest perceived organizational risk. The response pattern — accept, debrief, date the re-entry, instrument the pattern — is the same in all four cases. Only the trigger event you are waiting for changes.
The step-by-step process
Run this as a fixed sequence, not as improvisation, because the emotional temperature right after a loss is exactly when reps improvise badly.
Hour 0 — the live response. If you get the news on a call, do not negotiate. Say some version of: "Thanks for telling me directly instead of letting it go quiet. That's more than most people do." Then ask one question and stop talking: "Was this a capability call or a switching-cost call?" That single question sorts the loss into the two buckets that matter. Capability means you have a product gap to route to product management. Switching cost means you had the better product and lost anyway, which is a very different fix. Do not ask for a price re-open. Do not offer one.
Hour 0–24 — the written close. Send a short email the same day. Three sentences of acknowledgment, one line offering the artifact you already built — the gap summary, the ROI model, the integration map — with no strings attached, and one ask for a 20-minute debrief in the next two weeks. Attaching the work product is the move most reps skip. It costs you nothing, it is already written, and it lands on the desk of a buyer who is about to go negotiate a renewal with the incumbent. You have just made yourself useful in a conversation you are not in.
Day 3–14 — the debrief call. Frame it as process improvement, not re-litigation, and say so explicitly in the invite: "Not a pitch, and I won't try to reopen it." Ask five questions, in this order, and record it if they consent:
- What was the deciding factor, in their words, not yours?
- Who in the room was hardest to convince, and what convinced them?
- What would have had to be true for the answer to be different?
- When does the incumbent agreement actually come up for renewal, and is it auto-renewing?
- What does the incumbent have to fail at for this to be re-opened?
Question four is the one that pays. An auto-renewing agreement with a 90-day notice window means your real re-entry date is not "in a year" — it is a specific week, roughly four months before the anniversary, and it is knowable today.
Week 2 — the internal capture. Write the record while it is fresh. This is where most organizations leak the value. The fields that matter are not the ones in a default CRM layout: incumbent name, incumbent contract end date, notice period, auto-renew yes/no, deciding factor verbatim, named champion, named blocker, product gaps cited, and the trigger event you are watching for. Nine fields. If your closed-lost form has twenty-two required picklists and none of these, that is a RevOps problem to fix this quarter, not an individual rep problem.
Month 1–11 — the low-cost nurture. Two to four touches a year, each carrying something the buyer can use whether or not they ever buy from you. A benchmark, a relevant regulatory change, an introduction. No "just checking in." The cost of keeping an account warm this way is perhaps thirty minutes a quarter.
Re-entry — the dated return. Reach out four to six months before the contract end date you captured, and open with the specific thing they told you. "You mentioned last year that the reporting handoff was the part that hurt. Curious whether that got better." That opener is unfakeable by any competitor who was not in the room.
Costs, timelines, and typical ranges
Be honest about the economics, because this determines how much effort the post-loss motion deserves.
A four-month mid-market cycle typically consumes somewhere between forty and eighty hours of AE time, plus solutions-engineering hours for demos and any proof of concept, plus whatever demand-gen spend created the opportunity. At loaded rep costs common in B2B software, that is a real number — often several thousand dollars of direct sell cost against a single opportunity, before you count the opportunity cost of the deals that rep did not work. The post-loss sequence described above adds roughly three to five hours in the first month and about two hours per year afterward. That is a rounding error against what you already spent, which is the entire argument for doing it.
On timelines: enterprise software agreements commonly run one to three years, with auto-renewal clauses and notice windows of thirty to ninety days. The practical consequence is that your re-entry window opens earlier than intuition suggests. If they signed a two-year deal in September, the evaluation for the next cycle realistically starts eighteen to twenty months later — and the notice deadline may be sooner than that. Marking the account "revisit in a year" is usually wrong by a quarter in one direction or the other. Use the date they gave you.
On probability: not every incumbent loss is recoverable, and pretending otherwise wastes territory. A rough triage that holds up in practice — treat these as judgment heuristics, not measured constants:
- Long tenure, no trigger event, satisfied users. Low recovery odds. Two touches a year, no more. Do not build a business case for an account that is not shopping.
- Short tenure with the incumbent, or the incumbent was itself acquired. Meaningfully higher odds. Vendor acquisitions reliably produce roadmap uncertainty, support degradation, and price increases within twelve to twenty-four months, and buyers who felt burned once are more willing to move.
- Your champion is still there and told you the truth in the debrief. Higher odds. A champion who explains the loss honestly is a champion who expects to talk to you again.
- You never met the economic buyer. Lower odds, and the diagnosis is on you. That is a single-threading failure to fix in your process, not an incumbent problem.
On the discount question, be unambiguous: dropping price after the decision is announced is close to strictly negative. It does not usually win the deal, because the decision was rarely about your price. It teaches the buyer that your list price is fiction, which poisons the next negotiation. And if it does work, you have bought a customer at a margin that makes them unprofitable to serve. If you genuinely had commercial room you never used, that is a deal-strategy failure from month two — a case for changing when you deploy concessions, not for deploying them after the whistle.
One more cost worth counting: the cost of *not* qualifying out. Deals that run four months and die to an incumbent are usually visible as high-risk by week six. A team that kills three such deals early instead of running them to completion recovers weeks of selling capacity per rep per quarter. The point of the post-loss debrief is partly to make next quarter's early-qualification calls sharper.
Where teams get it wrong
Arguing with the decision on the call. The instinct to fight is strong after four months, and it converts almost never. Worse, it changes what the buyer tells you in the debrief. People who feel they have to defend a choice stop giving you the real reasons and start giving you the safe ones.
Collapsing the loss into one CRM field. "Lost to competitor" tells your RevOps team nothing actionable. Without the incumbent's name, the renewal date, and the deciding factor in the buyer's own language, you cannot distinguish a product gap you should fix from a positioning problem you should fix from a market segment you should stop selling into. The single highest-leverage change most teams can make here is a closed-lost form that asks nine specific questions instead of one vague one.
Treating the debrief as a save attempt in disguise. Buyers detect this instantly, and it costs you both the intelligence and the relationship. If you promise not to pitch, do not pitch. Not at the end. Not as a "one quick thing."
Skipping the referral ask. A buyer who just told you no often has genuine goodwill and no way to express it. "Totally understood — do you know anyone else wrestling with this who'd be worth a conversation?" is a low-cost ask at a moment of maximum reciprocity. It is not guaranteed to produce anything, but it costs one sentence.
Waiting for the anniversary instead of the notice date. If the agreement auto-renews with a 60-day notice window, showing up thirty days before the anniversary means the renewal already happened silently. You need to be in the conversation before the window closes.
Never routing the product gap. If the deciding factor was a real missing capability, that belongs in front of product management with the account name, the deal size, and the exact requirement attached. One anecdote is noise. The same requirement appearing in eleven closed-lost records with a total pipeline value attached is a roadmap argument. This only works if the capture step in the process above is actually being done — which is why it lives in RevOps, not in individual rep discipline.
Letting a single loss rewrite the playbook. The opposite failure. One painful loss produces an overcorrection — a new required field, a new mandatory discovery question, a new stage gate — that adds friction to every deal to prevent one outcome. Wait for a pattern across several records before changing the process.
Blaming the rep for a structural loss. If the buyer had a three-year contract, deep integrations, and no trigger event, no amount of rep skill was closing that. Sales leaders who treat every incumbent loss as an execution failure train their teams to hide the truth in the CRM, which destroys the data quality the whole system depends on.
Decision framework: when to choose what
The judgment call after any incumbent loss is how much future investment the account deserves. Three tiers, and it is worth being disciplined about which one an account lands in, because the failure mode is treating every warm-ish account as tier one and burning a quarter's capacity on nostalgia.
Tier one — dated re-entry. Reserved for accounts where you captured a specific renewal date, still have a live champion, and identified a concrete gap the incumbent has not closed. These get a calendared re-entry, quarterly value touches, and a named owner. Expect a handful of these per rep per year — not dozens.
Tier two — trigger-watch. No confirmed date or no strong champion, but the account fits your ideal profile. These get monitoring rather than outreach: leadership changes on LinkedIn, funding events, an acquisition of the incumbent, a public incident. Two touches a year. If a trigger fires, promote to tier one immediately.
Tier three — release. Genuinely happy with the incumbent, no trigger, poor profile fit, or the relationship is personal and unwinnable. Log the record properly for pattern analysis and stop spending time. Releasing accounts honestly is what makes tier one credible.
The upstream lesson matters more than the downstream one. Most of what determines a four-month incumbent loss was decided in weeks two through six, when the questions that would have surfaced the switching-cost problem went unasked. Three questions, asked early, do most of the work: what would replacing the current system actually cost you in migration and retraining; if we matched their price exactly, what else would need to change for you to switch; and who besides you has to agree. A buyer who cannot answer any of these is not running an evaluation — they are running a benchmarking exercise, and you are the benchmark. That is not automatically a reason to walk, but it is a reason to work the deal at one hour a week instead of ten.
Related questions
Should I ever ask them to reconsider?
Once, and only with new information — a capability that shipped after their evaluation, or a materially different commercial structure. Ask permission first: "If something changed on our side in the next sixty days, would you want to know?" A no closes it cleanly. A yes gives you a legitimate reason to return.
How do I know if I was used as a price lever?
Signals: no access to the economic buyer, urgency that spiked right before their renewal date, requests for formal pricing early with little technical evaluation, and a decision announced within days of the incumbent's deadline. One of these means little. Three together mean you were quoting for someone else's negotiation.
What if the buyer's relationship with the incumbent is personal?
Then the deal was likely decided before you arrived. Do not take it personally and do not escalate. Add a discovery question about existing vendor relationships and tenure so you catch it in week two next time, and reallocate the hours to a winnable account.
Does this change if we lost to "build it internally" instead?
The mechanics are nearly identical — it is still an inertia loss. The difference is the trigger you watch for: internal builds tend to fail at maintenance, not at v1. Re-entry usually opens twelve to twenty-four months later, when the engineer who built it changes teams.
Who should own the post-loss record — the rep or RevOps?
The rep captures within two weeks; RevOps owns the schema, the reminder, and the pattern analysis. If capture depends purely on rep discipline with no structure behind it, it will not happen consistently, and the aggregate data will be too sparse to act on.
FAQ
Is four months an unusually long cycle to lose?
No. For mid-market and enterprise deals, four months is a normal cycle length, and losing at the end of one is a routine outcome even for strong reps. The length is not the problem; the absence of an early switching-cost test usually is. What makes a four-month loss feel worse is sunk-cost bias, not an unusual failure.
Should I tell my manager immediately or after the debrief?
Immediately, with the forecast corrected the same day. Late-stage losses that surface after the quarter closes damage credibility far more than the loss itself. Bring the debrief plan along with the news so the conversation is about the recovery motion rather than about the miss.
What if they refuse the debrief call?
Send the five questions in an email instead and ask them to answer any two. Partial answers still give you the deciding factor and often the renewal timing. If they ignore that as well, log what you know, set a trigger-watch, and stop spending time.
Can I keep talking to my champion after we lose?
Yes, and you should — as a professional relationship, not a covert sales cycle. Share useful material occasionally, congratulate them on moves, and stay visible. If they change companies, you have a warm entry into a new account, which is frequently how these losses eventually pay off.
Does discounting ever make sense against an incumbent?
Only before the decision, and only when tied to something you get in return — a longer term, a case study, a faster start date. Unilateral post-decision discounting signals desperation, devalues your list price, and rarely reverses a switching-cost decision. If price was truly the deciding factor, that is a packaging problem to solve upstream.
How many of these losses are actually recoverable?
Fewer than optimistic pipeline reviews assume, and more than discouraged reps assume. The recoverable segment is concentrated: short incumbent tenure, an acquisition or leadership change, a live champion, or a documented gap the incumbent has not addressed. Sorting honestly into those buckets is worth more than working every lost account equally.
Sources
- Gartner — B2B buying behavior and vendor selection research: https://www.gartner.com/en/sales
- Harvard Business Review — sales and negotiation research: https://hbr.org/topic/sales
- MIT Sloan Management Review — organizational decision-making and switching behavior: https://sloanreview.mit.edu/
- McKinsey & Company — B2B growth and go-to-market insights: https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
- Salesforce — opportunity and pipeline management documentation: https://help.salesforce.com/
- HubSpot — sales process and CRM practice resources: https://blog.hubspot.com/sales
- Bain & Company — customer loyalty and retention research: https://www.bain.com/insights/topics/customer-strategy-and-marketing/
- Stanford Graduate School of Business — negotiation and decision research: https://www.gsb.stanford.edu/insights
Related on PULSE
- What's the right way to handle "we need to think about it" when the buyer ghosts you for 2 weeks after?
- What's the right way to do a follow-up after a demo when the buyer says "we'll get back to you"?
- How do I respond to 'we're going to build this internally'?
- How do you handle a deal where the buyer's procurement adds 12 redlines you've never seen before in week 11 of the cycle?
- How do you measure win rate against Palantir as incumbent in competitive enterprise RFPs?
- How do I roll out a 15% price increase without churning the base?
This page will be disappearing soon. Save it to your device for $1 — or read it free while it is here.
@Kory-White- · if Venmo asks, the last 4 of my number are 2012
This page is gone.
This one is off the shelf now. $1 keeps it on your phone for good — the whole page, pictures and diagrams included.
executive-alignmentHow do you get executive sponsors and C-suite buyers aligned on a multi-year contract when each renewal is uncertain in 2027?
save-play-timingWhen should a CSM initiate a save play for at-risk accounts in 2027?
objection-handlingWhat's the right way to handle "we need to think about it" when the buyer ghosts you for 2 weeks after in 2027?
objection-handlingHow do you coach reps through objection handling without accepting excuses in 2027?
discovery-callsHow do you handle a discovery call where the buyer brings 6 stakeholders and you only planned for 1 in 2027?
price-compressionHow do we overcome a prospect's price compression objection when they've already found a cheaper alternative in their RFP process in 2027?
working-interviewsHow do working interviews (sales simulations) separate role-players from closers in 2027?
battlecardsHow do we design competitive battlecards that actually change rep behavior in the field in 2027?
persona-playsWhat makes a persona-based play stick versus collect dust in your playbook library in 2027?
challenger-sellingHow do you use Challenger Selling principles to reframe procurement objections as growth opportunities instead of cost-cutting in 2027?