The patterns sales already knows
but isn’t writing down.
Paste deal notes — won, lost, no-decision. Stratridge extracts objection patterns, positioning gaps, and the specific competitive moves that moved the deal — and writes the learning back into Strategic Context.
Most win/loss programs die after the first quarter because the analysis takes longer than the next quota. This one runs in five minutes per deal.
Pro workspaces. Notes can be pasted, uploaded as text, or pulled from your CRM via export.
“We lost a deal we should have won.”
You had the better product. The reps had relationships. Pricing was within range. And you still lost — to a competitor whose pitch your team has heard nine times and answered eight.
The pattern is in the notes. It’s never just one thing: a positioning gap that lets the rebuttal land, an objection no one armed the rep for, a comparison page that doesn’t exist. Every loss carries the receipts.
Win/Loss Review reads the notes the way a veteran sales coach would — pattern-first, blame-free — and ships the lesson back to the field before the next deal arrives.
Five extractions. One report.
Each pasted deal note returns five structured findings. Run ten deals and the patterns surface themselves; run thirty and you have a real coaching document.
Outcome and primary cause
Won, lost, no-decision, slipped — and the single biggest factor, in the rep’s own words, distilled. Not blame; signal.
Objection patterns
The specific buyer objections that landed, who raised them, when in the cycle, and whether the rep had a calibrated answer.
Positioning gap
Where the buyer’s mental model didn’t match your pitch. This is the leading indicator that something on your site or in your messaging is misfiring.
Competitor moves
Whose pitch dominated, what specific claims they made, what proof they brought. Feeds Battle Cards directly.
Recommended actions
Three specific actions per deal: a copy fix, a battle-card update, a process change. Prioritized by recurrence across your full deal corpus.
Memory write-back
Findings auto-ingest into Strategic Context tagged by competitor, segment, and stage. The Analyst can then answer ‘why are we losing in mid-market to Competitor B?’ with evidence.
Sample deal review.
Buyer didn’t believe our governance story. Rep flagged this in week two; no comparison page existed to forward. Competitor sent a one-pager; deal moved their direction within 48h.
3rd loss in 90 days where governance was the tipped factor. All against Competitor A. All in mid-market (>500 employees).
(1) Build /vs/competitor-a/governance page within 2 weeks. (2) Update Battle Card ‘Their gaps’ block with row-level-security beta status. (3) Brief AEs on the new governance positioning at next sales standup.
Tagged: competitor=competitor-a, segment=mid-market, stage=evaluation, cause=governance-trust. Surfaces in the Analyst when anyone asks about Competitor A losses.
Short answers.
Two to ten paragraphs is the sweet spot. We extract more from a focused note than from a 5,000-word transcript.
Notes are enough. Optional: paste a call transcript and we’ll extract the same fields with quote-level evidence.
Yes. Mark a deal as ‘exclude from learning’ if the loss was outside your control. The extraction still runs but doesn’t feed the pattern aggregation.
Sales hates dashboards that feel like grading. The output here is positioning fixes and battle-card updates — actions for marketing and product, not metrics on the rep.
Related capabilities.
Battle Cards
New objections from the field auto-flow into the right competitor card’s objection-handler block.
See Battle Cards →Positioning Audit
Recurring positioning gaps point at audit lenses scoring low. Run the audit; fix at the source.
Run a free audit →Strategic Context
Every review writes back as memory entries. Patterns accumulate across quarters, not just within one.
See Strategic Context →The pattern is in the notes. We just have to read them.
Run a free Positioning Audit to set the pillar baseline; once you have a workspace, every deal note ships through Win/Loss Review and writes back to Strategic Context.