Updated · 9 min read
Building a lifecycle team — the roles, the order, the size
Picture the inheritance. Someone on the marketing team gets handed the ESP — the email service provider, the platform that actually sends the emails — as a side project. Six months later, a new hire turns up with CRM in their job title. Six months after that, an ops engineer joins because someone finally noticed the data going into the ESP was a mess. A year in there are three people, three slightly different titles, and no coherent plan. That isn't a lifecycle team. That's a staffing event that happened to you. The deliberate version starts with one hire, not four — and every next hire is chosen by which bottleneck is already hurting.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Why one job title is doing four jobs
Before the org chart, the vocabulary. Lifecycle marketing — the practice of messaging users at the right moment in their journey, from first signup to long-time customer to win-back — is not one job. It's four, frequently smushed into a single hire because the company hasn't hit the size where the seams show yet. They look similar from the outside. They feel wildly different from the inside.
The Lifecycle Strategist. Owns the program roadmap, the segmentation logic, and the call on what actually ships. Thinks in cohorts (groups of users defined by when they joined or what they did), activation rates, and retention curves. Rarely the person sitting inside Braze on a Tuesday afternoon.
The Lifecycle Execution / CRM Manager. The builder. Writes Liquid (the templating language ESPs use to inject personalised values into emails), wires up Canvases (Braze's name for automated multi-step journeys), pulls segments, owns the calendar. Most job ads titled CRM Manager are looking for this human.
The Marketing Ops / Engineer. Owns the pipeline into the ESP — the integrations with the product, the data warehouse syncs, the SQL that builds custom user attributes, the event tracking schema. Sits adjacent to lifecycle and often reports into data or engineering rather than marketing, which is correct.
The Copy / Creative. Writes the emails, designs the templates, produces the assets. Can sit inside lifecycle or in a broader brand team. Either works fine.
The most expensive hiring mistake in lifecycle is hiring a strategist when you need a builder, or a builder when you need a strategist. The roles look similar from the outside and feel wildly different from the inside.
The order matters — start full-stack, specialise toward the pain
First — the full-stack operator.Someone who can build in Braze, write passable copy, and think strategically enough to pick what to work on. Rare, expensive, and the only shape that survives the first 18 to 24 months without the program stalling. The test: if they can't ship a Braze Canvas — a full automated journey, trigger to send — end-to-end inside a week, they can't carry the role solo. Prioritise execution capability over pedigree. Shipping beats slides.
Second — copywriter or ops engineer.Whichever bottleneck is already costing you most. If your operator is spending 60% of their week on copy, bring in a copywriter. If they're blocked daily on data not flowing into Braze cleanly — segments wrong, attributes stale — bring in an ops engineer. Don't split the difference and hire another generalist. You already have one.
Third — the other one.Whichever bottleneck the second hire didn't solve is now the problem. Solve it.
Fourth — the strategist. At four people, the operator-as-strategist hybrid starts cracking. The operator stops having time to zoom out. The roadmap goes reactive — whatever a stakeholder messaged about on Friday becomes Monday's priority. A dedicated Lifecycle Strategist owns the roadmap, the experimentation plan, and the cross-functional relationships. The operators report in, or work peer-to-peer, depending on the company. The signal you've hit this point: your lead tells you, unprompted, that they're just executing what's in front of them. That's the threshold. You're already there.
Fifth and beyond — specialisation. By channel (email, push, SMS, in-app), by lifecycle stage (acquisition, retention, winback), or by product line. The right axis depends on where the complexity actually lives in the business — not on a template from a blog post.
Ratio-wise, two to four operators per strategist is the zone that works at team sizes five to ten. Past that the strategist becomes the bottleneck and you're either adding a second strategist or breaking into pods.
The fractional shortcut nobody uses enough
The other route into senior thinking is part-time. A fractional hire works two to three days a week on a three to twelve month engagement — senior brain, junior hours, no full-time cost. It's the most underused move in lifecycle hiring, and it works in a specific shape.
Execution is harder to fractionalise. Campaigns need context, continuity, and daily presence — a two-day-a-week contractor can't carry that. Ops engineering is the same story. The pipeline compounds, and a half-built pipeline is often worse than no pipeline because it creates the illusion that the data is trustworthy. Fractional strategist works. Fractional builder rarely does.
The signal that fractional has stopped working: the program is genuinely in motion. Multiple campaigns a week. Daily back-and-forth with product on what to instrument next. Segmentation that changes under you. At that pace, you need someone whose calendar is yours.
What you actually pay for the chair
Bands vary heavily by market — US, UK, and Australia diverge significantly — and by company stage. These are the rough 2026 numbers for UK and US tech companies.
CRM Manager (2–4 years): £55–80k / $85–130k. Ships campaigns, owns day-to-day execution.
Senior CRM / Lifecycle Manager (4–7 years): £75–110k / $130–180k. Owns a lifecycle stage or channel end-to-end.
Head of CRM / Lifecycle Lead (7+ years): £100–160k / $180–260k. Owns strategy, roadmap, cross-functional leadership, and 3–10 reports.
VP / Director of Lifecycle (10+ years): £150k+ / $250k+. Usually at companies with 50M+ users or complex multi-product lifecycle portfolios.
One quirk worth knowing about. Marketing ops engineers track closer to software engineering bands than marketing ones, so a senior marketing ops engineer often out-earns a peer senior CRM manager at the same company by around 20%. That isn't unfair. That's correct pricing for scarce technical skill. Treat it as a planning constraint, not a salary-review grievance.
When lifecycle stops belonging to brand marketing
Lifecycle teams frequently report into brand marketing because the sends go out over email, and email looks like marketing. Fine for the first one or two hires. By the time you're running five-plus active flows in parallel, friction. And it's always the same friction.
Brand marketing thinks in campaigns: launch a thing, amplify it, measure the moment. Lifecycle thinks in flows: user does X, system triggers Y, measure the cohort across weeks. The two decision systems are genuinely different. A brand leader judging lifecycle work on campaign-level metrics will gradually turn lifecycle into a brand channel — which is an expensive way to not do lifecycle.
At team size four and above, the better reporting line is one of three:
Product — lifecycle as part of the product experience.
Growth — lifecycle as part of the growth loop.
Revenue Operations — lifecycle as part of the revenue system.
Each emphasises a different job. Pick based on what the business actually expects lifecycle to move — activation, retention, or monetisation — not on which org chart slot is currently empty. A bonus check: if the reporting line forces lifecycle to justify itself in brand-campaign language every quarterly review, you've got the wrong line.
The marketing ops question deserves the same directness. Do you need a dedicated ops engineer if the ESP is already set up? If data flows in cleanly and custom attributes update reliably, not yet. If you're hearing we can't trigger on this event because it's not in Braze or the segment is wrong, the attribute is stale on a regular basis, yes — and hire them full-time, not as a shared engineering resource you're borrowing between sprints.
covers the decision framework for reporting line based on business model — worth running through before the next org conversation.
Read to the end
Scroll to the bottom of the guide — we'll tick it on your reading path automatically.
This guide is backed by an Orbit skill
Related guides
Browse allThe lifecycle audit — a 30-point checklist
Lifecycle programs — the automated email, push and SMS journeys that move customers from signup to repeat purchase — decay quietly. A recurring audit is the cheapest discipline that catches drift before it turns up in the revenue deck. Here's the 30-point list, grouped by severity, that takes three hours the first time and ninety minutes after that.
Choosing which lifecycle programs to build first
New lifecycle lead, empty Braze account, a laundry list of programs you could build. The question nobody trains you for is which to build first. This is the selection framework — by business type, by team size, by data maturity, and the programs I'd actively wait on.
What is lifecycle marketing? A field guide for operators starting from zero
If you're new to CRM and lifecycle, the field reads like a pile of acronyms and vendor demos. It's actually one simple idea executed across five canonical programs. Here's the frame that makes the rest of the library make sense.
Segmentation strategy: beyond RFM
RFM is the floor of audience segmentation, not the ceiling. Every program that stops there ends up describing what users already did without ever predicting what they'll do next. Here's the segmentation stack that actually drives lifecycle decisions — and how to build it in Braze without ending up with 400 segments nobody understands.
Retention economics: proving lifecycle ROI to finance
Lifecycle programs get deprioritised when they can't defend their impact in dollars. The four models that keep the budget — LTV, payback, cohort retention, incrementality — and the four-slide pattern that wins a CFO room.
Lifecycle marketing for flat products
The standard lifecycle playbook assumes weekly engagement and tidy stage progression. Most real products aren't shaped like that. This is how to design lifecycle — the messaging program that nudges users through their relationship with a product — for things people use once a year, once a quarter, or whenever they happen to need you. The textbook quietly makes those programs worse.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 63 lifecycle methodologies, 91 MCP tools, native Braze integration. Free for everyone.