Most revenue teams build one dashboard and expect four audiences to read it. The rep opens it and finds board metrics. The CFO opens it and finds call counts. Both close the tab and go back to a spreadsheet. The fix is four views built on one metric layer, each answering the question that role is accountable for.
Why does one sales dashboard fail four different audiences?
One dashboard fails because each role owns a different decision, and the metric that drives one decision is noise for the next. A rep decides which deal to work this afternoon. A manager decides which rep to sit in on. A CRO decides whether the quarter will happen the way the plan assumed. A CFO decides whether to hold or revise guidance.| Role | Decision they own | Core metrics | Refresh |
|---|---|---|---|
| Account executive | Which deal to work today | Open deals by close date, deals with no recent change, attainment to date | Daily |
| Sales manager | Which rep to coach and where | Stage conversion by rep, win rate by stage, cycle length, close-date pushes | Daily |
| CRO | Whether the quarter happens as planned | Quarter composition, coverage by segment and age, forecast accuracy trend | Daily |
| CFO | Whether to hold or revise guidance | ARR waterfall, gross retention, net retention, variance to plan | Monthly with a weekly check |
What belongs on an account executive dashboard?
A rep view should list only the deals that rep can move this quarter and flag the ones that stopped moving. ORM treats meaningful activity on an opportunity as a change in stage, close date, or amount. Deals with none of those changes in a defined window belong on a risk list at the top of the rep's screen.The earliest warning on a deal is the absence of a signal. No reply to the last email, no meeting on the calendar, no field changing in the record. That silence shows up before any stage regression does, which makes it the most useful tile on a rep dashboard.
Keep the rep view to roughly six tiles: open pipeline by close date, the silent-deal list, close dates the rep moved this month, attainment against quota, deals closing this month, and next-step dates that have already passed.
What belongs on a sales manager dashboard?
A manager view should compare each rep against the team's own conversion history so coaching lands on a specific stage. Company-level win rate gives a manager nothing to act on. Win rate broken out by stage and by rep shows that one seller loses at proposal while another never gets past discovery, and those two problems need different coaching.Close-date changes deserve their own tile on this view. When a rep pushes a deal from one quarter into the next, that deal becomes less likely to close even while it still sits in commit. A weekly count of pushes per rep turns deal slippage from an end-of-quarter surprise into a Monday conversation.
Add cycle length by rep and coverage measured against that rep's own quota rather than the team number. Coverage averaged across a team hides the rep who is carrying one large deal and nothing else.
What belongs on a CRO dashboard?
A CRO view should show the composition of the quarter rather than the size of the pipeline. Revenue in any quarter comes from three places: deals already in pipeline on day one that close this quarter, deals created and closed inside the quarter, and deals pulled forward from a future period, usually at a discount. Most dashboards report the first source and ignore the other two.Coverage without context is the metric that creates the most noise on an executive view. ORM customer data puts the standard range at 3x to 5x, with most companies near 3.5x and outliers as low as 1.4x. A team can hold 4x and still miss badly when the pipeline sits in the wrong segment, is owned by the wrong reps, has aged past the point of closing, or carries close dates that keep moving. Read more on why pipeline coverage alone is a poor conclusion in the 3x coverage rule breakdown.
Two aging tiles belong here. ORM sees 10% or more of pipeline sitting untouched for 12 months across most customer bases. And of the pipeline carrying in-quarter close dates on the first day of a quarter, roughly 20% actually closes in that quarter, which means the visible number on day one overstates what the quarter will deliver.
What belongs on a CFO dashboard?
A CFO view should reconcile revenue movement month over month and hold the forecast to a measured accuracy number. ORM structures the monthly waterfall as beginning ARR, churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, increased product ARR, and ending ARR, where beginning ARR always equals the prior month's ending ARR. That reconciliation is the backbone of the finance view.Gross and net retention plot on that same chart rather than in a separate tile, because the waterfall rows are the inputs to both. Definitions for net revenue retention vary between finance and sales more than most teams realize, which is why the calculation belongs next to the movement that produced it.
Add a forecast accuracy trend line. Teams that reach roughly 90% accuracy on new and expansion business usually get there through heavy manual effort, and the number stops holding as soon as market conditions shift. Plotting accuracy over time tells the CFO whether the forecast is a measurement or an opinion.
How do you stop four dashboards from disagreeing?
Define every metric once in a shared layer and have all four views read that definition. Almost every dashboard argument is a definition argument. One team counts pipeline created at stage one, another counts it at qualification. One counts win rate on deal count, another on dollars. Both numbers are defensible and they will never match.Write the formula, the source field, the filter logic, and the owner for each metric in a single document. Require a change request before anyone edits a formula. When a number gets challenged in a forecast call, the answer is a lookup rather than a debate.
How do you roll this out without building four separate tools?
Build one metric layer and four saved views on top of it. Start with the CRO view because it forces the hardest definitions. Once the quarter composition, coverage cuts, and accuracy calculations exist, the manager view is a filter on the same data, the rep view is a filter on the manager view, and the CFO view adds the waterfall.Ship one view at a time and watch usage. A dashboard nobody opens after two weeks has the wrong metrics on it, and the fix is asking that role what decision they made last week and what they opened to make it.
Frequently Asked Questions
How many metrics should a sales dashboard show per role?
Six to eight for a rep or manager view, and no more than seven on an executive view. Past that point the reader scans instead of reads, and the dashboard stops driving a decision. If a metric does not change what someone does this week, move it to a diagnostic view.
Should reps and executives see the same numbers?
They should see the same definitions but different cuts. A rep needs deal-level detail on the accounts they own. An executive needs the composition of the quarter across the whole book. Sharing a definition layer means the two views never contradict each other in a meeting.
What is the most common mistake in role-based sales dashboards?
Building the executive view first and pushing it down to reps and managers. Reps then get a coverage ratio they cannot act on, and managers get a company-level win rate that hides which of their people is dragging it down. Build each view from the decision that role owns.
What belongs on a CFO sales dashboard specifically?
A monthly ARR waterfall that reconciles beginning ARR to ending ARR, gross and net revenue retention plotted on that same chart, and a forecast accuracy trend measured against prior submitted forecasts. Deal-level activity does not belong on a CFO view.
How do you keep four dashboards consistent?
Write every metric definition once, store it where all views read from it, and require a change request to alter a formula. Most dashboard disputes are definition disputes, not data disputes, and a shared definition layer removes the argument before it starts.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo