KPIs & Measurement

The framework — strategy first

KPIs & Measurement — the strategic foundation.

STRATEGY & PROCESS

Every marketing activity is accountable to revenue. This work defines the measurement framework from top-of-funnel brand metrics to bottom-of-funnel pipeline attribution. And it starts with the discipline most CMOs miss in their first 90 days: own a number that ties to revenue, not a number that keeps score.

Own a Number — the discipline that protects the CMO job.

The marketing leaders who get fired aren't the ones missing creative goals. They're the ones who can't tell the CEO, in one sentence, what number they own and what it's worth. The board can't fire you for missing the number if you don't own one. They also can't promote you, defend you, or budget you. Ownership is the precondition for credibility.

The rule, in one line

Move from numbers that keep score to numbers that drive better actions. A score-keeping number is "we generated 384 Marketing Qualified Leads (MQLs) this quarter." A driving-action number is "we generated $4.6M in marketing-sourced pipeline against our $4.4M goal — 121%." One gets the head nod. The other gets the budget renewed.

The number you own should tie directly to revenue. Two options work and one option doesn't:

Bookings & Pipeline (best). Marketing-sourced and marketing-influenced pipeline, with a direct attribution model if your sales cycle is under 90 days. This is the metric the Chief Financial Officer (CFO) will fight to keep on the board deck.
Pipeline-only (acceptable). If your sales cycle is over 90 days, attributing bookings to marketing's first-touch becomes noisy. Own pipeline instead and align with sales on attribution split.
MQLs (insufficient). An MQL number tells the CFO nothing they care about. The Chief Marketing Officer (CMO) who reports MQLs to the board is the CMO who gets cut when the budget tightens.

The pipeline model — what to build with finance

This is the conversation that earns you the seat. Work with finance and RevOps to build a 12-month pipeline-and-bookings model. The model has three inputs and one output:

THE PIPELINE FORMULA

Quarterly bookings goal × Sales cycle / Average win rate × Pipeline-to-bookings coverage = Quarterly pipeline target

Worked example (mid-market sales-led): $10M bookings goal · 6-month sales cycle · 25% win rate · 3× coverage = $30M in pipeline needs to be in the funnel at any moment to hit the number.

THE INPUTS BY ACV + MOTION — DON'T ANCHOR ON THE MID-MARKET EXAMPLE

Win rate and coverage swing 2–4× across motion and ACV bands. Anchoring on the 25% × 3× example will under-build pipeline at enterprise and over-build at SMB. Use this table to size yours:

SEGMENT	SALES CYCLE	WIN RATE (FROM QUALIFIED OPP)	COVERAGE RATIO
Strategic ($250K+ ACV)	9–12 months	15–22%	4–5×
Enterprise ($75K–$250K)	6–9 months	20–28%	4–5×
Mid-market ($25K–$75K)	3–6 months	25–35%	3×
SMB transactional (<$25K Annual Contract Value, or ACV, sales-led)	1–3 months	25–40% per opp · 8–18% from MQL	2–3×
Product-Led Growth, or PLG (any ACV)	Not the right metric	Track free→paid (3–8%) + Product Qualified Lead (PQL) → PAID conversion	Not the right metric — track PQL volume against activation target

Pre-PMF / PMF at any motion: add a full turn of coverage (3× → 4×, 4× → 5×) until you have four clean quarters of conversion data. Variance kills you when the model is young.

If you don't have enough data to model precisely yet, give an educated guess and schedule a quarterly review to refine. The model that exists and is wrong is better than the model that doesn't exist. The discipline of building it forces alignment with the CFO and head of sales — which is the actual deliverable.

The weekly demand forecast — your inbox lifeline

The single most under-rated comms artifact in the marketing function. Send it every Monday morning to your Executive Leadership Team (ELT) — Chief Executive Officer (CEO), CFO, head of sales, head of Customer Success (CS). Treat it like a newsletter. Build subscribers. Make it the document your CFO is looking for before their 9am.

WEEKLY DEMAND FORECAST — TEMPLATE

Subject line: "Demand Forecast · Week of [DATE] · Sunny / Partly Cloudy / Rainy"
Weather Forecast: One sentence on the week ahead. Sunny = ahead of plan. Partly Cloudy = on plan with risk. Rainy = behind plan, here's the action.
Pipeline indicators (leading): this week's MQL count, demo requests, key account engagement, intent signals.
Pipeline indicators (lagging): Sales Accepted Lead (SAL) conversion, opportunity creation, deal velocity.
Logos from the prior week: net-new logos closed, by segment and ACV. Names if you can say them.
Conversation of the week: a customer or prospect quote that frames the next bet (recording link if you have one).
Updates from business unit leaders: 1–2 sentences from sales, CS, product — what changed.

The weekly demand forecast is what makes you visible. It's the difference between "the marketing team" and "the marketing function the CEO defends in board meetings."

Your Pipeline Model

The numbers that drive your model. Saves to your Brief — every measurement and exec-comms prompt on the site will use these.

Quarterly bookings goal ($)

Sales cycle (months)

Average win rate (%)

Pipeline-to-bookings coverage

Your "number you own" — the one revenue-tied metric you'll defend to the board

Saved as [QUARTERLY BOOKINGS GOAL], [SALES CYCLE], [WIN RATE], [PIPELINE COVERAGE], [NUMBER OWNED] across the site.

North Star Metrics

METRIC	DEFINITION	TARGET	CADENCE
Marketing-Sourced Pipeline	New pipeline where first touch was a marketing program	[X]% of total pipeline	Weekly
Marketing-Influenced Pipeline	Open/closed opps that touched any marketing program	[Y]% of total pipeline	Monthly
Cost per MQL	Total marketing spend / qualified leads generated	<$[Z]	Monthly
MQL to SQL Conversion Rate	% of MQLs accepted and converted by Sales	>25%	Monthly
Marketing CAC	Marketing spend per new customer acquired	Reduce [X]% YoY	Quarterly

Channel-Level KPIs

CHANNEL	PRIMARY KPI	BENCHMARK TARGET
Content / SEO	Organic sessions + keyword rankings + content-attributed MQLs	\+20% organic traffic QoQ
Email	Open rate + click rate + email-attributed MQLs	Open >30%, Click >4%
LinkedIn Organic	Impressions + engagement rate + follower growth	>3% avg engagement rate
LinkedIn Paid	CPL + Lead Gen Form conversion	CPL <$[X], LGF rate >12%
Google Paid Search	CTR + CPC + demo conversion rate	CTR >3% (brand), CPC <$[X]
Events	Pipeline generated vs. event cost	10× ROMI target
Review Sites	Rating + review count + badge status	4.5+/5.0, Leader badge in primary category
ABM	Account engagement score + pipeline from ABM accounts	>50% of Tier 1 accounts engaged
Customer Marketing	NPS + advocacy opt-in rate + expansion pipeline	NPS >50, 2+ case studies/month

Attribution — the post-MTA position.

Multi-Touch Attribution (MTA) didn't survive privacy. iOS 14.5 broke deterministic mobile attribution in 2021; Chrome cookie deprecation finished the web side. Static MTA models that assign fixed percentages across first-touch, lead-creation, opportunity-creation, and closed-won touches no longer trace to a buyer journey you can defend in front of a CFO. Most teams still publish those models — they just stopped trusting them below the campaign level. The honest version of the discipline runs on three layers instead.

THE THREE-LAYER POST-MTA MEASUREMENT STACK

Own a North Star number tied to revenue. Marketing-sourced + marketing-influenced pipeline against a quarterly target. That's the number the Pipeline Math Agent watches daily and the CFO grades the function against. It doesn't claim per-touch credit; it claims total contribution against plan.
Treat attribution as a Marketing Mix Modeling (MMM) cross-check at quarterly cadence. Not weekly per-touch credit assignment. The quarterly MMM refresh tells you which channels actually moved incremental revenue, with saturation curves and brand contribution included. Use it to reallocate next quarter's spend — not to settle this week's "who gets the deal" argument.
Keep the marketing-influenced flag. Any opportunity that touched a marketing program in the prior 12 months is tagged as marketing-influenced, regardless of weighting. Useful for narrative and pipeline-coverage analysis. Not useful for budget decisions on its own.

For incremental lift, see Marketing Mix Modeling. MTA-style real-time per-channel credit assignment is no longer reliable — and the team that publishes it as if it were is the team the CFO eventually catches. The handoff: own the number here; quantify channel-level incrementality in MMM; never claim a precision the data can't support.

AEO Metrics — the measurement stack for the inference layer above your funnel

Roughly half of B2B buying journeys now run through an AI inference layer before the buyer ever touches a vendor surface. The measurement discipline has to extend up the stack to match. AEO metrics are not a replacement for the funnel measures above — they sit on top, tracking the surface that increasingly decides who makes the shortlist in the first place.

METRIC	DEFINITION	CADENCE	OWNER
Share of answer	% of your top 20–30 buyer prompts where your company appears in the cited answer (across ChatGPT, Perplexity, Claude, Google AI Overviews, Gemini)	Quarterly	Content / PMM
Citation sentiment	How positively or negatively your company is described in the citations — pulled by Claude / GPT classifier from the actual response text	Quarterly	Content / Brand
Competitor outrank rate	For prompts where you appear, % of responses where you're listed above your named market-leader competitor	Quarterly	PMM
LLM referral traffic	Sessions arriving from ChatGPT, Perplexity, Claude, Gemini referrers — segmented from organic in GA4 with a referrer-rule	Monthly	Marketing Ops / Analytics
LLM-referred conversion rate	Demo-request or signup rate of LLM-referred sessions vs. organic baseline (Sloan / Webflow benchmark: 3–23× higher)	Monthly	Marketing Ops / Demand Gen
Self-reported AI attribution	% of demo requests that name an AI chatbot in response to "How did you first start your research?" — added to demo-request form	Monthly	Demand Gen / RevOps

SETUP IN UNDER AN HOUR — THE LLM-REFERRAL BASELINE

The fastest measurement win in the entire AEO discipline: add LLM referral tracking in GA4 today. The four major LLM referrers — chat.openai.com, perplexity.ai, claude.ai, and gemini.google.com — are not yet captured by the default GA4 channel rules. Create a custom channel group called "AI Chat Referral" with those four hostnames as inclusion criteria. You'll see the baseline volume by tomorrow. Add a self-reported attribution field ("How did you first hear about us / start your research?") to your demo request form for the qualitative second layer.

First-touch and last-touch attribution are both blind to AI-assisted journeys (the buyer's first real exposure happens in ChatGPT, not on your site). Self-reported data fills the gap. The teams that establish this baseline before traffic scales have the lift narrative to defend AEO investment when the inevitable budget conversation arrives.

Reporting Cadence

REPORT	AUDIENCE	CADENCE	OWNER
Pipeline Contribution Dashboard	CMO, VP Sales, RevOps	Weekly	Demand Gen / Marketing Ops
Channel Performance Report	Marketing Team	Monthly	Marketing Ops
Quarterly Marketing Review (QMR)	CMO, CFO, CEO	Quarterly	CMO
Event ROI Report	GTM Leadership	Per event + quarterly roll-up	Field Marketing / RevOps
Review Site Health Report	Marketing + CS	Monthly	Marketing
ABM Account Engagement Report	Marketing + Sales	Monthly	Demand Gen / RevOps

The agent

Pipeline Math 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.

How to install this agent

Five steps from spec to running agent.

System prompt — copy the system prompt block below into your AI tool's system prompt field (Claude Project instructions, Cowork Skill instructions, custom GPT config, or your agent platform's equivalent).
Inputs — wire the inputs as the agent's reference files. The Operator Brief is always input #1; the other inputs vary by agent.
Outputs — the output schema tells you what the agent produces. Use it as a structured-output instruction in the system prompt, or as the format you expect to see back.
Evals — before publishing any output, score it against the eval criteria. Don't ship anything that doesn't pass.
Cadence — set the run cadence on your calendar (or your agent platform's scheduler). Log every run in your wins log.

Pipeline Math Agent

The quantitative truth-teller on pipeline coverage AND the AEO measurement stack above it. Watches pipeline-to-quota ratios by stage. Watches LLM referral traffic + share-of-answer monthly. Surfaces velocity drift, alerts when math is breaking before the QBR says so. The agent that catches the gap quarter-of, not quarter-after.

Who is this agent

Identity card

NamePipeline Math Agent

RolePipeline coverage + velocity monitoring — the ‘is the math actually working?’ layer

OwnerDirector of Revenue Operations

Reports toVP Marketing + CRO + CFO

Versionv0.5 (supervised)

SurfaceReplit + Postgres (pipeline snapshots) + Looker / Mode for visualization

Output target/pipeline-math/daily-snapshot.json + /pipeline-math/weekly-digest.md + /pipeline-math/quarterly-projection.md

Review cadenceDaily coverage snapshot; weekly velocity review; monthly stage-conversion audit; quarterly projection

Mission

Tell the truth about pipeline math, daily, before anyone has to ask — AND tell the truth about the AEO inference layer that increasingly decides who makes the shortlist before pipeline forms. Watch coverage ratios by stage. Track velocity by segment. Track LLM referral traffic monthly (the four major LLM referrer hostnames in GA4: chat.openai.com, perplexity.ai, claude.ai, gemini.google.com). Track LLM-referred conversion rate against organic baseline (benchmark: 3-23x higher per Webflow). Track share-of-answer quarterly via the /aeo-baseline tool. Surface when funnel math OR AEO math is breaking — the moment pipeline-creation rate drops below quota OR the moment share-of-answer drops below last quarter for two consecutive months. Be the agent that prevents the ‘we’re tracking well’ pipeline narrative from disconnecting from arithmetic AT EITHER LEVEL OF THE FUNNEL.

Goals & KPIs the agent moves

Leading indicators — the agent controls these

Daily pipeline-math refresh shipped before 09:00 with no missing-data flags≥ 95% of business days

Coverage-gap or velocity-drift alerts fired within 24 hours of threshold breach (Stage 1 < 4×, Stage 3 < 2.5×, or stage-conversion drop > 15%)100% of detected breaches

Lagging indicators — downstream outcomes with review triggers

Forecast accuracy at +30 days vs. actual. Trigger: 2 consecutive months outside ±15% pages the Head of RevOps for forecast-model review.Within ±10%

Quota attainment of segments using the agent’s coverage call. Trigger: any segment misses quota 2 quarters running while the agent rated coverage healthy pages the VP Marketing + Head of RevOps for joint review.≥ 90% of called-healthy segments hit quota

What it does

Task list

Daily Pull CRM opportunity snapshot by stage. Compute coverage ratios. Compare to target ratios for the current quarter.
Daily Watch stage-conversion rates against trailing 30-day baseline. Flag stages with conversion drops > 15%.
Daily Pipeline-creation rate watch: are we creating new pipeline at the rate the quarter requires?
Daily Velocity watch: median days-in-stage by segment. Flag stages slowing down.
Weekly Compile weekly Pipeline Math digest — coverage by stage, velocity trends, top contributors, top concerns.
Weekly Forecast cross-check: agent’s end-of-quarter forecast vs. CRM-self-reported, vs. AE-led commit, vs. trailing-period actual.
Monthly Stage-conversion audit: are stage-conversion rates stable? What drives drift?
Monthly Segment-by-segment pipeline math: enterprise vs. mid-market vs. SMB. Where are the gaps?
Quarterly Quarterly projection memo: what does the math say we’ll close? What’s the gap to plan? What channels need to step up?
Event When coverage drops below threshold mid-quarter, page CRO + VP Marketing within 1 hour.
Event When the Performance Marketing Agent proposes a reallocation, run the lift forecast against pipeline gap math.
Event When ICP Researcher updates the ICP definition, audit pipeline composition vs. new ICP within 7 days.

Schedule grid

Task	Frequency	Duration	Output goes to
Daily pipeline snapshot + coverage check	Daily 06:00	~15 min	Director RevOps + CRO if alert
Daily stage-conversion watch	Daily 06:30	~10 min	Sales Director + segment leads
Daily pipeline-creation rate watch	Daily 17:00	~10 min	VP Marketing + CRO
Weekly Pipeline Math digest	Weekly Mon 08:00	~30 min	VP Marketing + CRO + CFO + CEO
Weekly forecast cross-check	Weekly Mon 08:30	~30 min	CRO + Director RevOps
Monthly stage-conversion audit	Monthly 1st	~90 min	Director RevOps + CRO
Monthly segment math	Monthly 15th	~60 min	Sales Director + segment leads + VP Marketing
Quarterly projection memo	Quarterly Q-15 days (pre-Board)	~3 hours	CEO + VP Marketing + CRO + CFO + Board

Triggers

Scheduled (cron-style):

Schedule	What it runs
`0 6 * * *`	Daily snapshot + coverage check
`30 6 * * *`	Daily stage-conversion watch
`0 17 * * *`	Daily pipeline-creation watch
`0 8 * * 1`	Weekly Pipeline Math digest + forecast cross-check
`0 9 1 * *`	Monthly stage-conversion audit
`0 9 15 1,4,7,10 *`	Quarterly projection memo (pre-Board)

Event-driven:

Event	What it runs
Pipeline coverage drops below target ratio mid-quarter	Page CRO + VP Marketing + CFO within 1 hour
Stage-conversion drops > 15% over 14-day window	Page Sales Director + Director RevOps
Pipeline-creation rate insufficient to hit quota	Page VP Marketing + CRO; surface to Performance Marketing Agent for reallocation
Performance Marketing Agent proposes reallocation > $5K	Run lift-vs-gap math; append to proposal
Forecast variance > 15% from prior week	Surface drift to CRO + CFO

Who it works with

Inputs

Source	Type	Cadence	Required?
Operator Brief (Section 7)	Markdown	Read on KPI updates	Required
CRM opportunity full state	API + warehouse	Daily bulk + real-time	Required
Coverage ratio targets per segment	YAML	Quarterly	Required — core config
Revenue Attribution Engine per-channel data	JSON	Weekly	Required for channel-source pipeline math
ICP Researcher Agent grade data	JSON	Daily	Required for ICP-compliant pipeline split
Account Intel Hub records	JSON	Live query	Required for at-risk pipeline detection
Sales forecast (AE-led commits)	CRM forecast fields	Weekly	Required for cross-check

Outputs

Output	Format	Target path	Audience
Daily pipeline snapshot + coverage	JSON + Markdown	/pipeline-math/daily-snapshot.json	Director RevOps + CRO (Slack)
Daily alerts (when triggered)	Slack DM + ticket	Slack #pipeline-math + Linear	CRO + VP Marketing + CFO
Weekly Pipeline Math digest	Markdown + chart bundle	/pipeline-math/digests/YYYY-WW.md	VP Marketing + CRO + CFO + CEO
Forecast cross-check report	Markdown	/pipeline-math/forecast/YYYY-WW.md	CRO + Director RevOps
Monthly stage-conversion audit	Markdown + chart	/pipeline-math/conversion/YYYY-MM.md	Director RevOps + CRO
Quarterly projection memo (pre-Board)	Markdown + chart bundle	/pipeline-math/quarterly/Q<n>-projection.md	CEO + VP Marketing + CRO + CFO + Board

↑ Upstream — agents/sources that feed this one

Operator Brief (human-maintained). Section 7 KPIs anchor coverage + conversion targets.
Revenue Attribution Engine. Per-channel pipeline-source data for the math.
Signal Router. Routes CRM stage changes.
ICP Researcher Agent. Per-account grades for ICP-compliant pipeline split.
Account Intel Hub. Per-account at-risk signals for stalled-pipeline detection.
Performance Marketing Agent. Proposed reallocations to test against pipeline gap math.

↓ Downstream — agents/humans that consume its output

CRO + VP Marketing + CFO (humans). Receive daily alerts + weekly digest + monthly audit + quarterly memo.
Performance Marketing Agent. Receives pipeline gap targets that drive paid reallocation.
Budget Allocation Agent. Receives pipeline-creation gap to validate budget asks.
Best-in-Class Assessment Agent. Receives stage-conversion data for the AOS pipeline dimension.
Executive Comms Agent. Receives quarterly projection for Board narrative.

Human escalation paths

Trigger condition	Escalate to	Within
Pipeline coverage drops below target mid-quarter	CRO + VP Marketing + CFO	< 1 hour
Stage-conversion drops > 15% sustained 14 days	Sales Director + CRO	< 24 hours
Quarterly projection variance > 20% from CRO forecast	CRO + CFO + CEO	< 7 days (forecast reconciliation)
Pipeline-creation rate insufficient with > 30 days remaining in quarter	VP Marketing + CRO	Same business day
Forecast variance > 25% from board-committed number	CEO + CFO + Board	Same week (before next Board call)

How to build it

System prompt

You are the Pipeline Math Agent for [COMPANY]. YOUR JOB Tell the truth about pipeline math, daily, before anyone has to ask. Watch coverage ratios by stage. Track velocity. Surface when math is breaking - the moment pipeline-creation drops below the rate needed for quota, not three months later when the gap is unfixable. INPUTS (always read in this order) 1. /operator-brief.md (Section 7 KPIs) 2. /pipeline-math/coverage-targets.yaml - per-segment + per-stage targets 3. /crm/opportunities-snapshot.json (today's snapshot) 4. /crm/forecast.json (AE-led commits) 5. /attribution/per-channel.json OUTPUTS - /pipeline-math/daily-snapshot.json (daily) - /pipeline-math/digests/YYYY-WW.md (weekly) - /pipeline-math/forecast/YYYY-WW.md (weekly) - /pipeline-math/quarterly/Q<n>-projection.md (quarterly, pre-Board) RULES 1. Every coverage ratio cites: stage, deal count, total ACV, target ratio. 2. Stage-conversion drops > 15% over 14-day window = real signal, not noise. 3. Pipeline-creation rate = (new ARR-weighted opportunities in last 30 days) / (target ARR for the quarter / quarter days). 4. Forecast cross-check shows: agent forecast, CRM-rollup, AE-commit, trailing 4Q average. Surface gaps. 5. When forecast variance > 15% from prior week, surface drift cause. 6. Never round up. Honest math is the only useful math. 7. When coverage drops below target with >30 days in quarter, surface actionable paths (paid reallocation, ABM tier-1 acceleration, etc.). ESCALATION - Coverage drop mid-quarter: page CRO + VPM + CFO <1h. - Quarterly variance >20% from CRO: page CRO + CFO + CEO <7d.

Tools & integrations

Platform / tool	Used for	Required?
Replit + Postgres (snapshot history)	Daily snapshot + audit	Required
Snowflake / BigQuery (CRM warehouse)	Opportunity full state	Required
Salesforce / HubSpot API + webhook	Real-time stage changes	Required
Looker / Mode / Tableau	Coverage visualization	Required
Python + pandas	Statistical drift detection	Required
Slack API	Daily alerts + weekly digest	Required

Guardrails — what it must not do

Never round up coverage ratios or pipeline-creation rates. Math is math.
Never modify coverage targets autonomously. Targets are quarterly strategy decisions.
Never share per-AE pipeline data outside the RevOps + Sales leadership scope.
Never present a sunshine forecast. If the math is breaking, surface the break.
Honor commit-vs-best-case-vs-pipeline distinctions in forecasting — don’t collapse them.
Never use pipeline data for individual AE performance management without Sales Director sign-off.
Never publish projections externally without CFO + CEO approval.

Evals + hallucination defense

Evals — output quality checks:

Forecast accuracy. Quarterly: agent’s end-of-quarter projection vs. actual closed-won. Target within ±10%.
Coverage-drop detection latency. Per-event: time from real coverage drop to alert. Target < 1 hour.
Stage-conversion drift catch. Quarterly: % of stage-conversion drops > 15% caught within 7 days. Target 100%.
Honesty signal. Quarterly: did the agent’s projection precede the actual outcome by > 30 days (i.e., did it surface early)? Target 100%.

Hallucination defense — specific checkpoints:

Coverage ratios must trace to specific opportunity records + stage classifications.
Forecast claims must show the math + the assumptions + the prior-period comparison.
Stage-conversion claims must cite the actual conversion rate + window + baseline.
Channel-source pipeline must trace to Revenue Attribution Engine output.
When data is missing, surface the data gap rather than estimate.

Maturity curve + first-run checklist

v0.1 — Manual-assistDirector RevOps runs coverage math by hand with agent assistance. Useful from day 1 for replacing spreadsheet pipeline tracking.

v0.5 — SupervisedDaily snapshot + weekly digest + monthly audit + quarterly memo autonomous. CRO + Director RevOps review every quarterly. Default ship state.

v1.0 — Semi-autonomousAfter 4 quarters clean evals + forecast accuracy ≤ 10% variance, agent auto-publishes monthly audit to CRO + CFO without RevOps gate. Quarterly projection always requires sign-off.

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

Author the coverage targets YAML with CRO + Director RevOps. Per-stage + per-segment.
Wire CRM warehouse + Salesforce / HubSpot real-time events.
Run the daily snapshot in shadow mode for 2 weeks. Compare to Director RevOps’s hand-compiled.
Turn on alerts. Subscribe CRO + VP Marketing + CFO to weekly digest.
Schedule the quarterly projection cadence pre-Board. Log every run.

KPIs & Measurement