Stop calling it CRM. It is a growth engine.

Words matter more than operators like to admit. Category names carry operating assumptions, and operating assumptions decide who gets hired, what gets measured, and where the budget lands. 'CRM' is a category name from 1998, and it is quietly capping the ceiling of every DTC brand that still uses it.

This is not a semantic argument. It is a structural one. When retention lives inside a function called CRM, it inherits the assumptions of a discipline built for calendar-driven email production. When retention lives inside a function called a growth engine, it inherits the assumptions of a discipline built for compounding systems. The difference shows up in the P&L within two quarters.

What CRM inherits, and why it holds brands back

The CRM function inherits three assumptions from its origin as a sales-support discipline. First, the customer is a record to be managed, not a system to be modelled. Second, work is organised around campaigns and calendars, not hypotheses and holdouts. Third, the function reports to marketing, which means it is measured on send volume and open rate, not on incremental margin.

The reframe

A growth engine is a compounding loop with four discrete stages: capture, model, activate, measure. Each stage produces an artefact the next stage consumes. Each stage has a named owner. The loop runs continuously and is instrumented against a holdout at every activation. It is closer to how a product team runs than to how a marketing team runs.

The five moves that follow the reframe

1. Rename the function on the org chart

Trivial and enormous. 'Head of CRM' becomes 'Head of Retention' or 'Head of Growth Engine'. The rename is not cosmetic. It changes who applies for the role, what the next hire looks like, and what the person is measured on.

2. Move the reporting line to the CEO or COO

Retention that reports through marketing will always lose the resource fight against acquisition. Retention that reports directly to the operating executive gets the mandate to say no to campaigns that do not compound.

3. Move the primary tool from the ESP to the warehouse

The ESP is a send layer. It is not the source of truth. The warehouse is. When the model of the customer lives in the warehouse, every downstream tool inherits the same definition, and cross-channel activation stops being a special project.

4. Adopt the hypothesis as the unit of work

Every meaningful activity produces a written hypothesis, a defined holdout, a target metric, and a decision date. No hypothesis, no work. This one change kills roughly a third of the planned roadmap, and the third that dies was never going to compound.

5. Publish the retention P&L monthly

Revenue from the engine, cost of the engine, incremental margin against the holdout. One page. Read by finance, growth, and the board. The moment retention has its own P&L, the argument about budget stops being a matter of taste.

The objection we hear, and the answer

The objection is always the same. 'We do not have the engineering fluency to run it this way.' It is a real constraint, and it is not a reason to stay on the CRM model. It is a reason to hire, partner, or bring in a firm shaped to fill the gap. The brands that compound treat this fluency as a permanent function, not a temporary project.

"You do not need a bigger CRM team. You need a smaller, differently shaped one, with a mandate to say no."— Loiale, from the first thirty engagements

How Loiale sits inside this

We do not staff CRM teams. We build growth engines and hand them over. When we work with a brand still organised as a CRM function, the first thirty days include the reframe. The rename, the reporting line, the tool of record, the hypothesis discipline, the P&L. The engineering follows. It always does.