Most revenue dashboards die one of two deaths: they track forty metrics nobody reads, or they track vanity numbers that never change a decision. A RevOps dashboard exists for exactly one purpose — to answer, every week, "will we hit the number, and if not, where is it breaking?" This guide gives you the three-layer structure, the twelve metrics that earn their place, and the build order. (For what the RevOps function owns beyond reporting, see the RevOps complete guide.)
| Layer | Audience & cadence | Contents |
|---|---|---|
| 1. Executive | CRO / founders, weekly glance | Pipeline coverage, win rate, forecast accuracy, NRR |
| 2. Operational | RevOps + team leads, weekly review | All 12 KPIs with trendlines vs last quarter |
| 3. Drill-down | RevOps, when a number moves | Every metric segmented by rep, source, segment, period |
The layering is what keeps the dashboard alive. Executives get four numbers they can hold in their head; operators get enough to spot a trend; and when something moves, layer 3 answers why without anyone exporting to a spreadsheet. One metric, one owner, one definition — written down. Half of all dashboard arguments are actually definition arguments ("does pipeline include stage 1?"), and RevOps settles those once, in writing.
| Metric | Formula | Healthy range (2026) |
|---|---|---|
| Pipeline coverage | Open pipeline ÷ quota | 3–4× (higher for long cycles) |
| Pipeline velocity | (# opps × avg deal × win rate) ÷ cycle days | Trend up quarter over quarter |
| Win rate | Closed-won ÷ qualified opps | ~25–30% of qualified opps |
| Sales cycle length | Avg days from opp created → closed | Segment-dependent; watch the trend |
| Forecast accuracy | 1 − |forecast − actual| ÷ actual | ≥90% by week 2 of the quarter's end month |
| Lead → opp conversion | Opps created ÷ qualified leads | Track by source — blended hides everything |
| Quota attainment | % of reps at ≥100% | Majority of reps hitting; low = quota/hiring problem |
| CAC | Full S&M cost ÷ new customers | Payback < 12–18 months |
| LTV | Avg revenue per account × gross margin × avg lifetime | — |
| LTV:CAC | LTV ÷ CAC | ≥3:1 |
| Net revenue retention | (Start ARR + expansion − churn) ÷ start ARR | >100%; best-in-class 110%+ |
| Data quality score | % of records with required fields complete & fresh | ≥90% on scored fields |
Why data quality makes the list: it's the denominator of everything else. A win rate computed on opportunities where half the close dates are guesses isn't a win rate — it's a mood. Score completeness and freshness on the fields your other eleven metrics depend on, show the score on the dashboard, and watch hygiene improve the moment it becomes visible.
If your pipeline is outbound-driven, layer the funnel metrics upstream of the CRM too — deliverability, reply rate, and meeting rate feed lead→opp conversion. We covered that instrumentation in outbound ROI metrics and published reference numbers in the 2026 outbound benchmarks.
Three layers: an executive view (pipeline coverage, win rate, forecast accuracy, NRR), an operational view with the full 12 KPIs including pipeline velocity, conversion rates, CAC/LTV, and data quality, and drill-downs segmented by rep, source, and segment.
3–4× quota is the standard target — enough that normal win rates still land the number, without stuffing the pipeline with junk. Teams with long sales cycles or low win rates need the higher end.
Roughly 25–30% of qualified opportunities; around 21% across all deals. If yours is far below that, the problem is usually qualification (junk entering the pipeline) before it's closing skill.
Not to start. HubSpot and Salesforce native reporting handle all twelve core metrics. Add BI only when you need cross-object analysis the CRM can't express — and only after the CRM dashboard has survived a quarter of weekly use.
Executives glance weekly; RevOps runs a weekly operational review; drill-downs happen on demand when a metric moves. Monthly reviews are too slow — by the time a monthly review catches a conversion drop, you've lost six weeks of pipeline.
Want dashboard numbers worth trusting? GenFlows builds the data layer underneath — clean CRM records, enriched accounts, and outbound instrumented end-to-end. See the stack that feeds it or talk to our team.
By the GenFlows GTM engineering team. Last updated July 2026.