In brief
What does this guide cover?
Win-loss records can help demand generation identify the account conditions associated with buying, but only when teams validate and interpret the reasons first. This playbook walks through a six-step process: gather closed-deal evidence, confirm reasons with sales, translate repeated patterns into observable exegraphic signals, apply win and loss signals to campaigns, pass signal context to sales, and compare outcomes to refine the model. Its examples show how timing and fit signals can shape targeting without treating every lost deal as a bad-fit account.
Who this is for
For demand generation, sales operations, and product marketing teams that want to turn closed-won and closed-lost learning into more useful account targeting.
What you’ll take away
Ideas you can put to work
- Start with closed-won and closed-lost records and validate recorded reasons with sales before building campaigns around them.
- Translate deal reasons into account characteristics such as growth, technology change, leadership, operational readiness, and timing.
- Map repeated characteristics to observable signals including hiring, leadership changes, technology adoption, and expansion.
- Use win signals to prioritize accounts and loss signals to exclude, deprioritize, pause, or revisit accounts when circumstances change.
- Pass the signal and its meaning to sales in CRM fields, routing notes, or handoff alerts so outreach has relevant context.
- Compare signal-matched accounts with other accounts and revisit signals that are too broad, too late, or unrelated to wins.
Inside the guide
Collect and validate deal evidence
The playbook begins with closed-won and closed-lost opportunities from a defined segment. Useful fields include the recorded outcome reason, industry, company size, deal size, and notes; interview summaries can add context where available. The point is to use a consistent set of records and a focused segment so that patterns are easier to interpret and act on.
Recorded reasons should not be assumed to be complete or accurate. Review them with sales leaders or account executives and clarify what a label such as “no need identified” meant in the actual deal. The guide cites a comparison in which buyer-reported reasons often differed from CRM entries, underscoring the importance of validation. One deal may be an anecdote; repeated characteristics across wins are stronger candidates for a targeting signal.
Translate reasons into observable account signals
A win-loss reason describes what happened in a deal; the next step is to ask what was happening inside the account. The playbook groups explanations into growth or expansion, technology change, leadership and personnel, operational sophistication, and timing. For example, a need to support virtual care may correspond with new virtual nursing roles or clinic expansion, while a cloud migration may be visible through hiring or technology changes.
Those observable clues become exegraphic signals that can identify accounts with similar conditions before they enter an active buying cycle. The map distinguishes win signals, which can help prioritize accounts, from loss signals that may indicate exclusion or delay. Examples include an absent need trigger, a hiring freeze, an incumbent contract, or a build-in-house capability. A lost deal can reflect timing rather than permanent lack of fit.
Apply signals to campaigns and sales handoffs
Use standard firmographic filters as a starting audience, then apply win signals as a qualification layer. Apply loss signals deliberately: remove or deprioritize accounts where the conditions associated with poor fit are present, pause outreach during a freeze, or monitor for a future change. Align messaging with the specific change revealed by the signal, and reach accounts while that change is relevant.
The same signal-qualified audience can guide content, webinars, paid media, and outbound so that channel activity reaches the same buying groups. When an account engages, pass sales the reason it was selected. A CRM signal field, routing note, or handoff alert can state the observed change and how it relates to past wins. That context gives a rep a more relevant conversation starter than a generic activity notification.
Measure, refine, and repeat
Compare accounts that matched a win signal with those that did not, using the same measures for each group. The playbook lists campaign engagement, conversion to opportunity, win rate, sales-cycle length, and the share of losses marked “no need identified.” If the signal-matched group performs better, the team can expand the approach to another segment; if not, the signal may be too broad, mistimed, or unrelated to the true buying condition.
The quick-start sequence keeps the work practical: select a segment, validate common win and loss reasons, identify repeated account characteristics, map them to observable signals, build qualified and excluded audiences, attach context to handoffs, and review the results. The guide recommends revisiting the process regularly because markets change and signals that once predicted a win may lose relevance.
Good to know
Frequently asked questions
What data should a win-loss signal project start with?
The guide recommends closed-won and closed-lost opportunities for a defined segment, including outcome reasons, account details, deal size, and relevant notes.
Why validate CRM win-loss reasons?
Recorded reasons can be incomplete or differ from the buyer's explanation. Confirming them with sales helps prevent the team from building campaigns around misleading labels.
What is an exegraphic signal in this playbook?
It is observable evidence of an account characteristic linked to buying conditions, such as hiring, leadership change, technology adoption, or expansion.
Should every lost account be excluded?
No. The playbook notes that a loss may reflect timing rather than poor fit. Teams can pause, deprioritize, or revisit an account when a relevant signal appears.
How can sales use signal intelligence?
Include the observed signal and why it matters in the CRM record, routing notes, or handoff alert so reps can start with relevant account context.