Lifecycle and Email
Retention and win-back
The job here is specific: keep the customers you have, and define lapsed by your own data rather than by a default.
Retention and win-back: what it is and what it is not
Keep the customers you have, and define lapsed by your own data rather than by a default. In practice that means a purchase cycle analysis that defines lapsed for your category instead of inheriting ninety days, and then the harder half: replenishment timing for consumables, which is the highest-return automation most brands never build.
Why this work exists
It is the sort of work that never makes a slide, and shows up in every result that does.
Part of Lifecycle and Email, and the part where the diagnosis is usually most useful on its own.
The nearest piece of work to it is authenticating properly so the messages arrive at all. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
The sign it is working is that nothing surprising happens. Changes are noticed on the day they are made rather than in the next quarterly review.
The gap between that and where most accounts start is why this is scoped as retention and win-back rather than as a line inside something larger. Segmenting on behaviour, which you already have is the usual second step once it is in place.
When this is the right work
Start here if you recognise any of these:
- Repeat rate is falling and acquisition is covering it up
- Lapsed is defined as ninety days because that was the default
- Win-back means a bigger discount each time
If none of those is true, something else is probably the constraint, and the Lifecycle and Email overview maps the alternatives. The usual neighbours are retiring the addresses that are dragging everybody else towards spam and resisting the extra send that borrows revenue from next quarter.
What the work covers
The pieces of work inside it:
- A purchase cycle analysis that defines lapsed for your category instead of inheriting ninety days. Straightforward in principle; the detail is where it stops being quick.
- Replenishment timing for consumables, which is the highest-return automation most brands never build, with the evidence kept so the decision can be defended later.
- A win-back sequence with a real reason to return rather than an escalating discount, revisited rather than finished, because the inputs keep moving.
- List hygiene, because mailing the permanently gone damages deliverability for everybody else. Straightforward in principle; the detail is where it stops being quick.
How it runs
Three passes, each ending in something the client can check.
Deciding what not to do
A list of things deliberately left alone, with the reason for each. It saves the same conversation happening four times over the following year.
The second look
A fortnight after the first pass, the same ground gets covered again with fresh eyes. The second pass finds a different class of problem from the first.
Bringing in whoever owns the system
Developers, agency partners or whoever actually controls the platform get involved before recommendations are written, not after they are rejected.
What each part runs into
The specific resistance each part meets:
- A purchase cycle analysis that defines lapsed for your category instead of inheriting ninety days, and in Toronto the constraint on it is a measurement baseline that was never taken
- Replenishment timing for consumables, which is the highest-return automation most brands never build, harder in Jaipur because of a language mix the content has to match rather than assume
- A win-back sequence with a real reason to return rather than an escalating discount – in Gurugram, complicated by the fact that an enquiry path that runs through a messaging app rather than a form
- List hygiene, because mailing the permanently gone damages deliverability for everybody else, which in Hyderabad runs into a catchment smaller than the ambition on the website
The error worth naming
Escalating discounts. It teaches your best customers to lapse deliberately, which is an expensive lesson to deliver.
It is a cheap mistake to avoid and an expensive one to discover six months in.
How it is measured
Repeat purchase rate, reactivation rate, and revenue per recipient against a holdout. Agreed up front and reported every period, with the raw data available rather than only a summary.
It is worth tracking alongside one commercial number, so a technical win that sells nothing is visible as such.
What you end up with
At the end of the engagement there is a cycle-based definition of lapsed, a replenishment flow where it applies, and a win-back sequence with a holdout.
Comes with a date and a next review, so it ages visibly instead of quietly.
How it differs by sector
What this becomes in practice depends on who it is for:
- Marketplaces and platforms: Two sides to acquire, and a programmatic page set that can sink the whole domain. so this work has to account for that before anything else.
- Finance and fintech, where regulated claims, compliance review in the publishing path, and trust signals that have to be real. which moves this work earlier in the plan.
- In Real estate and property the binding constraint is that portals own the generic demand, so the win is locality authority and the specific listing.
The industry pages carry the rest of that detail. Marketplaces and platforms and Finance and fintech are the two where this piece of work most often decides the outcome.
Common questions
When is a customer actually lapsed?
At the point your own repurchase data says the probability of return drops sharply. That is a number in your database, not a convention.
Is it worth mailing people who never open?
Past a point, no. Continuing to mail them lowers your engagement signals and pushes everybody else towards the spam folder. Two pages carry the detail this one summarises: Subfolder localisation or Country-code domain, and then WordPress or Shopify.
What if this is not our problem?
Then we say so. The signals on this page are the honest filter, and work sold against the wrong diagnosis wastes a quarter. When this comes up in a pitch, Do we need a blog? and Does Google penalise AI-written content? are the pages that settle it.
What could go wrong with this work?
The usual risk is acting on a finding before it is solid. The diagnostic phase exists to avoid that, and where the data is too thin to be conclusive we will say so rather than proceed. The order most people need is E-E-A-T first, Embedding once the first one is running.
Will we speak to the person doing the work?
Yes. The person who diagnoses retention and win-back is the person who does it and the person on the review call. Handing a finding to somebody else to execute is where most of the value leaks. Technical SEO for Finance and fintech if the constraint is budget, Website Design and Development for Finance and fintech if the constraint is time.
Ask about retention and win-back
No brief needed. One paragraph about where you are stuck gets a specific answer back.
Start with an honest read on the gaps
We will show you what we would measure and why, so you can judge the approach before committing to it.