Reference and stewardship
What can I rely on, what is advanced and what needs refreshing?
Controlled vocabulary
| Term | Definition and what it is | What it is not |
|---|---|---|
| GTM | The work of identifying, reaching, serving and growing customers through a viable proposition and economics | Marketing channels alone |
| Growth | Improvement in economically useful customer and commercial outcomes over a stated horizon | More activity or revenue at any cost |
| Customer value | Value experienced by the customer; use “customer contribution” for enterprise economics | An unqualified synonym for revenue LTV |
| Signal | A dated observation potentially relevant to a decision | A verified explanation |
| Opportunity | An evidenced possibility for a feasible intervention to create value | An alert or idea without an owner and action |
| Decision | An accountable choice among alternatives under constraints | A recommendation or a dashboard |
| Activation | Delivery of an intervention; “customer activation” means first experienced product value | Automatically an email or a signup |
| Play | A repeatable commercial intervention with trigger, workflow, rights, measurement and learning | A prompt, tactic or vendor feature |
| Experiment | A planned comparison designed to inform a stated uncertainty and decision | Any campaign change |
| Incrementality | Difference caused by an intervention relative to an explicit counterfactual | Credited or correlated outcomes |
| Contribution LTV | Expected discounted customer contribution over a declared horizon and cost scope | Guaranteed value or a treatment effect |
| Marginal CAC | Additional expense per additional incremental customer in a defined tranche | Historical average CAC |
| Lifecycle | Governed customer relationship states and transitions | An email schedule |
| Next-best-action | Choice among eligible useful treatments, including no action, under evidence and constraints | Necessarily individual AI optimisation |
| Automation | Software performs specified repeatable work | Necessarily AI or autonomous judgement |
| Agent | A bounded system selects permitted next steps and tools dynamically using feedback | A scheduled prompt or fixed workflow |
| Autonomy | Delegated authority for a defined action without per-action approval | A whole agent’s unlimited mandate |
| Orchestration | Sequencing, state and recovery across workflow steps | A strategic brain |
| Control Plane | Optional technical shorthand for shared controls and coordination | A required custom product |
| GTM memory | Reviewed evidence and decision records with context, ownership and expiry | An unlimited AI database or automatic truth |
| Closed loop | Evaluated outcomes feed the next decision under an objective and controls | Proof of improvement or maximum autonomy |
| Optimise | Improve a declared objective within constraints; may include stopping | Constant automated adjustment |
Evidence and claim language
Use High, Medium or Low confidence in a specified proposition, not in an entire programme. For Qualified or Rejected historical claims, state confidence in the editorial narrowing or rejection and its supported boundary; never attach it implicitly to the rejected headline. “Unknown” identifies an unestablished local quantity. Accepted claims survive the editorial challenge; accepted-with-conditions claims require their stated prerequisites. Qualified claims have narrower scope. Advanced methods require additional capability. Experimental ideas need capped validation. Unresolved questions stay visible. Rejected ideas do not reappear as recommendations.
Evidence indicates a conclusion only within its method and population. Evidence suggests a direction when material uncertainty remains. Early evidence may justify testing, not a broad promise. Source inheritance does not create independent corroboration. Architectural feasibility and high confidence in an accounting identity do not establish commercial ROI.
Two cases that teach a bounded lesson
Booking.com and experiment-linked machine learning. The problem was turning model development into business improvements. The supplied research describes a primary practitioner paper about successful deployed ML applications and their experimental validation. The useful mechanism is connecting each model to an outcome and a decision. The reported outcome is production precedent across roughly 150 successful applications, not a denominator of all attempts or a pooled profit return. Evidence is a primary technical account, with selection and scale limits. Learn to evaluate the decision effect; do not infer that modern agent orchestration, a small firm or every ML project will achieve the same result. Booking.com KDD paper. Source treatment: OS §11; RT §§7,50–51. Publication: 2019 (year precision); Tier 2 practitioner evidence; not independent commercial evidence.
Unilever and product-image production. The problem was the cost and speed of imagery production. The company described a digital-twin and AI workflow that reduced production time and cost. The mechanism is a changed asset-production process, not an autonomous commercial strategy. The company-reported outcome illustrates a potential expense or throughput benefit; it does not isolate pure model causality, demonstrate incremental sales or provide a transferable return estimate. Evidence is a company case. Learn to compare accepted assets and actual purchases; do not generalise it to media, retention or an integrated GTM platform. Unilever announcement. Source treatment: OS §11; RT §50. Publication: 18 March 2025; Tier 3 company-reported evidence; not independent.
These references are carried forward from the supplied research and Red Team review. Editorial & Evidence QA checked the existing primary pages and publication metadata on 9 October 2026. This was a bounded citation check, not independent validation of commercial outcomes or a fresh audit of the full Booking.com methods. Their stated scope is preserved. The excluded Uber amount, provider ROAS claims and universal uplift ranges do not enter any investment model.
Technical implementation notes
For a justified machine-executed action, preserve the link from decision/version to approval, exact action, platform receipt, exposure, outcome and evidence. Bind approval to the material action fields. Recheck current permission, destination, state and cumulative limits before execution. An indeterminate platform result requires a state query and reconciliation before retry; a successful API response is not necessarily a delivered customer outcome. Keep manual or native fallback and a named restart authority. sourcesSYS §§15,20–22,25AI Augmented GTM Systems Architecture — Systems architecture; proposed patterns, not an audited deployment.AGT §24 and contract packAI Agent and Automation Operating Architecture — Automation architecture; explicitly no proven commercial agent result.Evidence for this chapter · 12 claim records
For a justified predictor, record objective, target, horizon, population, training/holdout periods, leakage tests, feature provenance, calibration, missingness, relevant subgroup performance, version, owner, drift trigger and fallback. For uplift, add identification and treatment-policy evaluation. For generated summaries, verify source fidelity and missed/contradictory evidence. These are different evaluations.
The specialist sources retain detailed API schemas, identity patterns, statistical methods and security controls. Consult SYS §§23–28 and AGT’s Implementation Contract Pack only after the chosen Play requires those capabilities. The five working artefacts remain the operational record of what was actually configured.
Open issues and design choices
The following remain unresolved locally: additional AI profit, coordination value, five-year ownership cost, measurement power, cohort forecasting quality, available treatments, budget mobility, reviewer capacity, native platform adequacy, customer acceptance, memory reuse and the value of greater autonomy. The Editorial Synthesis Report’s issue register records why each matters, required validation and the consequence of error.
Unresolved Design Choice: choose a CRM/export approach when one workflow can be supported economically; choose shared analytical services when several funded workflows need consistent joins and economics. Choose embedded execution with shared standards as the initial organisation; consider a shared team only for recurring coordination demand. Choose rules and cohorts when treatment evidence is sparse; consider individual treatment models only when the evidence and extra value support them. No universal architecture or team structure resolves these context-dependent choices.
Additional Research Required: before financial commitment, obtain actual data, costs, licensed-tool tests and authority evidence. Before using an excluded public number, verify its original method and cost basis. A missing input remains unknown; it is not an invitation to insert a market-average uplift.
Version and review policy
| Content | Review tag | Review trigger and owner |
|---|---|---|
| Economics, measurement distinctions and operating principles | Durable | Editorial/Finance/method owner reviews when definitions or methods materially change |
| Play mechanisms, capability map and operating roles | Review annually | Commercial owners review outcomes, context and obsolete work |
| Model validation, workflow and architecture choices | Review 6-monthly | Technical and business owners also review on data, model, API or policy change |
| Agent permissions, AI capabilities and discovery observations | Fast-moving | Verify at implementation and before authority changes; suspend on invalidated assumptions |
| Local evidence and forecasts | Decision-specific | Review on population, product, price, channel or policy change and at the recorded expiry |
Update a claim, its linked Play, tool and evidence record together. Keep the old version and reason for change. Reopen a rejected recommendation only with explicit evidence and an editorial verdict, not a renamed feature.
An advanced GTM organisation knows which customer problems it can change, values them honestly, gives people authority to act, and learns within the limits of its evidence. Its AI performs useful, bounded work. Its operators can stop, recover and simplify the system. Its advantage, where it exists, comes from better interventions and the ability to repeat them economically.
Build the necessary system. Prove the additional value. Automate what earns automation. Retain what improves the next decision. Repeat.
Related
Evidence for this chapter12claims reviewed, with confidence ratings, limits and sources.
Claim classifications
Accepted means a principle or mechanism survived critical review, not that it guarantees a return. Accepted with conditions means prerequisites apply. Qualified means the original claim has been narrowed. Advanced needs substantial readiness. Experimental needs a capped comparison. Unresolved means the evidence cannot settle the claim. Rejected means the recommendation is excluded.
High, Medium and Low describe confidence in the stated target, not the chance of a positive ROI. For a Qualified or Rejected historical claim, confidence applies to the decision to narrow or reject it and to the supported limit—not to the original headline. Read the headline and classification together. An accounting identity or design principle is not empirical evidence of a commercial outcome. Follow the linked chapters, Plays and tools to see where each claim applies.