Operating Cadence Designer

Operating Cadence Designer

Purpose

This skill helps design and install the operating cadence for clients. The cadence is the calendar that makes the revenue operating system real — it connects strategy (strategy scorecard), visibility (revenue dashboard), and execution (weekly/monthly rituals).

Without a cadence, leaders waste time in meetings that produce no decisions. With a cadence, every ritual has a clear purpose, owner, and output. This skill walks through the design and installation process.

---

When This Skill Activates

Use this skill in three main situations:

1. No existing cadence

Client has no consistent rhythm for revenue decisions. Meetings happen ad hoc. Leadership time is fragmented across email, Slack threads, and back-channel conversations. There is no single source of truth for the week's agenda or the month's priorities.

Design task: Build a complete weekly, biweekly, monthly, and quarterly rhythm from scratch. Start with the simplest version (7 weekly rituals + 1 biweekly + 2 monthly + 1 quarterly) and adapt to client size and stage.

2. Broken or inconsistent cadence

Client has some rituals, but they're inconsistent: some happen on schedule, some get cancelled or rescheduled. No one knows which meetings are mandatory. There is no clear escalation path from a signal to a decision.

Design task: Audit existing rituals, apply the 5P gate, consolidate into a clean calendar, and install decision rules that tell people when to escalate.

3. Cadence exists but no decision rules

Client has the calendar but no signal-based decision rules. Meetings happen, data is reviewed, nods happen, but nothing actually changes. Decision latency is long. Experiment kill rate is low. The cadence is status theatre, not a control system.

Design task: Install signal-based decision rules on top of the existing calendar. Define 8-12 key signals, set thresholds, route triggers to rituals, and train people on escalation.

---

The 5P Standard

Every meeting must pass the 5P gate. This is the non-negotiable foundation. If any P is missing or fuzzy, the meeting should be cancelled or rescheduled.

The 5Ps

1. Purpose — One clear sentence: "By the end of this meeting, we will...". This must finish with a concrete outcome (decision, list, design, changed plan), not an activity (discuss, review, understand).

1. Product — A tangible artifact that proves the meeting was worth the time.

• Examples: 3 decisions in the Decision Log with IDs and owners; prioritised problem list; A3 draft; updated experiment backlog; changed forecast or strategy scorecard tile.
• Not: "discuss pipeline" or "update everyone" (these are verbs, not products).

1. People — The smallest set of roles that can create the product and own the actions.

• No spectators. Everyone must bring proof, make decisions, or leave with actions.
• Invite by role, not just by name. Example: "one VP Sales" instead of "everyone from Sales".

1. Process — How the time will be used.

• 2-5 bullet agenda with explicit timeboxes.
• Which panels in the revenue dashboard (if applicable).
• Who facilitates, who decides, who takes notes, how the close happens.

1. Proof — The facts and pre-work needed so time is spent deciding, not discovering.

• Bowtie metrics, GRR/NRR, customer quotes, win/loss summaries, A3 snippets.
• Pre-reads sent at least one working day in advance for decision sessions.
• Clear baseline so you can measure later if the decision worked.

5P gate rule: If any P is missing or fuzzy, cancel the meeting or replace it with an async update. A healthy cadence has a non-zero cancel rate.

---

Cadence Design Workflow

Follow this sequence when designing a cadence for a client:

Phase 1: Assess Current State (Week 1)

1. Map existing meetings. What meetings happen now? List them with owner, frequency, duration, attendees, and stated purpose. Include 1:1s, team standups, leadership syncs, and functional reviews.

1. Run the 5P audit. For each meeting, can the owner write down all 5Ps clearly? Where are the gaps? Common failures: no clear Purpose, no Product (just "discuss"), no defined attendees, no pre-work or proof.

1. Identify decision gaps. Where are decisions made today? In the meetings, or in side channels and follow-ups? Is there a Decision Log? How long does it take from insight to decision?

1. Assess data readiness. Is there a revenue dashboard with live dashboards? Can people answer the key questions (pipeline health, GRR/NRR, constraint wall, experiment portfolio status) in minutes?

1. Interview key roles. Ask CRO, CEO, CMO, VP Sales, Head of CS: What decisions are you struggling to make? What meetings feel like waste? Where do you spend time that creates no value? What surprises you about the current system?

Output: A 1-page "Current State" document with audit findings, three pain points ranked by impact, and a rough sketch of what meetings should exist.

Phase 2: Design the Calendar (Week 2-3)

Use the operating cadence template. Adapt the rhythm to client size and stage.

Weekly (7 rituals) — 4.5 hours total

1. Revenue Dashboard: Pipeline and Decisions (75 min)

• Owner: CRO
• Purpose: Review bowtie, pipeline health, constraints, then make at most 3 decisions or A3 assignments
• Product: Decisions logged with IDs, owners, due dates
• Panels: Bowtie and segment views, pipeline by stage, constraint wall, experiment portfolio

1. Marketing Demand and Efficiency Loop (45 min)

• Owner: CMO or Head of Growth
• Purpose: Improve demand quality and SDR efficiency
• Product: Adjusted campaign focus, new experiments with stop rules

1. Sales Pipeline and Efficiency Loop (45 min)

• Owner: VP Sales
• Purpose: Improve pipeline health and sales efficiency
• Product: Clean pipeline, surfaced stuck items, problems framed as A3s

1. CS Value and Efficiency Loop (45 min)

• Owner: Head of CS
• Purpose: Improve retention and expansion
• Product: Account attention list, new countermeasures

1. Coaching and Revenue Craft Loop (45 min)

• Owner: Sales and CS leaders
• Purpose: Turn customer conversations into better plays
• Product: Coaching actions with check-in dates, playbook updates

1. Breach and Incident Huddle (30 min)

• Owner: RevOps on call
• Purpose: Catch and contain SLO breaches
• Product: Owner and containment plan for each breach

1. Automation and Agent Triage (30 min)

• Owner: RevOps and Platform
• Purpose: Prioritise automation and AI opportunities
• Product: Ranked automation experiments

Bi-weekly (1 ritual) — 60 min

1. Demo and Retro (60 min)

• Owner: Rotating facilitator
• Purpose: Show shipped experiments and countermeasures, decide keep/kill/scale
• Product: Keep/kill/scale decisions logged in Decision Log

Monthly (2 rituals) — 150 min

1. Strategy and Lever Review (90 min)

• Owner: CEO and CRO
• Purpose: Review strategy scorecard, choose levers, adjust WIP and SLOs
• Product: Updated WIP caps, next quarter lever list

1. Data Spine and Definition Review (60 min)

• Owner: RevOps and Data lead
• Purpose: Check data freshness and completeness
• Product: Data health status, definition change log

Quarterly (1 ritual) — 180 min

1. Quarterly Reset (2-3 hours)

• Owner: CEO
• Purpose: Refresh strategy scorecard, confirm cadence, align next quarter targets and SLOs
• Product: Updated strategy scorecard, confirmed cadence changes, new SLOs

Key design rules:

• Keep weekly rituals short and focused. No meeting longer than 75 minutes.
• Most rituals feed the same revenue dashboard. No parallel streams.
• Reduce, never add. If you're tempted to add a meeting, cancel an existing one first.
• Schedule decision sessions early in the week. Leave space for countermeasures and follow-up.

Output: Colour-coded calendar showing all rituals, owners, attendees, duration, and which revenue dashboard panels they use.

Phase 3: Build Ritual Cards (Week 3-4)

For each ritual, create a one-pager (the "ritual card") that shows:

• Purpose statement
• Inputs (which dashboards or documents are needed)
• Outputs (what gets decided or changed)
• RACI (Driver, Approver, Contributors, Informed)
• Tollgates (what has to be true for the meeting to happen)
• Cancel rule (when to cancel or shorten)
• Pre-work and proof checklist

Adapt owner names and timings to the client. Print and laminate them. Put them in the revenue dashboard room so facilitators can see the standard at a glance.

Phase 4: Install Signal-Based Decision Rules (Week 8-10)

Once the calendar is stable and people are attending, layer in signal-based decision rules. This is Phase 2 of the 90-day rollout (see below).

1. Week 8: Choose 8-12 key signals from the four capability streams (Customer Insights, Revenue Motions, Enablement, Governance). Start with signals where you already have data.

1. Week 9: Set thresholds using 6 months of historical data. When a signal crosses a threshold, it becomes a trigger (something has changed enough that we need to act).

1. Week 10: Route each trigger to a specific ritual in the cadence. For example:

• Pipeline coverage SMB escalate to Marketing Demand Loop
• Win rate drops >5pp -> open A3 in Sales Pipeline Loop
• Decision latency >14 days -> escalate to Strategy and Lever Review
• 5P cancel rate 0% for 4 weeks -> challenge in Strategy and Lever Review

Print the signal map and post it in the revenue dashboard room. No new meetings. Just clearer escalation rules.

Output: Signal-based decision rules matrix with 8-12 signals, thresholds, and routing rules.

Phase 5: Transfer Ownership (Week 11-12)

In the final weeks of the 90-day programme, transfer operational ownership of the cadence to the client team. The Cadence Owner (usually the CRO or RevOps lead) becomes accountable for:

• Keeping the calendar on track
• Enforcing the 5P gate at the start of each meeting
• Logging decisions and actions in the Decision Log
• Monitoring cadence health KPIs
• Proposing cadence changes only in the Quarterly Reset

Run a "Cadence Keeper" workshop where the Cadence Owner and RevOps lead practice facilitating rituals, handling the 5P gate, and routing signals to the right forum.

---

90-Day Installation Programme

The cadence installs in a 12-week programme with clear phases and handoff points.

Phase 1: Stand-up (Weeks 1-2)

Goal: Assess the current state and design the ideal cadence.

• Audit existing meetings and run 5P gate
• Interview key roles (CRO, CEO, CMO, VP Sales, Head of CS)
• Map decision gaps and data readiness
• Design the calendar (weekly, biweekly, monthly, quarterly)
• Prepare ritual cards
• Brief the leadership team on the design

Output: Signed-off calendar, ritual cards, current state assessment

Phase 2: Co-host (Weeks 3-6)

Goal: Launch the cadence with the consultant as co-facilitator. Build the habit.

• Run all 7 weekly rituals with the consultant co-hosting or observing
• Apply the 5P gate strictly. Cancel or shorten any meeting that fails.
• Log all decisions and actions in the Decision Log
• Build or update the revenue dashboard (if not already done)
• Run the first Demo and Retro (biweekly)
• Run the first Strategy and Lever Review (monthly)
• Observe and coach the CRO on ownership

Output: Live cadence with 4 weeks of decisions logged, habits forming, revenue dashboard live

Phase 3: Hand-off (Weeks 7-10)

Goal: The client team leads the cadence. The consultant coaches and observes.

• The CRO leads all weekly rituals
• The consultant observes and coaches on facilitation, decision quality, and escalation
• Install signal-based decision rules (Week 8-10)
• Run Demo and Retro (biweekly)
• Run Quarterly Reset if applicable
• Coach the RevOps or Cadence Owner on decision logging and cadence health

Output: Client team running cadence independently; decision latency improving; kill rate and 5P cancel rate visible

Phase 4: Certification (Weeks 11-12)

Goal: Certify that the cadence is stable and the client team owns it.

• Client team runs all rituals without the consultant present
• The consultant spot-checks decisions and cadence health KPIs
• Hold final "Cadence Keeper" workshop with CRO, RevOps, and CEO
• Transfer the Cadence Owner role formally
• Schedule quarterly cadence reviews (tuning only in Quarterly Reset)
• Document any customisations or deviations from the standard

Output: Certified cadence; client team owns the calendar and decision log; cadence health KPIs in place

---

Cadence Health KPIs

Track these metrics to see if the cadence itself is working:

1. Decision latency — Time from insight (data signal) to logged decision, and from logged decision to live countermeasure. Target: 20% means the calendar is overloaded.

1. SLO hit rate — Share of weeks where key handover p95 SLOs (lead to first touch, MQL to SQL, etc.) are met. Target: >80%.

1. Freshness attainment — Share of weekly Data Spine checks that pass (data is current, complete, accurate). Target: >95%.

1. Forecast accuracy — Share of periods where actual revenue sits within forecast bands. Target: >70%.

1. Kill rate — Share of experiments killed by stop rule per quarter. Target: 20%+ per quarter. Kill rate 80%.

Review these KPIs monthly in the Strategy and Lever Review. Tune the cadence only in the Quarterly Reset.

---

Revenue Cadence: Meeting Architecture & Ceremony Agendas

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 |
          +--------+--------+
                   |
          +--------v--------+
          |  LEADERSHIP     |
          | (Monthly/QBR)   |
          | Trends+Decisions|
          +--------+--------+
                   |
          +--------v--------+
          |      TEAM       |
          |   (Weekly)      |
          |Pipeline+Forecast|
          +--------+--------+
                   |
          +--------v--------+
          |   ACTIVITY      |
          |    (Daily)      |
          | Calls/Deals/Logs|
          +-----------------+

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

The 7-Question Meeting Architecture

Before scheduling any revenue meeting, answer these:

| Element | Question | Bad Answer | Good Answer | |---------|----------|-----------|-------------| | Purpose | What decision does this produce? | "Check on things" | "Lock forecast by Friday noon" | | Frequency | How often? | "Weekly because that's what we do" | "Weekly for accountability, monthly for trends" | | Participants | Who MUST be here? | "The whole team" | "Sales managers + CRO only (RevOps attends async)" | | Inputs | What prep is required? | People wing it | Pre-built forecast model + deal aging report | | Agenda | How do we spend the time? | Meandering | 15 min data review, 30 min decisions, 5 min actions | | Outputs | What leaves the room? | "We'll figure it out" | Logged forecast, deal actions with owners | | Accountability | Who owns follow-through? | Nobody | Action log with due dates + owner names |

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

Core Ceremony Agendas

Daily: Sales Pipeline Pulse (15 min) Purpose: Surface blockers. Coordinate same-day wins. RevOps not in the room — pre-built CRM views make this self-serve.

Weekly: Pipeline Review (45 min, Sales Manager + team) Pre-meeting packet: stage movement (last 7 days), deal aging by stage, forecast accuracy vs. prior week,

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: NEON-Rutger
• Source: NEON-Rutger/B2B-revops-skills
• License: MIT
• Homepage: https://www.neontriforce.com

Install and usage instructions live in the source repository linked above.