Published June 13-17, 2026
1
How D2C brands can reduce Revenue Tax, shorten Time-to-Next-Transaction, and stop paying twice
The CMO’s New Job: From Campaigns to Customer Alpha
The Tax-onomy essay built the framework. The naming essay gave it a noun: the Alpha Operating System. This essay answers the CMO’s Monday morning question: what do I do with it?
AOS is not another marketing slogan. It is a way of running customer economics: every transaction is measured by the tax paid to create it, every customer is measured by transaction depth and attention state, and every quarter is judged by Alpha generated above Beta. The CMO’s job is to operate the system.
AOS Nomenclature
| Term | Meaning | Role in AOS |
| AOS | Alpha Operating System | Umbrella framework for customer economics |
| Revenue Tax Ladder | 0–5% Organic, 5–10% CRM, 10–15% NeoMarketing Recovery, 20–25% Adtech, 30–40%+ Intermediated | Measures transaction quality |
| Seven Transaction Buckets | Intermediated + six Direct buckets split by New/Repeat and Organic/CRM/Adtech | Places every transaction in one cell |
| Offer Tax | Discounts, coupons, cashback, free shipping, loyalty burn | Reveals hidden margin leakage |
| TAT | Transactions-Attention Table | Maps customers by transaction depth and attention recency |
| BRTN | Best, Rest, Test, Next | Customer-state language |
| NeoMarketing | Recovery rung between CRM and Adtech | Engine for drifting and lost customers |
| Atrium | Attention recovery engine | Rest / Test, NeoMails, NeoNet, ActionAds |
| Meridian | LTV maximisation engine | Best / B–, outcome underwriting |
| Seven Alpha Plays | Operational moves that shift transactions down the Ladder and customers leftward / downward on the TAT | Turns diagnosis into action |
| AOS Dashboard | Ten metrics tracking Tax, Time and Alpha | Governance instrument |
| Alpha Generated | Incremental contribution profit above Beta baseline | Outcome metric |
**
Three pressures are squeezing the modern D2C CMO simultaneously. Customer acquisition cost is rising, year on year, in every category. Repeat revenue — once the CMO’s safe ground — is leaking into paid media and marketplaces, where the brand pays platform tax to bring back customers it already owns. The CRM dashboards report opens, clicks, and ROAS, but say nothing about whether customers are drifting from loyal toward dormant, or moving from new toward repeat. They tell the CMO what was sent, opened, and clicked; they rarely show which customers are weakening before the P&L pays the bill. The CMO is being judged on outcomes that the current dashboard cannot read.
AOS responds to that gap. It is not a new toolkit, a better campaign methodology, or a fresh round of martech features. It is a new definition of what marketing’s job is. Under AOS, marketing is no longer the function that buys media and runs campaigns. It is the function that moves customers and transactions through measurable states, against a Beta baseline, and is held accountable for the Alpha that movement produces. Campaigns are still used; campaigns are no longer the unit of strategy. Customer movement is the unit of strategy.
That reframe lands as a change in the questions a CMO can answer in a board meeting.
| The CMO’s old question | The AOS question |
| How much revenue did we generate? | What tax did we pay to generate it? |
| Which channel performed best? | Was the customer New, Repeat-Owned, or Repeat-Reacquired? |
| Did campaigns lift engagement? | Did customers move N → T → B, or drift B → B– → R1? |
| What was our ROAS? | How much Alpha did we generate above Beta? |
Each row of the table is a job change. The old questions can be answered with a chart from any analytics tool. The AOS questions require a system. The first row shifts revenue from a volume number to an economic number. The second row separates legitimate acquisition from expensive reacquisition. The third row replaces engagement metrics with customer-state movement. The fourth row replaces ROAS — a backward-looking ratio with no baseline — with Alpha against Beta, which is forward-looking and benchmarked.
A quick recap for the reader new to this trilogy. AOS consists of two diagnostic instruments — the Revenue Tax Ladder (which classifies routes by their cost) and the Transactions-Attention Table (TAT) (which classifies customers by their state and trajectory). It deploys NeoMarketing — composed of Atrium, Meridian, NeoNet and ActionAds — as the recovery engine in the missing rung between CRM and Adtech. It executes through the Seven Alpha Plays, operational moves that shift transactions down the Ladder and customers leftward and downward through the TAT. It is governed by the AOS Dashboard, ten metrics measuring Tax, Time, and Alpha above Beta.
The Tax-onomy essay built that architecture. The naming essay gave it the umbrella. The CMO’s job is to run it. That is the new job. The rest of this essay is the playbook for running it.
2
The 90-Day AOS Playbook
A CMO can run an AOS pilot in ninety days. The first thirty are diagnostic — pulling data, classifying transactions, building the TAT, surfacing the leakage pools that will shock the executive team. The next thirty are decision — selecting two or three Alpha Plays to pilot, securing CFO buy-in on the Beta baseline, installing the governance rhythm. The final thirty are execution — running the pilot plays, measuring against baseline, producing the first board-ready Alpha number.
The playbook is seven steps. Each step is shorter to describe than to execute, but the description is what the CMO needs in order to convene the right people, ask for the right data, and defend the right decisions.
Step 1 — Build the transaction file (Week 1). Pull twelve months of transactions from the order management system: order ID, customer ID where known, date, gross revenue, discount applied, channel attribution, platform identifier. Pull the matching engagement events from the ESP, the push provider, and the WhatsApp BSP: open events, clicks, push opens, app sessions, with customer ID and timestamps. Pull paid media spend by campaign with audience targeting. Join them into one combined dataset, one row per transaction, with the customer’s last attention event before the transaction linked in. The CMO’s job at this step is championing the data request inside finance and engineering. If the CMO cannot convene these teams for an AOS audit, that is itself a finding — the company is asking marketing to generate Alpha without giving it sight of the customer economics that determine Alpha.
| Data source | Fields required | Likely owner |
| Orders | Order ID, customer ID, date, revenue, product, channel, platform | Commerce / Data |
| Customer master | First order date, lifetime orders, lifetime revenue, email / mobile | CRM / CDP |
| Paid media | Campaign, source, spend, prospecting vs retargeting, customer match | Growth |
| CRM events | Email opens / clicks, WhatsApp responses, push taps, app opens | CRM / Martech |
| Offers | Coupon, discount, cashback, free shipping, loyalty burn | Finance / CRM |
| Intermediaries | Commission, visibility spend, logistics, discounts, identity availability | Marketplace team |
Step 2 — Classify every transaction (Weeks 2–3). Apply the Three Questions. Q1: Direct or Intermediated? Q2 for Direct only: Organic, CRM, or Adtech? Q3: New or Known? Produce the Seven Bucket distribution. Default to last-click attribution for v1 — perfection is not the goal, consistency is. The CMO’s job at this step is defending the classification rules against attribution debates. The team will want to relitigate the rules every time a number looks ugly. Don’t let them. Document the rules, share them widely, and refuse to change them mid-quarter.
Step 3 — Compute Effective Transaction Tax (Week 3). Add Route Tax and Offer Tax for each bucket. Use category benchmarks for Route Tax until actual channel cost allocation is available; use the average discount percentage applied within the bucket for Offer Tax. The formula is unforgiving in its simplicity: Effective Transaction Tax = Route Tax + Offer Tax. That simplicity is the point. It prevents the most common deception in D2C — treating CRM as cheap even when CRM revenue is being bought with deep discounts. A 5–10% CRM route tax plus an 18% coupon is not a 5–10% transaction; it is an adtech-like transaction wearing owned-channel clothes. The headline number to compute is Paid Repeat Leakage — Repeat Direct Adtech revenue divided by total Direct Repeat revenue. The CMO’s job at this step is walking the CFO through the discount-as-tax argument before the CFO discovers it themselves. Better that the CFO sees the arithmetic before they see the number.
Step 4 — Build the TAT (Weeks 3–4). Define meaningful attention events explicitly: open, click, push tap, WhatsApp read, app session, magnet interaction. Compute days-since-last-meaningful-attention for every customer in the database, in parallel with transaction count over the trailing year. Assign each customer to one of nine cells. The headline number here is the Weakening Pool — the count of B– and T– customers. The CMO’s job is locking the attention-event definition for at least one quarter. Different teams will draw different lines. That’s fine. Pick a definition, document it, freeze it. Inconsistency is more damaging than imprecision.
| Transactions ↓ Attention → | 0–30 days Strong |
30–90 days Weakening |
90+ days Lost |
| 0 | N | N– | L |
| 1–2 | T | T– | R2 |
| 3+ | B | B– | R1 |
Step 5 — Identify the leakage pools (Week 5). Cross-tabulate the Seven Buckets against the TAT cells. Surface four numbers: Paid Repeat Leakage, Weakening Pool, R1 Recoverable Value, and Identity Capture Rate on Intermediated transactions. The CMO’s job at this step is converting those four numbers into a single board-ready slide titled “How much of last quarter’s marketing spend was structurally avoidable?” That slide is the diagnostic’s deliverable. It is the case for change, in one number.
| Leakage pool | What it reveals | CMO action |
| Paid Repeat Leakage | Repeat customers being bought back through paid media | Test owned-route alternatives |
| Weakening Pool (B– + T–) | Purchased customers starting to drift | Shift from Sell to Relate |
| R1 Recoverable Value | Former Best customers now lost to attention | Prioritise recovery economics |
| Intermediated without Identity | Sales that cannot compound into relationships | Build identity bridges |
Step 6 — Choose two or three Alpha Plays for the pilot (Week 6). Do not run all seven plays. Pick the readily-deployable ones first. The team will want to swing wide; the CMO must defend the focus.
The recommended pilot trio, ordered by deployment readiness:
| Pilot play | Target | Why start here | Primary metric |
| Play 6 — Shift Repeat Adtech to Owned | Repeat Direct Adtech | Fastest to deploy on existing stack | Paid Repeat Leakage |
| Play 4 — Protect Best from Becoming Rest | B– | High economic value, early-warning timing | B– → B rate |
| Play 5 — Recover Rest Before Adtech | R1 / R2 | Tests the missing rung and recovery economics | R1/R2 → B–/T– → B/T |
- Play 6 — Shift Repeat Adtech to Owned. Two weeks to deploy on existing CRM stack. Suppress 90-day-active customers from prospecting campaigns. Redirect the saved spend to owned-channel reactivation flows for the same cohort. Measure attributed revenue and effective tax against a matched control. First Alpha typically visible within 30–45 days. This is the play that pays for the rest of the pilot.
- Play 4 — Protect Best from Becoming Rest. Four weeks to deploy with existing CRM stack plus content commission. Identify the B– cohort from the TAT diagnostic. Pause promotional content for 30 days. Replace with utility, recognition, or service content. Measure attention recovery and subsequent transaction rate against a matched B– control held in standard promotional flow. First signal visible at 60–90 days. This is the play with the highest single-cell economic leverage on the grid.
- Play 5 — Recover Rest Before Adtech. Six weeks to deploy with content investment. Pick the top R1 cohort by historical LTV. Run a 30-day Atrium-style attention restoration with no transaction ask in weeks one and two. Measure attention restoration at day 30 (the Atrium step); measure transactions in days 31–60 against the same R1 cohort recovered through paid retargeting in the prior quarter (the Meridian step). First Alpha visible at 90–120 days; this is the longest cycle of the three.
The CMO chooses two of these three for the pilot. The dominant pattern: pick Play 6 (revenue case, easiest to deploy) and one of Play 4 or Play 5 (learning case, harder to deploy). The choice between Play 4 and Play 5 depends on which leakage pool is bigger — if the B– cohort is fat, Play 4; if R1 Recoverable Value is large, Play 5.
Step 7 — Install the AOS Dashboard (Weeks 7–8). Three numbers on the CMO’s Monday morning report: Paid Repeat Leakage this month vs last month, Weakening Pool count this month vs last month, Alpha Generated quarter-to-date against agreed Beta. Full ten-metric review quarterly with the CFO. The CMO’s job is installing the dashboard rhythm before the pilot data lands. Governance has to be in place when the results arrive. A dashboard installed after the fact is reporting; a dashboard installed before the fact is governance.
Do not start with campaigns. Start with classification. AOS begins when every transaction has a tax and every customer has a state.
The campaigns come later. They come once the diagnostic has surfaced where Alpha is actually leaking, and once the pilot plays have shown which interventions produce movement. The CMO who skips the classification and jumps to play execution is running standard marketing with new vocabulary. AOS is what the discipline becomes when the classification comes first.
* * *
Bridge — What to Expect in the First 90 Days
Before the playbook becomes a story, three things to set realistic expectations.
The diagnostic numbers that will shock. Most D2C brands discover, on first audit, that their Paid Repeat Leakage is between 30% and 45%. They had assumed it was below 15%. They discover that their Effective Transaction Tax on CRM revenue, once Offer Tax is included, is between 18% and 28% — almost touching adtech economics. They discover that 20% to 30% of their Best cohort is sitting in B–, drifting on attention, before the transaction signal has caught it. They discover that their Identity Capture Rate on marketplace transactions is closer to 5% than 50%. If your audit numbers come back clean, double-check the methodology — they usually don’t.
The conversations that will be hardest. The CFO will challenge the Beta baseline. Why last-year-same-period? Why not the rolling six-month average? Why not budgeted growth? These questions are legitimate; the answer is procedural, not analytical — pick a definition, document it, lock it for a year, refine with incrementality testing. The performance marketing team will push back on Repeat Direct Adtech being called AdWaste. They will argue that retargeting drives incremental revenue. The answer is empirical — design the suppression test and measure. The CDP and data engineering team will resist the attention-event definition because it cuts across multiple systems. The answer is procedural again — pick a definition you can sustain, not the most rigorous one. Each conversation is winnable, but only if the CMO walks in with the diagnostic numbers in hand. Without numbers, the conversations devolve into opinion.
The early wins to watch for. Play 6 shows revenue results in 30–45 days because the mechanic is fast — suppress an audience, redirect a budget, measure the lift. Play 4 shows attention recovery first, transaction recovery only later — open-rate stabilisation at day 30, transaction-rate stabilisation at day 60–90. Play 5 is the longest cycle — the Atrium step takes 30 days, the Meridian step needs another 30–60 days after that, so the first Alpha from Play 5 is at day 90–120. Plan the board update cadence accordingly. The 30-day update reports the diagnostic shock. The 60-day update reports Play 6 results and Play 4 attention movement. The 90-day update reports Play 6 sustained, Play 4 transaction movement, and Play 5 attention restoration. The full pilot story does not come together until day 120.
The pilot is a story that unfolds. The CMO’s job through the first 90 days is to manage expectations across that arc — to keep the CFO patient through the Atrium half of Play 5, to keep the e-commerce team aligned during the Play 4 promotional pause, to keep the board interested when the diagnostic shocks land before the corrective wins do.
3
The Hard Questions
A framework that cannot survive honest critique cannot survive deployment. Before the first board review, the CMO should be able to answer six questions from their own team. These are not the questions a sceptical outsider would ask — those tend to be superficial. These are the questions a thoughtful insider would ask after running the diagnostic for thirty days.
Question 1 — Is the 10–15% NeoMarketing rung real, or asserted? The honest answer is that it is provisional. The Tax Ladder is empirically observable: CRM costs 5–10%, Adtech costs 20–25%, and the gap between them is real. The claim that NeoMarketing — Atrium, Meridian, NeoNet, ActionAds — can occupy that gap at 10–15% effective tax is theoretical. It depends on a stack of assumptions: that ActionAds can fund the NeoMail rhythm, that Atrium can restore attention at meaningful rates, that NeoNet can replace platform tax with cooperative surplus. None of those has been demonstrated at scale in production by an independent brand outside of vendor pilots. The diagnostic half of AOS holds regardless — the Tax Ladder, TAT, Seven Buckets, and Dashboard are useful for diagnosis even if NeoMarketing economics fail. The CMO should treat NeoMarketing as a prescription under test, not as proven infrastructure.
Question 2 — Can attention recency be measured cleanly? Not exactly. Different teams will draw different lines on what counts as a meaningful attention event — an email open with image disabled, a push notification dismissed, an app open of three seconds — each is a judgement call. The problem is procedural, not analytical. Pick a definition, document it, lock it for a quarter, refine afterwards. The inconsistency cost of changing the definition mid-quarter is higher than the precision cost of picking an imperfect definition.
Question 3 — Do the Seven Plays sequence equally? No. Some require new product (Plays 5 and 7 lean on NeoMails and ActionAds, which most brands do not have). Some run on existing stack (Play 6 needs nothing but a suppression rule and a redirected budget). The framework lists them as a system; in practice, the CMO sequences them by deployment readiness. Deploy the readily-deployable plays in quarter one; let their data inform what to build for quarter two. A brand that tries to deploy all seven simultaneously is running a project, not a pilot.
Question 4 — How is the Beta baseline really set? The same problem hedge funds have with benchmark selection. There is no neutral answer. Use last-year-same-period as Beta v1 — imperfect, but defensible. Refine through incrementality testing in subsequent quarters: holdout cohorts, geo splits, time-shifted controls. The discipline is not in finding a perfect baseline; it is in measuring against something rather than against zero. A weak baseline rigorously applied beats a strong baseline negotiated quarterly.
Question 5 — Doesn’t AOS risk becoming consulting jargon? Yes. Names travel faster than disciplines. There will be brands that talk AOS — putting the word on slides, using “Alpha Generated” loosely, naming their dashboards “AOS Dashboard” — without running the diagnostic, picking the plays, or installing the governance. The dashboard is the test. If a brand cannot produce the ten metrics on a Monday morning, it does not run AOS regardless of what its slides say.
Question 6 — Does the CMO actually have the authority to run AOS? Probably not, on day one. AOS assumes cross-functional reach: CRM operations, marketplace identity capture, pricing and promotion policy, agency contracts. In most D2C brands, the CMO owns some of these and influences others. The diagnostic itself is the case for the missing authority. When the CMO walks into the CEO’s office with the Paid Repeat Leakage number, the Weakening Pool count, and the R1 Recoverable Value, the case for cross-functional governance writes itself. AOS is not a marketing initiative that needs CMO authority; it is a customer-economics programme that produces the case for the authority.
These six questions are not objections to be deflected. A CMO who can answer them — including the honest concession that NeoMarketing economics are unproven — earns more trust from a sceptical board than one who pretends the framework has no weak points.
4
Maya’s AOS Moment – 1
Maya is the CMO of a four-year-old direct-to-consumer skincare brand. Annual revenue $14M, growing 22% year on year. Customer base 380,000, of which 95,000 are active in the trailing 365 days. Marketing mix: ~40% Google and Meta paid, ~25% CRM (email and WhatsApp), ~15% influencer, ~20% organic and SEO. AOV $68. Gross margin 62%. Median purchase cycle 60 days. The CEO has been asking, quietly but persistently, why CAC keeps creeping up despite the revenue growth.
Before AOS
On paper, Maya is winning. Revenue is up. ROAS is green across the major campaigns. CRM revenue is healthy — last quarter it grew 18% year over year. Marketplace presence on Amazon and Nykaa is rising. The board is happy.
But something nags her. Every quarter, blended CAC is up. The performance marketing team explains it as auction inflation. The CRM team explains their growth as a sign of the lifecycle programmes working. The marketplace team celebrates the Amazon shelf placement. Each function is showing green; none of them is explaining the CAC creep.
She reads the Tax-onomy essay over a weekend. The line that bothers her is simple: a brand can grow revenue and still be paying for Beta on credit. The seven-bucket framework names something she has been feeling for two years: not all revenue is equal. She commissions a 30-day AOS audit with her senior analyst and her ESP partner.
The audit findings
Four weeks later, the findings land on her desk. They are worse than she expected.
| Finding | What Maya expected | What the audit showed |
| Paid Repeat Leakage | ~15% | 42% |
| Effective Transaction Tax on CRM bucket | 5–10% | 23% after 18% average Offer Tax |
| Best customers sitting in B– | Small issue | 27% of the Best cohort |
| R1 historical revenue | Unknown | $8M |
| Time to second transaction | 42 days historically | 67 days now |
| Marketplace identity capture | Not measured | 4% |
The detail behind each row matters. Paid Repeat Leakage at 42% means the retargeting campaigns the team had been celebrating as efficient repeat-revenue drivers were largely bringing back customers who were already in the database — paying Google and Meta to do what email should have done. Effective Transaction Tax on the CRM bucket of 23% — against the 7% the team had been reporting — hides 16 points of Offer Tax from an average 18% discount sitting in line items the channel-cost ledger never saw. Twenty-seven percent of her Best cohort sits in B–. Roughly 24,000 customers — proven repeat buyers — are weakening on attention before any transaction signal would have shown it. The team’s segmentation had been treating them as healthy Best because their transaction count is high. The TAT shows them drifting.
R1 represents $8M in historical revenue. Sixty-eight percent of that R1 cohort has not been reached through CRM in the last 120 days. The brand is not failing to recover them — it has stopped trying. Time to Second Transaction has stretched from 42 days to 67 days over the last 18 months. The lifecycle programmes the CRM team has been celebrating are not, in fact, compressing the second-purchase cycle. They are running alongside a slowdown. Identity Capture Rate on marketplace transactions is 4%. Of every hundred new buyers the brand acquires through Amazon, Nykaa, and Blinkit, four are ever brought into the owned database. The other ninety-six will, if they buy again, have to be paid for again — to the platform.
Maya schedules an emergency meeting with her CFO. She walks him through the numbers. The CFO’s first reaction is to challenge the methodology. The second is to ask whether the lifecycle programmes that have been showing growth are real or measurement artefacts. The third is the question Maya was waiting for: “You’re telling me 42% of our paid spend is structurally avoidable?”
Maya’s answer: “Possibly. I want to test it.” That sentence matters. She does not overclaim. She asks for a pilot.
The audit also changes how Maya sees her own team. Performance marketing is not the villain — it has been solving the problems the rest of the system handed to it. CRM is not innocent either — it has been celebrating revenue that often required heavy discounts. Marketplace is not merely distribution; it is revenue that may never compound unless identity is captured. The problem is not a person. It is the absence of an operating system.
The 90-day pilot
Maya picks three plays. She knows she should pick two; she picks three because she wants to test the full Atrium plus Meridian recovery sequence alongside the easier deployments.
Play 6 — Shift Repeat Adtech to Owned. Suppression rule applied to retargeting campaigns: any customer with a transaction in the last 90 days is excluded from prospecting and standard retargeting. Spend redirected to a new CRM reactivation flow targeting the same cohort. Matched control group retained on standard treatment. Two weeks to deploy.
Play 4 — Protect Best from Becoming Rest. The 24,000-customer B– cohort identified, segmented into a test group (12,000) and a control (12,000). Test group taken off promotional content for 30 days, replaced with utility content (skincare routine recommendations, ingredient education, founder voice notes). Test group held in a designated “Relate” stream, control held in standard treatment.
Play 5 — Recover Rest Before Adtech. Top 10,000 R1 customers by historical LTV. 30-day Atrium pilot: daily NeoMails with magnets (skin quiz, ingredient quiz, mini-stories from the founder) and no transaction ask in weeks one and two. Reactivation offers introduced gradually in weeks three and four. Matched control of 10,000 R1 customers retained on standard paid-retargeting recovery flow.
She agrees the Beta baseline with her CFO: same period prior year, adjusted for category growth. Any incremental contribution profit above that baseline counts as Alpha.
5
Maya’s AOS Moment – 2
The setback
Six weeks into the pilot, Play 4 hits a wall.
The 30-day “no promotion” rule generates internal resistance Maya did not anticipate. Her e-commerce team panics about a perceived revenue dip from the test cohort during the promotional pause. The merchandising team escalates to the COO. The COO calls Maya: can we resume promotion to that cohort, just for the festive week?
Maya negotiates a compromise. Utility content alongside reduced promotional frequency, not zero promotion. The Play 4 pilot continues but with weaker conditions than the design called for. At 90 days, the B– cohort decline rate is 4% better than control — statistically present, but well below the 15–20% Maya had hypothesised.
She documents the learning. Play 4 worked partially. The structural issue was not the play; it was the governance. AOS assumed the CMO had unilateral authority over how a customer cohort is treated for thirty days. In Maya’s organisation, that authority is shared with merchandising and e-commerce. The play succeeded to the extent her authority allowed; it underperformed where the authority was diluted.
She takes the learning to the CEO. Not as a complaint about cross-functional friction — as a structural finding. “The reason this play underperformed was governance, not design. If we want to run AOS properly, we need to clarify which cohort decisions belong to marketing and which to merchandising. Here is the cost of the ambiguity.”
The CEO agrees to a cross-functional review.
The impact at six months
Play 6 has held. Paid Repeat Leakage at six months is 31%, down from 42%. Owned Repeat Ratio is 69%, up from 58%. The CFO has recalculated contribution margin against the new bucket distribution; the picture is meaningfully better than the old dashboard had been showing.
Play 5 is partial. The Atrium step worked: 9% of the R1 cohort returned to active attention within 30 days, comparable to industry benchmarks for daily-engagement programmes. The Meridian step worked unevenly: of the 9% restored to B–, 31% converted to B within the next 90 days. Recovery Conversion Rate of 31% is below Maya’s hypothesis of 45% but well above what the paid-retargeting control achieved. This split teaches the team something important: Atrium restored attention, Meridian converted value. Counting the first step as full recovery would have overstated Alpha. AOS forced the team to count potential Alpha and realised Alpha separately.
Play 4 is inconclusive at a transaction level but produced the most valuable structural finding of the pilot: AOS works in proportion to the CMO’s cross-functional authority.
Net Alpha Generated: $740K incremental contribution profit over two quarters, measured against the agreed Beta baseline. Most of it from Play 6; some from Play 5. Maya now has a credible AOS Dashboard, a renegotiated agency contract paying against Alpha rather than against ROAS, and quarterly board reviews structured around the ten AOS metrics. She has briefed the CFO of her sister brand in the holding company.
The board discussion changes. Instead of asking only about CAC and ROAS, the CEO asks about Paid Repeat Leakage. The CFO asks whether the B– governance issue has been resolved. The marketplace team gets a new quarterly target: identity capture rate. The CRM team stops reporting only campaign revenue and starts reporting customer movement across the TAT.
What Maya learned
Three things, distilled.
First, the diagnostic was more valuable than any single play. The 42% Paid Repeat Leakage number — by itself — would have justified the whole exercise even if every play had failed. Knowing the size of the problem turned every other conversation from opinion into negotiation.
Second, the play that underperformed taught her more than the play that succeeded. Play 6 confirmed what the diagnostic had implied. Play 4 surfaced a governance problem that AOS had assumed away. Both findings were valuable; the second was actionable in a way the first was not.
Third, AOS is a framework that admits its weak points. The 10–15% NeoMarketing rung claim is provisional. Her own Play 5 results came in below hypothesis. She did not have to defend AOS as flawless to her board; she had to defend it as a discipline that produces measurable results and honest critiques. That was an easier defence than the one her previous frameworks had asked of her.
* * *
The CMO Takeaway
| AOS principle | What the CMO does on Monday |
| Every transaction has a tax | Build the seven-bucket revenue view |
| Every customer has a state | Build the TAT and track movement |
| Every discount is an economic choice | Add Offer Tax to CRM and paid performance |
| Every repeat paid sale may be leakage | Measure Paid Repeat Leakage monthly |
| Every recovery needs sequencing | Atrium restores attention; Meridian recovers value |
| Every outcome needs a baseline | Measure Alpha above Beta, not against zero |
The trilogy is now complete. The Tax-onomy essay showed how to see Tax and Time. The naming essay gave the system its umbrella: AOS. This CMO playbook shows how to run it. The work now moves from essay to audit, from audit to pilot, and from pilot to proof.
Maya did not run more campaigns. She ran a better operating system. The next CMO is reading the Tax-onomy essay this weekend. Their AOS audit starts Monday.
Buy New efficiently. Own Repeat completely. Recover before paying twice.