Win/loss analysis · 14 min read · Updated 2 Aug 2026
Win-Back Analysis Template (Free Customer Win-Back)
A blank win-back analysis you can fill in today, plus the guidance for what belongs in each field. This covers customers who left after buying, usually for a named competitor, which is a different exercise from win/loss analysis of deals you never closed.
Copy pastes straight into Google Sheets or Excel with the columns intact. Downloads are free with a work email.
The win-back analysis template
This is exactly what you get when you copy or download. Blank fields are yours to fill in; each table ships with one example row to show the pattern, which you delete.
Analysis scope
Fill this in first. One period and one clearly stated definition of lost, or the numbers will not be comparable next time.
- Period coverede.g. accounts churned between 1 Jan and 30 Jun 2026
- How we define lostNon-renewal, cancellation, or downgrade below a stated threshold
- Accounts in scopeHow many, and how they were selected
- Who ran the analysisNamed, and whether they spoke to the churned customers
- The decision this informse.g. whether to fund a win-back campaign this quarter
- Owner and next reviewOne named owner, and when this gets repeated
1. Accounts lost and where they went
First row is an example, delete it. One row per account. The destination column is the one teams guess at, so mark how you know.
| Account | Segment and size | ARR at churn | Date lost | Where they went | How we know |
|---|---|---|---|---|---|
| ExampleNorthwind Freight | Mid-market, 60 seats | 34k | 14 Mar 2026 | A named competitor | Confirmed in the exit call |
2. Why they actually left
First row is an example, delete it. Two columns for a reason, because the stated one and the real one differ more often than not.
| Account | Stated reason | Underlying reason | Evidence for the underlying reason | Was it in our control? |
|---|---|---|---|---|
| ExampleNorthwind Freight | Too expensive | Seven stakeholders needed read access and every one cost a seat | Raised twice in QBRs, and in the exit call | Yes, it is a packaging decision |
3. Patterns across the losses
First row is an example, delete it. Group the reasons and count them. One angry customer is an anecdote; four with the same reason is a roadmap item.
| Pattern | Accounts affected | ARR involved | Competitor most often involved | Confidence |
|---|---|---|---|---|
| ExampleRead-only stakeholders cost a full seat | 4 of 9 | 112k | The same competitor in 3 of the 4 | High, stated independently by all four |
4. What has changed since they left
First row is an example, delete it. This table decides whether a win-back is honest. With nothing in it, you are asking them to choose the same thing again.
| Issue that caused the loss | Status now | Shipped or changed on | Evidence a returning customer would accept |
|---|---|---|---|
| ExampleRead-only stakeholders cost a full seat | Fixed, viewer role added at no cost | 12 Jun 2026 | They can see it on the public pricing page |
5. Which accounts are worth approaching
First row is an example, delete it. Score each, then act only on the top tier. Approaching everyone is how a win-back programme becomes a nuisance.
| Account | Is their reason fixed? | Contract timing at the new vendor | Relationship still warm? | Verdict |
|---|---|---|---|---|
| ExampleNorthwind Freight | Yes, fixed in June | Renewal due Mar 2027, so approach Dec 2026 | Yes, their ops lead still replies | Approach, highest priority |
6. The approach, account by account
First row is an example, delete it. Name who reaches out and what you will not offer. The second is what stops win-backs turning into discounting.
| Account | Who reaches out | The opening | What we offer | What we do not offer |
|---|---|---|---|---|
| ExampleNorthwind Freight | Their original AE, not a campaign email | The specific thing that made them leave is fixed, here it is | Migration support and a short pilot | A discount below our published floor |
7. Win-back economics
First row is an example, delete it. Your own figures, measured. Published win-back rates come from consumer marketing and will not describe your business.
| Metric | Our figure | How it was measured | What it tells us |
|---|---|---|---|
| ExampleWin-back rate, last 4 attempts | 1 of 4 | Counted from accounts approached, not accounts contacted | Too small a sample to plan from yet |
8. Decisions, owners and dates
First row is an example, delete it. Three to five rows. Separate what fixes the cause from what pursues the individual accounts.
| Finding | What we will do | Owner | By when | How we will know it worked |
|---|---|---|---|---|
| ExampleFour of nine losses share one packaging cause | Confirm the viewer role covers it and close the gap in messaging | Maya R., Product Marketing | 12 Sep | The reason stops appearing in new churn |
How to fill in your win-back analysis
How to scope a win-back analysis
State the period and the definition of lost before anything else, because both determine whether next quarter's numbers mean anything next to this quarter's. Teams frequently discover halfway through that they have mixed non-renewals, mid-term cancellations and heavy downgrades into one set, which makes the win-back rate uninterpretable. Pick a definition, write it down, and use the same one every time even when a different one would flatter the period.
Period covered
A stated range, usually two or four quarters. Shorter than a quarter gives too few accounts to see patterns; longer than a year and the earliest losses left for reasons that no longer exist, which distorts the fix list.
How we define lost
Non-renewal, mid-term cancellation, or a downgrade below a threshold you name. Downgrades are the contested case. Include them if a downgrade means they moved most of their usage elsewhere, since that is a partial defection and behaves like one.
Accounts in scope
How many and how selected. If you filtered to accounts above a revenue line, say so, because the small accounts you excluded often churn for different reasons and their absence changes the pattern table.
Who ran the analysis
Named, and record whether they actually spoke to the churned customers. An analysis built only from CRM close reasons is a record of what your own team believed, which is a different and much less reliable thing than what the customer decided.
The decision this informs
Usually one of two: whether to fund a win-back campaign, or what to fix so this stops happening. These need different emphasis, and an analysis serving both without saying so tends to serve neither.
Owner and next review
One named owner and a repeat date, typically half-yearly. The comparison between two win-back analyses is where you see whether your fixes worked, which no single run can tell you.
How to record lost accounts in a win-back analysis
One row per account, and the column that gets guessed at is where they went. Teams assume a departing customer moved to the competitor they think about most, and the assumption then propagates into the pattern table and out into strategy. Mark how you know for every row. An account that simply stopped needing the category, or that built something internally, is a completely different finding from one that switched to a named rival.
Account, segment and size
Segment matters because win-back economics differ sharply by size. A 60-seat mid-market account is worth a named person making a call; a 5-seat account is worth an email at most, and mixing them produces an approach plan nobody can execute.
ARR at churn
The value at the point they left, not their peak. Accounts that shrank for two quarters before leaving are a different pattern from ones that left at full value, and the shrinkage is usually the earlier and more actionable signal.
Date lost
Actual date, because timing drives everything downstream. It sets when their new contract comes up for renewal, which is the only moment a win-back approach has real leverage.
Where they went
A named competitor, an internal build, a different category, or nowhere. That last one is common and under-recorded: customers who stopped doing the job at all are telling you something about the category rather than about your product.
How we know
Exit call, their public announcement, a job posting, their own case study, or an inference. Label inferences as inferences. This single column prevents most of the wrong conclusions this artifact produces.
How to find the real reason in a win-back analysis
Two columns for the reason, because the stated one and the underlying one differ more often than not. Price is the reason most often stated and least often true on its own: a customer getting clear value rarely leaves over a percentage, while one who is not will describe the bill as the problem. The underlying reason is what you fix, and it is only reachable by asking the customer rather than the account manager.
Stated reason
In their words, as given. Record it even when you think it is wrong, since the gap between the stated and underlying reasons is itself a finding about how well your team was reading the account.
Underlying reason
What actually drove it, with the specifics: "seven stakeholders needed read access and every one cost a seat" rather than "pricing". A reason at that level of detail is fixable; a category label is not.
Evidence for the underlying reason
Where it came from and when. Ideally the customer said it directly in an exit conversation. Second best is a documented pattern from earlier reviews. Weakest is the account manager's interpretation, which is systematically biased toward causes outside their own control.
Was it in our control?
Yes, no, or partly. Losses from an acquisition, a budget collapse or a strategy change are genuinely outside your control and should be marked so, because leaving them in inflates the fixable pile and demoralises the people reading it.
Ask the customer, not the account team
The most important habit in this artifact. Exit interviews get far higher response rates than people expect, especially when the request is framed as learning rather than as a save attempt, and comes from someone who was not the account owner.
How to find patterns in a win-back analysis
Group the underlying reasons and count them. This is the step that converts a set of individually sad stories into something a company can act on. One departing customer with a strong opinion is an anecdote, and organisations routinely reorganise their roadmap around exactly one. Four accounts leaving for the same underlying reason, worth a stated amount of revenue, is a different class of evidence and deserves a different response.
Pattern
Phrased as the specific cause, not the category: "read-only stakeholders cost a full seat", not "pricing". A pattern at category level cannot be fixed because it does not name anything in particular.
Accounts affected
A count against the total, as in 4 of 9. The denominator matters and gets dropped constantly. Four accounts out of nine is a dominant pattern; four out of ninety is a niche one, and the two justify very different investment.
ARR involved
Total the revenue behind each pattern. This is what makes the case for a fix, and it frequently reorders the list, since the loudest pattern in an internal discussion is often not the most valuable one.
Competitor most often involved
Where the pattern also concentrates around one competitor, you have found something specific about their positioning that is working. That is a competitive finding as much as a retention one, and it belongs in your battlecard as well as here.
Confidence
High, medium or low with the reason. "Stated independently by all four" is strong. A pattern assembled by interpreting four vague exit notes is weak, and should be marked so before it becomes a roadmap commitment.
How to record what has changed in a win-back analysis
This table decides whether a win-back attempt is honest. With nothing in it, the approach amounts to asking a customer to choose the same thing they already rejected, which does not work and costs you the relationship a second time. The strongest win-back opening is narrow and specific: the exact thing that made you leave is fixed, here is where you can verify it, would you like to see it.
Issue that caused the loss
Carry each one across from the patterns table so the connection is explicit. Issues appearing here without appearing there are things you fixed for other reasons, which is fine, but they are not win-back material.
Status now
Fixed, partly fixed, on the roadmap, or not changing. Be honest about the last two. A partly fixed issue can support an approach if you are precise about what changed; a roadmap item cannot, because customers who left over a gap have already been told about roadmaps.
Shipped or changed on
The actual date, which also tells you whether enough time has passed. A fix shipped last week has no customers using it yet, so an approach based on it is a promise rather than a demonstration.
Evidence a returning customer would accept
Something they can verify independently: a public pricing page, documentation, a trial they can run themselves. Your own claim that the problem is solved is the weakest possible evidence for the one audience that already had reason to doubt it.
If nothing has changed, do not run the campaign
The most useful conclusion this template can produce is that a win-back is not yet justified. Fix the cause first. Approaching a churned customer with nothing new burns the relationship you would need later, and it is the reason most win-back programmes fail quietly.
How to decide which accounts are worth approaching
Score every account and act only on the top tier. The instinct is to contact everyone who left, which converts a targeted programme into a mass email that reads as desperate and produces almost nothing. Three factors decide whether an approach can work: whether their reason is genuinely fixed, whether the timing gives them a moment to switch, and whether anyone on their side will still take the call.
Is their reason fixed?
Yes, partly, or no. This is close to a gate. An account whose reason has not changed should not be approached at all, whatever their revenue was, because there is nothing to say that they have not already heard.
Contract timing at the new vendor
The single most underrated factor. A customer six months into a two-year contract cannot move regardless of how well the conversation goes. Work out when their renewal falls and approach roughly three months before it, which usually means doing nothing for a year and then acting deliberately.
Relationship still warm?
Does anyone on their side still reply, and did they leave on reasonable terms? Accounts that left angry after a support failure need a different approach and considerably more time than accounts that left over a specific gap.
Verdict
Approach now, approach at a stated date, or do not approach. The dated option is the most common correct answer and the one teams skip, because it requires the discipline to write down a date twelve months out and then honour it.
Weight by what they were worth, not by how they left
The account that departed most vocally is not automatically the most valuable to recover. Score the revenue and the fit against your current ideal customer profile, since a poor-fit account you win back tends to churn a second time.
How to plan the approach in a win-back analysis
Name who reaches out and what you will not offer. The first matters because a win-back is a relationship conversation and a marketing automation sequence signals immediately that nobody remembers them. The second matters because win-back campaigns drift toward discounting faster than any other sales motion, and the research on that is not encouraging: recovering a customer on a deep discount tends to produce a low-value second relationship.
Who reaches out
A named person with prior history where possible, usually the original account executive or their manager. If the relationship ended badly, someone senior who was not involved is a better choice than the person associated with the failure.
The opening
Specific and short: the thing that made you leave is fixed, here is where to see it. Openings that lead with a new release, a rebrand or an offer read as a campaign. The one thing a returning customer needs to hear is that you understood why they left.
What we offer
Usually migration help, a short pilot, or a genuine commercial concession tied to the original problem. The offer should reduce the effort of returning rather than simply reduce the price, since effort is what actually stops them.
What we do not offer
Write the floor down before anyone makes a call. Thomas, Blattberg and Fox's 2004 study in the Journal of Marketing Research found that the optimal strategy in their setting was a low reacquisition price followed by higher prices once the customer had returned, which is worth knowing precisely because it is so easy to do the first half and never manage the second.
Do not approach through a mass campaign
Win-back email blasts to everyone who ever churned are the version of this that most companies run, and they perform badly while quietly damaging the accounts that were genuinely recoverable. Five well-chosen conversations beat five hundred emails.
How to record win-back economics
Measure your own figures rather than importing published ones. The frequently quoted rates for selling to lapsed customers come from consumer marketing and describe a very different purchase from a multi-stakeholder B2B renewal. Your own numbers will be a small sample at first, and saying so in the table is more useful than borrowing a confident-looking figure that describes somebody else's business.
Win-back rate
Accounts recovered divided by accounts approached, not divided by accounts contacted or by everyone who churned. Define the denominator in the table, because this is the metric most easily made to look good by changing what it is measured against.
Cost per win-back
Time and any commercial concession, compared against what new acquisition costs you. Win-backs are frequently cheaper, which is the strongest argument for running the programme, but only when the approach is targeted rather than broadcast.
Second-tenure value and retention
What recovered accounts are worth, and whether they stay. This is the number that decides whether the programme is worth repeating, and recovering accounts that churn again within a year is a failure however good the recovery rate looks.
Time from loss to recovery
Usually far longer than teams expect, since it is governed by the new vendor's contract term rather than by your persuasiveness. Recording it sets realistic expectations for the next cycle and stops the programme being judged too early.
Treat published benchmarks with care
The widely cited figure that firms have a 20 to 40 percent probability of selling to a lost customer traces to Marketing Metrics by Farris, Bendle, Pfeifer and Reibstein, popularised through Griffin and Lowenstein's Customer Winback in 2001. It is a reasonable rule of thumb and it is not a B2B software benchmark. Measure yours.
How to fill in the decisions section of your win-back analysis
Three to five rows, separating what fixes the cause from what pursues the individual accounts. These are genuinely different pieces of work with different owners and timescales, and running them together is how the fix quietly disappears: the sales team pursues the accounts, the pattern that caused the losses stays in place, and the same analysis produces the same findings six months later.
Finding
From the pattern table with its count attached: "four of nine losses share one packaging cause". Findings without counts get argued with; findings with counts and revenue attached get acted on.
What we will do
Split explicitly. Fixing the cause belongs to product or pricing. Approaching the accounts belongs to sales, usually with a date months out. Writing both makes it visible when only one of them happens.
Owner
Named. Win-back programmes are unusually prone to having no owner because they sit between retention, sales and product, and an unowned programme reliably becomes an email sequence that somebody set up once.
By when
Real dates, and expect the approach dates to be far out. A row reading "approach in December, three months before their renewal" is a correct and useful entry, and it needs to survive in a system that will actually surface it.
How we will know it worked
For fixes, the reason stops appearing in new churn, which is the more important measure. For approaches, a recovered account that is still there a year later. Both are observable, and neither is the number of emails sent.
Sourcing and upkeep: keeping a win-back analysis honest
These rules apply to every section above. This artifact fails in a specific and predictable way: it is built from internal records rather than from customers, which produces a comfortable account of why people left, and it then justifies a mass campaign that damages the relationships worth keeping. Every habit below defends against one half of that failure.
Ask the customer, not the account team
Exit conversations are the entire evidence base. Close reasons recorded in a CRM by the person who lost the account are systematically biased toward causes outside their control, and price appears far more often than it deserves to.
Record where they went, and mark inferences
Assuming the destination is how a win-back analysis quietly becomes a story about the competitor the team already worries about. Customers who left the category entirely, or built internally, are telling you something different and more important.
Fix the cause before running the campaign
If nothing has changed, the right output is a fix list rather than an outreach list. Approaching churned customers with nothing new burns the relationship you would need at their next renewal.
Time the approach to their renewal, not to your quarter
A customer mid-contract cannot move. This usually means the correct action is a dated reminder several months out, which requires more discipline than a campaign and works considerably better.
Write the discount floor down in advance
Win-back conversations drift toward price faster than any other sales motion. Deciding the floor before anyone dials is what keeps a recovered account worth recovering.
Measure your own rates, not published ones
Published win-back statistics come largely from consumer marketing. Use them for orientation and never for planning. A stated small sample is more honest than a borrowed large one.
Repeat it and compare
Half-yearly. The comparison shows whether your fixes stopped the pattern, which is the only reliable evidence that the analysis was worth running. Keep old versions rather than overwriting.
A win-back analysis example
You lead competitive intelligence at Pipedrive. Nine mid-market accounts churned in the first half of 2026 and several went to HubSpot Sales Hub, so you work out which are genuinely recoverable. This is that analysis, filled in.
Published pricing and packaging verified 2 August 2026, from the companies’ own pages rather than third-party round-ups, which frequently conflate annual and monthly prices. Pricing changes without notice, so re-check before quoting any of it.
Sections marked illustrative are invented for this example. Win rates, deal counts, discounting behaviour, customer quotes, owners and internal dates are not published by HubSpot, Pipedrive or anyone else, so those rows are a plausible fictional scenario rather than reported fact, and should not be read as claims about how either company performs or negotiates. Everything else comes from the two pricing pages linked below, read on the date shown.
Analysis scopeIllustrative
| Field | Example entry |
|---|---|
| Period covered | Accounts churned between 1 Jan and 30 Jun 2026 |
| How we define lost | Non-renewal or cancellation. Downgrades excluded, counted separately |
| Accounts in scope | 9 mid-market accounts above 20k ARR, all of them, not a sample |
| Who ran the analysis | Tom A., Competitive Intelligence. Spoke to 6 of the 9 directly |
| The decision this informs | Whether to fund a win-back push in Q4, and what to fix first |
| Owner and next review | Tom A., next run 1 Feb 2027 |
1. Accounts lost and where they wentIllustrative
| Account | Segment and size | ARR at churn | Date lost | Where they went | How we know |
|---|---|---|---|---|---|
| Northwind Freight | Mid-market, 60 seats | 34k | 14 Mar 2026 | HubSpot Sales Hub | Confirmed in the exit call |
| Calder & Sons | Mid-market, 45 seats | 26k | 2 Feb 2026 | HubSpot Sales Hub | Confirmed in the exit call |
| Peakline Services | Mid-market, 30 seats | 21k | 30 Apr 2026 | HubSpot Sales Hub | Inferred from a public job posting, not confirmed |
| Ashgrove Media | Mid-market, 25 seats | 18k | 12 Jun 2026 | Back to spreadsheets | Confirmed in the exit call |
| Vantor Group | Mid-market, 80 seats | 44k | 1 Jan 2026 | Nowhere, acquired and absorbed into the buyer's system | Public acquisition announcement |
2. Why they actually leftIllustrative
| Account | Stated reason | Underlying reason | Evidence for the underlying reason | Was it in our control? |
|---|---|---|---|---|
| Northwind Freight | Too expensive | Seven stakeholders needed read access and every one consumed a paid seat | Raised in two QBRs and again in the exit call | Yes, it is a packaging decision |
| Calder & Sons | Consolidating vendors | Same read-access problem, plus marketing already used another suite | Exit call, and their own stated consolidation programme | Partly, the suite breadth is not something we compete on |
| Peakline Services | No reason given | Unknown, they declined an exit conversation | None, this row is honestly empty | Unknown |
| Ashgrove Media | Team shrank, no longer needed it | Headcount fell from 25 to 9 and the tool stopped being worth any price | Exit call, and their public announcements | No |
| Vantor Group | Acquired | Absorbed into the acquirer's existing system | Public acquisition announcement | No |
3. Patterns across the lossesIllustrative
| Pattern | Accounts affected | ARR involved | Competitor most often involved | Confidence |
|---|---|---|---|---|
| Read-only stakeholders consume a full paid seat | 2 of 9 confirmed, likely 3 | 60k confirmed, 81k if Peakline is included | HubSpot in both confirmed cases | Medium, two independent confirmations and one inference |
| Losses genuinely outside our control | 3 of 9 | 83k | None | High, all three externally verifiable |
| Wanted a broader suite covering marketing | 1 of 9 | 26k | HubSpot | Low, a single account and a secondary reason |
4. What has changed since they leftIllustrative
| Issue that caused the loss | Status now | Shipped or changed on | Evidence a returning customer would accept |
|---|---|---|---|
| Read-only stakeholders consume a full paid seat | Not changed. Still our position, and the gap that decided these losses | No date | Nothing we could show them, which settles the question for now |
| Reporting across two teams needed manual consolidation | Partly fixed, cross-team pipeline view shipped | 18 May 2026 | They can see it in a self-serve trial |
| Wanted a broader suite covering marketing | Not changing, and deliberately so | No date | None, we compete as a sales tool |
5. Which accounts are worth approachingIllustrative
| Account | Is their reason fixed? | Contract timing at the new vendor | Relationship still warm? | Verdict |
|---|---|---|---|---|
| Northwind Freight | No, the seat gap is unchanged | Renewal likely Mar 2027 | Yes, their ops lead still replies | Do not approach yet. Revisit only if the seat gap closes |
| Calder & Sons | No | Renewal likely Feb 2027 | Cooled, no contact since January | Do not approach |
| Peakline Services | Unknown, we never learned the reason | Unknown | Unknown | Do not approach. Try once more for an exit conversation instead |
| Ashgrove Media | Not applicable, they shrank | Not applicable | Yes, friendly departure | Do not approach now. Revisit if they grow past 20 people |
| Vantor Group | Not applicable, acquired | Not applicable | Not applicable | Closed, no win-back possible |
6. The approach, account by accountIllustrative
| Account | Who reaches out | The opening | What we offer | What we do not offer |
|---|---|---|---|---|
| Northwind Freight | Dana K., their original AE, if and when the gap closes | The seat structure that made you leave has changed, here is the pricing page | Migration support and a 30-day pilot on their real data | Any discount below our published floor, since the gap is the issue rather than the price |
| Ashgrove Media | Dana K., a light check-in only | No pitch, just a note when they next post a sales hire | Nothing yet | Any offer at all, they do not need the product at their current size |
7. Win-back economicsIllustrative
| Metric | Our figure | How it was measured | What it tells us |
|---|---|---|---|
| Accounts approachable this cycle | 0 of 9 | Scored against fixed reason, timing and relationship | The honest output of this analysis is a fix list, not a campaign |
| Losses attributable to one fixable cause | 2 confirmed, 60k | Counted from exit calls only, inferences excluded | The clearest revenue case we have for revisiting seat packaging |
| Losses outside our control | 3 of 9, 83k | Acquisition and headcount reduction, externally verifiable | A third of the churn was never recoverable and should not be counted against retention work |
| Exit conversation response rate | 6 of 9 | Requests sent by someone other than the account owner | Higher than expected, and the reason this analysis has any evidence at all |
8. Decisions, owners and datesIllustrative
| Finding | What we will do | Owner | By when | How we will know it worked |
|---|---|---|---|---|
| Two confirmed losses worth 60k share one packaging cause we have not addressed | Put read-only seat pricing on the pricing agenda with the churn evidence attached | Elena V., CEO, with Maya R. presenting | 12 Sep 2026 | A documented decision either way, rather than the topic recurring |
| No account is currently worth approaching | Run no win-back campaign this quarter and record why | Tom A., Competitive Intelligence | 15 Aug 2026 | No outreach goes out, and the reasoning survives to the next review |
| One loss has no reason recorded at all | One further exit-conversation request to Peakline, from someone senior | Dana K., Sales | 29 Aug 2026 | Either a reason is recorded or the row is closed as unknown |
| A third of churn was outside our control and is being counted against retention | Report controllable and uncontrollable churn separately from now on | Tom A., Competitive Intelligence | 1 Feb 2027 | Next review separates the two without being asked |
How to roll out your win-back analysis
- 1Copy or download the blank analysis. Use Copy to paste it straight into Google Sheets or Excel with the columns intact, or download the CSV, Notion or PDF version.
- 2Define lost before you count anything. Non-renewal, cancellation or downgrade below a threshold. Use the same definition every time, even when another one would flatter the period.
- 3Delete the example rows. Each table ships with one example row so the pattern is obvious. Remove it before you circulate the analysis.
- 4Record where each account went, and how you know. A named competitor, an internal build, a different category, or nowhere. Mark inferences as inferences rather than letting them harden.
- 5Ask the customers, not the account team. Stated and underlying reasons go in separate columns, because price is the reason most often stated and least often true on its own.
- 6Count the patterns and total the revenue behind each. One departing customer is an anecdote. Four with the same underlying cause, worth a stated amount, is a roadmap item.
- 7Only approach accounts whose reason is genuinely fixed. Then time the approach to their new contract's renewal rather than to your quarter, which usually means waiting and writing the date down.
- 8Write the discount floor before anyone makes a call. Win-back conversations drift toward price faster than any other sales motion, and a recovered account bought too cheaply rarely stays.
Win-back analysis FAQ
What is a win-back analysis?
A win-back analysis examines customers who left after buying: where they went, why they actually left as opposed to what they said, what patterns connect the losses, whether anything has changed since, which accounts are genuinely recoverable, and what the economics of recovering them look like. Its defining feature is that it starts after the relationship ended, which makes it a different exercise from win/loss analysis of deals you never closed. The most valuable output is often a fix list rather than an outreach list.
What is customer winback?
Customer winback is the practice of reinitiating a relationship with customers who have lapsed or defected. It became a defined area of customer relationship management largely through Griffin and Lowenstein's book Customer Winback in 2001 and Thomas, Blattberg and Fox's paper Recapturing Lost Customers in the Journal of Marketing Research in 2004, both of which argued that retention had absorbed nearly all the attention while reacquisition was left to ad hoc effort. Winback and win-back are the same word; both spellings are in common use.
What is a good winback rate?
There is no credible universal benchmark for B2B software, and the figure most often quoted is not one. The widely repeated claim that firms have a 20 to 40 percent probability of selling to a lost customer, against 60 to 70 percent for active customers and 5 to 20 percent for new prospects, traces to Marketing Metrics by Farris, Bendle, Pfeifer and Reibstein, popularised through Griffin and Lowenstein. It is a reasonable orientation and it describes consumer purchasing rather than multi-stakeholder B2B renewals. Measure your own, define the denominator as accounts approached, and expect a small sample.
How do you win back a customer?
Fix the thing that made them leave, wait for a moment when they can actually move, then have one specific conversation. All three are necessary. Approaching a churned customer before the cause is fixed asks them to choose the same thing again. Approaching them mid-contract at their new vendor means the answer is no regardless of the conversation. And the opening that works is narrow: the specific thing that made you leave has changed, here is where you can verify it. Not a new release, not a rebrand, not an offer.
How do you win back unhappy customers?
Unhappy departures need more time and a different person. A customer who left over a specific gap can be approached by their original account executive once the gap closes. A customer who left angry, usually after a support or reliability failure, associates that person with the failure, so the approach should come from someone senior who was not involved, and it should start with acknowledgement rather than with a proposal. The realistic timescale is a year or more, and attempting it early tends to confirm their decision rather than reopen it.
Is a 20% returning customer rate good?
It depends entirely on what the 20 percent is measured against, which is why this number travels badly. Twenty percent of accounts you deliberately approached returning is a strong result for B2B software. Twenty percent of everyone who ever churned returning would be extraordinary and probably indicates a measurement error. In ecommerce, returning-customer rate usually means repeat purchasers within a period, which is a different metric again. Define your denominator in the analysis, because this is the figure most easily improved by changing what it is divided by.
What is the 80-20 rule in customer retention?
The Pareto principle applied to customers: roughly 80 percent of revenue comes from 20 percent of customers, so retention and win-back effort should concentrate there. The underlying observation is real and the ratio is a rule of thumb rather than a law, with the actual split varying widely by business. For win-back specifically it is a useful corrective, because the instinct is to contact everyone who left, when the correct action is usually to identify the few accounts with meaningful revenue and a recoverable reason and to ignore the rest.
What is the rule of 7 in B2B?
The rule of 7 is a marketing heuristic holding that a buyer needs around seven exposures to a brand before acting. It originates in advertising folklore rather than in research, and no study establishes seven as a threshold. In B2B it is sometimes cited to justify persistent outreach cadences. For win-back it is actively unhelpful: repeated contact with a customer who left, before their situation has changed, reads as pursuit rather than persuasion. Timing against their renewal matters far more than frequency.
What are the 4 types of customers?
Several incompatible four-type models circulate and none is canonical. Some split by behaviour into loyal, discount, impulse and need-based, which comes from retail. Others split by relationship stage into prospects, new, active and lapsed, which is closer to useful for win-back. In a win-back analysis the distinction that actually matters is different again and worth building yourself: customers who left for a reason you can fix, customers who left for a reason you cannot, customers who left the category entirely, and customers who disappeared without telling you why.
What are the 3 C's of customer satisfaction?
No canonical version exists and the lists disagree, with consistency, customer journey and completeness appearing in one common formulation and entirely different Cs in others. None traces to a founding study. The frameworks with real research behind them in this area are worth using instead: the Gaps Model of Service Quality from Parasuraman, Zeithaml and Berry in the Journal of Marketing in 1985, and the SERVQUAL instrument that followed it in 1988. Both are properly attributable, unlike most alliterative lists on this topic.
What are the 7 principles of customer success?
There is no standard set. Customer success as a discipline is young enough that its frameworks are largely vendor-authored, and the numbered lists in circulation are marketing artifacts from software companies selling into the category rather than established practice. That is not a reason to dismiss them, only a reason not to treat them as authoritative. For win-back specifically, the practically useful principle is narrower and evidenced: churn reasons recorded by the account owner are systematically less accurate than reasons given by the customer.
What is the difference between win-back analysis and win/loss analysis?
Where in the lifecycle they look. Win/loss analysis examines deals: why you won or lost opportunities in the sales process, including deals you never closed. Win-back analysis examines customers: people who bought, used the product, and then left. The reasons differ systematically. Deals are lost on capability gaps, price and evaluation dynamics, while customers leave over things only visible after months of use, such as support, packaging that bites as they grow, and gradual displacement by another tool. Both are worth running, and our win/loss report template covers the first.
Should you discount to win a customer back?
Carefully, and with the floor decided before anyone makes a call. Thomas, Blattberg and Fox studied exactly this question in the Journal of Marketing Research in 2004 and found that the optimal approach in their setting was a low reacquisition price followed by higher prices once the customer had returned. The practical difficulty is that companies execute the first half enthusiastically and the second half rarely, which produces recovered accounts that are permanently unprofitable. Where the loss was caused by a gap rather than by price, reducing the effort of returning usually works better than reducing the price.
How long should you wait before trying to win a customer back?
Long enough that the cause is genuinely fixed and their new contract is approaching renewal, which is usually nine to eighteen months in B2B software. The timing is set by their contract rather than by your readiness, and this is the factor teams most often ignore. A customer six months into a two-year agreement cannot move whatever you say. The practical implication is uncomfortable: the correct action for most recently churned accounts is to write a date roughly three months before their renewal and do nothing until then.
Which lost customers are worth trying to win back?
Three conditions, and all three should hold. Their reason for leaving is genuinely fixed, verifiably and by something they can check themselves. Their timing allows a move, meaning their contract with the new vendor is near renewal. And someone on their side will still take the call. Beyond those, weight by what the account was worth and by fit against your current ideal customer profile, because a poor-fit account recovered on effort tends to churn a second time and costs more the second time around.
What is second lifetime value?
Second lifetime value is what a recovered customer is worth across their second relationship with you, a concept popularised by Griffin and Lowenstein in Customer Winback. It matters because it is the number that decides whether a win-back programme is worth running at all. A high recovery rate producing accounts that churn again within a year is not a success, and recovery rate alone conceals that entirely. Measure how long recovered accounts stay and what they spend, not just how many came back.
What phrases calm angry customers?
This question belongs to customer service rather than to win-back analysis, and it is worth separating them because the search results mix the two heavily. De-escalating a live support interaction is about acknowledgement and immediacy. A win-back conversation happens months or years after the relationship ended, when nobody is angry any more and the question is whether anything has actually changed. Scripted empathy phrases are counterproductive there: a former customer who left over a specific gap wants evidence that the gap closed, not a rapport technique.
How do you find out where a churned customer went?
Ask in the exit conversation, which is the most reliable route and gets a better response rate than most teams expect, particularly when the request comes from someone other than the account owner and is framed as learning rather than as a save attempt. Failing that, public signals help: their job postings naming a tool, their own case studies, a vendor's published customer list, or their integrations. Mark inferences as inferences in the analysis, because assuming the destination is how a win-back analysis quietly turns into a story about whichever competitor the team already worries about.
What is an example of a win-back analysis?
Scope: nine mid-market accounts above 20k ARR that churned in the first half of 2026, with lost defined as non-renewal or cancellation, and exit conversations completed with six of the nine. Destinations: three confirmed to one named competitor, one back to spreadsheets, one absorbed by an acquirer, one inferred from a job posting and marked as unconfirmed. Patterns: two confirmed losses worth 60k share a single packaging cause, three losses worth 83k were outside our control, and one wanted a broader suite. What has changed: the packaging cause has not been addressed, so there is nothing a returning customer could verify. Scoring: zero accounts are approachable this cycle, because the reason is unfixed in the recoverable cases and the uncontrollable losses are closed. Decision: run no campaign, put the packaging evidence in front of the pricing decision instead, and report controllable and uncontrollable churn separately from now on. The honest output was a fix list, not an outreach list.
What are the most common mistakes in a win-back analysis?
Six recur. Building it from CRM close reasons rather than from exit conversations, which records what your team believed rather than what the customer decided. Assuming where accounts went instead of confirming it. Counting uncontrollable losses like acquisitions against retention performance, which distorts every conclusion. Launching a mass campaign before the cause is fixed, which burns the relationships that were genuinely recoverable. Timing outreach to your quarter rather than to their renewal. And measuring recovery rate without measuring whether recovered accounts stay, which makes an expensive failure look like a success.
Win-back analysis built on live competitor data
Flares tracks what competitors ship and change, so you know what a lost customer would be returning from.
Discover Flares14-day free trial · 30-second setup