RC-401f · Module 3
Building the RevOps Dashboard
3 min read
A dashboard that shows everything shows nothing. The RevOps dashboard is not a collection of charts. It is a decision-support system with exactly three layers, each serving a different audience and a different decision cadence. Layer one is the executive summary — three numbers the CEO checks daily: current quarter attainment percentage, forecast confidence interval, and pipeline coverage ratio. Layer two is the operational view — the metrics the CRO and VP Sales use weekly: stage conversion rates, deal velocity by segment, rep performance distribution, and pipeline health indicators. Layer three is the diagnostic view — the data CIPHER and LEDGER use to identify root causes when the operational metrics show anomalies.
- Design the Executive Layer Three metrics, no more. Quarter attainment: closed revenue as a percentage of target, updated in real time. Forecast confidence: the spread between best-case and worst-case scenarios from the monthly analysis, expressed as a percentage band around the base case. Pipeline coverage: total weighted pipeline divided by remaining quota, where 3x coverage is healthy and below 2x is a warning. These three numbers tell the executive whether the revenue plan is on track, how certain that assessment is, and whether there is enough pipeline to recover if deals slip. Everything else is operational detail.
- Build the Operational Layer Weekly decision metrics for revenue leaders. Stage conversion rates: what percentage of deals advance from each stage to the next, compared to the trailing 90-day average. A conversion rate drop of more than 10% at any stage signals a systemic problem — competitive displacement, messaging failure, qualification drift. Deal velocity: average days in each stage by deal segment, compared to target. Rep performance: not just quota attainment but activity-to-outcome ratios that identify who is efficient and who is busy. Pipeline aging: deals that have exceeded the average stage duration by more than 1.5x.
- Implement the Diagnostic Layer When the operational layer shows an anomaly — conversion dropped, velocity slowed, pipeline aged — the diagnostic layer provides root cause data. CIPHER drills into cohort analysis: which deal segments are underperforming? Which lead sources? Which competitors are winning the deals you are losing? LEDGER correlates the pipeline anomaly with financial impact: what does a 10% conversion drop at Stage 3 mean for the quarterly forecast? The diagnostic layer transforms "something is wrong" into "this specific thing is wrong, it affects revenue by this amount, and here is where to intervene."
Do This
- Limit the executive layer to three metrics — attainment, confidence, and coverage tell the whole story
- Update the operational layer weekly and compare against trailing averages to detect trend changes
- Build the diagnostic layer to answer "why" when the operational layer shows "what"
Avoid This
- Show executives 20 charts and expect them to find the signal — information overload produces decision paralysis
- Report operational metrics without baselines — a number without context is noise
- Treat the dashboard as a reporting tool — it is a decision-support system and every metric should map to a specific decision