A sales KPI dashboard is a single screen showing the handful of measures a sales team acts on, updated continuously and broken down per person. That is the definition. The reason most of them fail is not that they show wrong numbers, but that they show too many correct ones. A dashboard with thirty tiles gets read carefully exactly once, in the week it is built, and glanced at forever afterwards. The tiles are all accurate. Nobody can tell you what any of them changed.
This is a design problem rather than a data problem, and it has a fix that costs nothing: a rule for what is allowed on the screen.
The rule that keeps a dashboard useful
Every metric on the dashboard must have a named person who would do something differently if it moved.
Not "would be interested to know". Would act. If you cannot name the person and the action, the number is context. Context is genuinely useful and belongs in a report somebody pulls when they have a question. It does not belong on a dashboard, because the cost of a tile is not screen space, it is the attention it takes from the tiles that do change behaviour.
Run that test against an existing dashboard and it usually removes half of it. The survivors, for most sales teams, are a short list.
The five that usually survive
Activity. Conversations held, calls connected, meaningful first contacts. The input a rep most directly controls. It belongs on the dashboard because it moves first and it is the only row a struggling rep can act on today.
Opportunities created. How many of those conversations became something real with a value and a next step. This is where judgement enters the funnel and where a large share of sales problems actually live.
Conversion between those two stages. Expressed as a rate, always shown next to its counts. This single number separates a team that cannot get in front of anyone from a team that gets in front of everyone and loses them, and those two situations need opposite responses.
Revenue, with deal count beside it. Value alone hides the difference between one large deal and eleven small ones, which are different businesses with different risks.
Days since last activity, per person. The most underrated tile on any sales dashboard. Revenue lags the behaviour that produces it by however long your sales cycle runs, so by the time a rep's revenue column looks wrong, the disengagement it reflects is weeks old. Days since last activity moves immediately. It is the tile that prevents problems rather than describing them.
Five tiles. Add a sixth only when somebody genuinely misses it, and require them to name the decision it would change.
Leading and lagging, and why the ratio matters
Revenue is a lagging indicator. It describes what already happened, and by the time it looks bad it has been bad for a while. Quota attainment is lagging. Win rate over a completed period is lagging.
Conversations held, opportunities created and days since last activity are leading. They move first and they leave you time to do something.
A dashboard made entirely of lagging indicators is a financial report with a sales team's names on it. It will tell you accurately, every month, that last month is already over. A working balance is roughly two leading measures for every lagging one, which in the list above is exactly what you get.
This is the same insight behind the balanced scorecard method, which argued in the early 1990s that measuring an organisation on financial outcomes alone describes its past rather than its future. You do not need the full apparatus to take the useful half.
Per person, not just per team
A team-level dashboard tells you whether you have a problem. It almost never tells you where it is, because averages destroy exactly the signal you need.
A team converting 18% of conversations into opportunities sounds like a team with a modest conversion problem worth a group training session. Broken out per person it frequently turns out to be four people at 30% and one person at 4%, which is one coaching conversation, not a training session. The group session would have bored four people and probably not fixed the fifth.
The same applies to any agency reporting across several clients. A rep doing well on one account and badly on another averages to mediocre, which is the least actionable summary available. If you run outbound for multiple clients, the dashboard needs a client dimension even though it makes the table bigger.
Rule of thumb: aggregate to detect, break out to act. A dashboard that can only do the first half is a status board.
Choosing the window, and why a calendar month is often wrong
Most dashboards default to a calendar month because that is how invoices work. For sales management it is frequently the wrong window.
If your sales cycle is longer than the window, outcome metrics are close to meaningless inside it, because almost nothing closes. The dashboard will show near-zero revenue for reasons that have nothing to do with performance, and people will learn to ignore the revenue tile, which teaches them to ignore the dashboard.
If you run cohorts, programmes or quarters that do not line up with month boundaries, a fixed calendar window reports across cohort edges and blends groups that should be compared.
A dashboard worth using lets you set the window. Thirty days is a sensible default. What matters is that the period is yours to choose, and that whatever you choose is stated on the screen, because most disagreements about a number turn out to be two people reading two different windows correctly.
KPI dashboard software, and what actually distinguishes it
There are broadly three ways to get a sales KPI dashboard, and the choice matters more than the feature lists suggest.
A generic dashboard tool connected to your CRM. These are flexible and will draw anything. The catch is that they are a presentation layer over data they do not own, which means somebody has to define every metric inside the tool, and those definitions drift away from the CRM's definitions over time. You end up maintaining the same logic in two places and eventually discovering they disagree. They work well when you genuinely need to combine sources, and they are more maintenance than most teams expect.
Whatever reporting the CRM already includes. The definitions cannot drift because there is only one copy of them. The limitation is that you get the shape of reporting the vendor decided on. For most teams this is the right starting point and it is routinely skipped because building a custom dashboard feels more serious than configuring an existing one.
A spreadsheet. Genuinely fine at small scale, and the honest trade is that it is accurate on the day it is updated and progressively less accurate every day afterwards. The failure is silent, which is what makes it dangerous. Nobody announces that the sheet is now four days stale.
When comparing dashboard software, the questions that separate tools are not about chart types. Ask whether metric definitions live in one place or two. Ask whether the window is configurable. Ask whether you can break any team number down to the person without rebuilding the view. Ask what happens to a metric definition when the underlying field changes. And ask who is expected to maintain it, because a dashboard with no owner degrades quietly.
Sales KPI dashboard examples
A small team selling one product. Five tiles, per person, thirty day window, reviewed weekly. Headline is the conversion rate between conversations and opportunities, because at this size the constraint is almost always the middle of the funnel.
A long sales cycle. Lead with stage progression rather than outcomes: opportunities created, opportunities advanced, pipeline value added. Revenue stays on the dashboard but as a quarterly figure, so nobody reads a normal month as a disaster.
An agency running sales for clients. Two levels. A per-client view for the client conversation, and a per-rep-per-client view internally. Do not try to serve both from one table.
A coach or franchisor. Covered below, because the usual assumptions break.
When the people are not your employees
Everything above assumes the reps work inside your system, where the data is yours by default. A large group of people need precisely this dashboard and cannot have it.
A coach whose clients run their own businesses. A franchisor with independent franchisees. A dealer group where each site keeps its own systems. A course creator whose students are building their own agencies. Every one of them is trying to help a set of people sell better, and every one needs a per-person funnel to do it. None of them can open a dashboard, because the accounts belong to the people being measured.
The substitutes are familiar. A shared spreadsheet that is current for about ten days. A weekly call where everyone reads their numbers aloud. Screenshots sent over chat. All three depend on self-reporting, which has a flaw no amount of discipline corrects: the person doing worst reports least. The gaps in the data line up precisely with the people who need the most help, so the dashboard becomes a chart of who is comfortable being seen.
Fixing it structurally means the data flows between separate accounts on the basis of permission rather than ownership. Each person keeps their own account, and chooses to share a defined slice with whoever is coaching them.
For that permission to mean anything, three properties matter. Declining has to cost the person nothing inside their own account, or it is not a choice. Unshared data should never leave the server, rather than being sent and hidden in the interface, because the second is a front-end decision. And history from before the relationship started should be asked for separately, since it is more than people assume they agreed to even though it is exactly the data that proves a programme works.
Inflowave reports it this way, as part of its sales performance management. Each person on a roster carries leads created, opportunities opened, deals won, revenue closed and last activity for a window you choose, on an account they own and pay for themselves. Metrics are blanked in the database query for anyone who has not accepted, history is its own opt-in, acceptances are append-only against a versioned agreement, and either side can end it whenever they want.
Keeping a dashboard alive
Dashboards decay, and they decay in predictable ways.
They grow. Adding a tile is easy and removing one feels like an admission, so they only ever get longer. Schedule a review where the default action is deletion and every tile has to justify itself against the named-person test.
Definitions drift. Somebody changes what counts as an opportunity and does not restate the history, so a trend line breaks for reasons unrelated to performance. When a definition changes, say so loudly and show the old basis alongside the new one for at least one period.
They lose their owner. A dashboard nobody is responsible for is a dashboard nobody notices has broken. Name a person.
And they get used as a leaderboard when they were built as a diagnostic. If the weekly review opens with the revenue tile and the word "why", people will start managing the tiles rather than the work. Open with the rate between two stages instead. It signals that the conversation is about the mechanism, which is the only part anybody can actually change on a Tuesday.
Sales KPI dashboard examples
A small team selling one product. Five tiles, per person, thirty day window, reviewed weekly. Headline is the conversion rate between conversations and opportunities.
A long sales cycle. Lead with opportunities created, opportunities advanced a stage, and pipeline value added. Revenue stays on the screen but as a quarterly figure, so a normal month does not read as a disaster.
An agency running sales for clients. Two dashboards rather than one: a per-client view for the client conversation, and a per-rep-per-client view internally. Trying to serve both from one table produces something that serves neither.
A team on a contest. The dashboard stays diagnostic and a separate leaderboard carries the ranking. Mixing them turns the diagnostic screen into something people manage rather than read.
Dashboard, scorecard or leaderboard
| KPI dashboard | Scorecard | Leaderboard | |
|---|---|---|---|
| Answers | What is happening now | How is each person doing, by stage | Who is ahead |
| Unit | One tile per measure | One row per rep | One ranked row |
| Audience | The team, continuously | The manager, in a one to one | The floor, publicly |
| Good at | Awareness | Diagnosis | Motivation |
| Cannot do | Tell you who to coach | Create urgency | Explain anything |
Frequently asked questions
What are typical KPIs for sales?
Activity such as calls connected or conversations held, opportunities created, conversion rate between those two stages, revenue with deal count beside it, average deal size, win rate, and days since last activity. Most teams track far more than this. The discipline that helps is requiring every measure on the screen to have a named person who would act differently if it moved.
What are the 5 main KPIs for a sales dashboard?
Activity, opportunities created, the conversion rate between them, revenue reported alongside deal count, and days since last activity. Five is not a magic number, it is roughly the point at which a screen can still be read at a glance. Add a sixth only when somebody genuinely misses it and can name the decision it would change.
What is the difference between a KPI and a dashboard metric?
In practice the distinction worth keeping is between measures you act on and measures that give context. A KPI is the first kind: it has an owner and a threshold at which somebody does something. Context is the second kind, and it is genuinely useful, but it belongs in a report somebody pulls rather than on a screen competing for attention with the numbers that drive action.
What makes a good KPI dashboard?
Few tiles, each with a named owner. A stated time window. Per-person breakdown available without rebuilding the view. Metric definitions that live in one place rather than being duplicated between the CRM and a separate reporting tool, since duplicated definitions always eventually disagree. And an owner for the dashboard itself, because one nobody is responsible for is one nobody notices has broken.
How often should a sales dashboard update?
Continuously is fine for a dashboard, which is the difference between it and a scorecard. The caution is that a live-updating screen invites people to watch it, and watching a number is not the same as acting on one. If the team is refreshing the dashboard rather than working, the problem is usually that it is being used as a leaderboard without anyone deciding to.
Should a KPI dashboard show individual performance?
Yes, and this is where most dashboards fall short. Team averages tell you a problem exists and hide where it is. A team converting 18% might be four people at 30% and one at 4%, which is one coaching conversation rather than a group training session. Aggregate to detect, break out to act.
