neon-rutger/b2b-revops-skills/revenue-operating-cadence

Revenue Operating Cadence Framework

The difference between scaling to $150M and stalling at $20M isn't forecasting accuracy; it's operating rhythm. Your cadence is the machine that turns strategy into deals into board updates. Get it wrong and you're firefighting every week. Get it right and revenue becomes predictable.

The Core Principle: Data Pyramid

Every decision flows from clean data. Every data input flows from activity. The pyramid collapses if the base is dirty.

          ┌─────────────────┐
          │    BOARD        │
          │  (Quarterly)    │
          │  Narrative+KPIs │
          └────────┬────────┘
                   │
          ┌────────▼────────┐
          │  LEADERSHIP     │
          │ (Monthly/QBR)   │
          │ Trends+Decisions│
          └────────┬────────┘
                   │
          ┌────────▼────────┐
          │      TEAM       │
          │   (Weekly)      │
          │Pipeline+Forecast│
          └────────┬────────┘
                   │
          ┌────────▼────────┐
          │   ACTIVITY      │
          │    (Daily)      │
          │ Calls/Deals/Logs│
          └─────────────────┘

If activity is garbage → pipeline data lies → forecasts fail → board gets surprises.

The Meeting Architecture (7 Questions for Every Meeting)

Before you schedule it, answer these:

Rule: If a meeting doesn't produce decisions or logged actions, send an email instead.

The Core Ceremonies

Daily: Sales Pipeline Pulse (15 min, team level)

Purpose: Surface blockers. Coordinate same-day wins.

Rep 1: "AWS deal stuck on legal review. Need legal in Wed meeting."
Rep 2: "Acme expanded scope, moving to $650k. Closes Friday."
Rep 3: "Nordic Bank went dark for 3 days. Need help re-engaging."

RevOps role: Not in the room. But your pre-built CRM views should make this data self-serve.

Weekly: Pipeline Review (45 min per team, Sales Manager + team)

Purpose: Inspect deal progression. Identify stalled deals. Lock forecast.

Pre-meeting packet (built by RevOps):

• Pipeline stage movement report (last 7 days)
• Deal aging by stage (red flag if over 14 days without movement; Rework, Outreach, 2026)
• Forecast accuracy vs. prior week
• Win/loss summary (reasons why deals close/slip)

Agenda:

Key questions to ask:

• Which deals moved stage? Why?
• Which are stalled? What's the blocker?
• What's our commit number? What's the gap to plan?
• Who's at risk of slipping? What's the recovery action?

Output: Updated individual forecasts logged in CRM.

Weekly: Forecast Roll-up (30 min, CRO + Sales Managers + RevOps)

Purpose: Aggregate to company view. Identify gaps to plan.

Participants:

• CRO (decision owner)
• Sales managers (inputs)
• RevOps (owns the model, flags anomalies)

Pre-meeting:

• Consolidated forecast from all teams
• Variance to plan (month/quarter)
• Confidence % by deal stage
• Top 10 at-risk deals

Agenda:

Questions:

• Where do we stand vs. quarterly target?
• What's our gap? What closes it?
• Where's the risk in the commit?

Output: Locked company forecast. Gap-closing action log.

Bi-weekly: Funnel Review (60 min, Marketing + Sales + CS + RevOps)

Purpose: Diagnose funnel health. Identify stage bottlenecks.

Pre-meeting data:

• Conversion rates by stage (vs. historical baseline)
• Lead-to-opportunity velocity
• MQL quality score (if tracked)
• Bottleneck analysis (where do deals slow down?)
• Win rate by segment/region

Agenda:

Questions:

• Are conversion rates healthy? Where's the drop-off?
• Is MQL quality up or down?
• How fast are deals moving through pipeline?
• What's the correlation between retention and new revenue?

Output: Cross-functional action owners. Experiments to try (e.g., "improve lead routing to reduce opp velocity").

Monthly: Business Review (90 min, Leadership + RevOps + Finance)

Purpose: Review performance vs. plan. Spot trends. Small steers.

Participants:

• CRO / VP Sales
• CMO / VP Marketing
• VP Customer Success
• RevOps
• Finance (if available)

Pre-meeting deck (8-10 slides max):

1. Revenue vs. plan ($M, waterfall, growth %)
2. Pipeline health (coverage, velocity, quality)
3. Efficiency metrics (CAC, payback, LTV:CAC)
4. Retention & expansion (NRR, GRR, churn)
5. Go-to-market performance (what's working)
6. Risks & escalations
7. Asks & resource needs

Rule: No more than 1 chart per slide. If you need 5 charts to explain something, you don't understand it yet.

Output: Documented priorities, resource decisions, escalations.

Quarterly: QBR (Half-day, Leadership team + board prep)

Purpose: Assess strategy execution. Major steers. Plan adjustments.

Participants:

• CEO / CRO
• All functional leaders
• RevOps (data owner)
• Finance (if applicable)

Data inputs:

• Full-year revenue performance (actual, forecast, plan variance)
• Pipeline trends (coverage, velocity, win rate)
• Customer health (NRR, cohort analysis, churn reasons)
• Efficiency trends (CAC, payback, burn multiple)
• Market/competitive shifts
• Team capacity vs. targets

Agenda:

Morning (2-3 hours)
├─ Revenue health (30 min)
├─ Go-to-market performance (30 min)
├─ Pipeline & forecast confidence (30 min)
├─ Customer & retention (30 min)
├─ What's working / What's not (30 min)
└─ Steers & resource reallocation (30 min)
 
Afternoon (1 hour)
├─ Board deck dry-run
├─ Key narratives (What do we tell the board?)
└─ Board asks & timeline

Key questions:

• Are we on track for annual targets? By how much?
• What's working that we should double down on?
• What's broken that we need to fix?
• Where should we invest next? What should we kill?
• What capabilities are we missing?

Output: Updated quarterly plan. Board deck draft. Resource allocation decisions.

Quarterly: Board Meeting (2-3 hours)

Purpose: Governance, accountability, strategic guidance.

Board deck structure (8-10 slides):

SLIDE 1: Executive Summary + Asks
┌─────────────────────────────────┐
│ Key narrative in 3 bullets      │
│ If you read nothing else...     │
│ Board decisions needed          │
└─────────────────────────────────┘
 
SLIDE 2-3: Revenue Performance vs. Plan
├─ ARR, ARR growth %, composition
├─ Waterfall (starting ARR → ending ARR)
└─ Variance explanation (story, not excuses)
 
SLIDE 4-5: Pipeline & Forecast
├─ Coverage ratio (pipeline / annual target)
├─ Velocity trends (deal cycle time)
├─ Win rate by segment
└─ Confidence in this quarter's forecast
 
SLIDE 6: Efficiency Metrics
├─ CAC ($)
├─ CAC Payback (months)
├─ LTV:CAC ratio
├─ Burn multiple (spend per $ ARR)
├─ Rule of 40 (growth % + operating margin %)
└─ Trends quarter-over-quarter
 
SLIDE 7: Retention & Expansion
├─ NRR (%), GRR (%)
├─ Cohort churn trends
├─ Top churn reasons + actions
└─ Expansion revenue trends
 
SLIDE 8: Go-to-Market Update
├─ What's working (segment, product, channel)
├─ What's broken + fix in progress
├─ Competitive landscape shifts
└─ Key experiments running
 
SLIDE 9: Strategic Initiatives
├─ Status (on track / at risk / complete)
├─ Timeline
├─ Key risks & mitigation
└─ Resource needs
 
SLIDE 10: Asks & Decisions Needed
├─ Board votes required
├─ Budget requests + ROI expected
└─ Timeline for decisions

Golden rules:

• Lead with narrative, not data
• Show trends, not snapshots
• Highlight risks and asks upfront
• No more than 3 metrics per slide
• Connect every number to strategy

RevOps role: Build the data foundation. Don't own the narrative; that's the CEO/CRO role.

The Data Inputs That Matter

Anti-patterns (Kill These)

Async-First Operating Cadence (For Distributed Teams)

Not every org can do synchronous weekly calls. Here's how to run the cadence async-first without losing accountability.

The structure: