A CRM can record what happened to a deal, but it was never built to record why a competitor won.
That’s a different job that requires capturing the specific claim a competitor made, close to the moment it happened, and checking it against what else the team is seeing. CRMs don’t do that.
Four Deals With Full CRM Records Provide Zero Insight
A record in Salesforce typically includes a deal’s stage history, close date, deal amount, and activity count. Many organizations also maintain a loss reason field with a small set of preset options such as “price”, “timing”, “no decision”, “feature gap”, and “went dark”. That’s the complete official record of what may have been a six-month evaluation, and each field answers a version of the same question: what happened, and when, while none of them really answer why.
For example, let’s say that there were four deals that lost to the same competitor last quarter, and all four were tagged as “price.” That tells a RevOps leader nothing about whether the price gap was big or small, based on scope or value, or whether the same exact objection surfaced in all four calls. The dropdown closes the case before anyone asks any real questions.
The CRM Is Doing Its Job, It’s Just Not the Job You Need Done
In another example, a competitor tells the prospect their platform can’t support multi-region data residency and the prospect relays that information to your sales rep. This may actually be the most valuable piece of information the deal produced, since it opens a huge vulnerability against this competitor in any future comparable deal. Yet there’s usually no CRM field designed to capture this type of information.
At best, that claim lands in an open-text “Notes” field nobody reviews. The instinctive fix is to request more dropdown options:
- A “competitor claim” category
- A “data residency” subfield
- Whatever would have captured this specific loss
That addresses the wrong layer. The CRM is functioning exactly as designed. It exists to track pipeline mechanics, support forecasting, and give visibility into rep activity. Capturing why a competitor won a specific deal is a different function, one that requires structured detail collected close to the moment it happened, then checked against what else the team is seeing elsewhere. A system built for pipeline reporting was never designed to do both.
This is why adding fields will never close the gap. A new dropdown option only captures a claim if the rep remembers it, decides it’s worth logging, and enters it correctly before the next deal takes over their attention.
Most of the time none of that happens, not because the rep is careless, but because nothing in the workflow prompts it. The claim that cost or won the deal was said once, on a call, and then it was gone.
The CRM continues to function as a scoreboard. It shows a deal was lost, but it was never built to explain why.
Track the Claim, Not Just the Outcome
The fix is a capture layer that runs alongside the CRM instead of inside it.
FieldForce runs short, AI-led interviews across the field organization on a recurring cadence, asking reps what competitors actually claimed in the deals they just ran, while the details are still fresh. Sedulo’s research team validates what comes back and builds it into a structured competitor record connected to your CRM or shared drive, so the claim that determined the deal stays accessible instead of disappearing with the call.
The CRM keeps doing the job it was built for.
This is one piece of a larger pattern in how competitive knowledge moves, or fails to move, through a sales organization. For the full diagnostic and what actually fixes it, read Why Are We Losing Deals? The Real Reason B2B Sales Teams Lose Winnable Accounts (And How to Fix It)