Fictional example: Northfield Software is an invented company, not a real customer
Executive summary
This quarter Northfield Software ran 14 win-loss interviews (6 won, 6 lost, 2 no-decision). The clearest pattern: five of the six losses faced “Rival A”, and four of those five interviews mentioned a new onboarding claim Rival A started making in the weeks before the deal closed. The CRM recorded three of those five losses as “price”; the buyers said something different. Action: update the Rival A battlecard with the onboarding objection and give sales a response before the next deal reaches that stage.
Ranked reasons we win
1. Faster time-to-value (mentioned in 5 of 6 won interviews)
Illustrative quote: “We were live in under two weeks. The other option quoted us six.”
2. A named technical contact during the trial (4 of 6)
Illustrative quote: “Having one person who actually knew our setup made the trial feel safe.”
3. Clearer pricing than Rival B (3 of 6)
Illustrative quote: “We could actually work out what we would pay next year. That mattered more than I expected.”
Ranked reasons we lose
1. A new onboarding claim from Rival A (4 of 6 lost interviews)
Illustrative quote: “Rival A said they would have a dedicated person for the first 90 days. That tipped it for us.”
2. Perceived feature gap on reporting (3 of 6)
Illustrative quote: “We needed the export to go straight into our BI tool, and that wasn’t there yet.”
3. Price, stated but secondary (2 of 6)
Illustrative quote: “Price came up, but honestly the onboarding thing mattered more.”
Per-competitor view
Rival A: faced in 7 deals, won 2, lost 5. Where they beat Northfield: the 90-day onboarding promise, introduced this quarter. Where Northfield beat them: integration depth and clearer pricing.
Rival B: faced in 4 deals, won 3, lost 1. Where they beat Northfield: a lower list price for small teams. Where Northfield beat them: reporting and a faster implementation.
CRM said vs buyer said
Kept narrow on purpose: only the deals where the two genuinely disagree, one stacked block per deal.
Deal 1142
CRM lost reason: Price
What the buyer actually said: “Price was a factor but what really decided it was the dedicated onboarding person Rival A offered.”
Deal 1158
CRM lost reason: Price
What the buyer actually said: “We needed the BI export and it wasn’t ready. That was the real blocker.”
Deal 1171
CRM lost reason: “No budget”
What the buyer actually said: “Budget existed. We just preferred Rival A’s onboarding story and didn’t say so directly to the rep.”
Matching a loss to a competitor move
The method: for every lost deal, put the interview date next to the dated competitor events you track over the same weeks (a pricing change, a release, a campaign). In the Northfield example, Rival A published its “90-day dedicated onboarding” page in week 1 of the quarter. Four of the five losses to Rival A had interview dates in weeks 3 to 9, all mentioning onboarding unprompted. A single loss in week 11 mentioned price only and had no onboarding mention, which is a weaker signal and was not counted toward the pattern.
A loss that lines up with a tracked competitor event in the weeks before it is a real signal worth acting on. A loss with no nearby event is more likely about your own pitch, product or process, and deserves a different kind of follow-up.
Actions
Sales: add a response to the onboarding objection to the Rival A battlecard; rehearse it before the next deal reaches evaluation.
Product: scope the BI export gap; it appeared in 3 of 6 losses and is specific enough to size.
Marketing: add a time-to-value proof point to outbound messaging aimed at Rival A competitive deals, since it is the top reason Northfield wins.
A copy-ready blank report template
The same structure, stripped of the fictional content, ready to fill in with your own interviews.
Get the sample report as a PDF
A clean PDF of the Northfield Software example above, formatted for sharing with your team.
Common questions
What should a win-loss report include?
An executive summary, ranked reasons for winning and losing with illustrative quotes, a per-competitor breakdown, a short table of where the CRM lost reason differs from what the buyer actually said, and concrete actions for sales, product and marketing. Skip anything that does not point to a decision.
How do I match a loss to a specific competitor move?
Put the interview date next to the dated competitor events you track over the same weeks: a pricing change, a release, a campaign. A loss that lines up with a competitor event in the weeks before it is a real signal; a loss with no nearby event is more likely about your own pitch or product.
Why does the CRM lost reason often differ from what the buyer says?
The CRM field is filled in quickly by the rep who just lost the deal, with the least incentive to dig past the comfortable answer. "Lost on price" is the easy entry. A structured interview usually finds the real driver was a missing feature, a trust gap, or a competitor message that landed, with price as the stated but not the real reason.
Is this report example a real company?
No. Northfield Software and its rivals, Rival A and Rival B, are a fictional example built to show the structure, not real companies or real quotes. Use the blank template below with your own interview data.
How often should a win-loss report run?
Monthly or quarterly, on a consistent sample, works better than one large report once a year. A steady cadence lets you see which patterns persist and which were one deal, and it keeps the per-competitor view current enough to feed battlecards.