Product →Examples →FAQ →All solutions →About →
Business problemsHow it worksRolesOrganizations
Scopeout for win-back

Bring back the users who left.

Who is worth winning back, why they left, and which product change or message brings them home. Scopeout runs the win-back loop and reports what it recovered.

Win-back · churned accounts worth recovering
Missing CSV import38 · $19k
Too expensive after trial24 · $9k
Switched to competitor15 · $8k
No longer needed8 · $2k
Fixable in product1 of 4 · start there

Win-back starts with why

Most reactivation is a discount email. Scopeout starts with the reason they left, fixes it where it can, and only then reaches out.

Rank who is worth winning back

Dormant and churned accounts scored on past value and the fixability of why they left.

Who is worth winning back
Past MRRweight 0.5
Reason fixability0.3
Recency0.2
Top of the list38 accounts · CSV import

Fix the reason first

If they left because of a product gap, the fix ships behind a flag before anyone is emailed.

Pull request #511 · csv-import
14 tests passed
Preview ready
Behind flag import_v1
Linkedchurn reason · 38 accounts
Merge

Then reach out, and measure

Win-back messages tested on return and reactivated revenue, with the reason for leaving in the copy.

Win-back · “CSV import is here” vs generic
generic · 4%names the fix · 17%+13 pts · $11k recovered

The same loop, your metrics.

The method does not change by business model. The evidence, the tests and the number that has to move do.

B2B SaaSrecovered MRR

Churned accounts scored on value and fixability, fix first, then win-back.

E-commercelapsed customers reordering

Why they stopped buying, replenishment and win-back offers measured on reorders.

Consumer appreactivated users

Dormant users by reason, product fixes shipped before the win-back push.

Marketplacereactivated sellers

Inactive sellers by reason, listing friction fixed, then outreach.

Built for win-back

Churn reasons · confirmed
Missing CSV import38
Price after trial24
Competitor15
No need8

Churn reasons, confirmed

Cancellation notes, tickets and replays clustered into reasons with evidence.

Win-back message · from the record
They hitno CSV import · Mar
What changedshipped in PR #511
Sent to38 accounts
Came back11 · $11k MRR

Messages that name the fix

Win-back copy written from the record: what they hit, what changed.

Recovered MRR · per month
AprMayJunJulAugSep$11k this month

Reactivated revenue

Recovered MRR per campaign, per reason, per segment.

Feeds retention
Reasonmissing import
Now watchedimport step in onboarding
Resultchurn −2 pts next cohort
Recordedrun #131

Learning for retention

Every win-back reason feeds the retention loop so fewer leave next time.

Start from a prompt.

Find

“Which churned accounts from the last six months are worth winning back, and why did they leave?”

Run this when my batch opens →
Fix

“The top churn reason is missing CSV import. Design and build it behind a flag, then draft the win-back message.”

Run this when my batch opens →
Review

“How much revenue did reactivation recover this quarter?”

Run this when my batch opens →

Questions, answered.

Does it email churned users on its own?

Only after approval. Messages are drafted from the record and sent through your tool once a person signs off.

What if the reason is price?

It says so, with the numbers, and proposes a packaging test rather than a discount by default.

How does it measure success?

Reactivated accounts and recovered revenue per campaign, against a control group.

Stop running the business. Start directing it.

Join the waitlist

Private beta. We onboard teams in small batches. Or contact us.