revenue-operating-cadence

What problem does it solve?

Revenue teams stall and get surprised when their operating cadence fails to convert activity and pipeline reality into disciplined decisions, actions, and board-ready reporting.

Core Features & Use Cases

• Design a scalable meeting architecture: Define purpose, frequency, participants, inputs, agenda, outputs, and accountability so meetings produce decisions and logged actions (not status theater).
• Implement the data pyramid for predictability: Ensure activity data underpins pipeline data, which underpins forecast data, which underpins leadership and board outputs.
• Run the core RevOps ceremonies: Daily pipeline pulse, weekly pipeline review, weekly forecast roll-up, bi-weekly funnel review, monthly business review, and quarterly QBR/board meeting—each with required inputs and explicit decision outputs.
• Fix common cadence anti-patterns: Pre-read enforcement, action logging with owners and due dates, analytical forecasting (commit/best-case/at-risk), metric limits, and cadence-based coaching.

Quick Start

Use this skill to help you redesign your revenue meetings and reporting cadence by asking: "Given our current meeting schedule and the decisions we must make each week and quarter, propose an operating cadence with the right data inputs, agendas, outputs, and an action-logging system that will stop board surprises."