Win/Loss Analysis for Competitive Replacement Deals

A greenfield deal closes when the buyer believes the problem is real. A replacement deal closes when the buyer believes the switching cost is worth paying. Those are not the same interview, the same scorecard, or the same battle card — and most win/loss programs treat them as if they were.

2.4x

If your win/loss debrief asks "what made you choose us?" and stops there, you're getting greenfield answers from replacement buyers. They'll tell you about features. The actual decision was about three other things: the political cost of admitting the incumbent failed, the migration risk, and whether their internal champion could survive the project if it went sideways.

This guide is the version we use with clients running structured replacement-deal reviews. Two hours per interview, six interviews per quarter, one rewrite of the displacement battle card. The cost is real. So is the conversion lift on the next ten deals against the same incumbent.

Replacement deals are political projects with a software bill attached.

Why the standard win/loss script fails on replacement deals

Most win/loss templates were designed for evaluation deals — buyer has a budget, no incumbent, three vendors on the shortlist. The questions ("what was your top criterion?", "who else did you consider?") map cleanly to that shape. Replacement deals break the assumptions in three places.

The buyer rarely admits they're replacing. Half the time the deal is coded as "new logo" in your CRM because the prospect didn't volunteer that they're ripping out a competitor. They want leverage in the procurement conversation, and "we're evaluating options" sounds less desperate than "we've already decided the incumbent has to go." If your interviewer doesn't probe for the incumbent, the entire frame is wrong.

The decision criteria are stratified. There's the surface criteria (the RFP, the scorecard, the demo rubric) and the survival criteria (will my boss blame me if migration takes nine months instead of three). The surface answers go in the deck. The survival answers decide the deal. A standard interview captures the first set.

The timeline is non-linear. Greenfield deals progress through stages. Replacement deals sit dormant for six to fourteen months while the buyer builds internal consensus, then close in three weeks once the political window opens. If you ask "when did you start evaluating?" you'll get the three-week answer and miss the fourteen months of context that explains why they picked you.

The five-question reframe

The replacement interview is not a longer version of the greenfield interview. It's a different one. We've narrowed it to five anchor questions that, in our client work, surface roughly 80% of the actionable signal.

The replacement-deal interview anchors

The fifth question is the one most teams skip. It's awkward to ask — buyers don't love admitting their org had cold feet. But the answer is the most valuable artifact in the entire interview, because it tells your sales team exactly which stakeholder to pre-empt on the next deal against the same incumbent.

When to run the interview

The window matters. Too early and the buyer is still in honeymoon mode and won't tell you what scared them. Too late and the buyer's narrative has solidified — they've told the story of the deal so many times internally that the rough edges are sanded off.

The week 6–10 window for wins is non-obvious. Sales teams want to interview at week one because the rep has rapport. But week-one buyers are in love with you. Week-eight buyers have hit the first migration speed bump and can articulate, with specificity, what they wish they'd known before signing. That specificity is the entire point.

What to code, beyond the standard taxonomy

Standard win/loss codebooks have categories like "product fit," "price," "relationship," "timing." Useful, but insufficient for replacement deals. Add four replacement-specific codes to your taxonomy.

The right side of that table is where replacement deals live. If your CRM and your interview transcripts don't capture those four dimensions, your win/loss program is generating greenfield insights and applying them to a different kind of deal.

The five steps

C

We were running win/loss for two years before we segmented replacement from greenfield. The minute we did, the loss reasons separated cleanly. Greenfield losses were about price and feature gaps. Replacement losses were almost entirely about migration risk and champion exposure. We had been writing the wrong battle cards.

The signal you're looking for in the data

After three or four quarters of structured interviews, patterns emerge. The patterns worth acting on are usually narrower than teams expect.

These proportions vary by category, but the shape is consistent across the SaaS replacement deals we audit: migration risk and timing dominate, product capability is third or fourth, and price is rarely decisive on its own. If your battle cards lead with capability comparisons, they're optimized for a battle that decides 14% of the outcome.

What changes in the battle card

The replacement battle card is not the greenfield battle card with a "switching from [Competitor]?" header bolted on. It's a different document.

The difference is structural. A greenfield buyer is convincing their org that the problem is worth solving. A replacement buyer is convincing their org that the cure is not worse than the disease. The card has to answer the second question.

What to do Monday

Pull the last twenty closed deals from your CRM. Tag each one greenfield or replacement. If the split is roughly even and your win/loss program treats them identically, you have a quarter of work to do. Start with two interviews — one win, one loss, both against the same incumbent — using the five-anchor script. Compare the transcripts to the most recent battle card you have for that competitor. The gap between what the buyers actually said and what the card actually claims is the size of the rewrite.