Activation, retention and CRM are one system

I have stopped believing in three teams. For years the org chart told a tidy story: growth owns acquisition, product owns activation, CRM owns retention. Three leaders, three roadmaps, three sets of metrics, three quarterly reviews. It looks rational on a slide. In practice it is where retention goes to die. Every handoff is a seam, and every seam leaks. The user does not experience three teams; they experience one continuous arc from the moment they sign up to the moment they either stick or leave. If we are organised against the way the user actually behaves, we lose.

The handoff is the leak

Picture the classic relay. Growth hits its number and hands a freshly acquired user to product. Product gets them through the first screens and considers activation done. CRM picks them up weeks later with a lifecycle programme built on calendar logic. Each team optimises its own slice and declares victory. Meanwhile the user who signed up, half-finished setup, and never came back is nobody's problem, because they fell into the gap between two dashboards. The damage is never inside a team's remit. It is always in the space between them. That space is exactly what a Head of Activation, Retention and CRM should own outright.

Activation is the first retention event

This is the idea I keep coming back to. Activation is not a precursor to retention; it is the first instance of it. The first time someone reaches value is the first time they decide to stay. At BUUT I defined the activation funnel explicitly: KYC, child added, allowance set, first transaction. Each step is a tiny retention decision, and treating them that way changed how we built. We lifted onboarding conversion by 70% and cut support demand by roughly 50% in the same motion, because the things that block activation and the things that drive early churn are the same things. Fix the funnel and you fix the first week of retention for free. They were never separate problems.

Trigger on behaviour, not the calendar

Most CRM is still a broadcast schedule wearing a personalisation costume. Tuesday newsletter, monthly re-engagement blast, a birthday email the system thinks is delightful. It is sending on our calendar, not the user's behaviour. The lifecycle messaging that actually works is triggered by what the user did or conspicuously did not do: finished KYC but never added a child, made one booking but not a second, hit the value moment and went quiet. At Coworksurf I built the email and SMS lifecycle behind activation and repeat bookings around exactly these signals, and cut time-to-value by 65%. The message lands because it is a response to reality, not an entry in a content calendar. CRM is a product surface. It deserves the same behavioural instrumentation as the app, not a separate marketing toolchain bolted on at the end.

Instrument behaviour, not sends

Get the measurement wrong and the whole system drifts. Open rates, click rates, send volume: these measure our activity, not the user's progress. I do not care that an email was opened; I care whether the user took the next key action. So I instrument behaviour, not sends. The metrics that matter are time-to-value, first-key-action completion, and the early-retention curve in the first days and weeks. A campaign that lifts open rate but leaves the activation curve flat has done nothing, and a trigger that quietly moves people from step three to step four is worth more than any newsletter, even if nobody ever praises its open rate. Measure the funnel, not the megaphone.

How I would run it as one system

One funnel, one owner, one set of metrics from signup to habit. I would map the full journey as a single funnel and instrument every step in the same warehouse, so activation events and lifecycle messages read off one source of truth rather than two disconnected stacks. I have implemented HubSpot and lifecycle systems wired directly to product behaviour, so the trigger and the in-app moment are the same event, not a guess made days later. The team is organised around stages of the user's life, not around channels we happen to own. Growth experiments, product onboarding and lifecycle messaging sit under one roadmap because they are levers on the same curve.

The argument, in one line

Activation, retention and CRM are not three functions that hand off to each other. They are one system with one job: get the user to value, then keep them there. The moment you split that job across three teams, you create seams, and the user falls through them. I would rather own the whole arc, instrument the behaviour end to end, and be accountable for the only number that integrates all three: whether people stay. That is the function I want to lead, because that is how I already think the work should be done.