The RevOps Dashboard: 15 Metrics That Give You Complete Revenue Visibility
A single dashboard that shows revenue health across marketing, sales, and customer success. Here's what to include and how to build it.Includes process templates, metric definitions, and team align...
Most revenue dashboards are not dashboards. They are data dumps. Fifty metrics arranged in a grid, half of which nobody looks at, a quarter of which are calculated differently depending on who built the chart, and the remainder of which are genuinely useful but buried under the noise. A RevOps dashboard should answer one question: is our revenue engine healthy? If the answer is yes, the dashboard confirms it in thirty seconds. If the answer is no, the dashboard tells you where the problem is so you can investigate and fix it before the quarter is lost.
This guide defines the 15 metrics that provide complete revenue visibility across marketing, sales, and customer success. For each metric, we cover what it measures, why it matters, how to calculate it, where the data comes from, what a healthy range looks like, and what to do when it signals a problem. This is not a list of every possible revenue metric. It is the minimum set that gives you enough information to manage the entire revenue engine from a single view.
- The 15 metrics are organized into four categories: Pipeline Generation (4 metrics), Pipeline Conversion (4 metrics), Revenue Performance (4 metrics), and Customer Health (3 metrics). Each category covers a critical phase of the revenue lifecycle.
- Every metric needs a definition (exact calculation), a source (where the data comes from), a benchmark (what good looks like), and a response protocol (what to do when the metric moves outside the healthy range).
- The dashboard should be reviewed weekly by the RevOps team, monthly by leadership, and quarterly by the executive team. Each review cadence focuses on different time horizons and levels of detail.
- Build the dashboard in layers: executive summary (5 metrics, one-glance health check), operational detail (all 15 metrics with trends), and diagnostic drill-down (ability to filter by segment, rep, product, and time period).
Dashboard Design Principles
Before defining the 15 metrics, it is worth establishing the design principles that separate useful dashboards from decorative ones. These principles apply regardless of which BI tool you use (Looker, Tableau, Metabase, HubSpot dashboards, Salesforce reports).
Principle 1: One Question Per Section
Each section of the dashboard should answer a single question. The Pipeline Generation section answers: "Are we creating enough new pipeline?" The Pipeline Conversion section answers: "Are we converting pipeline to revenue efficiently?" The Revenue Performance section answers: "Are we hitting our revenue targets?" The Customer Health section answers: "Are our customers healthy and growing?" When a section tries to answer multiple questions, it becomes cluttered and the signal gets lost in the noise.
Principle 2: Trend Over Snapshot
A single number is meaningless without context. "$2.4M pipeline" tells you nothing. "$2.4M pipeline, down 18% from last month and 25% below the trailing three-month average" tells you there is a problem. Every metric on the dashboard should show the current value, the trend (typically a sparkline or bar chart showing the last 6-12 data points), and a comparison to a benchmark (target, prior period, or historical average). The trend is often more informative than the absolute number because it reveals direction and velocity of change.
Principle 3: Actionable, Not Informational
Every metric on the dashboard should have a corresponding action when it moves outside the healthy range. If pipeline generation drops, the action might be to increase SDR activity, accelerate marketing campaigns, or review lead quality from recent campaigns. If win rate drops, the action might be to analyze lost deals for patterns, review competitive positioning, or increase sales coaching on objection handling. If a metric has no corresponding action (it is "nice to know" but nobody does anything when it changes), remove it from the dashboard. It is consuming attention without driving decisions.
Principle 4: Consistent Definitions
The number one source of confusion in revenue reporting is inconsistent metric definitions. What counts as "pipeline"? Is it all open deals or only deals in qualified stages? Does it include renewals or only new business? Is it weighted by probability or at face value? Every metric on the dashboard needs a precise, documented definition that everyone agrees on. Write the definitions in the dashboard itself (hover tooltips or a definitions page) so that anyone viewing the dashboard can verify they understand what they are looking at.
Based on RevOps dashboard implementations across B2B SaaS companies
Category 1: Pipeline Generation (4 Metrics)
Pipeline generation metrics answer the question: are we creating enough new opportunities to hit future revenue targets? These metrics are leading indicators. Problems here show up in revenue numbers 1-2 quarters later, which is why catching pipeline generation issues early is the single most impactful thing a RevOps dashboard can do.
Metric 1: New Pipeline Created (Weekly/Monthly)
What it measures: The total dollar value of new opportunities created within the measurement period. This includes only new business opportunities (not renewals or expansions) at the qualified stage or beyond. Opportunities that are created and immediately disqualified should be excluded.
Why it matters: Pipeline creation is the earliest indicator of future revenue. If pipeline creation drops today, revenue will drop in 1-2 quarters (depending on your sales cycle). By the time the revenue impact is visible, it is too late to fix the pipeline gap.
How to calculate: Sum of opportunity amounts where opportunity created date falls within the measurement period AND opportunity stage is at or beyond your qualified threshold (typically Stage 2 or later in a 5-7 stage process). Exclude renewals and expansions, which should be tracked separately.
Healthy benchmark: New pipeline created should be 3-5x the revenue target for the period. If your quarterly revenue target is $1M, you need $3-5M in new pipeline created per quarter to hit that target at typical B2B win rates (20-30%). If pipeline creation drops below 3x coverage, it is a warning. Below 2x is a crisis.
Response when unhealthy: Diagnose the source. Is it a volume problem (fewer leads entering the funnel) or a conversion problem (leads entering but not qualifying into pipeline)? If volume: check marketing campaign performance, inbound traffic trends, and outbound activity levels. If conversion: check lead quality from recent campaigns, SDR-to-AE handoff effectiveness, and qualification criteria.
Metric 2: Pipeline Coverage Ratio
What it measures: Total open pipeline divided by remaining revenue target for the current quarter. This answers the question: do we have enough pipeline to hit our number?
How to calculate: Total open pipeline (all open opportunities, weighted or unweighted) / (quarterly revenue target minus revenue already closed this quarter). A coverage ratio of 3.0 at the start of the quarter means you have three dollars of pipeline for every dollar you still need to close.
Healthy benchmark: 3x coverage at the start of the quarter. The ratio naturally decreases through the quarter as deals close and pipeline depletes. By mid-quarter, 2x coverage is healthy. By the last month, 1.5x. If coverage is below these thresholds at any point, the quarter is at risk.
Metric 3: Marketing Qualified Leads (MQLs)
What it measures: The number of leads that meet your marketing qualification criteria (lead score threshold, behavioral triggers, firmographic fit) within the measurement period.
Why it matters: MQLs are the raw material that feeds pipeline. MQL volume and quality together determine pipeline creation. MQL volume without quality creates a flood of unqualified leads that wastes sales time. Quality without volume creates a pipeline gap.
How to calculate: Count of leads whose lifecycle stage changed to MQL within the measurement period. Track both the total count and the MQL-to-SQL conversion rate. If MQL volume is increasing but MQL-to-SQL conversion is decreasing, the quality is declining even though the volume looks healthy.
Healthy benchmark: This varies dramatically by industry, ACV, and go-to-market motion. PLG companies might generate thousands of MQLs per month. Enterprise sales companies might generate dozens. The benchmark should be based on your own historical data: what MQL volume has historically produced sufficient pipeline? Set the target based on backward math from the revenue target.
Metric 4: Pipeline Source Mix
What it measures: The distribution of new pipeline by source: inbound (marketing-generated), outbound (sales-generated), partner (referral and channel), and expansion (existing customers).
Why it matters: Over-reliance on a single pipeline source creates fragility. If 80% of your pipeline comes from inbound and Google changes its algorithm or your SEO traffic drops, your pipeline collapses. A healthy source mix provides resilience and indicates that multiple go-to-market motions are working.
Healthy benchmark: No single source should represent more than 50% of total pipeline. A balanced mix for a Series B SaaS company might be: 35-40% inbound, 30-35% outbound, 15-20% partner/referral, 10-15% expansion. The exact targets depend on your growth stage and go-to-market strategy, but diversity is the key principle.
Category 2: Pipeline Conversion (4 Metrics)
Pipeline conversion metrics answer the question: how efficiently are we turning pipeline into revenue? These metrics reveal the health of the sales process: where deals stall, where they leak, and how long it takes to move from qualified opportunity to closed revenue.
Metric 5: Win Rate
What it measures: The percentage of qualified opportunities that result in a closed-won deal. Calculated as closed-won deals divided by (closed-won plus closed-lost) for opportunities that reached the qualified stage.
Healthy benchmark: B2B SaaS win rates typically range from 15-30% for all qualified opportunities. Segment by deal size (enterprise vs. mid-market vs. SMB), by source (inbound vs. outbound), and by rep. Win rate differences across segments reveal where your sales process is strongest and where it needs improvement. A rep with a 35% win rate is doing something different from a rep with a 15% win rate, and that difference is coachable.
Response when unhealthy: Analyze closed-lost deals from the past quarter. Categorize by loss reason (price, product fit, competitor, timing, no decision). If losses are concentrated in a specific reason, the response is targeted: price objections indicate a positioning or discounting problem, competitor losses indicate a competitive enablement gap, and no-decision losses indicate an issue with urgency creation or champion enablement.
Metric 6: Average Sales Cycle Length
What it measures: The average number of days from opportunity creation to close (won or lost). Track separately for won deals and lost deals. Won deals that take too long indicate a bloated sales process. Lost deals that take too long indicate that disqualification is happening too late, wasting sales resources.
Healthy benchmark: Varies dramatically by ACV. $10K ACV: 30-45 days. $50K ACV: 60-90 days. $100K+ ACV: 90-180 days. The trend matters more than the absolute number. If your cycle is lengthening quarter over quarter, investigate. Common causes include: buyers adding more stakeholders to the decision (larger buying committees), reps skipping qualification steps (unqualified deals entering the pipeline and lingering), or competitive dynamics (more alternatives to evaluate).
Metric 7: Stage Conversion Rates
What it measures: The conversion rate between each consecutive stage of your pipeline. What percentage of deals move from Discovery to Demo? From Demo to Proposal? From Proposal to Negotiation? From Negotiation to Close?
Why it matters: Aggregate win rate tells you whether you are converting pipeline. Stage conversion rates tell you where you are losing deals. If 80% of deals pass from Discovery to Demo but only 30% pass from Demo to Proposal, the demo stage is the bottleneck. The response is different from a bottleneck at the negotiation stage (which would indicate pricing or terms issues rather than product demonstration issues).
Response when unhealthy: Focus coaching and process improvement on the stage with the lowest conversion rate. Listen to call recordings from that stage. Review what top performers do differently at that stage compared to underperformers. The stage conversion rate is the most diagnostic metric in the sales process because it pinpoints exactly where deals are failing.
Metric 8: Pipeline Velocity
What it measures: The rate at which pipeline converts to revenue. Calculated as: (number of deals x average deal size x win rate) / average sales cycle length in days. The result is a dollar-per-day metric that represents how much revenue your pipeline produces per day.
Why it matters: Pipeline velocity is the single best summary metric for sales efficiency. It incorporates volume (number of deals), value (deal size), effectiveness (win rate), and speed (cycle length). An improvement in any of the four components increases velocity, and the metric reveals which lever has the most room for improvement.
Healthy benchmark: Track the trend rather than targeting an absolute number. A healthy revenue operation shows steady or increasing pipeline velocity over time. Sudden drops warrant investigation. Gradual decline over multiple quarters indicates a systemic issue that needs structural intervention (process redesign, team training, tool changes) rather than tactical fixes.
Track all 15 metrics in one dashboard
OSCOM connects your CRM, marketing automation, and product data to build a unified RevOps dashboard with real-time metrics, automated alerts, and drill-down analysis. See your revenue engine clearly.
Build your dashboardCategory 3: Revenue Performance (4 Metrics)
Revenue performance metrics answer the question: are we hitting our targets? These are lagging indicators. By the time they show a problem, the problem has already occurred. But they are essential for accountability, forecasting, and board-level reporting.
Metric 9: New ARR (Monthly/Quarterly)
What it measures: Annual recurring revenue from new customers acquired within the measurement period. This is the primary growth metric for subscription businesses.
How to calculate: Sum of annualized contract values for deals closed-won within the period where the deal type is "new business." If you sell monthly contracts, annualize them (MRR x 12). If you sell multi-year contracts, use the annual portion only.
Response when behind target: Decompose the gap. Is it a volume problem (fewer deals closed) or a value problem (deals closing at lower ACVs)? If volume: trace back to pipeline generation and conversion metrics to find the upstream cause. If value: investigate whether discounting has increased, deal mix has shifted toward smaller segments, or specific large deals slipped to next quarter.
Metric 10: Expansion ARR
What it measures: Additional ARR from existing customers through upsells, cross-sells, seat expansion, or plan upgrades. Tracked separately from new ARR because expansion revenue has different economics (no acquisition cost) and different operational drivers (customer success, product adoption, account management).
Healthy benchmark: For SaaS companies past $5M ARR, expansion should represent 20-40% of total new ARR added each quarter. Companies with strong product-led growth can see expansion rates above 50% of total new ARR. If expansion is below 15%, it typically indicates that the product lacks natural expansion vectors (no seat-based pricing, no tiered plans, no add-on products) or that customer success is not positioned to identify and execute expansion opportunities.
Metric 11: Net Revenue Retention (NRR)
What it measures: The percentage of recurring revenue retained from existing customers, including expansion and contraction. Calculated as: (beginning ARR + expansion - contraction - churn) / beginning ARR x 100.
Why it matters: NRR is the single most important metric for long-term SaaS viability. An NRR above 100% means your existing customer base is growing without any new customer acquisition. This is the compounding engine that makes SaaS businesses valuable. An NRR below 100% means you are losing more revenue from existing customers than you are gaining from expansion, which creates a "leaky bucket" where new customer acquisition must outpace customer losses just to maintain flat revenue.
Healthy benchmark: Best-in-class B2B SaaS: 120-140%. Good: 105-119%. Concerning: 90-104%. Critical: below 90%. NRR should be tracked monthly but evaluated on a trailing 12-month basis to smooth out quarterly variability from large contract renewals and annual billing cycles.
Metric 12: Forecast Accuracy
What it measures: How close the actual revenue result was to the forecast. Calculated as: actual revenue / forecasted revenue x 100. A result of 95% means you came within 5% of the forecast.
Why it matters: Forecast accuracy is a meta-metric that measures the quality of your revenue operation's judgment. Accurate forecasts enable confident resource allocation, hiring plans, and investor communication. Inaccurate forecasts (whether consistently over or under) indicate problems with deal qualification, stage criteria, or rep discipline in updating deal status.
Healthy benchmark: Target 90-100% accuracy on the committed forecast (deals in commit and closed categories). The total pipeline forecast will naturally be less accurate (70-85% is typical) because it includes earlier-stage deals with higher uncertainty. Track accuracy by category: committed deals should be 90%+ accurate. Best-case deals should be 50-70% accurate. Pipeline deals should be 20-30% accurate. If committed accuracy is below 85%, your commit criteria need tightening.
Category 4: Customer Health (3 Metrics)
Customer health metrics answer the question: are our customers successful and likely to renew? These metrics are often missing from revenue dashboards because they live in different systems (support, product) and are owned by a different team (customer success). Including them on the RevOps dashboard creates the cross-functional visibility that RevOps promises.
Metric 13: Gross Revenue Churn Rate
What it measures: The percentage of ARR lost to customer cancellations and downgrades within the measurement period. Calculated as: (churned ARR + contracted ARR) / beginning ARR x 100.
Healthy benchmark: Monthly gross churn below 1% (annualizes to less than 12%). Best-in-class enterprise SaaS achieves monthly gross churn below 0.5% (less than 6% annually). If gross churn exceeds 1.5% monthly (18%+ annualized), the company is churning customers faster than most growth rates can compensate for, creating the leaky bucket problem.
Response when unhealthy: Segment churn by cohort (when did the customer start?), by segment (which customer segment churns most?), by product (which plan or feature set has the highest churn?), and by reason (why are customers leaving?). The segmentation reveals whether churn is a broad systemic issue or concentrated in a specific area that can be targeted.
Metric 14: Customer Health Score Distribution
What it measures: The distribution of accounts across health score bands (healthy, at-risk, critical). Rather than showing the average health score (which masks distribution), show the count and percentage of accounts in each band.
Why it matters: The distribution reveals the upcoming pipeline of churn risk. If 30% of your accounts are in the "at-risk" band, you have a future churn problem that has not materialized yet. The health score distribution is a leading indicator of retention, just as pipeline creation is a leading indicator of revenue.
Healthy benchmark: Target 70%+ accounts in healthy band, 20% or fewer in at-risk, and 10% or fewer in critical. Monitor the trend: is the percentage of healthy accounts increasing or decreasing? A slow shift from healthy to at-risk over multiple months is a warning signal even if absolute churn has not increased yet.
Metric 15: Time to Value
What it measures: The number of days from contract start (or trial start) to the first activation milestone. The activation milestone is a product-specific moment when the customer derives meaningful value: first report generated, first workflow automated, first integration connected, first team member invited.
Why it matters: Time to value is the strongest predictor of long-term retention. Customers who activate quickly renew at dramatically higher rates than customers who are still onboarding after 30 days. Every day between contract start and activation is a day where the customer might decide it is not worth the effort, start evaluating alternatives, or simply forget they bought your product.
Healthy benchmark: Depends on product complexity. Self-serve products: under 7 days. Mid-market products with implementation: under 30 days. Enterprise products with full onboarding: under 60 days. Track the trend and set a target based on historical data from your most successful customers (those who renewed and expanded). What was their time to value? That is your target for all customers.
Response when unhealthy: If time to value is increasing, investigate the onboarding process. Common causes: implementation scope growing (customers requesting too many customizations upfront), insufficient onboarding resources (customers waiting in queue for implementation), unclear activation criteria (customers not understanding what "done" looks like), or product complexity (too many steps required to reach initial value).
Building the Dashboard: Technical Implementation
Dashboard Build Process
Document the exact calculation for each metric: the SQL query or formula, the source tables, any filters or exclusions, and the aggregation level (daily, weekly, monthly). Get sign-off from marketing, sales, and CS leaders on every definition. Disagreement on definitions discovered after the dashboard is built wastes time and erodes trust.
Create the data transformations (dbt models, SQL views, or BI tool calculations) that produce each metric. Test each metric against a known dataset to verify accuracy. Compare the dashboard output to manually calculated numbers from a recent period. If they do not match exactly, debug until they do.
Arrange metrics in four sections matching the four categories. Within each section, place the most important metric first and largest. Use sparklines for trends. Use color coding for health (green/yellow/red) but sparingly, only where clear thresholds exist. Add filter capabilities for time period, segment, rep, and product.
Configure automated alerts for metrics that move outside healthy ranges. Set up weekly email distribution to the RevOps team and monthly distribution to leadership. Create a Slack integration for real-time alerts on critical metrics (pipeline coverage dropping below 2x, committed forecast accuracy falling below 85%).
Schedule weekly RevOps review (all 15 metrics, identify issues, assign investigations). Monthly leadership review (summary metrics, trends, action items). Quarterly executive review (strategic metrics, forecast accuracy, annual projection). Annual strategy review (full year performance, target setting for next year).
The Weekly Dashboard Review Meeting
The dashboard is a tool, not a destination. Its value is realized in the weekly review meeting where the RevOps team examines the metrics, identifies issues, and assigns investigation and remediation actions. Without the meeting, the dashboard is a screen that nobody looks at. With the meeting, the dashboard becomes the operating system of the revenue function.
The weekly review should take 30 minutes and follow a consistent agenda. First five minutes: scan all 15 metrics and identify any that are outside the healthy range. Next fifteen minutes: discuss the 2-3 most concerning metrics, hypothesize root causes, and assign diagnostic analysis (who will investigate and report back?). Next five minutes: review action items from the previous week's investigation. What did we find? What are we doing about it? Final five minutes: identify any data quality issues (metrics that look wrong, data gaps, sync failures) and assign fixes.
The key discipline is to focus on exceptions, not on metrics that are healthy. If pipeline generation, conversion, revenue, and customer health are all in the green zone, the meeting can be five minutes: "Everything looks healthy, no action items." The meeting expands only when something is wrong. This keeps the cadence sustainable and prevents "dashboard fatigue" where the team stops paying attention because the meeting feels like a ritual rather than a problem-solving session.
Common Mistakes in RevOps Dashboards
Too many metrics. The most common mistake. A dashboard with 30+ metrics overwhelms the viewer and reduces the likelihood that any metric gets meaningful attention. If you cannot fit all metrics on a single screen (without scrolling), you have too many. Limit the main view to 15 metrics. Provide drill-down views for deeper analysis, but do not put them on the primary dashboard.
Vanity metrics. Metrics that always go up and never require action. Total MQLs generated all-time. Total website sessions. Total emails sent. These metrics make people feel good but do not inform decisions. Every metric on the dashboard should be able to tell you something is wrong. If a metric can only ever tell you things are fine, it is a vanity metric and should be removed.
No targets or benchmarks. A metric without a comparison is just a number. "$850K in new pipeline" means nothing without knowing whether the target was $500K (we are ahead) or $1.2M (we are behind). Every metric needs either a target (based on the plan), a comparison to prior period, or a benchmark against historical averages. Ideally all three.
Stale data. A dashboard that shows data from three days ago is not a dashboard. It is a report. For pipeline and conversion metrics, data should be refreshed at least daily. For activity and engagement metrics, hourly or real-time is ideal. For revenue and churn metrics, daily is sufficient. If your BI tool cannot refresh at the required frequency, consider using a tool that can or building a lightweight real-time dashboard for the most time-sensitive metrics.
Key Takeaways
- 1Fifteen metrics across four categories (Pipeline Generation, Pipeline Conversion, Revenue Performance, Customer Health) provide complete revenue visibility without overwhelming the viewer.
- 2Every metric needs a precise definition, a data source, a healthy benchmark, and a response protocol. Without these, metrics generate confusion instead of action.
- 3Trends are more informative than snapshots. Show the trajectory of each metric over time, not just the current value. Direction and velocity of change matter more than absolute numbers.
- 4The weekly review meeting is what makes the dashboard valuable. Without a regular cadence of reviewing metrics, identifying issues, and assigning actions, the dashboard is decoration.
- 5Less is more. Remove any metric that does not have a corresponding action when it moves outside the healthy range. If nobody does anything when the metric changes, it should not be on the dashboard.
RevOps metrics and dashboards that drive revenue decisions
Metric definitions, dashboard design patterns, and operational frameworks for revenue teams that manage by the numbers. Delivered weekly.
A revenue dashboard is not a technology project. It is an operating system for the revenue function. The technology (BI tool, data pipeline, visualizations) is the means. The end is a shared understanding of revenue health that enables faster, better decisions across marketing, sales, and customer success. The 15 metrics in this guide are not the only metrics that matter. They are the minimum set that covers the complete revenue lifecycle from pipeline generation through conversion through revenue realization through customer retention. Start here. Build the dashboard. Establish the review cadence. And then iterate based on what you learn: add metrics when you need deeper visibility, remove metrics when they stop driving action, and continuously refine definitions as your business evolves. The goal is not a perfect dashboard. The goal is a shared language for revenue health that everyone in the organization understands and trusts.
See exactly where revenue is leaking in your funnel
Oscom audits your funnel across 12 categories and surfaces the specific fixes that increase conversion and retention.