What Should a Sales Dashboard Include?

What a sales dashboard actually is

A sales dashboard is a single screen that shows a sales team its current performance against target, updated automatically from the systems where deals are recorded. It combines results, activity, and pipeline health so a rep can see where they stand and a manager can catch a problem while there is still time to fix it.

The distinction that matters: a sales report looks backward at a closed period. A dashboard shows the period in progress. That difference is the entire reason dashboards exist, and it dictates what belongs on one.

If a number cannot change what someone does this week, it belongs in a monthly report, not on the dashboard.

The 7 components every sales dashboard should include

A complete sales dashboard includes seven components, only three of which are metrics. Most teams get the metric selection roughly right and then ship a screen that still goes unused, because the surrounding structure is missing.

Here is the full component set.

1. A headline number

One number, larger than everything else, answering the question the team opens the dashboard to ask. For most sales teams that is revenue against target for the current period.

The headline number needs a target attached to it. Revenue of $312,000 means nothing on its own. Revenue of $312,000 against a $400,000 quarterly target, with 4 weeks remaining, is a decision.

Give it a cumulative line chart rather than a single figure where you can. A line running against a target line shows pace, and pace is what tells you whether to act.

2. Output metrics

Output metrics are the results: revenue closed, deals won, new recurring revenue, and average deal size. They tell you whether the team is winning.

These are the numbers leadership asks about, which is why most dashboards are built entirely from them. That is also why most dashboards arrive too late to be useful. By the time closed revenue falls short, the quarter is already decided.

3. Input metrics

Input metrics are the activity that produces results: meetings booked, calls made, demos delivered, lead response time, and new pipeline created. They move first, which makes them the early warning system.

A dashboard with only outputs tells you the score. A dashboard with inputs tells you why the score is what it is, roughly 3 to 6 weeks before the score changes.

Include both. Teams that track only activity end up rewarding busywork, and reps learn to inflate call counts without advancing a single deal.

4. Pipeline health signals

Pipeline health is the component most commonly missing, and it is where dashboards earn back their build cost. It covers deals with no scheduled next step, deals sitting in one stage past a threshold, pipeline coverage against target, and deals with a close date in the past.

These are not performance metrics. They are hygiene flags, and they are the ones that quietly wreck a forecast. A pipeline that looks healthy in aggregate often contains a third of its value in deals nobody has touched in 3 weeks.

Display them as counts with a threshold, not as charts. "11 deals with no next step" prompts action. A bar chart of next-step distribution does not.

5. A time comparison

Every metric needs something to be compared against, or the reader has to supply context from memory. That comparison can be a target, the same period last month, the same period last year, or a rolling average.

Pick one comparison convention and apply it across the whole screen. Mixing month-over-month on one tile and year-over-year on the next forces the reader to check the label on every single number, which is exactly the friction that kills dashboard habits.

6. A filter layer

Filters are what let one dashboard serve a team without fragmenting into 9 dashboards. The useful ones for sales are rep or team, region or territory, product line, deal size band, and date range.

Filters have a cost. Every filter is a decision the reader has to make before they see anything, so default every filter to the most common view and let people narrow from there. A dashboard that opens on a blank state waiting for input gets closed.

7. A data freshness stamp

Show when the data last updated, visibly, on the screen. This is a small component with an outsized effect on trust.

The moment a rep suspects the numbers are stale, they stop treating the dashboard as a source of truth and go back to asking in Slack. A timestamp reading "updated 4 minutes ago" prevents that. A dashboard that silently refreshes overnight while looking live does the opposite.

Which sales metrics to include

Choose 6 to 9 metrics for a single screen, weighted toward the ones your team can act on this week. The table below covers the metrics that earn their place most often, grouped by what they tell you.

Sales dashboard metrics grouped by output, input, and pipeline health

One caution on win rate. It is volatile over short windows, so a daily win rate figure is closer to noise than signal for most teams. Keep it on a monthly or quarterly view rather than the live screen.

What to include by role

Build separate views by role rather than one dashboard everyone tolerates. The metrics that help a rep sell are not the ones that help a founder decide whether to hire.

Sales dashboard content by role, with the metrics each role should not see

The leave off column matters as much as the include column. A rep looking at company-wide forecast accuracy learns nothing and loses the habit of checking their own numbers. Precision about audience is what separates a dashboard people open from a dashboard people were told to open.

What to leave off your sales dashboard

Four things belong nowhere on a live sales dashboard, regardless of how interesting they are.

• Vanity metrics with no owner. Total contacts in the CRM, emails sent company-wide, and lifetime deals closed do not change anyone's next action.
• Metrics that only move quarterly. Customer acquisition cost, sales cycle length, and net revenue retention are real metrics that belong in a monthly review. On a live screen they sit static and train people to stop looking.
• Anything requiring a paragraph to interpret. If a tile needs a footnote, it is analysis, not a dashboard element.
• Duplicate views of the same thing. Revenue by month, revenue by week, and revenue by rep all on one screen means three tiles doing one job. Pick the cut that drives the decision and drop the rest.

The hardest discipline in dashboard design is subtraction. Every tile you add reduces the attention every other tile receives, so a 15-tile dashboard is not more informative than a 7-tile one. It is less.

Define your metrics before you build

Write a plain-language definition for every metric before anything gets built, because the same metric name routinely means three different things inside one company.

Win rate is the standard example. Does the denominator include every opportunity created, or only opportunities that reached a qualified stage? Are deals still open counted at all? Two people can look at the same tile, read 34%, and walk away with contradictory conclusions about the team.

For each metric, record four things: the exact calculation, the source system, the refresh cadence, and who owns the definition when it needs to change. This takes an afternoon and prevents the meeting where the dashboard itself becomes the subject of the argument.

The same discipline applies to stage definitions. If "qualified" means a discovery call happened to one rep and a budget was confirmed to another, every pipeline metric on the screen inherits that inconsistency.

Building a sales dashboard when your data is not all in one CRM

Most sales dashboard guides assume your data already sits cleanly inside a single CRM, and for a lot of teams it does not. Deals live in one tool, targets live in a spreadsheet, payments run through Stripe, and inbound leads arrive through a form that writes somewhere else entirely.

You have three practical paths.

Use your CRM's built-in reporting. Fastest to set up and free with the tool you already pay for. The constraint is that CRM dashboards report on CRM data, so the spreadsheet holding your targets and the payment processor holding actual collected revenue stay outside the picture.

Use a dedicated dashboard tool. These connect to common sales sources and handle display well. They work best when your sources are on the supported integration list and your metric definitions match the tool's assumptions.

Build the dashboard as its own small application. This used to mean a developer and several weeks. With an ai dashboard builder, it means describing the screen you want and the sources it should pull from.

That third path is what Emergent is built for. You describe the dashboard in plain language, including the metrics, the role-based views, the filters, and the sources, and the agents build a working full-stack application around it: frontend, database, authentication, and deployment. Because it is a real application rather than a reporting view, the parts that dedicated tools struggle with become straightforward.

• Sources that do not fit a template: pull from a CRM, a spreadsheet of targets, and Stripe into the same screen, with your own calculation for each metric rather than the tool's default.
• Role views without separate builds: built-in authentication means a rep signs in and sees their own pipeline while a manager sees the team, from the same application.
• Metric definitions you control: the win rate calculation is yours to specify and change, not a preset you work around.
• Ownership of what you build: the code syncs to GitHub on paid plans, so a developer can extend the dashboard later instead of rebuilding it.

The same approach applies well beyond sales. Teams use it for a KPI dashboard covering the whole business, and it overlaps naturally with no-code CRM builders when the pipeline data and the dashboard should live in one system.

A checklist before you build

Run through these 8 questions before opening any tool. They apply whether you build in a CRM, a dashboard product, or a custom application.

1. Who opens this screen, and how often?
2. What decision does each metric change?
3. What is the headline number, and what target sits behind it?
4. Which comparison convention applies across the whole screen?
5. Where does each metric's data come from, and how fresh is it?
6. What is the written definition of every metric on the screen?
7. Which 3 filters default to what values?
8. What did you decide to leave off, and where does it live instead?

If you cannot answer question 2 for a metric, cut it. That single filter usually removes a third of the candidate list and improves the result.

Conclusion

A sales dashboard should include seven components: a headline number with a target, output metrics, input metrics, pipeline health signals, a consistent time comparison, a default-set filter layer, and a visible freshness stamp. The metrics inside those components should be chosen by role, capped at 6 to 9 per screen, and defined in writing before anything is built.

The dashboards that fail are rarely missing data. They are usually missing the decision behind each number, which is why they accumulate tiles and lose readers at the same time.

Start with the decisions your team makes every week, work backward to the metrics that inform them, and build only that. If your data sits across several tools and no template fits, describing the dashboard you need is now a faster route than configuring your way toward it.