Lifecycle for startups: the three flows to build before anything else

Lifecycle marketing — the set of automated messages a product sends users at specific moments in their relationship with it — runs on infrastructure. Audience data, event tracking, the measurement scaffolding that tells you whether a flow is working. Each flow you build adds to that infrastructure. The next flow leans on it.

Early-stage teams usually start with whichever flow their ESP — their email service provider, the platform that actually sends the mail — shipped a template for. Or whichever stakeholder is loudest in the standup. The right ordering, almost always, is welcome → conversion-moment flow → winback. Each one builds on what the last one set up. Skip the order and you rebuild the same plumbing three times.

The first impression of the brand and the product, automated. Three to five messages covering: an immediate welcome (minutes after signup), first-action guidance (day 0–1), value reinforcement (day 3–5), social proof (day 7–10), and a check-in (day 14).

Why first: every acquired user flows through this. A 20% lift in activation from sharper welcome content compounds against every future acquisition — every signup, forever. No other flow has that kind of reach. The welcome sequence guide covers the structural detail.

Target for week 1: ship a 3-message welcome, even if the copy is rough. Iterate from there. Perfection is the enemy of shipping, and a rough welcome live in week one beats a perfect one live in November.

This one depends on the business model. The principle holds regardless: after welcome, invest in the flow that moves users from "first engagement" to "committed user". That's the second-highest-impact flow whatever the label on the business.

SaaS with a trial: the trial-to-paid sequence. Highest financial impact of any flow in the program — every percentage point of improvement translates to proportional revenue lift against acquisition spend.

Commerce: cart abandonment first, then browse abandonment once cart is solid. Combined, these typically contribute 10–15% of lifecycle-attributed revenue for early-stage commerce.

Subscription or consumable: the replenishment flow — the message that fires when a user is statistically due to re-buy. See replenishment emails.

Target for weeks 2–3: pick the right one for your business model and ship the core sequence. Don't build all three in parallel. Two mediocre conversion flows is worse than one good one.

No trial, no cart, no consumable? Pick whichever conversion moment does exist — first repeat purchase for commerce, first re-visit for content, first value action for freemium. The flow has to exist somewhere; find it and build it.

Winback fires at 60–90 days of dormancy — the point a user has stopped engaging but hasn't yet been written off. Two to three messages attempting re-engagement, before the sunset sequence (the polite goodbye that suppresses unresponsive addresses to protect deliverability) takes over. Short, honest, with a clear return path. No bribery.

Why third: you need acquisition and activation flows in place before you have dormant users to win back. Once you do, winback reclaims value from users you already paid to acquire — at a cost per send orders of magnitude below re-acquisition CAC (customer acquisition cost, the all-in spend to land a new user). The easiest revenue in the program.

Target for weeks 4–6: ship a 2-message winback. Pair with the sunset sequence for users winback doesn't reach. The two together cover the full dormancy arc; either alone leaves a gap.

Each skipped item is genuinely valuable in the right program. The issue is opportunity cost — every day spent on a newsletter in weeks 2–4 is a day not spent on welcome or conversion, which carry 5–10× the ROI for an early-stage program.

Newsletter specifically is a month 4–6 question at the earliest, and only if you have real editorial capacity. A half-committed newsletter with irregular cadence and thin content damages the program more than it helps. Three things have to be true before you start one: you have a voice, you have a content pipeline, you have tolerance for low direct revenue attribution. Most early-stage programs don't yet have all three.

By day 90, you should have:

• Welcome flow live and A/B tested (split-tested against a control to prove a copy or structure change actually moved a metric) at least once.

• Conversion-moment flow live with initial results.

• Winback flow live, with first cohorts entering.

• A 2-page quarterly plan covering next priorities (see quarterly planning).

• Baseline metrics on activation, conversion, and dormancy — so future work has a real starting point to measure against.

One note on tooling. Any modern ESP works for these three flows. Klaviyo. Customer.io. Iterable. Braze. The CDP question — whether to add a customer data platform that unifies your event data across tools — comes later. Don't let tool selection delay shipping; you can migrate, and you will almost certainly discover things about your data model that change what tool you'd have picked anyway.

And if you don't know what your activation event is — the specific in-product action that correlates with a user sticking around — finding it is part of shipping the welcome flow. Look at cohort retention data: which first-week actions predict 30-day retention? That's your candidate. Welcome is a forcing function for this analysis. Without a defined activation event, welcome copy can't be specific, and you'll feel that the moment you sit down to write message two.

A full-stack operator can ship all three flows in 60–90 days, with welcome live by week 2–3. Longer than that and the ordering collapses — you're working on all three at once, which is the exact pattern this guide exists to prevent.

covers the 90-day plan in more detail, including the milestones for each flow and the capacity math that makes this sequence achievable rather than aspirational.