CRM February 2026 · 5 min read

The first 90 days of a lifecycle programme

A phased playbook for standing up email, push, and in-app flows from scratch without boiling the ocean.

SD
Servet Demirhan Performance Marketing and Growth

Every lifecycle programme starts with the same uncomfortable truth: you are sitting on a database of users who signed up, maybe converted once, and then went silent. The instinct is to build a dozen flows on day one. Resist it. The first 90 days should follow a strict phase gate model: audit, quick wins, architecture, then scale. Skip a phase and you end up rebuilding everything in month four.

Days 1-14 — The audit

Before you write a single subject line, map what already exists. Pull a full export of every automated email, push notification, and SMS that is currently live. Document the trigger, audience, send cadence, and last 30-day performance for each. You will almost certainly find zombie flows: campaigns set up by a previous team member, still sending, with open rates below 5 percent and no suppression logic. Pause or kill those immediately. Then audit your data layer. Can you reliably identify a user's signup date, first purchase date, last active date, and product category affinity? If any of those are missing, fix the instrumentation before moving forward.

Days 15-30 — Quick wins

Now you ship the three flows that generate the most revenue per hour of work: a welcome series, an abandoned cart sequence, and a post-purchase follow-up. The welcome series should be three emails over seven days. Email one lands within five minutes of signup and sets expectations. Email two (day two) delivers a value hook, your best content, a how-to guide, or a curated product selection. Email three (day seven) introduces the first conversion incentive. Keep the design minimal: one column, no hero banner, plain text with a single CTA button. These three flows alone typically recover 8-15 percent of otherwise lost revenue within the first month.

Days 31-60 — Flow architecture

With the quick wins generating data, you now have the signal needed to build a proper flow architecture. Map the full customer journey across stages: anonymous, signed_up, activated, converted, repeat, at_risk, churned. For each transition between stages, define the trigger event and the messaging sequence. A user who moves from activated to at-risk (no session in 14 days) should receive a re-engagement flow. A user who makes a second purchase should enter a loyalty nurture. The critical discipline here is suppression: every flow must check whether the user is already in a higher-priority sequence before enrolling them.

Days 61-90 — Measurement and iteration

By month three, you should have five to eight flows running in production. The question shifts from "what should we build" to "what is working". Set up a weekly review cadence with three metrics per flow: send-to-open rate, click-to-conversion rate, and incremental revenue per recipient. The last one is the most important and the hardest to measure correctly. You need a proper holdout group, typically 10 percent of eligible users who receive nothing, to calculate true incrementality. Without a holdout, you are measuring correlation and calling it causation. The teams that get this right in the first 90 days build a compounding advantage that is very difficult for competitors to replicate.