Ops & Governance

The framework — strategy first

Ops & Governance — the strategic foundation.

STRATEGY & PROCESS

The difference between a good marketing team and a great one is often operations. This work defines how you govern content, manage the marketing technology stack, maintain data quality, and run the marketing function with operational discipline.

AI OPERATING MODEL LIVES IN AI Operating Model — THIS MODULE GOVERNS THE HUMAN OPS LAYER

Read both sections together. AI Operating Model covers the agent stack: the 3-layer LLM Ops framework (Context → Data → Action), the Marketing Agent Org Chart (Web Operations / Performance Marketing / Field Marketing as named team members), the 8-layer infrastructure stack, agent lifecycle (Recruiting → Onboarding → Active → Under Review → Terminated), agent KPIs, and the governance approval workflow that gates every agent before it ships. Ops & Governance (this section of the playbook) covers the human ops layer: content governance, MarTech, data quality, UTM, the three CMO meetings.

Where they connect:

Content governance feeds the Editorial Policy that Editor Agents enforce. The content lifecycle in AI Operating Model only works because the human-defined Editorial Policy in Ops & Governance is sharp.
Marketing data governance feeds the schema.md files the Data layer reads. Bad data in Ops & Governance = worse agent outputs than a human would produce. AI Operating Model's data layer cannot rescue Ops & Governance's data hygiene.
UTM governance feeds the attribution model agents read. If Urchin Tracking Module (UTM) parameters aren't disciplined, no agent can deliver accurate attribution. The agent inherits your hygiene.
The three CMO meetings become the venue where agent performance is reviewed. Add a 5-min "agent roster review" to the Monthly Pipeline Council: which agents shipped, which are in Review, which were Terminated and why.

Senior-operator move: when the human ops layer is loose, AI Operating Model agents amplify the looseness. Tighten the human layer first, then add the agent layer on top.

Content Governance Framework

Content governance ensures that every piece of content produced is accurate, on-brand, legal-safe, and strategically aligned before it reaches any audience.

STAGE	ACTIVITY	OWNER	GATE CRITERIA
Strategy	Content mapped to ICP persona, funnel stage, and quarter	Content Lead + PMM	Tied to campaign brief or content calendar
Brief	Content brief created with: keyword, audience, angle, CTA, format	Content Strategist	Brief reviewed and approved before creation starts
Creation	Draft written by in-house writer or external agency/freelance	Writer / Agency	First draft delivered per agreed SLA
Review Round 1	Subject matter expert review (PMM or product) for accuracy	PMM / Product	Factual accuracy confirmed; messaging aligned
Review Round 2	Brand voice and style review	Content Lead	Voice, tone, and style guide compliance
Legal Review	Claims, customer references, competitive comparisons checked	Legal	Required for: customer quotes, competitive claims, data
SEO Review	On-page SEO elements optimized	SEO Specialist	Keyword, meta, internal links set
Final Approval	Sign-off before publish/distribute	Content Lead or CMO	All gates passed
Distribution	Content live, social scheduled, paid amplification (if applicable)	Demand Gen / Social	Published in CRM campaign; UTMs applied
Performance Review	Views, MQLs, engagement tracked at 30/60/90 days	Content + Demand Gen	Monthly content performance report

Content Calendar Management

PLANNING HORIZON	WHAT IT COVERS	OWNER	REVIEW CADENCE
Annual Content Calendar	High-level themes, major content programs, quarterly campaigns	CMO + Content Lead	Annual + Q3 preview for following year
Quarterly Content Plan	Specific content by type, campaign, and owner; 13-week view	Content Lead	Reviewed at start of each quarter
Monthly Publishing Calendar	Week-by-week publishing schedule by channel	Content Coordinator	Weekly sync; updated on Mondays
Weekly Sprint	Daily execution: drafts due, reviews needed, scheduled posts	Content Team	Tuesday morning standup

CONTENT CALENDAR — MINIMUM FIELDS

Title / topic
Content type (blog, guide, video, social, email, etc.)
Target persona + funnel stage
Campaign / theme association
Primary keyword (for SEO content)
Author / owner
Draft due date
Review due date
Publish date
Distribution channels
CTA + offer link
Performance-tracking link (UTM)
Status (planned / in-progress / in-review / scheduled / live)

Marketing Technology Stack

The marketing technology stack must be rationalized annually. Every tool in the stack should map to a clear use case, an owner, and a measurable ROI.

HOW TO READ THE STACK TABLE

The vendors named below are common examples — your stack should match motion (PLG vs. sales-led), vertical, and ARR scale, not match this table. Where two or three vendors anchor a category, the senior-operator move is to pick one and run it deep before adding the second. Where Tier 2 alternatives are listed (PLG / SMB tools), they often beat the enterprise default on time-to-value and total cost for companies under $20M ARR.

CATEGORY	CORE USE CASE	COMMON EXAMPLES (Tier 1 enterprise / Tier 2 PLG-SMB)	INTEGRATION REQUIREMENTS
CRM	Source of truth for contacts, accounts, and pipeline	Salesforce (mid-market+) / HubSpot (SMB-mid) / Pipedrive (SMB)	Bi-directional sync with all marketing tools
Marketing Automation / MAP	Email nurture, lead scoring, campaign attribution	Marketo (enterprise) / HubSpot (SMB-mid) / Customer.io (PLG-mid) / Braze (consumer-PLG)	Native CRM integration; bi-directional sync
Website CMS	Content publishing and conversion optimization	WordPress, Webflow, Contentful, HubSpot CMS, Sanity	Form-to-CRM sync; analytics integration
SEO / Content Intelligence	Keyword research, content gap analysis, rank tracking	Ahrefs, Semrush, Clearscope, Surfer SEO	CMS integration; analytics connection
Paid Advertising Platforms	Demand gen via search, social, display, and retargeting	Google Ads, LinkedIn Ads, Meta Ads, Reddit Ads, programmatic via The Trade Desk or StackAdapt	UTM tracking back to CRM; budget management
Analytics / BI	Performance reporting and attribution modeling	GA4 / Mixpanel / Heap / PostHog (open-source) for product analytics; Looker, Tableau, Mode, or Hex for BI	CRM + MAP + paid platforms integration
Sales call recording + coaching	Call recording, sentiment, coaching, deal intelligence	Gong (mid+) / Chorus (mid+) / Avoma (SMB) / Fathom (PLG-SMB)	CRM sync; calendar integration
Conversational Marketing / Chat	Real-time website engagement and meeting booking	Drift, Intercom, Qualified, Chili Piper for routing	CRM integration; MAP integration for nurture
Intent data + ABM Platform	Account-based advertising and intent signal tracking	6sense / Demandbase (sales-led mid-market+) / Common Room (PLG product signals) / HockeyStack (PLG attribution) / Bombora (intent feed only) / Foundry, ZoomInfo Intent	CRM account sync; sales alert integration
Data enrichment	Firmographic + contact enrichment	ZoomInfo, Apollo, Clearbit (now HubSpot Breeze), Clay (workflow enrichment), Cognism (GDPR-strong)	CRM enrichment writeback; cadence-tool integration
Sales Enablement	Content delivery and sales productivity	Highspot, Seismic, Showpad, Gong Engage	CRM integration; marketing content publishing
Review Management	Review-platform presence management	G2, Gartner Peer Insights, TrustRadius (horizontal); KLAS Connect, AdvisoryHQ, PeerSpot (vertical)	NPS/CSAT integration for solicitation triggers

Marketing Data Governance

Bad data corrupts every downstream metric — MQL counts, attribution models, pipeline reports. Fix it at the source. A disciplined data governance program is the difference between numbers you can defend in front of a CFO and numbers the room argues about.

DATA PROBLEM	ROOT CAUSE	SOLUTION
Duplicate Contact Records	Multiple form submissions, manual imports, poor dedup rules	Implement CRM dedup tool; enforce email as unique identifier; quarterly dedup audit
Missing UTM Parameters	Links shared without UTMs; ads without tracking templates	UTM governance policy; automated UTM builder; MAP tracking fallback
Incorrect Lead Source	Manual data entry; source overwritten by later touchpoint	Source is immutable at creation; Last Touch tracked in separate field
Stale Contact Data	Email bounces; job changes; unsubscribes not processed	6-month email validation cycle; enrichment refresh via a data-enrichment provider (ZoomInfo, Apollo, Clearbit, Clay, or Cognism — pick one)
Attribution Discrepancies	Different attribution models in MAP vs. CRM vs. BI tools	Single source of truth defined; MAP is system of record for attribution
Unhygienic Pipeline Stages	Opps in early stages that are actually dead	Mandatory activity-based stage advancement; quarterly pipeline scrub with Sales

Campaign Tagging & UTM Governance

UTM NAMING CONVENTION

utm_source — the traffic source (e.g., google, linkedin, newsletter, partner-name)
utm_medium — the channel type (e.g., cpc, email, social, organic, webinar, event)
utm_campaign — the campaign name in snake_case matching the CRM campaign name (e.g., q2_2026_abm_enterprise)
utm_content — the specific ad, email, or placement variant (e.g., hero_banner_v1, subject_line_b)
utm_term — paid keyword (paid search only)

Rule: All links distributed by marketing must have UTM parameters. No exceptions for paid channels.

Rule: UTM naming must match the CRM campaign name exactly for attribution to work correctly.

Rule: A UTM governance doc is maintained in the marketing wiki and reviewed at campaign kickoff.

AEO is cross-functional — the 4-function ownership model.

Answer Engine Optimization sits across the marketing function. No single owner works — the discipline touches content, technical SEO, customer marketing, and PR simultaneously. The senior-operator move is to name owners by function, not by tactic, and let the CMO orchestrate. The structure that ships:

FUNCTION	OWNS	WEEKLY ARTIFACTS
CMO	Orchestration, vision, resource allocation. Sets strategy and the culture of rapid experimentation that AEO requires. Decides which buyer prompts to invest in winning and which to concede.	AEO Baseline reread quarterly. AI citation share-of-voice tracked in the monthly executive dashboard. Founder LinkedIn post cadence enforced.
Product Marketing / Content Marketing	Content audit, prompt strategy, competitive positioning, FAQ content creation. Owns the answer-side discipline: what gets written, what gets cited, what the corpus says about the category.	FAQ-content production calendar (5–10 pieces per quarter). "Alternatives to [competitor]" page maintained. G2 discussion thread seeding.
SEO / AEO (Growth)	Technical optimization, distribution, cross-platform publishing, measurement. Owns the surface-side discipline: schema, bot-accessibility, LLM referral tracking, syndication to G2/marketplaces/newswires.	GA4 LLM referral dashboard. HubSpot/Webflow AEO grader scores. Distribution checklist run on every content piece.
Customer Marketing	Review generation engine, advocacy program, Reddit/community presence. Owns the consensus-side discipline: getting authentic customer voice into the trusted citation surfaces (G2, Capterra, Reddit, podcast appearances, customer-led video).	NPS-tied review collection program. Tier-1 champion roster. Reddit AMA cadence. Customer-led FAQ video library.

The orchestration discipline — quarterly AEO review

Once a quarter, the CMO runs the AEO baseline (a 60-second exercise) for the company against the same 20–30 buyer prompts the team committed to investing in. The output is shared with the four function owners in a 45-minute review.

The review answers four questions: (1) Which prompts did we win this quarter (mentioned with positive sentiment)? (2) Which prompts did we lose and to whom? (3) Which of the four functions needs more resourcing next quarter? (4) Which two prompts is each function committing to win in the next 90 days?

The strategic discipline AEO requires: keep strategy in-house, use agencies and tooling for execution support only. The discipline is still being defined; a culture of rapid experimentation matters more than a perfect plan.

The meetings every CMO should own.

The CMOs who survive aren't the ones who run the most campaigns. They're the ones who run the right meetings on cadence, with the right people in the room, reviewing the right data. Three meetings matter more than any other. Own these three and your role becomes structural — you're the operator the rest of the GTM motion organizes around.

The three-meeting stack

Weekly Pipeline Call. Monthly Pipeline & Revenue Council. Quarterly Revenue Handbook (SLA). Three meetings, three time horizons. Together they make marketing the function that runs on rhythm instead of crisis.

Weekly Pipeline Call — the baller move that earns the CMO seat

This is the meeting most marketing leaders avoid because it feels like sales territory. It’s the meeting the best ones run because it makes them indispensable. The CMO who hosts the weekly pipeline call is the CMO the head of sales fights to keep.

WEEKLY PIPELINE CALL — RUN OF SHOW

Cadence: Every week. Tuesday or Wednesday, 45 minutes. Same time, same Zoom link, no excuses.
Attendees: CMO, head of sales, head of demand gen, head of BDR/SDR, RevOps lead. Optional: CS lead if expansion pipeline is in play.
Agenda — section 1 (15 min) · Pipeline health: Coverage ratio against quarter goal. Net-new opps this week. Aging deals at risk. Movement from SAL → SQO → Closed Won.
Agenda — section 2 (15 min) · Channel performance: Conversion rate by source. Days-to-close by source. ACV by source. Where the leakage is.
Agenda — section 3 (15 min) · Accountability: Who owns which gap. Specific commitments by name, with a deadline before the next call. RevOps tracks them.

Two principles make this meeting work. First, never make it an operational check-in — that's what your team's standups are for. Make it a meeting where leaders are held accountable for moving numbers. Second, marketing leads often convert 30–45 days faster than referrals; show that math every call. It changes how the head of sales talks about marketing inside their own forecast meetings.

Monthly Pipeline & Revenue Council — the alignment meeting

The weekly pipeline call is tactical. The monthly Pipeline & Revenue Council is the strategic version: GTM managers presenting progress against quarterly initiatives, owned by one person, supported by two or three.

MONTHLY PIPELINE & REVENUE COUNCIL — STRUCTURE

Cadence: First Friday of every month, 90 minutes.
Who's in the room: Direct reports to the GTM executive team — not the executives themselves. One meeting owner, two or three supporters running specific sections.
What's on the agenda: Quick wins that are scaling. What isn't working and the proposed adjustment. Progress against the three quarterly initiatives that matter most.
Success criteria: Healthy and productive alignment. Booking targets met or win rates increased. Efficient TOFU growth and sourced-pipeline creation targets hit.
What to avoid: This meeting cannot become a status update. If nobody's commitments change as a result of the meeting, the meeting was a waste of 90 minutes.

Quarterly Revenue Handbook — the SLA that becomes the playbook

The Quarterly Revenue Handbook is sometimes called the GTM SLA. It's the document that codifies — for one quarter at a time — who does what, when, with what definitions. The reason every quarter rather than annually: sales realities shift every 90 days. The handbook prevents the "we never agreed to that" arguments that derail Q+1.

QUARTERLY REVENUE HANDBOOK — WHAT'S INSIDE

Segmentation: which accounts belong to which seller, by ICP tier, ACV band, and vertical
Pricing & packaging: current pricing, current packaging, what's being tested, what's grandfathered
Follow-up SLAs: marketing-sourced lead → BDR contact within X hours; SAL → AE follow-up within Y hours; demo no-show → re-engagement sequence within Z days
Roadmap delivery: what's shipping this quarter, when, and what the GTM motion is around each release
Feedback loops: how the field tells product what's working and not working; how product tells marketing what's coming; how marketing tells the field what's resonating
Definitions: MQL, SAL, SQO, ICP-fit account, lost-reason taxonomy — all locked for the quarter
Approval gates: who signs off on pricing exceptions, discounting beyond X%, custom contract terms

The Enablement Stack — what your team has to be world-class at

Enablement is the work that turns the playbook into pipeline. Most CMOs under-resource it because it doesn't ship customer-facing artifacts. The teams that win run a four-layer enablement stack — every layer staffed, every layer audited quarterly.

LAYER	WHAT IT IS	OWNER	CADENCE
Industry	Foundational knowledge about the industry you serve — vertical dynamics, buyer language, regulatory shifts, current macro pressures	PMM + Field Marketing	Quarterly industry refresh + monthly news briefing
Product	How to navigate and use the product — for SDRs (the demo flow), AEs (the deep dive), customers (onboarding)	PMM + Product	Per-release enablement + monthly skills sessions
Use Case	Everything about your personas — pains, success criteria, objections, common questions, social proof per persona	PMM + Customer Marketing	Quarterly persona refresh + per-launch update
GTM	Strategic initiatives — demo scripts, call coaching, launches, competitive battlecards, win/loss patterns	PMM + Sales Enablement	Weekly battlecard updates + monthly win/loss review

The enablement stack also needs three operational tools: a call-recording and coaching system (Gong or Chorus for mid-market+; Avoma or Fathom for SMB and PLG teams), a content management platform with tracking, and AI for quick outline generation and learning dissemination. The tools aren't the discipline. The discipline is that someone is paid to own each layer and report on it monthly.

Your Operating Cadence

The meetings you actually run, with named owners. Saves to your Brief so every Ops & Governance prompt knows your real rhythms.

Weekly Pipeline Call — day & time, owner

Monthly Pipeline & Revenue Council — date pattern, meeting owner

Quarterly Revenue Handbook — review owner, deadline pattern

Enablement layers you have explicit owners for (comma-separated: Industry, Product, Use Case, GTM)

Saved as [WEEKLY PIPELINE CALL], [MONTHLY PIPELINE COUNCIL], [QUARTERLY REVENUE HANDBOOK], [ENABLEMENT LAYERS] across the site.

The additional cadence menu — for larger teams that need more rhythm

The three-meeting stack above is the operator essential. Every CMO runs those three or the function loses rhythm. The table below is the menu of optional cadence to add once team size, organizational complexity, or cross-functional load demands it. Pick from this list; don't run all of it.

REQUIRED VS OPTIONAL

Required (above): Weekly Pipeline Call. Monthly Pipeline & Revenue Council. Quarterly Revenue Handbook. Those three carry the function.

Optional (below): Add as the team grows past ~15 marketing headcount or when cross-functional coordination starts breaking down between the required meetings. Smaller teams cover most of this in standup + Slack.

MEETING	CADENCE	PARTICIPANTS	AGENDA	WHEN TO ADD
Marketing Weekly Standup	Weekly (Monday)	Full marketing team	Sprint priorities, blockers, campaign status	Once the team exceeds ~8 people and Slack standups stop landing
Marketing <> Sales Sync	Weekly (Wednesday)	CMO, Demand Gen lead, CRO, BDR Lead	Pipeline coverage, MQL quality, campaign alignment	When the Weekly Pipeline Call needs a working-level partner meeting underneath it
Content Review	Bi-weekly	Content team + PMM	Drafts in review, upcoming calendar, performance review	Once you have 2+ writers + a PMM partner on the editorial calendar
Campaign Retrospective	Post-campaign (within 2 weeks)	Campaign owner + Demand Gen + RevOps	Results vs. goals, learnings, recommendations	Always run for campaigns over $50K spend; optional below that band
Marketing Leadership Sync	Monthly	CMO + Directors	OKR progress, budget review, headcount, strategy pivots	Once you have 3+ Director-level reports
GTM Leadership Sync	Monthly	CMO + CRO + CPO + CEO	Pipeline coverage, revenue trends, segment performance, go-forward alignment	Series B+; before that the Monthly Pipeline Council usually covers this
Marketing QBR	Quarterly	Full marketing team + Sales leadership	Q results, Q+1 plan, OKR review, budget reforecast	Always — but at smaller teams this folds into the Quarterly Revenue Handbook session

Marketing OKR Framework

Marketing Objectives and Key Results (OKRs) translate company revenue targets into measurable marketing outcomes. OKRs are set annually, reviewed quarterly, and graded on a 0.0–1.0 scale where 0.7 is success.

MARKETING OKR STRUCTURE

Objective 1: Build a predictable pipeline engine.

KR1: Achieve $[X]M in marketing-sourced pipeline in FY.
KR2: Maintain CPL below $[Y] across Tier 1 channels.
KR3: Reach [N] MQLs per month by Q4.

Objective 2: Establish [COMPANY NAME] as the category leader.

KR1: Achieve >25% share of voice in Tier 1–2 press.
KR2: Secure [N] Tier 1 media placements per quarter.
KR3: [N] inbound demo requests per month from organic / direct.

Objective 3: Drive customer expansion and retention through marketing.

KR1: Produce [N] customer case studies per quarter.
KR2: Achieve [N]% of expansion pipeline influenced by customer marketing.
KR3: NPS uplift of +[X] points from customer-communication programs.

Objective 4: Build a high-performance, data-driven marketing organization.

KR1: 100% of campaigns launched with approved campaign brief and UTM tracking.
KR2: Full attribution model live in BI by Q2.
KR3: Marketing tech stack audit complete; [N] redundant tools eliminated.

Marketing Compliance & Legal Guardrails

Email regulation spans the US CAN-SPAM Act, Canada's Anti-Spam Legislation (CASL), the European Union's General Data Protection Regulation (GDPR), and California's Consumer Privacy Act (CCPA). Build the suppression and consent infrastructure for the strictest of these and the rest are covered.

COMPLIANCE AREA	REQUIREMENTS	OWNER	REVIEW FREQUENCY
Email Marketing (CAN-SPAM / CASL / GDPR)	Unsubscribe in every email; physical address; suppression list maintained; explicit consent required for CASL/GDPR jurisdictions	Marketing Ops + Legal	Quarterly audit
Customer References & Testimonials	Written permission required before any customer name, logo, or quote is used publicly; separate permission for press vs. website	PMM + Legal	Each customer story approval
Competitive Claims	All comparative claims must be factually substantiated and reviewed by Legal before publication or distribution	PMM + Legal	Each campaign with competitive content
Data Collection (Forms)	Privacy policy linked on every form; GDPR consent checkbox for EU contacts; data retention policy documented	Marketing Ops + Legal	Annual audit + at platform change
Advertising Standards	All paid ads must comply with platform-specific ad policies (Google, LinkedIn, Meta) and industry advertising standards	Demand Gen + Legal	Each new campaign launch
PR & Media Claims	Revenue claims, market share, and customer count claims must be reviewed by Finance + Legal before press release distribution	CMO + Legal + Finance	Each press release

Appendix

A. Review-Platform Request Email Template

TEMPLATE — REVIEW REQUEST (works for G2, Gartner Peer Insights, TrustRadius, KLAS, or any platform-equivalent)

Subject: Would you share your experience on [PLATFORM]?

Hi [FIRST NAME],

Given the results you've seen with [COMPANY NAME] — [reference a specific outcome] — I wanted to ask a quick favor.

Would you be willing to share your experience on [PLATFORM — G2 / Gartner Peer Insights / TrustRadius / your category's review site]? It takes under 5 minutes, and your story helps similar teams find the right solution.

[Direct link to the specific platform profile page]

No pressure — and thank you for being a fantastic partner.

[YOUR NAME]

Honor each platform's incentive policy — G2 allows standard gift-card programs; Gartner Peer Insights prohibits incentives entirely; TrustRadius and KLAS have their own rules. Check before offering anything.

B. Content Pre-Publish Checklist

Target keyword identified and present in title, H1, and meta description.

At least one internal link to a related piece of content or key landing page.

Customer quote, stat, or social proof included.

CTA included and aligned to funnel stage (top = download, mid = webinar, bottom = demo).

Brand voice reviewed — matches tone guide in Module 1.

Legal/compliance check for any customer references or claims.

OG tags and featured image set for social sharing.

C. Campaign Brief Template

CAMPAIGN BRIEF — REQUIRED FIELDS

Campaign name
Goal (pipeline / MQLs / brand)
Target audience (ICP segment + persona)
Campaign dates
Budget
Channels (list all)
Key message
Primary CTA
Success metrics (and targets)
Dependencies (content needed, sales enablement, etc.)
CRM campaign tag

D. Event SLA Checklist

FUNCTION	SLA	OWNER
Lead Processing	Net new leads in CRM within 48 hours	RevOps / Marketing Ops
Hot Lead Follow-Up	AE or BDR contact within 24 hours of event	Sales / BDR
Post-Event Email	Sent to attendees within 2 business days	Marketing
Nurture Enrollment	Leads enrolled in sequence within 3 business days	Marketing
Pipeline Report	Published within 7 business days post-event	RevOps

Appendix E: Marketing Glossary & Key Definitions

E.1 Lead & Pipeline Definitions

TERM	DEFINITION
Visitor	An anonymous individual who visited the [COMPANY NAME] website or a content asset. Not yet a known contact in CRM.
Lead / Contact	A named individual in CRM with at minimum an email address. Has not yet been scored or qualified.
MQL — Marketing Qualified Lead	A lead that has reached a threshold score (behavioral + firmographic) indicating sufficient intent to be ready for Sales Development review. Defined and agreed by Marketing + Sales jointly.
SAL — Sales Accepted Lead	An MQL that a BDR/SDR has reviewed and accepted as meeting the ICP criteria (right company, right persona, enough intent). The handoff gate.
SQL — Sales Qualified Lead	A lead that has been contacted, an ICP fit confirmed, and an initial discovery or qualification call booked. SQL = a real conversation has begun.
PQL — Product Qualified Lead	A lead who has taken a product action (free trial signup, sandbox activity, key feature usage) indicating product intent. Specific to PLG motions.
Opportunity	A named deal in the CRM pipeline representing a specific purchase evaluation at a specific account. Requires: named contact + estimated deal size + close date.
Pipeline	The total dollar value of open Opportunities at any given stage. 'Total pipeline' = all open stages. 'Stage 2+ pipeline' = past qualification.
Pipeline Coverage Ratio	Total pipeline / Revenue target. Best practice: 3–5× pipeline coverage heading into a quarter.

E.2 Funnel & Attribution Metrics

TERM	DEFINITION
Marketing-Sourced Pipeline	Pipeline where the first-ever engagement with the account originated from a marketing program. The strictest measure of marketing's pipeline contribution.
Marketing-Influenced Pipeline	Pipeline where any marketing touchpoint occurred at any point in the account's journey to becoming an opportunity. Broader than sourced.
First-Touch Attribution	100% of credit assigned to the first marketing program touched. Best for measuring awareness channels.
Last-Touch Attribution	100% of credit assigned to the last marketing program before conversion. Overweights bottom-funnel programs.
Multi-Touch / Linear Attribution	Revenue credit distributed equally across all marketing programs that were touched during the buyer journey. The fairest view for comparing channel ROI.
W-Shaped Attribution	40% credit to first touch, 40% to lead conversion touch, 20% distributed across all other touches. Balances awareness and conversion measurement.
Conversion Rate (CVR)	% of a population that completes a desired action (Visitor → Lead, MQL → SAL, SAL → SQL, SQL → Won).
Funnel Velocity	The speed at which leads/opps move through the funnel. Tracked as average days per stage. Increasing velocity = improving qualification quality or sales process.
Churn Rate	% of customers who cancel their subscription in a period. Annual Churn Rate = (Churned ARR / Starting ARR) × 100.
NRR — Net Revenue Retention	(Starting ARR + Expansion – Contraction – Churn) / Starting ARR × 100. The single most important metric for SaaS business health. World-class >120%.

E.3 Channel & Campaign Terms

TERM	DEFINITION
CAC — Customer Acquisition Cost	Total Sales + Marketing spend / total new customers acquired in a period. Separate Marketing CAC = Marketing spend only / new customers from marketing-sourced pipeline.
CPL — Cost Per Lead	Total channel spend / total leads generated by that channel. Used to compare efficiency across demand gen channels.
ROAS — Return on Ad Spend	Revenue generated / Advertising spend. More direct than ROI; used primarily for paid acquisition channels.
Organic Traffic	Website visitors who arrived via unpaid channels: search engines (SEO), direct URL entry, social shares, or referral links.
Paid Traffic	Website visitors who arrived via a paid channel: paid search (SEM), paid social, display advertising, sponsored content.
Dark Social	Traffic and sharing that occurs in private or unmeasurable channels: Slack, WhatsApp, email forwards, LinkedIn DMs. Cannot be tracked via UTMs.
ICP — Ideal Customer Profile	The firmographic and behavioral characteristics of the type of company most likely to buy, renew, and expand with [COMPANY NAME]. Defines targeting for all GTM programs.
Buyer Persona	A semi-fictional representation of a specific buyer type within an ICP account, based on real data and research. Defines messaging, content, and channel strategy.
ABM — Account-Based Marketing	A B2B strategy that treats individual high-value accounts as markets of one, with personalized outreach across multiple channels targeting specific buying committee members.

Confidential — Internal Use Only Page

SOURCE	TYPE	REQUIRED
/operator-brief.md	Markdown	Your full Operator Brief — primary brand context. Read on every run.
utm-convention.md	Markdown	format + regex
naming-convention.md	Markdown	campaign/asset naming
campaigns/<campaign>/assets.md	Markdown	links, UTMs, asset names

The agent

Ops & Governance Pipeline Council Agent.

For teams operating in AI Operating Model territory, the work above runs on a named agent that watches the inputs on cadence and surfaces drift before the human team notices.

Pipeline Council Agent

Stewards the weekly Pipeline Council AND the quarterly AEO Council — the two cross-functional meetings where Marketing + Sales + RevOps + CFO (weekly pipeline) and Marketing + PMM + SEO/AEO + Customer Marketing (quarterly AEO review) align on the math at both ends of the funnel. Drafts the agendas, distributes the pre-reads, captures decisions, tracks follow-through.

Who is this agent

Identity card

NamePipeline Council Agent

RoleCross-functional pipeline meeting operations — the ‘does anything actually get decided?’ layer

OwnerDirector of Marketing Operations (with CRO co-ownership)

Reports toVP Marketing + CRO

Versionv0.5 (supervised)

SurfaceClaude Project + Slack + Postgres (decision log + action tracker)

Output target/council/agendas/, /council/pre-reads/, /council/decisions/, /council/action-tracker.md

Review cadenceWeekly council operation; monthly action-tracker audit; quarterly cadence + format review

Mission

Operate two cross-functional councils as programs, not as calendar invites — the weekly Pipeline Council AND the quarterly AEO Council. Pipeline Council: draft the weekly agenda from current pipeline math + stuck deals + leadership concerns. Distribute the pre-read 24 hours ahead so the meeting starts with shared context. Capture decisions with named owners + due dates. Track follow-through. AEO Council (quarterly): orchestrate the 4-function review across CMO + PMM/Content + SEO/AEO Growth + Customer Marketing. Pull the AEO Baseline result, the prompts won/lost, the citation share-of-voice trend, and the resourcing requests. Document which 2 prompts each function commits to winning in the next 90 days. Be the agent that prevents the recurring ‘wait, didn’t we decide that last week?’ failure mode at BOTH cadences.

Goals & KPIs the agent moves

Leading indicators — the agent controls these

Pre-read drafted, approved by VP Marketing (or delegate) within SLA, and distributed ≥ 24 hours before council≥ 95% on-time, 100% human-approved before send

Decisions captured with named owner + due date in the same session and posted to the action log within 2 hours of council close≥ 95%

Lagging indicators — downstream outcomes with review triggers

Action close-out rate (decisions resolved by the next council). Trigger: 3 consecutive councils below 60% pages the VP Marketing for council-discipline review.≥ 70%

Stuck-deal cycle time after council intervention (days to next forward motion). Trigger: median above 14 days for 2 consecutive months pages the VP Marketing + Head of RevOps for joint review.Median ≤ 10 days

What it does

Task list

Weekly council T-2 days Pull the current pipeline math from Pipeline Math Agent. Identify the 3–5 highest-stakes items for council attention.
Weekly council T-2 days Surface stuck deals: pipeline items in stage > 1.5× median time-in-stage. Surface to deal owner.
Weekly council T-1 day Draft the agenda. Each item: context, decision required, recommended decision, deal/account references.
Weekly council T-1 day Distribute the pre-read package (agenda + Pipeline Math digest + Account Intel snapshots for named accounts).
Weekly council day Capture decisions in real-time. Each: decision text, named owner, due date, success criteria.
Weekly council day Post the decision log to Slack #pipeline-council immediately after.
Weekly council T+1 day Update the action tracker. Send personalized follow-ups to each named owner.
Daily T+2 to T+6 Track action progress. Nudge unstarted actions at T+3. Escalate at T+5.
Monthly Action-tracker audit: close-out rate, escalation rate, repeat-decisions rate. Surface to VP Marketing + CRO.
Quarterly Council cadence + format review with VP Marketing + CRO. Are we discussing the right things? Is the cadence right?
Event When a decision contradicts a prior council decision, surface the contradiction immediately.
Event When an action stalls > 14 days, escalate to that owner’s leader.

Schedule grid

Task	Frequency	Duration	Output goes to
Weekly pre-read drafting (T-1 day)	Weekly Thu 14:00	~90 min	Council attendees (VP Marketing + CRO + CFO + Sales Director + Head PMM)
Weekly council (T-day)	Weekly Fri 09:00	60 min (scheduled)	Council members
Weekly decision log post (T-day)	Weekly Fri 10:00	~15 min	Slack #pipeline-council + named owners
Weekly action follow-up (T+1 day)	Weekly Mon 09:00	~30 min	Named owners (personalized)
Daily action progress watch	Daily 17:00	~10 min	Named owners; escalation to leaders if stuck
Monthly action-tracker audit	Monthly 1st	~60 min	VP Marketing + CRO + Director MarOps
Quarterly cadence + format review	Quarterly Q-1 days	~90 min	VP Marketing + CRO + CFO

Triggers

Scheduled (cron-style):

Schedule	What it runs
`0 14 * * 4`	Weekly pre-read drafting (Thursday)
`0 10 * * 5`	Weekly decision log post
`0 9 * * 1`	Weekly action follow-up (Monday)
`0 17 * * *`	Daily action progress watch
`0 9 1 * *`	Monthly action-tracker audit

Event-driven:

Event	What it runs
Action stalled > 14 days	Escalate to owner’s leader within 24 hours
Decision contradicts prior decision	Surface contradiction immediately in council
Pipeline Math Agent flags coverage drop	Add to next council agenda as P1
Repeat decisions in 3 consecutive councils (re-discussing same item)	Surface to VP Marketing + CRO for cadence review
Council member misses 2+ consecutive councils	Page Director MarOps for delegate-rotation

Who it works with

Inputs

Source	Type	Cadence	Required?
Operator Brief (Section 7)	Markdown	Read on quarterly review	Required
Pipeline Math Agent daily snapshot + weekly digest	JSON + Markdown	T-2 days before council	Required
CRM opportunity full state (stuck deal detection)	API + warehouse	T-2 days	Required
Account Intel Hub records for named accounts	JSON	T-1 day	Required
Prior council decision log + action tracker	Postgres	Continuous	Required
Council attendees + roles registry	YAML	Continuous	Required — core config
Calendar integration (Google / Outlook)	API	Continuous	Required for council scheduling

Outputs

Output	Format	Target path	Audience
Weekly council agenda	Markdown	/council/agendas/YYYY-WW.md	Council attendees
Weekly pre-read package	Markdown + linked artifacts	/council/pre-reads/YYYY-WW.md (Slack DM to attendees)	Council attendees
Weekly decision log	Markdown + Slack post	/council/decisions/YYYY-WW.md + Slack #pipeline-council	Slack channel + named owners
Action tracker (continuous)	Markdown table	/council/action-tracker.md	VP Marketing + CRO + named owners
Personalized action follow-ups	Slack DM	Slack DM per owner	Named owners
Monthly action audit	Markdown	/council/audits/YYYY-MM.md	VP Marketing + CRO + Director MarOps
Quarterly cadence review	Markdown	/council/quarterly/Q<n>.md	VP Marketing + CRO + CFO

↑ Upstream — agents/sources that feed this one

Pipeline Math Agent. Primary input for agenda items + pipeline-status context.
Account Intel Hub. Per-account context for named-deal discussion.
Signal Router. Routes stuck-deal signals + escalations.
Pricing Intelligence Agent. Surfaces price-related stuck deals.
ABM Account Researcher. Surfaces tier-1 account opportunities for council attention.

↓ Downstream — agents/humans that consume its output

Council members (VP Marketing + CRO + CFO + Sales Director + Head PMM). Receive pre-read + agenda + decision log.
Named action owners (humans). Receive personalized follow-ups + progress tracking.
Owners’ leaders (humans). Receive escalations on stalled actions.
Best-in-Class Assessment Agent. Receives council operational data for AOS governance dimension.
Executive Comms Agent. Receives quarterly council patterns for the Board narrative.

Human escalation paths

Trigger condition	Escalate to	Within
Pre-read missed T-1 distribution	Director MarOps + VP Marketing	Immediate
Council ran > 90 min on a 60-min scheduled meeting 2+ weeks running	VP Marketing + CRO	Same week (cadence issue)
Action close-out rate < 50% in a month	VP Marketing + CRO + Director MarOps	Same month
Same decision repeated 3+ consecutive councils	VP Marketing + CRO	Immediate
Council member missed 3+ consecutive councils	VP Marketing	Same week

How to build it

System prompt

You are the Pipeline Council Agent for [COMPANY]. YOUR JOB Operate the weekly Pipeline Council as a program. Draft agendas. Distribute pre-reads 24h ahead. Capture decisions with owners + due dates. Track follow-through. Prevent "wait, didn't we decide that last week?" forever. INPUTS (always read in this order) 1. /operator-brief.md (Section 7) 2. /pipeline-math/daily-snapshot.json (today's state) 3. /pipeline-math/digests/YYYY-WW.md (last weekly) 4. /council/action-tracker.md (open actions) 5. /council/attendees.yaml (members + roles) 6. /crm/opportunities-stuck.json (stuck deal detection) OUTPUTS - /council/agendas/YYYY-WW.md - /council/pre-reads/YYYY-WW.md (T-1 day) - /council/decisions/YYYY-WW.md (T-day) - /council/action-tracker.md (continuous) AGENDA ITEM STRUCTURE 1. Context (3-5 lines: what's the situation) 2. Decision required (1 line: what needs deciding today) 3. Recommended decision (1-2 lines: what the data says) 4. Referenced deals/accounts (linked) 5. Estimated time (5 / 10 / 15 min) DECISION CAPTURE STRUCTURE Each decision: { text, named_owner, due_date, success_criteria } RULES 1. Pre-read must distribute T-1 day before council. Hard rule. 2. Every decision requires named owner + due date. No "team will follow up." 3. Surface prior-decision contradictions immediately - don't let council re-decide what was decided 2 weeks ago. 4. Action follow-ups personalized per owner. 5. Escalate stalled actions (>14 days) to owner's leader. 6. Stale actions (>30 days) surface for explicit close-out or drop decision. ESCALATION - Pre-read missed deadline: page Director + VPM immediately. - Same decision 3+ councils: page VPM + CRO immediately.

Tools & integrations

Platform / tool	Used for	Required?
Claude Project + Postgres (decision log + action tracker)	State + audit trail	Required
Slack API	Real-time decision posts + personalized follow-ups	Required
Calendar API (Google / Outlook)	Council scheduling	Required
Salesforce / HubSpot API	Stuck-deal detection + opportunity context	Required
Account Intel Hub API	Per-account context for named-deal items	Required
Pipeline Math Agent API	Primary input for agenda	Required
Linear / Jira API	Action item tickets for follow-through	Optional but recommended

Guardrails — what it must not do

Never publish council decisions outside the marketing + sales + finance leadership scope without VP Marketing approval.
Honor named-deal confidentiality — some accounts may not be appropriate for broad sharing.
Never modify prior decisions autonomously. Decision revisions require explicit council action.
Never let council time exceed scheduled length without VP Marketing acknowledgment.
Honor council member calendar — if quorum can’t make it, reschedule rather than proceed.
Never use council attendance data for individual performance management.
Never let an action stall > 30 days without explicit close-out or drop decision.

Evals + hallucination defense

Evals — output quality checks:

Pre-read on-time. Weekly: pre-read distributed T-1 day. Target 100%.
Decision discipline. Weekly: % of decisions with named owner + due date + success criteria. Target ≥ 95%.
Close-out rate. Monthly: % of decisions closed by next council. Target ≥ 70%.
Recurrence catch. Quarterly: % of recurring decisions surfaced as such within the same council. Target 100%.

Hallucination defense — specific checkpoints:

Pipeline data in pre-reads must cite Pipeline Math Agent snapshot + date.
Stuck-deal claims must cite specific opportunity IDs + stage timelines.
Decision log must capture verbatim decisions, not paraphrased.
Action close-out claims must cite the resolution artifact (PR merged, contract signed, etc.).
When prior decisions are referenced, cite the council date + decision ID.

Maturity curve + first-run checklist

v0.1 — Manual-assistDirector MarOps drafts agendas with agent assistance. Useful from day 1 to formalize the cadence.

v0.5 — SupervisedWeekly cycle autonomous (agenda + pre-read + decision log + follow-ups). Director MarOps + VP Marketing review. Default ship state.

v1.0 — Semi-autonomousAfter 90 days clean evals + close-out rate ≥ 70%, agent auto-drafts pre-reads and pings Director MarOps in Slack for one-line approval before pre-reads land in the CRO + CFO + CEO inboxes. Council operation always human-led. Hard rule: no pre-read reaches a senior-executive inbox without a named human approver on the draft.

First-run checklist — 5 steps from spec to running agent:

Author the attendees + roles registry with VP Marketing + CRO.
Wire Pipeline Math + CRM + Account Intel Hub + Slack + Calendar inputs.
Run the first 4 weekly councils with agent assistance + Director MarOps as facilitator.
Turn on full autonomous operation. Subscribe VP Marketing + CRO to weekly decision log + monthly audit.
Schedule quarterly cadence review. Log every run in /council/agent-log.md.

Ops & Governance — the strategic foundation.

STRATEGY & PROCESS

Content Governance Framework

Content Calendar Management

Marketing Technology Stack

Marketing Data Governance

Campaign Tagging & UTM Governance

AEO is cross-functional — the 4-function ownership model.

The meetings every CMO should own.

Weekly Pipeline Call — the baller move that earns the CMO seat

Monthly Pipeline & Revenue Council — the alignment meeting

Quarterly Revenue Handbook — the SLA that becomes the playbook

The Enablement Stack — what your team has to be world-class at

Your Operating Cadence

The additional cadence menu — for larger teams that need more rhythm

Marketing OKR Framework

Marketing Compliance & Legal Guardrails

Paste-ready prompts for Ops & Governance.

Martech audit

UTM convention

OKR template

The agent for Ops & Governance.

Five steps from spec to running agent.

UTM & NAMING LINTER

Agent card

Operating profile

System prompt

Inputs

Outputs

Evals

Failure modes

Hallucination defense

Ops & Governance Pipeline Council Agent.

Pipeline Council Agent

Identity card

Mission

Goals & KPIs the agent moves

Leading indicators — the agent controls these

Lagging indicators — downstream outcomes with review triggers

Task list

Schedule grid

Triggers

Inputs

Outputs

↑ Upstream — agents/sources that feed this one

↓ Downstream — agents/humans that consume its output

Human escalation paths

System prompt

Tools & integrations

Guardrails — what it must not do

Evals + hallucination defense

Maturity curve + first-run checklist