Rajesh Jain

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.

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.

An operating system for D2C customer economics — a name for the framework the D2C Tax-onomy essay built

1

A Framework needs a Name

The D2C Tax-onomy essay  built a complete architecture. It diagnosed the hidden tax in every transaction. It introduced the Revenue Tax Ladder. It classified every sale into seven mutually exclusive buckets. It added Offer Tax as a hidden cost layer. It mapped customers through the Transactions-Attention Table. It identified the missing rung between CRM and Adtech. It converted the diagnosis into seven Alpha Plays and a new dashboard.

But the architecture still needs one thing: a name. A framework without a name is a thesis. A framework with a name is a system. The two are not the same operational object. Without a name, a framework does not travel. It gets remembered as a long essay, a clever chart, or “that transaction-tax idea.” It does not become a shared operating language across the constituencies that have to coordinate to make it work.

Consider what already-named systems look like. RFM is sixty years old and still cited weekly because it has three letters that travel. The BCG Matrix is half a century old and still appears in board decks because it has a noun. Net Promoter Score does no analytical work that other satisfaction measures don’t do — it dominates because Net Promoter Score is a phrase that survives meetings and memos and quarterly reviews. AIDA, the 7Ps, MQL-to-SQL, OKRs, SaaS Magic Number — each acquired authority not through superior analytical depth but through the gift of a name compact enough to move.

The D2C Tax-onomy framework has the substance. It does not yet have the noun. Until it has one, it will be cited rather than adopted and implemented as a system with a stable architecture and a measurable outcome. Naming is the bridge from idea to infrastructure.

This essay names it.

Alpha Operating System

The framework is the Alpha Operating System. AOS.

The word Alpha names the outcome. The framework is not trying to improve activity for its own sake. It is trying to create uplift above the baseline — the incremental contribution profit that comes from paying less tax per transaction, moving customers faster to the next transaction, and preventing the same customer from being bought twice. Alpha is the unit of value the system produces.

The phrase Operating System names the scope. AOS is not a dashboard, a matrix, a campaign method, or a product pitch. It is the managerial system that connects diagnostics, intervention, measurement and governance into one coherent operating rhythm. It tells a CMO how to read revenue, how to read customers, where to intervene, and how to prove whether the intervention created Alpha.

In one sentence: the Alpha Operating System is a customer-economics framework that helps D2C brands reduce Revenue Tax, shorten Time-to-Next-Transaction, and generate measurable Alpha above Beta.

The one-line promise stays simple:

AOS — Buy New efficiently.  Own Repeat completely.  Recover before paying twice.

2

The Nomenclature

The naming hierarchy matters because each term should do exactly one job. AOS is the umbrella. The Revenue Tax Ladder and the TAT are diagnostic instruments. NeoMarketing is the recovery engine that occupies the missing rung. The Seven Alpha Plays are the operational moves. The AOS Dashboard is the governance layer. Beneath those top-level components, the four NeoMarketing sub-engines — Atrium, Meridian, NeoNet, ActionAds — do specific work within the recovery layer. Keeping each name doing one job preserves the architecture’s clarity.

LEVEL	NAME	ROLE
Umbrella framework	Alpha Operating System (AOS)	The full customer economics system
Economic diagnostic	Revenue Tax Ladder	Classifies routes by the cost to create transactions
Transaction classifier	Seven Transaction Buckets	Places every sale in exactly one bucket
Hidden cost layer	Offer Tax	Adds discount, coupon, free shipping and incentive cost
Customer-state diagnostic	TAT — Transactions-Attention Table	Maps each customer by transaction depth and attention recency
Segment language	BRTN	Best, Rest, Test, Next — canonical commercial segmentation
Recovery engine	NeoMarketing	The missing rung between CRM and Adtech (10–15%)
Sub-engine	Atrium	Restores attention on weakening and lost cells
Sub-engine	Meridian	Converts restored attention into transactions; maximises LTV
Sub-engine	NeoNet	Cooperative recovery and acquisition across brand boundaries
Sub-engine	ActionAds	Monetises non-transacting attention; funds the recovery layer
Operational moves	The Seven Alpha Plays	Interventions that move customers and transactions
Governance layer	AOS Dashboard	Ten metrics measuring Tax, Time, and Alpha above Beta

Why not the alternatives

Three names presented themselves as candidates. Rejecting each one sharpens AOS.

Not NeoMarketing — too narrow. NeoMarketing names a specific engine inside the framework: the recovery layer between CRM and Adtech. Naming the whole framework after one of its parts collapses the architecture. The Tax Ladder is not NeoMarketing. The TAT is not NeoMarketing. The Alpha-above-Beta accounting is not NeoMarketing. If the umbrella is called NeoMarketing, the diagnostic work gets mistaken for a product pitch, and that weakens the framework’s trust with finance audiences. AOS can include NeoMarketing without being reduced to it. AOS preserves hierarchy.

Not Alpha Ladder — metaphor collision. The phrase has rhetorical power — every brand is on the Alpha Ladder; the question is whether customers are climbing or falling — but the framework already contains a ladder, and that one is the Revenue Tax Ladder. Calling the umbrella also a ladder forces the reader to disambiguate every time the word appears. Which ladder do you mean? That ambiguity costs more than the rhetorical gain. There is a deeper structural problem: a ladder is a single-axis metaphor, up or down. The framework is explicitly two-dimensional. Transactions move down the Tax Ladder along one axis; customers move leftward and downward through the TAT along a different two-axis pattern. The umbrella metaphor must accommodate both movements. Ladder does not. AOS preserves dimensionality.

Not Alpha Marketing OS — caps the ceiling. Adding Marketing to the name solves a real anchoring problem — the reader knows immediately what discipline the framework belongs to. But the cost is a cap on the framework’s intellectual range. The framework is genuinely larger than marketing as a department. The Tax Ladder is customer economics. The TAT is customer-state engineering. The Alpha-above-Beta measurement is finance language. Marketing operates the framework, but the framework is not about marketing in the way that media-mix modelling is about marketing. It is about the economics of the customer base. CFOs and CEOs should be able to own the language too. The word Marketing can sit in the subtitle and the sales copy. It does not need to sit inside the name. AOS preserves the ceiling.

Three rejections, three features preserved: hierarchy, dimensionality, ceiling. AOS is what remains when all three constraints are satisfied.

3

What Changes when the System has a Name

Naming is not vanity. It is a coordination mechanism that turns a long-form thesis into something operationally tractable across multiple constituencies. Four conversations change when AOS becomes a noun.

The CMO conversation. AOS turns scattered concerns into one operating language. Rising CAC, discount dependency, weak repeat performance, marketplace leakage, declining CRM reach, lapsed Best customers, retargeting waste — these stop being seven separate symptoms requiring seven separate diagnoses and become measurable movements inside one system. The CMO can now describe quarterly performance in one frame: Tax reduced, Time compressed, Weakening Pool stabilised, Alpha generated. One operating language replaces seven disconnected dashboards.

The CFO conversation. A CFO reading a slide that says “We are implementing the Alpha Operating System” is not in the same conversation as one reading “We are trying a new marketing approach.” The first sentence presupposes a system being deployed, with measurable outputs, against a baseline. The second sentence triggers the “yet another marketing initiative” filter that CFOs apply to protect their attention. The question moves from whether marketing generated revenue to what tax was paid to generate it and whether the uplift exceeded the Beta baseline. That makes the framework board-ready and budget-defensible in a way unnamed marketing thinking is not.

The agency and partner conversation. Today’s standard contracts pay agencies against impressions, clicks, ROAS, or campaign-level revenue — proxies for outcome rather than outcome itself. Under AOS, the contract can be written against Alpha Generated, audited through the AOS Dashboard, with the agency receiving a Carry on Alpha above Beta. Work gets tied to specific measurable movements: reducing Paid Repeat Leakage, shifting repeat transactions from Adtech to CRM, recovering R1 cohorts before paid media, reducing Offer Tax, accelerating N to T and T to B. The pricing model already exists in finance — Beta + Alpha + Carry is exact hedge-fund economics. Without the system named, the contract has no anchor; with the system named, the contract has a referent.

The vendor conversation. A martech vendor stops selling features (email volume, push reach, search relevance) and starts selling an operating system. The features become the components that operate AOS — but the customer is no longer purchasing email-sending capacity, they are purchasing the system that produces Alpha through whichever components are needed. That is a different market category, addressed to a different buyer (CMO and CFO jointly, not just the head of email), at a different price point (outcome-based, not seat-based). The name is what makes that repositioning sayable.

In each of these four conversations, the framework existed beforehand. The conversations changed only because the framework acquired a noun the four constituencies could refer to in common. That is what naming does. It is the lowest-cost, highest-leverage coordination move available to any framework once it has the substance to justify the noun.

The honest caveat

A name is necessary, but it is not sufficient. AOS will matter only if it can be run. It must classify real transactions, map real customers, trigger real interventions, and produce measurable Alpha above a pre-agreed Beta baseline. Otherwise it becomes another elegant framework that lives in a deck.

The next step after naming is proof. A CMO should be able to run an AOS audit in thirty days. Classify the last quarter’s transactions into the Seven Buckets. Calculate Effective Transaction Tax per bucket. Identify Paid Repeat Leakage. Build the first TAT distribution. Size the B–, T– and R1 pools. Estimate the Alpha opportunity. Then run a ninety-day pilot on one or two Alpha Plays — typically Play 6 (Shift Repeat Adtech to Owned, deployable within existing CRM stack) and Play 4 (Protect Best from Becoming Rest, the highest-ROI move on the grid). Measure against pre-agreed Beta. Book Alpha only against what beats the baseline.

This is the correct sequence. The D2C Tax-onomy essay built the framework. This essay gives it a name. The workbook that follows makes it operational. The name is not the end of the work. It is the point at which the work can finally travel.

The framework had to be built before it could be named. Now that it has a name, the next work is building proof.

Alpha Operating System.  Buy New efficiently. Own Repeat completely. Recover before paying twice.

The New D2C Dashboard

Every framework eventually has to land on a dashboard. The Revenue Tax Ladder, the TAT, the missing rung, the seven plays — none of these matter if the Monday morning review still reports total revenue, blended ROAS, and aggregate LTV. A brand that cannot read its revenue and its customers at the level the framework demands cannot run the framework. It can only describe it.

Most D2C dashboards are built for activity and attribution. They show revenue, orders, CAC, ROAS, conversion rate, repeat rate, AOV, channel contribution, campaign performance, and cohort retention. These metrics are useful — they answer the question what happened? They do not answer the Alpha question: what tax did we pay, how long did the customer take, and what state did the customer move to?

Ten metrics — five about revenue and tax, five about customers and time — translate every framework in Parts 2 through 6 into something the brand can measure quarterly, monthly, weekly.

The Tax half of the dashboard

1. Revenue by seven buckets. Every transaction assigned to one of the seven buckets — Intermediated, New Direct Organic, New Direct CRM, New Direct Adtech, Repeat Direct Organic, Repeat Direct CRM, Repeat Direct Adtech. This is the base table. Without it, the brand cannot distinguish good revenue from expensive revenue. Total revenue hides composition. Bucket revenue reveals quality. The first question in every review should be: how much revenue came from each bucket, and how is the mix shifting quarter over quarter?
2. Effective Transaction Tax. Route Tax plus Offer Tax, calculated per transaction, averaged across the bucket. A Repeat Direct CRM bucket showing a 5–10% Route Tax but a 25–30% Effective Tax is silently running adtech economics through its own email list. The CFO and the CMO must see the same number. Either show both, or stop pretending owned channels are cheap.
3. Paid Repeat Leakage. The single most diagnostic metric in the dashboard.

Paid Repeat Leakage = Repeat Direct Adtech Revenue ÷ Total Direct Repeat Revenue

A low number means the brand owns its repeat engine. A high number means the brand is paying again for customers it already had. A Paid Repeat Leakage above 30% in any quarter is a structural relationship failure, not a campaign performance success. Every CMO should know this number. The standard ad-platform dashboard will not report it; the brand has to build it.

4. Owned Repeat Ratio. The mirror of Paid Repeat Leakage.

Owned Repeat Ratio = (Repeat Direct Organic + Repeat Direct CRM) ÷ Total Direct Repeat Revenue

This is the cleanest single measure of whether the brand’s CRM is actually doing the job it claims to do. A strong D2C brand should see this ratio rise over time. If it falls, the brand is becoming more dependent on rented attention even for existing customers.

5. Identity Capture (% of all transactions converted to Direct ID, by surface). What percentage of total revenue is happening on surfaces the brand does not control? Intermediated revenue may be necessary and profitable, but if its share rises without a parallel identity-capture strategy, the brand is building sales without building relationships. Pair this metric with Identity Capture Rate — for every platform sale, what percentage of customers were converted into direct identity within 30 days through QR codes, warranty registration, NeoMail subscription, replenishment club, or Mu offers? The goal is not to fight the platform. The goal is to prevent every platform customer from remaining permanently platform-owned.

The Time half of the dashboard

6. TAT distribution. What percentage of the customer database currently sits in each of the nine TAT cells? The healthy distribution has weight in N, T, and B (the Strong column), modest counts in N–, T–, B– (the Weakening column, accepted as inevitable but managed), and a controlled R1 + R2 pool (the Lost column, sized to be recoverable on the NeoMarketing rung). A distribution heavy on the right two columns is an attention crisis the transactions dashboard will report six months later. A brand can have a good quarter and still be creating next quarter’s AdWaste.
7. Weakening Pool — B– plus T– counts. The two cells where intervention costs are lowest and ignored intervention costs are highest.

Weakening Pool = B– customers + T– customers

These are customers with purchase proof and weakening attention — not yet lost, not yet expensive to recover, but on the slope. If the weakening pool grows, the CRM team must change strategy from Sell to Relate. This is the metric that should appear on the CMO’s dashboard before any acquisition number.

8. R1 Recoverable Value and Recovery Conversion Rate. Not all Rest is equal. R1 is the high-priority recovery pool: former Best customers who have lost attention. The dashboard should show R1 count, R1 historical revenue, expected future LTV if recovered, and the cost of recovery through owned, NeoMarketing, and adtech routes. This turns recovery from a campaign idea into a capital-allocation decision.

Paired with the value metric is the conversion metric:

Recovery Conversion Rate = (B– → B conversions via Meridian) ÷ (R1 → B– attention recoveries via Atrium)

This is the cleanest possible split between the two engines’ contributions. A high Atrium recovery rate with a low Meridian conversion rate says the brand is good at restoring attention but bad at monetising it — a Meridian problem. A low Atrium recovery rate with a high downstream conversion says the brand is good at converting attention when it has it, but not good at restoring it — an Atrium problem. Without separating the two, the dashboard cannot tell which engine to fix.

9. Time-to-Next-Transaction. The clean operational expression of the Time lever from Part 1, measured per state transition rather than as a single median:

N → T: time from identity to first transaction T → B: time from first or second purchase to Best B → B–: time from strong attention to weakening B– → R1: time from weakening to lost R1 → B or T: time from recovery to active state

A brand should not only ask whether customers repeat. It should ask how quickly they repeat, through which route, and at which transition the system is slowest.

10. Alpha Generated. The headline outcome metric. The uplift in (Revenue minus Effective Tax) times Frequency, measured above the brand’s pre-agreed Beta baseline, attributed honestly to the NeoMarketing interventions. Alpha cannot be claimed against zero; it can only be claimed above what the brand would have done anyway. Some customers would have repeated regardless. Some paid campaigns would have worked regardless. Alpha is only the improvement above that expected path. If Alpha is rising, the framework is working. If Alpha is flat while total revenue rises, the brand is growing Beta, not Alpha.

The dashboard as governance

The ten metrics together produce a different kind of weekly review.

The old dashboard asks: revenue is up, ROAS is healthy, campaigns performed. The new dashboard asks: Which revenue was low-tax? Which revenue was bought? Which repeat revenue was reacquired? Which customers are weakening? Which Best customers are about to become Rest? Which platform buyers have been identified? Which discounts are hiding inside CRM? Which customers moved down the TAT? Which customers drifted right? How much Alpha was created above Beta?

That is a different conversation entirely. One in which the CFO and the CMO are looking at the same numbers, the procurement officer and the head of growth are aligned on what each channel is genuinely worth, and the agency partner can be paid against Alpha rather than against impressions. This is the operating system the framework has been building toward.

The Tax-onomy of Transactions in Parts 2 and 3 was the diagnostic. The TAT in Part 4 was the customer map. The missing rung in Part 5 was the engine. The seven Alpha plays in Part 6 were the playbook. The dashboard in this part is the governance.

A D2C brand running this system has answered the question the essay opened with: where does Alpha come from when Beta belongs to everyone?

It comes from paying less tax per transaction, from reducing the time to the next transaction, and from never paying twice for a customer the brand already owned. It comes from running the brand’s marketing not as a channel mix but as a portfolio of customer states, each priced and managed for the specific Alpha it can generate.

The road to Alpha is now visible. It has been visible since Part 1. But it was not walkable until the framework — Ladder, TAT, missing rung, plays, dashboard — was complete.

Buy New efficiently. Own Repeat completely. Recover before paying twice.

The Seven Alpha Plays – 4

Play 7 — Monetise Non-Transacting Attention. From N, N–, R2, some L to attention revenue. Primary lever: new revenue stream. NEVER served: adjacent to Never Pay Twice.

Not every identified customer will buy soon. Some may never buy. But if they still pay attention, they still have value. Traditional CRM sees non-transactors as failed conversion opportunities. NeoMarketing sees a second possibility: attention can be monetised, safely and selectively, without destroying trust. This is the role of ActionAds inside NeoMails. A customer who opens, plays, predicts, answers, or interacts is giving the brand something valuable — attention and signal. If that customer is not ready to transact, the brand can still create value through relevant ActionAds, partner offers, samples, surveys, or lead actions. The key is that monetisation comes after attention is earned, not before. The larger point is that D2C brands have been monetising only buyers. NeoMarketing lets them monetise attention, not just transactions.

The seven plays as a system

Each play, taken alone, generates some Alpha. Taken together, they compose into a closed loop. Plays 1 and 2 create the identified database the other plays operate on. Plays 3 and 4 keep customers transacting at low tax. Plays 5 and 6 substitute high-tax routes with low-tax routes for both reacquisition and repeat. Play 7 funds the layer that makes Plays 4, 5, and 6 economically viable.

None of the plays requires giving up Adtech entirely. What they require is using Adtech for the job it is genuinely good at — legitimate New customer acquisition where no cooperative route exists — and stopping the use of Adtech as the default tool for every problem the marketing stack does not yet have a better answer for.

This is the practical meaning of the two levers from Part 1. Less Tax is not an abstract goal — it means fewer transactions in Intermediated and Repeat Direct Adtech, and more in Repeat Direct CRM and Organic. Less Time is not an abstract goal — it means faster N → T → B movement, and fewer customers sliding B → B– → R1.

The CMO’s job is no longer to run more campaigns. The CMO’s job is to move customers and transactions.

What the plays do not yet produce is the dashboard that proves they are working. That is the work of the closing part.