Marketing is a system,
not a department.
Nine modules, one operating system: how CHARLESGATE differentiates, attracts, earns, wins, and repeats. Work through the Academy in order, keep it open as a reference forever, and mark lessons complete as you go — progress is shared with the team.
Lesson format: first principles → why it matters → how it works → CHARLESGATE example → do the work. One lesson is a 15–25 minute read. Suggested cadence: one lesson a week, discussed as a team, workbook exercise done for real.
The Growth Code
CHARLESGATE's canonical growth system — the five stages, the flywheel, the operating cadence.
CHARLESGATE's Canonical Growth System
Status: v1.1 — August 2026. Naming settled: The Growth Code. Stage definitions updated to match field use at CPM (Attract = attract attention; Earn = earn pipeline; Win = win the deal). The one-page ruling on definitions and gates: CG_Growth_Code_v1.1_Canon.md.
The One-Page Version (Put This on the Wall)
### THE GROWTH CODE Different attracts. Earned wins. Repeat.
1. DIFFERENTIATE — Choose who you serve and what only you can claim. Positioning, ICP, offer, message. 2. ATTRACT — Attract attention. Get known by right-fit buyers before they're in-market: content, paid, events, owned audience. 3. EARN — Earn pipeline. Turn attention into qualified opportunities: outbound, ABM, nurture, hand-raiser follow-up. Trust is earned person by person, before the ask. 4. WIN — Win the deal. Qualified opportunity to signed and onboarded: clear offers, one narrative, disciplined follow-through. 5. REPEAT — Compound every relationship. Retain, expand, refer, review — then feed it all back into stage 1.
Every campaign, every piece of content, every dollar of spend must be able to answer: which stage of the Code are you moving, for which ICP, and how will we know it worked?
Naming: Three Options, One Recommendation
The spine stays: Differentiate → Attract → Earn → Win → Repeat. The question is what we call the system.
| Option | Rationale | Risk |
|---|---|---|
| 1. The Growth Code recommended | Extends CHARLESGATE's existing "Code" language (Brand Codes, "creativity + the Code is the moat"). One system family: Brand Code = who we are; Growth Code = how we grow. Ownable, wall-worthy, zero corn. "That's not in the Code" becomes usable shorthand. | Requires discipline not to dilute "Code" across too many internal artifacts. |
| 2. The Earned Growth Engine | Leads with Michael's core principle — earned, not borrowed. Describes the mechanics honestly (it's an engine/flywheel, not a funnel). Strong external/differentiator framing for pitches: "our proprietary Earned Growth Engine." | Longer; less chantable internally; "engine" is common consultant-speak. |
| 3. The Compounding Five (tagline: Different attracts. Earned wins. Repeat.) | Emphasizes the flywheel math — each stage compounds the next. Numeric names travel well ("run the Five on this account"). | Least distinctive; "five things" frameworks are everywhere. |
Recommendation: The Growth Code. It's the only option that plugs into language CHARLESGATE already owns, it names the system (which is the moat), and it works both internally (training, reviews) and externally (a proprietary system clients can't get elsewhere). Keep "Different attracts. Earned wins. Repeat." as the motto under any name.
Why a Code, Not a Funnel
Two first-principles observations drive the whole design:
- Funnels leak; flywheels compound. A funnel treats every closed deal as an ending. In our business — property management contracts, developer relationships, investor repeat business — the second transaction is the cheapest revenue we will ever earn, and a happy client is simultaneously a retention asset, a referral source, a review, a case study, and a cross-OpCo lead. A system that doesn't explicitly harvest that is leaving our best economics on the table.
- AI pulls everyone to the middle. When every competitor can generate competent-sounding marketing in seconds, "competent" becomes worthless. The 2026 data backs this up: buyers are measurably less likely to consider vendors whose outreach feels synthetic, and creative/brand has become the most powerful form of targeting. What can't be generated: a genuinely different position, proof earned over thousands of doors and dozens of sell-outs, real relationships, and a proprietary operating system. That's the moat. The Growth Code is the system half of "creativity + the Code."
The Code is B2B-first (owners, developers, investors, institutions) but steals the best of B2C — brand, emotion, attention, creative — deliberately rather than accidentally. Module 1, Lesson 7 of the training program teaches exactly what transfers and what doesn't.
The Five Stages
STAGE 1 — DIFFERENTIATE
Be the obvious choice for somebody, not an option for everybody.
Definition. The strategy stage. Decide — on evidence, not vibes — who your best-fit customer is, what alternatives they'd otherwise choose, what you can claim that competitors provably can't, and how you say it. Everything downstream (content, campaigns, sales) inherits from this stage. Weak here = expensive everywhere else.
Strategic job. Convert "we're a great full-service firm" (a claim everyone makes) into "for [specific ICP], we are the only [category] that [distinct capability], which means [value they care about] — and here's the proof." April Dunford's core insight, and ours: positioning is context-setting. Buyers evaluate you against alternatives — including doing nothing — and if you don't set the frame, the incumbent or the cheapest option sets it for you.
Core questions this stage answers:
- Who is our best-fit customer (ICP), and who are we willing to not serve?
- What would they do if we didn't exist? (Status quo counts as a competitor.)
- What capabilities, expertise, relationships, or proof do only we have?
- What value does that create that this ICP actually cares about?
- What is our one-liner, our story, and our offer — in approved, written-down words?
Key plays / motions that live here:
- Positioning Canvas per OpCo / service line (Dunford method — workbook template 1)
- ICP definition + tiering; named account lists (feeds ABM in Attract)
- Messaging Document — approved boilerplate, value themes with proof, competitive responses (Dunford's messaging doc structure; template 3)
- Offer architecture — productized, named, risk-reversed offers (Hormozi value equation; template 4)
- Category POV: the editorial stance we take in public (feeds Earn)
Metrics that matter: win rate vs. named alternatives · % of deals where we set the criteria vs. respond to theirs · price/fee premium held without discounting · message consistency audit (does every rep and page say the same thing?) · shortlist inclusion rate for tier-1 ICP accounts.
Connects forward: Differentiate is the input to every other stage. A campaign without a positioning decision behind it is just noise with a budget.
STAGE 2 — ATTRACT
Attract attention. Get discovered by the right buyers before they're in-market.
Definition. The attention stage: marketing awareness + lead gen. The relationship state here is an audience — they don't know us yet, or know of us but we've never talked. Make the right people know we exist, with the right association attached, before they have a signed problem. In B2B, roughly 95% of your market is not buying right now (the Ehrenberg-Bass / LinkedIn B2B Institute "95:5" finding). Attract is how you win the 95 so you're on the shortlist when they become the 5. Trust assets get produced here (honest answers, proof, case studies, all public); they get deployed 1:1 in Earn.
Strategic job. Build mental availability: when a Boston developer thinks "sell-out risk," a condo board thinks "our manager isn't responsive," an investor thinks "who actually knows this market" — CHARLESGATE surfaces automatically. Attention is a prerequisite for trust; you can't earn what you never got.
Core questions:
- Where does our ICP already spend attention (rooms, feeds, inboxes, events, search/AI answers)?
- What creative and POV will make them stop — and remember us for the right thing?
- Which motions fit each OpCo: content-led, outbound, ABM air-cover, events, founder-led, partner?
- Are we reaching future buyers (the 95%) or only chasing the in-market 5%?
Key plays / motions:
- Content-led attention: TAYA-grade answers, market data, editorial POV (CHARLESGATE's existing strength — extend it)
- Founder/personality-led: Michael + OpCo leaders as visible, opinionated market voices (Gerhardt: people follow people, not logos)
- ABM tier-1: named-account campaigns for developers/institutions (Full-Funnel/Zinkevich model; HubSpot ABM blueprint in the resource library)
- Outbound: relevant, researched, human — never synthetic-feeling (45% of 2026 buyers penalize synthetic outreach)
- Events/community: broker breakfasts, developer roundtables, board-member education
- SEO → AEO: be the cited answer when buyers ask Google or an AI assistant
- Paid as amplifier of proven organic — performance follows creative, not the reverse
Metrics: qualified reach within ICP (not vanity reach) · branded search + direct traffic trend · engaged target accounts (ABM) · audience owned (followers→email list) · share of voice on our themes · event/community participation by ICP · % of new opportunities that say "we already knew you."
Exit gate (Attract → Earn): a hand-raiser (= MQL: an ICP-fit contact who took a written hand-raise action such as scorecard completion, review request, webinar attendance, or a worked guest list) or the first 1:1 named-account touch. The moment we're talking to a person instead of an audience, they're in Earn.
Connects forward: Attention without trust is a billboard. Attract hands warmed, right-fit people to Earn.
STAGE 3 — EARN
Earn pipeline. Trust is earned, not borrowed: person by person, before the ask.
Definition. The pipeline stage: sales + ABM + nurture. The relationship state here is a known person who is not yet a qualified opportunity. Turn hand-raisers and named-account contacts into real conversations, and real conversations into qualified opportunities: outbound, broker and partner channels, hand-raiser follow-up, 1:1 content sends, discovery. The trust doctrine still governs the stage (Sheridan's They Ask, You Answer built the assets in Attract); here those assets get deployed — the distribution kit is what turns a piece of content into an ABM touch. We earn the right to pitch before we pitch.
Strategic job. Collapse perceived risk and prove intent before the formal sales process starts. B2B real estate decisions are high-stakes, committee-approved, career-attached. The vendor that has already answered the hard questions honestly — pricing, problems, comparisons, "who we're NOT for" — walks into qualification pre-trusted. Sheridan's evidence and ours: the prospect who consumed our honest content closes faster and negotiates less.
Core questions:
- Which named accounts and hand-raisers are we touching this week, at what quota, with what sequence — and is it logged same day?
- What does a hand-raiser get within 24 hours, and who owns the response?
- What earns a next step short of a proposal — assessment, benchmark, performance review, tour?
- What is our qualification standard (problem, authority, urgency, economics, fit), and who logs it, when?
Key plays / motions:
- Named-account outbound: weekly quotas, one sequence with segment flavors, same-day logging
- ABM tier programs: ACTIVE / WARM / WATCH treatment levels (Full-Funnel/Zinkevich model)
- Broker and partner channel: named partners, a cadence, a real value exchange
- Hand-raiser conversion plays: 24-hour response standard, discovery-call targets per source
- Distribution kits: 1:1 sends of trust assets to named accounts (produced in Attract, deployed here)
- Nurture sequences mapped to journey stage, not blast email; lead magnets with real value (Hormozi: make the free thing better than competitors' paid thing)
- Relationship plays: multi-year cultivation of tier-1 accounts (People-first GTM workbook in the library)
Metrics: first conversations booked · touches to named accounts + booking rate · lead-to-opportunity conversion · qualified pipeline added (units/$) · hand-raiser response time · % of inbound that arrives pre-sold (self-reported attribution — often truer than software).
Exit gate (Earn → Win): passes the qualification standard and is logged in HubSpot as a qualified opportunity, same day. Not before.
Connects forward: Earn delivers pre-trusted, qualified opportunities to Win — which is what makes Win cheap.
STAGE 4 — WIN
Win the deal. Convert qualified opportunities into signed business without discounting your way there.
Definition. The sales-process stage. The relationship state here is a qualified opportunity that is not yet a client. Starts the day an opportunity clears the Earn gate; ends signed AND onboarded. The offer, the pitch, the proposal, the follow-through, the close. Phase 1 covers the marketing side (offers, enablement assets); Phase 2 (Sales) will build this stage out fully.
Strategic job. Make buying easy and differentiated. Most deals aren't lost to competitors — they're lost to indecision and the status quo. The Win stage exists to give a champion everything they need to sell us internally: a clear offer, a story that frames the alternatives honestly (Dunford's Sales Pitch structure — already in the resource library with worked examples), proof for the committee, and risk reversal for the skeptic.
Core questions:
- Is our offer clear, named, and comparable to nothing? (If procurement can commoditize it, we built it wrong.)
- Does our pitch teach the buyer how to choose — market insight → alternatives → our difference → proof — or just list features?
- What does the buying committee need that our champion can't say for us?
- Where do deals stall, and what asset or play unsticks each stall point?
Key plays / motions:
- Offer design: named packages, guarantees where we control outcomes, clear scope tiers
- The CHARLESGATE sales narrative per OpCo (Dunford Sales Pitch method: insight → alternatives map → "perfect world" → us)
- Enablement kit: one-pagers, case studies by ICP, competitive responses (approved wording, Dunford doc Section 4), proposal templates
- Deal acceleration kits (case study + reference offer, tuned to the stall point) on every late-stage deal, with an SLA
- Close discipline: every open opportunity carries a dated next step; nothing sits 14 days without one
- Pipeline hygiene + deal reviews against ICP fit (kill bad-fit deals early — that's positioning discipline, not lost revenue)
Metrics: opportunity→close win rate · proposal win rate · sales cycle length · pipeline coverage (≥3x remaining target) · CAC by motion/channel · discount frequency/depth · % of pipeline that is ICP tier-1/2 (fit quality).
Exit gate (Win → Repeat): signed AND onboarded. Not just signed.
Connects forward: A won deal is not an outcome; it's an asset. Win hands relationships to Repeat with expectations set correctly (over-promising is a Repeat-stage tax).
STAGE 5 — REPEAT
The second deal is the cheapest. Compound the relationship.
Definition. The compounding stage — the reason this is a flywheel and the HoldCo's structural advantage. Retain, expand, cross-serve, and convert happy clients into referrals, reviews, case studies, and market intelligence. Then feed all of it back into Differentiate (sharper proof, sharper ICP) and Attract (advocates make noise we don't pay for).
Strategic job. Monetize the HoldCo structure. One relationship, four engines: a developer we sell out (CRG) needs management (CPM), marketing (AFF), and capital for the next project (CG Capital). An investor CPM manages will buy and sell through CRG. Nobody else in this market can run that play — but only if it's a system with owners, triggers, and metrics, not a hallway hope.
Core questions:
- Which current clients have unserved needs another OpCo solves — and who owns making that introduction this quarter?
- What is our referral play (not "we appreciate referrals" — an actual play with a trigger, an ask, and a thank-you)?
- Which wins become case studies, reviews, and brag points this quarter?
- What are clients telling us that should change our positioning, offers, or ICP?
Key plays / motions:
- Cross-OpCo flywheel map: defined triggers (e.g., sell-out closing → CPM proposal within 30 days) with named owners
- QBRs / annual owner reviews that surface expansion and referral moments
- Referral engine: systematic ask at peak-satisfaction moments; partner referral loops (attorneys, lenders, architects)
- Review generation cadence; case-study pipeline (every flagship win gets documented)
- Voice-of-client loop: structured feedback → quarterly positioning/offer review (closes the loop to Stage 1)
Metrics: revenue retention (gross + net) · % revenue from existing relationships + referrals · cross-OpCo attach rate (clients using 2+ OpCos) · LTV:CAC by ICP · reviews/quarter · case studies/quarter · referral-sourced pipeline.
Connects forward: Repeat → Differentiate (proof and client intelligence sharpen the position) and Repeat → Attract (advocates, reviews, and case studies are attention we earned). The wheel spins faster each cycle. That's the compounding.
How the Flywheel Actually Spins
┌──────────────────────────────────────────────┐
│ proof, intel, advocates feed back │
▼ │
DIFFERENTIATE → ATTRACT → EARN → WIN → REPEAT ───────┘
(the choice) (attention) (pipeline) (revenue) (compounding)
- Differentiate decides the game. Attract fills the room. Earn builds the pipeline. Win signs the deal. Repeat multiplies it — and re-arms Differentiate with proof.
- The stage boundaries are relationship states, not activity types: audience → known person → qualified opportunity → client. Each gate is a HubSpot state change with a written definition (see
CG_Growth_Code_v1.1_Canon.md). Activities overlap; the state never does. - Each stage lowers the cost of the next: sharp positioning makes attention cheaper; attention makes trust faster; trust makes closing easier; easy closes create advocates; advocates make everything cheaper.
- Diagnosis rule: find the constraint. Plenty of traffic but thin pipeline? The break is in Earn or Differentiate, not "we need more leads." Deals stall at proposal? Win-stage problem — usually an offer or narrative problem, which means it's really a Differentiate problem. The Code tells you where to look before you spend.
Operating Cadence (How a Company Runs on This)
| Rhythm | Ritual | Output |
|---|---|---|
| Annual | Positioning + ICP review per OpCo (full canvas re-run) | Updated Positioning Canvas, Messaging Doc, offer architecture |
| Quarterly | Growth Code review: metrics by stage, constraint diagnosis (score each stage 1–10, evidence required), campaign planning | 1-page plan per OpCo: the constraint stage + 2–3 campaigns against it, each written as a Growth Hypothesis (hypothesis · concentration · failing trigger — see the Canon doc) |
| Monthly | Scorecard review: the stage metrics above, one page per OpCo | Kill/scale decisions on plays |
| Weekly | Play execution standup; content + pipeline review | Shipped work |
What Makes This Ours (the Differentiator Claim)
- Earned, not borrowed is built into the architecture — Earn is a stage, not a tactic.
- The cross-OpCo flywheel is structurally uncopyable by single-line competitors.
- Proof-fed positioning: Repeat formally feeds Differentiate, so the position sharpens every cycle instead of going stale.
- AI-era stance: AI runs inside the Code (leverage on production, research, personalization); the Code itself — the choices, the creativity, the relationships, the proof — is the part AI can't commoditize.
Sources & Lineage (Synthesized, Not Borrowed Wholesale — Where Thinkers Conflict, We Took a Position)
- April Dunford (Obviously Awesome, Sales Pitch, messaging document template — all in Michael's Drive library): positioning method, messaging doc structure, sales narrative. We adopt her canvas nearly whole.
- Al Ries & Jack Trout (Positioning, 22 Immutable Laws): own a word in the mind; better to be first in a category you define than fourth in one you don't.
- Maja Voje (GTM Strategist — PDF + checklist in the library): motions as choices, beachhead segments; informs Attract/Win motion selection and Module 3.
- Marcus Sheridan (They Ask, You Answer): the Earn stage's content spine; CHARLESGATE already practices TAYA — the Code institutionalizes it.
- Andrei Zinkevich / Full-Funnel (+ HubSpot ABM blueprint in the library): ABM as full-journey account programs, not ad targeting.
- Alex Hormozi ($100M Offers, $100M Leads): value equation, offer design, lead magnets that out-value paid products.
- Donald Miller (StoryBrand): customer-as-hero message structure — used in Earn/Win copy, subordinated to Dunford positioning (where they conflict, positioning wins; story is the delivery vehicle).
- Dave Gerhardt (Founder Brand, Exit Five): founder-led media, brand as B2B advantage.
- Gary Vaynerchuk: attention as the asset; native content; volume with a POV.
- Binet & Field / Ehrenberg-Bass / LinkedIn B2B Institute: 95:5, brand + activation balance (~60/40 as a long-run heuristic), mental availability — the evidence base for making Attract about future buyers, not just leads.
- 2026 field data (Demand Gen Report 2026 B2B trends; LinkedIn B2B Institute): 96% AI adoption, buyer penalty for synthetic outreach, creative-as-targeting — the evidence behind the AI-era stance.
The Growth Code v1.1 — Canonical Definitions
The v1.1 ruling: canonical stage definitions, the three gates, and Growth Hypotheses — what settles every boundary question.
Overview
What this is: the one page that settles what the five stages mean, where each one ends, and who owns it. Updated August 2026 to match how CPM actually runs the Code in the field. If any doc, deck, or meeting debate conflicts with this page, this page wins.
The Code: Differentiate → Attract → Earn → Win → Repeat. Different attracts. Earned wins. Repeat.
The Rule that Makes the Stages Work
A stage is a relationship state, not an activity type. Activities cross stages all day. A relationship can only be in one state at a time, and HubSpot records the state. If you can't say which stage a contact is in, the CRM record is wrong: fix the record, not the definition.
The Five Stages
1. DIFFERENTIATE — make the choices
Who we serve, who we don't, what only we can claim, how we say it, and what we sell. This lives in the Brand Code. It's not a pipeline stage: it's the settings every other stage inherits. Weak here = expensive everywhere else.
- Core question: why should our ideal customer choose us over every alternative, including doing nothing?
- Owner: the president, with marketing. Refreshed annually, or when the market forces it.
2. ATTRACT — attract attention
State: an audience. They don't know us yet, or know of us but we've never talked.
The work: marketing awareness + lead gen. Content (the Big 5, market data, POV), paid amplification, events, newsletter, self-service pages. Trust assets get produced here: honest answers, proof, case studies, all public.
- Exit gate: a hand-raiser or the first 1:1 named-account touch. The moment we're talking to a person instead of an audience, they're in Earn.
- Hand-raiser = MQL. One term, one definition: a contact who fits the ICP and took a written hand-raise action (scorecard or Presence Score completion, review or audit request, webinar attendee, worked guest list). Each OpCo writes its own list of actions and fit test; marketing and sales sign it. Took the action but doesn't fit the ICP? That's a list member, not a hand-raiser, and it doesn't cross the gate.
- Core question: where does our ICP spend attention, and what makes them stop and remember us for the right thing?
- Owner: marketing.
3. EARN — earn pipeline
State: a known person, not yet a qualified opportunity.
The work: sales + ABM + nurture. Outbound to named accounts, broker and partner channels, hand-raiser follow-up (24-hour standard), 1:1 content sends, discovery. Trust assets get deployed here: the distribution kit is what turns a piece of content into an ABM touch. We earn the right to pitch before we pitch.
- Exit gate: passes the qualification standard (problem, authority, urgency, economics, fit) and is logged in HubSpot as a qualified opportunity, same day.
- Core question: how do we earn a real conversation and prove intent before we pitch?
- Owner: sales, with marketing running the nurture machinery.
4. WIN — win the deal
State: a qualified opportunity, not yet a client.
The work: the sales process proper. The narrative (insight → honest alternatives → us + proof), proposals, acceleration kits, references, negotiation, signature. Coverage stays at 3x. No deal sits 14 days without a dated next step.
- Exit gate: signed AND onboarded. Not just signed. Over-promising here is a tax Repeat pays later.
- Core question: what makes yes the lowest-risk, highest-value choice at the moment of decision?
- Owner: sales.
5. REPEAT — compound the win
State: a client.
The work: proof capture at the moments it's earned (onboarding, renewal, stabilization), referral asks at peak satisfaction, one expansion thesis per active client, cross-OpCo triggers with named owners and SLAs. Everything feeds back: proof sharpens Differentiate, advocates fuel Attract.
- Core question: which current client has an unserved need, and who owns that introduction this quarter?
- Owner: whoever owns the account. Every happy client appears somewhere on this page of the plan, with a name and a date next to it.
The Three Gates (the Whole Answer to "but There's Overlap")
- Audience → person (Attract → Earn): hand-raiser (= MQL: ICP fit + a hand-raise action) or first named-account touch.
- Person → qualified opportunity (Earn → Win): passes the qualification standard, logged same day.
- Opportunity → client (Win → Repeat): signed and onboarded.
Each gate is a HubSpot state change with a written definition both marketing and sales signed. Activities overlap constantly: content shows up in Earn, trust keeps building in Win. The state never overlaps. Measure the stages by state changes, not by which team ran the activity.
Growth Hypotheses (New in v1.1)
Every quarterly plan carries one named Growth Hypothesis per stage. A Growth Hypothesis has three parts, and it needs all three or it isn't a Growth Hypothesis, it's a wish:
- The hypothesis: "If we [action], then [how the ICP reacts], producing [number] by [date]."
- The concentration: what we're pouring resources into, and what we're explicitly ignoring to afford it. No sacrifice, no Growth Hypothesis.
- The failing trigger: the metric, the threshold, the date, and the pre-agreed action when it misses. Tripwires get decided in daylight, not in the moment.
Campaign briefs, experiment logs, and tripwires are all the same thing now: Growth Hypotheses, written in this grammar, refereed by the scorecard. A tactic that can't name its Growth Hypothesis doesn't run. (Earlier v1.1 drafts called these "Core Bets"; same thing, one name now, matching the AFF material.)
The Quarterly Constraint Check (10 Minutes, Presidents)
Score each stage 1–10, evidence required, at the quarterly review. The lowest score is the constraint, and the constraint gets the quarter's Growth Hypotheses. Diagnose before you spend: "we need more leads" is almost never the real problem.
The two standing questions, all year:
- "Which stage is constrained? Show me the stage metrics."
- "What campaign or play does this belong to?"
Companions: CG_Growth_System_Framework.md (the full wall version, updated to these definitions) · the CPM GTM Plan Template (the proven implementation) · the Brand Codes (where Differentiate lives).
CHARLESGATE Marketing Training Program
The full Academy at a glance: every module, every lesson, the rollout plan.
Full Curriculum Map — "the Growth Code Academy"
(Updated 2026-07-07: Modules 4–9 built. This file replaces CG_Marketing_Training_Curriculum_Map.md — that file was locked during the update; delete it and rename this one when convenient.)
How to read this page:
- BUILT — written in full, ready to use today.
- 🗺️ MAPPED/SPECIFIED — defined; building it is the next phase.
| Deliverable | Status |
|---|---|
The Growth Code framework (CG_Growth_System_Framework.md) | Built |
| This curriculum map | Built |
Module 1 — all 7 lessons (CG_Marketing_Training_Module_1.md) | Built |
Module 1 workbook — 7 templates w/ filled CHARLESGATE examples (CG_Marketing_Workbook_Templates_Module_1.md) | Built |
Marketing & Sales Glossary (CG_Marketing_Sales_Glossary.md) | Built |
Module 2 — all 7 lessons (CG_Marketing_Training_Module_2_Demand.md) | Built |
Module 3 — all 8 lessons (CG_Marketing_Training_Module_3_GTM_Motions.md) | Built |
Module 4 — all 6 lessons (CG_Marketing_Training_Module_4_Campaigns.md) | Built |
Module 5 — all 6 lessons (CG_Marketing_Training_Module_5_Measurement.md) | Built |
Module 6 — all 5 lessons (CG_Marketing_Training_Module_6_Brand.md) | Built |
Module 7 — all 4 lessons + Phase 2 scope (CG_Marketing_Training_Module_7_Sales_Bridge.md) | Built |
Module 8 — all 4 lessons (CG_Marketing_Training_Module_8_AI_Era.md) | Built |
Module 9 — capstone, all 3 lessons (CG_Marketing_Training_Module_9_Capstone.md) | Built |
Module 2–9 workbooks — T8–T25 + T7 v2, blank canvases w/ worked examples (CG_Marketing_Workbook_Templates_Module_2.md … _Module_9.md) | Built |
Glossary v2 — Modules 2–9 terms merged (CG_Marketing_Sales_Glossary_v2.md) | Built |
Exec track — presidents' version (CG_Marketing_Training_Exec_Track.md) | Built |
Field Module F1 — Attribution, Distribution Engine & AEO (CG_Growth_Code_Attribution_and_SEO_AEO_Module.md) + Templates T26–T28 | Built |
| Phase 2: Sales Process program | 🗺️ Scoped in Module 7 (SPICED, narrative-live, proposals, negotiation, account management) |
The lesson format (proven in Module 1): every lesson = First principles → Why it matters → How it works → CHARLESGATE example → Do the work (exercise or template). One teachable unit, ~15–25 min read, self-serve.
Program logic: Module 1 is the strategic foundation everyone takes. Modules 2–6 build the marketing skill stack. Modules 7–8 bridge to sales and the AI era. Module 9 is the capstone where each OpCo team builds its real plan. Every module ladders back to a Growth Code stage.
Module 1 — The Foundation: Strategy, Positioning & the Growth Code ✅ Built
Growth Code stage: Differentiate. The module everything else inherits from.
| # | Lesson | One line |
|---|---|---|
| 1.1 | What Marketing Actually Is | Marketing ≠ promotion. From first principles: creating and keeping customers profitably — and the strategy→tactics chain that most teams skip. |
| 1.2 | The Growth Code: Our Operating System | The five stages, why a flywheel beats a funnel, and how to diagnose any growth problem by finding the constraint stage. |
| 1.3 | Positioning: The Battle for a Slot in the Mind | Dunford's method + Ries's laws: alternatives, distinct capabilities, differentiated value — and why "full-service" is not a position. |
| 1.4 | ICP, Segmentation & Personas: Choosing Who to Win | Best-fit customers, tiering, and personas that describe buying behavior — not demographics theater. |
| 1.5 | Messaging: From Position to Words That Sell | The messaging hierarchy and document (Dunford structure + StoryBrand delivery): one approved source of truth. |
| 1.6 | Offers: What You Sell IS the Marketing | Hormozi's value equation applied to services: named, productized, risk-reversed offers that can't be procurement-commoditized. |
| 1.7 | B2B vs. B2C: What Transfers, What Doesn't | Committees, cycles, and deal math vs. emotion, memory, and creative — and why the best B2B steals from B2C on purpose. |
Module 2 — Demand: How Buyers Buy & How We Attract Them ✅ Built
Growth Code stages: Attract + Earn. The buyer-side physics of marketing.
| # | Lesson | One line |
|---|---|---|
| 2.1 | The Funnel Is a Journey (and Most of It Is Dark) | Funnel stages vs. real buying journeys; the 95:5 rule; why the dark funnel breaks attribution software. |
| 2.2 | Demand Creation vs. Demand Capture vs. Lead Gen | Three different jobs with different math — and why gating everything strangles the Earn stage. |
| 2.3 | The Channel Map: Where Attention Lives | Channels vs. mediums; owned/earned/paid/rented; choosing 2–3 channels to dominate instead of 8 to dabble. |
| 2.4 | Content Strategy & TAYA 2.0 | They Ask, You Answer as a system: the Big 5, assignment selling, and honesty as a conversion asset — upgraded for the AI-answer era. |
| 2.5 | SEO → AEO: Becoming the Cited Answer | Search still matters, but the new job is being the source AI assistants cite when a developer asks "best condo management Boston." |
| 2.6 | Performance & Paid: Amplify, Don't Rescue | Paid media as amplifier of proven messages; creative as targeting; the brand/activation budget balance (Binet & Field). |
| 2.7 | Attention & Organic Social: The Gary Vee Lesson, Applied to B2B | Native content, volume with a POV, and why underpriced attention still exists in commercial real estate niches. |
Module 3 — GTM Motions: The Playbook Library ✅ Built
Growth Code stages: Attract + Win. Each lesson: what it is → when to use it → how it works → B2B vs. B2C fit → the CHARLESGATE application.
| # | Lesson | One line |
|---|---|---|
| 3.1 | What a GTM Motion Is (and How to Choose) | Voje's framework: motions are resource-allocation choices; beachheads first; motion-market fit. |
| 3.2 | ABM: Account-Based Marketing | Full-Funnel/Zinkevich model — tiered named accounts, personalized programs; the developer/institutional play. |
| 3.3 | Inbound & Content-Led | Earning discovery at scale; CHARLESGATE's incumbent strength, systematized. |
| 3.4 | Founder & Personality-Led | Gerhardt's Founder Brand: people follow people; building Michael + OpCo leaders as market voices. |
| 3.5 | Outbound That Doesn't Feel Synthetic | Research-led, relevance-first outbound; the 2026 penalty for AI-smelling sequences. |
| 3.6 | Community, Relationship & Event-Led | Rooms, roundtables, and long-cycle relationship plays (People-first GTM); where B2B real estate is actually won. |
| 3.7 | Channel/Partner & Product-Led | Referral ecosystems (attorneys, lenders, architects) and productized self-serve entry points for a services firm. |
| 3.8 | Combining Motions into One Coherent GTM | The motion stack per OpCo: primary, secondary, experimental — and the sequencing mistakes that kill focus. |
Module 4 — Campaigns, Plays & Execution ✅ Built
Growth Code stages: Attract + Earn + Win. Where strategy becomes shipped work.
| # | Lesson | One line |
|---|---|---|
| 4.1 | The Hierarchy: Strategy → Motion → Campaign → Play → Tactic | Getting the words right so the work gets right; why "let's do a webinar" is a tactic in search of a strategy. |
| 4.2 | The Campaign Brief | One page that forces the thinking: objective, ICP, stage, message, channels, budget, success metric. (Template built in Module 1 workbook.) |
| 4.3 | Building Plays: Repeatable, Documented, Owned | Turning things that worked once into playbooks anyone can run — the self-serve scaffolding this whole program exists for. |
| 4.4 | Creative That Converts | Creative is the last unfair advantage; hooks, angles, and the editorial bar for "earned not borrowed" work. |
| 4.5 | Conversion Paths: Landing Pages, CTAs & Friction | From click to conversation; offer-message match; reducing the cost of "yes." |
| 4.6 | The Marketing Calendar & Operating Cadence | Annual → quarterly → monthly → weekly rhythm; capacity honesty; kill/scale discipline. |
Module 5 — Measurement, Budget & ROI ✅ Built
Growth Code stage: all five — the instrument panel.
| # | Lesson | One line |
|---|---|---|
| 5.1 | The Metrics That Matter (by Growth Code Stage) | Leading vs. lagging; the one-page scorecard; vanity-metric detox. |
| 5.2 | Attribution: Useful Lies and Honest Approximations | Why software attribution undercounts Earn-stage work; self-reported attribution; triangulation over false precision. |
| 5.3 | CAC, LTV & Payback: The Deal Math | Unit economics per OpCo; why CPM's LTV changes what CAC we can afford; blended vs. per-motion CAC. |
| 5.4 | Budgeting: Brand vs. Demand, 60/40 in the Real World | Allocating across stages and motions; what to protect in a downturn (hint: not the demand-capture line). |
| 5.5 | Reporting That Drives Decisions | The monthly one-pager per OpCo; narrating cause, not dumping dashboards. |
| 5.6 | Experimentation: Small Bets, Fast Kills | Test design for small teams; minimum detectable signal; the experiment log. |
Module 6 — Brand: The Long Game ✅ Built
Growth Code stages: Differentiate + Attract + Repeat.
| # | Lesson | One line |
|---|---|---|
| 6.1 | What Brand Actually Is | Memory structures and mental availability, not logos; brand as pre-sold trust at scale. |
| 6.2 | Brand vs. Demand: The False War | Why brand is the cheapest demand gen over 3+ years; the evidence (Binet & Field) and the B2B application. |
| 6.3 | The CHARLESGATE Brand Codes & Voice | Our distinctive assets, voice, and editorial standards — how the Brand Code and Growth Code interlock. |
| 6.4 | Category POV: Saying Something That Costs Something | Challenger stances, honest takes, and picking fights worth picking (the Ries "law of sacrifice" applied). |
| 6.5 | Brand in the AI Era: The Creativity Moat | AI pulls everyone to the middle; distinctiveness, taste, and proof are the un-generatable assets. |
Module 7 — The Sales Bridge (Intro Now; Deep in Phase 2) ✅ Built
Growth Code stage: Win.
| # | Lesson | One line |
|---|---|---|
| 7.1 | Marketing–Sales Handoff: MQL, SQL & the SLA | Definitions everyone signs; speed-to-lead; routing and feedback loops. |
| 7.2 | The Enablement Kit | Case studies, one-pagers, competitive responses, proposal templates — built from the Messaging Doc, not improvised per deal. |
| 7.3 | The Sales Narrative (Dunford's Sales Pitch) | Insight → alternatives map → perfect world → us + proof; one story every seller tells the same way. |
| 7.4 | CRM & Lifecycle Basics for Marketers | Stages, hygiene, and what marketing owes the pipeline (and vice versa). |
| — | Phase 2 expansion | Full sales process program: discovery, qualification (SPICED — worksheets already in the library), proposals, negotiation, account management. Scoped in detail at the end of Module 7. |
Module 8 — Ai-Era Marketing: Running the Code with Leverage ✅ Built
Cross-cutting. The moat thesis, operationalized.
| # | Lesson | One line |
|---|---|---|
| 8.1 | The Thesis: AI Pulls Everyone to the Middle | Why average is now free, and the three assets that survive: creativity, proof, proprietary systems. |
| 8.2 | AI Inside the Workflow | Research, drafting, repurposing, personalization at scale — with the Messaging Doc as AI context (Dunford's own 2026 guidance). |
| 8.3 | What Stays Human | POV, taste, relationships, accountability; the synthetic-outreach penalty and the editorial bar. |
| 8.4 | Marketing to Machines | AEO and being citable: structured, sourced, genuinely expert content that AI assistants quote. |
Module 9 — Capstone: The OpCo Growth Plan ✅ Built
All stages. The program's exit exam is a real plan, not a certificate.
| # | Lesson | One line |
|---|---|---|
| 9.1 | Run the Code: Full-Stack Diagnosis | Score your OpCo on all five stages; find the constraint. |
| 9.2 | The One-Page Growth Plan | Positioning → ICP → motion stack → 3 campaigns → scorecard, on one page, defended to Michael + presidents. |
| 9.3 | The 90-Day Execution Sprint | From plan to plays: owners, calendar, kill criteria, first review. |
Field Module F1 — Attribution, the Distribution Engine & AEO ✅ Built
Sits alongside Modules 1–9. Growth Code stages: Measurement + Attract + Earn (armor in Win). Deepens 5.2, 2.6, 2.7, 3.4, 2.5, 8.4 with an outside case (Fibbler/Adam Holmgren) and current 2026 answer-engine research. Adds Templates T26–T28.
| # | Lesson | One line |
|---|---|---|
| F.1 | Attribution Honesty: Stop Attributing the Brand | The attribution-tool founder who ignores his own attribution; set posture by spend type, refuse last-click on brand spend, steer by reach + engagement + self-reported + one honest number (MER). |
| F.2 | The Distribution Engine: Organic Test Market, Paid Amplifier | Batch production, three pillars with known jobs, the promotion gate (organic proves before paid scales), two-layer cold/retargeting amplification; where Fibbler's marketer-audience playbook does NOT transfer to our considered, high-ACV sale. |
| F.3 | SEO + AEO: Being the Cited Answer (2026 field update) | AEO ≠ ranking (88% of AI-cited content isn't top-10); answer blocks, schema, entity + off-site mentions, the Endless Customer bridge, and share-of-model measurement in GA4. |
Suggested Rollout (for Michael to Pressure-Test)
- Weeks 1–4: Module 1, one lesson per week, team discussion + workbook exercise each week (workbook templates are built). Presidents do lessons 1.1–1.3 minimum.
- Quarterly: one module per quarter thereafter (2 → 3 → 4+5 → 6+8), capstone (9) at the one-year mark. Module 7 slots wherever the sales-side counterparts can commit the four co-signed sessions.
- Format decision pending: full IC track (all lessons + exercises) vs. condensed exec track for presidents (framework + lesson summaries + capstone). Recommend both — exec track is cheap to derive once lessons exist.
Next Build Phase
- Phase 2: the Sales program — per the scope at the end of Module 7 (SPICED discovery/qualification, running the narrative live, proposals, negotiation, account management). The only remaining build.
Workbook index (all built): T1–T7 (..._Module_1.md) · T8–T10 (..._Module_2.md) · T11–T13 (..._Module_3.md) · T14–T15 (..._Module_4.md) · T16–T19 (..._Module_5.md) · T20 (..._Module_6.md) · T21–T22 (..._Module_7.md) · T23 (..._Module_8.md) · T24–T25 + T7 v2 (..._Module_9.md) · T26–T28 (CG_Growth_Code_Attribution_and_SEO_AEO_Module.md, appendix)
Resource Library Tie-Ins (Michael's Drive Folder, Already on Hand)
- April Dunford: OA + Sales Pitch workbooks, messaging doc template, worked pitch example → Modules 1, 7
- Maja Voje: GTM Strategist PDF, GTM checklist w/ AI prompts → Modules 3, 8
- HubSpot ABM Blueprint + SPICED worksheets → Modules 3, 7
- People-first GTM Model Workbook → Module 3.6
- Fletch PMM positioning examples (Notion) → Module 1.3 supplementary
- HubSpot budget templates spreadsheet → Module 5.4
- Startup Content Planning Workbook & Templates → Modules 2.4, 4.6
CHARLESGATE Marketing & Sales Glossary
Plain-language marketing and sales vocabulary — every term the modules use.
The Team's Plain-Language Reference · v2.0 (2026-07-07 — Academy Modules 2–9 Terms Merged Into Their Sections; §9 Added)
(This file replaces CG_Marketing_Sales_Glossary.md — the original was file-locked during the update; delete it and rename this one when convenient.)
How to use: These are the working definitions for the Growth Code Academy and for how we talk at CHARLESGATE. Where the industry uses a term sloppily, we've picked one meaning and noted it. When in doubt in a meeting, ask "which definition are we using?" — that question has saved more strategies than any tool.
1. Strategy & Positioning
Strategy — The set of choices about who we serve, why they should pick us, and where we'll focus — plus what we're giving up to make those choices real. A plan is a list of actions; a strategy is the logic that decides which actions matter. No sacrifice, no strategy.
Positioning — The deliberate act of defining the context buyers use to evaluate you: what category you're in, what alternatives you're compared against, and what only you can claim. (Dunford: context-setting. Ries/Trout: owning a slot in the mind.) Not a tagline — the decision behind the tagline.
Differentiation — The provable ways you're different from the alternatives in ways the buyer cares about. Test: can a named competitor truthfully claim the same sentence? Then it's not differentiation, it's decoration.
Distinctiveness vs. differentiation (M6) — Two jobs, often confused: differentiation is why choose us; distinctiveness is knowing it's us at all — the recognizable elements that let memory accrue to our name instead of leaking into the category. You need both; ads that argue brilliantly for the category while the buyer remembers the incumbent have the first without the second.
Competitive alternatives — What the buyer would actually do if you didn't exist — including "do nothing," "do it ourselves," and "hire the cheap one." The status quo is usually your biggest competitor.
Category / market frame — The mental bucket a buyer puts you in, which determines who you're compared to and what "expensive" means. You can often choose your frame; choose the one you win in.
Value proposition — The concise answer to "why should this specific buyer choose you": the value delivered + why it's believable. Built from positioning, not instead of it.
Category POV (point of view) — The editorial stance a company takes about where its market is going and what buyers should demand. A POV that costs nothing ("service matters!") is not a POV. The five tests (M6): costs us something specific · names a real buyer pain · operations can cash it indefinitely · a named competitor couldn't say it · durable for years.
Category wallpaper (M6) — The stance anyone could say at a conference tomorrow ("real estate needs to embrace innovation"). Costs nothing, names no pain, builds nothing.
Stance-beyond-capability (M6) — A public POV your operations can't cash. A scandal on a timer; never take one.
Moat — A structural advantage competitors can't quickly copy: proprietary data, systems, relationships, brand memory, switching costs. Our thesis: in the AI era, creativity + a proprietary growth system are the marketing moat, because average output is now free.
GTM (go-to-market) — The complete approach for taking an offer to a market: ICP + positioning + motions + channels + sales model, working as one system.
GTM motion — A repeatable approach to acquiring customers (e.g., ABM, inbound, outbound, founder-led, partner-led, event-led, community-led, product-led, performance/paid). Companies run a stack of 2–3 well, not 8 badly. (Voje: motion choice is resource allocation, matched to beachhead and buying behavior.)
Motion-market fit (M3) — A motion matched to how the ICP actually buys, the deal's economics, our unfair assets, and a time-to-signal we can afford to wait out. The four tests of Lesson 3.1; a motion must pass all four.
Motion stack (M3) — The chosen architecture per OpCo: one primary motion (majority of resource — matched to how most revenue is actually won), 1–2 secondary (chosen because they feed or convert the primary), max one experimental (small, kill-dated). Stacks, not silver bullets.
Interlock (M3) — The property of a healthy stack: each motion lowers another's cost (founder content warms ABM; events feed the ledger and the list; partner referrals arrive pre-trusted). An unstated feed is an unmanaged one.
Time-to-signal (M3) — How long a motion takes to prove or disprove itself (outbound: weeks; inbound/ABM: 2–4 quarters; founder-led: quarters). Mismatch between the motion's clock and leadership's patience is the #1 cause of motion-hopping.
Peanut-buttering (M3) — Spreading resource evenly across motions (or channels, or campaigns) because choosing is uncomfortable. The primary gets the majority; that's what primary means.
Beachhead — The first, narrow segment you commit to winning before expanding. Small enough to dominate, connected enough to lead somewhere.
TAM / SAM / SOM — Total Addressable Market (everyone who could conceivably buy) / Serviceable Addressable Market (the portion you could realistically serve) / Serviceable Obtainable Market (what you can actually win near-term). Useful for honesty, dangerous for theater.
2. Audience: ICP, Segments, Personas
Segmentation — Dividing a market into groups that buy differently (needs, process, economics) — not just look different demographically.
ICP (Ideal Customer Profile) — The account-level profile of your best-fit customer: where you win most, deliver most, earn best economics, and generate the best repeat/referral/proof assets. In our world, often a building/asset profile plus its ownership.
Anti-ICP — Who you deliberately decline. As strategically important as the ICP; bad-fit revenue degrades the whole system (service strain → bad reviews → repelled good-fit buyers).
Persona — A named role in the buying process (champion, economic buyer, skeptic, blocker) described by what they want, fear, and need as evidence — not demographic trivia.
Buying committee — The group that actually makes a B2B decision (typically ~5–7 people; a condo board is a buying committee with feelings). You market to a committee even when you're talking to one member.
Champion — The person inside the account who sells you internally when you're not in the room. Your real job in B2B: arm the champion.
Economic buyer — The person/group with budget authority to say the final yes.
Trigger event — The occurrence that moves a buyer in-market (manager stops responding, financing closes, inspection fails, board turns over). Most B2B buying is trigger-driven, not persuasion-driven.
Category entry point (CEP) (M6) — The situation or thought through which a buyer enters the category ("our manager stopped responding," "financing closed — now what"). Brands are retrieved through entry points; the strategic act is choosing 3–5 to own per OpCo and attaching our name to them relentlessly. The Template 2 trigger inventory is secretly a brand document.
Tiering (Tier 1/2/3) — Ranking ICP accounts by fit + value to allocate effort: named-account pursuit (T1), systematic coverage (T2), inbound-only (T3).
1:1 / 1:few / 1:many (M3) — ABM program tiers: a handful of must-win accounts with bespoke plans / clusters of 5–15 sharing a situation, running a shared play / the wider named list on scaled programs with account-level tracking.
95:5 rule — At any moment, roughly 95% of your category's buyers are not in-market; only ~5% are. (Ehrenberg-Bass / LinkedIn B2B Institute.) Implication: most marketing should build memory with future buyers, not just harvest current ones.
3. Funnel, Journey & Demand
Funnel — The classic stage model of a buyer's path: awareness → consideration → decision (with post-sale stages often bolted on). Useful for measurement; misleading as a model of behavior — real buyers loop, stall, and skip.
Flywheel — A loop model where post-sale outcomes (retention, referrals, proof) feed pre-sale stages, compounding over time. The Growth Code is a flywheel: Repeat feeds Differentiate and Attract.
Buyer journey — The real path a buyer takes: trigger → research (mostly invisible to you) → shortlist → committee → decision → renewal. Most of it happens before they ever talk to sales.
Dark funnel — The parts of the journey your software can't see: word of mouth, peer Slack groups, podcasts, AI-assistant answers, forwarded PDFs. Large and growing; the reason self-reported attribution matters.
TOFU / MOFU / BOFU — Top/Middle/Bottom of funnel: content and plays for early awareness, active evaluation, and final decision respectively.
Demand generation (demand gen) — Creating want for a solution among people not yet looking — teaching the market to care. Long horizon, compounding payoff.
Demand capture — Harvesting existing demand from people already looking (search, review sites, referrals-in-motion). Short horizon, capped by market size.
Honest capture ceiling (M2) — The computed maximum worth spending on capture: query/trigger volume × achievable share. Spend past it and you're bidding against yourself in the auction. Surplus goes to creation, not to more capture.
Lead generation (lead gen) — Converting interest into identifiable contacts (form-fills, event sign-ups). Not the same as demand gen — lead gen without demand gen means paying more each year for colder names.
Lead — A person who has identified themselves with some signal of interest. Signal quality varies wildly; hence qualification.
MQL (Marketing Qualified Lead) / hand-raiser — Same thing, one definition: a contact who fits the ICP and took a written hand-raise action (scorecard or Presence Score completion, review or audit request, webinar attendee, worked guest list). Crossing it is the Attract → Earn gate. Each OpCo writes its own action list and fit test, and sales and marketing sign the same definition (Template 21). An action without ICP fit is a list member, not an MQL.
SQL (Sales Qualified Lead) — A lead sales has accepted as a genuine opportunity after conversation/qualification.
Pipeline — The set of active opportunities, by stage, with values. "Pipeline coverage" = pipeline value ÷ target (rule-of-thumb: 3–4×).
Conversion rate — % of people moving from one step to the next. The compounding levers of the whole system live here.
Conversion path (M4) — The last meter of the journey: from attention earned (the click) to conversation started (the assessment booked). The narrowest point in the system — fixing a leak here beats adding volume anywhere else.
Message-offer match (M3/M4) — The page must be the promise of the click, kept. The visitor from the cost article lands on a page about cost and the assessment — not the homepage. Mismatch is the #1 silent leak.
One page, one job (M4) — Every conversion page has exactly one CTA — the next rung of the offer ladder. A page asking for three things converts to none of them.
Lead magnet — Something genuinely valuable exchanged for contact/permission (market report, benchmark, toolkit). Hormozi's bar: the free thing should be better than competitors' paid thing.
Nurture — Systematic, useful follow-up that builds trust with not-yet-ready buyers. Done right it's the Earn stage in email form; done wrong it's spam with a workflow.
Gating — Requiring contact info to access content. Trade-off: gates create leads but strangle reach and trust. Our default: un-gate the answers (TAYA), gate the tools.
4. Messaging, Content & Brand
Messaging — The approved language that carries your positioning: one-liner, boilerplates, value themes with proof, competitive responses. Lives in the Messaging Document (single source of truth; also your AI context file).
Messaging hierarchy — The layered structure from position → one-liner → elevator → boilerplates → value themes. Each layer derives from the one above.
One-liner — The sentence anyone in the company can say verbatim: what we are + biggest benefit + who it's for.
Value theme — A load-bearing claim: the value + the capabilities enabling it + the proof. A value theme without proof is an adjective.
StoryBrand / SB7 — Donald Miller's message structure: the customer is the hero; you're the guide with empathy + authority, offering a plan, a call to action, and stakes. Governs how we tell it; positioning governs what we claim.
Proof — Evidence a claim is true: named results, statistics, case studies, reviews, references, awards ("brag points"). The currency of the Earn stage.
Proof engine (M6) — The Repeat-stage machinery run as a system: case studies quarterly, reviews as a managed play, published numbers, the annual data report. In the AI era this graduates from hygiene to the content strategy — un-fakeable artifacts force competitors onto ground AI can't level for them.
Case study — A documented client story: situation → what we did → measurable result. The single most reusable B2B asset.
Social proof — Trust borrowed from other buyers: reviews, testimonials, logos, counts. In B2B, named + specific beats voluminous + vague.
Content marketing — Earning attention and trust by publishing genuinely useful material instead of renting interruptions.
They Ask, You Answer (TAYA) — Marcus Sheridan's content philosophy: answer buyers' real questions — especially the uncomfortable ones — more honestly than anyone. The Big 5: cost/price, problems, comparisons ("vs."), reviews, best-of. CHARLESGATE already practices TAYA; the Growth Code makes it the Earn stage's spine.
Trust arbitrage (M2) — The open lane TAYA exploits: every competitor's silence on price and problems is an opportunity — honesty in that lane converts, because the buyer's real fear is "who will be straight with me when something goes wrong?"
Assignment selling — Sheridan's practice of assigning content before sales conversations ("read this pricing article before our call") so meetings start educated.
Thought leadership — Content that takes a defensible, useful position on where the market is going. Earns trust only when it costs something to say.
Editorial calendar — The planned schedule of content by ICP, stage, and channel. Discipline beats inspiration.
Angle (M4) — The strategic way into a message: which value theme, aimed at which persona's fear or ambition, through which frame. One message supports many angles (the treasurer's angle is not the president's). Kept in the angle inventory, appended to the Messaging Doc.
Hook (M4) — The first three seconds: the line, image, or claim that earns the next ten. Hooks are promises; the body must cash them — a hook the body doesn't cash is clickbait, and our ICPs remember clickbait in the worst way.
Earned specificity (M4) — The detail only our operations could produce: the real number, the named lesson, the honest problem. Earned, not borrowed applied to creative — borrowed creative quotes the industry; earned creative quotes our buildings.
The creative bar (M2/M4) — House standard for everything shipped: a specific, a number, or an opinion that costs something. AI-era ratchet: "would a competitor's AI publish this?" If yes, it's below the flood line.
Document, don't create (M2) — Gary Vee's rule, house-adopted: the raw material is the work we already do. Publishing what's true beats manufacturing what's clever, and the supply is infinite.
Brand — The sum of memory structures and associations a market holds about you — what they think of you when you're not in the room, and whether they think of you at all. Built by consistency + distinctiveness + experience over time.
Brand codes / distinctive assets — The repeatable identifiers (visual, verbal, tonal, formats, named frameworks and offers) that make work recognizably yours before the logo appears. At CHARLESGATE these live in the Brand Code and the T20 commit list. Test: do buyers attribute it to us without the logo?
Mental availability — How easily a brand comes to mind in buying situations (Ehrenberg-Bass). The Attract stage's real objective — being remembered into shortlists.
Retrieval test (M6) — The brand audit in one question: when the ICP thinks [entry point], what surfaces? Run it with attribution verbatims, win/loss language, and referrer sentences ("what do you say when you recommend us?").
Dual-clock work (M6) — Assets that convert now and deposit memory (the market letter, the annual data report). The best answer to the brand-vs-demand budget war: build more things that are unkillable from either side.
Brand vs. performance (brand vs. demand) — Long-horizon memory-building vs. short-horizon activation. Not a war; a portfolio. Evidence (Binet & Field) suggests roughly 60/40 brand-to-activation over multi-year horizons; the mix flexes by category and lifecycle. Cutting brand to fund capture is borrowing from next year at loan-shark rates.
Share of voice (SOV) — Your share of the category's marketing presence. Long-run rule of thumb: SOV above your market share predicts growth.
Tone of voice — The recognizable way you sound. Ours: direct, editorial, evidence-led, plain words. Per-OpCo registers (M6): same character, different altitude (CPM speaks to volunteers with day jobs; CG Capital speaks under compliance).
Drift audit (M6) — The quarterly check that distinctive assets and voice are being used consistently — and that any movement of standards was chosen, not drifted into.
5. Channels, Campaigns & Execution
Channel — Where a message travels to an audience (email, LinkedIn, search, events, referral network, direct mail, PR).
Medium / format — The form the message takes (video, article, report, dinner, webinar). Channels carry mediums.
Owned / earned / paid / rented — Channel ownership classes: owned (your list, site), earned (press, reviews, referrals, AI citations), paid (ads, sponsorships), rented (social platforms — reach exists at an algorithm's pleasure). Strategy: convert rented/paid attention into owned audience.
Trust channel vs. attention channel (M2) — Some channels create awareness (social, PR, paid); some create trust (referrers, events, email, long-form answers). Map to stage: attention serves Attract, trust serves Earn. A map that's all attention channels fills the top of a bucket with a hole in it.
Minimum effective dose (M2/M3) — The cadence below which a channel or motion produces nothing but the feeling of activity. Sub-threshold presence in six channels equals effective presence in zero.
Underpriced attention (M2) — Gary Vee's arbitrage: attention available at a fraction of its worth, paid in effort and craft. Our market's version: commercial real estate B2B social is a desert of genericness — the bar for distinctive is on the floor.
ICP follower density (M2) — The metric behind B2B social: who follows, not how many. Fifty board presidents outvalue fifty thousand strangers. Impressions are weather.
Campaign — A time-boxed, coordinated push with one objective, one ICP, one core message, defined channels, budget, and a success metric. If it can't fill the one-page brief, it's not a campaign yet.
Play — A documented, repeatable sequence with an owner and trigger ("new sell-out closing → case-study production play"). Plays are how a small team scales judgment. Promotion bar (M4): it worked twice and we can say why.
Play card (M4) — The one-page standing format (Template 14): name, trigger, time-stamped steps, owner + SLA, linked assets, AI column, metric + run log. A play without an owner is a suggestion.
Run log (M4) — The per-play record of every run and its result. Two years of run logs is institutional memory competitors can't buy.
Tactic — A single action (an email, an ad, an event booth). Tactics without a campaign and strategy above them are noise with a budget.
Orphan tactic (M4) — Work that can't name its parent campaign, play, or motion. Individually defensible, collectively incoherent — how marketing budgets die. Adopt it into a parent or kill it.
Tracing test (M4) — Five questions up the hierarchy for any proposed or in-flight work: what tactic → what play/campaign → what motion (is it in the stack?) → which stage and ICP → what metric by when. Run at proposal (cheap) and at quarterly review (honest).
Red-team review (M4) — A colleague's explicit job: attack the campaign brief before launch. Standard attacks: vanity metric? swap-test failure? dishonest reach math? timeline vs. time-to-signal mismatch?
Kill criteria / kill-or-scale (M4) — The pre-written evidence threshold that stops a campaign or promotes it, decided at the review date per the criteria, not per mood. Both outcomes are wins; the only losing outcome is the zombie.
Zombie campaign (M4) — Running because nobody decided. See also zombie certificate (§6).
Kill order (M4) — The pre-written mid-quarter sacrifice sequence: experiments die first, then campaign scope, never the standing cadences. Written at planning time, when you're wise.
Capacity honesty (M4) — Hours available vs. hours planned, shown, at or under 100%, with the cut list attached and visible. A calendar at 140% produces 60% plus burnout.
Market-moments calendar (M4) — The calendar's first draft, written by the market's clock: budget season, annual meetings, leasing season, development cycles. Ignoring the market's rhythm is malpractice; real estate hands it to us free.
ABM (Account-Based Marketing) — Treating named target accounts as markets-of-one: tiered lists, personalized programs, marketing + sales working the same accounts together across the full journey (Zinkevich/Full-Funnel model — not just ad targeting by company name).
Engaged account (M3) — ABM's unit of measurement, per written definition (e.g., ≥2 committee members with meaningful activity in 60 days). Not leads: three committee members from a Tier-1 account consuming the case study is pipeline forming.
Account intelligence (M3) — Per-account homework: the committee (names, roles, fears), current situation, alternatives, trigger horizon, warm paths in.
Warm path (M3) — The relationship route into an account: mutual contact, shared room, partner intro. Checked before anything cold is sent; a warm path beats a cold sequence every time.
Air cover (M2) — Named-account paid/organic presence supporting ABM and outbound: being visibly familiar to the 50 accounts before the 1:1 note lands.
Inbound — Being found by in-market buyers through content, search, and reputation. Complement of outbound — proactively reaching chosen accounts (calls, email, DMs, mail). Modern rule: outbound must be researched, relevant, and human — buyers penalize synthetic.
Synthetic swap test (M3) — If the outreach message reads identically when addressed to the next account on the list, it fails — rewrite or don't send. Applies to AI-personalization doubly.
Trigger play (M3) — A public signal (permit filed, inspection failed, portfolio traded) → a useful, human response within an SLA. In real estate the intent data is public record, and it's free.
Founder-led / personality-led marketing — Building audience and trust through visible, opinionated people rather than logos (Gerhardt: people follow people). High-leverage in B2B; requires actual opinions.
Community-led / relationship-led — Growth through rooms, networks, and long-cultivated relationships. Where B2B real estate is actually won; slow to build, brutal to copy.
Relationship ledger (M3) — The Tier-1/referrer relationship book, run like pipeline: owner, last meaningful touch, last give, next give, cadence. Reviewed monthly — because it is pipeline, earlier. Untracked generosity is unmanaged strategy.
Give-first cadence (M3) — The systematized generosity that powers relationship and partner motions: introductions made, intel shared, wins amplified — tracked, not invoiced.
Hosted room (M3) — The event-led power move: convene, don't attend; teach, don't table. The roundtable dinner, the board-education night. The convener position can't be bought.
Event-led — Using gatherings (yours or others') as the primary motion — roundtables, dinners, workshops. Teach, don't table.
Channel/partner-led — Growth through referrers and complementary firms (attorneys, lenders, reserve-study firms, architects). Formalize the loop: give first, track it, thank loudly.
Partner activation (M3) — % of mapped partners who sent ≥1 referral this half. The partner motion's health gauge; an unfed loop dies in two quarters.
Product-led (PLG) — The product itself acquires/converts users (free tiers, self-serve). Services translation: productized entry offers and self-serve tools (calculators, assessments) that deliver value before a conversation.
Productized entry point (M3) — Services PLG: the named, scoped, repeatable tool or assessment that delivers real standalone value and wires to the offer ladder's next rung. Gate the tool, not the answers.
Performance marketing — Paid media optimized to measurable response. Amplifier of proven messages, not a rescue for weak positioning. Organic proves, paid scales (M2): nothing gets paid promotion until it earned organic signal.
Cost-per-thousand (M2) — House style for media "CPM," to avoid collision with the OpCo. Yes, everyone makes the joke once. Once.
SEO / AEO — Search Engine Optimization: being found in search. Answer Engine Optimization: being cited by AI assistants answering buyer questions. AEO rewards the same thing TAYA does: genuinely expert, structured, sourced answers.
Zero-click journey (M2) — Buyer research that ends at the AI-composed answer, without a site visit. Absence from the answer is invisibility at the moment of maximum intent.
Citability audit (M2/M8) — The quarterly instrument: buyer questions × AI assistants, logged — who's cited, who's named, are we present, is it accurate. Plus the Win-stage query class (M8): "is [CHARLESGATE] a good choice for X? what are the risks?"
Citation magnet (M2/M8) — The original-data asset machines prefer to cite: the rental market report, absorption benchmarks — specifics nobody else has, methodology stated, named experts attached.
Answer-first structure (M2) — The question as a heading, a direct 2–3 sentence answer immediately below, then the depth. Machines extract; make extraction easy.
Extractable summary (M8) — The two-sentence answer a machine can quote whole and accurately. If the machine must paraphrase, it may paraphrase wrong; give it the sentence we want repeated.
Entity hygiene (M8) — Consistent name, services, locations, authorship, and directory presence across the open web, so machines can triangulate who we are. Boring, compounding, delegable.
Retargeting — Ads shown to people who already engaged. Cheap frequency; creepy when overdone.
CTA (call to action) — The specific next step you ask for. One per asset.
Landing page — A page with one job: convert a specific audience on a specific offer. Message-offer match is 80% of the result.
A/B test — Comparing two versions to see which performs better. Needs enough volume for signal; small teams should test big swings, not button colors.
6. Metrics, Measurement & Economics
KPI — Key Performance Indicator: a metric someone owns and acts on. If nobody changes behavior when it moves, it's decoration.
Leading vs. lagging indicators — Predictive activity/quality measures (engaged Tier-1 accounts, list growth) vs. result measures (revenue, retention). Manage with leading; judge with lagging. Every scorecard stage-row needs at least one of each.
Vanity metric — Numbers that flatter but don't decide anything (raw impressions, follower counts without ICP density). The vanity test (M5): what decision would change if this number doubled? None → off the panel.
Decision note (M5) — The margin note every scorecard metric carries: "if X for two months → Y." A metric with no decision attached goes back in the drawer.
CAC (Customer Acquisition Cost) — Total sales + marketing cost to win a customer — including people-hours at loaded rates. Compute blended and per-motion; per-motion is where decisions live.
Allowable CAC (M5) — The ceiling per motion: LTV ÷ 3 by default, adjusted for payback tolerance. Motions exceeding it are killed or must claim the relationship-LTV exception with the math shown.
LTV (Lifetime Value; also CLV) — Total profit a customer relationship generates over its life. In management contracts and repeat developer relationships, LTV is what justifies serious CAC. LTV:CAC rule-of-thumb: 3:1+ healthy; interpret with payback.
Relationship LTV (M5) — The HoldCo's number: one relationship across OpCos (sell-out + management + AFF + capital). It's why we can rationally outspend any single-line competitor for the same relationship — the flywheel as a pricing advantage in acquisition.
CAC payback — Months to recover CAC from a customer's margin. The cash-flow reality check on growth spend; in an FCF-first year, the first metric, not the third.
Attribution — Assigning credit for a conversion across touches (first-touch, last-touch, multi-touch models). All models are estimates; software systematically undercounts dark-funnel and Earn-stage work (last-touch bias, trackability bias — M5). Antidote: triangulate software + self-reported attribution ("how did you hear about us?" — open text, asked on every form and call, logged verbatim).
Triangulation stack (M5) — Four witnesses read together: self-reported attribution · software attribution (demoted to capture-efficiency duty) · aggregate correlation (branded search, "already knew you" rate) · MER. House stance: attribution software is a witness, never the judge. When witnesses disagree, the disagreement is the finding.
MER / marketing efficiency ratio — Total revenue ÷ total marketing spend. Blunt but honest; the hardest instrument to fool — if channel numbers look great and MER is flat, something's lying.
ROI / ROAS — Return on investment (profit-based, all-in) / Return on ad spend (revenue ÷ ad cost, narrow). Don't let a good ROAS on capture spend masquerade as marketing ROI. Platforms grade their own homework.
Pipeline velocity — How fast pipeline converts to revenue: (# opps × win rate × avg deal) ÷ cycle length. The four levers of the Win stage in one formula.
Win rate — % of qualified opportunities that close. Track vs. named alternatives — it's a positioning metric wearing a sales badge.
Churn / retention / NRR — Churn: % of customers/revenue lost per period. Retention: the inverse. NRR (Net Revenue Retention): revenue from existing customers this year ÷ last year, including expansion — >100% means the base grows itself. The Repeat stage's headline numbers.
Cross-OpCo attach rate — CHARLESGATE-specific: % of clients using 2+ OpCos. The flywheel's truth metric.
Share of shortlist — % of ICP deals where you're invited to compete. The Attract/Earn stages' downstream truth metric.
Cohort analysis — Comparing groups by start period to see if economics are improving (e.g., do this year's new associations retain better than last year's?).
Marketing scorecard — The one-page, stage-organized monthly view (per OpCo) of the handful of metrics that matter (Template 16). If it doesn't fit on a page, it's a dashboard, not a scorecard.
Dashboard dump (M5) — Forty charts, no narrative, no ask. The reporting failure the monthly one-pager exists to replace: narrate cause, then request decisions.
Decision grammar (M5) — Asks phrased so they're approvable or rejectable in one sentence ("requesting $X move from search to the letter, per the capture-ceiling math"). Asks that can't be phrased as decisions are mood.
Know / believe / guessing (M5) — House confidence labels for reported narrative: "we know speed-to-lead improved; we believe it's driving the proposal lift; we're guessing on the review effect." Precision about uncertainty is what makes narrative trustworthy.
Shared engines (M5) — HoldCo-level assets no single OpCo owns: Michael's voice, the cross-OpCo flywheel plays, house data assets, the play library and AI infrastructure. Funded as a HoldCo line with named governance, or quadruple-taxed and quietly starved.
Downturn paragraph (M5) — The pre-written, pre-signed cut sequence in every budget: capture flexes to the honest ceiling first, campaigns shrink second, the compounding cadences never. Signed in daylight, before the pressure arrives.
Experiment (M5) — A bet with a hypothesis, budget, clock, and pre-committed verdict rule. Campaigns exploit what we believe; experiments buy information about what we don't. One slot per OpCo at a time.
Minimum detectable signal (M5) — The small-team substitute for statistical significance: the movement, defined in advance, big enough to notice above noise and worth acting on. No pre-committed signal by the kill date = verdict is no, regardless of how the room feels.
Smallest honest version (M5) — The cheapest build that gives the mechanism a real chance: the fake-door test (a page and ten outreaches before the tool is built), three hand-run events before a series. Information first, infrastructure after.
Zombie certificate (M5) — The second extension of an experiment. There is no third.
7. Sales (Working Set — Phase 2 Goes Deep)
Sales enablement — Everything marketing builds so sellers sell better: case studies, one-pagers, competitive responses, pitch narratives, proposal templates. Built from the Messaging Doc, not improvised per deal — every improvised deck is a small act of message erosion.
Champion test (M7) — The enablement kit's design gate: could the champion forward this artifact to the skeptic with no cover note and have it land? Self-contained, plain-worded, proof-forward. Materials that only work with us presenting them don't work.
Objection library (M7) — The recurring dozen objections with the honest answer, the proof asset, and the reframe — written calm, in daylight. Half of it already exists as TAYA content; the two share one honesty standard.
Stall-point walk (M7) — The kit-building method: walk the last five won/lost deals with sales — what artifact was needed at each stall, what got improvised, what the champion asked for that didn't exist. That list, not a brainstorm, is the build order.
Sales narrative / pitch — The one story every seller tells the same way. Dunford's Sales Pitch structure: market insight → honest map of the alternatives → what "perfect" would look like → us + proof. Teaches the buyer how to choose, not just what we do — a decision-teaching pitch (M7), not a features pitch.
Alternatives map / strong-case-first (M7) — The narrative's second movement: the buyer's real options, each with its honest strong case written first. If we can't state why someone reasonably chooses the national or stays self-managed, we don't understand the market we're pitching into. One strawman and the pitch dies.
Derived criteria (M7) — The "perfect world" decision criteria, derived in front of the buyer from the alternatives map's tradeoffs — never reverse-engineered from our feature list. Buyers smell reverse-engineered criteria.
Owned gap (M7) — The weakness stated before the buyer finds it ("on pure price, the discount local wins — here's what the gap buys"). Owned gaps build the pitch; hidden ones end it.
Discovery — The structured first conversation(s): their situation, pain, impact, decision process — before prescribing anything.
Qualification — Deciding whether a deal deserves pursuit. Frameworks: BANT (Budget, Authority, Need, Timeline — blunt, dated) and SPICED (Situation, Pain, Impact, Critical event, Decision — journey-oriented; worksheets already in Michael's resource library; our Phase 2 default).
Objection — A stated barrier. Usually one of: no priority, no trust, no budget, wrong fit, wrong timing. Best handled before it's raised — in content (TAYA), proof, and offer design.
Risk reversal — Shifting decision risk from buyer to seller: guarantees, easy-outs, pilots, performance triggers. Champion armor for committee decisions. Guarantee what your operations control; never the market.
Proposal — A decision document for the whole committee, not a quote. Should restate the problem, the plan, the proof, and the offer — in Messaging-Doc language.
Speed-to-lead — Time from inquiry to first meaningful response. Conversion decays by the hour; this is the cheapest Win-stage fix that exists. Now a signed standard with a clock per lead type (Template 21) — the response clock is part of the offer.
SLA (marketing↔sales) — The signed internal agreement: definitions (MQL/SQL), response times, feedback loops, and who does what by when. Both directions: marketing owes quality + context; sales owes speed + disposition with coded return reasons (M7 — no silent graveyard; the return codes are marketing's free QA data).
Classification test (M7) — Before co-signing definitions: both sides independently classify the last 20 inbound contacts. Every disagreement is a definition bug; fix the wording until classification is identical.
Handoff — The moment a lead moves marketing→sales (or sales→operations). Where trust earned is most easily dropped; script it (routing play card, context attached).
Lifecycle stages / advocate stage (M7) — The CRM stages mirroring the signed definitions: lead → MQL → SQL → opportunity → client → advocate (referrers, reviewers, case-study participants — Repeat-stage pipeline events most CRMs never configure and ours must).
Trigger task (M7) — The cross-OpCo flywheel as software + SLA: closed-won fires a task with an owner and a clock in the receiving OpCo ("sell-out closed → CPM proposal within 30 days"). Culture plus hope, replaced by rails.
Data-trust number (M7) — The CRM truth audit's score: 20 recent records graded 0–3 on source, verbatim, tier, and stage freshness, averaged. It should embarrass everyone exactly once.
Bad-fit funeral (M7) — Killing mis-fit pipeline in daylight at the quarterly ICP-fit audit. Killing bad-fit deals early is positioning discipline, not lost revenue.
Upsell / cross-sell / expansion — Selling more of the same / adjacent services / growing the account overall. At CHARLESGATE, cross-sell = the cross-OpCo flywheel with named triggers and owners.
Referral — New business sourced by an existing relationship. A play with a trigger (peak-satisfaction moments), an ask, and a thank-you — not a hope.
QBR / annual review — Structured periodic client review. Repeat-stage machinery: surfaces expansion, referral moments, proof, and voice-of-client intel.
Voice of client (VoC) — Structured capture of what clients say (reviews, interviews, complaints) fed back into positioning, offers, and ICP quarterly. Closes the flywheel loop.
8. Ai-Era Terms (2026 Working Set)
"AI pulls everyone to the middle" — Our house thesis: generative AI makes competent-average marketing free, so average is now invisible. The differential value moves to what can't be generated: real positioning choices, earned proof, creative distinctiveness, relationships, and proprietary systems (the Code).
Leverage inside standards (M8) — The house AI posture, refusing both failure modes: not abstinence (out-produced 10:1), not surrender (synthetic flood). AI amplifies production; the codes, the bar, and the proof requirements govern what ships. AI touches everything; AI ships nothing.
Synthetic outreach penalty — Documented 2026 buyer behavior: a large share of B2B buyers (≈45% in current research) are less likely to consider vendors whose outreach feels AI-generated. Specificity and proof read human; adjectives read generated.
AI context file / context library (M8) — The artifact set fed to AI tools so output stays on-position: Messaging Doc, ICP grids, voice standards, play cards, proof inventory, POV pages. Versioned, dated, owned by the editorial owner. No context = every AI draft erodes the position slightly. (Dunford's own 2026 guidance: the messaging doc is now the machine's briefing.)
Bare prompt (M8) — Generation without the context library. Banned for external-facing work.
The fabrication rule (M8) — No unverified generated facts, ever. Every number and claim traced to the proof inventory or cut. Unverified generated specifics are radioactive — AI's confident inventions are the fastest route to a trust incident.
The human line (M8) — The four never-delegated categories, written per OpCo: POV & stance (machines can argue any side, which is why they can't hold one) · taste — the final call · relationships & presence (DMs, rooms, replies from the named person) · accountability (a named human stands behind every external artifact). An unwritten line migrates one convenient exception at a time.
Review tiers (M8) — Tier 1: external high-stakes — named-owner review, claim-by-claim. Tier 2: external routine — bar check + spot verification. Tier 3: internal — light touch. Tiers keep the line affordable; a line too expensive to hold becomes theater.
Dinner-defense test (M8) — For founder voices: could the named person defend every sentence as theirs, extemporaneously, at a dinner? If not, it doesn't post under their name.
First reader (M8) — The machine that reads us before the buyer does: the assistant answering their question, the chatbot summarizing our proposal. Not the audience — the summarizer, citation chooser, and shortlist suggester.
Committee's chatbot (M8) — The Win-stage machine moment: a committee member pastes our proposal into a chatbot and asks "is this credible? what should we push back on?" Run the query on ourselves first; entity hygiene and claim consistency are Win-stage armor.
Creative as targeting — 2026 finding: distinctive creative now does much of the audience-selection work algorithms used to do — the right people stop for the right idea. Creative is a strategy line, not a decoration line.
AEO / being citable — See §5. The new SEO question: when an AI assistant answers your buyer's question, are you the cited source?
Flood line (M6/M8) — The rising quality bar set by generated content. Everything shipped must clear what the flood can now produce: "would a competitor's AI publish this?"
Human-in-the-loop — AI drafts, humans decide: judgment, taste, claims, and relationships stay human; production leverage goes to the machine.
Differentiating-hours proportion (M8) — The truest AI-adoption metric: the share of human hours spent on un-generatable work (taste, stance, relationships, proof-gathering). Done right, it rises every quarter.
9. Planning, Diagnosis & Operating Cadence (Modules 4, 5, 9)
Operating cadence — The rhythm that keeps the system honest: annual (positioning + ICP review, budget frame) → quarterly (Growth Code review: constraint diagnosis + campaign slate + motion check) → monthly (scorecard one-pager, kill/scale calls) → weekly (execution standup: shipped/blocked/next, 30 minutes). Out of cadence is out of existence.
Binding constraint / flow test (M9) — Growth systems are serial, so output is governed by the weakest stage, not the average. The flow test interrogates the candidate: if this stage improved one point, would output rise — or does the bottleneck just move? Where two stages are jointly binding, the upstream one is primary (position before promotion, always).
Counter-diagnosis (M9) — The strongest rival constraint verdict, written down with the evidence that would decide between them. The "strong convictions, loosely held" ritual; it frequently changes the verdict.
Evidence edition (M9) — The program-wide scoring rule: no evidence, no score. Where evidence is missing, score conservatively and log the instrumentation gap — the gap is itself a finding about how we've been steering.
One-page plan (M9) — Template 24: position → ICP → constraint → motion stack → ≤3 campaigns → scorecard commitment, on one page, in that order. One page is not a summary of the plan; one page is the plan. A plan that needs ten pages hasn't decided yet.
Derivation check (M9) — Every line on the plan traces to an artifact (T1, T2, T7v2, T13, T5s, T16) or gets named out loud as homework or fiction.
Not-doing list (M9) — The plan's shadow: motions not fed, campaigns declined, channels exited, one reason each. Sacrifice made visible is what makes the page credible.
Defense session (M9) — The plan presented to the president + Michael as a diagnosis seeking holes, not a pitch seeking approval. The presenter's win condition is a better plan. A defense where nothing changed was a ceremony.
Sprint goal (M9) — The ONE leading indicator a 90-day sprint exists to move, derived from the constraint. The single goal makes mid-sprint tradeoffs self-answering.
Definition of done (M9) — Written before work starts. "Launched" is not done; "launched, instrumented, and first-cycle-reviewed" is done.
Capacity ledger (M9) — Hours per owner per week, honest, summing under reality. Also where "who actually does marketing work here" stops being ambiguous.
Decision checkpoint (M9) — Day 30/60 held as kill-criteria moments, not status theater. Sprints fail politely by default; the criteria make failure loud, early, and cheap.
Kill discipline (M9) — The organization keeping its word to itself: when the workstream everyone likes is under threshold at day 30, the criteria win over the sunk cost. Every time they do, the organization's word gets stronger. There is no neutral outcome at day 30.
Maintained by: [owner TBD]. Terms marked (M2)–(M9) entered with that Academy module. Missing a term the team keeps tripping on? Add it — this document is meant to be argued with.
The Growth Code — Executive Track
The Code in five minutes, all nine modules at exec altitude, and the president's operating role.
The Presidents' Version: What the System is, What Your Team Owes You, and What to Ask
CHARLESGATE Growth Code Academy · Exec Track v1.1 (Aug 2026) · Reading time: ~90 minutes total, consumable in module-sized pieces
v1.1 definitions update: the stages now carry the field definitions proven at CPM — Attract = attract attention (marketing awareness + lead gen), Earn = earn pipeline (outbound, ABM, nurture), Win = the sales process from qualified opportunity to signed and onboarded. Each boundary is a HubSpot state change, not an activity type. The one-page ruling: CG_Growth_Code_v1.1_Canon.md.
Who this is for: OpCo presidents and growth leads who govern marketing without running it day-to-day. The full Academy (9 modules, ~40 lessons) is the IC track; this is the altitude you operate at: the system's logic, the artifacts your team owes you, the questions that expose weak thinking, and the four moments a year where your signature is the system working.
How to use it: Read Part 1 (the Code) and Part 3 (your operating role) now — 30 minutes. Read each module summary in Part 2 the quarter your team takes that module. Presidents also do three full lessons from the IC track: 1.2 (the Code), 1.3 (positioning), and 9.2 (the plan you'll be defending against). Everything else here is sufficient.
Part 1 — The Code in Five Minutes
The system: Differentiate → Attract → Earn → Win → Repeat. Different attracts. Earned wins. Repeat.
- DIFFERENTIATE — choose who we serve and what only we can claim. Positioning, ICP, offer, message. Weak here = expensive everywhere else.
- ATTRACT — attract attention: content, paid, events, owned audience. Get known by right-fit buyers before they're in-market; ~95% of any category isn't buying now, and the shortlist is drawn from memory when the trigger fires. Ends when an audience member becomes a person: a hand-raiser or the first named-account touch.
- EARN — earn pipeline: outbound, ABM, nurture, hand-raiser follow-up. Trust is earned person by person, before the ask — the stage most competitors skip, which is why it's ours. Ends when an opportunity passes the qualification standard and is logged.
- WIN — win the deal: qualified opportunity to signed AND onboarded. Clear offers, one sales narrative, disciplined follow-through.
- REPEAT — compound every relationship: retain, expand, refer, prove — and feed it back into stage 1. The HoldCo's structural advantage lives here: one relationship, four engines.
Why a flywheel, not a funnel: funnels end at the sale; our economics begin there. Each stage lowers the next one's cost — sharp positioning makes attention cheap, attention makes trust fast, trust makes closing easy, easy closes create advocates, advocates make everything cheaper. Run it three years and our CAC falls while competitors' rises.
The diagnosis rule (your most-used tool): growth problems are constraint problems, and the constraint is always at a stage. "We need more leads" is almost never the real problem. Your standing first response to any growth complaint: "Which stage is constrained? Show me the stage metrics."
The AI-era stakes: AI makes competent-average marketing free, so competent-average is now invisible. What survives: real positioning choices, earned proof, creative distinctiveness, relationships, and proprietary systems. The Code is the system half of "creativity + the Code is the moat." Your OpCo's marketing either compounds those un-generatable assets or it's decorating the middle.
Part 2 — The Nine Modules at President Altitude
Module 1 — Foundation: Strategy, Positioning & the Code
The idea: Marketing is creating and keeping customers profitably — four questions in order: who, why us, how, what did it return. Positioning is context-setting (Dunford): buyers evaluate us against alternatives, and if we don't set the frame, the incumbent or the cheapest bidder does. The law most companies can't stomach: no sacrifice, no position — "full-service for anyone in Boston" is an absence of a position.
What your team owes you: the Positioning Canvas (T1) with a one-sentence position that survives the swap test · an ICP one-pager (T2) with ten named Tier-1 accounts, an explicit anti-ICP, and trigger events · a Messaging Doc (T3) with proof behind every claim · one core + one entry offer (T4), ops-signed · a campaign brief standard (T5).
Questions to ask:
- "Put a competitor's name in our one-liner. Does it still read true?" (If yes, we have no position.)
- "Who are we explicitly NOT for — and does sales comp know it?"
- "Which claims in the Messaging Doc have no proof behind them, and who's collecting it?"
- "What does our offer promise that operations hasn't signed off on?"
Module 2 — Demand: How Buyers Buy
The idea: ~95% of buyers aren't in-market; the winners are decided in the invisible part of the journey (peer asks, advisor mentions, AI answers, forwarded PDFs — the dark funnel) before our software sees anything. Three different jobs get blurred into one budget: demand creation (teaching future buyers to care — compounding), demand capture (harvesting the 5% looking now — capped), and lead-gen mechanics. Capture is capped and inflating; creation is what makes capture cheap. House law: un-gate the answers, gate the tools.
What your team owes you: the buyer-journey map (T8) with self-reported attribution live ("how did you hear about us?" logged verbatim, everywhere) · the demand/capture split (T9) — spend and hours classified, with a target ratio (default 60/40) · a channel plan (T6): max 3 committed channels with owners, plus a defensible "not doing" list · the Big-5 honest answers shipping (T10-A) · a quarterly AI-citability audit (T10-B).
Questions to ask:
- "What's our actual creation/capture ratio — dollars and hours? Defend it."
- "When a board member asks ChatGPT our category's biggest question, are we in the answer?"
- "Which uncomfortable question did we answer publicly this quarter?" (If nothing made anyone nervous, it isn't TAYA.)
- Budget-review trap to refuse: judging long-horizon trust work on 30-day conversion windows. That's how the best work gets killed.
Module 3 — GTM Motions: The Playbook Library
The idea: motions (ABM, inbound, founder-led, outbound, relationship/event, partner, product-led) are resource-allocation choices, not preferences. Four tests decide: buying-behavior fit, economics fit, unfair-asset fit, time-to-signal fit. Each OpCo needs its own stack — one primary (majority of resource, matched to how revenue is actually won), 1–2 secondary chosen for interlock, max one experimental with a kill date. The kills are the strategy. Under v1.1, motions map to stages: content-led, founder-led, and events build Attract; ABM, outbound, partner, and relationship motions run Earn.
What your team owes you: the Motion Stack Canvas (T13) with the primary-justification sentence, explicit interlocks, stage coverage, and capacity-honest dosing — plus, if ABM is in the stack, the tiered named list and a staffed weekly account standup (T12).
Questions to ask:
- "Finish this sentence: most of our revenue is actually won by TBD." (The primary motion must match the answer.)
- "Which motions did we kill, and why?" (No kills = no choices.)
- "What's each motion's time-to-signal, and are we committed past it?" (Motion-hopping at month 3 of a 9-month curve is the #1 failure.)
- "Can we staff this stack at effective dose? Show me the hours."
Module 4 — Campaigns, Plays & Execution
The idea: the hierarchy — strategy → motion → campaign → play → tactic — is the delegation architecture. You govern at strategy/motion; your marketing lead owns campaigns; anyone runs a play. Work that can't name its parent is an orphan tactic, and orphan tactics are how budgets die. Campaigns are bets made explicit in one-page briefs; plays are proven bets documented so the company stops re-solving solved problems; the calendar is strategy given time slots, with capacity honesty and a pre-written kill order.
What your team owes you: "no brief, no launch" as standing rule — briefs reviewable by you in five minutes · a growing play library (T14) including the cross-OpCo flywheel play with named owners and SLAs · a quarterly calendar (T15) at ≤100% capacity with the cut list attached.
Questions to ask:
- "What campaign or play does this belong to?" (Ask it about any proposed tactic; the sponsor gala, the webinar, the sponsorship.)
- "What's the kill criterion, and what happened at the last review date?"
- "Show me the cut list." (A calendar without visible cuts is planned at 130% and will deliver 60%.)
- "Which play did we document this quarter that used to live in someone's head?"
Module 5 — Measurement, Budget & ROI
The idea: honest approximations beat precise fictions. Attribution software sees the last click of a journey it watched 10% of — it systematically over-credits capture and starves the Earn-stage work that causes our best clients. Antidote: triangulate four witnesses (self-reported attribution, software, aggregate trends, MER); software is a witness, never the judge. Deal math (LTV, CAC per motion, payback) decides what acquisition is allowed to cost — and cross-OpCo relationship LTV means we can rationally outspend single-line competitors for the same relationship. Budgets derive from the math; the downturn cut sequence is pre-signed in daylight.
What your team owes you: a one-page scorecard per stage (T16) — leading and lagging kept straight, every metric with an owner and a decision note · unit economics (T17) built with finance · a budget canvas (T18) whose envelope is derived (target wins × allowable CAC), with the downturn paragraph for your signature · the monthly one-pager (5 blocks, ends in decisions requested) · an experiment log with pre-committed signals and kill dates (T19).
Questions to ask:
- "What decision changes if this number doubles?" (The vanity test — ask it of any dashboard.)
- "What does the self-reported log say versus the software — and where do they disagree?" (The disagreement is the finding.)
- "What's our allowable CAC per motion, and is any motion over it?"
- The monthly meeting standard: decisions inside thirty minutes, or the report failed. And the block to check first: "what decisions are you requesting?" If it's empty every month, you're reading a newsletter.
Module 6 — Brand: The Long Game
The idea: brand is memory structures — what buyers retrieve when their trigger fires, before any search begins. Built by consistent, distinctive presence attached to chosen "entry points" (the 3–5 buying situations we want to automatically retrieve our name). Brand vs. demand is a false war: brand is pre-paid Attract and Earn, the cheapest demand gen over 3+ years (Binet & Field), and it matters more in B2B because buying moments are rare and risk is career-attached. A category POV must cost something — the cost is the credibility. And in the AI era, distinctiveness, taste, and proof are the assets that appreciate while competent-average evaporates.
What your team owes you: the memory audit (what buyers actually retrieve vs. what we intend) · the HoldCo Distinctive Asset & Voice Canvas (T20) — 5–7 committed assets used relentlessly, voice standards, and your OpCo's POV one-pager · the two-clock defense of the brand budget, stapled to the downturn paragraph.
Questions to ask:
- "When our #1 ICP hits their trigger, what do they retrieve — and what's our evidence?"
- "What does our POV cost us?" (A stance with no cost is content, not a position.)
- "Is this recognizably us without the logo?"
- The discipline you personally enforce: the compounding lines (letter, content cadence, distinctive formats) are never the downturn cut. That trade always looks smart in the quarter and always invoices at loan-shark rates in year two.
Module 7 — The Sales Bridge
The idea: the marketing→sales handoff fails structurally (different clocks, different counts) unless both sides sign the same gate definitions — the Attract→Earn hand-raiser standard and the Earn→Win qualification standard — plus an SLA (the 24-hour hand-raiser response; conversion decays by the hour, and the response clock is part of the offer) and a monthly feedback ritual. The enablement kit industrializes marketing's promises — built once from the Messaging Doc, designed for the committee meeting we're not in (the champion test: forwardable with no cover note). The sales narrative (Dunford) teaches the buyer how to choose — insight → honest alternatives map → derived criteria → us + proof — one story, every seller, same way. The CRM is where all of it either gets recorded truthfully or dissolves into anecdote — including the cross-OpCo triggers that make the flywheel software instead of hope.
What your team owes you: the co-signed definitions + SLA sheet (T21) · a kit built from stall-point walks of real deals, not brainstorms · the narrative (T22), fairness-tested and table-read · CRM trigger tasks live for the flywheel, and a data-trust number that stops being embarrassing.
Questions to ask:
- "What's our actual hand-raiser response time, measured — versus the 24-hour standard we signed?"
- "What are the top three return-reason codes on handoffs — and what did marketing change because of them?"
- "Could our champion forward this proposal artifact to the skeptic with no cover note?"
- "When the last sell-out closed, did the CPM proposal task fire — and was its SLA kept?" (The flywheel is real or it isn't; the CRM knows.)
Module 8 — AI-Era Marketing
The idea: AI collapses the cost of competent execution to near zero; what everyone can do cheaply, nobody differentiates with. Both failure modes are live: abstinence (out-produced 10:1 at matching quality) and surrender (synthetic flood, penalized by buyers). The house posture: leverage inside standards — AI touches everything, ships nothing. The Messaging Doc and its siblings are the context files that keep machine output on-position; the human line (POV, taste, relationships, accountability) is written per OpCo and never delegated. And machines now read us before buyers do — the answer engines choosing citations, the committee's chatbot summarizing our proposal — which makes entity hygiene and citable proof Win-stage armor, not just marketing hygiene.
What your team owes you: the AI Leverage Map & Guardrails (T23) — context library owned and current, workflows mapped (AI does / human does / human reviews), the fabrication rule in force, the human line written · pilot metrics showing leverage (hours reclaimed at held quality) · the extended citability audit including "is CHARLESGATE a good choice — what are the risks?" run on ourselves quarterly.
Questions to ask:
- "Show me the human line for our OpCo — what never gets delegated, in writing?"
- "Where did a generated number or claim last get caught before shipping — and would it have been?"
- "What share of the team's hours now go to un-generatable work (relationships, stance, proof) versus assembly?" (The truest adoption metric — it should rise every quarter.)
- For your founder-voice people, the test is simple: could they defend every posted sentence as theirs at a dinner?
Module 9 — Capstone: The OpCo Growth Plan
The idea: the program's exit exam is a real plan. Each OpCo team scores all five stages with evidence, names the binding constraint (the flow test: if this stage improved, does output rise — or does the bottleneck just move?), compresses the year onto one page (position → ICP → constraint → motion stack → ≤3 campaigns → falsifiable scorecard commitment, plus the not-doing list), defends it, and converts it into a 90-day sprint with owners, definitions of done, and kill criteria.
Your role is the point of this module — see Part 3. The one-page plan and the sprint are co-signed by you. The defense session works only if you attack it properly.
Part 3 — The President's Operating Role
The system asks four things of you per year, plus one standing behavior.
1. The annual defense session (Module 9). Your team presents the one-page plan and the sprint. Your job is diagnosis seeking holes, not approval theater. The standard attacks, in order: the constraint ("convince me it's not the counter-diagnosis"), the sacrifice ("show me the not-doing list — what did you decline?"), the capacity ("show me the hours math — first drafts are always 130%"), the falsifiability ("which numbers does this plan promise, and when do we know it failed?"). A defense where nothing changed was a ceremony. Then co-sign — the signature means you own the sacrifices too, and you defend them when someone's favorite idea isn't on the page.
2. The quarterly Growth Code review. One hour: constraint re-check against the scorecard, campaign slate for the quarter (≤3, brief-backed), motion-stack health against leading indicators, budget re-allocation. You hold the time-to-signal line here: no killing 9-month motions at month 3, no zombie extensions past written kill dates.
3. The monthly one-pager. Fifteen minutes of reading, thirty of meeting, decisions at the end. You enforce the genre: narrative with confidence labels (know/believe/guessing), kill/scale calls made per written criteria, asks in decision grammar. If the "decisions requested" block is empty two months running, ask why the meeting exists.
4. The signatures. Five artifacts carry yours: the Motion Stack Canvas (T13) · the budget canvas with its downturn paragraph (T18) — signed in daylight, before the pressure · the lifecycle/SLA sheet (T21) alongside your sales lead · the one-page plan (T24) · the sprint (T25). Everything else is your team's to own.
5. The standing behavior — the two questions. Any growth complaint, any budget ask, any shiny tactic, all year: "Which stage of the Code is constrained — show me the stage metrics" and "what campaign or play does this belong to?" Asked consistently, those two questions do more for your OpCo's marketing than any budget increase. They're also how the team learns you read the one-pagers.
Red flags — how weak marketing thinking smells
- No sacrifice anywhere. No anti-ICP, no not-doing list, no killed motions. A strategy that gave nothing up isn't one.
- Vanity numbers leading the report. Impressions, raw followers, MQL counts. Apply the vanity test out loud.
- Every dashboard green while MER is flat. Something is grading its own homework.
- "We need more leads." Almost always a mis-diagnosis; make them show the stage metrics.
- Creation work judged on capture windows. The best long-horizon work murdered in budget review — refuse the cross-judging.
- A calendar with no cut list, briefs with no kill criteria, pilots with no verdicts. Planning at 130%, betting without stakes, zombies.
- Marketing that could wear any competitor's logo. The swap test, applied to everything from the one-liner to the ad.
- AI volume without the bar. More output, less specificity — the flood, self-inflicted, in a finite universe that remembers.
The HoldCo layer (all presidents, together)
Three things no single OpCo owns but every OpCo's plan depends on: Michael's founder voice (shared air cover across all stacks), the cross-OpCo flywheel (trigger tasks with owners and SLAs — every closing feeds someone else's pipeline; the structurally uncopyable advantage, but only as a system), and shared assets (the market data reports, the play library, the AI infrastructure — funded as a HoldCo line with named governance, or quadruple-taxed and starved). The four one-page plans get read together annually: four constraints, one resource pool, sequenced deliberately. That reading is where the HoldCo out-executes four separate companies sharing a logo.
Companion documents: CG_Growth_System_Framework.md (the wall version — read it once in full) · the module files and workbooks (your team's track) · CG_Marketing_Sales_Glossary_v2.md (when a term in a meeting sounds slippery, it's defined there). Exec track derived from Academy Modules 1–9; teaching-draft examples and numbers carry the same validation caveat as everything in the program.
Growth Code Field Module F1
Attribution honesty, the founder distribution engine, and SEO + AEO: three sharpeners, with templates T26–T28.
Attribution Honesty, the Distribution Engine & AEO
CHARLESGATE Growth Code Academy · Field Module (sits alongside Modules 1–9) · Status: COMPLETE · Built 2026-08
What this is: three sharpeners for how we run the modern Code, prompted by an outside case study (Adam Holmgren of Fibbler, who bootstrapped a paid-ads attribution tool to $1M ARR with a team of two, almost entirely on his own LinkedIn and amplified posts) and by a refresh of current answer-engine research. This is a field module, not a tenth subject. It patches and deepens threads that already live in the Code: attribution (5.2, 2.6), the founder/organic engine (2.7, 3.4), and SEO to AEO (2.5, 8.4). Read those first. This module assumes them and pushes each one step further into practice.
A candor note before you start. Most of what follows is already doctrine here. The Code taught triangulation over false precision two modules ago. It taught organic-proves-then-paid-scales, and it taught being the cited answer. What the Fibbler case adds is not new theory. It adds a harder edge on three moves teams still soften in the field: deliberately not attributing brand spend, running the organic feed as a literal test market with a promotion gate, and the current mechanics of getting quoted by a machine. Where the case does not transfer, this module says so plainly rather than importing it.
By the end of this module you can: set an attribution posture that differs by spend type, and defend the decision to stop attributing your best top-of-funnel work · run a founder distribution engine as a batch-produced test market with an explicit paid-amplification gate · execute a current AEO checklist (structure, schema, entity, off-site mentions) and measure share of model, not rankings alone · and map all three back to the five stages so they land in the plan, not in a slide.
How to use this module: one sitting per lesson, three weeks, or a half-day working session for a president plus their marketing lead. Every lesson ends with Do the Work and a template. The three templates (T26–T28) live as fillable canvases in the appendix at the end of this file. Prerequisites: self-reported attribution live (2.1), the Demand/Capture Split (Template 9), and the Channel Plan (Template 6). Without those, this module is counting without categories.
A note on examples: CHARLESGATE examples are illustrative teaching drafts, directionally right, but every number and claim gets validated against current company data before anyone acts on it.
Lesson F.1: Attribution Honesty: Stop Attributing the Brand
First principles
The founder of an attribution tool was asked how he attributes his own advertising. His answer: he does not. "I care zero about attribution for our own advertising. I just want to reach as many of the right people as possible and engage with them as much as possible." The man sells attribution software. For his own top-of-funnel spend he ignores the thing he sells, because he understands what it can and cannot see.
That is not a contradiction. It is Lesson 5.2 stated at its logical end. Attribution answers one narrow question well: which trackable click preceded a conversion. For demand capture, that answer is genuinely useful and you should chase it hard. For demand creation, the same tool is worse than useless, because it will confidently credit the last click of a journey it watched almost none of, and the budget will follow the credit. The trap is not that attribution lies. The trap is that it lies precisely, in a dashboard, which is far more persuasive than an honest approximation.
So the posture is not "attribution good" or "attribution bad." The posture is: attribution changes job by spend type. Capture spend gets attributed to the click. Creation and brand spend get measured a different way entirely, by reach into the right audience, by engagement, and by mental availability. Push last-click discipline onto brand spend and you will cut the brand spend, because it will never win a last-click argument against a retargeting ad. The retargeting ad is standing at the finish line taking credit for the race.
Two ideas do the work here.
Engagement is the proxy for memory. You cannot measure whether a future buyer remembers you. You can measure whether the right people stopped, reacted, replied, saved, and came back. Engagement from ICP humans is the closest leading signal you have that a memory formed. The Fibbler read on why most companies waste ad money is sharp: they target and reach the right people, then fail at engagement, because the creative and message are forgettable. Reach without engagement builds nothing. Engagement is the tell.
Over-attribution is self-harm. The spiral from 5.2, restated as a warning you will actually face in a budget meeting: software over-credits capture, capture gets funded, creation gets cut, the pipeline creation was quietly filling thins out a year later, cost-per-lead rises, the response is more capture spend, repeat until the well is dry. Every step was defended with data. The data was a true answer to the wrong question.
Why it matters
Because this is the exact place our best work is most exposed. The market letter, the founder voices, the referrer network, the AEO citations, the hosted rooms: structurally invisible to click attribution, and structurally the moat. If the instrument cannot see the moat, the instrument does not get a vote on funding it. Fix the instrument before you obey it.
There is a second, quieter payoff. Deciding in advance that you will not attribute brand spend removes a standing argument from every review. The team stops trying to prove the unprovable and starts steering by the signals that actually move: reach, engagement, self-reported attribution, and the marketing efficiency ratio. Less theater, more steering.
How it works
1. Set the posture by spend type, in writing. Two columns.
- Capture spend (search ads on trigger queries, review-site presence, retargeting the in-market): attribute hard. Cost-per-SQL, win rate, speed-to-lead. Chase the click. This is where the click-tracking earns its keep.
- Creation and brand spend (founder content and its amplification, the letter, the data reports, sponsorships, air cover): do not attribute to a click. Judge on reach into ICP density, engagement from ICP humans, self-reported attribution mentions, and movement in the aggregate signals (branded search trend, direct trend, "already knew you" rate). Give it a fair clock, quarters not weeks.
2. Pick one honest number for the whole system. The bluntest instrument is the hardest to fool: MER, marketing efficiency ratio (total revenue divided by total marketing spend, per OpCo, trended). If every per-channel dashboard looks great and MER is flat, a per-channel dashboard is lying somewhere. When a debate over channel credit gets religious, MER is the referee. One number the whole room trusts beats five numbers each side cherry-picks.
3. Run an engagement read on brand spend, monthly. Not impressions. Engagement from the right people: replies, saves, shares, DMs, comments from ICP accounts, return visits, and the engaged-account density on any ABM list while founder content runs (the 3.2 crossover metric). If reach is high and this is flat, the creative is the problem, not the targeting. Fix the message before you touch the audience.
4. For high-value deals, mine the engagement list by hand. The Fibbler move that transfers cleanly: for higher-ACV opportunities, do not automate the follow-up to people already engaging with your content and ads. Pull the list of most-engaged accounts (visible in the ad manager, in the CRM, in who keeps opening the letter) and have a human reach out with a genuine, specific message. Automation is for low-ACV volume. A relationship sale worth six or seven figures deserves a person. This is Lesson 3.5 (outbound that does not feel synthetic) aimed at an audience that is already warm, which is the highest-yield outbound there is.
CHARLESGATE example
Michael's HoldCo LinkedIn voice, run through the posture (teaching draft). It is creation and brand spend, full stop. So we do not ask what it "converted" last month, and we kill that question if it shows up in a review. We ask four things instead. Reach: are we landing in front of the right owners, developers, and board members, measured by ICP-follower density, not total impressions. Engagement: are those people reacting, saving, and replying, and are developers on the CRG named-account list engaging more in the months the content runs. Self-reported: are "I follow Michael" and "saw your post" showing up in the how-did-you-hear log. MER: is HoldCo revenue per marketing dollar holding or improving over the trailing year. If a budget meeting proposes cutting Michael's content support to fund more search ads because "the search ads are attributable and the content is not," that is the exact spiral from 5.2, and the posture doc is the pre-signed answer: search flexes to its honest ceiling first, the founder engine is protected. Same logic protects the CPM lead's voice and the market letter. We know the letter influences signings because signers tell us so verbatim. Click attribution will never show it. We believe MER and self-reported together are truer than any single dashboard. We are guessing on the exact contribution split, and we are comfortable guessing, because the alternative is a precise fiction that would defund the letter.
Do the Work
Template 26 (Attribution Posture Map): list every marketing line, sort each into capture (attribute to click) or creation/brand (measure reach, engagement, self-reported, MER), and write the one-sentence rule for each column. Name your one honest system number (MER per OpCo) and where it lives. Then pull your current most-engaged accounts and hand five of them to a human for a real outreach this week. Gate: if any creation line is currently being judged on a capture window, that is the first thing the map fixes.
Lesson F.2: The Distribution Engine: Organic Test Market, Paid Amplifier
First principles
Most teams believe their constraint is content. It is usually distribution. Fibbler's entire growth came from one person posting consistently and then paying to amplify only the posts that already worked. The content was the cheap part. The system around it was the asset: a repeatable way to produce volume, let the audience vote, and put money behind the winners.
Lesson 2.7 gave us the organic operating system (pillars, document-don't-create, the editorial bar, engagement as the real networking). Lesson 2.6 gave us the rule that organic proves and paid scales. Lesson 3.4 made the founder voice a motion with its own economics. This lesson connects the three into one loop and names the gate in the middle that teams keep skipping.
The loop: produce in batches, publish on clear pillars, let the audience vote, and amplify only the winners.
Four mechanics make it run.
Batch production. Fibbler writes the week's posts in one sitting on Sunday night, working from one or two sentence note-outlines jotted during the week while reading other people's posts. Creation and distribution are separated. You do not write a post the day it ships. You harvest raw material continuously (the building turnaround, the pricing call that went sideways, the number that surprised you) and you shape a week of it at once. Batching is how a busy operator sustains cadence, which is the whole game, because the channel rewards showing up for quarters, not sprinting for three weeks.
Clear pillars, known outcomes. Fibbler runs three explicit pillars: the product topic (attribution), building the company in public, and operator tactics (the thing he is expert in). An occasional fourth personal pillar. He is deliberate that different pillars do different jobs: personal and build-in-public posts grow followers, trust, and surface area (they bring investors, partners, and hires), while the topic and tactics posts drive actual signups. You do not measure a trust post by signups. You know going in which job each pillar does.
Volume reveals winners cheaply. Twelve-plus posts a month is not vanity. It is a cheap way to discover which ideas land before you spend a dollar amplifying them. You cannot predict the winner. You can afford to find it, if your production is batched and your bar is honest.
Format serves the scroll. Pure text stopped working for Fibbler; image posts now stop the thumb. The point is not "use images." The point is that the format is a variable you test like any other, and a raw, human, authentic look beats polished corporate wallpaper. A distinctive recurring visual asset (Fibbler uses a pink lion mascot with hundreds of variants, plushies at events) builds mental availability. We have a doctrine for this already: distinctive brand assets, Module 6. The founder engine is where they get reps.
The gate everyone skips: the promotion threshold. Fibbler only promotes an organic post into a paid Thought Leader ad after it clears roughly 100 likes, and he rotates a handful of proven posts through the paid layer, pulling any whose click-through decays. Organic is the test market. Paid is the multiplier. The threshold is what stops you from paying to scale a dud. Almost nobody runs this gate. They either never amplify (and the winners die in the feed after 48 hours) or they amplify everything (and pay to distribute their weakest work).
Why it matters
This is the compounding Attract engine for the 95% who are not in-market, at near-media-cost. It feeds half of Module 3: ABM lands warmer, outbound feels less synthetic, and the dark funnel runs straight through the shares and DMs. And it is the most human-legible proof of the AI-era thesis. Feeds are flooding with generated sameness. A named person with real deals and a real number is the scarce format. AI pulls everyone to the middle. A property manager telling the truth about a botched special assessment is not in the middle.
Where this does NOT transfer (read before you copy the playbook)
Fibbler sells to marketers. That is easy mode: his audience lives on LinkedIn, engages professionally, and buys a low-friction product they can try themselves. We are three steps harder, and pretending otherwise will burn budget.
- Our like-counts will be smaller, and that is fine. A board president or a developer is less likely to publicly like a post than a growth marketer is. Do not import the literal 100-like threshold. Set the gate on ICP-density signals: engagement, saves, and DMs from the right accounts, plus profile visits and connection requests from target titles. Fifty of the wrong likes is a worse signal than three developers in the replies. Density over volume, as always in our finite universes.
- Our sale is considered and high-ACV, so the human touch weighs more. Fibbler's product-led motion can automate the low end. Ours cannot. The engine's real payoff for us is not self-serve signups. It is warm surface area that makes the manual, relationship-driven Win stage land. The posts are the bait; the DMs and the human follow-up are the pipeline (3.4).
- Do not cargo-cult the mascot or the CTV specifics. A distinctive asset is sound doctrine; a pink lion is his. LinkedIn CTV placements and Thought Leader ad mechanics are platform-specific and will change. Take the structure (test organic, gate, amplify winners, two paid layers), not the props.
How it works
1. Separate harvest from production. A running notes file per voice. One or two sentence outlines captured continuously. One batch session a week that shapes the week's posts. Cadence target: 2–3 posts per week per voice, sustained for quarters (2.7's bar), which is 12-plus shots a month to find winners from.
2. Fix the pillars and their jobs. Three pillars per voice, each with a known outcome. A working default for our leaders: the domain-topic pillar (drives inbound and signups), the build-in-public or operating pillar (grows trust, hires, and partners), and the operator-tactics or category-POV pillar (builds authority in the lane). An occasional personal fourth. Write the job next to each pillar so nobody judges a trust post by pipeline.
3. Run the promotion gate. Publish the batch. Watch for the ICP-density signal, not raw likes. A post that clears the gate becomes a candidate for paid amplification. Keep 3–4 proven posts live in the paid layer at once, rotate them, and pull any whose engagement or click-through decays. Nothing gets paid budget until it earned organic proof from the right people. This one rule deletes most wasted spend.
4. Amplify in two layers (this is Lesson 2.6's air cover and retargeting, given Fibbler's cleaner structure):
- Cold layer, expand reach: promote the proven post to a broad-but-targeted ICP audience (by company size, industry, and specific titles that match the buyer, not vanity "head of" titles), at low frequency, to push new right-fit people into your world.
- Retargeting layer, build frequency: hammer the people already engaged (site visitors, letter readers, past engagers) with higher frequency to cement mental availability. Set a frequency cap so it stays present, not creepy.
5. Harvest the engaged for the human motion. Pull the most-engaged accounts and route the high-value ones to a person for real outreach (F.1, step 4). The engine's job is to manufacture warm, not to close.
6. Value first, product last. Fibbler rarely posts about the product directly. He posts adjacent to the topic and mentions the product at the end, if at all. For us: teach, show the work, name the number, take the position. The pitch is the exception, not the pattern.
CHARLESGATE example
Two voices, one engine (teaching draft).
Michael, HoldCo altitude. Pillars: (1) Boston market POV and where owners should push (topic, drives inbound to all four OpCos), (2) building CHARLESGATE in public, the holding-company thesis and the operating lessons (trust and surface area, brings partners, hires, and CG Capital conversations), (3) the creativity-moat and company-building POV (authority in the lane). Batch Sunday. Gate on developer and owner engagement, not likes. Winners get amplified: cold layer to Boston owners and developers by title, retargeting layer against the CRG named-account list and letter readers so the 50 developers keep seeing him before CRG's 1:1 outreach lands.
Bryant, AFF. Pillars: (1) teardowns of what makes development marketing convert (topic, drives agency inbound), (2) building the agency and the craft in public (trust, brings talent and referrals), (3) creative POV and honest post-mortems (authority). Same loop. AFF is the natural founder-led OpCo because agency buyers purchase judgment and taste, and taste is only observable in public (3.4). The promotion gate for AFF can lean more on raw engagement than CPM can, because AFF's buyers behave more like Fibbler's (marketers who engage publicly). We know the loop works when engaged-account density on the target lists rises in the months the voices run. We believe the two-layer amplification compounds mental availability. We are guessing on the exact paid budget split between layers, so we start small, watch the engaged-account lift, and scale the layer that moves it.
Do the Work
Template 27 (Distribution Engine Canvas): for one voice, define the three pillars and the job of each, set the batch cadence and the harvest method, define the promotion gate in ICP-density terms (what signal, from which accounts, promotes a post), and design the two amplification layers (cold audience definition, retargeting audience, frequency cap). Name the engaged-list handoff to a human. Run it for 30 days, then review against the Channel Plan (2.7's sprint, now with the gate): commit at cadence or kill with reasons. No zombie presence.
Lesson F.3: SEO + AEO: Being the Cited Answer (2026 Field Update)
First principles
Search did not die. It grew a mouth (2.5). The buyer still has a question and still asks a machine. The machine now composes an answer and cites a few sources instead of listing ten links, and a large and rising share of research ends inside that answer with no click. The job moved. SEO asked whether we rank. AEO (answer-engine optimization) asks whether we are the source the machine cites, and the name it says, when it answers our buyer's question.
The single most clarifying finding from the current research: AEO is not a subset of SEO ranking. An Ahrefs Brand Radar analysis of 15,000 prompts found that only about 12% of the content AI engines cite also appears in Google's top ten results. Read that again. Roughly 88% of what the machines quote does not come from the traditional top ten. Ranking and getting cited are different games with overlapping but distinct rules. You can win one and lose the other.
Answer engines choose sources by entity clarity, structure, freshness, and reputation, more than by legacy rank. And there is a justice to it that keyword-era SEO never had: the machine is trying to give its user the most credible, specific, useful answer, which rewards exactly what our Code already builds. Honest, specific, structured, sourced answers from a consistent, well-reviewed entity get cited. This is the Endless Customer method (Marcus Sheridan's current framing of They Ask, You Answer, now in its second edition) doing double duty. The radical-transparency, answer-the-buyer's-real-questions discipline that earns human trust is the same discipline that earns machine citation. TAYA was pre-optimized for the machine reader. We just have to structure it correctly and prove the entity.
Why it matters
Run the trigger moment forward. The board president asks an assistant "how do I switch property management companies in Boston, and who is good?" The answer names two or three firms. If we are in it, we are on the shortlist before any visible funnel begins. If not, we are invisible at the moment of maximum intent, and no capture budget reaches inside the answer box. This is Attract and Earn compressed into one machine-mediated moment, and increasingly it is a Win-stage moment too, when the committee pastes our proposal into a chatbot and asks "is this credible, what should we push back on" (8.4).
The strategic window is still open. Our niches (condo management, mid-size new-dev sell-outs, Boston rental data, multifamily lease-up marketing) are barely contested in AI answers. Early, consistent, citable presence compounds; catching up later costs multiples. And the off-site lever is underappreciated: the research finds unlinked brand mentions correlate with AI citations far more strongly than backlinks do (one analysis put it at 0.664 versus 0.218). The machine cares that credible places across the web talk about you, more than that they link to you. That reframes the whole earned-media and reputation program as a machine-channel investment.
How it works
The 2026 field checklist. Keep the SEO fundamentals as the substrate (crawlable, fast, intent-matched, real backlinks), then add the AEO layer.
1. Design for the four answer intents. Most answer opportunities fall into four buckets, and each wants a different shape: definitional ("what is X") wants a concise plain-language answer up top; process ("how do I X") wants an ordered, numbered workflow with a checklist; comparison ("X vs Y") wants a balanced table with real evaluation criteria; decision ("best X for Y", "should I X") wants an honest recommendation including who it is not for. Map each buyer question to its intent and build the matching shape.
2. Lead every section with an extractable answer block. A 40 to 60 word direct answer immediately under a question-shaped heading, then the depth below it. Machines quote what they can cleanly lift. If the machine has to paraphrase you, it may paraphrase you wrong. Hand it the sentence you want repeated. One question per section, clean headings, summary boxes.
3. Get the schema right. Clean, validated JSON-LD tied to visible content is the highest-leverage technical move, especially for Google AI Overviews and Gemini. The four that matter most: Organization, Article, FAQPage (with question-shaped headings that match real buyer questions), and Person (author) linked to the Organization so the machine builds a knowledge graph of who is expert here. Entity linking is the point. Do not mark up content that is not on the page.
4. Clear the bots and the plumbing. The AI crawlers (GPTBot, ClaudeBot, OAI-SearchBot, and the AI Overview fetchers) have to reach and read your pages. Check robots.txt is not blocking them and that key content is server-rendered enough to be read cleanly. On llms.txt: publish one if you like, it is cheap, but the current evidence is that it does not yet move citations, so do not treat it as a priority or a fix.
5. Build the entity across the open web. Consistent name, services, and locations everywhere (NAP hygiene). Named experts with real footprints. Reviews with volume, recency, and good responses (sentiment echoes nearly verbatim into answers). Presence in the third-party sources the machines actually cite (the directories, association pages, and press that show up in your audit's source log), and unlinked brand mentions in credible places, which the research says matter more than backlinks. Reddit, industry forums, local press, and association directories are entity fuel. Note the Code loop: reviews and press are Repeat-stage outputs feeding Attract, now machine-readable (2.5, 8.4).
6. Publish original data, the citation magnet. Machines prefer sources with specifics nobody else has. Our unfair advantage is operating data: rent and turnover reality from thousands of managed units, absorption curves from real sell-outs, lease-up velocity from real projects. "Boston rental market report, [year], from N managed units, methodology stated, named expert attached" is un-generatable, and every AI answer about the Boston rental market wants to cite something exactly like it. Refresh it on a schedule, because stale data loses citations to fresher sources. The maintenance is the moat.
7. Measure share of model, not rankings. The new instrument panel:
- Share of model (share of voice in AI): run a fixed set of 20 to 50 buyer-intent prompts across ChatGPT, Perplexity, Gemini, and Google AI Mode monthly; count how often you are mentioned; divide your mentions by all brand mentions in the set. A spreadsheet and a prompt set do this for free; tools help at scale but are not required to start.
- Citation rate and recommendation position: how often you are cited, and your average slot in the answer.
- AI referral traffic: track it in GA4. Google introduced an "AI Assistant" channel grouping in May 2026; reconcile citation share against that referral traffic as the closest visibility-to-click read AI search offers.
- Accuracy: log whether what the machine says about you is correct, and feed errors into the fix list.
Expect three to six months to measurable movement on a consistently published, established domain. And one number worth watching because it changes the ROI argument: multiple analyses report AI-sourced visitors convert at a markedly higher rate than classic organic (Ahrefs reported AI traffic was about 0.5% of sessions but 12.1% of signups; treat the exact figures as reported-elsewhere, not ours, and validate on our own GA4). The direction is the point: fewer, hotter visitors.
CHARLESGATE example
CPM owner acquisition (teaching draft). Prompt set for the monthly share-of-model read: "best condo management company Boston," "how much does condo management cost in Boston," "how to switch property management companies Massachusetts," "what to ask a property management company," "self-manage vs hire a property manager for a condo association." Suppose the audit finds we are cited on cost (the TAYA cost article's ranges get quoted) but absent from "best" and "switch," where a national aggregator and two directories dominate. The four-part fix: restructure the switching guide answer-first with FAQPage schema and a 50-word answer block per section (structure); get accurately listed in and mentioned by the directories and association pages the machine keeps citing, and push the review-generation play because sentiment echoes into answers (entity and reputation); publish the rental report with a named CPM expert and Person schema linked to the Organization (original data and provenance); confirm GPTBot and the AI fetchers can read the pages (plumbing). Re-run the prompt set in 90 days and watch share of model, not rankings. The same play for Authentic aims a different machine question ("best multifamily lease-up marketing agency," "how to market a new apartment building") at developers and owners, so the machine cites AFF's craft content and case data. Demand creation by citation, feeding the warm outreach. We know our niches are thin in the answers today. We believe consistent citable publishing widens the lead while the window is open. We are guessing at the exact time-to-citation, which is why the instrument is a monthly prompt set, not a forecast.
Do the Work
Template 28 (AEO Field Checklist and Share-of-Model Tracker): this extends Template 10-B. Run the seven-point checklist against your top ten buyer questions (intent type, answer block present, schema present, bot access confirmed, off-site entity check, original-data asset, tracked). Build the 20-to-50 prompt set and run the first monthly share-of-model read across four assistants. Output the quarterly machine-channel plan: one structure fix, one entity/reputation fix, one data asset, one measurement setup (GA4 AI-referral tracking live). Owner and re-run date on the calendar. This is a standing instrument now, not a project.
WHERE THIS LANDS IN THE CODE
Every piece maps to a stage. That is the test of whether it belongs in the plan.
| Piece | Primary stage(s) | How it shows up in the plan |
|---|---|---|
| Attribution posture by spend type (F.1) | Measurement across all five; protects Attract and Earn budget | The posture doc sits with the Budget Canvas (T18); MER is the referee line in the monthly one-pager (5.5) |
| One honest number / MER (F.1) | All five | The system-level honesty check on the scorecard (T16) |
| Manual outbound to the engaged (F.1) | Earn → Win | A play card (T14): pull most-engaged, human outreach on high-ACV |
| Distribution engine and pillars (F.2) | Attract (feeds Earn) | The founder-brand plan (3.4) gains the batch cadence, the gate, and the two paid layers |
| Promotion gate, organic-to-paid (F.2) | Attract | The rule inside the paid line of the Budget Canvas: nothing scales unproven |
| Distinctive asset / mental availability (F.2) | Differentiate → Attract | Reps for the Brand Code's distinctive assets (Module 6) |
| AEO checklist and entity build (F.3) | Attract + Earn, armor in Win | The standing machine-channel plan (8.4), extended with 2026 mechanics |
| Original-data assets (F.3) | Attract (cited), Repeat feeds it | Citation magnets on a publishing calendar; reviews/press loop (Repeat → Attract) |
| Share-of-model measurement (F.3) | Measurement | Monthly prompt set; GA4 AI-referral channel; quarterly re-audit |
FIELD MODULE EXIT CHECKLIST
You are done with this field module when your OpCo has, on paper and reviewed:
- Attribution Posture Map (T26): every line sorted capture vs creation/brand, the rule per column written, MER named as the one honest number, five engaged accounts handed to a human this week (F.1)
- Distribution Engine Canvas (T27): three pillars with their jobs, batch cadence and harvest method, a promotion gate defined in ICP-density terms, two amplification layers designed, the engaged-list handoff named (F.2)
- A 30-day engine run completed for one voice, reviewed against the Channel Plan, committed or killed with reasons (F.2)
- AEO Field Checklist run against the top ten buyer questions, with the four-part gap plan and GA4 AI-referral tracking live (T28 / F.3)
- First monthly share-of-model read logged across four assistants, quarterly re-audit calendared with an owner (F.3)
NEW WORKBOOK TEMPLATES THIS MODULE ADDS (T26–T28)
Fillable canvases in the appendix below, in the standard workbook style (blank canvas plus worked CHARLESGATE example).
- Template 26: Attribution Posture Map (F.1): spend sorted by attribution job, per-column rules, the one honest number, the engaged-account handoff.
- Template 27: Distribution Engine Canvas (F.2): pillars and jobs, batch cadence, the promotion gate in density terms, two-layer amplification, engaged-list-to-human handoff.
- Template 28: AEO Field Checklist and Share-of-Model Tracker (F.3): the seven-point checklist per buyer question, the prompt set, the monthly read, the quarterly machine-channel plan. Extends T10-B.
NEW GLOSSARY TERMS INTRODUCED (extend the glossary)
attribution posture (F.1, differs by spend type) · the one honest number (F.1, MER as system referee) · engagement as memory proxy (F.1) · over-attribution spiral (F.1) · distribution engine (F.2, organic test market plus paid amplifier) · promotion gate (F.2, the organic-to-paid threshold, set on ICP density for us) · batch production / harvest-then-shape (F.2) · pillar job (F.2, each content pillar has a known outcome) · cold layer / retargeting layer (F.2, two-layer amplification) · share of model (F.3, share of voice in AI answers) · answer block (F.3, the 40–60 word extractable answer) · answer intents (F.3, definitional / process / comparison / decision) · entity fuel (F.3, off-site mentions the machine triangulates) · AI Assistant channel (F.3, GA4 referral grouping, May 2026)
Appendix: Workbook Templates T26–T28
Rules of the workbook (unchanged): every template pairs a blank canvas with a worked CHARLESGATE example; the examples are teaching drafts, validated against real data before external use; plain language only; date and version these as living documents.
TEMPLATE 26: ATTRIBUTION POSTURE MAP
(Lesson F.1. Decide, in writing, what you attribute to a click and what you refuse to. The refusal is the point.)
Blank canvas
Part A: sort every line
| Marketing line | Capture (attribute to click) | Creation/Brand (do NOT attribute to click) | How it is judged instead |
|---|---|---|---|
Part B: the rules and the number
| Item | Your answer |
|---|---|
| Capture-column rule (one sentence) | Attribute to the click: cost-per-SQL, win rate, speed-to-lead |
| Creation/brand-column rule (one sentence) | Do not attribute to a click: reach into ICP density, ICP engagement, self-reported mentions, MER, over quarters |
| The one honest number (MER), where it lives, who trends it | |
| The pre-signed protection line (what flexes first in a cut) | |
| Engaged-account handoff: who pulls the list, who does the human outreach, this week |
Gate: any creation line currently judged on a capture window gets fixed here first.
Worked example: CPM (teaching draft)
| Marketing line | Capture | Creation/Brand | Judged by |
|---|---|---|---|
| Google Ads, trigger queries | ✓ | Cost-per-SQL, capped at honest ceiling | |
| Retargeting in-market visitors | ✓ | Cost-per-SQL, frequency-capped | |
| Market letter | ✓ | List growth, "read your letter" mentions, MER | |
| CPM lead's LinkedIn + amplification | ✓ | ICP engagement, self-reported "saw your post", engaged-account lift | |
| Rental data report | ✓ | Citations, branded search lift, referral pipeline | |
| Referrer lunches | ✓ | Referral-sourced pipeline (quarters) | |
| One honest number | MER per OpCo, trended in the monthly one-pager | ||
| Protection line | Search flexes to ceiling first; letter and founder engine last | ||
| Engaged handoff | Alana pulls top-engaged monthly; Todd/CPM AE does the human outreach on 8+ unit prospects |
The finding this map produces: the moat lines (letter, founder voice, data, referrers) are structurally unattributable, so we protect them by rule and steer them by MER plus self-reported, not by a dashboard that cannot see them.
TEMPLATE 27: DISTRIBUTION ENGINE CANVAS
(Lesson F.2. Turn a founder voice into a batch-produced test market with a paid-amplification gate. One canvas per voice.)
Blank canvas
Part A: the pillars and their jobs
| Pillar | What it covers | The job it does (be specific) | How it is measured |
|---|---|---|---|
| 1. Domain topic | Inbound / signups | ||
| 2. Build-in-public / operating | Trust, surface area, hires, partners | ||
| 3. Operator tactics / category POV | Authority in the lane | ||
| 4. Personal (occasional) | Followers, relatability |
Part B: the production system
| Item | Your answer |
|---|---|
| Harvest method (where raw material is captured continuously) | |
| Batch session (day/time, how many posts per session) | |
| Cadence target (posts/week, sustained for quarters) | 2–3/week |
| Format defaults + distinctive asset |
Part C: the promotion gate (density, not raw likes)
| Item | Your answer |
|---|---|
| The signal that promotes a post (engagement/saves/DMs from WHICH accounts) | |
| Who reviews and promotes, and how often |
Part D: two-layer amplification + handoff
| Layer | Audience definition | Frequency | Objective |
|---|---|---|---|
| Cold (expand reach) | ICP by size/industry + specific buyer titles | Low | New right-fit reach |
| Retargeting (build frequency) | Site visitors, letter readers, past engagers | Higher, capped | Mental availability |
| Engaged-list handoff | Most-engaged accounts → named human for outreach | Warm → pipeline |
Worked example: Michael, HoldCo voice (teaching draft)
| Pillar | Covers | Job | Measured by |
|---|---|---|---|
| 1. Boston market POV | Where the market is going, what owners should demand | Inbound to all four OpCos | Inbound intros, self-reported "follow Michael" |
| 2. Building CHARLESGATE | HoldCo thesis, operating lessons | Trust, partners, CG Capital conversations, hires | DMs, partner/investor inbound |
| 3. Creativity-moat / company-building POV | The AI-era thesis, taste as moat | Authority in the lane | Speaking invites, engaged-account density |
Production: running notes file; batch Sunday, 5 posts; 2–3/week; image + human text, consistent visual signature. Gate: promote when developers/owners (target titles) engage, save, or DM, not on raw likes. Amplification: cold layer to Boston owners/developers by title; retargeting against the CRG 50-developer list and letter readers so CRG's 1:1 outreach lands warm. Handoff: Alana pulls most-engaged monthly; Michael or the relevant OpCo lead does real outreach on the highest-value accounts.
The finding: the engine's payoff for us is not self-serve signups (that is Fibbler's easy mode), it is warm surface area that makes the human Win stage land.
TEMPLATE 28: AEO FIELD CHECKLIST AND SHARE-OF-MODEL TRACKER
(Lesson F.3. Extends T10-B. Make us the cited answer, and measure share of model, not rankings.)
Blank canvas, Part A: the seven-point checklist (per top-10 buyer question)
| Buyer question | Intent (definitional / process / comparison / decision) | Answer block present (40–60 words, under a question heading)? | Schema present (Org / Article / FAQPage / Person-linked)? | Bots can read it (GPTBot / ClaudeBot / OAI-SearchBot / AI Overview)? | Off-site entity check (directories, reviews, mentions machines cite)? | Original-data asset backing it? | Tracked in share-of-model set? |
|---|---|---|---|---|---|---|---|
Blank canvas, Part B: monthly share-of-model read
Fixed set of 20–50 buyer-intent prompts, run across ChatGPT, Perplexity, Gemini, Google AI Mode.
| Prompt | Assistant | Are we mentioned? | Cited (linked)? | Position in answer | Accuracy of what is said | Competitors named |
|---|---|---|---|---|---|---|
Share of model = our mentions ÷ all brand mentions in the set. Log monthly. Reconcile against GA4 AI-referral traffic (the "AI Assistant" channel). Expect 3–6 months to movement.
Blank canvas, Part C: the quarterly machine-channel plan
| Move | What | Owner | Date |
|---|---|---|---|
| 1. Structure fix (answer blocks / schema / intent shape) | |||
| 2. Entity + reputation fix (directories, reviews, off-site mentions) | |||
| 3. Original-data asset to build/refresh | |||
| 4. Measurement setup (GA4 AI-referral live, prompt set built) |
Worked example: CPM (teaching draft, compressed)
Part A highlights: "how to switch property management companies MA" (process intent · answer block GAP · no FAQPage schema · bots OK · absent from the directories the machine cites · no data asset · tracked) → restructure answer-first with FAQPage schema and a numbered workflow. "how much does condo management cost in Boston" (definitional · answer block present · cited by 2/4 assistants today · keep and refresh).
Part B findings (illustrative): share of model ~15% on the CPM set; cited on cost, absent from "best" and "switch," where a national aggregator and two directories dominate; one assistant states our service area wrong (accuracy flag → fix NAP).
Part C plan: (1) restructure the switching guide + add FAQPage/Person schema; (2) claim and correct the cited directories, push the review play (sentiment echoes into answers), fix the NAP error; (3) publish the rental report with named CPM expert and Person-to-Org schema; (4) stand up GA4 AI-referral tracking and lock the 25-prompt set. Re-run in 90 days; watch share of model climb, not rankings.
Cross-references: T26 pairs with T18 (Budget Canvas) and the 5.5 one-pager · T27 extends the 3.4 founder-brand plan and the 2.7 attention sprint, feeds 2.6's paid rules · T28 extends T10-B (Citability Audit) and the 8.4 machine-channel plan.
Sources. Inspiration and the attribution/distribution principles: the Adam Holmgren (Fibbler) interview, cited throughout Lessons F.1 and F.2, for the "attribution-tool founder ignores his own attribution" posture, the batch-and-pillars production system, the promotion-gate and two-layer amplification structure, and the manual-outbound-to-engaged move (transferable principles only; the SaaS/marketer-audience specifics are flagged as non-transferring in F.2). SEO/AEO facts (Lesson F.3), current as of August 2026: AirOps: AEO complete guide 2026 and the Ahrefs Brand Radar 12%/88% cited-vs-top-10 finding it reports; Powered by Search: AEO best practices; ALM Corp: AEO 2026 playbook (answer-first blocks, four answer intents); SiteUp.ai: structured data for LLMs 2026 and Cognizo: schema markup for AI citations 2026 (Organization/Article/FAQPage/Person schema, JSON-LD tied to visible content); Maciej Turek: how LLMs choose sources 2026 (bot access, unlinked-mentions 0.664 vs backlinks 0.218, llms.txt caveat); LLM Pulse: share of voice in AI search and SUSO: track AI traffic in GA4 (share of model, GA4 "AI Assistant" channel May 2026, 20–50 prompt sets, conversion-rate findings); Marcus Sheridan / They Ask, You Answer (the Endless Customer / question-led transparency bridge). Prior Code lineage (already sourced in their modules): Binet & Field (60/40, MER logic), Ehrenberg-Bass / LinkedIn B2B Institute (95:5, mental availability), Zinkevich/Full-Funnel (dark funnel, self-reported attribution), Gerhardt (Founder Brand), Vaynerchuk (attention, document-don't-create).
Strategy, Positioning & the Growth Code
Strategy, positioning, ICP, messaging, offers — the module everything else inherits from.
Module brief
CHARLESGATE Growth Code Academy · Module 1 of 9 · Status: COMPLETE
How to use this module: One lesson per week for seven weeks, or a two-day intensive. Every lesson ends with Do the Work — an exercise tied to a template in the Module 1 Workbook. Do not skip the exercises. Reading about positioning is like reading about push-ups.
A note on examples: CHARLESGATE examples in this module are illustrative teaching drafts — directionally right, but every number and claim must be validated against current company data before external use. That validation is part of the exercises.
1.1What Marketing Actually is
First principles
Strip away the software, the acronyms, and the agencies, and marketing is one thing: the discipline of creating and keeping customers, profitably.
Not "making content." Not "running ads." Not "the department that makes things look nice." Those are outputs — sometimes useful, often not. The function itself sits upstream of all of them, and it answers four questions in order:
- Who should we serve? (Choice)
- Why us — why should they pick us over every alternative, including doing nothing? (Difference)
- How do they come to know, trust, and choose us? (System)
- What did it cost and what did it return? (Math)
Everything else in this entire program is an elaboration of those four questions.
Here's the chain that connects thinking to doing — learn these words, because sloppy vocabulary produces sloppy work:
Strategy (the choices: who, why us, where to play) → Motions (the repeatable go-to-market approaches we commit to) → Campaigns (time-boxed pushes with an objective) → Plays (documented, repeatable sequences) → Tactics (individual actions: an email, an ad, an event) → Channels & mediums (where and in what form it travels).
Most weak marketing teams — including, historically, ours — operate bottom-up: someone proposes a tactic ("we should do a webinar"), it gets done, nobody can say which strategy it served, and six months later nobody can say if it worked. The Growth Code exists to force top-down: no tactic without a campaign, no campaign without a stage and an ICP, no stage without a position.
Why it matters
Because activity is not progress, and in a HoldCo with four OpCos and limited marketing bandwidth, every unstrategic tactic is stolen from a strategic one. The teams that win in our market aren't the ones doing the most marketing. They're the ones doing the most aligned marketing — where the LinkedIn post, the pitch deck, and the proposal all push the same position to the same buyer.
There's a second reason, new as of the last couple of years: AI made competent execution free. Anyone can generate a decent blog post, a passable email sequence, a fine-looking deck. When execution is free, the differential returns move entirely to the layer AI can't do for your competitors: the choices. Who, why us, with what proof. That's strategy. That's the moat.
How it works
A working definition to carry forward: marketing is everything the market experiences of us before, during, and after the sale. The proposal is marketing. The property manager's response time is marketing. The honest blog post about our pricing is marketing. This is why "marketing is a department" thinking fails — the department's job is to orchestrate that experience deliberately instead of letting it happen by accident.
Practical implication: before approving any marketing work, ask the three-question filter:
- Which ICP is this for? (If "everyone" — reject.)
- Which Growth Code stage is it moving? (Differentiate / Attract / Earn / Win / Repeat. If unclear — reject.)
- How will we know it worked? (A metric and a timeframe. If none — reject.)
That filter alone, applied ruthlessly, would upgrade most B2B marketing teams by 30% without a dollar of new spend.
CHARLESGATE example
Take a real recurring decision: should CPM sponsor a local condo-association trade event?
Bottom-up thinking: "It's $4K, competitors will be there, we should have a table." Maybe right, maybe wrong — no way to know.
Top-down through the filter: ICP = self-managed and dissatisfied-with-manager condo associations, 20–80 units, Greater Boston. Stage = Attract (they don't know us) and Earn (board members need trust before they'll ever switch — switching managers is painful and they've been burned). Success = 25 board-member conversations, 10 added to the market-letter list, 2 building assessments booked within 60 days. Now the decision is legible — and so is the design: don't buy a table and stand there; run a 20-minute "questions your management company hopes you never ask" session. Same $4K, entirely different outcome, because strategy chose the tactic instead of the tactic wandering in on its own.
Do the Work
Pull the last five marketing activities your OpCo did (any tactic — post, event, email, sponsorship). Run each through the three-question filter honestly. Score: how many pass all three? For each failure, write one sentence: what choice was missing? Bring the scores to the module discussion. (No template needed — a blank page and honesty.)
1.2The Growth Code: Our Operating System
First principles
Every business that grows repeatably does five things, in a loop:
- Differentiate — choose who to serve and what only you can claim.
- Attract — get discovered by the right buyers, ideally before they're in-market.
- Earn — convert attention into trust before asking for anything.
- Win — convert trust into signed business.
- Repeat — compound the relationship: retain, expand, refer, prove — and feed it all back into 1.
That's the Growth Code. It's a flywheel, not a funnel, for a first-principles reason: a funnel ends at the sale, which mismodels our economics. In property management, in developer relationships, in investor repeat business, the sale is the beginning of the valuable part. A model that doesn't harvest retention, expansion, referrals, and proof is a model that quietly discards our best margin.
Motto, worth memorizing: Different attracts. Earned wins. Repeat.
Why it matters
Three jobs the Code does for us:
1. Shared language. When four OpCos and a dozen people say "campaign," "lead," and "brand" and mean twelve different things, coordination costs eat the strategy. The Code (plus the Glossary) is the fix.
2. Diagnosis. Growth problems are always constraint problems, and the constraint is always at a stage. "We need more leads" is almost never the real problem. Plenty of site traffic but thin pipeline? That's an Earn or Differentiate break. Deals stall at proposal? Win-stage — and usually, dig deeper, an offer or positioning problem. First response to any growth complaint: which stage is constrained? Show me the stage metrics.
3. The moat. Read the market honestly: AI pulls everyone to the middle. Every competitor now produces competent-average marketing at near-zero cost, which means competent-average is the new invisible. What can't be generated: a real position, proof earned over thousands of doors, relationships built over years, and a proprietary system for compounding them. The Code is that system. It's a strategic asset of the HoldCo, same class as the Brand Code.
How it works
Each stage has a job, a set of plays, and metrics (full detail in the framework document — read it after this lesson; it's the wall version of this system).
The part people miss: the stages lower each other's costs. Sharp positioning makes attention cheap (a distinct POV gets remembered; generic gets scrolled). Attention makes trust faster (they've seen us before the first call). Trust makes closing cheap (Sheridan's data and ours: educated prospects close faster and haggle less). Easy closes create advocates. Advocates make everything cheaper. Run the loop for three years and your CAC falls while competitors' rises. That's compounding, and it's why consistency beats brilliance in this system.
And the HoldCo twist — our structurally uncopyable move: the cross-OpCo flywheel. One relationship, four engines. CRG sells out a developer's project → CPM manages it → AFF markets the developer's next one → CG Capital helps fund it. A single-line competitor cannot run that play. But it only happens if Repeat is a system — triggers, owners, metrics — not a hallway hope.
CHARLESGATE example
Diagnose a composite, realistic scenario: CPM wants to grow condo-association business. Site traffic is decent (Attract: okay). Proposals go out; win rate is mediocre and price objections are constant (Win: weak). Diagnose upstream: proposals all say "full-service, responsive, local" — which every competitor also says (Differentiate: broken). The constraint isn't sales skill and it isn't leads. Fix order: positioning first (what can CPM claim that the big nationals and the small locals provably can't?), then rebuild the proposal narrative on it, then pour attention in. Spending on Attract before fixing Differentiate would have amplified an undifferentiated message — paying to be ignored faster.
Do the Work
Workbook Template 7 (Growth Code Stage Audit): score your OpCo 1–5 on each stage using the scorecard's evidence prompts. Identify your constraint stage and write a three-sentence diagnosis: what's weak, what evidence says so, what you'd fix first. This audit becomes your Module 9 capstone starting point.
1.3Positioning: The Battle for a Slot in the Mind
First principles
Positioning is not a tagline, a logo, or an aspiration on a slide. Two definitions, forty years apart, that agree:
- Al Ries & Jack Trout (Positioning: The Battle for Your Mind): positioning is what you do to the mind of the prospect — owning a slot, a word, an association. Minds are crowded and lazy; they file you under one thing or they don't file you at all.
- April Dunford (Obviously Awesome): positioning is context-setting — the deliberate act of defining how you're the best in the world at something a well-defined market cares about. Buyers can't evaluate you in a vacuum; they compare you to alternatives. If you don't set the frame of comparison, someone else will — usually the incumbent, the cheapest bidder, or "my cousin has a license."
First principle underneath both: **buyers don't buy the best option; they buy the best option as they understand the choice.** Positioning is the discipline of shaping that understanding honestly and to your advantage.
And the law most companies can't stomach, from Ries — the law of sacrifice: you cannot own a position while refusing to give anything up. "Full-service real estate firm for anyone in Greater Boston" is not a position; it's an absence of one. The willingness to be for someone — and visibly not for everyone — is the price of being chosen.
Why it matters
Weak positioning is the most expensive problem in marketing because it's invisible on any single invoice. It shows up as: ads that need more budget to get less response, content nobody remembers, sales cycles that end in price-grinding, and win rates that depend on who golfed with whom. Every downstream dollar works harder or lazier depending on this single upstream choice. Dunford's blunt observation, which matches our experience: most struggling products (and services) are fine — they're just positioned in a context where they look like everyone else.
For CHARLESGATE specifically: the AI era makes this existential. When all marketing output converges on competent-average, position is one of the few inputs that can't converge — because it's made of real choices and real proof, not words.
How it works
Dunford's method (we adopt it nearly whole; the full workbooks are in Michael's resource library, and the canvas is Template 1):
- List true competitive alternatives. What would the customer actually do if you didn't exist? Include status quo (self-manage, do nothing) and "hire the cheap option." Not who you consider a rival — what they consider a substitute.
- Isolate distinct capabilities. Features, expertise, relationships, structure, proof that you have and the alternatives genuinely don't. "Responsive service" fails this test unless you can prove it and they can't. Our HoldCo structure passes it. Thousands of managed units of operating data passes it.
- Translate capabilities into differentiated value. Nobody buys capabilities; they buy what capabilities do. So what? Then what? Keep asking until you hit something a buyer would pay for.
- Identify who cares most. Which specific customers feel that value hardest? That's your best-fit segment — the input to Lesson 1.4.
- Choose your market frame. What category do you enter their mind through? "Property manager" invites comparison to every property manager. A sharper frame changes the shortlist entirely.
- Layer a trend (optional, carefully). Only if genuinely relevant — riding a trend you can't deliver on is borrowed positioning, and borrowed positions get repossessed.
Order matters. Most companies start with the category and a tagline — steps 5 and 6 — then wonder why they sound like everyone in the category. Alternatives → capabilities → value → who cares is the sequence that produces an earned position.
CHARLESGATE example
CRG's New Development Group, run through the sequence (teaching draft):
- Alternatives a Boston developer weighs: big-brand residential brokerage with a new-dev arm; boutique broker who did their friend's project; in-house sales; "list it and hope."
- Distinct capabilities: the only local group where new-dev sales, in-house marketing (AFF), property management (CPM), and capital relationships (CG Capital) sit under one roof; pricing and absorption instincts fed by managing thousands of units of real rent-and-turnover data, not just comps; marketing begun pre-permit, not post-CO.
- Differentiated value: faster sell-out at stronger pricing, with fewer surprises — because the pricing model is fed by operating data competitors don't have, and because the marketing engine starts before the shovel does. And the relationship doesn't die at closing: management and capital continue it.
- Who cares most: developers of 20–150 unit projects in Greater Boston — big enough that carry costs make sell-out speed a P&L event, small enough that national-brand teams treat them as second-tier accounts.
- Frame: not "a brokerage that does new construction" — a sell-out system for mid-size Boston developments. Different frame, different shortlist, different conversation.
Notice what the position sacrifices: the 4-unit condo conversion and the 400-unit institutional tower are explicitly not the center of the bullseye. That sacrifice is what makes the claim believable to the 20–150 unit developer.
Do the Work
Workbook Template 1 (Positioning Canvas): complete it for your OpCo or service line. Hard rules: minimum three real alternatives including status quo; every distinct capability must survive the test "can a named competitor truthfully claim this too?"; every value statement must survive "so what?" twice. Then draft the one-sentence position: For [best-fit customer], [OpCo] is the only [frame] that [distinct capability], which means [value]. Bring it to review — expect it to be torn up once. That's the process working.
1.4ICP, Segmentation & Personas: Choosing Who to Win
First principles
You cannot be the obvious choice for everyone, because "obvious" is relative to a specific someone's alternatives, stakes, and situation. So the foundational act of marketing is choosing — and the honest name for not choosing is "hoping."
Three tools, three different jobs. Teams blur them constantly; don't:
- Segmentation = dividing the market into groups that buy differently. Useful segments differ in needs, buying process, or economics — not just size or geography.
- ICP (Ideal Customer Profile) = the segment(s) you prioritize: the accounts where you win most often, deliver the most value, earn the best economics, and create the strongest Repeat-stage assets (expansion, referral, proof). ICP describes the organization (or asset/owner profile — in our world, often the building plus its ownership).
- Personas = the people inside the account who drive the decision: the champion, the economic buyer, the skeptic, the blocker. Personas describe roles in a buying process — what they care about, what they fear, what "career-safe" looks like to them — not demographic trivia. Nobody needs to know the board president's favorite podcast. You need to know she's a volunteer with a full-time job who's terrified of special assessments and just wants the building off her back.
Why it matters
The ICP decision is quietly the highest-leverage economic decision in marketing, because fit compounds through every Growth Code stage. Right-fit accounts: cheaper to attract (concentrated watering holes), faster to trust (your proof matches their situation), likelier to close (your difference actually matters to them), better economics (less churn, more expansion), and better Repeat assets (their case study attracts their peers). Bad-fit revenue does the opposite at every stage — it's not just lower-margin, it's system-degrading, because bad-fit clients generate the service failures that become the reviews that repel good-fit buyers.
Hormozi's market test is a good screen for whole segments: look for pain (a bleeding-neck problem, not a nice-to-have), purchasing power, easy to target (they gather somewhere), and growing. A segment failing two of four is a hobby, not a market.
How it works
- Mine your own base first — evidence over aspiration. Pull your best 10–20 clients: best margins, best relationships, referrals given, multi-OpCo potential. What do they share — asset type, size band, ownership structure, sophistication, trigger event that brought them in? That pattern is your draft ICP. (Dunford makes this move central: best-fit customers reveal your real position.)
- Tier it. Tier 1: named accounts we'd move heaven and earth for (this list is the ABM program's raw material — Module 3.2). Tier 2: strong fit, systematic pursuit. Tier 3: acceptable inbound, no proactive spend. Explicit anti-ICP: who we decline — and everyone, including sales comp plans, knows it.
- Map the buying committee. B2B decisions are committee decisions (typical mid-market deals involve roughly half a dozen stakeholders — and a condo board is a buying committee with feelings). For each ICP, name the 3–5 roles, and for each: what they care about, what they fear, what evidence moves them, and what question they'll ask in the meeting you're not in.
- Write the trigger events. Most B2B buyers move on triggers, not persuasion: manager quit responding, project financing closed, building failed an inspection, board turned over, 1031 clock started. Triggers tell you when attention and outbound are welcome — which is most of the battle in Attract.
CHARLESGATE example
CPM condo-management ICP (teaching draft): Tier 1 — Boston-core associations, 20–80 units, professionally managed but dissatisfied (responsiveness, financials opacity, deferred-maintenance drift), healthy reserves or willingness to fund, engaged board. Anti-ICP — sub-8-unit self-managed buildings shopping on price alone; hostile litigation-riddled associations. Committee: board president (champion; wants their evenings back and no surprises), treasurer (skeptic; wants clean financials and reserve discipline), the longtime owner-resident (blocker; fears change and fee increases), property committee chair (evaluator; asks about maintenance response times). Triggers: manager non-response streak, botched special assessment, annual meeting revolt, failed elevator inspection. Every piece of CPM's Attract and Earn work should be aimable at a named row in that table — the market letter answers the treasurer, the "questions to ask your manager" guide arms the president, the case study calms the blocker.
Do the Work
Workbook Template 2 (ICP + Buying Committee): complete the ICP one-pager for your OpCo — evidence-based (pull the actual best-client list first), tiered, with anti-ICP and triggers — plus the buying-committee grid for your #1 ICP. Deliverable includes ten named Tier-1 accounts. If you can't name ten, that's a finding: your ICP is a theory, not a list. Fix that first.
1.5Messaging: From Position to Words that Sell
First principles
Positioning is the decision; messaging is the language that carries the decision to market. Two disciplines govern good messaging:
1. Consistency beats cleverness. A message repeated identically across every touchpoint builds a memory structure; ten clever variations build nothing. This is why the core artifact of this lesson is boring on purpose: a Messaging Document — one approved source of truth for what we say. April Dunford's messaging doc structure (the actual template is in Michael's resource library, and we've adapted it as Template 3) exists to kill four expensive problems: teams rewriting the same copy forever, message drift across materials, new hires improvising positioning, and executives bottlenecked approving copy one email at a time.
2. The customer is the hero — you're the guide. Donald Miller's StoryBrand insight, which is really a cognitive one: people process the world as stories with themselves in the lead role. Messaging that opens with our excellence casts us as the hero and loses the reader. Messaging that opens with their problem, names the stakes, and presents us as the guide with a plan — that gets read. Miller's SB7 spine: a character (the buyer) has a problem, meets a guide (us) with empathy and authority, who gives them a plan, calls them to action, and shows the stakes — failure avoided, success achieved.
Where Dunford and Miller pull differently, here's our position: **Dunford governs what we claim (position, value themes, proof); Miller governs how we tell it (customer-hero structure).** Positioning is the substance; story is the delivery vehicle. Never let narrative charm smuggle in claims the position can't back.
Why it matters
Messaging is where positioning either cashes in or dies. A sharp position rendered in generic language ("full-service excellence, white-glove service, trusted partner") is indistinguishable from no position — the buyer only ever experiences the words, not the strategy deck behind them. And in 2026 there's a new reason the document matters: your messaging doc is the context file for AI. Dunford herself now flags this — a maintained messaging document is what keeps AI-assisted content on-position instead of pulling you toward the generic middle. No doc, and every AI-drafted email is a small act of position erosion.
One more evidence point: buyers penalize synthetic-feeling language (45% less likely to consider a vendor whose outreach feels AI-generated, per 2026 buyer research). Specificity and proof are what make language feel human. Adjectives are what make it feel generated.
How it works
The messaging hierarchy — each layer derived from the one above, never freelanced:
- Position (from Lesson 1.3): the one-sentence "only" claim.
- One-liner: what we are + biggest benefit + hint of who it's for. The sentence anyone at CHARLESGATE can say verbatim.
- Elevator paragraph: one-liner + top value points + a piece of proof.
- 100-word / 500-word boilerplates: for proposals, listings, PR, directories — written once, approved once, reused everywhere.
- Value themes (2–3, each with supporting capabilities + proof): the load-bearing claims. A value theme without proof is an adjective. Format per theme: the value → the features/capabilities that enable it → the evidence (named client result, statistic, review).
- Competitive responses: approved, classy answers to "how are you different from [big national]?" and "why are you more expensive than [cheap local]?" — written calm, in daylight, not improvised on calls. (Rule from Dunford we adopt: respond to the claim, don't name-drop the competitor.)
- Proof inventory: approved case studies, quotes, stats, brag points — the ammunition depot every layer draws from.
Writing rules of the house: plain words over industry words; specific over superlative ("average response under 4 business hours" beats "unmatched responsiveness"); every claim traceable to proof; write like Michael talks — direct, editorial, evidence-led; and read it aloud — if you wouldn't say it to a client at coffee, it doesn't ship.
CHARLESGATE example
CRG New Development Group, hierarchy in action (teaching draft — validate the proof before use):
- One-liner: "CHARLESGATE runs a complete sell-out system for mid-size Boston developments — marketing, pricing, and sales under one roof, informed by the rent and turnover data from thousands of units we manage."
- Value theme 1 — Sell out faster at stronger pricing. Enabled by: pre-permit marketing start; pricing models fed by CPM operating data; in-house AFF creative. Proof: [named project]: X% absorption in Y months vs. neighborhood comp average of Z. ← pull the real numbers; the theme is only as strong as this line.
- StoryBrand rendering for a landing page: "You've got millions in carry costs burning while units sit. (Problem.) We've sold out [N] Boston developments and manage [X,000] units — we know what actually rents, sells, and sticks in this market. (Guide + authority.) Here's the plan: pricing study → pre-sale marketing engine → dedicated sales team. (Plan.) Book a sell-out strategy session. (CTA.) Stop guessing at absorption. (Stakes.)"
Same substance top to bottom; different altitude per layer. That's the hierarchy working.
Do the Work
Workbook Template 3 (Messaging Hierarchy + Doc): using your completed Positioning Canvas (1.3) and ICP (1.4), draft the one-liner, elevator paragraph, and two value themes with proof for your OpCo. Then the acid tests: (a) swap test — put a competitor's name in your one-liner; if it still reads true, rewrite it; (b) proof test — highlight every claim lacking evidence in the doc; that highlighted list is your proof-collection backlog, and it goes into the Repeat-stage plays (case studies, reviews) to fix.
1.6Offers: What You Sell is the Marketing
First principles
An offer is the complete, concrete package a buyer says yes or no to: what's included, what outcome is promised, what it costs, what risk they carry, and why now. Most service firms don't design offers — they quote engagements: bespoke scopes, hourly-ish pricing, "every deal is different." That feels sophisticated and client-centered. It's actually a tax on every stage of the Growth Code: unnameable in Attract (you can't advertise a shrug), unteachable in Earn (nothing concrete to explain), and commoditizable in Win (procurement reduces bespoke scope to a rate-card comparison — they set the frame, and the frame is price).
Alex Hormozi's value equation ($100M Offers) is the cleanest tool for thinking about this. Perceived value rises with the dream outcome and the buyer's perceived likelihood it actually happens, and falls with time delay and effort & sacrifice required:
Value = (Dream outcome × Likelihood of achievement) ÷ (Time delay × Effort & sacrifice)
Amateurs sell the numerator only ("great results!"). Professionals engineer all four: raise certainty with proof and guarantees, cut time-to-value with fast starts, cut effort with turnkey onboarding. And Hormozi's framing goal — the "Grand Slam" offer — is the right ambition stated plainly: an offer so specific and risk-shifted that comparing it to competitors on price becomes impossible, because nobody else is selling the same thing.
Why it matters
The offer is the hinge between marketing and revenue — the strongest positioning still dies at a mushy "send us an RFP and we'll scope something." And offers are a differentiation surface: two firms with identical capabilities can present wildly different value simply by how they package, name, guarantee, and de-risk the same work. In B2B especially, remember what the buyer is actually buying: not just the outcome — the safety of the decision. Your champion has to defend this choice to a board or a capital partner. Risk reversal isn't a discount tactic; it's champion armor.
One editorial position, because Hormozi is a B2C-inflected thinker and we're not: scarcity and countdown-timer urgency mostly read as manipulation to sophisticated B2B buyers — skip the theater. But real urgency (leasing season, carry costs, the board's annual meeting) and real scarcity (we onboard a limited number of associations per quarter because quality is the moat) are honest and powerful. Use only the kind you can defend with a straight face.
How it works
Design sequence (Template 4 walks it):
- Start from the ICP's dream outcome — in their words, not our service list. A board president's dream outcome is not "property management services"; it's "I never think about the building between meetings."
- Name the offer. Named things are discussable, referrable, and rememberable. "The Sell-Out System." "The First-90-Days Turnaround." A name moves the offer from commodity to product.
- Stack the value — what's included, stated as outcomes with the enabling deliverables, including the pieces you already do but never mention (the pricing study, the reserve review, the vendor audit). Unstated value is donated value.
- Engineer each equation variable: proof for likelihood (case studies, numbers, references); a fast time-to-value milestone in the first 30 days (the "quick win" that retires buyer's remorse); effort reduction (we run the transition, we chase the old manager for records — say so explicitly, switching pain is the #1 silent objection).
- Reverse the risk you control. Guarantees, performance triggers, easy-out clauses. Rule: guarantee what your operations actually control; never guarantee the market.
- Ladder it. A small, low-risk entry offer (paid or free: building assessment, sell-out pricing study, marketing audit) → core offer → expansion offers (the cross-OpCo flywheel formalized). The entry offer is Earn-stage machinery: it gives trust a concrete next step short of a marriage proposal.
The sprint/step-down structure (field-tested, 2026). When the client's situation is intensive-then-steady — a distressed asset, a turnaround, a launch — don't price one flat engagement across both phases. Package Year 1 as a named, fixed-scope, fixed-period sprint priced to the intensity and tied to the outcome, then step scope and fee down to steady-state. The origin case: a 776-unit asset at ~72% occupancy, reframed from "management proposal" to a "Re-Stabilization Sprint" — drag occupancy to ~93–95%, clear the backlog, priced to that outcome, stepping down in Year 2. "A distressed asset doesn't need management, it needs re-stabilization — and pricing it the same both years undersells the work in Year 1 and possibly overcharges in Year 2." Two reasons the structure wins: it makes the performance story undeniable (fee tied to the result, not set-and-forget), and it's productized — a repeatable tier for the next similar deal. The strategic corollary: dominate the opportunities where our model is different instead of forcing our way into the standard model.
And the hard rule on unpriced value: unstated value is donated value (rule 3 above) — but unpriced strategic value is worse than donated: it gets repositioned against you. A proposal that lists the strategic layer as free "coordination" or "no markup" trains the client to read your highest-value function as a pass-through cost. Name it, scope it, price it as its own transparent line — and kill "no markup" language wherever it appears. (Worked example: the Valenza Strategic Marketing & Fee Note in the resource library.)
CHARLESGATE example
CPM condo offer, redesigned (teaching draft): instead of "CPM provides comprehensive association management — request a proposal," an offer built on the equation: "The First-90-Days Turnaround" — for 20–80 unit Boston associations leaving a manager who's stopped performing. Included: full records recovery and transition managed by us (effort ↓ — "you fire them; we handle everything else"); a 30-day building and financials assessment delivered to the board (time-to-value ↓); response-time standard with monthly reporting (likelihood ↑, and it operationalizes the positioning claim); first-annual-meeting prep package (dream outcome — the board looks good to the owners they answer to); and an easy-out: if after 90 days the board isn't satisfied, they can exit without penalty (risk reversal on what we control). Suddenly Attract has something to advertise, Earn has something to explain honestly (TAYA article: "What switching property managers actually costs — and who should pay it"), and Win has something no rate card can flatten.
Do the Work
Workbook Template 4 (Offer Design Canvas): design one core offer and one entry offer for your OpCo. Score your current de facto offer on the four equation variables (1–5 each) first, then the redesign — the deltas tell you where the engineering went. Gate before anything ships: operations must sign off that every promise is deliverable. An offer ops can't cash is a Repeat-stage crisis on a payment plan.
1.7B2B vs. B2C: What Transfers, What Doesn't
First principles
B2B and B2C marketing are the same discipline pointed at structurally different buying situations. Neither is "more advanced." The failure mode is copying tactics across the boundary without understanding which structural differences drive them. Know the structure; then steal freely and deliberately.
The structural differences that actually matter:
| Dimension | B2C | B2B (our world) |
|---|---|---|
| Who decides | One person (maybe a household) | A committee — board, partners, capital sources; ~5–7 stakeholders with different fears |
| Cycle | Minutes to weeks | Months to years; trigger-driven |
| Deal size / frequency | Small, frequent | Large, rare, career-attached |
| Risk to the buyer | Refundable regret | Professional reputation ("nobody gets fired for hiring the safe choice") |
| Emotion vs. logic | Emotion decides, logic is optional | Emotion still decides — fear, ambition, pride — but logic must justify it to the committee |
| Reach math | Mass audiences, broad targeting | Small, finite universes — in our market, the real ICP universe is often a few hundred accounts you could literally list |
| Brand's job | Instant preference at shelf/feed | Being on the shortlist months before the deal; pre-answering "are they legit?" |
| Channels | Wherever attention is cheap | Wherever trust forms: relationships, rooms, referrals, content, LinkedIn |
The one B2C-import most B2B people get wrong in both directions: emotion. Amateurs assume B2B is rational and write spec-sheet marketing that moves no one. Cynics assume it's all relationships and skip the proof. The truth (backed by the B2B Institute's research and every deal we've done): B2B decisions are made emotionally by people managing personal risk, then defended rationally to a committee. So the work must do both jobs — move the human, arm the justification.
Why it matters
CHARLESGATE sits on both sides of this line, which is a genuine advantage if we're deliberate: CRG's resale/leasing business and new-dev unit sales are substantially B2C (individual buyers, emotional purchases, shorter cycles, consumer channels), while the clients — owners, developers, boards, investors, institutions — are B2B. AFF markets B2C-style on behalf of B2B clients. A team fluent in both grammars, and precise about which one any given piece of work speaks, out-executes specialists who only know one. A team that blurs them runs Instagram plays at institutional investors and RFP-speak at condo buyers, and wonders why neither lands.
How it works — the transfer guide
Transfers from B2C to B2B (steal deliberately):
- Creative and distinctiveness. Committees are made of humans who scroll like everyone else. The 2026 evidence is blunt: creative has become the most powerful form of targeting, and B2B's genericness makes distinctive creative cheaper to win with in our categories than in consumer ones.
- Brand as memory. The 95:5 logic is a B2C insight (mental availability, Ehrenberg-Bass) that applies harder in B2B because the buying moments are rarer — you can't retarget your way into a shortlist you weren't remembered for.
- Attention instincts (Gary Vee's lesson, adapted). Native content, volume, showing up where attention actually is. Adapted, not adopted: in B2B the metric behind the volume is who saw it, not how many.
- Offer craft and friction removal (Lesson 1.6) — Hormozi's equation was built B2C-first; the variables are universal.
Does NOT transfer (leave at the border):
- Impulse mechanics. Countdown timers, flash pricing, manufactured FOMO — reads as clownish to a board and gets screenshotted.
- Volume-lead-gen math. B2C can burn 99% waste reach; with a 300-account ICP universe, "spray" isn't waste, it's reputation damage inside the whole addressable market.
- Single-decider messaging. B2C persuades a person; B2B must arm a champion to persuade others when you're not in the room. If your materials only work with you presenting them, they don't work.
- Instant-conversion expectations. Applying e-commerce attribution windows to an 18-month developer relationship makes the best B2B marketing look like failure and kills it in budget review — this is half of why weak teams over-fund demand capture and starve Earn.
Runs in both, tuned differently: content (B2C entertains toward desire; B2B teaches toward trust), social proof (reviews vs. named case studies and references), email (promos vs. genuinely useful market intelligence), events (activations vs. rooms where relationships form), paid media (conversion engine vs. air cover + capture).
CHARLESGATE example
One new-dev project, both grammars at once: selling units (B2C): lifestyle creative, the neighborhood story, model-unit content, Instagram/broker buzz, urgency from real absorption ("60% sold in 90 days"), emotional close — this is your home. Winning the next developer client (B2B): the same project repackaged as evidence — a case study with absorption curve vs. comps, pricing-model methodology, a developer-roundtable walkthrough of what worked, an ABM sequence to the 50 named Tier-1 developers, arming their capital partners with the numbers. Same building. Two markets, two grammars, one team that knows exactly which it's speaking — and the B2C excellence is itself the B2B proof. That last move — making consumer-side craft the business-side evidence — is the AFF/CRG flywheel in miniature, and almost nobody in our market runs it deliberately.
Do the Work
Workbook Template 5 gets its first use here (Campaign Brief): take one upcoming initiative in your OpCo and write the brief twice — once as if the audience were B2C, once B2B. Note what changed: audience size, message, proof, channel, time horizon, success metric. Then mark which version is actually true for this initiative — and check that its metric matches its grammar (an Earn-stage B2B play judged on 30-day conversions is set up to be murdered in budget review). Bring both briefs; the module discussion compares them.
Module 1 Exit Checklist
You're done with Module 1 when your OpCo has, on paper and reviewed:
- Growth Code stage audit with a named constraint stage (1.2 / Template 7)
- Positioning Canvas + one-sentence position that survives the swap test (1.3 / Template 1)
- ICP one-pager: tiers, anti-ICP, triggers, buying-committee grid, ten named Tier-1 accounts (1.4 / Template 2)
- Messaging hierarchy: one-liner, elevator, two value themes with proof, plus a proof backlog (1.5 / Template 3)
- One core offer + one entry offer, ops-approved (1.6 / Template 4)
- One campaign brief written in the correct B2B/B2C grammar (1.7 / Template 5)
These artifacts are not homework — they're the operating documents Modules 2–9 build on, and the raw material for your Module 9 capstone plan.
Sources drawn on in this module (see framework doc for the full lineage): April Dunford — Obviously Awesome, Sales Pitch, and the messaging document template (all in the CHARLESGATE resource library); Al Ries & Jack Trout — Positioning, The 22 Immutable Laws of Marketing; Donald Miller — Building a StoryBrand; Alex Hormozi — $100M Offers; Marcus Sheridan — They Ask, You Answer; Maja Voje — GTM Strategist (in the library); Ehrenberg-Bass Institute / LinkedIn B2B Institute — 95:5 and mental availability research; Demand Gen Report 2026 B2B trends (synthetic-outreach penalty, creative-as-targeting).
Rules of the workbook:
- Every template pairs a blank canvas with a worked CHARLESGATE example. The examples are teaching drafts — directionally right, but every number/claim must be validated against current company data before external use.
- Write in plain language. If a cell reads like a brochure, redo it.
- These are living operating documents, not homework. Date them, version them, review them on the annual/quarterly cadence in the framework doc.
Contents: T1 Positioning Canvas · T2 ICP + Buying Committee · T3 Messaging Hierarchy & Doc · T4 Offer Design Canvas · T5 Campaign Brief · T6 Channel Plan · T7 Growth Code Stage Audit
T1Positioning Canvas
(Adapted from April Dunford's Obviously Awesome method — full workbooks in the CHARLESGATE resource library. Complete top to bottom, in order. Lesson 1.3.)
Blank canvas
| Field | Prompt | Your answer |
|---|---|---|
| Scope | Which OpCo / service line is this canvas for? | |
| 1. Competitive alternatives | If we didn't exist, what would the customer actually do? Include status quo / do-nothing. Min. 3. | |
| 2. Distinct capabilities | What do we have that the alternatives provably don't? Test each: "Can a named competitor truthfully claim this too?" If yes, cut it. | |
| 3. Differentiated value | What does each capability do for the customer? Ask "so what?" twice per line. | |
| 4. Who cares most (best-fit) | Which specific customers feel that value hardest? How do we recognize them? | |
| 5. Market frame | What context/category do we want to be evaluated in? (Not necessarily the default one.) | |
| 6. Relevant trend (optional) | Only if we can genuinely deliver against it. | |
| One-sentence position | For [best-fit customer], [we] are the only [frame] that [distinct capability], which means [value]. | |
| What we sacrifice | Who/what this position is explicitly NOT for. If empty, the position is fake. |
Worked example — CRG New Development Group (teaching draft)
| Field | Answer |
|---|---|
| Scope | CRG — New Development Sales & Marketing |
| 1. Alternatives | (a) National-brand brokerage new-dev division; (b) boutique broker w/ personal relationship; (c) in-house sales team; (d) standard listing approach ("list at CO and hope") |
| 2. Distinct capabilities | Only local firm with sales + marketing agency (AFF) + management (CPM) + capital (CG Capital) under one roof; pricing/absorption models fed by operating data from thousands of managed units; marketing engine that starts pre-permit, not post-CO; post-sale continuity (management of what we sell) |
| 3. Differentiated value | Faster sell-out at stronger pricing → carry costs cut, capital recycled sooner; fewer pricing misses → so what? → fewer painful re-positionings mid-sellout → so what? → lender/investor confidence on the next deal; one accountable partner start-to-finish → less coordination overhead and finger-pointing |
| 4. Who cares most | Boston-area developers, 20–150 unit projects; carry-cost-sensitive; too small to be a national brand's priority account, too big to gamble on a friend-of-a-friend broker; repeat builders who value the next deal, not just this one |
| 5. Market frame | Not "brokerage that does new construction" → a sell-out system for mid-size Boston developments |
| 6. Trend | AI-commoditized listing marketing makes data-fed pricing + genuinely creative campaigns the visible differentiator |
| One-sentence position | For Boston developers of 20–150 unit projects, CHARLESGATE is the only sell-out system that combines sales, in-house marketing, management operating data, and capital relationships under one roof — which means faster sell-outs at stronger pricing, with a partner who's still there after closing. |
| Sacrifice | Not centered on: 2–6 unit condo conversions; 300+ unit institutional towers; out-of-market developers who bid everything on fee alone. |
T2ICP + Buying Committee
(Lesson 1.4. Evidence first: build from your actual best-client list, then aspire.)
Blank canvas
Part A — ICP one-pager
| Field | Your answer |
|---|---|
| OpCo / service line | |
| Evidence base (best 10–20 clients reviewed — list them) | |
| Tier 1 (named accounts, move-heaven-and-earth) — profile + the 10+ named accounts | |
| Tier 2 (strong fit, systematic pursuit) — profile | |
| Tier 3 (acceptable inbound only) — profile | |
| Anti-ICP (we decline / don't pursue) — and why | |
| Trigger events (what makes them in-market NOW) | |
| Watering holes (where they gather: rooms, feeds, associations, events, publications) | |
| Market test (Hormozi): pain? purchasing power? targetable? growing? | Score /4 + one line each |
Part B — Buying-committee grid (for your #1 ICP)
| Role | Who (title/position) | What they want | What they fear | Evidence that moves them | The question they ask when we're not in the room |
|---|---|---|---|---|---|
| Champion | |||||
| Economic buyer | |||||
| Skeptic / evaluator | |||||
| Blocker | |||||
| End users / influenced |
Worked example — CPM Condo Association Management (teaching draft)
Part A
| Field | Answer |
|---|---|
| OpCo | CPM — Condominium association management |
| Evidence base | [Pull actual list: top 15 associations by margin, tenure, referrals given, board relationship quality] |
| Tier 1 | Boston-core associations, 20–80 units, professionally managed but dissatisfied (slow response, opaque financials, deferred-maintenance drift); healthy reserves or willing boards; engaged president/treasurer. Named accounts: [list 10+ specific buildings/associations from market data]. |
| Tier 2 | 12–20 unit associations upgrading from self-management; 80–150 unit associations in inner suburbs |
| Tier 3 | Small self-managed buildings arriving via referral; take selectively |
| Anti-ICP | Sub-8-unit price-only shoppers (economics don't work); associations in active litigation-meltdown (service failures we inherit, reviews we don't deserve) |
| Triggers | Manager non-response streak; botched special assessment; failed inspection (elevator, façade); annual-meeting revolt; board turnover; management company sold/roll-up churn |
| Watering holes | CAI-New England events; board-member peer networks; building attorneys + reserve-study firms (referrers); Google/AI search "replace property management company Boston"; neighborhood association groups |
| Market test | 4/4 — Pain: acute at trigger moments; Power: association budgets + assessments; Targetable: yes, literally addressable buildings; Growing: condo stock + roll-up churn creating dissatisfaction |
Part B
| Role | Who | Wants | Fears | Evidence that moves them | Question asked without us |
|---|---|---|---|---|---|
| Champion | Board president | Their evenings back; no surprises; owners off their back | Being blamed for a bad switch | Case study of a same-size association's switch; the 90-day easy-out | "Is this going to blow up on me?" |
| Economic buyer | The board (vote) | Defensible decision | Fee increase backlash from owners | Side-by-side of total cost incl. what bad management costs (deferred maintenance, botched projects) | "What does this do to our fees?" |
| Skeptic | Treasurer | Clean books, reserve discipline | Opaque financials continuing under a new logo | Sample monthly report package; references from treasurers | "Can I actually read their reports?" |
| Blocker | Longtime owner-resident | Nothing to change | Any change | Transition plan showing zero owner effort; testimonial from a similar building's holdout | "Why are we doing this at all?" |
| Influenced | Owners at large | Responsiveness | Assessment surprises | Response-time standard in writing | "Will anyone answer the phone?" |
T3Messaging Hierarchy & Messaging Doc
(Structure adapted from the April Dunford Messaging Document template in the CHARLESGATE resource library. Lesson 1.5. This becomes the AI context file too — keep it current.)
Blank canvas
| Layer | Content | Status (draft/approved + date) |
|---|---|---|
| Position (from T1) | One sentence | |
| One-liner | What we are + biggest benefit + who it's for | |
| Elevator paragraph | One-liner + top value + one proof | |
| 100-word boilerplate | For proposals, PR, directories | |
| Value theme 1 | Value → enabling capabilities → proof | |
| Value theme 2 | Value → enabling capabilities → proof | |
| Value theme 3 (optional) | Value → enabling capabilities → proof | |
| Competitive response 1 | Their claim → our approved response (no naming) | |
| Competitive response 2 | Their claim → our approved response | |
| Proof inventory | Approved case studies / quotes / stats / brag points + links | |
| Proof backlog | Claims currently lacking evidence → collection plan + owner |
Acid tests before "approved": ① Swap test — insert a competitor's name; if it still reads true, rewrite. ② Proof test — every claim traceable to the inventory. ③ Aloud test — would you say it to a client at coffee?
Worked example — CRG New Development Group (teaching draft — replace bracketed proof with validated numbers)
| Layer | Content |
|---|---|
| Position | (from T1 worked example) |
| One-liner | "CHARLESGATE runs a complete sell-out system for mid-size Boston developments — marketing, pricing, and sales under one roof, informed by rent and turnover data from thousands of units we manage." |
| Elevator | "Developers of 20–150 unit projects in Boston carry millions in costs while units sit. We combine pre-permit marketing, data-fed pricing, and a dedicated sales team — one accountable partner instead of three vendors. [Project X] hit [Y%] absorption in [Z] months against a neighborhood average of [A]. And because we manage what we sell, we're still there after closing." |
| Value theme 1 — Sell out faster at stronger pricing | Capabilities: pricing models fed by CPM operating data; pre-permit marketing start; AFF in-house creative. Proof: [Project X absorption stat]; [pricing premium vs. comp]. |
| Value theme 2 — One accountable partner, start to finish | Capabilities: sales + marketing + management + capital under one roof; single reporting line to the developer. Proof: [named developer quote]; [repeat-client count]. |
| Competitive response — "The national brand has more reach" | "Reach matters when you're selling to the whole world. Mid-size Boston projects sell out through precise local buyer targeting and broker relationships — and through pricing that's right the first time. That's what our operating data feeds. [Stat.]" |
| Proof backlog | Absorption stats per project (owner: [name], via closing records, Q3); treasurer-grade developer references (owner: [name]); review count on [platform] (Repeat-stage play). |
T4Offer Design Canvas
(Hormozi value equation, adapted for B2B services. Lesson 1.6. Ops sign-off required before anything ships.)
Blank canvas
Step 1 — Score the current de facto offer (1–5 each): Dream outcome clarity ⬜ · Perceived likelihood (proof) ⬜ · Time to first value ⬜ · Buyer effort/sacrifice ⬜
| Field | Prompt | Your answer |
|---|---|---|
| ICP + dream outcome | In their words | |
| Offer name | Named = discussable, referrable | |
| Value stack | What's included, as outcomes + deliverables (incl. the things we do but never say) | |
| Likelihood levers | Proof attached: case studies, stats, references, standards in writing | |
| Speed levers | What lands in the first 30 days | |
| Effort levers | What we take off their plate (esp. switching pain) | |
| Risk reversal | Guarantee/easy-out on what our ops control (never the market) | |
| Honest urgency | Real seasonal/carry/board-calendar reasons for "now" (no theater) | |
| Price & frame | Anchored against cost of the status quo, not competitor rate cards | |
| Entry offer | Small, low-risk first step (assessment, study, audit) | |
| Expansion path | Cross-OpCo next offers + trigger + owner | |
| Ops sign-off | Every promise deliverable? Name + date |
Step 2 — Re-score the redesigned offer. The deltas show your engineering.
Worked example — CPM "First-90-Days Turnaround" (teaching draft)
| Field | Answer |
|---|---|
| ICP + dream outcome | 20–80 unit Boston associations leaving a non-performing manager. Dream outcome (president's words): "I never think about the building between meetings, and nobody yells at me at the annual meeting." |
| Offer name | The First-90-Days Turnaround |
| Value stack | Full transition managed by us (records recovery, vendor handoff, owner comms); 30-day building + financials assessment delivered to the board; written response-time standard w/ monthly reporting; first-annual-meeting prep package; reserve-study coordination |
| Likelihood levers | Case study: [same-size association switch]; treasurer references; sample report package shown pre-signature |
| Speed levers | Assessment + owner-portal live in 30 days — the board has something visible to show owners fast |
| Effort levers | "You vote; we do everything else" — incl. chasing the old manager for records (the #1 silent objection, answered out loud) |
| Risk reversal | 90-day satisfaction easy-out, no termination penalty |
| Honest urgency | Budget-season and annual-meeting calendar: switch decisions made now take effect cleanly at fiscal year start |
| Price & frame | Anchored against cost of bad management: deferred maintenance, botched assessments, unit-value drag — not against the cheap local's rate card |
| Entry offer | Free Building & Financials Assessment (bounded scope) — Earn-stage machinery |
| Expansion path | Unit owners buying/selling → CRG (trigger: owner intake); capital projects → vendor/CG network (trigger: reserve study findings). Owner: [name]. |
| Ops sign-off | Required before launch — response-time standard must match current staffing reality. |
T5Campaign Brief (One Page, Mandatory Before Spend)
(Lessons 1.7 & 4.2. If the brief can't be completed, the campaign isn't ready.)
Blank canvas
| Field | Your answer |
|---|---|
| Campaign name + owner + dates | |
| ICP + personas targeted (from T2 — named tiers/accounts) | |
| Growth Code stage(s) this moves — and the constraint evidence | |
| Grammar: B2B or B2C? (and therefore the time horizon + trust math) | |
| Objective (one sentence, one number) | |
| Core message (pulled from T3 — layer + value theme used) | |
| Offer / CTA (from T4 — what are we actually asking them to do?) | |
| Channels + plays (where, what format, what cadence) | |
| Budget + effort ($ + people-hours, honestly) | |
| Success metric + review date (stage-appropriate — no e-commerce windows on 18-month relationships) | |
| Kill criteria (what result by when = stop) | |
| Three-question filter check | ICP? ✔/✘ Stage? ✔/✘ Metric? ✔/✘ |
Worked example — "The Sell-Out Files" developer ABM campaign (teaching draft)
| Field | Answer |
|---|---|
| Name / owner / dates | The Sell-Out Files · [AFF lead + CRG new-dev lead] · Q1–Q2 (two quarters — B2B horizon) |
| ICP | Tier-1 named list: 50 Boston-area developers, 20–150 unit pipeline (from T2). Personas: principal (champion), CFO/capital partner (skeptic). |
| Stage(s) | Attract + Earn. Evidence: win rate on known relationships is strong; problem is the 40 Tier-1 developers who've never heard of us — an awareness/trust constraint, not a closing one. |
| Grammar | B2B: committee, long cycle, proof-led. Metric horizon set accordingly. |
| Objective | 15 of 50 named accounts engaged (meaningful content interaction or event attendance); 5 sell-out strategy sessions booked by end of Q2. |
| Core message | Value theme 1 (T3): faster sell-outs at stronger pricing, powered by operating data. Delivered as evidence, not adjectives. |
| Offer / CTA | Entry offer: complimentary Sell-Out Pricing Study for one active or planned project (T4 entry rung). |
| Channels + plays | (1) Case-study asset: full teardown of [Project X] w/ absorption curve vs. comps; (2) LinkedIn: Michael + CRG lead posting the teardown as a series (founder-led motion); (3) direct: researched, human 1:1 outreach to the 50 principals — no synthetic sequences; (4) developer roundtable dinner ×2 (8–10 seats each); (5) retargeting air cover on the named-account domains only. |
| Budget | $[X] hard + [Y] hrs/wk across AFF/CRG — honest capacity check attached |
| Success metric + review | Engaged-account count monthly; sessions booked; self-reported "how'd you hear about us" logged on every session. Review: end of month 2, then monthly. |
| Kill criteria | <5 engaged accounts by end of month 3 → stop spend, rework the asset or the list. |
| Filter | ICP ✔ Stage ✔ Metric ✔ |
T6Channel Plan (Per OpCo, Per Quarter)
(Lesson 1.1's filter applied to where we show up. Rule: dominate 2–3 channels before dabbling in a 4th.)
Blank canvas
| Channel | Owned/Earned/Paid/Rented | ICP density (H/M/L) | Growth Code stage it serves | Our current strength (1–5) | Commitment this quarter (cadence + owner) | Metric |
|---|---|---|---|---|---|---|
Bottom rows: Channels we are explicitly NOT doing this quarter (and why) · Experiment slot (max 1, with kill date)
Worked example — CPM, one quarter (teaching draft)
| Channel | Type | ICP density | Stage | Strength | Commitment | Metric |
|---|---|---|---|---|---|---|
| Market letter (email) | Owned | H (board members opt in) | Earn | 3 | Monthly, genuinely useful, [owner] | List growth; reply rate; assessments booked |
| TAYA content + AEO | Owned/Earned | H (trigger-moment search & AI answers) | Earn + Attract | 3 | 2 Big-5 answers/mo (cost, problems, comparisons), structured to be citable | Trigger-page conversions; self-reported attribution mentions |
| Referrer network (attorneys, reserve-study firms) | Earned | H | Attract + Repeat | 2 | 1 lunch/wk, [owner]; quarterly co-hosted board briefing | Referral-sourced pipeline |
| CAI-NE events | Paid/Earned | M-H | Attract | 2 | 1 speaking slot or workshop/qtr — teach, don't table | Board conversations; list adds |
| LinkedIn (CPM lead, personal) | Rented | M | Attract | 1 | 2 posts/wk from real building stories (anonymized) | ICP follower growth; inbound DMs |
| Not doing | Instagram (L density for board ICP — B2C grammar, wrong buyer); cold email blasts (synthetic penalty; small addressable universe = reputation risk) | |||||
| Experiment | AI-assistant citability audit: do ChatGPT/Gemini cite us for "switch property managers Boston"? Kill date: end of quarter. |
T7Growth Code Stage Audit (the Diagnosis Scorecard)
(Lesson 1.2. Run quarterly. The constraint stage gets the next quarter's focus — this feeds the Campaign Brief.)
Blank canvas — score each 1–5 with evidence
| Stage | Evidence prompts | Score | Evidence (be specific) |
|---|---|---|---|
| Differentiate | Could every team member state our one-liner identically? Does our position survive the swap test? Do we win against named alternatives without discounting? | ||
| Attract | Does our Tier-1 ICP know we exist before they're in-market? Branded search / "already knew you" trend? Are we visible in their watering holes? | ||
| Earn | Do we own an audience (list, community)? Have we answered the Big 5 honestly? Does inbound arrive pre-sold? Proof packaged? | ||
| Win | Named, clear offers? One sales narrative told consistently? Win rate, cycle length, discount frequency trend? Speed-to-lead? | ||
| Repeat | Retention trend? Cross-OpCo attach rate? Referral play running (not hoped)? Case studies/reviews produced last quarter? Client intel feeding positioning? |
Diagnosis (3 sentences): What's the constraint stage, what evidence says so, what we'd fix first. Beware: the symptom usually shows one stage downstream of the cause (weak Win numbers are usually a Differentiate problem; thin pipeline is usually Earn).
Worked example — the CPM scenario from Lesson 1.2 (teaching draft)
| Stage | Score | Evidence |
|---|---|---|
| Differentiate | 2 | Proposals say "full-service, responsive, local" — fails swap test; constant price objections = buyers see no difference |
| Attract | 3 | Decent traffic + event presence; branded search flat |
| Earn | 3 | TAYA content exists; list small; proof unpackaged (no current case studies) |
| Win | 2 (symptom) | Mediocre proposal win rate — but proposals carry an undifferentiated message |
| Repeat | 3 | Retention fine; referrals happen but unmanaged; zero case studies produced last quarter |
| Diagnosis | Constraint is Differentiate — Win's weakness is downstream of an undifferentiated proposal narrative. Fix order: T1 canvas → T3 messaging + proof backlog → rebuild proposal narrative → then scale Attract. Spending on leads now would amplify a generic message. |
How Buyers Buy & How We Attract Them
How buyers actually buy, and how we attract them — the buyer-side physics of marketing.
Definitions updated in v1.1. This module’s lesson text predates the update — where stage boundaries are discussed, the v1.1 Canon is the authoritative ruling (Attract = attract attention · Earn = earn pipeline · Win = qualified opportunity to signed and onboarded).
Module brief
CHARLESGATE Growth Code Academy · Module 2 of 9 · Status: COMPLETE
Growth Code linkage: This module operationalizes ATTRACT (get discovered by right-fit buyers before they're in-market) and EARN (build trust before the ask). Module 1 decided who and why us. Module 2 is the buyer-side physics: how buyers actually buy, and how we get known and trusted by them — especially the ~95% who aren't buying yet.
By the end of this module you can: map your ICP's real buying journey including the parts software can't see · classify every marketing dollar and hour as demand creation, demand capture, or lead gen — and defend the ratio · commit to 2–3 channels with a straight face · run TAYA as a system upgraded for the AI-answer era · audit whether AI assistants cite us · spend paid money only where it amplifies · and run an organic attention engine with an editorial bar.
How to use this module: One lesson per week for seven weeks, or a two-day intensive. Every lesson ends with Do the Work. Lessons 2.4 and 2.5 share one template — do them back-to-back. You will need your Module 1 artifacts (Positioning Canvas, ICP, Messaging Doc, Offers, Channel Plan); this module assumes they exist and builds on them. If they don't exist, stop and go back — attracting attention to an undifferentiated position is paying to be ignored faster.
A note on examples: CHARLESGATE examples are illustrative teaching drafts — directionally right, but every number and claim must be validated against current company data before external use.
2.1The Funnel is a Journey (and Most of it is Dark)
First principles
The funnel — awareness → consideration → decision — is a measurement model, not a description of behavior. It's useful for counting. It is misleading as a picture of how anyone actually buys, because real buyers don't descend an orderly staircase. They loop, stall, skip stages, go quiet for eight months, and reappear with a decision half-made.
Two facts about real buying behavior anchor everything in this module:
1. The 95:5 rule. At any given moment, roughly 95% of your category's buyers are not in-market; only ~5% are actively buying (Ehrenberg-Bass / LinkedIn B2B Institute). The condo board that will fire their manager next spring isn't researching managers today. The developer whose next project closes financing in Q3 isn't shopping for a sales team now. But both are forming memories now — and when their trigger fires, the shortlist is drawn from memory, not from a fresh open-minded search. The 5% is where revenue converts. The 95% is where revenue is decided.
2. Most of the journey is dark. Before a buyer ever fills out a form, they've asked a friend on another board, asked their attorney, asked ChatGPT, read reviews, lurked on LinkedIn, and forwarded someone's PDF around the committee. None of that appears in a CRM. This is the dark funnel — and it's not a measurement inconvenience; it's where the decision substantially happens. Attribution software sees clicks. Trust is built in conversations.
Put those together and you get the design principle for the Attract and Earn stages: market to the whole journey, including the parts you can't see, for buyers who aren't ready yet. Everything else in this module is mechanics for doing that.
Why it matters
Model buying as a funnel and you will manage to the visible 5% — because that's what the software can count. The predictable failure pattern: over-invest in capture (search ads, form-fills), judge long-horizon trust work by 30-day conversion windows, conclude it "doesn't work," cut it, and then wonder why cost-per-lead rises every year. (Module 1.7 flagged this: applying e-commerce attribution to an 18-month developer relationship makes the best B2B marketing look like failure. This lesson is where we fix the model that causes it.)
The dark funnel also breaks the naive read of every attribution report. When software says a new CPM inquiry came from "direct traffic," what actually happened was: attorney mentioned us at a closing → president read three market letters over six months → board member asked an AI assistant about switching managers and we were cited → then someone typed our name into a browser. Software credits the last step. Strategy has to credit the journey.
How it works
1. Map the real journey for your #1 ICP. Trigger → private research (dark) → peer/advisor consultation (dark) → shortlist formation (mostly dark) → committee evaluation (partially visible) → decision → post-sale experience. For each phase: what is the buyer doing, who are they talking to, what are they afraid of, and where could we be present?
2. Mark what's visible vs. dark. Visible: form-fills, event sign-ups, email engagement, ad clicks. Dark: word of mouth, referrer conversations, peer networks, podcasts, AI answers, forwarded content, social lurking. Be honest — for our categories the dark share is most of it.
3. Instrument what can be instrumented. The single highest-ROI fix in B2B measurement: self-reported attribution. Ask "how did you hear about us?" on every form, every intake call, every signed deal — as an open text field, not a dropdown — and log it religiously. Pair it with directional signals: branded search trend, direct traffic trend, "we already knew you" rate on first calls, engaged Tier-1 accounts.
**4. Design for the dark funnel instead of resenting it.** If decisions happen in invisible conversations, the job is to be present in them: content worth forwarding (ungated — a gate stops the forward), referrers armed with our materials, answers cited by AI assistants (Lesson 2.5), a founder voice people quote in rooms we're not in. You can't track it per-click. You can absolutely influence it — and measure it in aggregate.
CHARLESGATE example
The condo-board journey, mapped honestly (teaching draft). Trigger: manager misses the third consecutive maintenance request; president's inbox fills with angry owners. Dark research: president texts a friend who's on another board ("who do you use?"); asks the association's attorney at the next closing; asks ChatGPT "how hard is it to switch property management companies in Boston"; reads Google reviews at 11pm. Shortlist: three names — the friend's manager, the attorney's mention, and a firm whose market letter the treasurer has been receiving for a year. Visible funnel begins: now someone visits our site and books an assessment — and the CRM writes "source: direct."
Everything that decided the shortlist happened before our software saw anything. Which is why CPM's Attract/Earn plan (Module 1, Template 6) weights the attorney/reserve-study referrer network, the market letter, and AEO citability — presence in the dark phase — and why every assessment call opens with "how did you hear about us?" logged verbatim.
Do the Work
Workbook Template 8 (Buyer Journey & Dark Funnel Map): for your OpCo's #1 ICP, map trigger → decision across the phases above. For each phase: buyer's activity, who they consult, visible-or-dark, where we're present today (score 0–3), where we could be. Then implement the instrumentation minimum: self-reported attribution question live on every form and intake script within two weeks, with a shared log. Bring the map and your first ten logged answers to the module discussion — the answers will surprise you, and they'll be truer than the dashboard.
2.2Demand Creation vs. Demand Capture vs. Lead Gen
First principles
Three terms that get blurred into mush, and the blur is expensive. They are three different jobs with three different maths:
- Demand creation (demand gen) — making the 95% care: teaching future buyers a problem is solvable, a standard is possible, and we're the ones who proved it. Long horizon. Compounding. Hard to attribute per-click. This is the Attract and Earn stages doing their real work.
- Demand capture — harvesting the 5% who are looking right now: search at trigger moments, review sites, referral moments, "request a proposal." Short horizon. Highly measurable. And capped — capture cannot exceed the demand that exists.
- Lead generation — converting interest into identifiable contacts (form-fills, sign-ups). A mechanism, not a strategy. Lead gen tells you nothing about whether the interest was created, captured, or coerced by a gate.
The category error that wrecks B2B budgets: running gated-content lead gen and calling it "demand gen." A whitepaper behind a form doesn't create demand — it converts (a fraction of) existing curiosity into contact records, most of them not in-market, then burns list goodwill with follow-up sequences. Meanwhile the actual demand creation — the honest answers, the market letter, the visible POV — got defunded because it doesn't produce a weekly MQL count.
Why it matters
Capture is capped and inflating. There are only so many people searching "switch property management company Boston" this month. Once you've captured your fair share, every additional capture dollar bids against competitors for the same finite 5% — which is why cost-per-lead only ever rises for capture-only teams. The escape isn't better capture; it's creating demand so that (a) the 5% arrives pre-sold and asks for us by name, and (b) the pool of in-market buyers who prefer us grows.
Creation is what makes capture cheap. Branded search, direct traffic, "we already knew you," referrals — these are demand creation's dividends, and they convert at multiples of cold capture. Most teams have this exactly backwards: they over-invest in capture because it demos well in attribution software, and starve creation because its returns land in next year's budget under someone else's line item. Discipline here is a leadership job — expect this module to make some dashboards look worse and the business better.
And gating strangles Earn. Our default, from the glossary and worth repeating as house law: un-gate the answers, gate the tools. Answers must travel (into the dark funnel, into AI citations, into the forwarded email to the board). Tools — calculators, benchmarks, assessments — are worth an exchange of contact information because they deliver individualized value.
How it works
1. Classify everything. Take last quarter's marketing spend and hours and tag every line: creation, capture, or lead-gen mechanics. Most teams discover they're 70–80% capture while describing themselves as "doing demand gen."
2. Set a target ratio and defend it. The long-run evidence (Binet & Field's brand/activation research — the closest rigorous analog) points to roughly 60/40 creation-to-capture for sustained growth, flexing by lifecycle and category. A newer OpCo pushing for near-term pipeline might run 40/60 for a few quarters; a franchise with strong inbound should push past 60/40. What's not defensible is 20/80 while calling it demand gen.
3. Judge each job by its own metrics. Creation: engaged ICP reach, list growth and engagement, branded search trend, "already knew you" rate, share of voice on our themes. Capture: cost-per-SQL, win rate, speed-to-lead. Lead gen: judged downstream — SQL conversion and pipeline, never raw MQL volume. Cross-judging is how good work gets killed: creation judged on 30-day CPL always loses; capture judged on "brand lift" always wins undeservedly.
4. Protect creation in downturns. When budgets tighten, capture defends itself with a dashboard and creation can't. Cutting creation to fund capture is borrowing from next year at loan-shark rates — you'll pay it back as higher CPLs and colder lists.
The house doctrine, verbatim (from "The Demand Gap," our New Dev pre-read — the field version of this whole lesson):
- Capture competes with everyone on price and timing. Creation builds a pipeline only you have. - A launch is not demand — it's a spike. Most projects mistake the spike for the engine, ride the buzz, then panic when tours dry up. "The question isn't 'how was the launch?' It's 'what's generating a tour this Tuesday?'" If the answer is "we're waiting for the sign to do its job," there is no engine — there's a memory of a launch. - A tactic spends money to make noise. An engine spends data to make demand. A tactic ends; an engine learns — every instrumented funnel makes the next one smarter.
The demand-gap self-test — ask these about any active line of business; each "no" is a gap: (1) Can you name the source of your last 10 tours/meetings? (2) What's producing a tour this week — not at launch, this week? (3) Do you know your traffic-to-lead and lead-to-tour conversion rates? (4) Are you running demand creation, or only capture? If every lead was already looking for you, you have no pipeline the competition doesn't also have.
CHARLESGATE example
Same OpCo, both jobs, kept distinct (teaching draft). CPM owner acquisition — capture: Google Ads on trigger-moment queries ("replace condo management company Boston"), review-site presence, referral-moment responsiveness, speed-to-lead standard on assessment requests. Capped by how many boards hit a trigger this quarter — spend past that and we're just raising our own auction prices. CPM — creation: the market letter (owned audience of board members not currently in-market), honest Big-5 content, board-education events, the attorney/reserve-study referrer network. None of it "converts" this month. All of it decides whose name is on the shortlist when the trigger fires.
AFF lead-gen for a new-dev project shows the B2C contrast: for unit sales, capture is legitimately the main event — portal placements, retargeting, launch-list sign-ups — because the in-market pool is large, visible, and fast-cycling. But even there, creation shows up as project brand and neighborhood story that makes the capture convert. And one level up, CRG's new-dev demand (winning the next developer) is almost pure creation: the 50-developer universe isn't searching for a sales team — demand for a "sell-out system" has to be taught into existence (the Sell-Out Files campaign, Template 5). Three budgets, three maths. Label them or lose them.
Do the Work
Workbook Template 9 (Demand/Capture Split Worksheet): classify last quarter's spend and people-hours line by line (creation / capture / lead-gen mechanics), compute the actual ratio, set the target ratio with a one-paragraph rationale, and name the two moves that shift it (what gets cut, what gets funded). Gate: each job must have its own metrics row — if any creation line is being judged on a 30-day conversion window, fix the scorecard before you fix the spend.
2.3The Channel Map: Where Attention Lives
First principles
A channel is where a message travels (email, LinkedIn, search, events, a referrer's lunch table). A medium is the form it takes (article, video, dinner, report). Blur them and you get planning theater — "we need to do video" is a medium in search of a channel in search of a strategy.
Channel choice is governed by one question with three parts: where does our ICP's attention already live (density), can we be distinctive there (right to win), and which Growth Code stage does it serve (job)? Not: what's fashionable, what a vendor is selling this quarter, or where competitors are. Channels also come in ownership classes — owned (your list, your site), earned (referrals, press, reviews, AI citations), paid (ads, sponsorships), rented (social platforms, where reach exists at an algorithm's pleasure) — and the long game is always the same: convert rented and paid attention into owned audience. The market letter list is an asset on our balance sheet. The follower count is a lease.
And the house rule, already in the Module 1 workbook: dominate 2–3 channels before dabbling in a 4th. Attention compounds with frequency; memory structures are built by showing up in the same place, the same way, again and again. Sub-threshold presence in six channels equals effective presence in zero.
Why it matters
We are a small team across four OpCos. Every channel commitment has a minimum effective dose — a cadence below which the channel produces nothing but the feeling of activity. Two posts ever on LinkedIn, one newsletter a quarter, a booth once a year: each is a real cost with a fake benefit. The Channel Plan exists to force the honest trade: fewer channels, dominated, with owners and cadences — and an explicit "not doing" list, which is the part that actually takes discipline. (Ries's law of sacrifice from Lesson 1.3 applies to channels too: you cannot own a room while refusing to give up the other rooms.)
How it works
For each candidate channel, score it (this is Template 6 from the Module 1 workbook — this lesson is its full teaching):
- ICP density (H/M/L). What fraction of the people in this channel are our buyers? A CAI-NE workshop is low-reach, extreme-density. Instagram is huge-reach, near-zero density for a board-president ICP — and high density for condo buyers. Density beats reach in finite universes.
- Trust channel or attention channel? Some channels create awareness (social, PR, paid); some create trust (referrers, events, email, long-form answers). Map to stage: attention channels serve Attract, trust channels serve Earn. A balanced map has both; a map that's all attention channels fills the top of a bucket with a hole in it.
- Right to win. Do we have an unfair advantage here — data nobody else has, a voice, relationships, existing presence? Extend strengths before opening fronts.
- Compounding or decaying? Content, SEO/AEO, lists, and referrer relationships compound. Paid impressions decay the moment spend stops. A healthy portfolio is weighted toward compounding channels, with decaying channels used as amplifiers (Lesson 2.6).
- Cost of dominance. Not the cost to be there — the cost to be unmissable there, at cadence, for four quarters. If we can't fund dominance, we don't enter.
Then commit: 2–3 channels with cadence + owner + metric, one experiment slot with a kill date, and the "not doing" list with reasons. Review quarterly against the metrics — kill or scale, no zombie channels.
CHARLESGATE example
Same company, two opposite maps — which is the point. CPM (board-member ICP): market letter (owned, Earn, H density), TAYA content + AEO (owned/earned, Earn + Attract, H density at trigger moments), attorney/reserve-study referrer network (earned, Attract + Repeat, H density), CAI-NE speaking slots (paid/earned, Attract — teach, don't table), LinkedIn for the CPM lead (rented, Attract, M density). Explicitly not doing: Instagram (wrong grammar, wrong buyer), cold email blasts (synthetic penalty in a small addressable universe = reputation risk). CRG new-dev unit sales (B2C buyer ICP): Instagram/Meta (rented/paid, H density), portals (paid, capture, H density), broker network (earned, H density), project site + launch list (owned). Same firm, zero overlap in the maps — because the ICPs' attention lives in different places. A channel map is downstream of an ICP decision, never a company habit.
Do the Work
Complete Template 6 (Channel Plan) for your OpCo for next quarter — now with this lesson's scoring: density, trust-vs-attention, right to win, compounding-vs-decaying, cost of dominance. Hard requirements: max 3 committed channels + 1 experiment with a kill date; every committed channel has an owner, a cadence, and a metric; the "not doing" row is filled in with reasons you'd defend to Michael. If your plan has more committed channels than your team has owners, it's fiction — cut until it's true.
2.4Content Strategy & TAYA 2.0
First principles
Marcus Sheridan's They Ask, You Answer reduces content strategy to one honest sentence: your buyers have questions; answer them better and more honestly than anyone else, especially the ones that make you uncomfortable. The Big 5 — the question categories buyers always ask and vendors reliably dodge:
- Cost/price — what does it actually cost, and what changes the number?
- Problems — what goes wrong with this (including with you)?
- Comparisons — you vs. the alternatives, played straight.
- Reviews — what do others say, honestly aggregated?
- Best-of — who's actually best for which situation (including when it's not us)?
The mechanism isn't "content marketing." It's trust arbitrage: every competitor's silence on price and problems is an open lane, and honesty in that lane converts — because the buyer's fear isn't "which vendor is nicest," it's "who will be straight with me when something goes wrong?" Answering the uncomfortable question is the demonstration. CHARLESGATE already practices TAYA. This lesson's job is to upgrade it from a practice to a system — and to version it for 2026.
TAYA 2.0 adds three things the 2016 playbook didn't need: (a) answers structured to be cited by AI assistants, because a growing share of "they ask" now happens in a chat window (Lesson 2.5); (b) visible human expertise — named authors, faces, first-person experience — because anonymous competent content is now free and therefore worthless; (c) assignment selling wired into the sales process, not left as a content team's hope.
Why it matters
This is the Earn stage's spine. Sheridan's evidence and ours: the prospect who consumed your honest content before the first call closes faster, negotiates less, and trusts more — you've collapsed perceived risk before sales ever engaged. Content is the only salesperson working at 11pm when the board president is searching, and the only one who can be in five hundred dark-funnel conversations at once (an ungated answer gets forwarded to the whole committee; a gated one dies in a form).
And the AI-era stakes cut both ways: generic answer content is now free for everyone to produce, which means it's invisible. What can't be generated: real numbers from real operations, honest problem inventories from actual experience, comparisons written by someone who's genuinely done both. The gap between "content" and earned answers is widening — and the whole margin lives in the gap.
How it works
1. Build the question inventory from the field, not the keyword tool. Harvest the actual questions: what do prospects ask on intake calls, what do boards ask in evaluations, what does sales get asked twice a week, what do owners ask property managers? Twenty-five real questions minimum. The uncomfortable ones are flagged, not filtered.
2. Prioritize bottom-up — cost and comparisons first. Counterintuitive and critical: start with the questions closest to revenue (BOFU), because they convert the already-in-market and arm every active deal. "What does condo management cost in Boston" outworks ten thought-leadership posts.
3. Answer better and more honestly than anyone. House standards: real numbers or honest ranges with what moves them; name the tradeoffs; include who shouldn't hire us (the sacrifice that makes the rest believable — positioning discipline applied to content); named author with real expertise; plain words. If legal-or-sales flinches at publishing the price ranges, that's the signal you're about to earn trust nobody else will.
4. Ship it in layers. The written answer (structured for citation — next lesson), a short video of the expert answering it human-to-human, and a one-paragraph forwardable summary. Same substance, three altitudes — the messaging-hierarchy logic from Lesson 1.5 applied to answers.
5. Wire in assignment selling. Before the board presentation: "Most boards find these two pieces useful before we meet — our pricing article and 'what goes wrong when you switch managers.'" The meeting starts educated, objections surface early, and the content's ROI shows up as shorter cycles — measure it.
One reframe that changes how teams respond to a conversion miss: "Eight tours and zero reservations is a process and preparation failure, not a buyer-quality failure — assignment selling attacks that directly." When leads aren't converting, the reflex is to blame lead quality and buy more traffic; the fix is usually preparation — content assigned before the interaction so the meeting starts educated and the objections are pre-handled.
6. Maintain it. Answers age. Refresh the top 20 annually (prices change, the market moves); an outdated cost article is worse than none.
CHARLESGATE example
CPM owner acquisition, the flagship (teaching draft). The five anchor pieces: "What condo management costs in Boston — real numbers and what changes them" (cost; ranges by building size, what drives fees up or down, published while every competitor says "request a quote"). "The 5 real problems with switching property managers — and who should pay for them" (problems; names the switching pain out loud, which is the #1 silent objection, and pairs with the First-90-Days Turnaround offer from Template 4). "Big national firms vs. boutique Boston managers vs. us — an honest comparison" (comparison; played straight, including where the national's scale genuinely wins). "Questions your management company hopes your board never asks" (the event-session content from Lesson 1.1, in writing). "Who CHARLESGATE is NOT a fit for" (best-of/sacrifice; sub-8-unit price shoppers told kindly to go elsewhere — the anti-ICP from Template 2, published). Assignment selling: the assessment-call script assigns the cost and switching articles before every board meeting. Result to watch: boards that read both close meaningfully faster — track it and the content budget defends itself.
Do the Work
Workbook Template 10, Part A (Big 5 Inventory): harvest 25 real questions for your OpCo from intake calls, sales, and operations. Tag each: Big-5 category, journey phase, uncomfortable (Y/N), existing content (link or gap), revenue proximity (H/M/L). Commit: the top two BOFU gaps get answered — written + video + named author — within 30 days. Bring the inventory and the two drafts; the discussion pressure-tests honesty (if nothing in your draft made anyone nervous, it isn't TAYA yet).
2.5SEO → AEO: Becoming the Cited Answer
First principles
Search didn't die; it grew a mouth. The buyer behavior underneath SEO — I have a question, I ask a machine — is intact and growing. What changed is the machine's answer: instead of ten blue links, an AI assistant (or Google's AI overview) composes an answer and cites sources. The 2026 reality: a large and rising share of buyer research ends at the answer, without a site visit — the zero-click journey. Which relocates the job. SEO asked: do we rank? AEO (answer-engine optimization) asks: when the machine answers our buyer's question, are we the source it cites — and the name it says?
First principle worth internalizing: AEO is not a new dark art. Answer engines are trying to give the user the most credible, specific, useful answer — which means AEO rewards exactly what TAYA rewards: genuinely expert, specific, structured, sourced answers, plus a consistent and well-reviewed reputation across the open web for the machine to triangulate. The honest get cited. There's a justice to it that keyword-stuffing-era SEO never had.
Why it matters
Run the trigger moment from Lesson 2.1 forward: the board president asks an assistant "how do I switch property management companies in Boston, and who's good?" The answer names two or three firms. If we're in the answer, we're on the shortlist before any visible funnel begins. If not, we're invisible at the exact moment of maximum intent — and no amount of capture spend fixes absence from the answer. This is Attract and Earn compressed into one machine-mediated moment.
The strategic window: our niches — condo management, mid-size new-dev sell-outs, Boston rental market data — are barely contested in AI answers today. Early, consistent, citable presence in a niche compounds; catching up later costs multiples. This is underpriced attention (Lesson 2.7's logic) in machine form.
How it works
1. Keep the SEO fundamentals — they're the substrate. Crawlable, fast, intent-matched pages; clean structure; real backlinks. Answer engines learn from the same web Google indexes. Table stakes, not the game.
2. Structure content answer-first. The question as a heading, a direct 2–3 sentence answer immediately below it, then the depth (evidence, ranges, tradeoffs). Machines extract; make extraction easy. One question per section; clean headings; summary boxes; schema markup where it applies (FAQ, organization, review).
3. Publish original data — the citation magnet. Assistants prefer sources with specifics nobody else has. Our unfair advantage is operating data: rent and turnover reality from thousands of managed units, absorption curves from actual sell-outs. "Boston rental market report, [year]: what actually rented, at what price, how fast — from N managed units" is un-generatable, and every AI answer about the Boston rental market wants to cite something exactly like it.
4. Be a consistent entity. Machines triangulate identity across the web: same name, services, locations everywhere; named experts with real footprints (authorship matters — a named person with a visible history outranks "admin"); reviews (volume, recency, rating — assistants read them and echo their sentiment); mentions in trusted third-party sources (press, associations, directories). Note the Growth Code loop: reviews and press are Repeat-stage outputs feeding Attract — the flywheel, machine-readable.
5. Test monthly, like a ranking report. Ask the assistants (ChatGPT, Gemini, Perplexity, Claude — and Google's AI overviews) the questions your buyers ask. Log: who's cited, who's named, are we mentioned, is what's said about us accurate. This is the citability audit — it was the experiment row in CPM's Module 1 channel plan; it now graduates to a quarterly standing instrument.
CHARLESGATE example
CPM owner acquisition (teaching draft). Audit query set: "best condo management company Boston" · "how much does condo management cost in Boston" · "how to switch property management companies Massachusetts" · "what to ask a property management company" · "self-manage vs hire property manager condo association." Suppose the audit finds we're cited on cost (the TAYA article's ranges get quoted) but absent from "best" and "switch" answers, where a national aggregator and two directories dominate. Gap plan: restructure the switching guide answer-first; get listed accurately in the directories the machines keep citing (if assistants trust those sources, be in those sources); accelerate the review-generation play (Repeat stage) because review sentiment is echoing into answers; publish the rental market report with our operating data and put a named CPM expert on it. Two quarters later, re-audit. The same play, run for CRG new-dev ("how to price a new condo development Boston," "how long does a Boston condo sell-out take") makes the machine cite our absorption data at developers — demand creation via citation, feeding the Sell-Out Files ABM warm-up.
Do the Work
Workbook Template 10, Part B (AEO Citability Audit): 10 buyer questions (pull from your Part A inventory) × 3+ assistants. Log cited sources, named firms, our presence, accuracy of what's said about us. Output: a gap plan with three moves — one content restructure, one entity/reputation fix (reviews, directories, authorship), one original-data asset to build. Calendar the re-audit quarterly with an owner. New-term note for the glossary: zero-click journey, citability audit, answer-first structure.
2.6Performance & Paid: Amplify, Don't Rescue
First principles
Paid media is renting attention with precision and speed. That's all it is — and both properties are genuinely valuable: precision (put this in front of these 50 named accounts) and speed (be present at trigger-moment searches today, not after twelve months of SEO). What paid cannot do is fix anything upstream. Paid is an amplifier: feed it a sharp position and a proven message and it scales growth; feed it a generic message and you are paying to be ignored faster — at scale, with reporting. Weak teams use paid as a rescue for weak positioning or thin trust. It never works; it just makes the failure measurable.
Two evidence anchors govern the budget. First, Binet & Field: long-run growth comes from a balance of brand-building and activation — roughly 60/40 over multi-year horizons — and over-rotating to activation (capture) produces a short sugar-high and a long decay. Second, the 2026 finding that creative is the targeting: distinctive creative now does much of the audience-selection work algorithms used to do — the right people stop for the right idea. Which means the creative brief is not decoration on a media plan; it is the media plan's main lever.
A house terminology note, unavoidable in our building: in paid media, "CPM" means cost per thousand impressions. Since CPM is one of our OpCos, house style is to write cost-per-thousand in media contexts. (Glossary addition noted. Yes, everyone will make the joke once. Once.)
Why it matters
Paid is where the most B2B money dies quietly, for a structural reason: platforms grade their own homework. Platform-reported ROAS credits the platform for conversions the rest of the system created (the board that read our content for a year, then clicked a retargeting ad on the way in — the ad gets 100% of the credit and next quarter's budget). Meanwhile, in our finite ICP universes, broad-reach paid is structurally wasteful: with ~300 addressable condo associations or 50 target developers, "reach" beyond the universe isn't spillover, it's spend on people who can never buy. B2B paid earns its keep in four narrow jobs — and only those four:
- Capture at trigger moments — search ads on in-market queries. Capped by query volume (Lesson 2.2); spend past the cap only inflates the auction.
- Air cover for named accounts — being visibly present to the 50 accounts an ABM program is warming (Module 3.2), so the outreach doesn't arrive cold.
- Retargeting the engaged — cheap frequency against people already in our world (market-letter readers, content visitors). Powerful, and creepy past a frequency cap; set one.
- Amplifying proven organic — putting spend behind the post, the report, or the case study that already demonstrated organic resonance. Organic is the test market; paid is the multiplier.
How it works
Rules of engagement, in order:
- Organic proves, paid scales. Nothing gets paid promotion until it earned organic signal — engagement from ICP humans, replies, shares, self-reported mentions. This one rule deletes most wasted B2B ad spend.
- Match spend to universe size and stage. Finite universe → named-account targeting and retargeting only. Large universe (unit-buyers) → broad targeting with creative-as-targeting doing the selection. Attract-stage spend judged on memory metrics (engaged ICP reach, branded search lift); capture spend judged on cost-per-SQL and win rate. Never cross-judge.
- Brief creative like it's the strategy, because it is. Distinctive, specific, drawn from the Messaging Doc's value themes and proof — never platform-generic "we're hiring/we're proud" wallpaper. The 2026 penalty for synthetic-feeling work applies to ads doubly: an AI-flavored ad is invisible and it slightly erodes the brand it was meant to build.
- Measure at the system level. Per-motion CAC and MER (total revenue ÷ total marketing spend) as the honesty checks; platform ROAS as a directional input, never the verdict. Triangulate with self-reported attribution ("saw your ads" tells you air cover is registering).
- Cap capture at demand. Compute the honest ceiling (query volume × achievable share). Surplus budget goes to creation, not to bidding against ourselves.
CHARLESGATE example
Three paid programs, three grammars (teaching draft). New-dev unit sales (B2C, AFF executing): paid works hardest here — portal placements, Meta lifestyle creative built on the project brand, launch-list retargeting, urgency from real absorption ("60% sold in 90 days" — honest urgency per Lesson 1.6). Large in-market universe, fast cycle: capture-heavy is correct, and creative-as-targeting picks the buyer out of the feed. CPM owner acquisition (B2B, finite universe): search ads on trigger queries = the capture worth owning, with the honest ceiling computed; retargeting on market-letter readers and content visitors = cheap trust-frequency; broad LinkedIn lead-gen forms = explicitly not doing (universe too small, synthetic smell, platform grading its own homework). CRG new-dev / Sell-Out Files (ABM): air cover only — the case-study teardown promoted exclusively to the 50 named accounts' people, so when the 1:1 outreach lands (Module 3.5), we're already vaguely familiar. Judged on engaged accounts, not clicks. Total paid budget follows the Template 9 split: capture capped at demand, the surplus amplifying proven creation.
Do the Work
Score every current paid line against the four jobs and five rules: which job is it doing, is the universe-match right, did the creative earn organic proof first, what's the honest capture ceiling, and what would we know if we ignored platform ROAS and used per-motion CAC + self-reported attribution instead? Kill or reassign at least one line that exists only because a platform dashboard flatters it. Feed the result back into Template 9's ratio — paid is usually where the demand/capture split is most out of balance.
2.7Attention & Organic Social: The Gary Vee Lesson, Applied to B2B
First principles
Gary Vaynerchuk's core insight isn't about social media; it's about markets: attention is the asset, and it reprices. Attention migrates to new platforms and formats faster than advertisers follow, which creates windows of underpriced attention — reach and memory available at a fraction of its worth, paid for in effort and craft instead of dollars. His second insight: native or nothing. Content made for the platform (its format, rhythm, culture) earns attention; content adapted from a press release gets scrolled past at the speed of thumb. Third: document, don't create — the raw material is the work you already do; publishing what's true beats manufacturing what's clever, and it scales because the supply is infinite.
The B2B adaptation, per Module 1.7's transfer guide: steal the instincts, swap the metric. Gary Vee's game counts how many saw it. Ours counts who — ICP density of the audience, not size. Fifty board presidents and twelve developers following the right voice outvalue fifty thousand strangers.
Here's the arbitrage in our market, stated plainly: commercial and residential real estate B2B social is a desert of genericness — congratulatory reposts, stock-photo listings, "honored to announce." Attention in front of owners, boards, developers, and investors on LinkedIn is wildly underpriced because almost nobody in our category says anything real. The bar for distinctive is on the floor. That's not a problem; that's the opportunity.
Why it matters
Organic social is the compounding Attract engine for the 95% — the mechanism by which future buyers form memories of us years before their trigger fires, at near-zero media cost. It's also infrastructure for half of Module 3: the founder-led motion runs on it (3.4), outbound lands warmer because of it (3.5), ABM warm-up leans on it (3.2), and the dark funnel runs straight through its DMs and shares — the "saw your post" mentions in self-reported attribution are this channel cashing in.
And it's the most human-legible proof of the AI-era thesis: feeds are flooding with generated content, which means real — a named person, a real building, an actual number, an opinion that costs something — is becoming the scarcest and most valuable format. AI pulls everyone to the middle. A property manager telling the truth about a botched special assessment isn't in the middle.
How it works
The operating system, not the inspiration:
- Pillars from the Messaging Doc. 2–3 content pillars per voice, pulled from Template 3's value themes — so every post, however casual, pushes the position. (Sharp positions make attention cheap; this is where that cashes.)
- Document real work. The building turnaround, the pricing call that went sideways, the absorption curve that surprised us, the market data nobody else has. Anonymize what needs it; keep the specifics that make it true. Our operating reality is a content mine competitors can't fake and won't publish honestly.
- Volume with an editorial bar. Cadence: 2–3 posts/week, sustained for quarters — consistency over intensity (daily-for-three-weeks-then-silence builds nothing). Bar: every post has a specific, a number, or an opinion that costs something. No congratulatory wallpaper, no AI-flavored engagement-bait. The bar is what makes the volume compound instead of dilute.
- Native formats. Text-and-image posts that read like a person; short video where a human answers a Big-5 question to camera; carousels for data. Repurpose along the messaging hierarchy — the TAYA article becomes six posts — but re-make, don't re-paste.
- Engagement is the actual networking. Comments and DMs with ICP humans are the point, not the exhaust — fifteen minutes a day engaging in-network is a relationship play wearing a content costume. The DM thread with a developer is worth more than the impression count of the post that started it.
- Rented → owned, gently. Periodic (not constant) CTAs to the market letter and entry offers. The platform is the fishing ground; the list is the boat.
Measurement: ICP follower density (are the right people accumulating), inbound DMs and intros, "saw your post" in self-reported attribution, list adds sourced from social. Impressions are weather.
CHARLESGATE example
Four voices, one system (teaching draft). CPM lead: anonymized building stories — "a 40-unit association just discovered their reserve study was fiction; here's how boards can check theirs in 20 minutes." Board members share it to other board members: the dark funnel doing our distribution. CRG new-dev lead: absorption takes and pricing honesty — "everyone prices new construction off comps; here's why comps miss what actually rents" — which doubles as Sell-Out Files air cover to the 50 named developers. Michael: the market POV at HoldCo altitude — where Boston's market is going, what owners should demand, the creativity-moat thesis itself — the founder-led motion Module 3.4 systematizes. AFF: craft in public — teardowns of what makes development marketing work, which is both content-led demand gen for the agency and proof for CRG's system story. Every voice: pillars from the Messaging Doc, documentation over creation, the editorial bar, periodic CTAs to owned lists. One desert, four distinctive voices — the arbitrage compounding across the OpCo portfolio.
Do the Work
Run a 30-day attention sprint for one voice in your OpCo: pick the one platform with highest ICP density (almost certainly LinkedIn for B2B ICPs), define 2–3 pillars from your Template 3 value themes, and ship 12 posts in 30 days documenting real work — every post passing the bar (a specific, a number, or an opinion that costs something). Fifteen minutes daily engagement with ICP humans, logged. Measure: ICP-follower adds, DMs/conversations started, self-reported mentions. Review against the Channel Plan at day 30: commit at cadence, or kill with reasons. No zombie presence.
Module 2 Exit Checklist
You're done with Module 2 when your OpCo has, on paper and reviewed:
- Buyer Journey & Dark Funnel Map for the #1 ICP, with visible/dark phases marked and presence scored (2.1 / Template 8)
- Self-reported attribution live on every form and intake script, with a shared log and first entries reviewed (2.1)
- Demand/Capture Split computed for last quarter — spend and hours — with a target ratio and the two moves that shift it (2.2 / Template 9)
- Channel Plan committed: max 3 channels + 1 kill-dated experiment, owners and cadences named, "not doing" list defensible (2.3 / Template 6)
- Big 5 question inventory (25 real questions) and the top two BOFU answers shipped — written + video + named author (2.4 / Template 10-A)
- AEO Citability Audit run, gap plan with three moves, quarterly re-audit calendared with an owner (2.5 / Template 10-B)
- Every paid line scored against the four jobs; at least one platform-flattered line killed or reassigned; capture capped at the honest demand ceiling (2.6)
- 30-day organic attention sprint completed and a commit/kill decision made against the Channel Plan (2.7)
These artifacts are the Attract + Earn machinery your Module 3 motion stack will run on, and Module 9 capstone inputs.
New Workbook Templates This Module Calls for (Build Next)
- Template 8 — Buyer Journey & Dark Funnel Map (Lesson 2.1): per-ICP journey grid — phases trigger→post-sale × (buyer activity / who they consult / visible-or-dark / our presence today 0–3 / our play). Plus the instrumentation block: self-reported attribution question wording, where it's asked, where it's logged, who reviews it monthly.
- Template 9 — Demand/Capture Split Worksheet (Lessons 2.2, 2.6): line-by-line classifier for spend + hours (creation / capture / lead-gen mechanics), actual vs. target ratio, per-job metrics rows (so creation is never judged on capture windows), and the two reallocation moves with owners.
- Template 10 — Big 5 Inventory & AEO Citability Audit (Lessons 2.4, 2.5): Part A — 25-question inventory with Big-5 category, journey phase, uncomfortable flag, existing-content link/gap, revenue proximity, and the 30-day answer commitments. Part B — 10 questions × assistants grid (cited sources / named firms / us? / accuracy), gap plan (content restructure + entity fix + data asset), quarterly re-audit owner and date.
New Glossary Terms Introduced (Extend the Glossary)
Trust channel vs. attention channel (2.3) · minimum effective dose (of a channel/motion) (2.3) · trust arbitrage (2.4) · zero-click journey (2.5) · citability audit (2.5) · answer-first structure (2.5) · air cover (2.6 — named-account paid presence supporting ABM/outbound) · cost-per-thousand (2.6 — house style for media "CPM," to avoid collision with the OpCo) · honest capture ceiling (2.6) · underpriced attention (2.7) · document, don't create (2.7) · ICP follower density (2.7)
Sources drawn on in this module (see framework doc for full lineage): Ehrenberg-Bass Institute / LinkedIn B2B Institute — 95:5, mental availability; Andrei Zinkevich / Full-Funnel — dark funnel, demand creation vs. capture discipline; Marcus Sheridan — They Ask, You Answer (the Big 5, assignment selling); Binet & Field — brand/activation balance (~60/40 long-run heuristic); Gary Vaynerchuk — attention as the asset, native content, document-don't-create; Alex Hormozi — lead-magnet bar (free thing better than competitors' paid thing); Demand Gen Report 2026 B2B trends — synthetic-outreach penalty, creative-as-targeting, AI-answer behavior; Startup Content Planning Workbook (CHARLESGATE resource library) — Lesson 2.4 supplementary.
Rules of the workbook:
- Every template pairs a blank canvas with a worked CHARLESGATE example. The examples are teaching drafts — directionally right, but every number/claim must be validated against current company data before external use.
- Write in plain language. If a cell reads like a brochure, redo it.
- These are living operating documents, not homework. Date them, version them, review them on the annual/quarterly cadence in the framework doc.
Contents: T8 Buyer Journey & Dark Funnel Map · T9 Demand/Capture Split Worksheet · T10 Big 5 Inventory & AEO Citability Audit
T8Buyer Journey & Dark Funnel Map
(Lesson 2.1. Map the real journey for your OpCo's #1 ICP — including the parts software can't see. Prerequisite for the Channel Plan and every campaign brief.)
Blank canvas — Part A: the journey grid
| Phase | What the buyer is doing | Who they consult | Visible or dark? | Our presence today (0–3) | Our play (where we could be) |
|---|---|---|---|---|---|
| Trigger | |||||
| Private research | |||||
| Peer / advisor consultation | |||||
| Shortlist formation | |||||
| Committee evaluation | |||||
| Decision | |||||
| Post-sale experience |
Scoring: 0 = absent · 1 = accidental presence · 2 = deliberate but thin · 3 = deliberately dominant.
Blank canvas — Part B: the instrumentation block
| Item | Your answer |
|---|---|
| Self-reported attribution question (exact wording) | "How did you hear about us?" — open text, never a dropdown |
| Where it's asked (every form, every intake script — list them) | |
| Where verbatims are logged (one shared location) | |
| Who reviews it monthly | |
| Directional dark-funnel signals we track | Branded search trend · direct traffic trend · "already knew you" rate · engaged Tier-1 accounts |
Worked example — CPM condo-board journey (teaching draft)
| Phase | Buyer activity | Consults | Visible/dark | Presence | Our play |
|---|---|---|---|---|---|
| Trigger | Manager misses 3rd maintenance request; president's inbox fills with angry owners | — | Dark | 0 | Trigger outbound play (3.5): failed-inspection/public-record watch |
| Private research | Googles + asks ChatGPT "how hard is it to switch property management Boston"; reads reviews at 11pm | Machines | Dark (AI) / partially visible (site) | 1 | AEO citability (T10-B); honest switching-cost article, ungated |
| Peer/advisor | Texts friend on another board; asks association attorney at a closing | Friend, attorney | Dark | 1 | Referrer network (attorney/reserve-study lunches); content worth forwarding |
| Shortlist | 3 names: friend's manager, attorney's mention, the firm whose letter the treasurer gets | Committee memory | Dark | 2 | Market letter (owned audience of not-yet-in-market board members) |
| Committee evaluation | Proposals, references, board meeting | Whole board | Partially visible | 2 | Enablement kit (7.2): forwardable one-pager, treasurer-grade reports sample |
| Decision | Vote | Board | Visible | 2 | Easy-out risk reversal (T4); speed-to-lead SLA |
| Post-sale | Transition; first annual meeting | Owners | Visible to us | 2 | First-90-Days delivery → referral/review play at peak satisfaction (T14) |
| Instrumentation | Attribution question live on assessment form + intake script; verbatims logged in CRM field; [owner] reviews monthly |
The finding this map produces: everything that decides the shortlist happens before our software sees anything — which is why the letter, the referrers, and AEO out-rank ad spend in CPM's channel plan.
T9Demand/Capture Split Worksheet
(Lessons 2.2 & 2.6. Classify last quarter's spend AND hours. Most teams discover they're 70–80% capture while describing themselves as "doing demand gen.")
Blank canvas
Part A — the classifier (one row per line item; include people-hours at loaded rates)
| Line item | $ | Hours | Classification: Creation / Capture / Lead-gen mechanics | Judged by (its own metric — see Part C) |
|---|---|---|---|---|
Part B — the ratio
| Creation | Capture | Lead-gen mechanics | |
|---|---|---|---|
| Actual last quarter ($ + hrs) | |||
| Actual % | |||
| Target ratio (default 60/40 creation:capture, flexed by lifecycle — write the rationale) | |||
| The two moves that shift it (what gets cut, what gets funded — with owners) |
Part C — per-job metrics (mandatory — cross-judging is how good work gets killed)
| Job | Its own metrics | Never judged by |
|---|---|---|
| Creation | Engaged ICP reach · list growth/engagement · branded search trend · "already knew you" rate · share of voice | 30-day CPL or conversion windows |
| Capture | Cost-per-SQL · win rate · speed-to-lead | "Brand lift" |
| Lead gen | Downstream SQL conversion · pipeline | Raw MQL volume |
Gate: if any creation line is being judged on a capture window, fix the scorecard before you fix the spend.
Worked example — CPM owner acquisition (teaching draft)
| Line item | $ | Hrs | Class | Judged by |
|---|---|---|---|---|
| Google Ads, trigger queries ("replace condo management Boston") | $X | 2/wk | Capture | Cost-per-SQL; capped at honest ceiling (query volume × achievable share) |
| Market letter (monthly) | $– | 8/mo | Creation | List growth; reply rate; "read your letter" mentions |
| Big-5 content + AEO structuring | $– | 12/mo | Creation | Trigger-page conversions; citability audit trend |
| Referrer lunches + co-hosted briefings | $X | 4/wk | Creation | Referral-sourced pipeline (quarters, not weeks) |
| Review-site presence + response | $X | 1/wk | Capture | Assessment requests from review paths |
| Gated "guide" w/ email sequence (inherited) | $X | 3/mo | Lead-gen mechanics | Downstream SQL rate — found to be ~zero; kill and un-gate |
| Actual ratio | 48/45/7 → target 60/40/0 | Moves: (1) cap search at ceiling, surplus → letter data issue; (2) un-gate the guide, delete the sequence |
T10Big 5 Inventory & AEO Citability Audit
(Lessons 2.4 & 2.5 — do them back-to-back. Part A harvests the real questions; Part B checks whether the machines cite us when buyers ask.)
Blank canvas — Part A: Big 5 Inventory (25 real questions minimum)
Harvest from: intake calls, sales, operations, board meetings, owner emails. The uncomfortable ones are flagged, not filtered.
| # | The question (verbatim, buyer's words) | Big-5 category (Cost / Problems / Comparisons / Reviews / Best-of) | Journey phase | Uncomfortable? (Y/N) | Existing content (link or GAP) | Revenue proximity (H/M/L) |
|---|---|---|---|---|---|---|
| 1 |
Commitments: the top two BOFU gaps get answered — written + video + named author — within 30 days. Owners + dates: TBD
House answer standards: real numbers or honest ranges · name the tradeoffs · include who shouldn't hire us · named author · plain words · if nobody's nervous, it isn't TAYA yet.
Blank canvas — Part B: AEO Citability Audit (quarterly standing instrument)
| Buyer question (from Part A) | Assistant | Sources cited | Firms named | Are we present? | Is what's said about us accurate? |
|---|---|---|---|---|---|
| ChatGPT / Gemini / Perplexity / Claude / Google AI |
(10 questions × 3+ assistants. From Module 8.4, add the Win-stage query class: "Is [CHARLESGATE] a good choice for [X]? What are the risks?")
Gap plan (three moves):
| Move | What | Owner | Date |
|---|---|---|---|
| 1. Content restructure (answer-first) | |||
| 2. Entity/reputation fix (reviews, directories, authorship) | |||
| 3. Original-data asset to build |
Re-audit: quarterly · owner: TBD · next date: TBD
Worked example — CPM (teaching draft, compressed)
Part A highlights: "What does condo management actually cost in Boston?" (Cost · shortlist phase · uncomfortable Y · GAP → anchor piece #1 · H) · "What goes wrong when you switch managers, and who pays?" (Problems · research · Y · GAP → anchor #2 · H) · "Big national vs. boutique vs. you?" (Comparisons · evaluation · Y · partial · H) · "Are you worth the fee difference vs. [cheap local]?" (Cost/Comparisons · evaluation · Y · GAP · H) · "Who should NOT hire you?" (Best-of · any · Y · GAP → the sacrifice piece · M).
Part B findings (illustrative): cited on cost (article ranges quoted by 2/4 assistants); absent from "best" and "how to switch" answers, where a national aggregator + two directories dominate. Gap plan: (1) restructure the switching guide answer-first with schema; (2) fix directory listings the machines keep citing + accelerate the review play (sentiment echoes into answers); (3) build the rental market report with named CPM expert (citation magnet). Re-audit: quarterly, [owner].
Cross-references: T8 feeds T6 (Channel Plan) and every T5 brief · T9 feeds T18 (Budget Canvas) · T10-A feeds the content calendar (T15) and objection library (7.2) · T10-B is the standing machine-channel instrument (8.4). Sources: Ehrenberg-Bass 95:5; Zinkevich/Full-Funnel (dark funnel, self-reported attribution); Sheridan (Big 5); Binet & Field (60/40).
The Playbook Library: Choosing and Combining How We Go to Market
The playbook library: ABM, inbound, founder-led, outbound, community, partner — and combining them.
Definitions updated in v1.1. This module’s lesson text predates the update — where stage boundaries are discussed, the v1.1 Canon is the authoritative ruling (Attract = attract attention · Earn = earn pipeline · Win = qualified opportunity to signed and onboarded).
Module brief
CHARLESGATE Growth Code Academy · Module 3 of 9 · Status: COMPLETE
Growth Code linkage: This module operationalizes ATTRACT and WIN (with every motion also carrying Earn-stage freight — trust is built inside motions, not beside them). Module 1 chose who and why us. Module 2 taught the buyer-side physics. Module 3 is the heart of strategic marketing: choosing the repeatable approaches — motions — by which we acquire customers, and combining them into one coherent go-to-market per OpCo. Positioning underneath everything (Dunford), motions on top (Voje), stacked deliberately (Lesson 3.8).
By the end of this module you can: explain each of the seven motion families — what it is, when to use it, when NOT to, how it actually works, its B2B/B2C fit, and its metrics · score motions against your OpCo's buying behavior, economics, and unfair advantages instead of inheriting them by habit · run the selection discipline (Voje) and the ABM discipline (Zinkevich/Full-Funnel) · and build a motion stack — primary, secondary, experimental — that covers the Growth Code stages instead of chasing one silver-bullet motion.
How to use this module: One lesson per week for eight weeks, or two intensive days. Lessons 3.2–3.7 are the library — read all of them even if a motion "obviously isn't us," because knowing why a motion doesn't fit is half of strategy. Lesson 3.8 is the capstone; do not skip to it, and do not skip it. Module 1 artifacts (Positioning Canvas, ICP tiers, Messaging Doc, Offers) are prerequisites — a motion without a position is a delivery truck with no cargo.
A note on examples: CHARLESGATE examples are illustrative teaching drafts — directionally right, but OpCo mappings, numbers, and claims must be validated (and in CG Capital's case, compliance-reviewed) before external use.
3.1What a GTM Motion is (and How to Choose)
First principles
A GTM motion is a repeatable approach to acquiring customers — ABM, inbound, outbound, founder-led, community/event-led, partner-led, product-led, and their variants. The word that matters is repeatable: a motion is not a campaign (time-boxed) or a tactic (single action); it's a standing system with its own economics, cadence, team muscle, and time-to-signal.
Maja Voje's core insight, which this whole module runs on: motion choice is resource allocation, not preference. You don't pick motions the way you pick fonts. Each motion consumes a scarce budget of money, hours, and leadership attention, and each pays out on a different curve. Choosing motions is choosing what your team does all day — which makes it the most consequential marketing decision after positioning itself.
The selection logic has four tests, and a motion must pass all four:
- Buying-behavior fit. Does the motion match how this ICP actually buys — deal size, cycle length, committee or individual, where their trust forms (rooms vs. search vs. referrals), and whether they self-educate or need to be approached? A motion that fights the buying behavior loses to one that rides it, every time.
- Economics fit. Can the deal afford the motion? High-touch motions (ABM, relationship/event, outbound) cost real CAC per account and need high LTV to pay back. Low-LTV offers need low-touch, scalable motions (inbound, product-led). Run the math before the enthusiasm: LTV ÷ realistic per-account motion cost, against the 3:1 rule of thumb from the glossary.
- Asset fit (right to win). Which motions do our unfair advantages supercharge? Proprietary operating data supercharges content/inbound and AEO. Deep local relationships supercharge event/community and partner motions. A credible, opinionated founder supercharges founder-led. Running a motion without an asset behind it means competing on effort alone — the most expensive way to compete.
- Time-to-signal fit. How long until this motion proves or disproves itself — and can we afford to wait? Outbound and events produce conversations in weeks; inbound/content compounds over 2–4 quarters; ABM runs 2–4 quarters to pipeline; founder-led builds for quarters before it converts. Mismatch between a motion's clock and leadership's patience is the #1 cause of motion-hopping — killing good motions at month three of a nine-month curve.
And Voje's sequencing rule: beachhead first. Prove a motion on the narrowest winnable segment (Module 1.4's Tier-1 list is exactly this) before scaling it. A motion that can't win the beachhead won't win the market — it'll just fail more expensively.
Why it matters
Most companies never choose their motions; they inherit them. The founder did outbound, so there's outbound. A competitor runs webinars, so there are webinars. A vendor sold a tool, so there's whatever the tool does. The result is an accidental GTM: five motions at sub-threshold effort (remember Module 2.3's minimum effective dose — it applies to motions with even more force), none with an owner, none matched to how the buyer buys, all sharing a scorecard that measures none of them fairly.
For CHARLESGATE the stakes are multiplied by four: each OpCo sells a different offer to a different ICP with different economics and buying behavior — which means each OpCo needs its own motion stack, and copying CPM's stack onto CG Capital would be malpractice. The discipline of this module is what keeps four go-to-markets coherent instead of four accidents sharing a brand.
How it works
The selection process, per OpCo:
- Lay out the inputs: ICP + tiers (Template 2), buying-behavior notes (journey map, Template 8), deal economics (LTV, target CAC), and the unfair-asset inventory (from the Positioning Canvas's distinct capabilities — Template 1).
- Score all seven motion families (Lessons 3.2–3.7) against the four tests, 1–5 each. Be brutal on economics and time-to-signal — those are the two everyone fudges.
- Check stage coverage. Map surviving motions to Growth Code stages. A stack that's all Attract (three awareness motions, no trust machinery) or all Win (pure capture and outbound, no demand creation) fails before it starts. Module 2's demand/capture discipline applies here at the motion level.
- Write each motion's concentration line. Every motion card (Lessons 3.2–3.7) carries one: what we pour resources into, and what we explicitly ignore to afford it. It's the same concentration line a Growth Hypothesis carries (v1.1 Canon), so a motion and the hypothesis it serves read the same way. No sacrifice, no motion.
- Draft the stack: one primary (majority of resources — matched to how most revenue is actually won), one or two secondary (feeding or converting the primary), one experimental (small, kill-dated). Final stack construction is Lesson 3.8's job; this lesson produces the scored candidates.
CHARLESGATE example
A first-pass scoring across the HoldCo (teaching draft — this table is the module's spine; each row gets its full treatment in 3.2–3.7 and its final stack in 3.8):
| OpCo / line | ICP + buying behavior | Economics | Unfair assets | Motion candidates that survive the four tests |
|---|---|---|---|---|
| CPM (owner/association acquisition) | Finite universe of boards + owners; trigger-driven; they do search and ask AI at triggers; trust-heavy committee decision | High LTV (multi-year contracts) → can afford real CAC, but universe is finite | Operating data; TAYA content base; referrer relationships (attorneys, reserve-study firms) | Inbound/TAYA + AEO (primary candidate); partner-led; trigger-based outbound; board-education events |
| CRG — new-dev services | ~50 named developers; long cycles; relationship + proof driven; they don't search — they ask peers and capital partners | Very high LTV per sell-out → affords the most expensive motions | Sell-out track record + absorption data; AFF creative; cross-OpCo continuity | ABM (primary candidate); relationship/event-led; founder-led; outbound (inside ABM) |
| CRG — resale/leasing brokerage | Consumers + sphere; substantially B2C grammar; referral- and relationship-driven | Per-deal economics → motions must be cheap per acquisition | Agent spheres; brand; neighborhood presence | Relationship/sphere (primary candidate); personality-led agents; referral plays; geographic farming |
| AFF (agency clients) | Developers + RE brands buying creative judgment; they buy people and taste; portfolio-driven | Project + retainer LTV → moderate-to-high | The work itself (portfolio as proof); Michael + team voices; CRG/CPM proof loops | Founder/personality-led + content-led (co-primary candidates); partner referrals; selective outbound |
| CG Capital (LP/investor relationships) | Small named universe of institutions, family offices, HNW; trust + track record + compliance-constrained comms; nobody Googles their way to an allocation | Very high LTV → affords bespoke everything | Track record; cross-OpCo deal flow visibility; Michael's market credibility | ABM/relationship hybrid (primary candidate); founder-led POV; briefing events. Broad-reach motions fail the buying-behavior test outright |
Notice what the table kills: mass paid for CG Capital (wrong buying behavior), pure inbound for CRG new-dev (developers don't self-educate their way to a sales team), high-touch ABM for resale brokerage (economics fail). The kills are the strategy.
Do the Work
Workbook Template 11 (GTM Motion Selector): for your OpCo, score all seven motion families against the four tests (buying-behavior, economics, asset, time-to-signal), 1–5 each, with one line of evidence per score — no evidence, no score. Mark stage coverage per motion. Output: 2–3 surviving candidates ranked, with the single sentence "our primary motion candidate is X because that's how our revenue is actually won." Hold it — Lesson 3.8 turns candidates into the stack.
3.2ABM: Account-Based Marketing
First principles
When your market is a list, not a crowd, marketing changes species. ABM treats named target accounts as markets of one: you choose the accounts first, then build programs to win those specific accounts — marketing and sales running the same play on the same names, across the full journey. It inverts the funnel: not "generate leads and see who's in them," but "here are the 50 accounts that matter; make them know us, trust us, and talk to us."
Andrei Zinkevich's Full-Funnel model — our reference implementation — insists on the part the industry corrupted: ABM is a full-journey account program (awareness → engagement → activation → deal), not "ads targeted by company name." Buying a display campaign against a company list and calling it ABM is like buying a gym membership and calling it fitness. The model also gives us the standard tiering:
- 1:1 — a handful of must-win accounts, each with a bespoke plan.
- 1:few — clusters of 5–15 accounts sharing a pain/situation, running a shared play with light personalization.
- 1:many (programmatic) — the wider named list, running scaled programs (air cover, events, content) with account-level tracking.
The unit of measurement changes too: not leads — engaged accounts (a defined threshold of meaningful activity from the right people inside a named account). One form-fill from a random student is a "lead." Three committee members from a Tier-1 account consuming the case study and attending the roundtable is pipeline forming.
Why it matters
When to use it: finite, identifiable universe (you can literally list the accounts); high LTV that affords per-account investment; committee decisions and long cycles; a real Tier-1 list from Module 1.4 (if you couldn't name ten accounts then, ABM is premature — fix the ICP first). When NOT: large anonymous markets (unit buyers); low-LTV offers (economics fail); teams unwilling to run marketing and sales as one unit (orphaned ABM — marketing warming accounts sales never calls, sales calling accounts marketing never warmed — is the most common failure and it's fatal); or as a quick-pipeline fix (time-to-signal is 2–4 quarters; committing for fewer is paying the entry cost and skipping the payout).
The deeper strategic reason ABM fits us: in a 50-developer or 30-LP universe, every account interaction is material, and spray tactics don't just underperform — they damage reputation inside the entire addressable market (Module 1.7's warning, now operational). ABM is the anti-spray discipline: fewer, bigger, more winnable deals, pursued with craft.
B2B vs. B2C fit: pure B2B — the motion exists because of committees, long cycles, and nameable accounts. The closest B2C analog is luxury clienteling, which tells you the spirit: bespoke attention justified by deal size.
How it works
The Full-Funnel program structure (the HubSpot ABM blueprint in the resource library pairs with this):
- Account selection. The Tier-1 list from Template 2, refreshed with intent where observable (permits filed, financing closed, portfolio moves — in our world, "intent data" is often public record). The list is the strategy; garbage list, garbage program.
- Account intelligence. Per 1:1 and 1:few account: the committee (names, roles, fears — Template 2 Part B), current situation, alternatives they'd weigh, trigger horizon, warm paths in (mutual relationships, shared rooms, partners).
- Warm-up (Attract + Earn, account-scoped). Air cover (Module 2.6: the case study promoted only to their people), founder-led visibility in their feed (3.4), invitations to rooms worth being in (3.6), content answering their situation (Module 2.4's machinery, aimed). Weeks-to-months of becoming familiar before any ask.
- Activation. The entry offer from Template 4 — a sell-out pricing study, a portfolio review, a co-investment briefing — offered through researched, human 1:1 outreach (3.5). Low-friction, high-value, concrete: the trust-to-conversation bridge.
- Orchestration. Marketing + sales in a weekly account standup: per named account, what happened, what's next, who owns it. Without this meeting there is no ABM program, only ABM theater.
Metrics: engaged Tier-1 accounts (against the written definition of "engaged") · meetings/entry-offers accepted with named accounts · pipeline and win rate from the named list · account coverage (are we known by 2+ committee members?) · deal velocity vs. non-ABM baseline. Explicitly not: MQL counts, impressions, or anything that doesn't have an account name attached.
Concentration: pour the hours into a short, named Tier-1 list (1:1 for the top handful, 1:few for the rest) and one joint marketing-sales cadence against it. Ignore, to afford it: awareness spend aimed at "the market," accounts that aren't on the list, and MQL-volume targets. A list that keeps growing isn't concentrated.
CHARLESGATE example
CG Capital — the institutional/LP raise (teaching draft; every external element compliance-reviewed before use). Universe: ~30 named allocators — family offices, small institutions, HNW networks. Tiering: five 1:1 (mandate fit + warm-path quality), fifteen 1:few (clustered by investor type), the rest 1:many. Intelligence: mandates, past allocations, decision process, who they already trust. Warm-up: Michael's market POV where they'll see it; the market-thesis briefing (operating-data-fed — the un-generatable asset); an investor dinner-briefing cadence (3.6). Activation: a bespoke market-thesis session per 1:1 account — an entry offer that gives value before any raise conversation. Orchestration: capital + marketing in one standup, one account list. Note what ABM replaces here: there is no "lead gen" for institutional capital; there are named relationships, systematically earned. And the pattern is already in the building: the Sell-Out Files campaign (Module 1, Template 5) is ABM 1:many-plus-1:few for CRG new-dev — 50 named developers, air cover, founder-led content, roundtables, human 1:1 outreach, entry offer. Module 3 just names the discipline and adds the tiering and the standup.
Do the Work
Workbook Template 12 (ABM Tiering & Program Plan): tier your named list (1:1 / 1:few / 1:many) with selection rationale; write the "engaged account" definition your team will hold; per tier, define the warm-up plays, activation offer, owners, and the 90-day plan for the top five accounts; calendar the weekly account standup with named marketing + sales attendees. Gate: if you can't staff the standup, cut the list until you can — a smaller ABM program that runs beats a bigger one that's theater.
3.3Inbound & Content-Led
First principles
Inbound is earning discovery: being found and chosen by buyers who are educating themselves — because you answered what they asked (TAYA, Module 2.4), you're the cited answer at their trigger moment (AEO, Module 2.5), and there's a low-friction path from answer to conversation (entry offers, Template 4). Content is the engine; inbound is the full motion wrapped around it: publish → get found/cited → convert → nurture → sales meets an educated buyer.
The economics are the point: inbound assets compound. The pricing article works every night for years; the market report gets cited by machines indefinitely; the list grows. Paid attention decays the moment spend stops — inbound is the opposite curve, which is why it's expensive early (all cost, no signal) and absurdly cheap late (the asset base does the attracting). It is the purest expression of earned, not borrowed in the whole motion library.
Why it matters
When to use it: buyers who self-educate — they search, ask AI assistants, read, compare — at identifiable trigger moments; enough question volume/density to matter; high-enough LTV to repay the build; and a genuine expertise asset (we have the un-fakeable one: operating data). When NOT: as a fast pipeline fix — time-to-signal is 2–4 quarters, and leadership impatience kills more inbound programs than competition does; as a sole motion for tiny universes that don't self-educate (institutional LPs don't Google their way to allocations; developers rarely search their way to a sales team — for those ICPs content supports ABM rather than leading); or without publishing stamina — a quarter of enthusiasm followed by silence compounds nothing.
B2B vs. B2C fit: both, tuned per Module 1.7 — B2B content teaches toward trust (answers, data, proof); B2C content attracts toward desire (neighborhood guides, buying-process explainers for consumers). CRG's resale side can run consumer inbound (search-and-AI-friendly neighborhood expertise) with the same machinery at different altitude.
How it works
Assemble what Module 2 already built — this lesson is deliberately short on new machinery because the Module 2 artifacts ARE the inbound motion:
- Answer engine: Big 5 inventory → prioritized honest answers, named authors, video layers (Template 10-A).
- Discovery layer: SEO fundamentals + answer-first structure + original-data assets + entity/review hygiene (Template 10-B) — found by humans, cited by machines.
- Conversion paths: every high-intent answer pairs with an entry offer (assessment, study, calculator) — un-gate the answers, gate the tools. Message-offer match per landing page (one job per page).
- Nurture: the owned-audience letter — genuinely useful, evidence-led, monthly — for the 95% who arrived years early. Not-blast email; the Earn stage in inbox form.
- Assignment selling: sales assigns answers before meetings; meetings start educated (Module 2.4).
- Operating system: one editorial owner per OpCo; subject-matter experts as sources, not writers; refresh cadence on the top 20 assets; publishing calendar tied to the Channel Plan.
Metrics: trigger-page conversions and entry-offer take-rate · owned-list growth + engagement · self-reported attribution mentions (content/letter/AI answer) · % of inbound arriving pre-sold, and sales-cycle length on educated vs. cold deals · citability audit trend. Leading indicators first two quarters (publishing cadence held, ICP engagement); lagging thereafter (pipeline, CAC).
Concentration: pour into the handful of trigger-moment questions our ICP actually asks, answered better than anyone else answers them, plus the publishing stamina to hold the cadence for 2–4 quarters. Ignore, to afford it: topics outside the ICP's triggers, traffic for its own sake, gated whitepapers, and new channels before the core cadence holds.
CHARLESGATE example
CPM owner acquisition is the flagship inbound OpCo, and it's not close (teaching draft). The fit is textbook: a finite-but-searching universe (boards and owners genuinely do search and ask AI at trigger moments — Lesson 2.1's journey map proved it), high-LTV contracts that repay the build, trigger-driven buying that rewards being the cited answer at the moment of maximum pain, and the operating-data moat feeding content no competitor can fake. The assembled machine: Big-5 answers (cost, switching, comparisons — Lesson 2.4's five anchors) → AEO structure + rental market report as citation magnet → entry offer: the free Building & Financials Assessment (Template 4) → market letter nurturing every board member who's not ready yet → assignment selling into every board presentation. Each piece existed by end of Module 2; the motion is the loop that connects them with owners and cadence. Twelve months of discipline and CPM's cost of acquisition structurally diverges from every competitor who's still renting attention.
Do the Work
No new template — assemble. Using Templates 6, 9, and 10: write your OpCo's inbound motion on one page — publishing cadence + owner, the two conversion paths (answer → entry offer), the nurture vehicle + owner, the assignment-selling script for sales, and the leading/lagging metric split with review dates. If any component lacks an owner, the motion isn't real yet; say so on the page.
3.4Founder & Personality-Led
First principles
Dave Gerhardt's Founder Brand thesis, compressed: people follow people, not logos. A human face with a real POV earns attention and trust at rates no company page can approach — because trust is a human emotion, and it transfers: from the person to the firm, from the feed to the pipeline. In B2B this is systematically underexploited, which makes it systematically underpriced (Lesson 2.7's arbitrage, personified).
The motion: build one or more visible, opinionated market voices — publishing consistently where the ICP lives, engaging like a human, converting attention into owned audience and conversations. The raw material is Module 2.7's operating system (pillars from the Messaging Doc, document-don't-create, the editorial bar); this lesson turns it from a channel practice into an acquisition motion with its own economics.
What makes it a strategic asset in 2026 rather than a vanity project: a real person with real deals, real numbers, and opinions that cost something is un-generatable. AI floods every feed with competent-average content; a founder saying "here's the pricing mistake I made on a 60-unit sell-out and what it taught us" is not in the middle. The synthetic-outreach penalty has a mirror image: an authenticity premium.
Why it matters
When to use it: leaders with genuine expertise, a defensible POV, and the willingness to be consistently visible; ICPs that congregate where individuals publish (LinkedIn is the B2B default); long-cycle trust businesses where familiarity-before-the-deal decides shortlists — i.e., all four OpCos. It's also the cheapest air cover ABM can buy (3.2) and the thing that makes outbound land warm (3.5). When NOT: if it will be ghostwritten pablum — an obviously-AI founder feed is worse than silence, because it spends personal credibility, the one budget that doesn't refill; if the voice has no actual opinions (a POV that costs nothing is not a POV — glossary, category POV); and never as a single point of failure — a firm whose entire demand engine is one person's LinkedIn has key-person risk on its growth. Build a bench of voices; the founder is the flagship, not the fleet.
B2B vs. B2C fit: devastating in B2B precisely because it's rare there. In B2C-adjacent brokerage it's native — top agents have always been personality brands; the motion just gives it system and standards.
How it works
- POV from the position. The voice's stances derive from the Positioning Canvas and category POV — the founder brand is the Messaging Doc with a pulse, not a personal diary. (Dunford underneath, always.)
- Pillars and proof. 2–3 pillars per voice; every take anchored in real work, real numbers, named lessons. Document, don't create.
- Sustainable cadence. 2–3 posts/week, quarters not weeks; 15 minutes/day of genuine engagement — the DMs are the pipeline, the posts are the bait.
- Team leverage without ventriloquism. Support the voice with research, drafting from their transcripts and takes (interview them, don't invent them), editing, scheduling. The opinions, the specifics, and the replies stay human — human-in-the-loop, glossary definition, applied to people.
- Conversion machinery. Periodic CTAs to the owned list and entry offers; speaking and roundtable invitations harvested deliberately; the firm's pages amplify the humans, not vice versa.
- The bench. Each OpCo lead builds a voice in their lane (Module 2.7's four-voice example); Michael's HoldCo-altitude voice provides shared air cover over all of them.
Metrics: ICP follower density per voice · inbound DMs/intros/speaking invitations · "saw your post / follow Michael" in self-reported attribution · owned-list adds sourced from the voices · engaged-account lift on ABM lists when founder content runs (the 3.2 crossover metric).
Concentration: pour into one or two voices with a real POV, on the one platform where the ICP gathers (LinkedIn by default), at a cadence they can keep. Ignore, to afford it: being on every platform, ghostwritten volume, and topics the voice holds no stance on.
CHARLESGATE example
AFF is the natural founder/personality-led OpCo (teaching draft): agency buyers don't purchase deliverables, they purchase judgment and taste — and judgment is only observable in public. AFF's motion: the leads publishing craft-in-public (teardowns of what makes development marketing convert, honest post-mortems, creative POV), with the portfolio as rolling proof — content-led and founder-led fused, which is why 3.8 will make them AFF's co-primary. Michael's HoldCo voice runs above all four OpCos: Boston market POV, the creativity-moat thesis, owner/developer education — it simultaneously warms CRG's 50 developers (ABM air cover), lends credibility to CG Capital conversations (where the person's market judgment is half the diligence), and feeds CPM's referrer network visibility. One voice, four balance sheets credited. CRG resale agents run the B2C variant: agent personality brands with neighborhood POV — same operating system, consumer grammar, sphere-scale.
Do the Work
Draft a 90-day founder-brand plan for one voice in your OpCo (possibly you): the POV in three sentences derived from the Positioning Canvas; 3 pillars with five documented-work post ideas each; cadence + the 15-minute engagement block on the calendar; the support model (who researches, who drafts from transcripts, what stays human — write the line explicitly); conversion path (list + entry offer); and the three metrics you'll review monthly. Run it through the editorial bar from 2.7: if the sample posts contain no specific, no number, and no opinion that costs something, it's a logo with a face.
3.5Outbound that Doesn't Feel Synthetic
First principles
Outbound is the only motion where you choose the timing: you decide who hears from us and when, rather than waiting to be found. That's its unique strategic property — precision plus initiative — and it's bought at a known cost: you're interrupting someone who didn't ask. The whole craft of outbound is making the interruption worth it to the recipient.
The 2026 context sharpened this from etiquette into economics. AI made infinite personalized-looking sequences free — so buyers' filters hardened, and the research shows a synthetic-outreach penalty: roughly 45% of B2B buyers are less likely to consider a vendor whose outreach smells generated. The math flipped: volume outbound now produces negative returns in finite universes — every synthetic-feeling touch doesn't just fail, it inoculates a named account against the next touch. In a 50-developer market, a lazy sequence isn't a miss; it's arson.
So the modern rule, drawing on Hormozi's $100M Leads warm-to-cold framework: as familiarity drops, personalization and value must rise. Cold contact earns attention only through demonstrated relevance (you clearly know their situation) and led-with value (you give the good thing before any ask). Low volume, high craft, human sender.
Why it matters
When to use it: named-account universes (outbound is ABM's activation arm — 3.2's step 4); trigger-responsive plays (a public signal fires and you respond within days with something useful); reviving engaged-but-stalled relationships; anywhere waiting to be discovered cedes the timing to competitors. When NOT: spray lists of any kind (see arson, above); when you have no genuine relevance to claim (if the honest version of the message is "we sell things, you might buy things" — don't send it); when nothing upstream exists (cold outbound into zero familiarity works at a fraction of the rate of outbound air-covered by founder content and events — sequence the stack, 3.8); and never automated-personalization theater ("I loved your recent post" written by a machine that didn't).
B2B vs. B2C fit: essentially a B2B motion. The B2C analog is geographic farming in residential brokerage — a neighborhood is an ICP, the just-sold letter is trigger outbound — and the same law holds: the agent known in the neighborhood (relationship air cover) out-converts the stranger's postcard tenfold.
How it works
- Right list, right moment. Tier-1/2 named accounts only, prioritized by trigger signals — which in real estate are gloriously public: permits filed, financing recorded, inspections failed, portfolios traded, board filings. Watching the public record is our intent-data platform, and it's free.
- Research before contact. Per account: what's true about their building/project/fund right now, who's the right human, what's the warm path (mutual relationship, shared room, partner intro beats cold every time — check before sending anything).
- Lead with the give. The entry offer or a genuinely useful artifact: the pricing study, the benchmark, the relevant teardown, the market report chapter that answers their situation. Hormozi's bar from the glossary: the free thing should be better than competitors' paid thing.
- Write like one human to another. Specific observation → why it made us think of them → the give → a low-friction next step. Plain words, short, no persuasion theater. The synthetic swap test: if the message reads identically when addressed to the next account on the list, it fails — rewrite or don't send.
- Multi-channel, human throughout. Email + LinkedIn (warmer if the founder voice is already in their feed) + the event invitation (3.6 gives outbound a destination) + occasionally physical mail done well (scarce channels are attention arbitrage). Sequenced by judgment, not by workflow automation blasting on day 3.
- Speed-to-trigger as a standard. The window after a trigger fires is short and crowded; make "useful contact within X days of signal" an owned play with an SLA.
Metrics: reply quality (real conversations started) · meetings/entry-offers accepted from named accounts · trigger-response time · downstream: pipeline from outbound-touched accounts. Explicitly not: open rates, send volume, or "touches" — activity theater that rewards the exact behavior this lesson exists to kill.
Concentration: pour into named accounts with a live trigger and a genuinely relevant reason to write, sent by a person. Ignore, to afford it: spray lists, send-volume and "touches" targets, automated personalization, and accounts with no upstream familiarity yet.
CHARLESGATE example
Three plays (teaching drafts). CRG new-dev — the Sell-Out Files 1:1 layer: after two months of air cover and founder content, the CRG lead personally writes each warmed principal: a specific observation about their pipeline project (public record), one insight from our absorption data relevant to their submarket, the offer of a complimentary sell-out pricing study. Ten a month, hand-built. CPM — trigger outbound: elevator inspection failures and 40B filings are public; within days, the affected association's board contact receives a short, kind, useful note + our "what boards should ask after a failed inspection" guide. No pitch. The pitch is the usefulness — and when the manager-firing trigger fires months later, guess who's on the shortlist. CRG resale — farming: the neighborhood ICP, worked with real market specifics ("what the three sales on your street actually said about pricing") instead of generic postcards — outbound craft at consumer grammar.
Do the Work
Write three real outbound messages to three named Tier-1 accounts from your ABM/ICP list, each: researched specific → reason-for-them → the give → low-friction ask. Run all three through the synthetic swap test and read them aloud (Module 1.5's aloud test applies). Then define one trigger play for your OpCo: the public signal, the watch mechanism, the useful artifact, the owner, the response-time standard. Send the three messages this week — outbound is the one motion in this module you can genuinely start tomorrow, which is precisely why it's over-used badly and under-used well.
3.6Community, Relationship & Event-Led
First principles
Strip the software away and B2B real estate is a relationship market: finite players, long games, repeated interactions, reputations that travel faster than marketing. Deals are decided in rooms — dinners, boards, site walks, closings — years before and after any funnel touches them. The community/relationship/event motion is the decision to treat that reality as a system with owners and cadence instead of an organic happenstance ("People-first GTM," per the workbook in the resource library — the model where relationships are the primary growth engine, deliberately cultivated).
Three sub-motions, one family: relationship plays (multi-year cultivation of named accounts and referrers — the long game, run on a ledger, not a memory), event plays (rooms as the venue where trust forms at accelerated rates — with the standing rule from Module 1: teach, don't table; hosting your own room beats renting a booth in someone else's), and community plays (building or anchoring the ongoing gathering — the board-member education series, the developer roundtable circuit — where we're the convener, which is positioning you can't buy).
The first-principles economics: relationship capital compounds and is brutally hard to copy. It's the slowest motion to build and the deepest moat once built — a competitor can clone a landing page by Friday; they cannot clone fifteen years of closings, favors, and kept promises. It is also the motion most vulnerable to not being run as a motion at all — living in individuals' heads, untracked, unowned, evaporating with every departure.
Why it matters
When to use it: large deals, long cycles, finite geographically-concentrated universes, trust-dominant decisions — which is a description of every B2B line CHARLESGATE runs. This family is arguably our incumbent motion; the module's job is to industrialize it without making it transactional. When NOT: as a scalable-volume motion (it doesn't scale by spending; it scales by years); when you can't sustain presence (appearing at CAI-NE once and vanishing reads worse than absence — consistency is the entire signal); and never transactionally — a relationship play that's visibly an extraction device destroys the asset it's mining. The give-first discipline isn't manners; it's the mechanism.
B2B vs. B2C fit: B2B core. The B2C analog is the agent's sphere of influence — CRG resale natively runs on it (past clients, neighbors, the youth-sports sideline), and the same systemization (ledger, cadence, give-first, referral triggers) upgrades it from personality-dependent to durable.
How it works
- The room map. Where does the ICP already gather — CAI-NE, ULI, GBREB, board networks, lender/attorney circuits? Score by ICP density (Template 6 logic). Decide: which rooms do we join, which do we host?
- Hosted-room formats. The developer roundtable dinner (8–10 seats, peer conversation, one useful insight presented, zero pitch); the board-member education night ("questions your management company hopes you never ask," live); the investor market-briefing. Small, recurring, teach-first — the format IS the positioning.
- The relationship ledger. For Tier-1 accounts and top referrers: who owns the relationship, last meaningful touch, what we've given recently, what's next, cadence. Reviewed monthly like pipeline — because it is pipeline, earlier.
- Give-first plays, systematized. Introductions made, market intel shared, their events attended, their wins amplified, the useful artifact sent (3.5's gives, warm edition). Track gives like a CRM tracks calls — not to invoice them, but because untracked generosity is unmanaged strategy.
- Referral triggers. The peak-satisfaction moments (sell-out closed, turnaround delivered, annual meeting that went great) get a scripted, graceful ask — a play with a trigger, an ask, and a loud thank-you, per the glossary, not a hope.
- Event-to-system wiring. Every room feeds the machine: attendees → owned list (with permission), conversations → ledger, questions asked → Big-5 inventory (Template 10-A), hands raised → entry offers. An event that doesn't feed the system is an expensive party.
Metrics: Tier-1 relationships with a live cadence (touched per plan, not per accident) · referral-sourced pipeline and its win rate (referrals close at multiples — track it to defend the motion's budget) · hosted-room yield (conversations → assessments/studies booked) · repeat attendance (the community-forming signal) · gives logged per quarter. Time-to-signal honesty: conversations in weeks, pipeline in quarters, the moat in years.
Concentration: pour into a few rooms we can show up in every time (or host ourselves) and a live cadence with the Tier-1 relationships. Ignore, to afford it: one-off appearances, booth-and-badge-scan events, and any event judged on headcount.
CHARLESGATE example
CRG brokerage is the natural relationship/event-led OpCo (teaching draft) — both sides of it. New-dev services: the developer relationship game (roundtable circuit as the Sell-Out Files' warm engine, capital-partner and architect relationships as warm paths, every closed sell-out triggering the referral play at peak satisfaction). Resale: the agents' spheres, systematized — ledger, cadence, give-first, the neighborhood as community. Around them: CPM's board-education nights (the community play that manufactures trust with the exact humans who vote on management contracts — and feeds the market letter), and CG Capital's briefing dinners (for an ICP that decides almost entirely on relationship + track record, the room is not a marketing tactic supporting the motion; the room is the motion). Note the interlock the flywheel promises: one CRG closing dinner seats a developer (CRG), a future association (CPM), a marketing showcase (AFF), and a capital conversation (CG Capital). No other firm in this market can host that table. That's the structurally uncopyable part, catered.
Do the Work
Build the relationship ledger for your OpCo's ten most important relationships (Tier-1 accounts + top referrers): owner, last meaningful touch, last give, next give, cadence. Fill it honestly — the blanks are the findings. Then commit to one hosted room this quarter: format, the 8–15 invitees by name (from Tier lists), the teach-first content, the system wiring (list, ledger, inventory, entry offer), and a Template 5 campaign brief behind it. Review the ledger monthly alongside pipeline, forever.
3.7Channel/Partner & Product-Led
First principles
Two motions share this lesson because they share a superpower: both acquire customers while you sleep — one through other people's trust, one through self-serve value.
Partner/channel-led rests on a simple observation: your ICP already trusts someone — their attorney, lender, reserve-study firm, architect, GC, wealth manager — and that someone is in the room at the trigger moment before you are. The attorney knows the board is furious with their manager weeks before any search begins; the lender knows about the next development before the permit exists. A cultivated partner is a standing, pre-trusted referral channel into moments no marketing can see (the dark funnel, personified). The motion: map the partner universe, formalize the value exchange, give first, track it, thank loudly — the glossary's channel/partner-led definition, run as a system.
Product-led (PLG), translated for a services firm: in software, the product acquires users through self-serve value before any sales conversation. Our translation: productized, self-serve entry points — calculators, assessments, benchmarks, audits — that deliver real individualized value before a human conversation, qualifying and warming the buyer in the act of helping them. It's Hormozi's lead-magnet bar (the free thing better than competitors' paid thing) fused with Module 1.6's offer ladder: the entry offer, made partially self-serve, becomes acquisition machinery.
Why it matters
Partner — when to use it: adjacent professions touch your ICP at trigger moments (they do, in every OpCo lane); trust-dominant decisions where a warm referral collapses the Earn stage overnight (a referred deal arrives pre-trusted — the single cheapest Earn shortcut that exists); finite universes where referrer reputations carry. When NOT: if you won't reciprocate and track — an unfed referral loop dies in two quarters, and a partner who sends and receives nothing back becomes quiet anti-marketing; and never as pure extraction — partners smell one-way relationships instantly.
Product-led — when to use it: buyers who want value before conversation (Module 2's self-educating journeys); offers with a quantifiable first-value moment (pricing, benchmarks, health checks); as the conversion path inbound needs (3.3's step 3). When NOT: as a primary motion for high-touch trust businesses — a calculator never closed a $40M sell-out mandate; it opens doors, humans walk through them. In our world PLG is always a supporting motion; anyone selling it to us as the future of professional services is selling software economics to a relationship business.
B2B vs. B2C fit: partner-led is native to both (B2C referral: the agent's lender/attorney/inspector circuit). Product-led runs both grammars — consumer-facing tools (home-value, affordability) are B2C classics; the B2B versions just carry more proof and land on committees.
How it works
Partner motion:
- Map and tier the partner universe (ICP-adjacency × trigger visibility × trust carried): for CPM — association attorneys, reserve-study firms, insurance brokers, accountants; for CRG — lenders, architects, GCs, land-use attorneys; for AFF — complementary agencies, platforms, brokers; for CG Capital — wealth managers, fund counsel, placement networks (compliance-gated).
- Design the value exchange per tier — what do they get: referrals back, co-branded education for their clients (the board-education night co-hosted with the attorney serves their client development and ours), market data they can use, their expertise showcased to our audience.
- Run the give-first cadence (3.6's ledger extends to partners; the Module 1 channel plan already committed CPM to one referrer lunch a week — this is that line item, industrialized).
- Track and thank loudly. Referral source logged on every deal (the self-reported attribution question catches these); the thank-you is prompt, personal, and remembered.
Product-led motion:
- Choose entry points where our data moat shows: a rental pricing calculator fed by real operating data (un-fakeable); the board self-assessment ("score your management company in 10 minutes"); the sell-out pricing study (human-delivered but productized — named, scoped, repeatable); the development marketing audit (AFF).
- Deliver real value in the artifact itself — the output must be useful standing alone, or it's a brochure wearing a calculator costume.
- Gate the tool, not the answers (Module 2.2's law — tools are the legitimate gate).
- Wire the next rung: every tool output ends at the offer ladder's next step (assessment → proposal; study → mandate conversation), with a human follow-up that references their results — outbound with perfect relevance, gift-wrapped.
Metrics — partner: referral-sourced pipeline and win rate by named partner · partner activation (% of mapped partners who sent ≥1 referral this half) · gives delivered per partner · reciprocity balance. Product-led: tool completions from ICP (density again, not volume) · tool→entry-offer conversion · entry→core-offer conversion · self-reported "used your calculator/assessment" mentions.
Concentration: pour into a short list of named partners with real reciprocity, or one productized entry point done well. Ignore, to afford it: long partner lists nobody activates, and a second tool before the first one converts.
CHARLESGATE example
CPM's referrer network is the proven pattern (teaching draft): association attorneys and reserve-study firms sit exactly at the trigger moment (they hear "we hate our manager" first), the weekly referrer lunch and quarterly co-hosted board briefing are already in the Template 6 plan — this lesson adds the tiered map, the tracked gives, and the reciprocity review that turn a habit into a motion. CRG new-dev: lenders and architects as the warm-path grid ABM plugs into (3.2's "warm paths in" column is mostly this motion). CG Capital: wealth-manager and counsel relationships, compliance-gated, where the "referral" is an introduction and the give is genuinely useful market intelligence. Product-led across the house: the rental pricing calculator (CPM data moat, consumer-and-owner-facing), the board self-assessment (feeds the First-90-Days Turnaround ladder), the productized Sell-Out Pricing Study (already the Sell-Out Files' activation offer — note how the motions keep converging on the same machinery; that's coherence, and 3.8 makes it explicit).
Do the Work
Two artifacts. (1) Partner map: ten named partners for your OpCo, tiered, with per-partner value exchange, next give, owner, and the reciprocity log's home. (2) One productized entry point, spec'd: the tool/assessment, the standalone value it delivers, what's gated, the next-rung wiring, and the data-moat ingredient that makes ours un-copyable. Build the cheapest honest version this quarter; instrument the two conversion rates from day one.
3.8Combining Motions Into One Coherent GTM (Capstone)
First principles
Motions are not a menu to graze; they're an architecture. The capstone question isn't "which motions do we like?" — it's "which system of motions, sharing one position and one ICP, covers the Growth Code stages and feeds itself?" Three structural roles:
- Primary motion — where the majority of resource goes, matched to how most revenue is actually won for this OpCo. One. Singular. The most common GTM failure is refusing to pick it.
- Secondary motions (1–2) — chosen because they feed or convert the primary, not because they're independently attractive.
- Experimental (max 1) — small, instrumented, kill-dated. The discipline that lets you explore without diluting.
Two laws govern the stack. First, coherence: every motion runs the same positioning, ICP, and Messaging Doc (Dunford underneath any motion — a stack where each motion invents its own message is four small companies sharing a logo). Second, interlock: in a healthy stack, each motion lowers another's cost — content makes outbound warmer; founder visibility is ABM air cover; events feed the ledger and the list; partner referrals arrive pre-trusted, collapsing Earn; the entry offer converts all of them. That's the Growth Code's stage-compounding logic (each stage lowers the next one's cost) reappearing at the motion level — the flywheel, fractal.
And the honesty constraint from 3.1, now binding: every motion has a minimum effective dose. A stack you can't staff at dose is fiction. Five motions at half-dose equals zero motions at cost. Cut until it's true.
Why it matters
The sequencing mistakes that kill focus — name them so you can refuse them:
- Motion-hopping: quitting a 9-month motion at month 3 because a podcast praised a different one. Fix: time-to-signal written into the stack, reviewed against leading indicators, kill-dates honored in both directions (no early kills, no zombie extensions).
- Silver-bullet chasing: betting everything on one motion because it worked somewhere else. Fix: stacks, not bullets — and the four-test scoring from 3.1, which would have failed the transplant.
- Copying a competitor's stack without their assets: their founder has 80K followers; yours has 40 and no appetite. Motion choices are downstream of asset inventories.
- All-Attract stacks (or all-Win): three awareness motions and no trust or conversion machinery — a crowded top of a bucket with a hole in it. Fix: the stage-coverage check, mandatory.
- Peanut-buttering: equal resource to every motion because choosing is uncomfortable. The primary gets the majority; that's what primary means. (Ries's law of sacrifice, final appearance: you cannot run everything and own anything.)
Sequencing wisdom: start with the motions that create conversations now (outbound, events, relationship — weeks to signal) while building the compounding motions in parallel (content/inbound, founder — quarters to payoff), and layer paid amplification last, once there's proof to amplify (Module 2.6's first rule). A new line of business runs conversation-motions to survive while its compounding motions grow into primacy — then the stack rebalances. Stacks are living architecture, reviewed quarterly with the Growth Code audit.
How it works
Building the stack, per OpCo:
- Start from the 3.1 scorecard — surviving candidates, ranked.
- Name the primary with the one-sentence justification: most of our revenue is actually won by X, therefore X gets the majority of resource. If the sentence feels false, the scorecard was vanity — redo it.
- Choose secondaries for interlock, stated explicitly: "founder-led feeds ABM warm-up"; "partner referrals convert through the entry offer." An unstated feed is an unmanaged one.
- Run the stage-coverage check: map the stack against Differentiate → Attract → Earn → Win → Repeat. Gaps get filled by adjusting the stack, not by wishing.
- Dose and staff it: per motion — owner, hours/week, budget, minimum effective dose, and the honest capacity math. Cut here, in daylight, rather than discovering the cut mid-quarter.
- Sequence two quarters: what starts now, what builds in parallel, what waits; kill criteria and review dates per motion.
- One scorecard: leading and lagging metrics per motion (from lessons 3.2–3.7), on the OpCo's single page, reviewed monthly — kill/scale discipline per the framework's operating cadence.
CHARLESGATE example
The HoldCo motion-stack table (teaching draft — this is the module's deliverable in miniature; validate every mapping with OpCo leadership):
| OpCo / line | Primary | Secondary | Experimental | Interlock logic | Stage coverage check |
|---|---|---|---|---|---|
| CPM (owner/association acquisition) | Inbound/TAYA + AEO (3.3) | Partner-led referrer network (3.7); trigger outbound (3.5) | Board-education event series (3.6) → promote to secondary if room yield proves | Content arms the partners and the outbound gives; triggers time the outbound; events feed the letter; assessment entry offer converts all of it | Attract (AEO, partners) ✔ Earn (answers, letter, events) ✔ Win (entry offer→Turnaround) ✔ Repeat (reviews feed citability) ✔ |
| CRG — new-dev services | ABM, Full-Funnel model (3.2) | Relationship/event roundtable circuit (3.6); founder-led (3.4) | AEO for developer questions (2.5) | Founder content + air cover warm the 50; roundtables create the meetings; outbound activates with the pricing study; every sell-out feeds proof back to Differentiate | Attract (air cover, founder) ✔ Earn (teardowns, rooms) ✔ Win (pricing study→mandate) ✔ Repeat (closing → CPM/AFF/Capital triggers) ✔ |
| CRG — resale/leasing | Relationship/sphere, systematized (3.6) | Agent personality brands (3.4); referral plays + farming outbound (3.5/3.7) | Consumer AEO (neighborhood answers) | Personality content keeps the sphere warm; ledger + triggers convert it; farming extends it street by street | Coverage ✔ — B2C grammar throughout (Module 1.7) |
| AFF (agency clients) | Founder/personality + content-led, fused (3.4 + 3.3) | Partner referrals (3.7); selective outbound to a dream-list of accounts (3.5) | Productized marketing audit (3.7) | Craft-in-public is simultaneously proof, air cover, and referral fuel; CRG/CPM work supplies the un-fakeable case studies | Coverage ✔ — Win rides the portfolio + audit entry point |
| CG Capital (LP relationships) | ABM/relationship hybrid (3.2 + 3.6) | Founder-led market POV (3.4); briefing events (3.6) | — (deliberately none; compliance surface small) | Michael's voice + market-thesis briefings warm a 30-name universe; dinners convert to 1:1 conversations; track record is the proof engine | Coverage ✔ — all motions compliance-gated |
Above the OpCo stacks, two HoldCo-level assets make the whole thing more than the sum: Michael's founder voice (shared air cover across all five stacks) and the cross-OpCo flywheel (Repeat-stage machinery: every CRG closing triggers CPM, AFF, and Capital plays with named owners — the framework's uncopyable move, which no single OpCo stack owns but every stack feeds). That's the picture: five coherent stacks, two shared engines, one position family, one Code.
The flywheel is managed, not hoped for. The cross-OpCo flywheel runs as an operating system with real machinery: a HoldCo OKR with a number attached (inter-company cross-sell sourced/bundled revenue — $2.0M in 2026), a shared tracker with a named owner, monthly review at Presidents Council and the cross-OpCo sales meeting, a revenue-share policy so the referring OpCo is paid for the hand-off (incentives make the flywheel spin; goodwill alone doesn't), and a reporting cadence in which every open opportunity answers two questions: is there a cross-sell opportunity here (Y/N) and what is the NEXT STEP TO WIN? Cultural enthusiasm for "synergy" without the tracker, the owner, the rev-share, and the cadence is how flywheels stay slideware.
And when a stack enters a new market, entry is a playbook, not a project. The repeatable market-launch framework (built for CPM's Denver/Colorado entry, designed for reuse): launch-strategy one-pager (vision, narrative, success metrics) · market positioning ("why this market, why now," the independent-vs-national narrative) · audience map and top-account profiles · messaging guide with localized talking points · a 30/60/90 phased plan (Pre-launch → Launch → Momentum) · channel strategy weighted to local-first storytelling and relationship building · GTM assets list · scorecard · and duplicatable templates, so market #2 starts at 60% built. Design rules: modular, reusable, executable by a small nimble team.
Do the Work
Workbook Template 13 (Motion Stack Canvas) — your Module 3 exit artifact and a direct Module 9 capstone input: primary (with the one-sentence justification), secondaries (with explicit interlock statements), experimental (with kill date), stage-coverage map, per-motion owner/dose/capacity math (cut until true), two-quarter sequence, kill criteria, and the single scorecard. Present it to your OpCo president and Michael; defend the sacrifices out loud. The stack you can defend under questioning is the first one that's real.
Module 3 Exit Checklist
You're done with Module 3 when your OpCo has, on paper and reviewed:
- GTM Motion Selector scored — all seven families, four tests, evidence per score, 2–3 ranked candidates (3.1 / Template 11)
- If ABM is in your stack: tiered named list, written "engaged account" definition, 90-day top-five plan, weekly account standup calendared and staffed (3.2 / Template 12)
- Inbound motion assembled on one page from the Module 2 machinery — cadence, conversion paths, nurture, assignment selling, all with owners (3.3)
- 90-day founder-brand plan for one voice, with the human/AI support line written explicitly and sample posts passing the editorial bar (3.4)
- Three real outbound messages sent to named Tier-1 accounts (synthetic swap test passed) + one trigger play defined with owner and response-time standard (3.5)
- Relationship ledger live for the ten most important relationships + one hosted room committed this quarter with a campaign brief behind it (3.6 / Template 5)
- Partner map (ten named, tiered, value exchange, owner) + one productized entry point spec'd with conversion wiring (3.7)
- Motion Stack Canvas complete, capacity-honest, stage-coverage-checked, sequenced two quarters — presented and defended (3.8 / Template 13)
These artifacts are the go-to-market architecture that Modules 4 (campaigns and plays) and 5 (measurement and budget) will execute and instrument, and the core of your Module 9 capstone plan.
New Workbook Templates This Module Calls for (Build Next)
- Template 11 — GTM Motion Selector (Lesson 3.1): per-OpCo scorecard — seven motion families × four tests (buying-behavior fit, economics fit, asset fit, time-to-signal fit), 1–5 with an evidence line required per score; stage-coverage row per motion; output block for ranked candidates and the primary-motion sentence. Include the worked HoldCo first-pass table from 3.1 as the example.
- Template 12 — ABM Tiering & Program Plan (Lesson 3.2): named-list tiering grid (1:1 / 1:few / 1:many with rationale); the "engaged account" definition block; per-tier program rows (warm-up plays, activation offer, owners); 90-day plan for the top five accounts; weekly standup roster and agenda. Worked example: CG Capital LP program (compliance-flagged) and/or the Sell-Out Files retrofitted into tiers.
- Template 13 — Motion Stack Canvas (Lesson 3.8): primary/secondary/experimental blocks with justification and interlock statements; Growth Code stage-coverage map; per-motion owner + hours + budget + minimum-effective-dose + capacity check; two-quarter sequencing row; kill criteria; the single motion scorecard. Worked example: one full OpCo row from the 3.8 table, expanded.
(Also referenced but already built: Templates 1–7 from Module 1; Templates 8–10 specified in Module 2. Lessons 3.6 and 3.7's ledger and partner map are simple enough to live as sections inside Template 13's workbook page or as lightweight standalone sheets — builder's choice.)
New Glossary Terms Introduced (Extend the Glossary)
Motion-market fit (3.1 — a motion matched to buying behavior, economics, assets, and time-to-signal) · time-to-signal (3.1) · motion stack (3.1/3.8 — primary, secondary, experimental) · 1:1 / 1:few / 1:many (3.2 — ABM tiers) · engaged account (3.2 — the ABM unit of measurement, per written definition) · account intelligence (3.2) · warm path (3.2/3.5) · synthetic swap test (3.5 — if the message reads identically to the next account, it fails) · trigger play (3.5 — public signal → useful response within an SLA) · relationship ledger (3.6) · give-first cadence (3.6/3.7) · hosted room (3.6 — teach, don't table; convene, don't attend) · partner activation (3.7) · productized entry point (3.7 — services PLG) · interlock (3.8 — each motion lowering another's cost) · peanut-buttering (3.8 — the resource-allocation failure) · (Module 2's minimum effective dose and air cover recur here at motion scale.)
Sources drawn on in this module (see framework doc for full lineage): Maja Voje — GTM Strategist (motion selection as resource allocation, beachheads; PDF + checklist in the resource library); Andrei Zinkevich / Full-Funnel — full-journey ABM, tiering, engaged accounts (+ HubSpot ABM Blueprint in the library); April Dunford — positioning underneath any motion (Obviously Awesome, Sales Pitch); Marcus Sheridan — They Ask, You Answer (the inbound engine); Dave Gerhardt — Founder Brand, Exit Five (founder-led B2B); Alex Hormozi — $100M Leads (warm-to-cold outbound, lead-magnet bar, offer ladders); People-first GTM Model Workbook (resource library) — Lesson 3.6; Ehrenberg-Bass / LinkedIn B2B Institute — 95:5 (the demand context every motion runs in); Demand Gen Report 2026 — synthetic-outreach penalty (Lesson 3.5's economics).
Rules of the workbook: same as Module 1 — blank canvas + teaching-draft example; plain language; living documents, dated and versioned.
Contents: T11 GTM Motion Selector · T12 ABM Tiering & Program Plan · T13 Motion Stack Canvas
T11GTM Motion Selector
(Lesson 3.1. Score all seven motion families against the four tests. Rule: no evidence, no score. Output: 2–3 ranked candidates — Lesson 3.8 / T13 turns candidates into the stack.)
Blank canvas
Inputs on the table before scoring: ICP + tiers (T2) · journey map (T8) · deal economics (LTV, target CAC — T17 when built) · unfair-asset inventory (T1's distinct capabilities).
| Motion family | Buying-behavior fit (1–5 + evidence) | Economics fit (1–5 + evidence) | Asset fit / right to win (1–5 + evidence) | Time-to-signal fit (1–5 + evidence) | Growth Code stages covered | Survives? |
|---|---|---|---|---|---|---|
| ABM (3.2) | ||||||
| Inbound / content-led (3.3) | ||||||
| Founder / personality-led (3.4) | ||||||
| Outbound (3.5) | ||||||
| Community / relationship / event (3.6) | ||||||
| Channel / partner-led (3.7) | ||||||
| Product-led / productized entry (3.7) |
Output block:
- Ranked surviving candidates (2–3): TBD
- The primary-motion sentence: "Our primary motion candidate is TBD because that's how our revenue is actually won."
- The kills, named with reasons (the kills are the strategy): TBD
Worked example — CPM owner/association acquisition (teaching draft)
| Motion | Buying | Econ | Asset | Signal | Stages | Survives? |
|---|---|---|---|---|---|---|
| Inbound/TAYA+AEO | 5 — boards genuinely search & ask AI at triggers (T8) | 5 — high-LTV contracts repay the build | 5 — operating-data moat; existing TAYA base | 3 — 2–4 quarters | Attract+Earn | Yes — primary candidate |
| Partner-led | 5 — attorneys/reserve firms sit at the trigger before we do | 5 — near-zero CAC per referral | 4 — existing referrer relationships | 4 — quarters | Attract+Repeat | Yes |
| Outbound (trigger) | 4 — trigger-responsive, public signals | 4 — cheap per play | 4 — public-record watch = free intent data | 5 — weeks | Attract+Win | Yes |
| Event/community | 4 — trust forms in rooms | 3 — real hours cost | 3 — content to teach from | 4 — weeks-to-quarters | Attract+Earn | Yes — experimental |
| ABM | 3 — universe finite but too large to 1:1 at 300 accounts | 3 | 3 | 2 | — | Marginal — tiering logic borrowed, full program no |
| Founder-led | 3 — boards follow topics more than people | 4 | 3 — CPM lead's voice early | 2 | Attract | Supporting only |
| Product-led | 4 — assessment/calculator fits self-educators | 4 | 5 — data-fed tools un-fakeable | 3 | Earn+Win | Yes — as conversion machinery, not standalone |
Output: Primary candidate — inbound/TAYA+AEO ("our revenue is actually won by being the trusted, cited answer at the trigger moment"). Secondaries — partner-led, trigger outbound. Kills: broad paid (finite universe), full ABM (economics per account don't demand it), founder-led as primary (buying behavior).
T12ABM Tiering & Program Plan
(Lesson 3.2. Full-journey account programs, not ads-by-company-name. Gate: if you can't staff the weekly standup, cut the list until you can.)
Blank canvas
Part A — the tiered list
| Tier | Accounts (named) | Selection rationale (mandate fit × warm-path quality × trigger horizon) |
|---|---|---|
| 1:1 (bespoke plans, ~5) | ||
| 1:few (clustered plays, 5–15/cluster) | ||
| 1:many (programmatic air cover) |
Part B — the "engaged account" definition (the unit of measurement; write it so two people score identically)
An account is engaged when: TBD (e.g., ≥2 committee members with meaningful activity — content consumed, event attended, reply received — within 60 days).
Part C — program per tier
| Tier | Warm-up plays (air cover, founder content, rooms) | Activation offer (entry rung, T4) | Owner |
|---|---|---|---|
| 1:1 | |||
| 1:few | |||
| 1:many |
Part D — 90-day plan, top five accounts
| Account | Committee intel (names, fears, warm paths) | Next 3 moves | Owner | Date |
|---|---|---|---|---|
Part E — the standup: weekly · roster (marketing + sales, named): TBD · agenda: per account — what happened, what's next, who owns it. No standup = ABM theater.
Worked example — CG Capital LP program (teaching draft — every external element compliance-reviewed before use)
A: ~30 named allocators. 1:1 — five family offices/institutions with mandate fit + warm paths via [named relationships]. 1:few — fifteen clustered by investor type (family office / small institutional / HNW network). 1:many — the remainder. B: engaged = a named decision-maker has (a) attended a briefing or dinner, or (b) requested the market thesis, or (c) held a substantive conversation with Michael/Alex within 90 days. C: warm-up — Michael's market POV in their feeds; the operating-data-fed market-thesis briefing; dinner-briefing cadence (3.6). Activation — bespoke market-thesis session per 1:1 account (value before any raise conversation). D: [five named accounts, three moves each — mandate research → shared-room appearance → thesis session offer]. E: capital + marketing, one standup, one list. Note: no "lead gen" exists for institutional capital — only named relationships, systematically earned.
T13Motion Stack Canvas
(Lesson 3.8 — the Module 3 exit artifact and a direct Module 9 input. Present it to your president and Michael; defend the sacrifices out loud.)
Blank canvas
| Block | Your answer |
|---|---|
| Primary motion | TBD · Justification sentence: "Most of our revenue is actually won by TBD, therefore it gets the majority of resource." |
| Secondary motion 1 | TBD · Interlock statement: "It feeds/converts the primary by TBD." |
| Secondary motion 2 (optional) | TBD · Interlock: TBD |
| Experimental (max 1) | TBD · Kill date: TBD · Signal that promotes it: TBD |
| Stage-coverage check | Differentiate ⬜ Attract ⬜ Earn ⬜ Win ⬜ Repeat ⬜ — gaps filled by adjusting the stack, not by wishing |
| Dose & capacity (per motion) | Owner · hrs/wk · budget · minimum effective dose · capacity check — cut until true |
| Two-quarter sequence | What starts now (conversation motions) · what builds in parallel (compounding motions) · what waits (paid amplification — after proof) |
| Kill criteria & review dates | Per motion — leading indicators honored in both directions (no early kills, no zombie extensions) |
| The single scorecard | Leading + lagging metric per motion, on one page (feeds T16) |
Worked example — CPM stack, expanded from the 3.8 table (teaching draft)
| Block | Answer |
|---|---|
| Primary | Inbound/TAYA + AEO. "Most of our revenue is won by being the trusted, cited answer at the board's trigger moment — content, citations, and the letter get the majority of hours." |
| Secondary 1 | Partner-led referrer network. Interlock: "Content arms the partners — the attorney forwards our switching guide; the co-hosted briefing fills their client-development need and our room." |
| Secondary 2 | Trigger outbound. Interlock: "Public-record triggers time the outreach; the Big-5 artifacts are the give; the assessment converts it." |
| Experimental | Board-education event series. Kill date: session 3. Promotion signal: ≥15 ICP attendees/session + ≥3 assessments within 60 days. |
| Coverage | Attract ✔ (AEO, partners) · Earn ✔ (answers, letter, events) · Win ✔ (assessment → Turnaround) · Repeat ✔ (reviews feed citability) · Differentiate ✔ (published-numbers POV runs through all of it) |
| Dose | Content+AEO: [owner], 12 hrs/mo · Letter: [owner], 8 hrs/mo · Partners: [owner], 4 hrs/wk · Outbound: [owner], SLA-staffed · Events: [owner], 10 hrs/mo — capacity math attached, at ≤100% |
| Sequence | Now: partner cadence + trigger outbound (weeks-to-signal). Building: content/AEO + letter (quarters). Waits: any paid beyond capped trigger-query search. |
| Kill/review | Events per above; AEO reviewed at quarterly citability audit; partner program reviewed at reciprocity balance ≥ [X] referrals/half. |
| Scorecard | Leading: citability trend, list growth, referrer intros/mo, trigger-response SLA held. Lagging: assessments, proposal win rate, CAC per motion. |
Cross-references: T11 consumes T1/T2/T8 and feeds T13 · T12 consumes T2's Tier-1 list · T13 feeds T15 (calendar), T18 (budget), and T24 (growth plan). Sources: Voje (selection as resource allocation, beachheads); Zinkevich/Full-Funnel + HubSpot ABM Blueprint (T12); Ries (sacrifice — the kills are the strategy).
Where Strategy Becomes Shipped Work
Campaigns, plays and execution — where strategy becomes shipped work.
Module brief
CHARLESGATE Growth Code Academy · Module 4 of 9 · Status: COMPLETE
Growth Code linkage: This module operationalizes ATTRACT + EARN + WIN at the execution layer. Modules 1–3 made the choices: position, ICP, message, offers, channels, motion stack. Module 4 is where choices become shipped work — campaigns with briefs, plays with owners, creative with a bar, conversion paths without leaks, and a calendar the team can actually keep. Strategy that doesn't ship is a document; this module is the shipping department.
By the end of this module you can: trace any piece of marketing work up the hierarchy to the strategy it serves — and kill the orphans · write a campaign brief that forces the thinking before the spending · turn anything that worked twice into a documented play anyone can run · hold a creative bar that survives the AI-average flood · audit a conversion path for friction and fix the leak before asking for more traffic · and run an annual → quarterly → monthly → weekly cadence with capacity honesty.
How to use this module: One lesson per week for six weeks, or a two-day intensive. Lessons 4.1–4.2 are sequencing discipline; 4.3–4.5 are craft; 4.6 is the operating system that holds it all. You will need your Module 1–3 artifacts — especially the Messaging Doc (Template 3), Offers (Template 4), Campaign Brief (Template 5), Channel Plan (Template 6), and Motion Stack Canvas (Template 13). Execution without those inputs isn't execution; it's improvisation with a budget.
A note on examples: CHARLESGATE examples are illustrative teaching drafts — directionally right, but every number, claim, and OpCo mapping must be validated before external use.
4.1The Hierarchy: Strategy → Motion → Campaign → Play → Tactic
First principles
Lesson 1.1 introduced the chain; this lesson makes it load-bearing. Precise definitions, because sloppy vocabulary produces sloppy work:
- Strategy — the standing choices: who (ICP), why us (position), where to play (market frame). Changes rarely; reviewed annually.
- Motion — a repeatable approach to acquiring customers, chosen and stacked in Module 3. Changes rarely; reviewed quarterly against leading indicators.
- Campaign — a time-boxed push with one objective, one ICP, one Growth Code stage, a budget, and a success metric. Weeks to quarters. Campaigns live inside motions: the Sell-Out Files is a campaign inside CRG's ABM motion.
- Play — a documented, repeatable sequence with a trigger, steps, an owner, and an SLA. Plays are standing capability: the failed-inspection response, the referral ask at closing, the review-generation sequence. Campaigns end; plays run forever until retired.
- Tactic — a single action: this post, this email, this event. The atom of execution.
The structural rule: every layer inherits from the one above. A tactic serves a play or a campaign; a campaign serves a motion and a stage; a motion serves the strategy. Work that can't state its parent is an orphan tactic — and orphan tactics are how marketing budgets die: individually defensible, collectively incoherent.
Why it matters
"Let's do a webinar" is the most expensive sentence in B2B marketing — not because webinars are bad, but because it's a tactic in search of a strategy, proposed at the wrong end of the chain. Approve it and you've spent budget, hours, and team focus on something no one can evaluate, because no one said what it was for. Multiply by a year of enthusiastic bottom-up proposals and you get the familiar wreckage: a busy team, a full calendar, no compounding, and a leadership meeting where nobody can answer "what's working?"
The hierarchy is also the delegation architecture this program exists to build. When the layers are explicit, Michael and the presidents govern at the strategy/motion layer, marketing leads own campaigns, and anyone on the team can run a play — without every decision escalating. Confusion about altitude is why founders end up approving social posts. Clarity about altitude is how they stop.
How it works
The tracing test, applied to any proposed or in-flight work — five questions up the chain:
- What tactic is this? (Name the atom.)
- What play or campaign does it belong to? (If neither: orphan. Adopt it into one or kill it.)
- What motion does that campaign serve, and is that motion in our stack (Template 13)? (Work serving a motion we didn't choose is strategy drift wearing overalls.)
- Which Growth Code stage and ICP? (The Lesson 1.1 filter, permanently in force.)
- What metric will say it worked, and when? (No metric, no launch.)
Run the test at two moments: at proposal (the cheap moment — kill orphans before they cost anything) and at quarterly review (the honest moment — kill the orphans that snuck in anyway). Expect the first audit to find 30–50% orphans; that's normal, and the reclaimed capacity is the first dividend this module pays.
CHARLESGATE example
Trace the Sell-Out Files down the full chain (teaching draft). Strategy: CRG new-dev — a sell-out system for 20–150 unit Boston developments, for the ~50 named developers (Template 1 + 2). Motion: ABM, Full-Funnel model — the primary motion from the 3.8 stack. Campaign: the Sell-Out Files — a two-quarter push to make the 50 named accounts know the system exists and accept a pricing study; success = engaged Tier-1 accounts and studies booked. Plays inside it: the trigger play (permit filed → useful contact within 5 days), the roundtable dinner play, the 1:1 warm outreach play (3.5). Tactics inside those: this teardown post, this dinner on the 14th, this note to this principal. Every atom traceable to the strategy — which is exactly why the campaign is reviewable, killable, scalable, and teachable. Now the counter-example: "we should sponsor the spring gala" — trace it. Which campaign? None. Which motion? Unclear. Stage? "Brand?" Metric? Silence. Either adopt it into the relationship motion with a real design (who attends, who owns follow-up, what's the give) or decline. The hierarchy doesn't say no; it says show me the parent.
Do the Work
Inventory every marketing activity currently in flight or committed for your OpCo this quarter — every tactic, event, sponsorship, series. Run the tracing test on each. Output three lists: traced (parent named, keep), adoptable (orphan worth a parent — write the one-line adoption: which campaign/play it joins and its metric), orphans to kill (with the hours and dollars reclaimed, totaled). Bring the totals to the module discussion — the reclaimed-capacity number is usually the most persuasive strategic argument in the room.
4.2The Campaign Brief
First principles
A campaign is a bet: we believe that putting this message in front of this ICP through these channels with this offer will move this stage metric by this much, for this cost. The campaign brief (Template 5, built in the Module 1 workbook — this lesson is its full teaching) is the bet made explicit before the money moves. One page, ten fields:
- Objective — the Growth Code stage being moved and the metric that proves it, with a number and a date.
- ICP + persona — which tier, which committee members (from Template 2). "Everyone" is a rejection.
- The single message — pulled from the Messaging Doc's value themes, never freelanced. One message. Campaigns that carry three messages deliver zero.
- Offer / CTA — what we're asking them to do, from the offer ladder (Template 4). A campaign without a next step is decoration.
- Channels — from the committed Channel Plan (Template 6), with the honest reach math.
- Motion served — which stack entry this belongs to (Template 13).
- Budget + hours — dollars and people-time. Hours are where campaign costs hide.
- Timeline — start, milestones, end. Campaigns end; that's what makes them campaigns.
- Success metric + kill criteria + review date — what proves it worked, what triggers early death, when we decide.
- Owner — one name. Not a team, not a committee. One.
The naming gate (the rule that defines the layer): no objective + number + deadline = not a campaign. It's a content series, a channel, or an activity — name it accordingly. Three things get confused, and confusion is a tax on execution: a phase is the one-time macro sequence of a whole motion (intake → launch → sell-out; linear, spans the engagement); a campaign is a time-bound, goal-bound push that runs within or across phases, several at once, repeatable; a content series is a creative theme — an input to a campaign, not a campaign. A series with no number attached is not a campaign. The campaign is the only layer that is both time-bound and outcome-bound — CG3-style doctrine is timeless, components are timeless, plays are repeatable units; the campaign is where they get pointed at a specific result on a specific date. Without it, the team runs plays as disconnected activity and calls it marketing.
Prove the number is real (the math check, field 1's enforcement): target outcome → assumed conversion rates → implied volume needed upstream → current run rate → the gap this campaign must close. "4 reservations, assuming ~25% tour→reservation, means ~16 qualified tours, means ~120 leads upstream — and our current run rate covers half of that." If the math doesn't hold, the objective is a wish. No approved brief → no assets built, no spend.
Why it matters
The brief's value is only half coordination; the other half is forcing the thinking. Most bad campaigns aren't executed badly — they were never designed. The brief makes design unavoidable: you cannot fill in field 1 without choosing a stage; you cannot fill in field 3 without a Messaging Doc; you cannot fill in field 9 without confronting what failure looks like. Ten fields, and each is a checkpoint where a weak idea dies cheaply instead of expensively.
The brief is also how judgment scales. When the brief is the standard, a president can review five campaigns in twenty minutes and govern the strategy without touching the tactics — and a marketer two years into their career can propose work that gets approved on the merits, because the merits are legible. No brief, and every approval becomes a meeting; every meeting becomes a bottleneck; and the bottleneck's name is usually Michael.
How it works
The lifecycle: draft → red-team → resource check → launch gate → mid-flight review → kill-or-scale.
- Draft in one sitting. If a field won't fill, the campaign isn't ready — that's the brief working.
- Red-team review: one colleague's explicit job is to attack it. Standard attacks: is the metric a vanity metric? Does the message pass the swap test (1.5)? Is the reach math honest for a finite universe (2.6)? Is the timeline compatible with the motion's time-to-signal (3.1)?
- Resource check: hours named against real capacity (Lesson 4.6's math). A campaign staffed by wishful thinking fails at week three and poisons the retrospective.
- Launch gate: owner, president sign-off if budget exceeds the threshold, and the tracking in place before launch — the metric that starts recording after launch is a story, not a measurement.
- Mid-flight review at the halfway milestone against leading indicators — adjust or kill per the written criteria, not per mood.
- Kill-or-scale at the review date. Both outcomes are wins: a killed campaign refunds capacity; a scaled one earns a play (Lesson 4.3). The only losing outcome is the zombie — running because nobody decided. No zombie campaigns burning budget on momentum.
- Bank the pattern. Completed briefs — wins and losses — go into a central library as proven or disproven patterns. Over time, recurring shapes become named archetypes (the New Dev system runs three: Launch, Absorption, Segment/ICP) that pre-fill 80% of the next brief. The archetype library grows from your own evidence, not theory.
CHARLESGATE example
The CPM board-education series, briefed (teaching draft). Objective: Earn — 100 board members from Tier-1/2 associations on the market-letter list and 8 building assessments booked within two quarters. ICP: 20–80 unit Boston-core associations; president + treasurer personas. Message: value theme 2 from CPM's doc — "boards deserve financial transparency they can actually read" — one message, all sessions. Offer/CTA: the free Building & Financials Assessment (Template 4's entry offer). Channels: hosted rooms (3.6) + referrer co-hosting (attorney invites their client boards — the partner motion feeding the campaign) + market letter. Motion: the experimental slot in CPM's stack, auditioning for secondary. Budget/hours: $6K, 10 hrs/month — named owner. Timeline: monthly sessions for six months. Kill criteria: under 15 ICP attendees per session by session three. Review: day 90. Ten fields, one page — and notice that the brief is the argument: reading it, a president can say yes, no, or "fix field 5" in five minutes. That speed is the system working.
Do the Work
Write the Template 5 brief for your OpCo's next real campaign — the one you were going to run anyway. All ten fields; no field left as "TBD." Submit it to a colleague for the red-team pass with the four standard attacks. Revise, then bring both versions to the discussion: the delta between draft one and draft two is the forced thinking, made visible. Standing rule from this day: no campaign launches without a brief. Enforce it kindly and absolutely.
4.3Building Plays: Repeatable, Documented, Owned
First principles
A play is a documented, repeatable sequence with a trigger, steps, an owner, assets, an SLA, and a metric — the unit of institutional memory in a marketing organization. Campaigns are bets; plays are proven bets, promoted to standing capability. The referral ask at peak satisfaction (3.6), the failed-inspection response (3.5), the case-study production sequence after every flagship win — each worked, each will work again, and each dies with the person who invented it unless it's written down.
The first principle underneath: organizations don't compound by working harder; they compound by not re-solving solved problems. A team that documents its wins builds a library that makes every new hire productive in weeks, every campaign cheaper than the last, and every departure survivable. A team that doesn't is permanently re-inventing — talented, busy, and stuck at the same altitude forever. This is the self-serve scaffolding the entire Academy exists to build: the program teaches the concepts; the play library is where the concepts become company property instead of personal knowledge.
The play card format (Template 14), one page, always:
- Name — named things are runnable, referrable, improvable ("the Closing Referral Play").
- Trigger — the event that fires it (a sell-out closes; a permit is filed; a review hits 5 stars; a prospect goes quiet 30 days post-proposal).
- Steps — numbered, checklist-grade, with time stamps ("within 5 business days...").
- Owner + SLA — who runs it, how fast.
- Assets — the templates, links, and approved wording the play draws on (from the Messaging Doc and proof inventory — plays never improvise positioning).
- Metric + run log — what it produces, tracked per run.
Why it matters
Two failure modes make this lesson urgent. First, tribal knowledge evaporation: our best plays currently live in the heads and habits of specific people. Every departure, every OpCo expansion into a new market, every new hire re-learns by osmosis what should have been a document. Second, the campaign-only trap: teams that think exclusively in campaigns rebuild the machine every quarter and wonder why nothing accrues. The healthy structure is a small number of campaigns (bets on this quarter's constraint) running on top of a growing library of plays (the accumulated proven wins). Over three years, the library becomes one of the most valuable assets the marketing function owns — and it's un-copyable, because it's made of what worked here.
The bar for promotion to play: it worked twice, and we can say why. Once is an anecdote. Twice with a mechanism is a pattern. Document the pattern.
How it works
- Harvest candidates quarterly. At the kill-or-scale review (4.2), ask of everything that worked: is this repeatable? What was the trigger? Could someone else run it from a checklist? Also harvest from operations — the best Repeat-stage plays (referral asks, review generation, cross-OpCo triggers) are usually already half-running informally. And harvest from the calendar: two field-tested Attract-stage plays worth cards in every OpCo library — the Market-Moment Capture Play (trigger: a groundbreaking, ribbon-cutting, or client milestone appears on any team calendar → someone attends → photos, a developer/client testimonial captured in the moment ("we're excited to work with CHARLESGATE…"), participation in any planned PR → assets shipped to the content pipeline within a week; good for us and good for the client, which is why they say yes) and the Neighborhood Field Guide Play (trigger: new project or market signed → build the hyperlocal authority asset — the field guide a buyer or owner actually wants — reusable across the sales team, the microsite, and AEO). Both exist because someone scanned a calendar and asked "are we capturing this?" — make the scan itself a habit with an owner.
- Document at checklist altitude. The play card is one page. Ten pages is a manual nobody opens; one page with numbered steps and linked assets is a tool. Write for the person who joins next year, not the person who invented it.
- Assign the owner. A play without an owner is a suggestion. The owner runs it, logs it, and proposes improvements — the play card is versioned, not carved.
- Store centrally, find instantly. One library per OpCo, one house format, indexed by trigger and Growth Code stage. (This library is also AI leverage waiting to happen — Module 8.2 will wire plays into AI-assisted execution, which only works if the plays are written down.)
- Review the library quarterly. Run rates and metrics per play; retire the dead honestly (a retired play is archived with its lessons, not deleted); promote the campaign wins that earned a card.
CHARLESGATE example
The Closing Referral Play (teaching draft), CRG resale. Trigger: closing day plus 14 — the client is settled, satisfaction is peak, the memory is warm. Steps: (1) day 14: the agent's personal note — specific to the deal, no ask; (2) day 21: the review request, direct link, approved wording; (3) day 30: the referral ask, scripted graceful ("the best thing you could do for us..."), plus the give — a neighborhood market snapshot they'll actually forward; (4) log all three in the ledger; (5) any referral received → thank-you within 48 hours, loudly. Owner: each agent; the CRG marketing lead owns the assets and the log. SLA: the day-stamps above. Metric: reviews per quarter, referral conversations per quarter, referral-sourced pipeline. One page. Now note what just happened: the "we appreciate referrals" hope from Lesson 3.6 became a machine with a trigger and a log — and the same card, re-triggered ("sell-out closing + 30 days → CPM management proposal"), is the cross-OpCo flywheel play, which is the single most valuable play card in the entire HoldCo. Write that one first.
Do the Work
Workbook Template 14 (Play Card): document two plays your OpCo already runs implicitly — one Repeat-stage (referral, review, or cross-OpCo trigger), one from any other stage. Full card: name, trigger, steps with time stamps, owner, SLA, linked assets, metric, run log started. Then run each play once this month, per the card, and log it. The gap between "how we described it" and "what running it actually took" is your first version-two edit — plays are living documents, and the first run always teaches.
4.4Creative that Converts
First principles
Creative is the execution layer's differentiation surface — and in 2026 it carries more strategic weight than at any point in the discipline's history, for one structural reason: creative is the targeting (the 2026 finding from Module 2.6, now operationalized). Algorithms distribute; creative selects. The right idea, distinctively expressed, finds the right people — because the right people stop for it. Which means the creative brief is not the decoration on the media plan; it is the media plan's main lever.
And the inverse, the AI-era corollary: average creative is now free, and therefore invisible. Every competitor can generate competent-looking work in seconds. The feed is wallpaper. What stops a board president or a developer mid-scroll is the thing AI can't generate and competitors won't publish: a real number, a named lesson, an honest problem, an opinion that costs something. The house editorial bar from Lesson 2.7 — every piece has a specific, a number, or an opinion that costs something — is not a style preference. It is the conversion mechanism.
Three craft concepts, precisely defined:
- Angle — the strategic way into the message: which value theme, aimed at which persona's fear or ambition, through which frame. One message supports many angles (the treasurer's angle on financial transparency is not the president's).
- Hook — the first three seconds: the line, image, or claim that earns the next ten seconds. Hooks are promises; the body must cash them, or the click costs you trust.
- Earned specificity — the detail only we could write, because it came from our operations. This is earned, not borrowed applied to creative: borrowed creative quotes the industry; earned creative quotes our buildings.
Why it matters
Because distinctiveness compounds and genericness compounds too — in opposite directions. Distinctive creative builds memory structures (Module 6 will go deep); each exposure adds to the last. Generic creative doesn't just underperform, it erases itself — nobody can remember whose ad it was, which means the spend built the category's wallpaper, not our shortlist position. In our finite B2B universes, where the same 50–300 people see everything we make, the compounding is faster and the stakes are higher: we are always either building a distinctive memory or teaching our exact future buyers that we're skippable.
And the commercial real estate B2B creative bar is on the floor (2.7's desert). The arbitrage is still open. It will not stay open forever.
How it works
- Build the angle inventory from the Messaging Doc. Per value theme × per committee persona (Template 2): what does this claim mean to this person's Tuesday? The treasurer's angle on operating data is "financials you can read in ten minutes"; the president's is "your evenings back." Same theme, different doors. Ten angles per theme is a normal harvest.
- Write hooks against the fear or the ambition, with a specific. Formulas that work because they're honest: the counterintuitive stat ("Most Boston condo fees don't pay for what boards think they pay for"); the named mistake ("The pricing error we made on a 60-unit sell-out"); the question they're already asking (Big-5, verbatim); the honest cost ("What switching managers actually costs — including the part nobody bills you for").
- Cash the hook in the body. Structure: hook → the specific (number, story, evidence) → the insight → the next step (offer-ladder rung, when stage-appropriate). A hook the body doesn't cash is clickbait, and our ICPs remember clickbait in the worst way.
- Native per channel, one substance. The messaging-hierarchy logic (1.5) applied to creative: the market report becomes the LinkedIn carousel, the 90-second talking-head video, the dinner-table stat, the ad — re-made per format (2.7's rule: re-make, don't re-paste).
- Review against the bar, in daylight. Every piece, before shipping: Does it have a specific, a number, or an opinion that costs something? Would a competitor publish this? (If yes, it's not differentiated.) Does it pass the swap test? Is the claim in the Messaging Doc, and is the proof real? Two minutes per piece; the discipline is the moat.
- Let performance teach. Organic proves, paid scales (2.6). Track which angles and hooks earn ICP engagement; feed winners back into the inventory. Creative intuition is real, but a run log beats a hunch.
CHARLESGATE example
One claim, two executions (teaching draft). CPM's positioning claim: operational responsiveness, proven. Borrowed version: "CHARLESGATE Property Management — responsive, professional, trusted. Serving Boston associations for 20+ years. Contact us today." Every word true; every word wallpaper; a hundred competitors could run it unchanged — the swap test fails at scale. Earned version: "Last month our average maintenance response across 3,000+ Boston units was 3.2 business hours. We publish this number monthly — because your current manager could, and doesn't. Here's what else boards should demand in writing: [guide]." A number, an opinion that costs something (it commits us publicly, forever — that's why it converts), a Big-5 artifact as the CTA. Same claim; one version is targeting wallpaper, the other picks its reader out of the feed and arms them for the board meeting. The delta between those two is the whole lesson — and the monthly publishing commitment behind it is why creative excellence is ultimately an operations decision, which is the deepest reason it can't be faked.
Do the Work
Pull your OpCo's last five shipped pieces (posts, ads, one-pagers, emails). Score each against the bar: specific/number/costly-opinion (Y/N), swap test, hook honesty, Messaging Doc traceability. Then rewrite the three weakest as earned versions — real numbers from operations (validate them), real lessons, real stances. Ship the rewrites. Then build the start of your angle inventory: two value themes × your top three personas, three angles each. File it with the Messaging Doc; it's now a standing asset every campaign draws on.
4.5Conversion Paths: Landing Pages, CTAS & Friction
First principles
A conversion path is the last meter of the journey: the sequence from attention earned (the click, the scan, the "tell me more") to conversation started (the assessment booked, the study requested, the list joined). It is the narrowest point in the whole system — every upstream dollar and hour funnels through it — which produces the lesson's governing math: fixing a leak at the narrowest point beats adding volume anywhere else. Doubling a landing page's conversion rate doubles the yield of every campaign, motion, and channel that feeds it, forever, for the cost of a redesign. Doubling traffic costs double the budget, once.
Three laws govern the path:
- Message-offer match. The page must be the promise of the click, kept. The visitor from the "what condo management costs" article lands on a page about cost and the assessment — not the corporate homepage with seven navigation choices. Mismatch is the #1 silent leak: the visitor doesn't complain, they just leave.
- One page, one job. Every conversion page has exactly one CTA — the next rung of the offer ladder (Template 4), stage-appropriate. A page asking for three different things converts to none of them. (The corporate homepage is allowed to be a lobby; conversion pages are doors.)
- Friction is the denominator. Hormozi's value equation (1.6): perceived value falls with effort required. Every form field, every unclear next step, every "someone will contact you" vagueness raises the cost of yes. The conversion rate is the value of the offer divided by the friction of the ask — engineer both sides.
Why it matters
Because this is where campaigns quietly die and nobody files a report. The brief was sharp, the creative earned the click — and then the click hit a generic contact form asking for eleven fields and promising nothing, and the board president closed the tab. The campaign retrospective will blame the channel or the creative, buy more traffic, and repeat. Path leaks are invisible in most reporting precisely because they're between the things teams measure.
There's also a trust dimension particular to our categories: a high-stakes B2B buyer reads friction as a preview. A vague form and a slow follow-up whisper "this is what working with them is like." The conversion path is the first operational experience the buyer has of us — Lesson 1.1's law ("everything the market experiences is marketing") at its most literal.
How it works
- Map the paths that exist. For each committed channel and campaign: what happens after the click/scan/reply? Walk each path yourself, as the buyer, on a phone. Most teams have never done this once.
- Check message-offer match per path. The ad's promise, the page's headline, and the CTA must be one continuous thought. Per campaign brief field 3–4: the single message, the single offer, all the way down.
- Apply one-page-one-job. Per entry offer, a dedicated page: the promise, the proof (one strong piece — a number, a named result), what happens next in concrete terms ("you'll get a 40-minute walkthrough and a written summary — no proposal unless you ask"), and the one CTA. Concreteness is risk reversal in copy form.
- Cut friction to the honest minimum. Ask only what the next step needs — usually name, email, building/project. Every additional field must pay for itself in qualification value. And keep the house law: un-gate the answers, gate the tools (2.2) — the path converts because the ungated answers built the trust first.
- Engineer the follow-through. Speed-to-lead is part of the path: the assessment requested Tuesday night and answered Friday afternoon is a different offer than the one answered Wednesday at 9am. Set the SLA (it becomes a Win-stage standard in Module 7.1), and make the confirmation itself useful (the "what to expect" note, the prep checklist — value before the meeting).
- Instrument the two rates. Path conversion (visitor → action) and follow-through conversion (action → conversation held). Review monthly; fix the worst leak first. This is also where the self-reported attribution question lives (2.1) — the path is the toll booth where the dark funnel finally shows its face.
CHARLESGATE example
The First-90-Days Turnaround path, engineered (teaching draft). Entry: the switching-costs article (TAYA, honest, ungated) → in-line CTA: "Get the free Building & Financials Assessment." Page: headline keeps the thought ("Find out what your building's financials are actually telling you — in 30 days, free"); one proof line (a named turnaround result, validated); the concrete what-happens-next (walkthrough → written assessment → board-ready summary; "no proposal unless you ask" — friction and fear, both cut); three fields. Follow-through: confirmation email delivers the board-prep checklist immediately (value before the meeting); assessment call SLA: two business days; "how did you hear about us?" asked and logged verbatim. The before-state, for contrast: "Contact Us — a representative will respond shortly," eleven fields, no promise. Same traffic, same trust upstream; one path converts it, the other donates it to whichever competitor answers faster. CRG new-dev runs the same anatomy at ABM altitude: teardown → sell-out pricing study page → two fields, because at five-deal-a-year stakes, the study is the qualification.
Do the Work
Walk your OpCo's top three conversion paths end to end, on a phone, as the buyer — from the piece that earns the click to the confirmation that follows the action. Score each: message-offer match (Y/N), one-job check (count the CTAs), field count vs. honest minimum, concreteness of what-happens-next, follow-up SLA (measure it — request your own offer and time the response). Fix the single worst leak this month and instrument both rates. Bring before/after to the discussion. If any path ends at a generic contact form, that's your first fix — no exceptions and no feelings.
4.6The Marketing Calendar & Operating Cadence
First principles
Strategy is a set of choices; the calendar is those choices given time slots — and time slots are where they become real or don't. The operating cadence is the system that keeps the whole machine honest, from the annual choice to the Tuesday task:
- Annual — positioning + ICP review per OpCo (the framework's cadence); the year's 2–3 strategic themes; the budget frame (Module 5.4).
- Quarterly — the Growth Code review: stage metrics, constraint diagnosis, and the quarter's campaign slate — 2–3 campaigns per OpCo, aimed at the constraint stage, briefed per 4.2. Motion-stack review against leading indicators (3.8).
- Monthly — the scorecard review (Module 5.5's one-pager): kill/scale calls on campaigns and plays, path-leak review, calendar re-commit.
- Weekly — the execution standup: what shipped, what's blocked, what ships next. Plays run, content ships, pipeline reviewed. Thirty minutes, standing.
Two first principles hold the cadence together. First: out of cadence is out of existence. Work that isn't on a rhythm doesn't get partially done — it silently stops, and nobody notices until the quarterly review finds the gap. Consistency-over-intensity (2.7) is a cadence property, not a personality trait; the calendar is how ordinary teams achieve it. Second: capacity honesty. Every committed item costs hours from a finite pool. A calendar that plans 140% of real capacity doesn't produce 100% — it produces 60%, plus burnout, plus the quiet death of whatever nobody defended. The cadence exists to force the subtraction in daylight, at planning time, rather than by attrition mid-quarter.
Why it matters
Because the alternative isn't "flexibility" — it's the tyranny of the urgent. Without a calendar, marketing becomes a short-order kitchen: whoever asks loudest gets served, compounding work (content, nurture, plays) gets bumped for whatever has a deadline, and the quarter ends with a hundred shipped tactics and no moved stage metric. The calendar is how the important defends itself against the urgent — and in a HoldCo where four OpCos share finite marketing capacity, it's also how the allocation stays a leadership decision instead of a hallway negotiation.
Real estate hands us the annual rhythm for free, and ignoring it is malpractice: leasing season, fall budget season for associations (when boards decide to switch managers), spring annual meetings, development cycles keyed to permitting and construction calendars, investor cycles keyed to fiscal years. The calendar's first draft should be written by the market's clock, then filled with ours.
How it works
Workbook Template 15 (Calendar & Cadence Canvas) structures it:
- Start with the market's calendar. Per OpCo: the seasonal moments when your ICP's attention and triggers peak. Board budget season is CPM's Super Bowl; leasing season is the rental engine's; annual-meeting season fires switching triggers. Mark them first.
- Place the quarter's campaign slate (from the quarterly review): 2–3 campaigns per OpCo, each with its brief, aimed at the constraint stage, timed to the market moments where possible.
- Layer the standing rhythms: the market letter (monthly, non-negotiable — owned-audience assets die of irregularity), the content cadence from the Channel Plan, the play triggers (event-driven, but capacity-reserved), the quarterly instruments (citability audit, library review).
- Run the capacity math, honestly. Hours available per person per week for marketing execution (real hours — after operations, after meetings) versus hours the calendar demands. Over 100%? Cut until true — cut campaigns before cadences (a missed campaign is a lost bet; a broken cadence is a broken system). This is the "cut until it's true" rule from Templates 6 and 13, now applied to time itself.
- Protect the compounding lines. When something must give mid-quarter — and something will — the kill order is written in advance: experiments die first, then campaign scope, then never the standing cadences (letter, content, plays). Compounding work is precisely the work that feels safest to skip and costs most to skip. Write the order down at planning time, when you're wise, not mid-crisis, when you're not.
- Review and re-commit monthly. The calendar is a living instrument: kill/scale per the scorecard, absorb the learnings, re-run the capacity math. A calendar nobody updates is a calendar nobody follows.
CHARLESGATE example
CPM's year, sketched by the market's clock (teaching draft). August–October (budget season): the Earn/Win peak — board-education sessions at maximum cadence, the "what management should cost" content refreshed and promoted, assessment capacity staffed up, trigger-outbound SLA tightened (boards deciding budgets are boards comparing managers). November–January: the market letter's flagship issues (year-in-review data — citation magnet, per 2.5); case-study production from the year's wins (Repeat feeding Differentiate); annual positioning review. February–April (annual-meeting season): switching-trigger peak — the turnaround offer front and center, referrer co-hosted briefings, speed-to-lead at its sharpest. May–July: leasing-season content for the rental side; the experimental slot runs (kill-dated); library and play maintenance. Standing throughout: letter monthly, two posts weekly per the Channel Plan, plays on triggers, scorecard monthly, standup weekly. Capacity-checked at planning: the calendar above was cut from a first draft that planned 130% — the cut list is stapled to the canvas, which is exactly where dead ideas belong: visible, chosen, and revisitable, instead of secretly starved.
Do the Work
Workbook Template 15 (Calendar & Cadence Canvas): build next quarter's calendar for your OpCo. Requirements: market-moments row filled first · max 3 campaigns, each with a Template 5 brief · standing cadences with owners · play triggers reserved · capacity math shown, at or under 100% with the cut list attached · kill order written · monthly review dates named. Present it at the quarterly review and defend the cuts out loud. The calendar you can defend under "why isn't X on here?" is the first one that's real — and "because we chose Y with our finite hours" is a complete sentence.
Module 4 Exit Checklist
You're done with Module 4 when your OpCo has, on paper and reviewed:
- Tracing-test audit of all in-flight work: traced / adopted / killed lists, with reclaimed hours and dollars totaled (4.1)
- A Template 5 campaign brief for the next real campaign — all ten fields, red-teamed, with kill criteria and a review date; "no brief, no launch" adopted as standing rule (4.2)
- Two Play Cards documented, run once per the card, and logged — including one Repeat-stage play (4.3 / Template 14)
- Last five shipped pieces scored against the creative bar; three rewritten with earned specifics and shipped; angle inventory started and filed with the Messaging Doc (4.4)
- Top three conversion paths walked, scored, and instrumented; worst leak fixed; follow-up SLA measured and set (4.5)
- Next quarter's Calendar & Cadence Canvas: market moments, ≤3 briefed campaigns, standing cadences with owners, capacity math ≤100% with the cut list attached, kill order written (4.6 / Template 15)
These artifacts are the execution machinery that Module 5 will instrument and budget — and the operational core of your Module 9 capstone's 90-day sprint.
New Workbook Templates This Module Calls for (Build Next)
- Template 14 — Play Card (Lesson 4.3): one-page standing format — name, trigger, numbered time-stamped steps, owner + SLA, linked assets, metric, run log. Include two worked examples: the Closing Referral Play (CRG resale) and the cross-OpCo flywheel play (sell-out closing → CPM proposal trigger).
- Template 15 — Calendar & Cadence Canvas (Lesson 4.6): market-moments row per OpCo; quarterly campaign slate (max 3, brief-linked); standing cadences with owners; play-trigger capacity reserve; capacity math block (hours available vs. demanded, cut list attached); written kill order; monthly review dates. Include the worked CPM seasonal example.
(Template 5 — Campaign Brief — was built in the Module 1 workbook; Lesson 4.2 is its full teaching. The angle inventory from 4.4 lives as a section appended to Template 3's Messaging Doc rather than a standalone template.)
New Glossary Terms Introduced (Extend the Glossary)
Orphan tactic (4.1 — work that can't name its parent campaign, play, or motion) · tracing test (4.1) · red-team review (4.2) · kill criteria / kill-or-scale review (4.2) · zombie campaign (4.2 — running because nobody decided) · play / play card (4.3 — trigger, steps, owner, SLA, assets, metric) · run log (4.3) · angle (4.4) · hook (4.4) · earned specificity (4.4 — the detail only our operations could produce) · conversion path (4.5) · message-offer match (4.5 — formalized from 3.3) · one page, one job (4.5) · speed-to-lead (4.5 — formalized; owned jointly with Module 7.1) · capacity honesty (4.6) · kill order (4.6 — the pre-written mid-quarter sacrifice sequence) · market-moments calendar (4.6)
Sources drawn on in this module (see framework doc for full lineage): April Dunford — messaging discipline underneath all creative and briefs; Alex Hormozi — value equation applied to conversion friction ($100M Offers); Gary Vaynerchuk — native formats, document-don't-create (4.4); Binet & Field — creative's role in effectiveness; Demand Gen Report 2026 — creative-as-targeting, synthetic-content penalty; Marcus Sheridan — They Ask, You Answer (conversion paths built on ungated trust); Startup Content Planning Workbook (CHARLESGATE resource library) — calendar and cadence structures (4.6); Al Ries — law of sacrifice, applied to calendars and capacity.
Rules of the workbook: same as Module 1 — blank canvas + teaching-draft example; plain language; living documents, dated and versioned.
Contents: T14 Play Card · T15 Calendar & Cadence Canvas (Template 5 — Campaign Brief — lives in the Module 1 workbook; Lesson 4.2 is its full teaching.)
T14Play Card
(Lesson 4.3. One page, always. Promotion bar: it worked twice and we can say why. A play without an owner is a suggestion.)
Blank canvas
| Field | Your answer |
|---|---|
| Play name | |
| Growth Code stage + motion served | |
| Trigger (the event that fires it) | |
| Steps (numbered, checklist-grade, time-stamped: "within X business days…") | 1. 2. 3. |
| Owner + SLA | |
| Assets (linked templates + approved wording — from the Messaging Doc; plays never improvise positioning) | |
| AI column (per step: AI does / human does / human reviews — per T23) | |
| Metric + run log location | |
| Version + last-run lessons |
Worked example 1 — The Closing Referral Play (CRG resale) (teaching draft)
| Field | Answer |
|---|---|
| Name | The Closing Referral Play |
| Stage/motion | Repeat → feeds Attract · relationship/sphere motion |
| Trigger | Closing day + 14 (settled, satisfaction peak, memory warm) |
| Steps | 1. Day 14: agent's personal note — specific to the deal, no ask. 2. Day 21: review request, direct link, approved wording. 3. Day 30: scripted graceful referral ask + the give (neighborhood market snapshot worth forwarding). 4. Log all touches in the ledger. 5. Any referral → thank-you within 48 hrs, loudly. |
| Owner/SLA | Each agent runs; CRG marketing lead owns assets + log. Day-stamps above are the SLA. |
| Assets | Note template · review wording · ask script · snapshot template (all T3-derived) |
| AI column | Snapshot data assembly: AI does · note + ask: human does · logging: AI-assisted |
| Metric | Reviews/qtr · referral conversations/qtr · referral-sourced pipeline |
Worked example 2 — The Cross-OpCo Flywheel Play (teaching draft — the single most valuable card in the HoldCo)
| Field | Answer |
|---|---|
| Name | Sell-Out → CPM Handoff Play (pattern repeats for AFF and CG Capital variants) |
| Stage/motion | Repeat → the HoldCo's structurally uncopyable motion |
| Trigger | CRG sell-out closing recorded in CRM (closed-won event fires the task — 7.4's trigger rails) |
| Steps | 1. Within 5 days: CRG lead's warm intro of CPM to the developer/association (approved wording). 2. Within 30 days: CPM management proposal delivered, informed by the project's actual specs. 3. Parallel: AFF case-study request at peak satisfaction; CG Capital relationship note logged. 4. All three logged against the relationship, not the deal (relationship LTV, T17). |
| Owner/SLA | Trigger task auto-assigns: CPM BD lead (30-day proposal clock) · CRG lead owns the intro · [HoldCo owner] audits monthly |
| Assets | Intro wording · CPM new-building proposal template · case-study request script |
| AI column | Proposal first-draft from project specs: AI does · the intro and every client touch: human does |
| Metric | Attach rate (clients using 2+ OpCos) · trigger-to-proposal SLA held · flywheel-sourced revenue |
T15Calendar & Cadence Canvas
(Lesson 4.6. The market's clock first, then ours. Rule: cut until the capacity math is true — cut campaigns before cadences.)
Blank canvas
Part A — market moments (fill first; real estate hands us the rhythm)
| Quarter | The ICP's seasonal moments (attention + trigger peaks) | What they demand of us |
|---|---|---|
Part B — the quarter's campaign slate (max 3, from the quarterly review; each has a T5 brief)
| Campaign | Stage aimed (constraint?) | Brief link | Owner | Timing vs. market moment |
|---|---|---|---|---|
Part C — standing cadences (funded before campaigns; these never break)
| Cadence | Frequency | Owner | Non-negotiable? |
|---|---|---|---|
| Market letter / owned-audience vehicle | Monthly | Yes | |
| Content cadence (per Channel Plan) | Yes | ||
| Play triggers (capacity reserved) | Event-driven | Yes | |
| Quarterly instruments (citability audit, library review, kit review) | Quarterly | Yes | |
| Scorecard review (5.5 one-pager) | Monthly | Yes | |
| Execution standup | Weekly, 30 min | Yes |
Part D — capacity math
| Person | Real marketing hrs/wk (after ops + meetings) | Hours the calendar demands | Over/under |
|---|---|---|---|
Total: TBD% of capacity. If >100%, cut here, in daylight. Cut list (attached, visible, revisitable): TBD
Part E — the kill order, pre-written: when something must give mid-quarter: 1. Experiments die first → 2. Campaign scope shrinks → 3. Never the standing cadences.
Worked example — CPM's year by the market's clock (teaching draft)
| Quarter | Market moments | Our response |
|---|---|---|
| Aug–Oct | Board budget season — switching decisions get made | Earn/Win peak: education sessions at max cadence; cost-content refreshed + promoted; assessment capacity staffed; outbound SLA tightened |
| Nov–Jan | Year-end; boards reflect | Letter flagship issues (year-in-review data — citation magnet); case-study production; annual positioning review |
| Feb–Apr | Annual-meeting season — switching triggers fire | Turnaround offer front and center; referrer co-hosted briefings; speed-to-lead sharpest |
| May–Jul | Leasing season (rental side) | Leasing content; experimental slot runs; play/library maintenance |
Slate (Q3 example): Budget-Season Answer Dominance (Earn — constraint) · Referrer Co-Host Series (Attract) · [third slot deliberately empty — capacity]. Capacity: first draft planned 130%; cut list stapled (LinkedIn ads experiment, second data report). Kill order: signed.
Cross-references: T14 cards populate the play library and the sprint plan (T25); T15 consumes T13's stack and T5 briefs, and feeds T18's hours budget. Sources: Lesson 4.3/4.6; Startup Content Planning Workbook (resource library).
The Instrument Panel
Metrics, attribution, CAC/LTV, budgeting, reporting, experiments — the instrument panel.
Module brief
CHARLESGATE Growth Code Academy · Module 5 of 9 · Status: COMPLETE
Growth Code linkage: All five stages — this module is the instrument panel the whole Code runs on. Modules 1–4 built the machine; Module 5 makes it legible: which metrics matter per stage, what attribution can and can't tell us, the deal math that decides what we can afford, how budget follows strategy, reporting that produces decisions instead of dashboards, and an experimentation discipline sized for small teams. The theme throughout: honest approximations beat precise fictions.
By the end of this module you can: build a one-page scorecard with the right metric at the right stage — leading and lagging kept straight · explain why attribution software undercounts our best work and triangulate the truth anyway · compute CAC, LTV, and payback per OpCo and per motion, and use them to set what we can afford · allocate budget across creation/capture and stages, and defend it in a downturn · write the monthly one-pager that narrates cause and forces decisions · and run small experiments with kill dates and honest signal thresholds.
How to use this module: One lesson per week for six weeks, or a two-day intensive. Lessons 5.1–5.2 fix the model; 5.3–5.4 fix the math; 5.5–5.6 fix the ritual. Prerequisites: the Demand/Capture Split (Template 9), self-reported attribution live (2.1), and the Motion Stack (Template 13) — measurement without those is counting without categories.
A note on examples: CHARLESGATE examples are illustrative teaching drafts — directionally right, but every number must be validated against current company data (and QuickBooks/Xero actuals) before decisions are made on it.
5.1The Metrics that Matter (by Growth Code Stage)
First principles
A metric is a proxy for a decision. The only reason to measure anything is that some choice — fund, cut, fix, scale — depends on the answer. Start from the decisions and work backward to the metrics, and you get a one-page scorecard. Start from what the software happens to count, and you get a dashboard nobody can act on.
Two distinctions do most of the work:
Leading vs. lagging. Lagging metrics tell you what happened (revenue, closed deals, CAC); leading metrics tell you what's about to happen (engaged Tier-1 accounts, list growth, entry-offer take-rate, publishing cadence held). Every stage needs both — lagging for truth, leading for steering. The classic failure is managing long-cycle work by lagging metrics alone: content and ABM judged on 90-day revenue always die at exactly the moment they're about to pay (3.1's time-to-signal, now in measurement form).
Signal vs. vanity. A vanity metric moves without anything real moving: impressions, total followers, raw MQL counts, website traffic in aggregate. The test is brutal and simple — what decision would change if this number doubled? If the answer is "none," it's not on the scorecard. Vanity metrics aren't harmless decoration; they're camouflage. They make weak quarters look busy and let the real constraint hide.
The framework doc already names the metrics per stage (read them again now — they were designed for this lesson). The scorecard's job is to select 3–5 per stage, per OpCo — not all of them. An instrument panel with forty gauges is a wall, not a panel.
Why it matters
Because what you measure is what your team optimizes, whether you intend it or not. Put MQL volume on the scorecard and you will get gated content and bought lists — the exact Earn-strangling behavior Lesson 2.2 spent a lesson killing. Put engaged Tier-1 accounts on it and you get ABM discipline. The scorecard isn't a report about the strategy; it's an enforcement mechanism of the strategy — arguably the strongest one you have, because it runs every month without anyone having to argue.
And diagnosis runs on it: the Code's constraint logic (1.2) only works if each stage has honest gauges. "Which stage is constrained? Show me the stage metrics" requires that the stage metrics exist, on one page, per OpCo — that's Template 16.
How it works
Build the scorecard per OpCo, one page, five stage-rows:
- Differentiate: win rate vs. named alternatives · % of deals where we set the criteria · fee/price premium held · message-consistency spot check. (Slow-moving — review quarterly; the rest monthly.)
- Attract: qualified ICP reach (density, not volume) · branded search + direct trend · engaged target accounts · ICP follower density · share of voice on our themes.
- Earn: owned-list growth + engagement · return-visitor/repeat-consumer rate · self-reported attribution mentions by source · % of inbound arriving pre-sold · review volume + rating trend · citability audit trend (quarterly).
- Win: SQL→close win rate · proposal win rate · cycle length · speed-to-lead actuals · discount frequency/depth · pipeline ICP-fit %.
- Repeat: gross + net revenue retention · cross-OpCo attach rate · referral-sourced pipeline · reviews and case studies produced per quarter.
For each chosen metric: current value, target, trend arrow, owner. Then the two panel disciplines: mark each metric leading (L) or lagging (G) — every stage needs at least one of each; and write the decision each metric feeds in a margin note ("if entry-offer take-rate < X for two months → path audit per 4.5"). A metric with no decision attached goes back in the drawer.
CHARLESGATE example
CPM owner-acquisition scorecard, first draft (teaching draft). Differentiate: win rate vs. named national (target: know it at all — most firms can't); premium held without discounting. Attract (L): ICP follower density on the CPM lead's voice; branded search trend; referrer-sourced introductions per month. Earn (L): market-letter list growth from Tier-1/2 associations; "already knew you" rate on assessment calls; review volume trend. Win (G): assessment→proposal rate; proposal win rate; speed-to-lead actual vs. the two-day SLA; cycle length. Repeat (G): net revenue retention; referral pipeline; cross-OpCo attach (associations whose owners also transact with CRG). Fifteen metrics, one page, each with an owner and a decision note. What fell off the panel — total site traffic, impressions, social engagement rate — isn't forbidden; it's just weather (2.7), consulted when diagnosing, never steering the ship.
Do the Work
Workbook Template 16 (Growth Code Scorecard): build your OpCo's one-page scorecard — 3–5 metrics per stage, each with current value (dig it up; the digging is diagnostic), target, L/G tag, owner, and decision note. Apply the vanity test out loud to every candidate. Gate: at least one leading metric per stage, and no metric anyone on the team can't explain in one sentence. This scorecard is the monthly review's agenda (5.5) from now on — build it like you'll live with it, because you will.
5.2Attribution: Useful Lies and Honest Approximations
First principles
Attribution software answers one question: which trackable click preceded the conversion? That is a real answer to a narrow question. The lie begins when it's treated as the answer to a different question: what caused this customer? — because in our categories, cause lives mostly in the dark funnel (2.1): the attorney's mention, the forwarded market letter, the AI answer, the dinner conversation, the two years of posts that made our name feel safe. Software sees the last click of a journey it watched 10% of. Believe it whole, and you will systematically defund the 90% that did the work.
The structural biases, named precisely so they can be corrected:
- Last-touch bias: credit lands on the final trackable step — capture channels (branded search, retargeting, "direct") — which are disproportionately harvesting mechanisms. Attribution software is a machine for making demand capture look like demand creation.
- Trackability bias: what can be measured per-click gets credited; what can't (referrals, rooms, dark social, AI citations) gets zero. Budget follows credit; the unmeasurable starves regardless of contribution.
- Platform self-grading: every ad platform's reporting credits the platform (2.6). Their homework, their grade.
- Window bias: 30/90-day windows amputate long cycles. An 18-month developer relationship attributes to whatever happened in the last quarter of it.
The stance that follows — the module's thesis in one line: **use attribution as a witness, never the judge.** Triangulate multiple honest approximations instead of trusting one precise fiction.
Why it matters
Because attribution errors don't stay in the reporting; they become budget. The predictable spiral (2.2's warning, now mechanized): software over-credits capture → capture gets funded → creation gets cut → two years later the pipeline that creation was quietly filling thins out → CPLs rise → the response is more capture spend → repeat until the well is dry and nobody can say why. Every step was "data-driven." The data was a lie told precisely.
For the HoldCo the stakes concentrate in exactly our best work: the market letter, founder voices, referrer networks, hosted rooms, AEO citations — the entire Earn stage and most of Attract are structurally invisible to software attribution. If the instruments can't see our moat, the instruments must be fixed before they're obeyed.
How it works
The triangulation stack — four witnesses, weighed together:
- Self-reported attribution (2.1, now the star witness): "how did you hear about us?" — open text, asked everywhere, logged verbatim, reviewed monthly, coded into sources quarterly. People name the dark funnel: "our attorney," "been reading your letter for a year," "asked ChatGPT." Systematically biased toward memorable later touches — which is fine; that's a different bias than the software's, which is why the two together beat either alone.
- Software attribution — kept, demoted: useful for capture-channel efficiency (search-ad CPL, page conversion rates), directional for everything else. Never allowed to judge Earn-stage work.
- Aggregate correlation — the honest macro view: branded search trend, direct traffic trend, "already knew you" rate, inbound rate vs. content cadence, engaged-account lift when founder content runs (3.4's crossover metric). No per-click precision; real cause-shaped movement over quarters.
- MER — marketing efficiency ratio (2.6): total revenue ÷ total marketing spend, per OpCo, trended. The bluntest instrument and the hardest to fool. If per-channel numbers all look great and MER is flat, the per-channel numbers are lying somewhere.
Ritual: monthly, read the four witnesses together on one page; quarterly, code the self-reported log and re-weigh the channel narrative. When witnesses disagree, that disagreement is the finding — investigate it rather than picking the flattering witness.
CHARLESGATE example
One CPM signing, four testimonies (teaching draft). Software says: "direct traffic → assessment form." Self-reported says: "our attorney mentioned you, and honestly I'd been getting your market letter for a year — when the elevator failed I already knew who to call." Aggregate says: branded search for CHARLESGATE up 30% year-over-year while letter list grew 40%; referrer-sourced intros steady at 3–4/month. MER says: CPM revenue per marketing dollar improving two years running. Verdict: the attorney relationship (partner motion), the letter (Earn), and the trigger play (outbound) caused this; "direct traffic" merely recorded its final step. Now the budget meeting reads differently: the software-only version would fund search ads and cut the letter; the triangulated version protects the letter, deepens the referrer program, and keeps search at the honest capture ceiling. Same data era, opposite decisions — the delta is the discipline.
Do the Work
Build your OpCo's triangulation one-pager: the four witnesses, current reading each, and one paragraph reconciling them into a channel narrative you'd defend. Prerequisite check: if self-reported attribution isn't live and logged (2.1's assignment), stop and fix that first — it's the load-bearing witness. Then find one place where software attribution and self-reported disagree materially, investigate, and write the three-sentence finding. Bring it: the disagreements are where the real channel map lives.
5.3CAC, LTV & Payback: The Deal Math
First principles
Three numbers govern what any acquisition strategy is allowed to cost:
- CAC (customer acquisition cost): total sales + marketing cost to win a customer. Compute it blended (all spend ÷ all new customers — the honesty check) and per-motion (what does an ABM-won developer cost vs. an inbound-won association? — the steering wheel). Include people-hours, not just media; hours are most of our spend.
- LTV (lifetime value): gross-margin profit a customer relationship produces over its life. Not revenue — margin. And in a HoldCo, computed two ways: single-OpCo LTV and relationship LTV across OpCos, because the second number is the strategic one.
- Payback period: months until a customer's margin repays their CAC. The cash-flow reality check — a company can be LTV-rich and die of payback, especially one funding growth from operations. In an EBITDA/FCF-first year, payback is not the third metric; it's the first.
The working heuristics: LTV:CAC ≥ 3:1 for a healthy motion (below it, the motion is a treadmill; wildly above it, you're likely under-investing in growth), and payback tolerance set by the balance sheet, not by ambition. Heuristics, not laws — but you need a written number to deviate from deliberately.
Why it matters
Because deal math is what makes motion choices decidable instead of debatable (3.1's economics test, now with its full instrument). "Can CPM afford ABM-grade acquisition?" isn't a matter of taste: multi-year management contracts with renewal odds produce LTV that affords real per-account investment. "Can resale brokerage afford it?" No — per-deal economics demand cheap-per-acquisition motions (sphere, referral). The math already shaped the 3.8 stacks; this lesson makes every future stack argument quantitative.
And the HoldCo twist is where the math gets strategic: cross-OpCo attach transforms allowable CAC. A developer relationship worth one sell-out justifies $X of pursuit; the same relationship worth sell-out + management contract + AFF retainer + capital participation justifies a multiple of $X — which means the flywheel isn't just a Repeat-stage nicety, it's a pricing advantage in acquisition: we can rationally outspend any single-line competitor for the same relationship, because we harvest more of it. Almost nobody in our market can run that calculation. It's ours.
How it works
Workbook Template 17 (Unit Economics Worksheet), per OpCo (and per major line within CRG):
- Compute LTV honestly: average annual gross margin per client × average retention years (use real churn, not hoped churn) + expansion revenue margin. Flag every estimated input — the flags are the follow-up work with Arturo's team.
- Compute blended CAC from last year's actuals: all marketing + sales cost (media, tools, hours × loaded rates) ÷ new clients won.
- Compute per-motion CAC where the data allows: tag wins by primary source motion (self-reported + CRM source), divide motion cost by motion wins. Imperfect tagging beats no tagging; improve it quarterly.
- Compute payback per OpCo and per motion: CAC ÷ monthly gross margin per client.
- Set the allowable-CAC line: LTV ÷ 3 as the default ceiling per motion, adjusted for payback tolerance. Then audit the motion stack against it — any motion whose realistic per-account cost exceeds allowable CAC is either killed or must claim the relationship-LTV exception explicitly (cross-OpCo attach math shown, not gestured at).
- Re-run annually; sanity-check quarterly. These numbers steer budget (5.4) and defend or convict motions (3.8's review).
CHARLESGATE example
Four OpCos, four maths (teaching draft — every number illustrative). CPM: say ~$30K annual margin per association × 6-year average retention ≈ $180K LTV → allowable CAC ≈ $60K in principle; in practice payback discipline and finite-universe reality set spend far lower — the real finding is that CPM can afford serious per-account investment (content, events, referrer cultivation) and is probably under-spending, not over. CRG resale: per-transaction margin, episodic repeat → LTV per client modest → CAC must be low → sphere/referral motions aren't a preference, they're the only math that works. AFF: retainer + project LTV moderate-to-high, expansion-heavy → founder/content-led (cheap, compounding) primary is math-confirmed. CG Capital: relationship LTV potentially enormous, cycle long, payback slow → affords bespoke everything but strains cash-flow patience — a raise-stage reality the HoldCo budget must carry knowingly. And the flywheel line: a developer at sell-out + management + AFF + capital attach isn't a $X-LTV client, it's several multiples of that — the number that justifies the roundtable dinners, the bespoke studies, and the patience. Put the real figures in with finance; the shape of the argument survives contact with the actuals.
Do the Work
Workbook Template 17 (Unit Economics Worksheet): complete it for your OpCo with finance's help — LTV (flag estimates), blended CAC from actuals, per-motion CAC where taggable, payback, allowable-CAC line, and the motion-stack audit against it. Deliverable includes one written judgment: which motion is the math telling us to feed, and which to question? If any input required a guess, log the guess and the plan to replace it — the worksheet's flags are next quarter's finance-marketing agenda.
5.4Budgeting: Brand vs. Demand, 60/40 in the Real World
First principles
A budget is strategy expressed in dollars — the only document where stated priorities and actual priorities are forced to match. The allocation logic runs top-down, inheriting everything the program has built:
- Set the envelope per OpCo: % of revenue benchmarked to growth ambition and stage (aggressive-growth service firms typically run higher; mature lines lower), sanity-checked against the unit economics (5.3) — the envelope should be derivable from target new-client count × allowable CAC. If it isn't, the growth target and the budget are two different strategies wearing one plan.
- Split creation/capture per the Template 9 target ratio — the long-run 60/40 heuristic (Binet & Field, via 2.2/2.6), flexed by lifecycle: new lines may run 40/60 for near-term pipeline; strong-inbound franchises push past 60/40. The written ratio is the discipline; the flex is the judgment.
- Allocate to the motion stack (Template 13): the primary motion gets the majority — that's what primary means (3.8's peanut-buttering law, now in dollars). Secondary funded at effective dose; experimental small and kill-dated.
- Weight toward the constraint stage (Template 7 / the quarterly review): budget concentrated where the diagnosis says the break is — with the standing exception that compounding lines (letter, content cadence, plays) are funded before campaigns, because broken cadences cost more than skipped bets (4.6's kill order, in dollars).
- Hold a reserve (~10%) for triggers and opportunities — real estate hands us unplannable moments; a fully allocated budget can't respond to any of them.
Why it matters
Because the budget is where the demand/capture discipline either becomes real or reverts. Every structural force pushes toward capture: it demos well in software (5.2), it pays inside the fiscal year, and in a downturn it defends itself with a dashboard while creation stands mute. Which is why the protection rule has to be written before the pressure arrives: in a cut, capture flexes down to the honest ceiling and campaigns shrink — the compounding creation lines are last. Cutting the market letter to fund search ads is borrowing from next year at loan-shark rates (2.2), and it's exactly what every under-instructed budget process does by default.
The HoldCo layer adds the allocation question single-OpCo companies never face: shared engines — Michael's voice, the cross-OpCo flywheel plays, house data assets (the market report), the play library and AI infrastructure — benefit every OpCo and belong to none. Fund them as a HoldCo line with named governance, or they'll be quadruple-taxed and quietly starved: four OpCos each assuming someone else is paying for the thing that helps them all.
How it works
Workbook Template 18 (Budget Allocation Canvas) — the HubSpot budget templates in the resource library provide the line-item spreadsheet mechanics; the canvas provides the strategic layer above them:
- Envelope row: per OpCo — % of revenue, derived from target wins × allowable CAC (5.3), stated next to last year's actual for honesty.
- Creation/capture row: the target ratio (Template 9), dollars and hours — hours are half the budget and the half that usually escapes governance.
- Motion rows: allocation per stack entry, primary majority visible, experimental kill-dated.
- Stage-weighting note: this quarter's constraint stage and the dollars aimed at it.
- Shared-engines line: the HoldCo allocation, governed by name.
- Reserve line: ~10%, with the release rule (who can spend it, against what trigger).
- The downturn paragraph, pre-written: if the envelope cuts 20%, here is the exact sequence of what goes — signed now, in daylight, while everyone is calm.
Review cadence: quarterly re-allocation against the scorecard and constraint diagnosis; annual re-derivation from the unit economics. A budget set in January and untouched until December isn't discipline; it's abandonment with a spreadsheet.
CHARLESGATE example
The shape of a CPM budget conversation, run through the canvas (teaching draft). Envelope: derived — target 12 new associations × allowable CAC → the envelope, checked against % of revenue norms; the derivation surfaces immediately that CPM's historic spend was set by habit, not math (most firms' is). Creation/capture: targeted 60/40 — currently running 45/55, so the canvas names the two moves (Template 9): search spend capped at the honest ceiling, surplus into the letter's data flagship and the board-education series. Motions: inbound/TAYA primary takes the clear majority; partner program funded at real dose (the weekly referrer lunches are a line item, not a hobby); trigger outbound cheap but staffed; event series experimental, kill-dated. Constraint weighting: diagnosis says Earn — dollars follow. Shared engines: CPM contributes its share of the market-report build and Michael's voice support, governed at HoldCo. Reserve: held. Downturn paragraph: search flexes to ceiling first, event series pauses second, the letter and content cadence never — signed. That last sentence, pre-agreed, is worth more than the rest of the budget combined, because it's the one that gets tested.
Do the Work
Workbook Template 18 (Budget Allocation Canvas): build your OpCo's canvas for next year (or re-derive this year's): envelope with the wins × CAC derivation shown · creation/capture in dollars and hours · motion allocation with the primary's majority visible · constraint weighting · shared-engine contribution · reserve with release rule · and the downturn paragraph, pre-written and signed by the OpCo president. Present alongside the Template 17 math — a budget that can't show its derivation is a wish list with subtotals.
5.5Reporting that Drives Decisions
First principles
A report is not a record of activity; it is a machine for producing decisions. The test of any reporting artifact: did a resource move because of it — something funded, cut, fixed, scaled, or escalated? A report that produces only awareness is a newsletter. A dashboard that produces only access is furniture.
The failure mode it replaces is the dashboard dump: forty charts, no narrative, no ask — the reader is handed the raw materials of a conclusion and left to assemble it themselves, which they won't, because narrating cause is the analyst's job, not the audience's. Data doesn't speak for itself; that's precisely why reporting is a skill.
The instrument: the monthly one-pager per OpCo, five blocks, always the same shape (sameness is a feature — pattern-trained readers read fast):
- Scorecard deltas (from Template 16): the 5–8 metrics that moved, with trend arrows. Not all metrics — the moved ones.
- The narrative (≤5 sentences): what happened and why we believe it happened — cause, not description. "List growth accelerated after the budget-season content push; assessment bookings lag it by ~6 weeks, as expected" is narrative. "List grew 8%" is a chart with a word count.
- Constraint check: which Growth Code stage is the binding constraint this month, per the evidence — held over from last month or moved, and why.
- Kill/scale calls: the campaign and play decisions per the written criteria (4.2, 4.6) — made or proposed, with the one-line rationale.
- Decisions requested: the asks, named — budget shift, capacity, escalation, sign-off. If this block is empty, the report has no reason to exist this month — say so in one line and save everyone the meeting.
Why it matters
Because the monthly review is where the operating cadence (4.6) either compounds or performs. Run it as a reading of the one-pager with decisions at the end, and twelve months of it equals a strategy that steered — kill/scale discipline applied ~24 times, constraint diagnosis refreshed twelve times, budget corrected quarterly. Run it as a screen-share of dashboards, and twelve months equals twelve meetings.
There's also an altitude function specific to the HoldCo: the one-pagers are how four OpCos' marketing stays governable by people (presidents, Michael) who cannot and should not attend the weekly work. The one-pager is the interface between execution and governance — five blocks, one page, four OpCos, twenty minutes of leadership reading per month. That interface is what "operator-founder to institutional CEO" looks like at the marketing layer.
How it works
- The scorecard is the agenda. No new artifact each month; Template 16 read for deltas. Preparation cost stays low, which is what keeps the ritual alive past quarter two.
- Narrate cause with honest confidence. Use the triangulation stack (5.2) and say which witness supports the claim. Confidence labels are house style: know / believe / guessing — "we know speed-to-lead improved; we believe it's driving the proposal-rate lift; we're guessing on the review-velocity effect." Precision about uncertainty is what makes the narrative trustworthy enough to act on.
- Keep leading and lagging straight in the story. This month's lagging results were caused by work from two quarters ago; this month's leading indicators predict two quarters ahead. Reports that compress the lag mis-assign credit and blame — the reader must always know which era the number belongs to.
- Force the asks into decision grammar: "requesting $X move from search to the letter's data issue, per the capture-ceiling math" — approvable or rejectable in one sentence. Asks that can't be phrased as decisions aren't asks; they're mood.
- Quarterly, zoom out: the quarterly review (4.6) reads three one-pagers plus the motion-stack and budget checks; annually, the whole instrument feeds the positioning review. Same panel, three altitudes.
CHARLESGATE example
A CPM one-pager, October (teaching draft, compressed). Deltas: letter list +9% (budget-season content, per plan) · assessment bookings 6 (target 8) · speed-to-lead 1.8 days ✓ · proposal win rate 58% (↑ from 44% — narrative flag) · citability audit: cited in 4/10 queries (↑ from 2, quarterly). Narrative: budget-season push is performing on Earn (list, citations); Win improved materially after the narrative rebuild — we believe the new proposal story is the cause (know: the timing correlates exactly; guessing: some lift from two easy comps in the mix). Assessment volume is the miss; path telemetry says the leak is downstream of the switching article — friction audit scheduled (4.5). Constraint: Earn→Win handoff, watch one more month before re-diagnosing. Kill/scale: event series passed its session-three gate (avg 19 ICP attendees) — proposing promotion from experimental to secondary at quarter end, with the dose math attached. Decisions requested: (1) approve the event-series promotion + its Q1 budget line; (2) approve 10 hrs for the path audit. Two asks, both decidable before the coffee cools. That's the entire genre.
Do the Work
Write this month's one-pager for your OpCo — five blocks, one page, confidence labels on the narrative, decisions requested in approvable grammar (or the honest "no decisions this month" line). Deliver it at the monthly review and time the meeting: the target is decisions inside thirty minutes. Then make it a play: the one-pager's format, owner, and cadence go on a Template 14 card, because reporting is the one play every OpCo runs forever.
5.6Experimentation: Small Bets, Fast Kills
First principles
An experiment is a bet with a hypothesis, a budget, a clock, and a pre-committed verdict rule. It differs from a campaign (4.2) in intent: campaigns exploit what we believe; experiments buy information about what we don't. The discipline exists because the alternative isn't "no experiments" — it's undeclared ones: the pilot that never ends, the "let's try it" that becomes a standing cost with no verdict, the zombie channel kept alive by sunk cost and one anecdote (2.3's kill-or-scale rule, now given its full machinery).
Small-team truths, stated plainly, because most experimentation writing assumes an e-commerce data volume we will never have:
- We can't A/B test our way to strategy. With 50 developers or 300 associations, sample sizes for statistical significance mostly don't exist. Fine. The alternative to significance isn't vibes — it's minimum detectable signal: define in advance what movement would be big enough to notice above noise and worth acting on ("≥15 ICP attendees per session by session three"; "≥2 study requests from 30 outreaches"). If the pre-committed signal doesn't appear by the kill date, the verdict is no — regardless of how the room feels about the idea.
- Test big differences, not small ones. Button colors need Amazon's traffic; approaches — a new event format, a new entry offer, a new channel, a new angle family — produce signals small samples can read.
- One experiment slot per OpCo at a time (the Template 6/13 rule, held). Experiments are cognitively expensive; parallel ones in one small team contaminate each other's reads and everyone's focus.
Why it matters
Because a team that can't kill cleanly can't explore safely — every "try" becomes a permanent liability, so prudent people stop proposing tries, and the portfolio calcifies. The experiment log flips the incentive: a killed experiment with a written lesson is a successful experiment (the information was bought and banked); only the undecided one is a failure. That reframe — verdicts as wins regardless of direction — is what makes a small team genuinely exploratory without becoming scattered (the "strong convictions, loosely held" posture, given a form to live in).
And the log compounds like the play library does: two years of logged verdicts is an institutional memory of what this market rewards and punishes — un-copyable, and increasingly valuable as AI leverage makes generating options cheap while knowing which options die here stays expensive (Module 8's thesis, arriving early).
How it works
Workbook Template 19 (Experiment Log) — one row per experiment, seven fields:
- Hypothesis in falsifiable form: "we believe [change] will produce [signal] for [ICP] because [mechanism]."
- Stage + metric: which Growth Code stage, which scorecard metric it would eventually move.
- Design: the smallest honest version — cheapest build that gives the mechanism a real chance (a fake-door landing page before a real tool; three hand-run events before a series; ten hand-built outreaches before a program).
- Minimum detectable signal, pre-committed, in numbers.
- Clock: kill date, sized to the mechanism's time-to-signal (3.1) — long enough to be fair, short enough to be safe.
- Verdict: scale (→ campaign brief or play card), kill (→ lesson logged), or extend once with a written reason (extensions beyond one are zombie certificates).
- Lesson: one sentence, written even for scales — especially for scales, because why-it-worked is the transferable part.
Governance: the experimental slot is filled at the quarterly review, verdicts land at the monthly review (5.5's kill/scale block), and the log is read in full once a year — the annual read is where the pattern-level lessons surface.
CHARLESGATE example
Three log rows (teaching drafts). Row 1 — CPM event series: hypothesis — board-education rooms will out-earn content alone for the Tier-1 trigger audience because trust forms faster in person; signal — ≥15 ICP attendees/session by session three, ≥3 assessments within 60 days of any session; clock — session three. Verdict (per 5.5's example): scale → promoted to secondary, campaign brief written. Lesson: co-hosting with referrers was the mechanism — the attorney's invitation, not our topic, filled the room. That lesson now transfers to every OpCo's event thinking. Row 2 — CRG resale consumer AEO: hypothesis — neighborhood answer-content will earn AI citations for buyer queries; signal — cited in 3/10 tracked queries by day 90. Verdict: kill at day 90 (1/10; the aggregators' directory moat is stronger at consumer altitude than B2B). Lesson: consumer AEO needs a data asset, not articles — parked pending the rental-report consumer edition; re-proposable with that asset, and the log says exactly why. Row 3 — AFF productized audit: fake-door test first — a page and ten warm outreaches before any tool is built; signal — 3 requests. The smallest honest version is the discipline: information first, infrastructure after. Three rows, three verdicts, zero zombies — and every future quarterly review inherits the lessons.
Do the Work
Workbook Template 19 (Experiment Log): open your OpCo's log. First entry: audit the current experimental slot — if something is running without a hypothesis, signal, and kill date, retrofit them now or call the verdict now (most inherited "pilots" die honorably at this step, which is the point). Second entry: design next quarter's experiment properly — all seven fields, smallest honest version, signal pre-committed. Then log backwards: the last two "tries" your OpCo ran, with verdicts and lessons, because the log's value starts compounding the day it stops being empty.
Module 5 Exit Checklist
You're done with Module 5 when your OpCo has, on paper and reviewed:
- One-page Growth Code Scorecard: 3–5 metrics per stage, current values dug up, L/G tagged, owners and decision notes attached, vanity test applied out loud (5.1 / Template 16)
- Triangulation one-pager: four witnesses read together, one material software-vs-self-reported disagreement investigated with a written finding (5.2)
- Unit Economics Worksheet: LTV (estimates flagged), blended + per-motion CAC, payback, allowable-CAC line, motion-stack audit, one feed/question judgment written (5.3 / Template 17)
- Budget Allocation Canvas: derived envelope, creation/capture in dollars and hours, primary-motion majority visible, shared-engine line, reserve rule, downturn paragraph pre-signed (5.4 / Template 18)
- This month's one-pager delivered: five blocks, confidence labels, decisions requested in approvable grammar, meeting under thirty minutes (5.5)
- Experiment Log live: current slot retrofitted or verdicted, next experiment designed with pre-committed signal and kill date, two historical tries back-logged (5.6 / Template 19)
These instruments are the panel Modules 6–8 fly by, the budget logic the whole HoldCo plans against, and the evidence base your Module 9 capstone diagnosis stands on.
New Workbook Templates This Module Calls for (Build Next)
- Template 16 — Growth Code Scorecard (Lesson 5.1): five stage-rows × 3–5 metrics, each with current/target/trend/L-G tag/owner/decision note; monthly-review agenda format. Worked example: the CPM draft from 5.1.
- Template 17 — Unit Economics Worksheet (Lesson 5.3): LTV build-up (margin × retention + expansion, estimate flags), blended CAC, per-motion CAC tagging method, payback, allowable-CAC line, relationship-LTV (cross-OpCo) supplement, motion-stack audit block.
- Template 18 — Budget Allocation Canvas (Lesson 5.4): derived envelope, creation/capture split (dollars + hours), motion allocation, constraint weighting, shared-engines line, reserve + release rule, pre-signed downturn paragraph. Pairs with the HubSpot budget spreadsheet templates in the resource library for line items.
- Template 19 — Experiment Log (Lesson 5.6): seven-field rows (hypothesis, stage/metric, smallest-honest design, minimum detectable signal, clock, verdict, lesson), one-slot-per-OpCo governance, annual full read.
New Glossary Terms Introduced (Extend the Glossary)
Leading vs. lagging metric (5.1) · vanity test (5.1 — "what decision changes if this doubles?") · decision note (5.1) · last-touch / trackability bias (5.2) · triangulation stack (5.2 — four witnesses, one narrative) · witness, not judge (5.2 — house stance on attribution software) · blended vs. per-motion CAC (5.3) · relationship LTV (5.3 — cross-OpCo attach economics) · allowable CAC (5.3) · payback period (5.3) · shared engines (5.4 — HoldCo-level assets no single OpCo owns) · downturn paragraph (5.4 — the pre-signed cut sequence) · dashboard dump (5.5) · decision grammar (5.5) · know / believe / guessing (5.5 — house confidence labels) · minimum detectable signal (5.6) · smallest honest version (5.6) · fake-door test (5.6) · zombie certificate (5.6 — the second extension)
Sources drawn on in this module (see framework doc for full lineage): Binet & Field — brand/activation ~60/40, long-run effectiveness evidence (5.4); Ehrenberg-Bass / LinkedIn B2B Institute — 95:5 context for why lagging-only measurement kills Attract-stage work; Andrei Zinkevich / Full-Funnel — dark-funnel measurement, self-reported attribution practice (5.2); Alex Hormozi — LTV:CAC discipline and offer-ladder economics ($100M Offers/Leads); April Dunford — positioning review as the annual instrument; HubSpot budget templates (CHARLESGATE resource library) — 5.4 line-item mechanics; Demand Gen Report 2026 — platform-reporting skepticism, buyer-behavior shifts underlying the triangulation stance.
Rules of the workbook: same as Module 1 — blank canvas + teaching-draft example; plain language; living documents, dated and versioned. Every number below is illustrative — validate against QuickBooks/Xero actuals with finance before any decision rides on it.
Contents: T16 Growth Code Scorecard · T17 Unit Economics Worksheet · T18 Budget Allocation Canvas · T19 Experiment Log
T16Growth Code Scorecard
(Lesson 5.1. One page per OpCo; 3–5 metrics per stage; this IS the monthly review's agenda. Vanity test on every candidate: what decision changes if this number doubles?)
Blank canvas
| Stage | Metric | L/G (leading/lagging) | Current | Target | Trend | Owner | Decision note ("if X for 2 months → Y") |
|---|---|---|---|---|---|---|---|
| Differentiate (review quarterly) | |||||||
| Attract | |||||||
| Earn | |||||||
| Win | |||||||
| Repeat |
Panel disciplines: ≥1 leading AND ≥1 lagging per stage · no metric anyone on the team can't explain in one sentence · what fell off the panel is weather, consulted when diagnosing, never steering.
Worked example — CPM owner acquisition (teaching draft)
| Stage | Metric | L/G | Decision note |
|---|---|---|---|
| Differentiate | Win rate vs. named alternatives | G | If unknown → start logging on every deal (that's the finding) |
| Differentiate | Premium held without discounting | G | Discounting up 2 months → narrative/offer review (7.3/T4) |
| Attract | ICP follower density (CPM lead's voice) | L | Flat 2 quarters → channel-plan review |
| Attract | Branded search trend | L | — memory gauge, annual trend |
| Attract | Referrer-sourced intros/month | L | <2/mo → reciprocity review (3.7) |
| Earn | Letter list growth (Tier-1/2 associations) | L | Off-season sag → content calendar fix (T15) |
| Earn | "Already knew you" rate on assessment calls | L | The pre-sold gauge — brand's dividend |
| Earn | Review volume + rating trend | L | Feeds citability — below play cadence → 4.3 run-log check |
| Win | Assessment → proposal rate | G | Falling → path audit (4.5) |
| Win | Proposal win rate · cycle length | G | Falling → kit/narrative review |
| Win | Speed-to-lead actual vs. SLA | L | Broken 2 weeks → staffing escalation (7.1) |
| Repeat | Net revenue retention | G | — |
| Repeat | Referral-sourced pipeline · attach rate | G | Flat → flywheel play audit (T14) |
| Repeat | Case studies + reviews produced/qtr | L | Behind → proof-engine escalation (6.5) |
T17Unit Economics Worksheet
(Lesson 5.3. Complete with finance. Flag every estimated input — the flags are next quarter's finance-marketing agenda.)
Blank canvas
Part A — LTV build-up
| Input | Value | Estimated? (flag) |
|---|---|---|
| Average annual gross margin per client | ||
| Average retention (years — real churn, not hoped) | ||
| Expansion revenue margin (avg per client) | ||
| Single-OpCo LTV = (margin × years) + expansion | ||
| Relationship LTV (cross-OpCo attach scenario — show the math) |
Part B — CAC
| Input | Value |
|---|---|
| Total marketing + sales cost last year ($ + hours × loaded rates) | |
| New clients won | |
| Blended CAC | |
| Per-motion CAC (tag wins by source motion: self-reported + CRM source; imperfect beats none) | Motion: TBD CAC: TBD · Motion: TBD CAC: TBD |
Part C — payback + the line
| Item | Value |
|---|---|
| Payback (CAC ÷ monthly gross margin per client) | |
| Allowable CAC (LTV ÷ 3 default, adjusted for payback tolerance) | |
| Motion-stack audit: any motion whose realistic per-account cost exceeds allowable CAC? | Kill, or claim the relationship-LTV exception with the math shown |
| The judgment (one sentence): which motion is the math telling us to feed, and which to question? |
Worked example — CPM (teaching draft; all numbers illustrative)
A: ~$30K annual margin/association (flag: estimate) × 6-yr retention (flag: verify churn) ≈ $180K LTV. Relationship LTV: association whose owners transact via CRG + capital projects via network ≈ 1.5–2× (flag: attach data thin — that's a 7.4 finding). B: blended CAC from actuals: $[X]; per-motion: inbound-won ≈ $[low], event-won ≈ $[mid]. C: allowable CAC ≈ $60K in principle; payback discipline sets practical spend far lower. Audit verdict: no motion near the ceiling — CPM is likely under-investing in acquisition. Judgment: "Feed inbound + partners (CAC a fraction of allowable, compounding); question nothing on economics — question capacity instead (T15)."
T18Budget Allocation Canvas
(Lesson 5.4. A budget is strategy expressed in dollars. Pairs with the HubSpot budget spreadsheet templates in the resource library for line items.)
Blank canvas
| Row | Content |
|---|---|
| 1. Envelope | % of revenue, derived: target new clients × allowable CAC (T17) = $TBD · vs. last year's actual: $TBD |
| 2. Creation/capture split | Target ratio (from T9): TBD/TBD · in dollars AND hours |
| 3. Motion allocation | Per T13 stack — primary gets the visible majority; experimental kill-dated |
| 4. Constraint weighting | This quarter's constraint stage (T7): TBD · dollars aimed at it: $TBD |
| 5. Shared-engines line | HoldCo contribution (Michael's voice support, market report, play library/AI infra) — governed by: TBD |
| 6. Reserve | ~10% · release rule (who spends it, against what trigger): TBD |
| 7. The downturn paragraph (pre-written, pre-signed) | "If the envelope cuts 20%, the sequence is: TBD flexes to the honest ceiling first; TBD pauses second; the compounding cadences (letter, content, plays) never. Signed: [president] [date]" |
Review cadence: quarterly re-allocation vs. scorecard + constraint · annual re-derivation from T17.
Worked example — CPM (teaching draft)
- Envelope: 12 new associations × allowable CAC → derived $[X] (finding: historic spend was set by habit, ~40% below derived). 2. Split: target 60/40; currently 48/45/7 (per T9) — two moves named there. 3. Motions: inbound/TAYA majority; partners at real dose (referrer lunches are a line item, not a hobby); outbound cheap but SLA-staffed; events funded as experimental until session-3 gate. 4. Constraint: Earn — the data-report build and letter flagship get the increment. 5. Shared engines: CPM's share of the rental report + voice support, governed at HoldCo (named owner). 6. Reserve: 10%, released by president against trigger opportunities (e.g., a competitor roll-up churning accounts). 7. Downturn paragraph: "Search flexes to ceiling first; event series pauses second; letter and content cadence never. Signed: [Todd], [date]."
T19Experiment Log
(Lesson 5.6. One experimental slot per OpCo at a time. A killed experiment with a written lesson is a success; only the undecided one is a failure.)
Blank canvas — one row per experiment
| # | Hypothesis ("we believe [change] → [signal] for [ICP] because [mechanism]") | Stage + scorecard metric | Design (smallest honest version) | Minimum detectable signal (pre-committed, numeric) | Kill date | Verdict (scale / kill / extend-once + reason) | Lesson (one sentence — written even for scales) |
|---|---|---|---|---|---|---|---|
Governance: slot filled at quarterly review · verdicts land at monthly review (5.5 kill/scale block) · full log read annually — the pattern-level lessons surface there. Extensions beyond one are zombie certificates.
Worked example — three rows (teaching drafts)
| # | Hypothesis | Signal | Verdict | Lesson |
|---|---|---|---|---|
| 1 | Board-education rooms out-earn content alone for Tier-1 trigger audience (trust forms faster in person) | ≥15 ICP attendees/session by session 3; ≥3 assessments within 60 days | Scale → promoted to secondary; campaign brief written | Co-hosting with referrers was the mechanism — the attorney's invitation filled the room, not our topic. Transfers to every OpCo's event thinking. |
| 2 | Neighborhood answer-content earns AI citations for consumer buyer queries (CRG resale) | Cited in 3/10 tracked queries by day 90 | Kill at day 90 (1/10 — aggregator directory moat stronger at consumer altitude) | Consumer AEO needs a data asset, not articles. Parked pending rental-report consumer edition; re-proposable with that asset. |
| 3 | Developers will request a productized marketing audit (AFF) if offered warm | 3 requests from a fake-door page + 10 warm outreaches | (running) | Smallest honest version first: information before infrastructure. |
Cross-references: T16 is the monthly review agenda (5.5) and the capstone's evidence bank (9.1) · T17 feeds T18's envelope and T13's economics test · T18's downturn paragraph pairs with the 6.2 two-clock defense · T19's slot is governed by T6/T13's experiment rule. Sources: Binet & Field (60/40); Zinkevich (self-reported attribution); Hormozi (LTV:CAC); HubSpot budget templates (resource library).
Memory, Distinctiveness & the Assets AI Can't Generate
Brand as memory structures and pre-sold trust — the long game, and the creativity moat.
Module brief
CHARLESGATE Growth Code Academy · Module 6 of 9 · Status: COMPLETE
Growth Code linkage: This module operationalizes DIFFERENTIATE + ATTRACT + REPEAT at their longest time horizon. Positioning (Module 1) chose what we claim; demand (Module 2) taught how buyers buy; brand is the memory layer that makes both cheaper every year — the reason a board president thinks of us before searching, the reason the search results feel like confirmation instead of discovery. It is the least urgent work in this program and the most valuable per dollar over three years, which is exactly why it needs a module: nothing this slow survives without a defense written down.
By the end of this module you can: explain brand as memory structures and mental availability — and stop defending it with vibes · dissolve the brand-vs-demand budget war with the evidence · run the Brand Code and Growth Code as one interlocking system, with a distinctive-asset inventory and voice standards that hold across four OpCos · take a category POV that costs something and pays for it · and argue the AI-era case: distinctiveness, taste, and proof as the un-generatable assets.
How to use this module: One lesson per week for five weeks, or a one-day intensive. This module is deliberately positioned after measurement (Module 5): brand arguments made before a team understands leading indicators and long-horizon math get dismissed as decoration; made after, they read as what they are — the highest-compounding line on the budget. Prerequisites: Positioning Canvas (T1), Messaging Doc (T3), and the existing CHARLESGATE Brand Code materials.
A note on examples: CHARLESGATE examples are illustrative teaching drafts — directionally right, but every claim must be validated (and everything touching the Brand Code reconciled with the canonical Brand Code documents) before external use.
6.1What Brand Actually is
First principles
Strip the logo worship and the agency mystique: a brand is the set of memory structures a buyer holds about you — the associations, feelings, and expectations that fire when they encounter your name, or better, when they encounter their problem. Brand isn't what we say we are; it's what they retrieve when it matters.
The operating science (Ehrenberg-Bass, the same lineage as 95:5) gives us two working concepts:
- Mental availability: the probability we come to mind in a buying situation. Not fame in general — retrieval at the moment of need. Built by consistent, distinctive presence over time, attached to the right cues.
- Category entry points (CEPs): the situations, thoughts, and triggers through which buyers enter the category — "our manager stopped responding," "financing closed, now what," "who actually knows this market," "the board meeting is in three weeks and I need answers." Brands are retrieved through entry points. The strategic act is choosing which entry points to own and attaching our name to them relentlessly — which is why the trigger inventories from Template 2 are secretly a brand document.
And the third concept, the one that makes brand buildable rather than mystical: distinctive assets — the recognizable, ownable elements (name, visual system, voice, recurring formats, named frameworks like the Growth Code itself, even a signature chart style) that let a memory accrue to us instead of leaking into the category. Distinctiveness is not differentiation: differentiation is why choose us (Module 1's job); distinctiveness is knowing it's us at all (this module's job). Confuse them and you get ads that argue brilliantly for the category while the buyer remembers the incumbent.
The house doctrine, in four lines (from "The Brand Gap," our New Dev pre-read — carry these verbatim):
- A brand is not what you say it is. It's what they say it is. You don't own your brand — the buyer does. It's the gut feeling left in their mind after the tour, the ad, the spec sheet, the price. The developer who says "we're luxury" hasn't built a brand; they've made a claim.
- Trust is established — or ruined — in every interaction, not just the brochure, website, or logo. The property manager's response time is brand. The late deliverable is brand.
- Sameness is the most expensive mistake in marketing, because it forces you to compete on price. The brain sorts by difference: "another new luxury condo" is invisible; "the only building that…" is a category of one. The question is never is it good? — it's is it different, and is the difference one this buyer cares about?
- Charisma beats features. A charismatic brand is one for which people believe there's no substitute. Every building has a kitchen; charisma comes from clarity and conviction, not a longer amenity list.
Why it matters
Because in trigger-driven, long-cycle categories — every B2B line we run — the shortlist is drawn from memory before any search begins (2.1's journey evidence). The 95% aren't reading proposals; they're accumulating impressions. When the trigger fires, three names surface, and the firms not among them compete for the leftovers at a discount. Brand is what determines whether we're in the room before the room exists.
Framed in the Code's economics: brand is pre-paid Attract and pre-paid Earn. The board president who's read the letter for a year arrives pre-trusted (Earn, banked). The developer who's seen the absorption teardowns arrives pre-convinced we know the market (Differentiate, banked). Every stage's cost falls when memory has done the early work — which is the compounding claim of the whole flywheel, and brand is its storage medium.
How it works
- Audit the memory that exists. What do buyers retrieve about us today? Sources: self-reported attribution verbatims (what did they say they knew us for), win/loss notes, review language, what referrers actually say when they recommend us (ask them — their sentence is our de facto brand). Expect gaps between our intended position and the retrieved one; the gaps are the work.
- Choose the entry points to own. From the trigger inventories: which 3–5 buying situations, per OpCo, should automatically retrieve us? Prioritize by frequency × ICP value × our right to win.
- Attach relentlessly. Every piece of work — content, events, letters, posts — aims at an owned entry point, in a distinctive wrapper, repeated for years. (This is why the calendar's cadences never break: irregular presence builds no memory. 4.6's law is a brand law.)
- Measure what memory work can be measured: branded search trend, direct traffic, "already knew you" rate, unaided mentions in referrer conversations, share of voice on owned themes (all on the T16 scorecard already — brand's gauges were installed in Module 5 without the word "brand" attached).
CHARLESGATE example
Run the retrieval test on one entry point (teaching draft): a Boston developer thinks "sell-out risk" — what surfaces? For most of the 50-name universe, today, honestly: a big-brand brokerage (default availability), maybe a broker their friend used (relationship availability), and a general anxiety with no attached solution. The Sell-Out Files campaign, the absorption teardowns, Michael's market POV, the roundtables — Modules 2–4 built these as demand machinery, but this is their longest-horizon job: attaching CHARLESGATE to the "sell-out risk" entry point in fifty specific minds, so the trigger retrieves us before any search. Same audit, CPM side: "our manager stopped responding" should retrieve the letter, the published response-time number (4.4's earned specific — which is also a distinctive asset), the attorney's mention. When three independent cues converge on one name, the shortlist of three becomes a shortlist of one wearing two disguises. That's mental availability doing what capture spend never can.
Do the Work
Run the memory audit for your OpCo: pull 20 self-reported attribution verbatims, your last 10 win/loss notes, and 3 referrer conversations ("what do you say when you recommend us?"). Write down: what buyers actually retrieve, versus the Positioning Canvas's intended claim. Then choose the 3–5 entry points to own (from Template 2's triggers), and for each, list what we currently have attached to it and the gap. This audit feeds Template 20 in Lesson 6.3 — hold onto it.
6.2Brand vs. Demand: The False War
First principles
The brand-vs-demand fight is a budget-meeting artifact, not a strategic reality. The two are one system operating on two clocks:
- Demand work (activation/capture) converts existing memory and existing intent into revenue now. Sharp, measurable, fast-decaying.
- Brand work builds the memory and preference that future demand work will convert cheaply. Diffuse, slow, compounding.
Binet & Field's decades of effectiveness data — the closest thing marketing has to actuarial tables — say the two are complements with an optimal mix (~60/40 brand-to-activation as the long-run heuristic, category-adjusted), and that over-rotating to activation produces exactly the pattern we described in 2.2: a sugar-high of measurable wins, then rising acquisition costs as the memory reservoir drains. Activation harvests preference; something has to grow it.
The B2B correction to the old objection ("brand is for consumer companies"): the B2B Institute's research says brand matters more in B2B, not less, because buying moments are rarer (you can't retarget your way into a shortlist you weren't remembered for), risk is career-attached (the safe choice is the known choice — brand is the buyer's insurance), and committees need a name everyone recognizes (the champion's brand shortcut: "even the skeptic had heard of them").
The reconciliation, in Code terms: brand is Attract + Earn run at the years-long horizon; demand is Attract + Win run at the quarters horizon. Same stages, different clocks, one budget — which is why Template 18 forces the split to be written down rather than re-fought every cycle.
And one asymmetry the reconciliation must not soften (the New Dev doctrine, generalized): brand is in service of demand, never the endpoint. A brand that matters is necessary; it is not sufficient. "A beautiful brand with no demand engine is a billboard in the desert." When a budget or a debate forces a rank order, demand outranks brand — because the brand's entire job is to make the demand engine cheaper and the yes easier.
Why it matters
Because the war has a structural aggressor: demand can prove itself in software and brand can't (5.2's trackability bias), so every un-instructed budget process quietly disarms the brand side — and the damage invoices two years later, addressed to someone else. The defense is not passion; it's the instrument panel: leading indicators (6.1's memory gauges), the 60/40 ratio written into Template 9/18, the downturn paragraph pre-signed (5.4), and leadership literacy in the lag (5.5's "which era does this number belong to").
The other casualty of the false war is the work itself: teams that believe the dichotomy build brand work that doesn't convert (pretty, aimless "awareness") and demand work that doesn't brand (generic capture that rents the click and builds nothing). The best work refuses the split — and we have structural advantages in exactly that refusal.
How it works
Build dual-clock work — assets that convert now and deposit memory:
- The letter test case: the market letter converts (assessments booked from it monthly — demand) while every issue deposits distinctive memory (the voice, the data, the honesty — brand). One line item, both clocks. Most of our best machinery is like this; the classification discipline (T9) tags its primary job while acknowledging the second.
- Brand-build the capture: even pure demand work carries the distinctive wrapper — the voice, the visual system, the named offers. A search ad in house voice with a published number brands; a generic one just bids.
- Demand-wire the brand: even the longest-horizon work carries a path (4.5) — the POV essay ends at the letter; the report ends at the assessment. No orphaned awareness.
- Report the two clocks separately (5.5's discipline): brand lines defended by leading indicators and the annual trend; demand lines by quarterly conversion. Cross-judging is the war's ammunition; refuse to supply it.
- Fund per the written ratio and revisit annually — not per whichever side had a good month.
CHARLESGATE example
One asset, two clocks, fully wired (teaching draft): the Boston Rental Market Report (2.5's citation magnet). Demand clock, this quarter: gated tool-grade edition converts owner and developer contacts; the data arms every active CPM and CRG proposal; sales assigns it before meetings (assignment selling, 2.4). Brand clock, three years: the annual report becomes a distinctive asset in its own right — the recurring format, the signature charts, the "from N managed units" provenance line nobody can copy — and each edition deepens the entry-point attachment: "who actually knows this market" retrieves CHARLESGATE. Machine layer: every AI answer citing it compounds both clocks at once (the citation converts and memorializes). One budget line; Attract, Earn, and Differentiate all compounding on it; and in the budget meeting it's unkillable from either side of the false war — the demand hawk keeps it for the conversions, the brand advocate for the memory. Build more things like this and the war has nothing to fight over.
Do the Work
Classify your OpCo's current work three ways: brand-only, demand-only, dual-clock. For the biggest demand-only line: add the brand wrapper (voice, distinctive asset, named offer) — write the specific change. For the biggest brand-only line: wire the demand path (4.5) — write the specific CTA and next rung. Then write the one-paragraph two-clock defense of your brand budget for the next downturn conversation, citing your own leading indicators — and staple it to the Template 18 downturn paragraph, where it will eventually be needed.
6.3The CHARLESGATE Brand Codes & Voice
First principles
CHARLESGATE already holds a Brand Code — the canonical account of who we are: values, character, voice, visual identity. This program added the Growth Code — how we grow. The interlock is the point of this lesson: **the Brand Code is the what-we're-like that makes the Growth Code's how-we-grow recognizable, trustable, and un-copyable.** One system family, deliberately: Brand Code = identity; Growth Code = motion. A growth system without an identity produces effective noise; an identity without a growth system produces a beautiful secret.
Where they physically meet is the craft of this lesson:
- Distinctive assets (6.1) are Brand Code property deployed by Growth Code machinery: the name, the visual system, the voice, the recurring formats (the letter, the annual report, the teardown), the named frameworks and offers (the Growth Code itself, the First-90-Days Turnaround, the Sell-Out Files). An asset is only "distinctive" if buyers attribute it to us without the logo — that's the test.
- Voice is the Brand Code's audible layer, and ours is already written in this program's own DNA: direct, evidence-led, editorial, plain words over industry words, specific over superlative, honest about tradeoffs, opinionated where we've earned the opinion. Write like Michael talks (1.5's rule) — which at HoldCo scale means: write like the house talks, per the standards, so that four OpCos and forty writers still sound like one firm.
- Editorial standards are brand enforcement. The creative bar (4.4 — a specific, a number, or an opinion that costs something), the swap test (1.5), the synthetic-smell check (3.5) — these aren't just conversion craft; they're what keeps every artifact recognizably ours. Standards are how voice survives scale, new hires, and AI drafting (Module 8 will make this load-bearing).
Why it matters
Because consistency is where brand economics live (6.1: memory accrues through repetition of distinctive elements), and consistency across a HoldCo is hard: four OpCos, different ICPs, different grammars (B2B/B2C, 1.7), agents and leaders each with their own styles. Without written codes and standards, the portfolio drifts into four unrelated small brands plus a logo — quadrupling the cost of every impression, because memory can't accrue across the family. With them, the structure becomes an amplifier: every OpCo's work deposits into one memory bank ("those CHARLESGATE people are direct, they publish real numbers, they know this market") while each OpCo keeps its own altitude and grammar. The Brand Code is what lets the flywheel's cross-OpCo introductions arrive pre-trusted — the AFF client already knows the character of CPM before the first call, because the character is consistent.
There's also the market-side arbitrage, one more time: our category's brand hygiene is poor (2.7's desert). Mediocre firms with consistent codes read as institutions; good firms without them read as vendors. We intend to be a good firm that reads as an institution.
How it works
Workbook Template 20 (Distinctive Asset & Voice Canvas) — the practical interlock:
- Inventory the distinctive assets: everything a buyer might recognize as ours without the logo — formats, phrases, frameworks, named offers, visual signatures, the published-number practice. Score each: recognition (do ICPs actually attribute it to us? — evidence from the 6.1 memory audit), consistency of use, ownership strength (could a competitor adopt it tomorrow?).
- Prune and commit. Fewer assets, used relentlessly, beat many used sometimes (the law of sacrifice, brand edition). Choose the 5–7 the whole house commits to; retire the drift.
- Write the voice standards on one page — the house rules above, plus per-OpCo altitude notes (CPM speaks to volunteers with full-time jobs; CG Capital speaks under compliance; resale speaks consumer — same character, different registers, per 1.7). Include the don'ts with examples: no superlatives without numbers, no industry filler, no synthetic cheer.
- Wire enforcement into existing machinery — no new bureaucracy: the voice page joins the Messaging Doc as AI context (8.2); the creative bar review (4.4) adds one line — "is this recognizably us without the logo?"; the brand spot-check joins the monthly one-pager's Differentiate row (5.1's message-consistency metric, now with teeth).
- Reconcile with the canonical Brand Code documents — this canvas implements them for growth work; where they conflict, the Brand Code wins and the conflict gets escalated, not improvised around.
CHARLESGATE example
The interlock in one artifact family (teaching draft): the teardown format — honest, numbered, named-lesson breakdowns of real work (a sell-out's pricing calls, a turnaround's first 90 days, a development campaign's creative). Brand Code layer: the format is the character — Speak Hard Truths and Own It, rendered as a content genre; the voice is direct and evidence-led; the visual system makes every teardown recognizable at thumbnail distance. Growth Code layer: teardowns run in four motions simultaneously — founder-led posts (3.4), ABM air cover (3.2), AFF's craft-in-public (2.7), proof assets in the enablement kit (7.2). One distinctive asset, committed house-wide; every OpCo deposits into it; every deposit is attributable without the logo. Now the counterfactual: without the canvas, CPM writes "case studies," CRG writes "project spotlights," AFF writes "portfolio pieces" — same underlying substance, three formats, zero accrual. The difference between those two worlds is one page of written commitment, which is this lesson's entire argument.
Do the Work
Workbook Template 20 (Distinctive Asset & Voice Canvas): complete it for the HoldCo with your OpCo's inputs — asset inventory scored on recognition/consistency/ownership (use the 6.1 memory audit as evidence), the commit list of 5–7, the one-page voice standards with per-OpCo registers and don'ts, and the three enforcement wirings named. Flag every conflict with the canonical Brand Code for reconciliation rather than resolving it locally. This canvas ships to Michael and the presidents — it's a HoldCo instrument that OpCos feed, not four separate ones.
6.4Category POV: Saying Something that Costs Something
First principles
A category POV is a public position about how the category should work — a stance that names what's broken, what buyers should demand, and what standard we hold ourselves to in consequence. It is positioning (Module 1) made audible and argumentative: the Positioning Canvas said what only we can claim; the POV says what we believe that the category's incumbents can't afford to say.
The defining property, and the bar: a real POV costs something. It commits us publicly (the published response-time number costs operational freedom); it alienates someone (the "who we're NOT for" article costs bad-fit revenue — on purpose, per the anti-ICP); it picks a fight someone can pick back (the pricing-transparency stance indicts the industry's quote-request theater, and the industry may answer). A stance with no cost is content; a stance with cost is a position — Ries's law of sacrifice (1.3), applied to speech. The cost is the credibility. Buyers know that only the confident publish their numbers, only the honest name their problems, and only the different attack the default — so the cost is the proof, delivered before any claim.
And the fight must be worth picking: aimed at a real buyer pain (not an industry inside-joke), on ground where our operations can cash the check (never stance beyond capability — a POV our service contradicts is a scandal on a timer), and durable for years (POVs compound like brand assets because they are brand assets; changing stances quarterly is the tell of a firm with none).
Why it matters
Three returns on a well-chosen fight. Memory: distinctive stances are the stickiest memory structures available — buyers forget capabilities lists and remember "the firm that publishes its response times" (6.1's entry-point attachment, at maximum adhesion). Sorting: a POV repels bad-fit and attracts best-fit simultaneously — the board that resents transparency talk was never our client; the one that forwards it to the committee is Tier-1 self-identifying (the anti-ICP, self-enforcing at zero CAC). Air superiority: in the AI-content flood, POV is un-generatable by construction — a machine can draft an argument, but it cannot bear a cost, and readers can smell the difference between a take and a stake (2.7, 3.4). The founder-led motion runs on this fuel; this lesson is where the fuel gets refined.
The risk is real and priced in: some rooms cool, some competitors snipe, occasionally a stance needs public revision (revise honestly — "we said X; the data moved us to Y" is itself the brand behaving in character). The unpriced risk is the opposite one: the firm with no enemies has no position, and pays for its safety in invisibility, forever.
How it works
- Harvest candidate stances from earned ground: where do our operations already out-behave the category's defaults? (We publish numbers others hide; we start marketing pre-permit while others wait for the CO; we tell sub-8-unit boards the truth about fit.) The strongest POVs are descriptions of existing behavior, weaponized — zero stance-beyond-capability risk.
- Test each candidate: Does it cost us something specific? (Name it.) Does it name a real buyer pain? Can operations cash it indefinitely? Would a named competitor be unable to say it? (If they could say it comfortably, it's category wallpaper.) Will it still be ours in five years?
- Choose few; commit long. One HoldCo-altitude POV (Michael's lane) plus one per OpCo is plenty. Write each as a one-page argument: the broken default → the cost to buyers → the standard we hold instead → the proof → what we forgo by holding it.
- Deploy through everything: the POV is a content pillar (2.7), a founder-brand spine (3.4), a hosted-room theme (3.6), an enablement-kit frame (7.3's "insight" opener — the sales narrative and the POV must be the same argument), and a hiring filter (people join stances, not services).
- Defend it when tested — the test is the payoff. The first public pushback is the moment the stance becomes real to the audience; answer in character, with evidence, without heat.
CHARLESGATE example
Candidate stances through the test (teaching drafts). CPM: "Boards should never have to ask for their own numbers." Costs: commits us to radical financial transparency, monthly, forever; indicts the industry's opacity, which is most competitors' operating model. Cashable: our reporting practice. Un-sayable by: any firm whose margins live in the opacity. Durable: yes. Passes. CRG new-dev: "Comps are how developments get mispriced." Costs: publicly stakes our pricing method against the industry default; every sell-out becomes a test of the claim. Cashable: the operating-data pricing model — the stance is the differentiator, argued. Passes, and it's already the Sell-Out Files' intellectual spine — notice the convergence: strategy, POV, campaign, and sales narrative are one argument at four altitudes. That convergence is what "coherent" means. Rejected candidate: "Real estate needs to embrace innovation." Costs nothing, names no pain, every competitor could say it at a conference tomorrow. Category wallpaper — the test caught it. Michael's HoldCo altitude: the creativity-moat thesis itself — "AI makes average free; the only durable advantages left are creativity, proof, and proprietary systems" — a POV about the industry's next decade, cashable by how CHARLESGATE visibly operates, and the umbrella every OpCo stance nests under.
Do the Work
Draft your OpCo's category POV one-pager: three candidate stances harvested from earned ground → run all five tests on each, in writing → select one → write the full argument (broken default, buyer cost, our standard, proof, what we forgo). Then name its first three deployments (content pillar, room theme, narrative frame) and the pushback you expect with your in-character answer. Bring it to review alongside Template 20 — the POV joins the canvas as a committed distinctive asset, and it should be torn up at least once before it ships. Stances improve under fire; that's rather the point.
6.5Brand in the AI Era: The Creativity Moat
First principles
The program's thesis, stated at full strength for the final time before the capstone: AI pulls everyone to the middle. Competent strategy decks, competent content, competent campaigns — the entire middle of marketing competence is now free, instantly, for every competitor simultaneously. When a capability becomes free, its differentiating value goes to zero; the returns migrate to whatever remains scarce. This module's claim is that what remains scarce is precisely what this module has been building:
- Distinctiveness — memory structures and distinctive assets accrue only through years of consistent, recognizable presence. A competitor can generate our style tomorrow; they cannot generate the five years of deposits that make the style retrieve our name in a buyer's mind. Memory has no API.
- Taste — the editorial judgment that knows which of the fifty competent options is the right one: which stance, which specific, which cut. AI raises the floor of production and, in doing so, raises the premium on the ceiling — when everyone can make more, choosing better is the whole game. Taste is trained, human, and slow to copy (and it's why the editorial bar and the creative review are strategic infrastructure, not process overhead).
- Proof — real operating data, named results, kept promises, reviews earned over thousands of doors. Un-generatable by construction: proof is a record of the past, and the past can't be prompted. In an environment of infinite plausible claims, verified reality becomes the scarcest content category — and we own an operating company's worth of it.
Notice these are the Brand Code and Growth Code's load-bearing elements. The moat thesis isn't a new strategy bolted onto the program; it's the reason the program is shaped the way it is. Creativity + the Code: the un-generatable assets, run through a proprietary system that compounds them.
Why it matters
Because the middle is getting crowded fast, and the market is already repricing it: the synthetic-outreach penalty (3.5), the invisibility of competent-average content (2.4), creative-as-targeting (2.6) — every 2026 signal says buyers now filter for the human, the specific, and the proven, because everything else has become ambient noise. Firms whose marketing advantage was "we execute competently" are watching that advantage evaporate at generation speed. Firms whose advantage is distinctive memory, editorial taste, and provable operations are watching theirs appreciate — the flood devalues the middle and revalues the scarce, simultaneously.
For the HoldCo this is the strategic weather for the next decade, and it favors us structurally — but only if we hold the disciplines while competitors chase the leverage. The temptation AI presents is to produce more: more content, more sequences, more everything. Volume without the bar is self-defeating precisely now, when the feed's noise floor is rising monthly. The winning posture is leverage inside the standards: AI amplifying production (Module 8's subject) while the codes, the bar, and the proof requirements keep everything shipped above the flood line.
How it works
The brand disciplines, re-read as moat maintenance:
- Protect the deposits. Consistency of distinctive assets (T20's commit list) matters more, not less, as generation gets cheap — recognizability is the anti-flood technology. Drift audits join the quarterly rhythm.
- Raise the bar as the floor rises. The creative bar (a specific, a number, a costly opinion) is a ratchet: as generated content improves, "would a competitor's AI publish this?" replaces "would a competitor publish this?" in the 4.4 review. If the answer is ever yes, the piece is below the new waterline.
- Weaponize proof systematically. The proof engine (case studies quarterly, reviews as a managed play, the published numbers, the annual report) graduates from Repeat-stage hygiene to the content strategy — every un-fakeable artifact we publish forces competitors to compete on ground AI can't level for them.
- Keep taste human and accountable. Named editorial owners per OpCo (2.4), the human line written down (3.4, 8.3), review rituals staffed by people whose judgment we'd defend. Taste doesn't scale through tooling; it scales through standards plus apprenticeship — which makes the Academy itself part of the moat.
- Let the system compound. The play library, the experiment log, the scorecards, the codes — the proprietary operating system is the third un-generatable asset, and it improves with every cycle the team runs it. Competitors can buy the same AI; they cannot buy our accumulated verdicts about what works here.
CHARLESGATE example
Two firms, 2029, same tools (teaching draft — the thought experiment to keep). Firm A adopted AI for volume: forty posts a month, automated sequences, generated case studies. Every artifact competent; none distinctive; the synthetic smell accumulated into a reputation. Their feed is indistinguishable from four competitors running the same stack — literally interchangeable, swap-test-failing at portfolio scale. Buyers' filters, trained by three more years of flood, skip them ambiently. Their CAC is up because nothing deposits. Firm B — the one we're building — adopted AI for leverage inside the codes: production tripled, but everything ships through the bar, wearing the distinctive assets, anchored to published proof, voiced in the house character, aimed at owned entry points. Their five-year-old teardown format is category-famous; their annual report is cited by every AI assistant answering Boston rental questions (the machines, ironically, amplifying the un-generatable); their founder's POV has been consistent long enough to be load-bearing. Same tools, opposite trajectories — the delta is not the technology, it's the codes the technology ran inside. Module 8 teaches the leverage; this lesson's job was the frame it runs in.
Do the Work
Write your OpCo's moat inventory, one page, three columns: distinctiveness (which committed assets from T20 are genuinely accruing — evidence, not hope), taste (who holds the editorial bar, is the standard written, what's the apprenticeship plan), proof (the un-fakeable assets we have vs. the ones we're not producing — the case-study and published-number backlog). For each column: one action this quarter that deepens it. Then the closing exercise of the module: re-read your Module 1 Positioning Canvas and mark every element AI could now generate for a competitor. What survives the marking is your actual moat — and it should map, almost exactly, onto this module. If it doesn't, bring the mismatch to the capstone; that's a strategy conversation worth having out loud.
Module 6 Exit Checklist
You're done with Module 6 when your OpCo has, on paper and reviewed:
- Memory audit: 20 attribution verbatims + win/loss + referrer language read; retrieved-vs-intended gaps written; 3–5 entry points to own chosen with gap lists (6.1)
- Work classified brand/demand/dual-clock; one demand line brand-wrapped, one brand line demand-wired; the two-clock defense paragraph written and stapled to the downturn paragraph (6.2)
- Distinctive Asset & Voice Canvas: scored inventory, 5–7 committed assets, one-page voice standards with per-OpCo registers, three enforcement wirings, Brand Code conflicts flagged for reconciliation (6.3 / Template 20)
- Category POV one-pager: three candidates tested, one selected, full argument written, first three deployments and expected pushback named (6.4)
- Moat inventory: distinctiveness/taste/proof columns with one deepening action each; the Positioning Canvas AI-marking exercise done and mismatches flagged (6.5)
These artifacts are the identity layer Module 8's AI leverage must run inside, the narrative spine Module 7's sales bridge sells from, and the longest-horizon commitments in your Module 9 capstone.
New Workbook Templates This Module Calls for (Build Next)
- Template 20 — Distinctive Asset & Voice Canvas (Lessons 6.3, with 6.1/6.4 inputs): asset inventory grid (asset × recognition/consistency/ownership scores × evidence), the 5–7 commit list with retirement column, one-page voice standards (house rules, per-OpCo registers, don'ts with examples), enforcement wiring checklist, Brand Code reconciliation flags, and a POV appendix page (the 6.4 one-pager format: broken default → buyer cost → our standard → proof → what we forgo → deployments). One canvas at HoldCo level, fed by all OpCos.
(The 6.1 memory audit and 6.5 moat inventory are working exercises that feed Template 20 and the capstone rather than standalone templates.)
New Glossary Terms Introduced (Extend the Glossary)
Memory structures (6.1) · mental availability (6.1) · category entry point (CEP) (6.1 — the trigger-situations through which buyers enter the category) · distinctive asset (6.1/6.3 — recognizable without the logo) · distinctiveness vs. differentiation (6.1 — knowing it's us vs. why choose us) · retrieval test (6.1) · dual-clock work (6.2 — converts now, deposits memory) · memory reservoir (6.2) · voice standards / register (6.3) · drift audit (6.3/6.5) · category POV (6.4 — a stance that costs something) · category wallpaper (6.4 — the stance anyone could say) · stance-beyond-capability (6.4 — the POV your operations can't cash) · creativity moat (6.5 — distinctiveness + taste + proof, run through the Code) · flood line (6.5 — the rising bar generated content sets) · proof engine (6.5 — formalized from the framework's Repeat plays)
Sources drawn on in this module (see framework doc for full lineage): Ehrenberg-Bass Institute / Byron Sharp — mental availability, distinctive assets, category entry points; Binet & Field — brand/activation effectiveness evidence, the long/short split (6.2); LinkedIn B2B Institute — B2B brand evidence, 95:5; Al Ries & Jack Trout — sacrifice, owning a word, category thinking (6.4); April Dunford — positioning as the substance POVs argue (6.4); Dave Gerhardt — founder brand as POV delivery (6.4); Gary Vaynerchuk — attention economics underlying the desert arbitrage; Demand Gen Report 2026 — synthetic-content penalties, the repricing evidence (6.5); the CHARLESGATE Brand Code (canonical internal documents) — 6.3's reconciliation source.
Rules of the workbook: same as Module 1 — blank canvas + teaching-draft example; plain language; living documents, dated and versioned. This canvas is a HoldCo instrument fed by all OpCos — one canvas, not four. Every conflict with the canonical Brand Code documents gets flagged for reconciliation, never resolved locally.
Contents: T20 Distinctive Asset & Voice Canvas (with POV appendix)
T20Distinctive Asset & Voice Canvas
(Lessons 6.1, 6.3, 6.4. The Brand Code implemented for growth work. Inputs: the 6.1 memory audit — attribution verbatims, win/loss language, referrer sentences.)
Blank canvas — Part A: distinctive-asset inventory
An asset is "distinctive" only if buyers attribute it to us without the logo — that's the test.
| Asset (format, phrase, framework, named offer, visual signature, practice) | Recognition (1–5 — evidence from memory audit) | Consistency of use (1–5) | Ownership strength (could a competitor adopt it tomorrow? 1–5) | Verdict: COMMIT / retire |
|---|---|---|---|---|
The commit list (5–7, house-wide — fewer assets used relentlessly beat many used sometimes): TBD Retired (drift, visible and chosen): TBD
Blank canvas — Part B: voice standards (one page)
| Element | Standard |
|---|---|
| House rules | Direct, evidence-led, editorial · plain words over industry words · specific over superlative ("avg response 3.2 business hours" beats "unmatched responsiveness") · honest about tradeoffs · opinionated where we've earned the opinion · read it aloud — coffee-with-a-client test |
| Per-OpCo registers (same character, different altitude — 1.7's grammars) | CPM: TBD (speaks to volunteers with full-time jobs) · CRG new-dev: TBD (institutional, proof-led) · CRG resale: TBD (consumer warmth, neighborhood-specific) · AFF: TBD (craft-forward) · CG Capital: TBD (compliance-gated; counsel-approved templates only) |
| The don'ts (with examples) | No superlatives without numbers · no industry filler ("full-service," "white-glove," "trusted partner") · no synthetic cheer ("We're thrilled to announce…") · no congratulatory wallpaper |
| Entry-point attachments (from the 6.1 memory audit — which 3–5 buying situations each OpCo's work aims at, relentlessly) |
Blank canvas — Part C: enforcement wiring (no new bureaucracy — ride existing rails)
| Wiring | Where it lives |
|---|---|
| Voice page joins the Messaging Doc as AI context | T3 / T23 context library |
| Creative-bar review adds one line: "recognizably us without the logo?" | 4.4 review |
| Brand spot-check joins the monthly one-pager | T16 Differentiate row |
| Drift audit | Quarterly, alongside the citability audit |
| Brand Code conflicts | Flagged → escalated to [owner], never improvised around |
Blank canvas — Part D: POV appendix (one per OpCo + one HoldCo-altitude; Lesson 6.4's format)
| Field | Your answer |
|---|---|
| The stance (one sentence) | |
| The broken category default it names | |
| The cost to buyers of that default | |
| The standard we hold instead | |
| The proof (operations must cash it indefinitely) | |
| What it costs us (name it — no cost, no POV) | |
| What we forgo by holding it | |
| Five-test check | Costs something? ⬜ Real buyer pain? ⬜ Ops can cash it? ⬜ Competitor couldn't say it? ⬜ Durable 5 years? ⬜ |
| First three deployments (content pillar / room theme / narrative frame) | |
| Expected pushback + our in-character answer |
Worked example (teaching drafts)
Part A highlights: the teardown format (recognition 3 — "saw your teardown" appears in verbatims; ownership 4 — requires honesty competitors won't fund; COMMIT) · the published response-time number (recognition 4; ownership 5 — operational commitment competitors can't match; COMMIT) · the market letter format + annual data report (COMMIT) · named offers: First-90-Days Turnaround, the Sell-Out System (COMMIT) · "Different attracts. Earned wins. Repeat." (internal-facing; COMMIT) · assorted per-OpCo one-off content formats (retire — fold into the teardown family; three formats, zero accrual → one format, house-wide).
Part D worked — CPM POV: Stance: "Boards should never have to ask for their own numbers." Broken default: industry opacity — financials arrive late, unreadable, or on request. Buyer cost: deferred-maintenance drift and reserve fiction invisible until they're special assessments. Our standard: readable monthly financial packages + published response-time numbers. Costs us: operational freedom, forever — the numbers publish whether they're good or not. Forgo: clients who prefer comfortable opacity. Five tests: ✔✔✔✔✔ (the discount local cannot say it; their margin lives in the opacity). Deployments: content pillar ("questions your manager hopes you never ask"), board-education room theme, sales-narrative insight (7.3). Pushback expected: "everyone claims transparency" → answer: "Claiming isn't publishing. Here's ours, monthly, since [date]. Ask your manager for theirs."
Rejected candidate (kept as the example of the test working): "Real estate needs to embrace innovation" — costs nothing, names no pain, sayable by anyone at a conference tomorrow. Category wallpaper.
Cross-references: Part A consumes the 6.1 memory audit · Part B feeds T23's context library and the 4.4 review · Part D's POV is the 7.3 narrative's insight and the founder-brand spine (3.4). Sources: Ehrenberg-Bass/Sharp (distinctive assets, CEPs); Ries (sacrifice); the canonical CHARLESGATE Brand Code (reconciliation source).
Where Marketing's Work Becomes Sales' Ammunition
Handoff, enablement, the sales narrative, CRM basics — plus the Phase 2 sales program scope.
Definitions updated in v1.1. This module’s lesson text predates the update — where stage boundaries are discussed, the v1.1 Canon is the authoritative ruling (Attract = attract attention · Earn = earn pipeline · Win = qualified opportunity to signed and onboarded).
Module brief
CHARLESGATE Growth Code Academy · Module 7 of 9 · Status: COMPLETE (Phase 1 scope — the full sales program is Phase 2)
Growth Code linkage: This module operationalizes WIN from the marketing side of the line. Everything upstream — position, trust, motions, campaigns — converges on a handoff: a human conversation where earned trust becomes signed business. Most firms treat that handoff as a fence marketing throws leads over. This module builds it as a bridge: shared definitions with an SLA, an enablement kit built once from the Messaging Doc, one sales narrative every seller tells the same way, and the CRM hygiene that lets the whole system learn. Phase 2 (the full sales program — discovery, qualification, proposals, negotiation, account management) will build the far side of the bridge; these four lessons build marketing's half and the shared span.
By the end of this module you can: write lifecycle definitions both teams sign and an SLA both teams keep · assemble the enablement kit from existing Module 1 artifacts instead of improvising per deal · structure the sales narrative on Dunford's Sales Pitch method — insight → alternatives → perfect world → us + proof · and run CRM lifecycle basics well enough that marketing's reporting and sales' pipeline tell one story.
How to use this module: One lesson per week for four weeks, or a one-day intensive — ideally with sales-side counterparts in the room; every artifact here is co-signed or it's fiction. Prerequisites: Messaging Doc (T3), Offers (T4), ICP + committee grid (T2), and the proof inventory. The Dunford Sales Pitch workbooks and SPICED worksheets in the resource library pair with Lessons 7.3 and the Phase 2 expansion respectively.
A note on examples: CHARLESGATE examples are illustrative teaching drafts — directionally right, but every definition, number, and narrative claim must be validated (and co-signed by the relevant sales-side owner) before use.
7.1Marketing–sales Handoff: MQL, SQL & the SLA
First principles
The handoff fails for one structural reason: the two teams are paid on different clocks and count different things. Marketing celebrates volume it can influence this quarter; sales works deals that close on the buyer's calendar. Without shared definitions, marketing declares victory on "leads" sales calls garbage, sales ignores half the handoffs, the ignored half includes real buyers who go cold, and each side's retrospective blames the other — annually, forever. The fix is unglamorous and total: written definitions, a service-level agreement, and a feedback loop, signed by both sides.
The definitions, precisely (the glossary carries these; this lesson makes them contractual):
- Lead — an identified contact with any expression of interest. A fact, not a qualification.
- MQL (marketing-qualified lead), a.k.a. hand-raiser — the same thing under either name, and the Attract → Earn gate in the v1.1 Canon: a contact meeting written criteria evidencing fit + intent: ICP tier (from T2), trigger behavior (entry-offer request, assessment booking, high-intent page paths), engagement depth. The written part is the discipline: "the treasurer of a 45-unit Tier-1 association requested the assessment" is an MQL; a whitepaper download from a student is a list member, and calling it an MQL is how the definition dies.
- SQL (sales-qualified lead) — sales has engaged and confirmed: real fit, real need, real timeline worth pursuing. Sales' verdict, by sales' written criteria — marketing doesn't grade its own handoffs.
- Opportunity — a qualified deal in pipeline with stage, value, and next step.
And the SLA, the contract's live wire — both directions: marketing commits to MQL quality (definition held, context attached — what they engaged with, which trigger fired) and volume honesty; sales commits to speed-to-lead (first meaningful response inside a written clock) and disposition (every MQL accepted or returned with a reason — no silent graveyard). The reasons are the feedback loop: returned-MQL patterns are marketing's most valuable QA data, and they're free.
Why it matters
Speed-to-lead first, because the numbers are brutal and nobody's exempt: response inside the first hour multiplies contact and qualification rates several-fold versus even a few hours later; by day two, the trigger-driven buyer who requested an assessment Tuesday night has often already met the competitor who answered Wednesday morning. In trigger-driven categories — ours — the response clock is part of the offer (4.5 said it about paths; here it becomes a signed standard with a name attached). All the Earn-stage trust in the world depreciates by the hour once the buyer raises their hand.
The definitions matter for a quieter reason: they're the load-bearing joints of the whole instrument panel. Every Module 5 metric that crosses the handoff — MQL→SQL rate, cost-per-SQL, pipeline by source, funnel conversion — is only as real as the definitions underneath it. Undefined terms make the scorecard a fiction at exactly the stage where fiction is most expensive. And ICP discipline lives here too: the definition gate is where bad-fit demand gets filtered before it consumes sales hours (1.4's system-degrading revenue, stopped at the door).
How it works
Workbook Template 21 (Lifecycle Definitions & SLA) — one page, co-signed:
- Write the four definitions with your OpCo's specifics: ICP tiers in, anti-ICP out, the trigger behaviors that qualify, the engagement thresholds. Concrete enough that two people classify the same contact the same way without discussing it.
- Set the clocks: speed-to-lead standard per lead type (entry-offer requests get the fastest clock — that's a hand raised, not a browse), disposition window, return-reason requirement.
- Name the routing: who receives what, how it arrives (with context — the play card for handoffs), who covers when the owner's out. Routing ambiguity is where SLAs go to die.
- Build the feedback ritual: monthly, thirty minutes, both sides: returned-MQL reasons reviewed (marketing's QA), stuck-deal patterns reviewed (sales' early warning, marketing's content assignments), definition drift corrected. This meeting is the bridge; everything else is its paperwork.
- Instrument it: MQL→SQL rate, speed-to-lead actuals vs. standard, return reasons coded — all onto the T16 scorecard's Win row.
CHARLESGATE example
CPM's handoff, contractualized (teaching draft). MQL definition: association in the 20–80 unit Boston-core ICP (Tier 1/2 per T2), plus any of — assessment requested; switching-guide + cost-article path completed with letter signup; board-education session attended and follow-up accepted. Anti-ICP contacts get a kind referral elsewhere, never a handoff. SLA: assessment requests — first response within 4 business hours, assessment scheduled within 2 business days (the offer promised 30 days start-to-report; the clock starts here); all other MQLs — 1 business day. Disposition within 3 days, return reasons mandatory. Routing: to the CPM business-development lead with the trigger context attached ("treasurer, 45 units, came via failed-inspection guide — likely reserve-anxiety, bring the financials one-pager"). The feedback loop catching something real: three straight returns coded "building too small — inherited portfolio inquiries" → marketing tightens the assessment page's qualifying copy (4.5) rather than sales eating mis-fit meetings forever. Thirty minutes a month, and both teams' dashboards now describe the same pipeline — which, in most firms, would be a first.
Do the Work
Workbook Template 21 (Lifecycle Definitions & SLA): draft it for your OpCo with your sales-side counterpart — definitions, clocks, routing, feedback ritual, instrumentation. Then run the classification test: both of you independently classify the last twenty inbound contacts against the draft definitions; every disagreement is a definition bug — fix the wording until you'd classify identically. Co-sign it, calendar the monthly feedback ritual, and put speed-to-lead actuals on next month's one-pager (5.5). Measure the current actual before the standard takes effect; the before/after is the lesson's receipt.
7.2The Enablement Kit
First principles
Sales enablement is the industrialization of marketing's promises. Every deal needs the same dozen artifacts — the story, the proof, the answers to the same objections, the comparison the buyer will make anyway, the document the champion forwards upstairs. In an unenabled team, each seller improvises these per deal: hours burned, claims drifting from the position (every improvised deck is a small act of message erosion — 1.5's warning, at the deal layer), quality varying by seller, and the best answers dying in the inbox of whoever wrote them once. The kit is the fix: built once from the Messaging Doc, approved once, reused by everyone, maintained on a cadence.
The design principle that separates working kits from brand graveyards: build for the buying committee, not the seller's pitch. The committee decides when we're not in the room (1.7's law — materials that only work with us presenting them don't work). Every artifact's real job is to arm the champion: forwardable, self-explanatory, answering the question the skeptic will actually ask. The kit's core contents:
- The one-pager per ICP — the offer, the value themes with proof, the next step; committee-legible in ninety seconds.
- Case studies by ICP and situation (from the proof engine, 6.5) — the peer story the champion forwards: their building size, their problem, real numbers.
- Competitive responses (Messaging Doc, competitive section) — approved, classy answers to "how are you different from [the national]?" and "why are you more expensive than [the cheap local]?" — written calm, in daylight, never improvised at 4pm on a deal call.
- The objection library — the recurring dozen, with the honest answer, the proof asset, and the reframe. (Assignment-selling content, 2.4, is half this library — the switching-costs article answers the objection before the meeting.)
- Proposal and pitch templates — the narrative (7.3) pre-built, so sellers customize the 20% that's deal-specific instead of re-inventing the 80% that isn't.
- The pricing conversation kit — how we talk about fees: the value math, the honest ranges (TAYA discipline applied to the tensest moment), what we never discount and why.
Why it matters
Because Win-stage quality is mostly pre-manufactured. The difference between a 40% and a 60% proposal win rate is rarely the seller's charisma; it's whether the buyer arrived educated (2.4), whether the champion had ammunition for the meeting we missed, whether the objection met a rehearsed honest answer or a flinch, and whether the proposal told the one approved story or a personal remix. All of that is buildable in advance — which makes enablement the highest-ROI marketing work that most marketing teams never do, because it isn't visible in any channel dashboard (5.2's trackability bias, claiming its quietest victim).
There's also the consistency stake: the kit is how the position survives contact with the field. Four OpCos, dozens of sellers and agents — without approved artifacts, the market hears dozens of positionings; with them, one (6.3's voice discipline, now at the revenue edge).
How it works
- Inventory against the deal, not the shelf. Walk the last five won and lost deals with sales: what artifact was needed at each stall point? What got improvised? What did the champion ask for that didn't exist? That list — not a brainstorm — is the kit's build order.
- Build from the Messaging Doc, always. Every artifact is an assembly of approved components (claims, proof, competitive responses) into a deal-stage form. Nothing in the kit says what the doc can't back — the kit inherits its honesty from T3's proof test.
- Design for forwarding. Every artifact passes the champion test: could the treasurer send this to the skeptic with no cover note and have it land? Self-contained, plain-worded, proof-forward, next-step-explicit.
- Wire it into the motion: assignment selling assigns kit pieces before meetings (2.4); the ABM standup requests account-specific variants (3.2); the objection library feeds the Big-5 inventory and vice versa (the same honesty, two formats); stuck deals trigger a kit gap review (7.1's feedback ritual owns this).
- Maintain on a cadence: quarterly kit review — usage per artifact (ask sales what they actually open), proof freshness (stale numbers rot trust), gap list from the stall-point walk. Ownership: marketing owns the kit; sales owns the verdict on whether it works. Both names on it.
Two kit artifacts the inventory usually misses:
- The budget-objection library with the two-path offer. When a client pushes on the marketing/service budget, the kit should carry the reframes ready-made. The opening move: "Are you optimizing for lowest spend, or highest net proceeds and fastest outcome?" Against "others include it free": "They can 'include' it because it's generic and they aren't accountable for performance." And the structural answer — the two-path offer: Performance Standard (what we recommend and are proud to own) vs. Budget-Constrained (reduced scope with explicitly documented tradeoffs). "You choose, but we'll be clear about what each option is likely to produce." The boundary line, verbatim: "We're happy to right-size deliverables. We're not willing to underfund the fundamentals and pretend it won't affect results." (Full worked set: "Common developer objections regarding marketing" in the resource library — the reframes generalize to every OpCo.)
- The RFP discipline checklist. RFP responses get pitch-grade rigor: reconcile every deadline in the document (the body and the schedule table will disagree — catch it before it catches you); use the written Q&A window aggressively and early (a same-day question list is both intelligence-gathering and a seriousness signal); conduct the site inspection before drafting; and the review standard is fully responsive to their RFP with real data in every field — "strong deck" is not the bar, "responsive and sourced" is. Nothing ships with placeholder numbers.
CHARLESGATE example
The CPM kit, assembled from what already exists (teaching draft — note how little is new; enablement is mostly packaging discipline applied to Module 1–6 output). One-pager: the First-90-Days Turnaround, committee edition — offer, response-time standard with the published monthly number (6.4's POV cashing at the deal table), transition-effort reversal, easy-out clause. Case studies: the turnaround story in three sizes (30, 50, 80 units) because boards trust peers, not portfolios. Competitive responses: vs. the national ("their scale is real; here's what it costs you in response time — and here's both firms' numbers") and vs. the discount local ("here's the service-level math behind the fee difference — judge the gap yourself"). Objection library: switching pain (→ the article + the transition guarantee), "we just renewed" (→ the letter; this is a 95% contact, not a loss), fee anxiety (→ the pricing kit). Proposal template: the 7.3 narrative pre-built, board-meeting-ready. The champion test in action: the president forwards the one-pager and the 50-unit case study to the skeptical longtime owner; both artifacts were written for exactly that forward — which is why the next board meeting starts at "how would the transition work" instead of "why switch at all." That head start was manufactured months earlier, in the kit.
Do the Work
Run the stall-point walk with sales on your OpCo's last five deals (won and lost): artifact needed vs. artifact existed vs. artifact improvised, at each stage. Output the kit build order — the top three missing artifacts. Build artifact #1 this month, assembled strictly from the Messaging Doc, and run the champion test on it before shipping: hand it to someone with no context and ask what they'd conclude in ninety seconds. Then calendar the quarterly kit review with both names on the invite. The kit inventory and build order become a standing section of the 7.1 feedback ritual — the bridge maintains itself, monthly.
7.3The Sales Narrative (Dunford's Sales Pitch)
First principles
April Dunford's Sales Pitch insight completes the arc her positioning method started: most sales pitches fail because they describe the product instead of teaching the decision. The buyer — especially the first-time buyer of anything, which most of our buyers are (a board hires a manager once a decade; a developer picks a sell-out partner a handful of times ever) — isn't struggling to understand our features. They're struggling to understand how to choose: what the options even are, what the tradeoffs mean, what a good decision looks like from where they sit. The pitch that wins is the one that makes the buyer smart about the choice — and, honestly, positions us as the obvious conclusion of that intelligence.
The structure (the full workbooks and a worked example live in the resource library; this is the spine):
- The insight — our POV on the market, opened as a gift, not a claim about us: the thing we know from operating that reframes their situation. (This is the 6.4 category POV walking into the meeting — the narrative and the POV must be the same argument, or the firm has two stories.)
- The alternatives map, played straight — here are the real options, including status quo and cheaper paths, with each one's honest pros and cons. Played actually straight: the moment the buyer catches a strawman, the pitch dies and takes our credibility with it. Fairness here is the trust-arbitrage move (2.4) at the highest stakes.
- The perfect world — "given those tradeoffs, here's what the ideal solution for someone in your situation would look like" — the decision criteria, derived in front of them, from the tradeoffs they just validated.
- Us + proof — and here is that solution: our differentiated capabilities mapped one-to-one onto the criteria, each claim carrying its proof (the inventory, 1.5). The reveal lands because the criteria were earned, not asserted.
- The offer and next step — the T4 entry offer as the low-friction bridge from agreement to action.
One story, told the same way by every seller — customized in evidence per deal, never in architecture.
Why it matters
Because deals in our categories are lost less to competitors than to indecision — the committee that couldn't get confident enough to change anything (the framework's Win-stage diagnosis). A features pitch adds options to an already-overwhelmed buyer; a decision-teaching pitch reduces their uncertainty — it hands the champion the mental model to re-run without us, which is precisely what happens in the room we're not in (1.7's law, one more time, because it governs everything in this module). The narrative is champion armor in story form.
And it converts our deepest asset — operating knowledge — into Win-stage advantage. Any competitor can present features. Only an operator can open with an insight that makes the buyer say "nobody's explained it like that" — and that moment, ninety seconds in, is where the deal's frame gets set (Differentiate, executing at the table). The narrative is also where all the program's threads visibly braid: position (T1) supplies the difference, POV (6.4) supplies the insight, alternatives honesty (T3's competitive responses) supplies the map, proof (6.5's engine) supplies the evidence, offer (T4) supplies the close. If those artifacts exist, the narrative assembles; if the narrative won't assemble, an upstream artifact is weak — the pitch is positioning's final exam.
How it works
- Draft the insight from operating ground: what do we know — from thousands of units, dozens of sell-outs — that reframes the buyer's problem? Test: would a smart buyer want this insight even if they never hired us? If not, it's a claim wearing an insight's clothes.
- Build the alternatives map from T1's canvas — the real alternatives (status quo included), each with its honest strong case. Write the strong case first, for each: if we can't state why someone reasonably chooses the national or stays self-managed, we don't understand the market we're pitching into.
- Derive the perfect-world criteria so they follow from the map's tradeoffs — not from our feature list backward (buyers smell reverse-engineered criteria; the honesty of step 2 is what licenses step 3).
- Map us onto the criteria with proof per claim. Any criterion we can't map honestly gets removed or the gap gets owned out loud ("on pure price, the discount local wins — here's what the gap buys"). Owned gaps build the pitch; hidden ones end it.
- Rehearse it as a team — the narrative is an oral tradition with written support (the 7.2 deck and proposal carry it). Table-reads, objections thrown live (the 7.2 library is the sparring partner), every seller fluent in the architecture. Then instrument: proposal win rate and cycle length, before vs. after adoption (5.1's Win row) — the narrative is a play, and plays get run logs.
CHARLESGATE example
CPM's narrative, compressed (teaching draft). Insight: "Most boards evaluate managers on responsiveness promises. But the operating data says the real risk to your building is financial opacity — deferred-maintenance drift and reserve fiction that no response-time SLA catches. You'll have both problems; you can only see one of them from where you sit." Alternatives, straight: self-manage (cheapest, full control — works genuinely well under ~10 units with an engaged treasurer; above that, volunteer bandwidth is the building's binding constraint); the national (real scale, real systems — and your building is one of nine hundred; escalation is a queue); the discount local (real savings — funded by thin staffing, which surfaces exactly when you need them most); or us. Perfect world, derived: local density with real systems; financials a volunteer can actually read; response standards published, not promised; transition handled by the manager, not the board. Us + proof: the criteria map — monthly published response numbers (6.4's stance, cashing again), the readable-financials practice, the First-90-Days transition, the 50-unit case study. Next step: the free assessment — "decide with your own building's data, not our brochure." Note what the architecture did: the skeptical treasurer's toughest questions ("why not the cheap one? why not stay put?") became our talking points, answered fairly, before she asked — which is the whole method in one sentence.
Do the Work
Workbook Template 22 (Sales Narrative Outline): draft your OpCo's narrative — insight (operating-ground test applied), alternatives map with each option's strong case written first, derived criteria, us-map with proof per claim and gaps owned in writing, entry-offer close. Then the two tests: the fairness read — someone from sales plays the buyer's skeptic and attacks the alternatives map for strawmen; and the assembly check — every claim traced to T1/T3/proof inventory (untraceable claims are upstream homework, logged). Table-read it with the full sales-side team, revise, and version it. Phase 2 will build the discovery and qualification machinery around it; the story itself starts working now.
7.4CRM & Lifecycle Basics for Marketers
First principles
The CRM is not sales' database that marketing occasionally visits. It is the system of record for the entire Growth Code's Win and Repeat stages — the place where the handoff (7.1), the narrative's results (7.3), the attribution witnesses (5.2), the ICP discipline (1.4), and the flywheel's triggers (Repeat) either get recorded truthfully or dissolve into anecdote. A marketer who can't read the pipeline is flying the Attract and Earn stages with no downstream instruments; a CRM full of stale stages and empty fields is both teams flying blind while the dashboards render fiction confidently (garbage in, gospel out — 5.2's biases have a data-entry layer, and this is it).
The basics that carry the weight:
- Lifecycle stages mirror Template 21's definitions exactly — lead → MQL → SQL → opportunity (staged) → client → advocate (the Repeat-stage extension most CRMs never configure and ours must: referral sources, reviewers, case-study participants, cross-OpCo intros are pipeline events and get recorded as such).
- Source truth: every record carries original source (first-touch, however imperfect) plus the self-reported attribution verbatim (2.1) — both, permanently. This is the triangulation stack's raw material; lose it at entry and no analysis downstream can recover it.
- ICP fields: tier, segment, committee role — the fields that make "pipeline ICP-fit %" (T16's Win row) computable instead of vibes.
- Hygiene as a contract: stages current, next steps dated, close dates honest, required fields actually required. Hygiene isn't administrative virtue; it's what makes every number in Module 5 real.
Two house rules that put teeth in the basics:
- Log it or lose it — especially in an AI world. Logging activity is a requirement of the role, not a preference: "the reason is so that you can close deals faster and better — especially in an AI world. This is a must." Unlogged calls, notes, and follow-ups aren't just invisible to management; they're invisible to the AI leverage layer — the transcript mining, the drafted follow-ups, the account intelligence (Module 8) all run on what's in the system. An unlogged deal is a deal the machine can't help you win. And tool friction is not an excuse: figure it out and Own It.
- Instrument before you target. Never lock a goal onto a metric whose source tracking is broken — fix attribution first, then set the number. Holding people to targets measured against bad source data is unfair and teaches the team to distrust every number that follows.
Why it matters
Because this is where the loop closes — the whole program's loop. Marketing's claims about what's working (5.5's one-pager) are only as true as the CRM's source and stage data; sales' claims about lead quality are only as reviewable as the disposition records (7.1); the Repeat stage — the HoldCo's structural moat — only compounds if cross-OpCo triggers fire from data ("sell-out closed" must be a CRM event that launches the CPM play card, not a hallway mention that usually evaporates — 4.3's most valuable play runs on this rail or doesn't run). And the marketing-owes-sales / sales-owes-marketing ledger becomes concrete here: marketing owes clean handoffs with context, honest source data, and content assignments logged; sales owes dispositions with reasons, stage truth, and the self-reported question actually asked on calls. The CRM is where both sides' IOUs are either paid or visible.
One more stake, HoldCo-specific: the CRM is where relationship LTV (5.3) becomes findable. A developer who is simultaneously a CRG client, a CPM prospect, and a CG Capital conversation must be visible as one relationship — or the flywheel math, the allowable-CAC exception, and the whole cross-OpCo strategy run on memory and luck.
How it works
- Configure lifecycle to Template 21, exactly — same names, same definitions, plus the advocate extension. Divergence between the signed sheet and the system is drift with a login.
- Enforce entry standards at the door: required fields on creation (source, ICP tier, self-reported verbatim when known); handoff context in the record, not in Slack. The play card for lead routing (7.1) includes the data steps — hygiene rides existing rails instead of new resolutions.
- Make hygiene a cadence, not a campaign: weekly — sales' own pipeline pass (stale stages, dead next-steps); monthly — the feedback ritual reviews hygiene metrics alongside the SLA (7.1); quarterly — the ICP-fit audit (what % of pipeline is Tier 1/2 — the positioning discipline reading, 1.4) and the bad-fit funeral (kill mis-fit deals in daylight; killing them is strategy, not defeat).
- Wire the Repeat triggers: closed-won fires the referral/review play clock (4.3); the cross-OpCo trigger events (sell-out closed, association signed, fund conversation opened) create tasks with owners in the receiving OpCo. The flywheel becomes software plus SLA instead of culture plus hope.
- Read it monthly as a marketer: pipeline by source and ICP tier, MQL→SQL by segment, stall-point patterns (which stage eats deals — feeds the kit gap list, 7.2), and the advocate ledger (who owes us a case study; who we owe a thank-you). Fifteen minutes; it's the truest marketing report you'll read all month.
CHARLESGATE example
One relationship, traced through a properly configured system (teaching draft). A developer principal enters as a CRG new-dev lead (source: roundtable dinner; self-reported: "Michael's posts, then the dinner invite"). Warm-up logged against the account (ABM standup notes, 3.2). Pricing study accepted → MQL by definition → routed with context, clock running (7.1). Discovery run (Phase 2's machinery), SQL, opportunity staged honestly across a nine-month cycle — every stall visible, one stall pattern (capital-partner sign-off) feeding a new kit artifact (the lender-facing one-pager, 7.2's gap loop working). Closed-won → three triggers fire as tasks, with owners and dates: CPM proposal play (30-day clock), AFF portfolio/case-study play, CG Capital relationship note. The advocate extension records the referral he makes four months later ("source: referral — [name]" on the new lead, closing the attribution loop). Eighteen months, four OpCos, one legible relationship — and every Module 5 instrument along the way was reading real data. That is what the unglamorous fields were for; multiply it by every Tier-1 relationship and it's the HoldCo's operating advantage, recorded.
Do the Work
Run the CRM truth audit for your OpCo, with sales: (1) lifecycle stages vs. Template 21 — list every divergence; (2) pull 20 recent records — score source fields, self-reported verbatims, ICP tier, stage freshness (a simple 0–3 per record; average it — that's your data-trust number); (3) check whether any Repeat trigger exists in the system at all (most firms: no); (4) fix the two worst structural gaps this month — typically the advocate extension and the trigger tasks. Then add the data-trust number to the monthly feedback ritual's agenda. It should embarrass everyone exactly once; after that it's just another gauge that stays green because someone owns it.
Phase 2 Expansion — The Full Sales Program (Scoped, Not Built)
Module 7 built marketing's half of the bridge. Phase 2 builds the sales side as a standalone program, on the same lesson architecture, drawing on the SPICED worksheets already in the resource library:
- Discovery & qualification — SPICED (Situation, Pain, Impact, Critical event, Decision) as the house qualification framework; discovery call structure; disqualifying with grace (ICP discipline at the conversation layer).
- Running the narrative live — 7.3's story under interruption, objection, and committee dynamics; demo/walkthrough craft per OpCo.
- Proposals that close — from the 7.2 template to deal-specific assembly; pricing conversations; procurement navigation without commoditization (1.6's frame defense, live).
- Negotiation — value defense, discount discipline (the T16 Win-row metric gets its playbook), trading concessions for terms (references, case-study rights, multi-year commitments — Repeat assets negotiated at signing).
- Account management & expansion — QBR structure, the advocate ledger as a managed book, cross-OpCo expansion as a quota'd motion (the flywheel gets a sales owner, not just marketing triggers).
Prerequisite artifacts from this module: signed Template 21, live kit with quarterly cadence, versioned narrative, CRM configured to truth. Phase 2 assumes them the way Module 2 assumed Module 1 — build them first.
Module 7 Exit Checklist
You're done with Module 7 when your OpCo has, on paper and co-signed:
- Lifecycle Definitions & SLA: four definitions passing the 20-contact classification test, clocks set with before/after speed-to-lead measured, routing named, monthly feedback ritual calendared, Win-row metrics live (7.1 / Template 21)
- Stall-point walk done on five real deals; kit build order written; artifact #1 built from the Messaging Doc and champion-tested; quarterly kit review calendared with both names (7.2)
- Sales Narrative drafted, fairness-read by a sales skeptic, assembly-checked against T1/T3/proof, table-read with the team, versioned (7.3 / Template 22)
- CRM truth audit: stage alignment verified, data-trust number computed and on the ritual agenda, advocate extension and Repeat trigger tasks configured (7.4)
These artifacts are the Win-stage machinery your Module 9 capstone plan commits to, and the foundation Phase 2's sales program assumes.
New Workbook Templates This Module Calls for (Build Next)
- Template 21 — Lifecycle Definitions & SLA (Lesson 7.1): definition blocks (lead/MQL/SQL/opportunity, ICP-gated, behavior-specific), SLA clocks by lead type, routing map with coverage, return-reason codes, feedback-ritual agenda, co-signature line. Worked example: the CPM sheet from 7.1.
- Template 22 — Sales Narrative Outline (Lesson 7.3): the five-part spine (insight / alternatives map with strong-case-first columns / derived criteria / us-map with proof-per-claim and owned-gaps rows / entry-offer close), fairness-read and assembly-check gates, version log. Pairs with the Dunford Sales Pitch workbooks and worked example in the resource library.
(The enablement kit (7.2) is an inventory governed by the quarterly review rather than a template; its build order lives in the 7.1 ritual notes. The CRM truth audit (7.4) is a working exercise whose data-trust score reports into the ritual.)
New Glossary Terms Introduced (Extend the Glossary)
Lead / MQL / SQL / opportunity (7.1 — now contractual, per written definitions) · SLA (handoff) (7.1) · speed-to-lead (7.1 — the signed standard; introduced operationally in 4.5) · disposition + return reasons (7.1 — the no-silent-graveyard rule) · classification test (7.1) · enablement kit (7.2) · champion test (7.2 — forwardable with no cover note) · stall-point walk (7.2) · objection library (7.2) · decision-teaching pitch (7.3 — vs. the features pitch) · alternatives map / strong-case-first (7.3) · derived criteria (7.3) · owned gap (7.3 — the weakness stated before they find it) · lifecycle stages / advocate stage (7.4) · data-trust number (7.4) · bad-fit funeral (7.4 — killing mis-fit pipeline in daylight) · trigger task (7.4 — the cross-OpCo flywheel as software + SLA)
Sources drawn on in this module (see framework doc for full lineage): April Dunford — Sales Pitch (7.3's entire architecture; workbooks + worked example in the resource library), Obviously Awesome (the positioning the narrative assembles); Marcus Sheridan — They Ask, You Answer (assignment selling into the handoff; the objection library's honesty standard); SPICED worksheets (resource library, via HubSpot/Winning by Design lineage) — Phase 2's qualification spine; Alex Hormozi — offer clarity at the close, risk reversal as champion armor ($100M Offers); LinkedIn B2B Institute / Ehrenberg-Bass — committee dynamics, the 95:5 context for "we just renewed" contacts; speed-to-lead research (industry response-time studies) — 7.1's clock evidence.
Rules of the workbook: same as Module 1 — blank canvas + teaching-draft example; plain language; living documents, dated and versioned. Both templates in this workbook are co-signed artifacts — a sales-side signature is part of the template, not a formality.
Contents: T21 Lifecycle Definitions & SLA · T22 Sales Narrative Outline (the enablement kit (7.2) is an inventory governed by the quarterly review; its build order lives in the T21 feedback-ritual notes)
T21Lifecycle Definitions & SLA
(Lesson 7.1. Written definitions, a service-level agreement, and a feedback loop — signed by both sides. Test before signing: both parties independently classify the last 20 inbound contacts; every disagreement is a definition bug.)
Blank canvas
Part A — definitions (concrete enough that two people classify identically without discussing)
| Term | Our written definition (ICP tiers in, anti-ICP out, qualifying trigger behaviors, engagement thresholds) |
|---|---|
| Lead | |
| MQL (= hand-raiser: ICP fit + a written hand-raise action) | |
| SQL (sales' verdict, sales' criteria) | |
| Opportunity | |
| Advocate (the Repeat-stage extension — referrers, reviewers, case-study participants) |
Part B — the SLA (both directions)
| Commitment | Standard |
|---|---|
| Marketing → quality | MQL definition held; context attached (what they engaged, which trigger fired) |
| Sales → speed-to-lead | First meaningful response: entry-offer requests within TBD · all other MQLs within TBD |
| Sales → disposition | Accept or return with a coded reason within TBD (no silent graveyard) |
| Return-reason codes | e.g., wrong-size / anti-ICP / no-trigger / bad-timing / duplicate — codes are marketing's QA data |
Part C — routing: who receives what · how it arrives (with context — per the routing play card) · coverage when the owner's out: TBD
Part D — the feedback ritual: monthly, 30 min, both sides. Agenda: returned-MQL reasons → stuck-deal patterns (feeds kit gap list, 7.2) → definition drift → speed-to-lead actuals → data-trust number (7.4). Calendar slot: TBD
Part E — instrumentation onto T16's Win row: MQL→SQL rate · speed-to-lead actual vs. standard · return reasons coded.
Co-signatures: Marketing TBD · Sales TBD · Date TBD
Worked example — CPM (teaching draft)
A: MQL = association in the 20–80 unit Boston-core ICP (Tier 1/2 per T2) plus any of: assessment requested · switching-guide + cost-article path completed with letter signup · education-session attended with follow-up accepted. Anti-ICP contacts → kind referral elsewhere, never a handoff. Advocate = any client who has referred, reviewed, or sat for a case study (logged as pipeline events). B: assessment requests — first response 4 business hours, assessment scheduled within 2 business days; other MQLs — 1 business day; disposition within 3 days, coded. C: to the CPM BD lead, trigger context attached ("treasurer, 45 units, came via failed-inspection guide — bring the financials one-pager"). D: the loop catching something real: three straight "building too small" returns → the assessment page's qualifying copy gets tightened (4.5) instead of sales eating mis-fit meetings. Signatures: [marketing lead], [BD lead], [date].
T22Sales Narrative Outline
(Lesson 7.3 — Dunford's Sales Pitch method; full workbooks + worked example in the resource library. One story, told the same way by every seller — customized in evidence per deal, never in architecture.)
Blank canvas
| Part | Content | Gate |
|---|---|---|
| 1. The insight | Our operating-ground POV that reframes their situation (= the T20 Part D stance walking into the meeting) | Would a smart buyer want this even if they never hired us? |
| 2. The alternatives map | The real options incl. status quo — strong case written FIRST for each | A sales skeptic attacks it for strawmen (fairness read) |
| 3. The perfect world | Decision criteria derived from the map's tradeoffs in front of them | Criteria follow from step 2 — not reverse-engineered from our features |
| 4. Us + proof | Capabilities mapped 1:1 onto criteria, proof per claim; gaps owned out loud | Every claim traced to T1/T3/proof inventory (assembly check) |
| 5. Offer + next step | The T4 entry offer as the low-friction bridge | Concrete what-happens-next |
Version log: v___ · date · what changed · table-read done? ⬜ · instrumented (proposal win rate + cycle length, before/after)? ⬜
Worked example — CPM (teaching draft, compressed — the full version is a team oral tradition with this outline as its spine)
1. Insight: "Most boards evaluate managers on responsiveness promises. The operating data says the real risk to your building is financial opacity — deferred-maintenance drift and reserve fiction no response-time SLA catches. You'll have both problems; you can only see one from where you sit."
2. Alternatives, strong case first: Self-manage — cheapest, full control; genuinely works under ~10 units with an engaged treasurer; above that, volunteer bandwidth becomes the building's binding constraint. The national — real scale, real systems; and your building is one of nine hundred, so escalation is a queue. The discount local — real savings; funded by thin staffing that surfaces exactly when you need them. Us — [stated last, after the map is validated].
3. Perfect world, derived: local density with real systems · financials a volunteer can read · response standards published, not promised · transition handled by the manager, not the board.
4. Us + proof: monthly published response numbers (the T20 POV, cashing at the table) · readable-financials package (sample shown) · First-90-Days transition + easy-out · the 50-unit case study. Owned gap: "on pure price, the discount local wins — here's what the gap buys, judge it yourself."
5. Next step: the free Building & Financials Assessment — "decide with your own building's data, not our brochure."
Note the architecture's effect: the skeptical treasurer's toughest questions became our talking points, answered fairly, before she asked.
Cross-references: T21's definitions are the load-bearing joints of T16's Win row and the CRM lifecycle config (7.4) · T22 assembles T1 + T20-D + T3's competitive responses + the proof inventory + T4's entry offer — if it won't assemble, an upstream artifact is weak. Sources: Dunford (Sales Pitch); Sheridan (assignment selling into the handoff); SPICED worksheets (resource library — Phase 2's qualification spine).
Running the Code with Leverage
Running the Code with leverage: AI in the workflow, what stays human, marketing to machines.
Module brief
CHARLESGATE Growth Code Academy · Module 8 of 9 · Status: COMPLETE
Growth Code linkage: Cross-cutting — AI runs inside every stage of the Code; it is not a stage and not a strategy. Module 6 argued the moat thesis (what AI can't generate); this module operationalizes the other half: what AI should do for us, where the human line sits, and how to market to the machines that now sit between us and our buyers. The posture throughout: AI amplifies whatever system it's dropped into. Drop it into a coherent Code — approved messaging, written plays, editorial standards — and it compounds the advantage. Drop it into chaos and it generates chaos faster, in bulk, with confidence.
By the end of this module you can: state the thesis precisely enough to make budget decisions with it · run AI inside the workflow with the Messaging Doc as context and the play library as procedure — research, drafting, repurposing, personalization at leverage · hold the human line in writing: what never gets delegated, and why the editorial bar is now a survival trait · and treat answer engines as a distribution channel with its own discipline — being the source machines cite.
How to use this module: One lesson per week for four weeks, or a one-day intensive. This module assumes the whole program before it — its central claim is that Modules 1–7's artifacts are the AI infrastructure. Teams that skipped the Messaging Doc and the play library don't have an AI adoption problem; they have a prerequisites problem wearing an AI costume.
A note on examples: CHARLESGATE examples are illustrative teaching drafts. AI capabilities and buyer tolerance both move fast — validate current-state before operationalizing, and re-read this module annually; it has the shortest half-life in the Academy by design.
8.1The Thesis: AI Pulls Everyone to the Middle
First principles
State it precisely, because the precise version makes decisions the slogan can't:
1. AI collapses the cost of competent execution to near zero. Drafting, summarizing, designing, sequencing, analyzing — the middle 80% of marketing labor — now costs minutes instead of days. This is real leverage and we take it with both hands (8.2).
2. What everyone can do cheaply, nobody can differentiate with. Competence was never the goal; distinction was, and competence used to be scarce enough to serve as a proxy. That proxy is dead. The competent blog post, the competent nurture sequence, the competent deck — all now ambient, all invisible (2.4's widening gap between "content" and earned answers, now economy-wide).
3. The returns migrate to the un-generatable. Three assets survive, per Module 6.5: creativity (distinctiveness + taste — the judgment to choose the right option among infinite competent ones), proof (operating reality, published — the past can't be prompted), and proprietary systems (the Code itself: the accumulated choices, plays, verdicts, and standards that tell the leverage where to aim). Everything in this program was built to be on the surviving side of that line.
4. The buyer's filter is adapting in real time. The synthetic penalty (~45% less likely to consider vendors whose outreach smells generated — 3.5) is the leading edge of a broader repricing: as generated content floods every channel, buyers and their machines (8.4) develop sharper detectors for the human, the specific, and the verifiable. The flood raises the value of everything that can't float in it.
The strategic equation that falls out: advantage = (un-generatable assets) × (AI leverage) × (system coherence). All three are multipliers. Zero any one and the product is zero — leverage without assets produces distinctive nothing at scale; assets without leverage lose the volume war; both without a system produce brilliant incoherence.
Why it matters
Because both failure modes are live in our market right now, and both are seductive. Failure mode A — abstinence: treating AI as a threat to quality and opting out. Result: out-produced 10:1 by competitors whose median quality now matches yours, losing the frequency game that memory (6.1) runs on. Quality without volume loses to quality with volume. Failure mode B — surrender: treating AI as a replacement for judgment and flooding the zone. Result: the synthetic penalty compounding into reputation damage across a finite universe (3.5's arson math), the brand dissolving into the ambient noise it was supposed to rise above. Volume without the bar loses to everyone.
The winning posture is deliberately boring: leverage inside standards. And it's ours to take at an unfair price, because the standards already exist — that's what Modules 1–7 were. The firms that will struggle with AI adoption are the ones that never wrote down their position, their voice, or their plays, and therefore have nothing to point the leverage at. Our adoption cost is low precisely because the system came first. (This is the "AI implementation" line in the HoldCo's 2026 priorities, given its marketing-side rationale.)
How it works
The thesis converts to four operating rules, which the rest of the module details:
- AI touches everything; AI ships nothing. Every artifact gets human judgment between generation and publication — the depth of review scaled to stakes (8.3's tiers).
- Context is the control surface. AI output quality is determined by input context: the Messaging Doc, voice standards, play cards, and proof inventory are what keep generation on-position (8.2). No context, no coherence.
- The bar ratchets. "Would a competitor's AI produce this?" is the new floor test (6.5). Everything shipped must clear what the flood can now produce.
- Measure the leverage honestly. AI adoption is judged like any motion: time reclaimed, output volume at held quality, cycle-time on plays — on the scorecard, not on enthusiasm (5.1's disciplines apply to our own tooling too).
CHARLESGATE example
The equation, applied to one asset (teaching draft): the market letter. Un-generatable core: the operating data (proof), the editorial POV (taste), the years of trust and the distinctive format (memory). AI leverage on everything around the core: research assembly, first-draft sections from the data tables, repurposing into posts/carousels/scripts (2.7's hierarchy, automated), subject-line variants, list-segment tailoring. System coherence: the Messaging Doc keeps the drafts on-position; the voice standards keep them in character; the editorial owner (a named human, 2.4) makes the calls AI can't. Net: the letter that took two days takes half of one, ships more sections, spawns six derivative artifacts — and reads more like us, not less, because the human hours moved from assembly to judgment. Now the counterfactual: the same leverage applied without the core — a generated market letter with no proprietary data, no stance, no format equity — is exactly the ambient noise the thesis predicts, and precisely what several competitors will be sending by next year. Same tools. The moat was never the tools.
Do the Work
Write your OpCo's thesis audit, one page: (1) the three surviving-asset columns (from 6.5's moat inventory) — current strength, honestly graded; (2) current AI usage mapped against the two failure modes — where are we abstaining that we should leverage, where are we generating without the bar; (3) the multiplication check — which factor (assets / leverage / coherence) is our weakest multiplier right now, with evidence. That weakest factor is your Module 8 priority; the next three lessons are its repair manual. Bring the page to discussion — expect the room to disagree about the weakest factor, and expect that disagreement to be the most useful conversation this module produces.
8.2AI Inside the Workflow
First principles
The organizing insight, and it's Dunford's own 2026 guidance about her method: your positioning and messaging artifacts are no longer just alignment documents — they are the context files for machine leverage. The Messaging Doc (T3), voice standards (T20), ICP and committee grids (T2), play cards (T14), proof inventory, POV one-pagers (6.4): feed them to an AI as standing context and generation lands on-position by default; withhold them and every prompt is a fresh act of improvisation that pulls toward the generic middle (1.5's warning — "every AI-drafted email is a small act of position erosion" — solved by supplying the position).
This reframes the whole adoption question. The high-leverage move isn't better prompting; it's better artifacts, systematically supplied. Which means the Academy's paper output was secretly infrastructure all along: a team with a complete Module 1–7 artifact set has, without noticing, built exactly the context library that makes AI useful — and every artifact improvement now compounds twice (once for humans, once for the machines drafting alongside them).
Where the leverage lands, by function:
- Research: account intelligence assembly (3.2's dossiers from public record), trigger monitoring summaries (3.5's watch mechanism), competitive and market scans, question-inventory harvesting from call transcripts (2.4's Big-5 mining — transcripts in, candidate questions out).
- Drafting: first drafts of everything written — content, emails, briefs, one-pagers — from the context files, never from a bare prompt.
- Repurposing: the messaging hierarchy (1.5) and format ladder (2.7) run mechanically: report → article → posts → scripts → carousel, each re-made native, human-polished at the end.
- Personalization at scale: the warm middle between bespoke 1:1 and synthetic blast — 1:few ABM variants (3.2), letter segment tailoring, kit artifacts tuned per committee role (7.2) — always inside the swap-test constraint (3.5): if the machine's personalization would read identically for the next account, it isn't personalization and it doesn't send.
- Analysis: self-reported attribution coding (5.2's quarterly ritual, accelerated), scorecard narrative drafts (5.5), experiment-log pattern reads (5.6's annual review).
Why it matters
Because the arithmetic is not subtle: the functions above are 60–80% of a marketing team's clock, and a small team across four OpCos is the exact profile the leverage pays most — every reclaimed hour goes straight into the constraint (more plays run, more rooms hosted, more judgment applied). The capacity math in Template 15 changes materially when drafting and repurposing stop consuming the calendar; this is how a lean HoldCo team runs five motion stacks without the headcount those stacks would have demanded in 2020.
And there's a quality paradox worth stating: **used correctly, AI raises the floor and frees the ceiling.** The floor rises because context-fed drafts start on-position; the ceiling frees because human hours migrate from assembly work to the un-generatable work — taste, stance, relationships, proof-gathering. The failure version inverts both: bare-prompt generation lowers the floor (generic drift) while review burden consumes the ceiling (humans polishing slop). The delta between the two versions is entirely in the system — context files, procedures, and the human line — which is why this lesson is about infrastructure, not tips.
How it works
Workbook Template 23 (AI Leverage Map & Guardrails) structures the build:
- Assemble the context library, per OpCo: the artifact set (T2, T3, T14 cards, T20 voice page, proof inventory, POV) packaged as standing context — versioned, dated, owned by the same editorial owner who governs the Messaging Doc. Stale context is position erosion on autopilot; the library updates when the artifacts do, or the whole system quietly forks. The realized version of this already runs in the company: the Brand Code (CPM's first, now AFF and per-project) — seven modules (Strategic Foundation / Market & Customer / Positioning / Messaging / Voice & Identity / GTM Ops / AI Decision Logic & Guardrails) plus a meta layer and a skills layer. The design rule that makes it work: modular and composable — for any task, pull only the modules the task needs as context; modules version independently so Messaging can evolve without rebuilding Positioning. "The system scales with us instead of going stale." And the standard it's held to: something you actually build collateral and campaigns off of, not a style guide that sits in a drawer.
- Map the leverage, function by function: for each recurring workflow (the play cards make this concrete — plays are workflows), mark: AI does / human does / human reviews. The play card format gains an AI column; new plays get designed with it from the start.
- Write the guardrails as house rules: context files supplied on every generation task, no bare prompts for external-facing work · nothing external ships without named-human review (tiered by stakes — 8.3) · the swap test on all personalization · no fabricated specifics, ever — every number and claim traced to the proof inventory or cut (AI's confident inventions are the fastest route to a trust incident; treat unverified generated facts as radioactive) · client and deal confidentiality rules for what may enter which tools. And make the guardrails machine-readable, not just human-readable: the Brand Code's Module 7 (AI Decision Logic & Guardrails) is the pattern — banned vocabulary and AI-speak filters, claim-compliance rules (what may never be asserted in writing until confirmed: licensure, performance guarantees, Fair Housing language boundaries), ICP-fit disqualifiers, pricing-compliance lines, and escalation/approval triggers, all written as context the machine consumes on every generation. Human review catches what slips through; encoded guardrails stop most of it from being generated at all.
- Pilot on the highest-volume play first — usually repurposing or the letter workflow — instrument before/after (hours, cycle time, output volume, quality per the bar), then roll play by play. Adoption by play beats adoption by proclamation: it inherits the library's ownership, SLAs, and run logs.
- Review quarterly on the scorecard: the leverage metrics join the ops row; the guardrails join the drift audit (6.5). Tooling churns; the map and the rules are what persist.
The arc this is building toward — assistant → agent. Everything above is AI-as-assistant: human-initiated, human-shipped. The next layer is agentic execution: brand-code-aware agents that monitor target accounts, draft and iterate outreach, run brand QA on every outbound piece, surface market signals, and prep RFP responses end-to-end. The sequencing rule is the point of teaching it now: the agent layer is only safe and only possible when the foundation exists — context library complete, guardrails encoded (step 3), review tiers holding (8.3). Agents running on a stale or missing brand code don't scale the position; they scale the drift. Build the foundation first; the agents inherit it.
CHARLESGATE example
One play, before and after (teaching draft): CPM's trigger play (3.5 — failed elevator inspection → useful board contact within 5 days). Before: manual public-record checking (weekly, often missed), hand-built research on the association, drafted-from-scratch note, ~3 hours per trigger when it happened at all — the SLA broken more than kept. After, per the T23 map: monitoring summary automated (AI reads the public-record feeds, flags matches against the T2 tier list — AI does); account dossier assembled from public sources into the standard brief (AI does); first-draft note generated from the play card's structure + context library, in house voice, referencing the specific building's situation (AI does); the CPM lead verifies every fact, adds the human specifics, applies the swap test, sends under their name (human does — the relationship and the accountability never delegate). Net: ~40 minutes per trigger, SLA kept, coverage complete instead of sporadic — and the quality went up, because the human's 40 minutes are all judgment and none of it is data entry. Multiply across the play library and the capacity math of the entire motion stack changes. That's the lesson in one play.
Do the Work
Workbook Template 23 (AI Leverage Map & Guardrails): build it for your OpCo — context library assembled and ownership named · top five recurring workflows mapped (AI does / human does / human reviews) · house guardrails adopted with the fabrication rule in bold · pilot play chosen with before-metrics captured. Run the pilot for one month, log the after-metrics, and bring both to review. Gate: if your context library is missing artifacts, that's upstream homework (the relevant module's template), not a tooling gap — do not compensate with prompting heroics; they don't compound and the drift bill arrives later.
8.3What Stays Human
First principles
The human line is not a sentimental commitment; it's a strategic allocation of the scarcest resource — human judgment and human presence — to the exact points where they're irreplaceable and where their absence is detectable. Four categories never delegate:
- POV and stance. A position is a choice with a cost (6.4); machines can argue any side, which is precisely why they can't hold one. The stances, the sacrifices, the "who we're not for" — chosen by humans, owned by name. AI can stress-test a stance (argue against it, find its weak flank — good use); it cannot have one.
- Taste — the final call. Which draft, which specific, which cut, which kill: the editorial verdict on everything shipped (6.5). AI multiplies options; taste selects. The moment selection is delegated, the work regresses to the training-data mean by construction — the middle, automated.
- Relationships and presence. The DM that starts a deal (2.7), the dinner (3.6), the hard conversation, the apology, the reply from the actual person whose name is on the post (3.4's non-negotiable). Trust is a human ledger; entries written by machines bounce — and in a finite universe, get remembered.
- Accountability. Every external artifact has a named human who stands behind it — the fabrication check, the claim traceability, the signature. "The AI drafted it" will never be an accepted sentence in a client conversation, a compliance review (CG Capital's world), or a courtroom. The name on it owns it; that rule is load-bearing for everything else.
Everything outside those four is negotiable leverage territory (8.2). The line is written down per OpCo — because an unwritten line migrates one convenient exception at a time, and the migration is invisible until a buyer notices it for you.
Why it matters
The market enforcement is already priced: the synthetic penalty (3.5) is buyers detecting delegated humanity — outreach, follow-ups, even founder posts that smell generated spend credibility that doesn't refill (3.4's ghostwritten-pablum warning, now a house rule with a category). And detection keeps improving on both sides of the arms race; betting the brand on "they won't notice" is betting against the trend line with a finite universe watching.
But the deeper argument is the thesis itself (8.1): the four human categories are the surviving assets, operationally located. POV and taste are creativity's components; relationships are the dark funnel's whole substrate; accountability is what makes proof provable. Delegate them and we're not saving time — we're liquidating the moat and calling it efficiency. Hold them while leveraging everything else, and the arithmetic runs the right way: the machine does the assembly, the humans do exclusively the things that differentiate, and the proportion of company hours spent on differentiating work goes up every quarter. That proportion is arguably the truest single measure of AI adoption done right.
How it works
- Write the line, per OpCo (it's a section of Template 23): the four categories translated to local cases — which artifacts, which touches, which decisions. CG Capital's line sits strictest (compliance-gated comms — nothing external generates without counsel-approved templates); resale agents' personality brands sit close behind (the sphere is a human ledger, entirely); CPM's board communications, every founder voice's replies and DMs.
- Tier the review to stakes: Tier 1 — external, high-stakes (proposals, POV pieces, anything CG Capital): named-owner review, claim-by-claim. Tier 2 — external, routine (posts, letter sections, kit variants): bar check + spot verification. Tier 3 — internal drafts: light touch. The tiers keep the line affordable; a line too expensive to hold becomes theater within a quarter.
- Guard the founder voices specifically (3.4's support model, formalized): AI may research, structure, and draft from the human's actual transcripts and takes — interview them, don't invent them. The opinions, the specifics, and every reply stay human. The test: could the named person defend every sentence as theirs, extemporaneously, at a dinner? If not, it doesn't post under their name.
- Make the bar the enforcement mechanism: the 4.4 review already asks for a specific, a number, or a costly opinion — all three are exactly what bare generation can't supply truthfully. Held honestly, the existing bar catches most line violations without new bureaucracy; that's not a coincidence, it's why the bar was built that way.
- Audit the line quarterly alongside the drift audit (6.5): sample shipped work, check review-tier compliance, and ask the uncomfortable question in daylight — where did the line move this quarter, and did we choose the move or drift into it? Chosen moves are strategy; drifted ones are the failure mode, caught.
CHARLESGATE example
Michael's voice, operationalized (teaching draft — the highest-stakes instance, since it air-covers all four OpCos per 3.4). AI does: monitors the market-data feeds and drafts the weekly "what moved" brief; transcribes and structures his voice-note takes into post drafts; researches the thread he's replying into; stress-tests the POV pieces by arguing the other side. Michael does: every opinion, every specific from his own deals, every reply and DM, the final read on all of it — and the kill call on the drafts that are competent but not him (taste, exercised weekly, is what keeps the voice earning its premium). The tell this system is working: the posts get more specific and more frequent simultaneously — leverage feeding presence rather than replacing it. The tell it's failing: a follower DMs "did you write this?" — at which point the credibility spend has already happened and no process retro recovers it. One voice, but the same architecture scales down to every OpCo lead and agent running 3.4's motion: the machine amplifies the human; the human never delegates the humanity.
Do the Work
Write your OpCo's human line into Template 23: the four categories, localized to named artifacts and touches; the three review tiers with owners; the founder-voice rules if your OpCo runs one (most do, per 3.8's stacks). Then run the first line audit now, retroactively: sample the last month's shipped work, tier it, and honestly mark anything that crossed — no blame, one lesson each. Bring the marks to discussion: the patterns (it's almost always personalization shortcuts and reply delegation) are where your line needs its clearest wording.
8.4Marketing to Machines
First principles
A structural shift in the buyer journey, stated plainly: a machine now reads us before the buyer does. The board president asks an assistant, not a search box (2.5); the developer's analyst asks a model to summarize "firms that do X in Boston"; the committee member pastes our proposal into a chatbot and asks "is this credible? what should I push back on?" — that last one already happening, mostly invisibly, inside deals we're in right now. The machines are not the audience, but they are the first reader, the summarizer, the citation chooser, and increasingly the shortlist suggester. Marketing to machines is not a metaphor; it's a channel discipline with its own physics.
The physics, extending 2.5's AEO foundation: machines triangulate entities (is CHARLESGATE a consistent, well-attested thing across the open web — same name, services, locations, people, everywhere), prefer structure (answer-first, extractable, schema'd — machines quote what they can cleanly lift), weight provenance (named authors with real footprints, original data with stated methodology, sources other trusted sources cite), and echo reputation (reviews' volume, recency, and sentiment surface nearly verbatim in generated answers). The deep continuity — the reason this lesson doesn't rewrite the program: machines reward what the Code already builds. Honest answers, original data, named experts, consistent identity, earned reviews — TAYA's virtues, machine-read. There is no "trick the model" strategy worth building; there is only being the most citable source in the niche, which we were building toward anyway.
Why it matters
Because the zero-click share of the journey keeps growing, and in it, the answer is the shortlist (2.5's stakes, compounding annually): absence from the generated answer is invisibility at the moment of maximum intent, and no capture budget reaches inside the answer box. Our niches remain barely contested there — the window from 2.5 is still open, and every quarter of consistent citable publishing widens our lead while it stays open; catching up later costs multiples (the compounding runs for whoever starts first, and the desert logic of 2.7 applies to machine attention too).
The second front is newer and mostly ignored: machines as deal participants. When the committee's chatbot summarizes our proposal, what does it say? If our public web presence is thin, inconsistent, or contradicts the proposal's claims, the machine says that — a cold, plausible-sounding skeptic we never get to rebut, sitting in on the committee meeting. Entity hygiene and claim consistency are no longer just Attract-stage concerns; they're Win-stage armor. The proposal, the site, the reviews, and the data reports need to corroborate each other, because something tireless is checking.
How it works
- Run the citability audit as a standing instrument (2.5's quarterly ritual, now permanent): the buyer-question set × the assistants, logged — cited / named / accurate. Add the new Win-stage query class: "is [CHARLESGATE] a good choice for [X]? what are the risks?" — the committee's-chatbot simulation, run on ourselves before they run it on us.
- Publish the citation magnets on a calendar: the original-data assets (rental report, absorption benchmarks, cost articles with real ranges) are the machine channel's flagship spend — un-generatable provenance, methodology stated, named experts attached, refreshed on schedule (stale data loses citations to fresher sources; the maintenance is the moat here).
- Keep entity hygiene boring and perfect: consistent NAP and service descriptions everywhere, the directories machines actually cite (from the audit's source log) accurate and claimed, authorship pages with real footprints for every named expert, schema markup current. Unglamorous; compounding; delegable (an 8.2 workflow, in fact — AI monitoring our own entity consistency is a play card waiting to be written).
- Run the review engine as machine-channel spend: volume, recency, and response quality echo into answers (2.5) — the Repeat-stage play (4.3) now carries an Attract-stage machine dividend, which is the flywheel acquiring a robotic spoke.
- Write for the lift: every key page and answer keeps the extractable summary — the two-sentence answer a machine can quote whole and accurately. If the machine must paraphrase, it may paraphrase wrong; give it the sentence we want repeated. (The one-liner discipline from 1.5, discovered to have been AEO all along.)
- Watch the frontier lightly: assistant behaviors, citation patterns, and new surfaces (voice assistants, agent-mediated procurement) shift quarterly — the audit catches the drift empirically without requiring us to bet on any one prediction. Instruments over forecasts.
CHARLESGATE example
The committee's chatbot, simulated (teaching draft). Before a CPM proposal goes to a 60-unit association's board, we run the query ourselves: "Is CHARLESGATE a good property management choice for a mid-size Boston condo association? What should we watch out for?" The answer we're engineering toward cites the published response-time numbers (the machine loves a firm that publishes what others hide — provenance + specificity), quotes review sentiment ("boards mention responsive communication and readable financials"), references the rental report as evidence of market depth, and — this is the honest-content dividend nobody else will collect — treats our own published "who we're NOT for" and switching-costs articles as credibility signals: a firm that names its tradeoffs reads as trustworthy to a machine trained on the difference between marketing and evidence. TAYA's uncomfortable honesty (2.4), it turns out, was pre-optimized for the machine reader: the strategy that earned human trust earns machine citation for the same reason. The audit's job is to find where today's actual answer falls short of that engineered one — a directory error, a thin authorship page, a review gap, an unclaimed data question — and feed the gaps into the quarterly plan. Machine by machine, quarter by quarter, the answer becomes the one we built — because we're the only ones in the niche building it on purpose.
Do the Work
Extend your OpCo's citability audit (Template 10-B) with the Win-stage query class — run the committee's-chatbot simulation on your own firm across three assistants, log verbatim what they say, and mark every claim that's wrong, stale, or missing. Output the machine-channel quarterly plan: one data-asset action, one entity-hygiene fix, one review-engine push, one extractable-summary retrofit on a key page. Then write the play card (T14): the audit + gap-plan cycle, quarterly, owned — this is a standing channel now, and standing channels get plays, not enthusiasm.
Module 8 Exit Checklist
You're done with Module 8 when your OpCo has, on paper and reviewed:
- Thesis audit: surviving-asset grades, failure-mode map, weakest-multiplier verdict with evidence (8.1)
- AI Leverage Map & Guardrails: context library assembled with named owner, top five workflows mapped, house guardrails adopted (fabrication rule in bold), pilot play run with before/after metrics (8.2 / Template 23)
- The human line written and localized: four categories, review tiers with owners, founder-voice rules; first retroactive line audit done with patterns named (8.3 / Template 23)
- Citability audit extended with the Win-stage query class; committee's-chatbot simulation run and logged; machine-channel quarterly plan written; the audit cycle on a play card with an owner (8.4)
These artifacts are the leverage layer your Module 9 capstone plan runs on — and the disciplines that keep the leverage from dissolving the moat it's supposed to serve.
New Workbook Templates This Module Calls for (Build Next)
- Template 23 — AI Leverage Map & Guardrails (Lessons 8.2–8.3): context-library manifest (artifacts, versions, owner); workflow map grid (workflow × AI does / human does / human reviews); house guardrails block (context-always, no-bare-prompts, fabrication rule, swap test, confidentiality); the human line section (four categories localized, three review tiers, founder-voice rules); pilot log (before/after metrics); quarterly line-audit record. One per OpCo, reviewed at the drift audit.
(The 8.1 thesis audit and 8.4 machine-channel plan are working exercises: the first feeds the capstone, the second extends Template 10-B and lands on a Template 14 play card.)
New Glossary Terms Introduced (Extend the Glossary)
Leverage inside standards (8.1 — the house AI posture) · context library / context file (8.2 — the artifact set that keeps generation on-position) · bare prompt (8.2 — generation without context; banned for external work) · fabrication rule (8.2 — no unverified generated facts, ever) · the human line (8.3 — the four never-delegated categories, written per OpCo) · review tiers (8.3) · dinner-defense test (8.3 — could the named human defend every sentence as theirs?) · first reader (8.4 — the machine that reads us before the buyer does) · committee's chatbot (8.4 — the deal-stage query class) · citation magnet (8.4 — formalized from 2.5) · entity hygiene (8.4) · extractable summary (8.4 — the sentence we want the machine to repeat) · differentiating-hours proportion (8.3 — the truest adoption metric: share of human hours on un-generatable work)
Sources drawn on in this module (see framework doc for full lineage): April Dunford — messaging documents as AI context (her own 2026 guidance on the method's new role); Demand Gen Report 2026 / LinkedIn B2B Institute — 96% adoption, the synthetic-outreach penalty, creative-as-targeting (the repricing evidence); Marcus Sheridan — They Ask, You Answer (the honesty that machines reward, 8.4); Ehrenberg-Bass — distinctiveness and memory as the anti-flood assets (via Module 6); Dave Gerhardt — founder-voice authenticity (8.3's guarded category); Maja Voje — GTM checklist with AI prompts (resource library; 8.2 pairing); the CHARLESGATE Growth Code itself — the proprietary-system asset the whole module leverages.
Rules of the workbook: same as Module 1 — blank canvas + teaching-draft example; plain language; living documents, dated and versioned. One T23 per OpCo, reviewed at the quarterly drift audit. This template has the shortest half-life in the workbook — tooling churns; the map and the rules persist.
Contents: T23 AI Leverage Map & Guardrails
T23AI Leverage Map & Guardrails
(Lessons 8.2–8.3. The posture: leverage inside standards. AI touches everything; AI ships nothing.)
Blank canvas — Part A: the context library manifest
The artifact set supplied as standing context on every generation task. Stale context is position erosion on autopilot.
| Artifact | Version / date | Owner |
|---|---|---|
| Messaging Doc (T3) | (same editorial owner governs the library) | |
| ICP + committee grid (T2) | ||
| Voice standards (T20 Part B) | ||
| POV one-pagers (T20 Part D) | ||
| Play cards (T14 library) | ||
| Proof inventory (T3) |
Blank canvas — Part B: the workflow map
Start with the top five recurring workflows — the play cards make this concrete. New plays get designed with the AI column from the start.
| Workflow / play | AI does | Human does | Human reviews (tier) |
|---|---|---|---|
Blank canvas — Part C: house guardrails
| Rule | Standard |
|---|---|
| Context always | Context files supplied on every generation task; no bare prompts for external-facing work |
| Named-human review | Nothing external ships without it (tiers below) |
| THE FABRICATION RULE | No unverified generated facts, ever. Every number and claim traced to the proof inventory or cut. Treat unverified generated specifics as radioactive. |
| Swap test on personalization | If the message reads identically for the next account, it doesn't send (3.5) |
| Confidentiality | What may enter which tools: client data TBD · deal data TBD · CG Capital: counsel-approved templates only |
Blank canvas — Part D: the human line (never delegated — localized to named artifacts and touches)
| Category | Our localized line |
|---|---|
| POV & stance (machines can argue any side; they can't bear a cost) | |
| Taste — the final call (which draft, which cut, which kill) | |
| Relationships & presence (DMs, rooms, replies from the named person, hard conversations) | |
| Accountability (a named human stands behind every external artifact) |
Review tiers: Tier 1 — external high-stakes (proposals, POV pieces, anything CG Capital): named-owner review, claim-by-claim · Tier 2 — external routine (posts, letter sections, kit variants): bar check + spot verification · Tier 3 — internal drafts: light touch.
Founder-voice rules (if the OpCo runs a 3.4 motion): AI researches, structures, drafts from the human's transcripts and takes — interview them, don't invent them. Opinions, specifics, and every reply stay human. The dinner-defense test: could the named person defend every sentence as theirs, extemporaneously?
Blank canvas — Part E: pilot log + line audit
| Item | Entry |
|---|---|
| Pilot play + before-metrics (hours, cycle time, volume, quality-per-bar) | |
| After-metrics (1 month) | |
| Quarterly line audit: sampled work · tier compliance · where did the line move, and did we choose the move or drift into it? |
Worked example — CPM (teaching draft)
B — the trigger play, mapped (3.5 / T14): public-record monitoring + tier-list matching: AI does · account dossier assembly into the standard brief: AI does · first-draft note from the play card + context library, in house voice, referencing the specific building: AI does · fact verification, human specifics, swap test, sent under the CPM lead's name: human does — the relationship and the accountability never delegate. Result (pilot log): ~3 hrs/trigger → ~40 min; SLA kept; coverage complete instead of sporadic; quality up — the human's 40 minutes are all judgment.
B — the letter workflow: research assembly + data-table first drafts + repurposing into six derivative posts: AI does · editorial POV, final substance calls: human does (named editorial owner) · Tier-2 review on derivatives, Tier-1 on the flagship data issue.
D — worked human line (Michael's voice, the highest-stakes instance): AI monitors data feeds and drafts the weekly "what moved" brief; transcribes voice-note takes into post drafts; researches reply threads; stress-tests POV pieces by arguing the other side. Michael: every opinion, every specific from his own deals, every reply and DM, the final read, the kill call on drafts that are competent-but-not-him. Failure tell: a follower asks "did you write this?" — the credibility spend has already happened.
Cross-references: Part A is T3/T20 doing double duty (Dunford's 2026 guidance: the messaging doc is the AI context file) · Part B extends every T14 card · Part E's line audit rides the T20 drift audit · the differentiating-hours proportion (share of human hours on un-generatable work) is the truest adoption metric — consider adding it to T16's ops row. Sources: Dunford (context files); Demand Gen Report 2026 (synthetic penalty); Lessons 8.2–8.3.
The Exit Exam is a Real Plan, Not a Certificate
The exit exam is a real plan: full-stack diagnosis, the one-page growth plan, the 90-day sprint.
Module brief
CHARLESGATE Growth Code Academy · Module 9 of 9 · Status: COMPLETE
Growth Code linkage: All five stages. Eight modules built concepts and artifacts; the capstone converts them into the only outputs that matter — a diagnosis, a plan, and a sprint. Each OpCo team runs the full Code on its real business, compresses the answer onto one page, defends it to Michael and the presidents, and then executes 90 days of it with owners and kill criteria. The Academy ends the way the Code begins: with choices, made in daylight, on evidence.
By the end of this module you can: score your OpCo on all five stages with evidence and name the binding constraint · compress positioning → ICP → motion stack → campaigns → scorecard onto one defensible page · and convert the page into a 90-day sprint with owners, a calendar, kill criteria, and a first review that actually happens.
How to use this module: Three working sessions over three to six weeks — diagnosis (9.1), plan (9.2), sprint design (9.3) — culminating in the defense session. This is a team exercise per OpCo, led by the OpCo's marketing owner with the president in the room for 9.2 and 9.3. Every prior module's artifacts are inputs; the capstone creates almost nothing new — it selects. If an input artifact is missing, the capstone will find the hole within an hour, which is one of its jobs.
A note on examples: the worked fragments below are teaching drafts. Your capstone uses real numbers, real names, and real dates, or it isn't a capstone — it's a book report.
9.1Run the Code: Full-Stack Diagnosis
First principles
Diagnosis before prescription — the Code's oldest rule (1.2), now executed at full depth. The exercise: score your OpCo 1–5 on each of the five stages, with evidence for every score, and find the binding constraint — the stage whose weakness caps the whole system's output. The constraint logic is worth restating precisely, because it's the capstone's engine: growth systems are serial — attention flows through trust, through conversion, through compounding — so aggregate output is governed by the weakest stage, not the average. Investment anywhere except the constraint buys almost nothing until the constraint moves; which is why "where should we spend?" is always the wrong first question, and "where's the break?" is always the right one.
What's different from the Module 1 audit (Template 7, first run in Lesson 1.2): you now have instruments. Then, scores were informed judgment; now, every stage has a gauge row on the T16 scorecard, a year of self-reported attribution, unit economics (T17), CRM truth (7.4), and the memory audit (6.1). The capstone diagnosis is the first one this OpCo has ever run with real evidence under every number — treat the delta between your Module 1 scores and today's as data in its own right (what did we think was broken versus what the instruments say?).
Scoring discipline: every score cites its evidence in one line — a metric, an audit result, a pattern from the logs. No evidence, no score (3.1's rule, universalized). Where evidence is missing, score conservatively and log the instrumentation gap; a diagnosis that flatters itself wastes the whole exercise.
Why it matters
Because the constraint decision is the plan. Everything in 9.2 — which campaigns, which budget weighting, which motions get fed — derives from which stage is named the constraint. Name it wrong and the year's marketing optimizes a non-binding stage: the classic case from 1.2 (pouring Attract spend on a broken Differentiate stage — paying to be ignored faster) and its quieter siblings (fixing Win-stage narrative when the real break is bad-fit pipeline from a mushy ICP; buying leads when Earn is leaking every one it gets). The diagnosis hour is the highest-leverage hour in the annual calendar, which is why it gets a full lesson and a defense rather than a slide.
And there's a portfolio layer: four OpCos, four constraints, one HoldCo resource pool. The capstone diagnoses feed a HoldCo-level view — where the shared engines (5.4) and Michael's attention should concentrate this year. A HoldCo that knows all four constraints can sequence; one that doesn't peanut-butters (3.8's failure, at the portfolio altitude).
How it works
- Re-run Template 7, evidence edition: per stage, the 1–5 score + the one-line evidence + the trend arrow (better/worse/flat since Module 1). Use the scorecard's stage rows as the evidence bank; supplement with the audits (memory 6.1, citability 10-B, CRM truth 7.4, unit economics T17).
- Interrogate the candidate constraints: the lowest score is the candidate, not the verdict. Test it with the flow question: if this stage improved one point, would output measurably rise — or would the bottleneck just move one stage over? Sometimes two stages are jointly binding (weak Differentiate expressing itself as weak Win — the 1.2 composite); name the upstream one as primary, per the fix-order rule (position before promotion, always).
- Write the three-sentence diagnosis (1.2's format, now with receipts): what's weak, what evidence says so, what you'd fix first. If it takes more than three sentences, the diagnosis isn't done cooking.
- Pressure-test as a team: the strongest counter-diagnosis gets written down too, with what evidence would decide between them — this is the "strong convictions, loosely held" ritual, and it frequently changes the verdict. Bring both to the defense.
- Log the instrumentation gaps found along the way — they're next quarter's measurement backlog (5.1), and their existence is a finding about how the OpCo has been steering.
CHARLESGATE example
A compressed worked diagnosis (teaching draft — CPM owner acquisition). Differentiate: 4 — win rate vs. named alternatives up since the narrative rebuild (7.3); premium held; evidence: proposal win 58%, discounting rare. Attract: 3 — branded search and referrer intros trending up; ICP follower density growing but citability still 4/10 on the audit; evidence: T16 rows + 10-B log. Earn: 3 — list growth strong in budget season, weak off-season; "already knew you" rate 40% and rising; evidence: attribution log. Win: 4 — speed-to-lead inside SLA, cycle shortening; evidence: 7.1's before/after. Repeat: 2 — referral play running but cross-OpCo attach nearly unmeasured, case-study production one quarter behind, advocate stage half-configured; evidence: CRM truth audit, proof-engine backlog. Candidate constraint: Repeat. Flow test: a one-point Repeat improvement feeds proof to Differentiate, referrals to Attract, and attach revenue at near-zero CAC — output rises without another dollar upstream. Counter-diagnosis: Earn's off-season sag is the real cap; decided by whether referral-sourced pipeline (Repeat's gauge) or off-season list engagement (Earn's) moves revenue more per point — the T17 math says Repeat. Three sentences: Repeat is the constraint; the flywheel's machinery (triggers, advocate ledger, proof engine) exists on paper but not in cadence, per the CRM audit; fix first: the trigger tasks and case-study cadence, because everything downstream of a signed client is currently luck. Note what made this diagnosis possible: eight modules of instruments. That was the plan all along.
Do the Work
Run the full-stack diagnosis for your OpCo: Template 7 re-scored with evidence lines and trend arrows · flow-tested constraint verdict · the three-sentence diagnosis · the written counter-diagnosis with its deciding evidence · the instrumentation-gap log. One page total. This page is the opening slide of your defense and the premise of your 9.2 plan — everything after it is derivation.
9.2The One-Page Growth Plan
First principles
One page is not a summary of the plan; one page is the plan — the forcing function that converts eight modules of artifacts into choices. The discipline is subtractive: everything on the page earns its place by deriving from the diagnosis; everything else is, by definition, not this year's plan. A plan that needs ten pages hasn't decided yet — it's still negotiating with itself. (Clarity is leverage; confusion is a tax — the page is where the tax gets paid or repealed.)
Workbook Template 24 (One-Page Growth Plan) — six blocks, fixed order, because the order is the logic:
- Position — the one-sentence claim (T1) and the category POV (6.4), current versions. Two lines. If these changed during the program, the change is the headline.
- ICP — Tier-1 named-account count, the anti-ICP line, this year's beachhead (3.1). Three lines.
- Constraint + diagnosis — the 9.1 verdict, three sentences, evidence cited.
- Motion stack — primary / secondary / experimental (T13), with the one-sentence primary justification and this year's dose changes (what gets fed, what gets cut — the 5.3 math's verdict).
- The campaigns — maximum three, each in one line: name · stage aimed at (must include the constraint) · ICP · offer · success metric · owner · quarter. Each has a T5 brief behind it; the page carries the bet, the brief carries the design.
- The scorecard commitment — the 5–8 numbers this plan promises to move, from T16, with current → target values and the review cadence. This block is what makes the page falsifiable — and a plan that can't fail isn't a plan.
Why it matters
Because the defense is the point. The page gets presented to Michael and the presidents and questioned — why this constraint, why these campaigns and not others, what was sacrificed, what kills each bet. The plan you can defend under questioning is the first one that's real (3.8's rule, graduating to the whole strategy); the defense session is where hedges, wishes, and unowned numbers get found — cheaply, in a conference room, instead of expensively, over four quarters. The genre matters: this is not a pitch seeking approval but a diagnosis seeking holes. The presenter's win condition is a better plan, not a clean getaway — and the reviewers' job is the counter-diagnosis, the capacity math, and the sacrifice check ("what did you decline to do? show me the not-doing list"). A defense where nothing changed was a ceremony, and the Academy doesn't do ceremonies.
The page also solves the portfolio problem: four OpCos, four pages, readable in twenty minutes — the HoldCo's entire marketing strategy legible in one sitting, comparable across OpCos, and reviewable quarterly against the same six blocks (5.5's interface discipline, at annual altitude). This is what "institutional" looks like at the strategy layer: not thicker documents — comparable ones.
How it works
- Draft from artifacts, not from memory: each block pulls its current-version source (T1, T2, 9.1, T13, T5s, T16). Anything you're tempted to write that has no artifact behind it is either this year's homework or this year's fiction — decide which, out loud.
- Run the derivation check: every campaign traces to the constraint (or explicitly defends why it doesn't — sometimes a non-constraint bet is right; it just has to be chosen, not drifted into); the stack's dose changes trace to the T17 math; the scorecard targets trace to the campaigns that would move them.
- Attach the not-doing list — the page's shadow: the motions not fed, the campaigns declined, the channels exited, with one reason each. Sacrifice made visible is what makes the page credible (1.3's law, closing the loop).
- Run the capacity check before the room does: the three campaigns + standing cadences against T15's honest hours. The most common defense finding, every year, everywhere: 130% plans presented with a straight face. Get there first, cut in daylight.
- Defend, revise, sign: the session's changes get made, the page gets signed by the OpCo president and marketing owner, and it becomes the quarterly review's reference document — the thing the monthly one-pagers (5.5) report against all year.
CHARLESGATE example
The CPM page's spine, compressed (teaching draft). Position: the readable-financials/published-standards manager for 20–80 unit Boston associations; POV: "boards should never have to ask for their own numbers." ICP: 62 named Tier-1; anti-ICP holds (sub-8-unit price shoppers); beachhead: budget-season switchers in Boston core. Constraint: Repeat (per 9.1, evidence cited). Stack: inbound/TAYA primary (fed — the data-report line grows per T18); partners secondary (held at dose); events promoted to secondary (per the 5.6 verdict); trigger outbound held; new experimental slot deliberately empty this year — the Repeat fix is operational work, and the experiment budget goes to it. That last clause is the kind of sentence a defense produces: an empty slot, chosen, with a reason. Campaigns (3): the Advocate Engine (Repeat/Win — trigger tasks + case-study cadence + review play, industrialized; the constraint campaign); Budget-Season Answer Dominance (Earn/Attract — the seasonal peak, per T15); Referrer Co-Host Series (Attract — the promoted event motion at secondary dose). Scorecard commitment: referral-sourced pipeline, attach rate, case studies/quarter, off-season list engagement, proposal win rate — current → target, monthly review. Not-doing: consumer AEO (killed per the 5.6 log), LinkedIn ads (universe math), a second data report (capacity). One page; every line traceable; three real bets; falsifiable by Q3. Defensible — which is the entire specification.
Do the Work
Workbook Template 24 (One-Page Growth Plan): build your OpCo's page — six blocks from current artifacts, derivation-checked, capacity-checked, not-doing list attached. Then the defense session: present to your president and Michael; log every question you couldn't answer cleanly (each is either a revision or homework); revise; co-sign. The signed page goes wherever your team's eyes actually land weekly — 4.6's law about visibility applies to strategy hardest of all. Out of sight is out of execution.
9.3The 90-DAY Execution Sprint
First principles
Plans don't deliver results; execution does — and the unit of execution is the sprint: 90 days, named owners, a real calendar, kill criteria, and a first review that happens on the date it was calendared. Ninety days is the honest horizon: long enough for leading indicators to move (most motions' first signals — 3.1), short enough that nothing can hide. A year-long plan without a 90-day sprint is a wish with a nice font; the sprint is where the page (9.2) meets the week (4.6).
The sprint's anatomy — Workbook Template 25 (90-Day Sprint Plan):
- The sprint goal — the one leading indicator this sprint exists to move, derived from the constraint. One. The discipline of the single goal is what makes trade-off decisions self-answering mid-sprint ("does this serve the goal?" replaces a meeting).
- The workstreams — the 3–5 concrete builds/launches from the plan's campaigns: each with an owner (one name), a definition of done, and week-level milestones. Definition of done is written before work starts — "launched" is not done; "launched, instrumented, and first-cycle-reviewed" is.
- The plays going live — which T14 cards start running (or start being kept, honestly) this sprint, with their triggers armed and SLAs staffed.
- The calendar — the sprint mapped onto T15: weekly standup slot, the two mid-sprint checkpoints (day 30/60), the day-90 review, all scheduled now, attendance non-negotiable. Reviews that float, drown.
- Kill criteria + the escalation line — per workstream: what evidence by day 30/60 triggers stop-or-pivot, and what blockers escalate to the president rather than waiting for day 90. Sprints fail politely by default; the criteria make failure loud and early, which is what makes it cheap.
- The capacity ledger — hours per owner per week, honest, summing under reality (4.6's math, at sprint grain). The sprint is also where "who actually does marketing work in this OpCo" stops being ambiguous, possibly for the first time.
Why it matters
Because the gap between strategy and results is always the same gap: the plan was annual, the work is weekly, and nothing connected them. The sprint is the connective tissue — and it's also the Academy's proof of concept: nine modules of frameworks either produce shipped work in the next 90 days or the program was an expensive book club. That's the standard, said out loud, on purpose.
The sprint also builds the muscle the whole operating cadence depends on: kill discipline under real conditions. It's easy to write kill criteria in a workshop; the test is day 30, when the workstream everyone likes is under its threshold and the room has to choose between the criteria and the sunk cost. Every sprint the criteria win, the organization's word to itself gets stronger — and that compounding credibility is worth more than any single workstream's survival. (The reverse compounds too. There is no neutral outcome at day 30.)
And for the HoldCo: four synchronized sprints, reviewed on the same day-90, give Michael and the presidents a quarterly portfolio read — what shipped, what moved, what died honestly, where the constraint verdicts are being confirmed or overturned by contact with reality. The Code's operating cadence (framework doc), fully inhabited: annual choices, quarterly sprints, monthly scorecards, weekly standups. That's the whole system, running.
How it works
- Derive the sprint from the page: the constraint campaign contributes the sprint goal; the quarter's campaign slate contributes the workstreams; the plan's plays contribute the go-lives. Nothing enters the sprint that isn't on the page (and if something must — reality happens — it displaces something visibly, per the kill order, 4.6).
- Staff it honestly, then cut: the capacity ledger first, the workstream list second. The standard sprint mistake is five workstreams on three people's margins; three workstreams that finish beat five that gesture (peanut-buttering's last stand).
- Run the weekly standup on 4.6's format: shipped / blocked / next, thirty minutes, the sprint goal's leading indicator read aloud every week (visibility is a strategy — the number that gets said moves).
- Hold the checkpoints as decision points, not status theater: day 30 — kill criteria checked, first pivots; day 60 — trajectory call (will the goal move by 90? what has to change?); day 90 — the review: goal verdict, per-workstream done-or-not against the written definitions, plays' run logs read, lessons logged (5.6's format — sprints are experiments at organizational grain), and the next sprint drafted in the same session while the evidence is warm.
- Feed the loop: day-90 findings update the scorecard (T16), the plan page (9.2 — plans are living, quarterly), and, once a year, the diagnosis itself (9.1). The flywheel's last gear: execution evidence flowing back into strategy, which was the Code's promise from the first page of the framework.
CHARLESGATE example
CPM's sprint one, from the worked plan (teaching draft). Goal: referral-sourced + attach pipeline events per month — the Repeat constraint's leading indicator — from ~2/month (mostly luck) to 8/month by day 90. Workstreams (3): (1) Trigger rails live — the cross-OpCo and closed-won trigger tasks configured in the CRM with owners and SLAs (7.4's build; done = first five triggers fired and actioned on-SLA); owner: CPM marketing lead + ops. (2) Advocate engine v1 — the referral/review play cards (4.3) armed on every active client at peak-satisfaction moments; done = 100% of this quarter's closings entered the play, run log live. (3) Proof cadence unblocked — the two overdue case studies shipped and the quarterly production slot calendared with named client targets; done = both live in the kit (7.2) and cited in one proposal each. Plays going live: closing referral play, review play, the trigger-response play (already running, now on rails). Kill/escalate: if trigger-task configuration slips past day 30, escalate to the president — it's a dependency for everything (the honest sequencing: rails before engine). Capacity: 26 hrs/week across three people, ledgered, at 92%. Day 90, the honest range of outcomes: the goal number moved — or it didn't and the review says why with evidence, which re-opens the counter-diagnosis (was Earn the constraint after all?). Either way the system learned at full speed — and that, not any single number, is what the Academy was for.
Do the Work
Workbook Template 25 (90-Day Sprint Plan): build your OpCo's sprint one from the signed plan — goal, workstreams with owners and definitions of done, plays armed, calendar with all reviews scheduled, kill criteria and escalation line, capacity ledger cut until honest. Present it in the same defense session as the plan (they're one decision), then start Monday. At day 90, run the review, log the lessons, and draft sprint two in the room. The Academy is over; the cadence is not. That was the design.
Module 9 Exit Checklist — The Program's Exit Checklist
The Academy is complete for your OpCo when:
- Full-stack diagnosis: five stages scored with evidence lines and trends, constraint flow-tested, counter-diagnosis written with deciding evidence, instrumentation gaps logged (9.1 / Template 7 re-run)
- One-Page Growth Plan: six blocks, derivation-checked, capacity-checked, not-doing list attached — defended to the president + Michael, revised, co-signed, and posted where eyes land (9.2 / Template 24)
- 90-Day Sprint: goal, staffed workstreams with definitions of done, plays armed, reviews calendared, kill criteria live, capacity ledger honest — launched (9.3 / Template 25)
- The cadence inhabited: weekly standup running, monthly one-pager reporting against the plan (5.5), day-30/60/90 checkpoints held as decision points, sprint two drafted at the day-90 review
Four OpCos through this checklist = the HoldCo running on the Growth Code. That was the program.
New Workbook Templates This Module Calls for (Build Next)
- Template 24 — One-Page Growth Plan (Lesson 9.2): the six fixed blocks (position+POV / ICP+beachhead / constraint diagnosis / motion stack with dose changes / ≤3 campaigns in one-line format / scorecard commitment with current→target), plus the not-doing list and capacity-check appendix, defense-log page, and co-signature line. Worked example: the CPM spine from 9.2, expanded.
- Template 25 — 90-Day Sprint Plan (Lesson 9.3): sprint goal block (one leading indicator, current→target), workstream grid (owner / definition of done / weekly milestones), plays-going-live list with triggers and SLAs, sprint calendar (standup + day-30/60/90 sessions), kill criteria + escalation line, capacity ledger, day-90 review format (goal verdict / done-or-not / run logs / lessons / sprint-two draft).
(The 9.1 diagnosis re-uses Template 7 with the evidence-edition additions: evidence line, trend arrow, flow test, counter-diagnosis block — fold these into Template 7 as version 2 rather than a new template.)
New Glossary Terms Introduced (Extend the Glossary)
Binding constraint / flow test (9.1 — would output rise, or does the bottleneck just move?) · counter-diagnosis (9.1 — the strongest rival verdict, written down with its deciding evidence) · evidence edition (9.1 — no evidence, no score, program-wide) · one-page plan (9.2 — the page is the plan) · derivation check (9.2 — every line traces to an artifact or gets named fiction) · not-doing list (9.2 — sacrifice made visible) · defense session (9.2 — a diagnosis seeking holes, not a pitch seeking approval) · sprint goal (9.3 — the one leading indicator) · definition of done (9.3 — written before work starts) · capacity ledger (9.3) · decision checkpoint (9.3 — day 30/60 as kill-criteria moments, not status theater) · kill discipline (9.3 — the organization keeping its word to itself)
Sources drawn on in this module: the preceding eight modules — the capstone deliberately introduces no new external frameworks. Lineage notes for the mechanics: constraint-based diagnosis (the Growth Code framework doc, Lesson 1.2; Goldratt's theory-of-constraints logic applied to growth stages); one-page planning and defense rituals (the HoldCo's own operating-system practices — OKR/scorecard cadence, quarterly reviews); sprint structure (agile execution conventions adapted to marketing grain); kill discipline (Lessons 2.3, 4.2, 4.6, 5.6 — the program's most repeated muscle, on purpose).
Rules of the workbook: same as Module 1 — blank canvas + teaching-draft example; plain language. These are the capstone artifacts: real numbers, real names, real dates, or it's a book report.
Contents: T7 v2 additions (evidence edition) · T24 One-Page Growth Plan · T25 90-Day Sprint Plan
T7Growth Code Stage Audit, Evidence Edition
(Lesson 9.1. Fold these additions into the Module 1 workbook's T7 rather than replacing it. Rule: no evidence, no score — where evidence is missing, score conservatively and log the instrumentation gap.)
Additions to the T7 grid
| Stage | Score (1–5) | Evidence line (metric / audit / log — one line, mandatory) | Trend since last audit (↑/↓/→) |
|---|---|---|---|
| Differentiate | |||
| Attract | |||
| Earn | |||
| Win | |||
| Repeat |
Evidence bank: T16 stage rows · self-reported attribution log (2.1) · memory audit (6.1) · citability audit (T10-B) · CRM truth audit (7.4) · unit economics (T17).
The flow test (the lowest score is the candidate, not the verdict): if this stage improved one point, would output measurably rise — or does the bottleneck just move one stage over? Where two stages are jointly binding, name the upstream one primary (position before promotion, always).
The counter-diagnosis (mandatory): the strongest rival verdict, written down, with the evidence that would decide between them: TBD
Three-sentence diagnosis: what's weak · what evidence says so · what we'd fix first.
Instrumentation gaps found: TBD (→ next quarter's measurement backlog, 5.1)
Worked example — CPM (teaching draft, compressed from Lesson 9.1)
Differentiate 4 (proposal win 58% post-narrative-rebuild; discounting rare; ↑) · Attract 3 (branded search + referrer intros ↑; citability 4/10; →) · Earn 3 ("already knew you" 40% and rising; off-season list sag; ↑) · Win 4 (SLA held, cycle shortening; ↑) · Repeat 2 (attach nearly unmeasured; case-study production a quarter behind; advocate stage half-configured; →). Flow test: a one-point Repeat improvement feeds proof to Differentiate, referrals to Attract, attach revenue at near-zero CAC — output rises without another upstream dollar. Counter-diagnosis: Earn's off-season sag is the real cap; decided by whether referral pipeline or off-season engagement moves revenue more per point — T17 math says Repeat. Diagnosis: Repeat is the constraint; the flywheel machinery exists on paper but not in cadence (CRM audit); fix first the trigger tasks and case-study cadence — everything downstream of a signed client is currently luck.
T24One-Page Growth Plan
(Lesson 9.2. One page IS the plan. Six blocks, fixed order — the order is the logic. Presented, questioned, revised, co-signed, posted where eyes land.)
Blank canvas
| Block | Content |
|---|---|
| 1. Position (2 lines) | One-sentence claim (T1, current version) + category POV (T20-D). If these changed during the program, that change is the headline. |
| 2. ICP (3 lines) | Tier-1 named-account count · the anti-ICP line · this year's beachhead |
| 3. Constraint + diagnosis | The T7v2 verdict, three sentences, evidence cited |
| 4. Motion stack | Primary / secondary / experimental (T13) + the primary-justification sentence + this year's dose changes (fed / cut, per T17's verdict) |
| 5. The campaigns (max 3, one line each) | Name · stage aimed (must include the constraint, or defend why not) · ICP · offer · success metric · owner · quarter — T5 brief behind each |
| 6. Scorecard commitment | The 5–8 numbers this plan promises to move (T16): current → target · review cadence. This block makes the page falsifiable — a plan that can't fail isn't a plan. |
Appendices (attached, one page total):
- The not-doing list — motions not fed, campaigns declined, channels exited, one reason each. Sacrifice made visible is what makes the page credible.
- Capacity check — the 3 campaigns + standing cadences vs. T15's honest hours. Get there before the room does.
- Defense log — every question not answered cleanly at the defense session → revision or homework.
Co-signatures: OpCo president TBD · Marketing owner TBD · Date TBD
Worked example — CPM spine (teaching draft, from Lesson 9.2)
1. The readable-financials/published-standards manager for 20–80 unit Boston associations. POV: "Boards should never have to ask for their own numbers." 2. 62 named Tier-1 · anti-ICP holds (sub-8-unit price shoppers) · beachhead: budget-season switchers, Boston core. 3. Constraint: Repeat (T7v2 above). 4. Inbound/TAYA primary (fed — data-report line grows per T18) · partners held at dose · events promoted to secondary (per the T19 verdict) · trigger outbound held · experimental slot deliberately empty — the Repeat fix is operational work and gets the experiment budget. 5. The Advocate Engine (Repeat/Win — trigger tasks + case-study cadence + review play, industrialized; the constraint campaign) · Budget-Season Answer Dominance (Earn/Attract — the seasonal peak) · Referrer Co-Host Series (Attract — the promoted motion at secondary dose). 6. Referral-sourced pipeline · attach rate · case studies/qtr · off-season list engagement · proposal win rate — current → target, monthly review. Not-doing: consumer AEO (killed per T19) · LinkedIn ads (universe math) · a second data report (capacity).
T2590-DAY Sprint Plan
(Lesson 9.3. Presented in the same defense session as the plan — they're one decision. Then start Monday.)
Blank canvas
| Block | Content |
|---|---|
| 1. Sprint goal | The ONE leading indicator this sprint exists to move (from the constraint): TBD · current → day-90 target |
| 2. Workstreams (3–5) | Per workstream: owner (one name) · definition of done (written before work starts — "launched, instrumented, first-cycle-reviewed," not "launched") · week-level milestones |
| 3. Plays going live | Which T14 cards start running this sprint — triggers armed, SLAs staffed |
| 4. Calendar | Weekly standup slot · day-30 + day-60 checkpoints · day-90 review — all scheduled now, attendance non-negotiable |
| 5. Kill criteria + escalation line | Per workstream: what evidence by day 30/60 triggers stop-or-pivot · what blockers escalate to the president rather than waiting |
| 6. Capacity ledger | Hours per owner per week, honest, summing under reality (T15's math at sprint grain) |
Day-90 review format: goal verdict · per-workstream done-or-not against the written definitions · plays' run logs read · lessons logged (T19 format — sprints are experiments at organizational grain) · sprint two drafted in the same session, while the evidence is warm.
Worked example — CPM sprint one (teaching draft, from Lesson 9.3)
1. Goal: referral-sourced + attach pipeline events/month: ~2 (mostly luck) → 8 by day 90. 2. Workstreams: (a) Trigger rails live — cross-OpCo + closed-won trigger tasks configured in the CRM with owners and SLAs; done = first five triggers fired and actioned on-SLA; owner: CPM marketing lead + ops. (b) Advocate engine v1 — referral/review play cards armed on every active client at peak-satisfaction moments; done = 100% of the quarter's closings entered the play, run log live. (c) Proof cadence unblocked — two overdue case studies shipped + quarterly production slot calendared with named client targets; done = both live in the kit and cited in one proposal each. 3. Plays live: closing referral · review · trigger-response (now on rails). 4. Calendar: standup Tuesdays 9:00 · checkpoints [dates] · day-90 review [date]. 5. Kill/escalate: trigger-task configuration slipping past day 30 escalates to the president — it's a dependency for everything (rails before engine). 6. Capacity: 26 hrs/wk across three people, ledgered, 92%. Day 90, the honest range: the number moved — or it didn't and the review says why with evidence, which re-opens the counter-diagnosis. Either way the system learned at full speed.
Cross-references: T7v2 consumes the whole instrument panel (T16, T10-B, T17, 6.1, 7.4) · T24 selects from every prior template — anything on the page with no artifact behind it is either homework or fiction, decided out loud · T25 derives strictly from T24; nothing enters the sprint that isn't on the page. Sources: the preceding eight modules; constraint logic per the framework doc (Lesson 1.2).
Team Dashboard
Lesson completion across the whole roster — live from the shared tracker. A module cell fills as its lessons are marked complete.
Loading team progress…