When we take on a new account, the first question isn't "what's the lifecycle strategy?" It's "where is the revenue that's currently being lost?"
There's always a list. It usually contains the same five or six items, in the same order. The work of the first three months is recovering that revenue systematically, not because it's more creative than building a lifecycle programme from scratch, but because it's faster to prove ROI and harder to argue with.
This post describes the framework we use to sequence that work. We call it the ROAS-first approach, not because we're obsessed with return on ad spend, we're not, but because every decision in the first 90 days is made by asking: "what's the fastest path to positive return on the programme investment?"
Step 1: The revenue audit
Before any strategy work, any creative, any segmentation discussion, we run a revenue audit. This takes one week and answers three questions:
Where is revenue being lost today? Cart abandonment rate and recovery rate. Lapsed customer rate and win-back rate. Post-purchase second-purchase conversion rate. Browse-abandon → purchase conversion rate. For most accounts, these four numbers reveal between 15% and 40% of potential annual revenue that's currently slipping through unaddressed triggers.
What's the quality of the existing programme? We look at revenue per recipient by flow, campaign, and segment. We look at deliverability (inbox placement, bounce rate, block rate). We look at list health (engagement decay rate, suppression hygiene). Bad quality in any one of these areas caps programme upside regardless of what else you do.
What's the attribution model? How is revenue currently being attributed to email? What's the attribution window? Is it click-based or open-based? Is the window consistent across all sends? If the model is wrong, any strategy work built on top of it will produce misleading results. We fix attribution before we measure anything else.
Step 2: The quick-win stack
The revenue audit produces a prioritised list. We sequence the items by two criteria: revenue impact (what would recovering 10% of this lost revenue be worth per month?) and implementation speed (how many days does it take to build and launch?).
The standard quick-win stack, in approximate priority order for most accounts:
- Abandoned cart, email (if not live or underperforming). Typically live within five days. Revenue recovery starts immediately. Median improvement over an underperforming existing flow: 30-50% uplift in recovered revenue.
- Post-purchase welcome sequence (if not live). Second-purchase conversion in the 30-day window is the clearest signal of programme health. Building this well takes two weeks; the cohort results take 60 days to be meaningful.
- Win-back, top decile lapsed customers only (fastest path to measurable ROI from lapse recovery). Not the full lapsed segment, the top decile by historic LTV. These customers have the highest re-engagement probability and the highest incremental value if reactivated. Build for this segment first, expand later.
- Browse-abandon (if high-traffic, low-conversion website). Browse-abandon converts at lower rates than cart abandon but adds to total programme revenue without cannibalising other flows.
The goal of the quick-win stack is to demonstrate programme ROI within 60 days. If we can't show the client a positive return on the engagement cost within 60 days from the quick-win stack alone, something is wrong with either the brief, the list health, or the attribution model, and we need to know that early.
Step 3: The lifecycle build
With quick wins live and proving ROI, the lifecycle architecture can proceed at a pace that doesn't put the engagement under immediate commercial pressure. The lifecycle build covers the six flows described in "The lifecycle email anatomy", layered in a sequence that respects the customer experience and avoids double-touching from multiple triggers simultaneously.
The sequencing principle: build lifecycle flows from the bottom of the funnel upward. Win-back before post-purchase expansion before top-of-funnel welcome. The reason is simple: recovering customers who've already demonstrated purchase intent produces a faster return than nurturing new subscribers who haven't yet decided whether they'll buy at all.
Step 4: The segment architecture
Most ESPs allow you to build infinite segments. Most clients have too many. The segments that drive commercial decisions are small in number: RFM tier (at minimum: active, at-risk, lapsed), lifecycle stage (prospect, first-time buyer, repeat buyer, VIP), and acquisition channel (because the customer who came in via paid social behaves differently to the one who found you organically).
We define these segments precisely, document them in the account brief, and build all reporting and trigger logic around them. New segments are added only when there's a commercial question they answer, not because a platform makes them easy to create.
Step 5: The 90-day review
At 90 days, the framework resets. The quick wins are now mature enough to show cohort data. The lifecycle flows have processed enough volume to produce statistically meaningful results. The segment architecture is tested against actual customer behaviour.
The 90-day review asks one question: where is the programme today versus where it was when we started? We answer it in three numbers: revenue per recipient (program-level), MQL-to-SQL rate or first-purchase conversion rate (funnel-level), and list health score (deliverability + engagement decay rate). If all three are trending correctly, the programme is working. If one is declining, we know which layer to investigate.
Why "ROAS-first" is a mindset, not a metric
The ROAS-first label is shorthand for a decision-making discipline: every programme choice is filtered through "does this produce return on the investment?" before it's filtered through "does this feel strategic?" Most strategy failure in email programmes comes from building structures that feel strategically coherent but don't connect to the revenue model.
The lifecycle canvas is a tool for designing customer experiences. The ROAS-first framework is a tool for building programmes that pay for themselves, which is the precondition for every lifecycle canvas surviving contact with a CFO review.
Both tools are necessary. The ROAS-first framework tells you where to start. The lifecycle canvas tells you where you're going. Use them in that order.