Weekly Marketing Ops KPIs: Pipeline, Velocity, CAC

If your weekly marketing report doesn’t predict revenue and provoke action, it’s noise. This playbook shows exactly what marketing ops leaders should report every week - pipeline, velocity, CAC, SLAs, channel ROI, and data health - plus the formulas, ranges, and rituals to make it stick.

A weekly marketing report exists to answer two questions: Are we on track to hit revenue targets? If not, what will we change by Friday? Anything that doesn’t move those answers forward is decoration. You don’t need 45 charts and a 20‑minute preamble - you need a tight stack of forward indicators and the courage to act on them.

Weekly also means “leading.” Monthly and quarterly reporting is where you reconcile and tell the story; weekly is where you steer. That’s why you’ll see speed-to-lead, pipeline coverage, and sales velocity here. They move faster than bookings and can be corrected inside the week. If you wait for end-of-month, you’re in postmortem mode by design.

Finally, weekly reporting is a ritual, not a file. The best teams run a 30‑minute session with the same view, same definitions, and a short list of high‑impact changes. The output is a clear owner and a deadline. No slides required.

Start with five numbers that a founder or revenue leader can absorb at a glance. These are the top row of your dashboard and the only metrics you read out loud before diving deeper. The point is to orient the room and frame the decisions for the week.

Recommended executive stack:

- Weekly pipeline created (new opportunities) and dollar value, by segment
- Sales velocity (trailing 4 weeks): (Opps × Win rate × ACV) / Sales cycle (days)
- Pipeline coverage for the next 90 days vs target (weighted and unweighted)
- Blended CAC trend (trailing 8 weeks) and payback months (directional)
- Speed-to-lead: % of inbound leads touched within 5 minutes and within 1 hour

These five will catch 80% of issues early. If pipeline dips, you drop a campaign or spin one up. If velocity slows, you inspect cycle time and stage frictions. If coverage is light, you pull forward pipeline creation. If CAC drifts, you reallocate budget. If speed-to-lead slips, you fix routing and SLAs immediately - because the cost of delay compounds daily.

Pipeline is your fuel. But not all pipeline is equal, and a weekly view is where quality and timing matter. Looking only at “opps created” hides conversion and value shifts that will bite two months later. Build a simple set that separates creation, quality, and momentum.

First, report new opportunities (count and value) by segment (SMB, mid‑market, enterprise) and by motion (inbound, outbound, partner). Then report average opportunity value (ACV proxy) and qualification rate (SQL/SAO rate) for each. Finally, track aging: % of pipeline older than your median sales cycle at each stage. Old pipeline is often dead pipeline you haven’t cleaned.

Make it visual: a stacked bar for opps created, a line for ACV, and a heatmap for conversion by source. Your goal each week is to prevent a “pipeline cliff” six weeks out. If enterprise opps dip now, you won’t feel it until next quarter. Weekly is where you keep the machine fed.

Coverage and quality: SQLs, pipeline value, and weighted coverage

Coverage answers “Do we have enough to hit the number?” and quality answers “Will it convert?” Both belong in the same frame. Report unweighted coverage (pipeline value / next‑90‑day quota) and weighted coverage (sum of stage‑weighted values / next‑90‑day quota). Weighted tells you realism; unweighted reminds you of optionality.

Useful ranges: unweighted coverage of 3–5× is healthy in SMB and outbound motions; 2–3× can work for high win‑rate inbound motions; enterprise often needs 4–6× due to longer cycles and higher variance. But these are starting points. Calibrate to your historical conversion by segment and motion.

Now add SQL quality: track SQL‑to‑closed‑won conversion by source and average age at SQL. If your weighted coverage is fine but SQL conversion is falling, you’re feeding the forecast with low‑probability deals. That’s a fixable upstream issue - messaging, targeting, or qualification - rather than a forecast problem.

Conversion rates by stage and by source

Stage conversion is where small compounding gains stack fast. Weekly, report these three pairs for each major source: MQL→SQL, SQL→Opportunity (if you use SAO/SAL), and Opportunity→Closed‑Won. Also track median days in stage. Rising days in stage are an early signal of friction long before conversion tanks.

Resist the urge to compare channels with different intents (e.g., high‑intent inbound vs cold outbound) by the same conversion thresholds. Compare each channel to its own history and its own target. Your job weekly is to spot deltas, not to litigate attribution philosophy.

When you do see a drop, ask in order: Did volume spike (dilution)? Did ICP drift (list/keyword quality)? Did the offer or CTA change (intent mismatch)? Did routing or SLAs break (slow touch)? Work upstream to downstream - most conversion problems start earlier than the chart suggests.

Speed-to-lead is one of the few levers that increases revenue without increasing spend. Your weekly report should show median and 90th percentile response time for inbound leads, plus the % contacted inside 5 minutes and inside 1 hour. For paid search and demo requests, the 5‑minute target is non‑negotiable.

Pair speed with outcome: show SQL rate by response‑time band (e.g., 0–5m, 5–60m, 1–24h, 24h+). The pattern is consistent across industries: faster first touch yields higher conversion and shorter cycles. Weekly visibility makes it easy to spot a Friday routing bug or a timezone coverage gap before it burns your ad dollars.

Finally, monitor SLA adherence between marketing and sales: time to first touch, time to qualify, and time to next step scheduled. If adherence slides, look for ownership gaps, handoff ambiguity, or workflow errors. Fix the system before you retrain humans - the system sets the floor.

Velocity compresses your funnel into one rate you can improve. Use the standard formula over a trailing 4‑week window to smooth noise: Sales Velocity = (Number of Opportunities × Win Rate × ACV) ÷ Sales Cycle (days). Report it by segment and motion.

If velocity drops, decompose: Did you create fewer opps? Did win rate slip? Did ACV fall? Did cycle time expand? Each driver has different fixes. The beauty of weekly is that you can run small, fast experiments - tighten ICP filters, test a stronger CTA, or remove one approval step in legal to cut days.

For a sanity check on the forecast, compare weighted pipeline for the next 90 days to a velocity‑based projection. If weighted pipeline says you’ll hit 120% but velocity implies 85%, someone’s optimism is writing checks the machine can’t cash. Resolve the gap now, not at QBR.

You can’t calc lifetime value weekly with precision, but you can keep CAC and payback moving in the right direction. Report blended CAC trend as a trailing 8‑week line and channel‑level CAC proxied by “spend ÷ new customers” or “spend ÷ new qualified opportunities × SQL→Won rate.” Pair it with gross margin to estimate payback months.

Basic formula reminder: Payback Months ≈ CAC ÷ (ARPA × Gross Margin). If ARPA or margin shift materially, call it out. Enterprise motions may prefer “CAC per $1 of pipeline” weekly with a rolling conversion factor. The point is to keep economics honest while you iterate campaigns.

Watch early warning signals: rising CPCs without matching CVR, falling ACV from discounting, and creeping non‑working spend (tools and humans) that never shows up in channel CAC. Weekly is where you prevent slow CAC inflation that only becomes obvious in finance close.

Channels have different clocks. Paid can move within 48 hours, organic shows trend over weeks, outbound responds to list/offer seasonality. Your weekly frame should reflect those clocks without holding them to unrealistic timelines. Look for direction, not instant ROI on everything.

Segment channels by intent and by motion: high‑intent inbound (brand, competitor, MoFu keywords), mid‑intent content (problem/solution SEO, LinkedIn), and outbound (email, phone, social touches). Compare each to its own target and lag profile, not to each other.

When a channel underperforms weekly, decide whether to optimize (tweak bids, creative, routing), expand (increase budget or send volume), or pause (protect CAC). The dashboard should make that decision obvious.

Paid media weekly indicators that matter

For paid search and social, track: spend, CPC/CPM, CTR, LP CVR, cost per qualified lead (CPL), cost per qualified opportunity (CPQO), and cost per $1 of pipeline. Add a leading indicator of creative fatigue (impressions to first decay in CTR) and an estimate of incrementality if you run brand terms.

If you’re reporting to a founder, keep it business‑first: “We spent $38K, created $420K of pipeline at $90 CPQO, and are pacing toward 3.8× coverage. CAC holding at $1,450 with 7.2‑month payback.” That’s a decision‑ready line, not a channel diary.

If you need help structuring this for scale, consider consolidating your paid signals into a single view. A practical way is to anchor spend to pipeline, not just leads, and manage budgets against pipeline goals. If you’re missing that machinery, a compact performance marketing layer that speaks finance can save months of trial and error.

Organic and content weekly indicators (direction over noise)

Organic won’t deliver same‑week revenue, but it will warn you if you’re going to win or lose a quarter from now. Report: non‑brand clicks, money‑page rankings (top 20 tracked keywords that actually convert), pages indexed vs published, and assisted pipeline touches (last 30/60/90 days). Use 4‑week trends - not daily wobbles.

Quality indicator: % of content mapped to ICP problems with a revenue‑backed CTA (demo, pricing, ROI calculator), not just traffic bait. Another one: internal link coverage to commercial pages. If your new content never points at product or sales pages, you’re building an island.

If you want the compounding effect without adding headcount, systems for AI drafting, human editing, and programmatic internal linking help you scale. We’ve seen this stack move the needle - from 0 to 80K organic visits/month and 2K inbound leads/month at Cleverence - when the pipeline goal sets the brief. If you’re light here, explore an AI SEO content program built around revenue pages, not vanity impressions.

Outbound weekly indicators (quality > volume)

For outbound email and calling, track: sends, open rate (or delivered for Apple MPP), positive reply rate, meetings booked rate, bounce rate, spam complaint rate, and domain reputation health. The two ratios that matter most weekly are positive replies per 100 contacts and meetings per 100 contacts.

Quality checks: list coverage of ICP fields (industry, role, tech), offer strength (is there an insight or asset, not just “quick call?”), and domain warmup status. If meetings dip and bounce rate rises, pause sends and fix data or domain health before you burn another domain.

Outbound success is lumpy - judge it by 4‑week rolling averages and by sequence/offer cohorts, not day‑to‑day swings. Your weekly goal is to protect domain health and feed sales with realistic meetings, not to push vanity volume.

Most weekly reports ignore the plumbing. That’s where silent revenue leaks live. Add a small “Ops Health” panel that tracks: duplicate rate, required field completion at lead and opportunity creation, enrichment coverage (% of records with firmographic and contact fields), and lifecycle stage accuracy (audit sample).

Automation reliability matters just as much: workflow error rate (last 7 days), average lead routing time, CRM–MAP sync failures, and uptime of critical webhooks. If any of these spike, they mask real performance and corrupt your historical baselines.

If your CRM foundation is shaky, fix that before you add more channels. Clean objects, standardized lifecycle, and a simple, inspectable routing logic will raise every KPI in this article. If you need to formalize it, a focused HubSpot CRM implementation or cleanup sprint pays for itself in fewer missed leads and faster cycles.

Pick one source of truth. For many teams, that’s the CRM for funnel and pipeline, ad platforms for spend, GA4/Search Console for organic, and a BI layer (e.g., Looker/Data Studio or a warehouse + simple model) to unify. Don’t “platform hop” during the meeting - pipe it into one view with consistent names and date ranges.

Must‑have plumbing: UTM discipline (source/medium/campaign consistently cased), lifecycle timestamps (lead created, MQL, SQL, Opp created, Closed), and a canonical list of stages with exact definitions. If your “SQL” means five different things, your report is politics, not analytics.

For formulas that need cross‑system math (e.g., velocity, payback), either compute in the BI layer or push fields back into the CRM via a nightly job. Keep it transparent - if someone can’t click through to the record level, they won’t trust the metric when it turns red.

Anton Chisliuk · AI Marketing Ops runs on this operator model: one senior builder owns CRM, content, paid, and automation so metrics line up with execution. That’s how we’ve taken a B2B SaaS from 0 to 80K organic visits/month and 2K inbound leads/month without adding headcount layers. If you’re curious how this works in practice, read more about the operator approach and why we avoid agency overhead.

Guard the time and the format. The best cadence is Monday or Tuesday morning, 30 minutes, camera on, dashboard up. No slides. Everyone sees the same view. The owner reads the five executive KPIs, then you drill into the one or two areas that actually need a change.

Define three roles: Driver (runs the agenda and calls on owners), Analyst (updates metrics and flags anomalies ahead of time), and Owners (channel/ops owners who commit to changes). Decisions are captured live in a simple tracker with an owner, due date, and expected impact.

End with a short “What we will do by Friday” list: fix routing for EMEA demo requests, swap non‑performing paid creative variants, publish two bottom‑funnel pages, pause a fatigued outbound domain, and run a discount‑free enterprise CTA test. Next week starts with a check against that list before new topics.

- Vanity stack: drowning in secondary metrics while ignoring pipeline and velocity.
- Definition drift: MQL/SQL redefined every quarter, killing trust and trend analysis.
- Overreacting to noise: whiplash budget moves on 3 days of data.

- Channel comparison traps: judging cold outbound by inbound demo standards, or brand search by non‑brand discovery standards.
- Ignoring the plumbing: routing breaks, duplicate explosions, and enrichment failures that corrupt every shiny chart.
- Slide theater: spending more time designing decks than changing systems.

Solutions are simple: freeze definitions, limit top‑row KPIs to five, use rolling windows to smooth noise, compare channels to their own targets, and add an Ops Health panel. Most important - tie every red metric to a system change with an owner and a date.

Benchmarks are context, not commandments. Use them to start conversations, then calibrate to your motion. Here are working ranges we see across B2B and prosumer funnels - sanity checks, not report cards.

- Speed-to-lead: 60–80% within 5 minutes (inbound demo/quote), 90%+ within 1 hour for all inbound forms.
- SQL rate (inbound high‑intent): 35–60%; (content‑led): 10–30%; (outbound): 3–10%.
- Opportunity→Won: SMB 20–35%; Mid‑market 15–25%; Enterprise 10–20%.

- Unweighted pipeline coverage next 90 days: SMB 3–5×; Mid‑market 3–4×; Enterprise 4–6×.
- Blended CAC payback: SMB 3–9 months; Mid‑market 6–12 months; Enterprise 9–18 months.
- Outbound positive reply rate: 2–6%; meetings per 100 contacts: 1–3.

Use this structure verbatim for your next meeting. It fits on one screen and drives decisions fast.

1) Executive KPIs (top row)
- Pipeline created (count, $) by segment
- Sales velocity (trailing 4 weeks)
- Pipeline coverage next 90 days (weighted/unweighted)
- Blended CAC trend + payback (direction)
- Speed-to-lead (% <5m, % <1h)

2) Funnel and quality
- MQL→SQL, SQL→Opp, Opp→Won by source
- Average opp value by segment
- Aging: % above median cycle by stage

3) Channels
- Paid: spend, CPL/CPQO, pipeline per $1, creative fatigue
- Organic: non‑brand clicks, money‑page ranks, pages indexed, assisted pipeline
- Outbound: replies/100, meetings/100, bounce/complaints, domain health

4) Ops Health
- Duplicates, required fields, enrichment coverage, lifecycle accuracy
- Workflow error rate, routing time, sync failures, webhook uptime

5) Actions by Friday
- 3–5 changes with owner, date, expected impact

If your current report can’t answer “Are we on track?” in 60 seconds, you don’t have a metrics problem - you have a system problem. Stand up the view, freeze definitions, and run the ritual for three weeks. You’ll feel the drag disappear. If you want a second set of operator eyes, that’s what I do - hands on the tools, no agency tax, outcomes over optics.

Weekly reporting is where revenue is won or lost. Keep the stack tight: pipeline created, velocity, coverage, CAC/payback direction, and speed-to-lead. Pair it with funnel conversion, channel‑specific indicators, and a small Ops Health panel. Then run a real ritual - short, consistent, and action‑oriented.

You don’t need another dashboard; you need a dashboard that tells you what to change by Friday. Freeze definitions, make the formulas transparent, and assign owners. The compounding effect of small weekly fixes - faster routing, cleaner data, tighter offers - will outperform big quarterly swings.

If you want help standing this up fast (HubSpot, paid, SEO, outbound, automation), book a free Growth Audit and we’ll map your KPI stack to a 90‑day build plan.

Written by Anton Chisliuk - Leads, sales, content, and systems - one senior operator.

- What KPIs should a marketing ops leader report weekly?

Lead with five: pipeline created (count and $), sales velocity (trailing 4 weeks), pipeline coverage next 90 days (weighted/unweighted), blended CAC/payback direction, and speed-to-lead. Then drill into funnel conversion by source, channel indicators (paid, organic, outbound), and an Ops Health panel.

- How do I calculate sales velocity for a weekly report?

Use: (Opportunities × Win Rate × ACV) ÷ Sales Cycle (days). Calculate by segment and by motion over a trailing 4‑week window to smooth noise. If velocity drops, decompose the drivers - volume, win rate, ACV, or cycle time - then assign a fix you can land this week.

- What is a good pipeline coverage ratio?

It depends on your motion. As a starting range: SMB 3–5×, mid‑market 3–4×, enterprise 4–6× for the next 90 days. Calibrate to your historical conversion and sales cycle. Track both unweighted (optionality) and stage‑weighted (realism) coverage every week.

- How do I track CAC and payback weekly without noisy data?

Trend blended CAC on an 8‑week rolling basis and use channel‑level proxies (spend ÷ new customers or spend ÷ new qualified opps × SQL→Won rate). Estimate payback as CAC ÷ (ARPA × Gross Margin). The goal is direction and early warnings, not GAAP precision weekly.

- What’s the fastest way to improve weekly conversion?

Fix speed-to-lead. Aim for 60–80% of inbound touched within 5 minutes and 90%+ within 1 hour. Then tighten ICP targeting, strengthen offers/CTAs, and remove stage friction (approvals, handoffs). These typically lift conversion without new spend.

- How should we run the weekly meeting?

30 minutes, same time, same dashboard. Read the five executive KPIs, drill into one or two problem areas, and end with 3–5 owner‑assigned changes due by Friday. No slides. Start next week by closing the loop on those actions before adding new topics.