The job
Sixty deals closed. Forty-three won. Seventeen lost. The team knows why they lost three. The other fourteen are a mystery. The patterns that run across all forty-three wins go unseen.
Win/loss synthesis reads every closed deal (the discovery notes, the calls, the emails, the objections, the close reason or disqualification reason). It clusters them. Returns the patterns: “Of your wins, 70% had clear trigger event discussed in discovery. Of losses, 40% had unclear timeline.” That’s feedback the team can act on.
Plated well: the Chef reads the synthesis. Recognizes the pattern. Updates one recipe. Next quarter, trigger-event discovery gets sharper. The win rate lifts.
The recipe
All seven ingredients still apply. The leverage on this dish is Feedback Loop (Ingredient #7). Win/loss is the system’s way of getting smarter every month.
Training sets what you want measured (trigger events, timelines, decision-makers, objections?). Examples show the station what patterns matter at your company. Feedback Loop is the load-bearing ingredient: the synthesis surfaces a pattern. The Chef confirms it. The team updates one recipe (discovery questions, objection responses, proposal structure). The station learns. The cycle repeats. Output Over Process says: tell the station to surface “the three patterns that matter most,” not every correlation it finds.
How to build it
-
Define what you measure. For each won deal: did you find a trigger event? Was timeline clear? Were you clear on decision-maker?
-
For each lost deal: what was the disqualification reason? Too expensive? Timeline not clear? Competitive loss? Scope mismatch? Get honest on each one.
-
Collect 60 recent closed deals. 40+ wins, 15+ losses. That’s your sample.
-
Tell the station what patterns matter. “Surface the three factors that are present in 60%+ of wins but missing in losses.”
-
Set the guardrails. The station never invents a pattern. If it’s there, show it with data. “70% of wins had X” is a real claim. “Winners probably also X” is speculation.
-
Run the first synthesis manually. Read the 60 deals. What do you see? What’s different between the wins and losses? Compare to what the station finds. Did it catch your patterns?
-
The Chef reviews the synthesis. The station surfaces patterns. The Chef says which are real, which are noise, which matter enough to change a recipe.
What breaks it
-
Incomplete deal data. The station reads CRM notes that are thin. “Won.” No discovery notes. No timeline data. No decision-maker clarity. The synthesis is worthless. First, get your deal data clean. Then run synthesis.
-
The Chef reads the synthesis but doesn’t act. The synthesis says “70% of losses had unclear budget.” The Chef acknowledges it. Nobody updates the discovery questions. By next month, the pattern hasn’t changed. The synthesis was an exercise, not feedback. Act on the patterns.
-
Pattern is real but not actionable. The synthesis says “customers in the Northeast region close 15% faster.” True. But the sales team can’t change the customer’s location. The pattern exists but the recipe can’t change. Focus on patterns you can act on.
-
Feedback loop stops. The synthesis ran once. The Chef made a change. By month three, the synthesis never runs again. The change is invisible. The system doesn’t improve because the loop is broken. Make synthesis monthly. Track the result of each change.
When it’s working
By month two, the team has updated one recipe based on win/loss synthesis. By month three, win rate has shifted. By month six, you can point to three changes the team made because synthesis showed the pattern.
The signal: when the Chef says “I want to know the pattern on X,” the station can surface it in an hour instead of the team spending a day analyzing deals.
Monday Move
Collect your last 30 closed deals. Have the station identify the three strongest patterns: present in most wins, absent in losses. Read the synthesis. Which patterns do you recognize? Which are new? Which matter enough to change how you discover, propose, or object-handle?
Dish 9 of 10 on the Sales Station. Build-note leverage: Feedback Loop (Ingredient #7). Chef reviews every synthesis cycle.