Executive Dashboard: What It Should Show, With CEO, CRO, CFO and Board Examples

An executive dashboard is one screen that tells a leadership team whether the company will hit its number and where the risk sits. For a B2B SaaS company that means five to seven revenue metrics, each shown against plan with its trend and the range around it, refreshed on the cadence of the decision it supports.

Most executive dashboard examples online are BI vendor screenshots: a revenue tile, a marketing funnel, a ticket count, a headcount chart. They show what a dashboard looks like. They rarely show what a revenue leader needs to see to act early. This guide does that, with four example dashboards (CEO, CRO, CFO and board) built on one illustrative company, so you can see the numbers reconcile from one view to the next.

The bar for the page is simple. The metric that creates the most noise at the executive level is total pipeline coverage without context. It makes executives feel informed while it hides the actual risk. A good executive dashboard does the opposite: it shows how the quarter is going to happen, early enough to change it.

What is an executive dashboard?

An executive dashboard is a decision screen for the people who set targets, budgets and guidance. It aggregates results by segment, region and team, compares each number with plan, and shows enough of the "why" for a leader to ask the right next question.

It is different from the dashboards below it. A rep dashboard is a work queue of open deals; an operational dashboard monitors activity as it happens; a report holds the full detail for analysis. The difference between an executive dashboard and a rep dashboard comes down to grain: executives act on aggregates, reps act on records.

The test for any tile is whether an executive could make a decision from it. If the answer is "no, but it is interesting," it belongs in a report, not a dashboard.

What should an executive dashboard show?

A revenue executive dashboard should show the forecast as a range against plan, how the quarter will be made, whether the pipeline is real, how ARR moved, retention, deal velocity and the cost of growth. That is seven metrics. Every one of them is shown against a comparison, because a number with nothing beside it cannot tell anyone whether to act. Two choices in that table matter more than the rest.

First, the forecast is a range. A board trusts a forecast that is consistent, traceable and framed with a realistic range: a low case, an on-target case and an upper bound. A single number pretends there is only one possible outcome.

Second, coverage is never shown alone. A company can have 4x coverage and still miss badly if the pipeline is concentrated in early stages, dependent on a few large deals, inflated by stale opportunities or built on close dates that keep moving. Coverage belongs next to its composition, not on a tile of its own.

Executive dashboard examples

The four examples below are one illustrative company seen from four seats. It is a B2B SaaS business with $40.0M of ARR at the start of July, a Q3 plan of $4.00M in new and expansion ARR, and it is week 6 of a 13-week quarter. All numbers are illustrative. They are built to reconcile, so the forecast on the CEO view is the same forecast on the CRO, CFO and board views. That consistency is the point: if a number shows up on one screen, it should show up the same way on the next.

CEO dashboard example

A CEO dashboard answers three questions: will we make the quarter, is the business compounding, and is next quarter being built. It is the view behind the weekly stand-up with the CEO, so it leads with status and ends with the decisions on the table.

The pacing chart is the one most CEO dashboards get wrong. Within a quarter the third month is always the largest and the first month the smallest, and a striking share of business closes in the final week. At ORM we break each quarter into a 13-week seasonality profile for each customer. One real example runs 0.70, 0.59, 0.63, 0.81, 0.96, 0.73, 0.60, 1.44, 0.84, 0.68, 1.27, 1.47, 2.27. Without that profile you cannot tell whether you are ahead or behind at week 6.

The math, so you can rebuild it: the first six weights add up to 4.42 out of a quarter total of 12.99, so 34% of the quarter's bookings should be in by the end of week 6 (4.42 / 12.99). On a $4.00M plan that is $1.36M. The company has $1.24M, so it is $0.12M behind its seasonal pace. A straight-line pace (6 / 13 = 46%, or $1.85M) would show it $0.61M behind and set off the wrong alarm.

CRO dashboard example

A CRO dashboard shows how the quarter will be made and which part of it is at risk. It decomposes the forecast into its sources, shows coverage against the gap that is left, and tracks whether deals are moving at the expected pace.

This layout follows the three moves a CRO behind plan at week six should make, in order. First, find the gap: is it deal size, win rate, pipeline or time to close? Second, find what in the pipeline can still be sold this quarter, and stop spending time on deals with no clear path. Third, put executive support where it has the biggest impact. "Sell harder" is not a plan at week six. The dashboard has to show where the gap is.

Look at the two deal size rows. The average open deal is $78K, and the average won deal is $46K. That gap is common: most deals close for less than the amount in the CRM. A forecast that multiplies open deal count by the pipeline average will run high every quarter. For a full role-by-role breakdown of metrics, including the manager and rep views, see our sales KPI dashboard examples by role.

CFO dashboard example

A CFO dashboard shows whether recurring revenue is compounding and whether guidance still holds. Its anchor is the monthly ARR bridge, with gross and net retention on the same screen.

If I could put one chart in front of every SaaS CFO, it would be this bridge: beginning ARR, churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, product increase ARR and ending ARR, month by month, with beginning ARR always equal to the prior month's ending ARR. A reconciling waterfall like that ends most arguments about what "growth" meant last month. The build steps are in how to build an ARR waterfall, and the definitions are on our ARR bridge page.

Renewals sit on their own tile for a reason. There is less uncertainty in a renewal: you usually know the amount and the date, and most renewals close within about 30 days of the renewal date. New business timing depends on when the deal last changed stage. Rolling the two into one number hides the risk in both.

Board dashboard example

A board dashboard shows the full-year trajectory as a range, the record of past forecasts, and the few metrics investors compare across companies. It changes slowly on purpose. The board meets monthly or quarterly, so the screen should explain what changed since the last meeting and why.

The forecast record table is what earns trust over time. If a board can see that last quarter's day-one forecast landed close to the actual, it stops interrogating every line. Accuracy here is 1 minus the absolute error divided by the actual. In Q1 the day-one forecast was $3.10M and $2.76M closed, an error of $0.34M, or 12.3% of the actual, so accuracy was 88%. Whatever formula you use, print it on the board view. For more on the slide side of this, see how to present a forecast to the board and the guide to board reporting cadence.

How should you lay out an executive dashboard?

Put status first, the "how" second, the "why" third and the decisions last. Read top to bottom, the screen should answer: where do we stand, how will the period be made, what is driving it, and what are you asking me to decide. A few rules keep the layout honest:

• Every number has a comparison. Plan, the prior period, a seasonal pace or a sourced benchmark. A bare number cannot tell anyone whether to act.
• Show movement, not just levels. A deal being in Proposal is useful. Knowing that it moved into Proposal yesterday is more useful. ORM snapshots the pipeline every day for this reason: the change in the data carries more signal than the state of it.
• Keep it to five to seven tiles per row of status. Detail lives one click down. See how many metrics should be on a sales dashboard.
• Make every number traceable. If you show a forecast, you should be able to drill down and explain exactly how it came together, down to the deals.
• Print the data cutoff. A snapshot time on the page stops the "which number is right" debate before it starts.

The visual rules (chart types, what sits above the fold, how many charts one screen holds) are covered in our sales dashboard layout guide.

How often should an executive dashboard be reviewed?

Refresh the data daily, and review each view on the cadence of the decision it supports. A weekly decision needs a weekly review; a guidance decision needs the monthly close. The weekly view is a delta report: what changed in seven days and what leadership should do about it. Our guide to the weekly revenue dashboard for leadership meetings covers its six panels and how to keep that meeting short.

How do you build an executive dashboard?

Start from the decisions, lock the definitions, reconcile to finance, then automate. Most of the work is agreeing what the numbers mean, not drawing the charts.

1. List the decisions each executive owns. The CEO funds and hires. The CRO allocates deals and executive time. The CFO sets guidance. The board approves the plan. Each tile has to map to one of those decisions.
2. Lock one definition per metric. Write down what counts as a booking, which amount field is the source of truth, and when a deal is created. We have seen one company with nine competing amount fields (TCV, ACV, ARR, renewal amount and legacy fields that stopped being filled in after 2021). Defining the closed-won booking amount at another took five to seven passes.
3. Reconcile to finance before anyone sees it. When you add up a year of bookings on the dashboard, it should match what the company reports internally. If it does not, the CFO will stop using the screen on day one.
4. Snapshot the pipeline daily. Movement (stage changes, amount changes, close date changes) is what the "why" row runs on, and you cannot show change without history.
5. Add seasonality and a range. Replace straight-line pacing with a weekly seasonal profile, and replace the single forecast number with a floor, expected case and ceiling.
6. Name an owner and a cadence for every view. Reps own their deals, managers own the rollup, regional leaders own their number and the CRO owns the company forecast. Use the same definitions, the same cadence and the same rules every week.

You do not need perfect CRM data to start. Every company thinks its data is uniquely bad. What matters is that it is consistently imperfect, because a consistent pattern can still be modeled and still predicts. Whether you build in the CRM or a BI tool depends on how many sources you blend; we compare the options in CRM dashboard vs BI tool for sales reporting.

What are the most common executive dashboard mistakes?

The most common mistake is a dashboard that makes leaders feel informed while it hides the risk. These are the ones we see most often, and what to put in their place. The one that costs the most is the static forecast. In the first half of 2026, many teams had coverage that looked fine on paper while fewer deals were being decided: not won, not lost, just sitting there, with days in stage creeping up. A coverage tile did not show that. A velocity row and a model forecast that reacts to changing conditions did.

Where does ORM fit?

ORM produces the numbers that the CRO, CFO and board views depend on: a statistical forecast with a range, the quarter broken into carry-over, in-quarter and pull-forward, daily pipeline snapshots for the movement row, and a reconciling ARR bridge with GRR and NRR. ORM targets 95% forecast accuracy on new and expansion revenue from day 1 to day 90 of the quarter, with no manual adjustments, and connects to the CRM and finance systems you already run. ORM's sales forecasting software builds these views from your own data. If you want to see your quarter decomposed this way, schedule a demo.