A sales dashboard is one self-refreshing screen holding the five to eight KPIs you steer your sales on: pipeline value by stage, win rate, average deal size, the length of the sales cycle and revenue against target. Roughly half of those describe what still has to happen, not what already did.
Most sales teams now record more than they will ever use. Every deal has a stage, every stage a probability, every rep a target. And then it is Monday morning, someone asks what we are going to land this month, and the answer comes out of the same gut feeling as five years ago.
That is rarely an unwillingness to do the arithmetic. It is what is on the screen. Closed revenue, invoiced, achieved against target: every one of them a figure about a period you can no longer influence. They are not wrong, they are just too late to act on.
A sales dashboard earns its place once it shows the other half as well: what is in the pipeline, how fast it is moving and where it gets stuck. Below: which KPIs those are, how many fit on one screen, what changes per role, and what your CRM has to have settled before any of those numbers means anything.
What is a sales dashboard?
It is one screen that refreshes itself and carries the figures that decide whether you change course. Not a collection of charts about selling, but the five to eight numbers a decision hangs on in the sales meeting.
The difference with a sales report is direction. A report answers a question somebody once asked, usually about a closed period, and is filed afterwards. A dashboard stays open and shows whether something is changing. Microsoft draws the same line in Power BI, where a dashboard is a single page bringing the most important tiles together and a report is the underlying analysis across several pages.
In practice you use them side by side. The dashboard for the weekly conversation, the report for the month or quarter close. Where it goes wrong is when the report becomes the dashboard: then you get a screen full of final scores that nobody can do anything about.
Who is looking also decides what belongs on it. In a mid-sized company that is usually a sales manager with three to ten reps, sometimes a director who runs sales on the side. That is a different starting point from the examples you find online, where a team of thirty sits on a leaderboard and internal competition is half the point. On a small team a ranking like that backfires: with four reps, number four is the same person every week, and they know it too.
Which KPIs belong on a sales dashboard?
Split them in two. Outcomes tell you how it went, efforts tell you what is still coming. A dashboard with only outcomes is a scoreboard; a dashboard with only efforts says nothing about whether any of it works.
- Revenue against target. Not just the amount, but the gap against what you agreed, and the number of days left to close that gap.
- Pipeline value by stage. The sum of open deals, broken down by where they sit. This is the only figure on the screen you can still do something about today.
- Win rate. The share of closed deals you win. Calculate it on closed deals, not on all deals, otherwise your win rate drops every time somebody enters a new opportunity.
- Average deal size. Combined with win rate it tells you how much pipeline a target needs. Twice as many small deals is not the same thing as one round of large ones.
- Sales cycle length. The number of days between first contact and signature. This figure decides whether the deals in there now can still land this quarter.
- Stage conversion. Where do deals drop out? A team that stumbles at the quote has a different problem from a team that cannot get meetings.
- New opportunities this period. The inflow. Without it, a draining pipeline looks like a good month for two months running.
Seven is already on the generous side. Start with the four your team already talks about and add the rest only when somebody asks for them. What a KPI is exactly, and how it differs from an ordinary metric, is in the glossary.
How many fit in the end is not a design question but a behavioural one: what sits below the fold does not get looked at, not even by people who promise they will. Five to eight tiles without scrolling is the practical ceiling. Past eight, every new tile starts crowding out the others rather than adding to them, which is the exact opposite of what a dashboard is for. A rep who has to work through twenty tiles every morning does it exactly one morning.
If you need more, the answer is almost never a bigger screen. It is a second screen for a different role, or a drill-through from a tile into the analysis beneath it. That keeps the opening page readable for someone giving it ten seconds, while anyone who wants to dig still reaches the detail.
Worked example: how much pipeline do you need?
Three of the KPIs above form one sum together, and that sum is probably the most useful thing a sales dashboard can hand you.
Take a team with an annual target of €1,200,000, so €300,000 a quarter. Average deal size is €15,000, which means twenty deals have to be won per quarter. The win rate is 25 percent, so eighty opportunities have to reach a decision to land those twenty.
Eighty opportunities at €15,000 is €1,200,000 of pipeline. Four times the quarterly target, and that factor is no coincidence: it is one divided by your win rate. At 20 percent you need five times your target in pipeline, at 33 percent only three.
Then the sales cycle joins in, ninety days in this example. So that pipeline has to be standing on day one of the quarter. Whatever arrives in week six no longer counts towards this quarter, however hard anyone pulls at it.
That is where the screen earns its keep. A team that knows this sum sees in week one that there is €800,000 in the pipeline instead of €1,200,000, and still has three months to do something about it. A team watching only closed revenue finds the same shortfall in the last week of the quarter, and by then discounting is about the only lever left.
The sum also shows where the cheapest gain sits. Going from a 25 to a 30 percent win rate brings the pipeline you need down from €1,200,000 to €1,000,000. That is two hundred thousand less chasing for the same result, and it is usually easier to arrange than two hundred thousand of extra inflow.
Fill in these four numbers with your own before you build anything. If they do not match what the team expects, you have found the most important discussion in the room before a single chart has been drawn.
Looking back or looking ahead?
This is the line between a screen that gets used and a screen that after six weeks only shows up in browser history.
A dashboard telling you what was invoiced last month hands you no lever at all. That month is over. It is a result, and a result gets read once. Steering happens on the things that can still move: the deals stuck at the quote stage, the accounts nothing has happened with for three weeks, the inflow that started dropping two months ago.
That does not mean closed revenue has to come off the screen. It means it should not be the only thing on it. The rule of thumb we use: if you removed every historical figure, there should still be enough left to hold a conversation about next week. If there is not, you have built a report and called it a dashboard.
In practice it comes down to one thing: next to every outcome, put the figure that causes it. Pipeline next to revenue. Stage conversion next to win rate. New opportunities next to deal size. Then every tile is the start of a question instead of the end of a discussion.
One dashboard per role, not one for everybody
The temptation is to build a single screen everyone gets something out of. That becomes a screen nobody gets anything out of, because the questions differ too much.
- The rep looks at their own deals: what is open, what has not been touched this week, how far am I from target. This screen is a worklist, not an assessment, and that distinction decides whether it gets opened every morning or only when the manager asks.
- The sales manager looks at the team and at the pattern: where do deals fall out, which stage is taking longer than last quarter, what inflow is needed to make November. The sum from the previous section belongs here, because this is the role that can act on it.
- The board looks at how sales relates to the rest of the company: is the revenue coming in also revenue with margin, and can we deliver what is being sold.
That third one is forgotten most often, and it is exactly where sales meets the rest of your steering information. Margin per customer sits in your accounting system rather than your CRM, and that is the same connection you need for a financial dashboard. At board level that pipeline eventually sits next to the financial and operational figures on a single management dashboard. A deal that sales books as a win and finance books as a project at four percent margin is precisely the conversation you want to be able to have at board level without two people spending an afternoon working out who is right.
Do not build all three at once. Start with the role that asks for figures most often, because that is the role that will actually use the screen.
Where the figures come from
Four sources cover nearly any sales dashboard, and each delivers a different piece:
- The CRM. Deals, stages, touchpoints and pipeline. This is the only place holding what still has to happen, which makes it the most important source on the whole screen.
- Your accounting or ERP system. Invoiced revenue and margin. What sales calls a won deal and what finance calls an invoice are rarely the same amount on the same day.
- Quoting or configuration software. If quotes are produced outside the CRM, without this source you miss exactly the stage where most deals die.
- Marketing. Only relevant if you want to follow conversion from the first touch rather than from the first conversation.
Ready-made connections exist for most of these systems; Microsoft maintains a list of every Power Query connector and the common CRM and accounting packages are on it. Whatever is not on the list almost always offers an API or a scheduled export.
Connecting is not the hard part. The hard part is that the same customer is named four slightly different ways across four systems, and somebody has to decide which one is real. What building that model costs and how long it takes is worked out in our article on getting a Power BI dashboard built.
How often all of it refreshes is a smaller question than it looks. Once a night is enough for nearly any sales team: pipeline and win rate do not move by the hour, and a figure that keeps jumping invites watching rather than steering. More often only becomes interesting with a short cycle and high daily volume, a webshop or an inside sales team run on a daily rhythm. For everyone else, this morning’s figure is as useful as one from ten minutes ago, and it saves a lot of discussion about why the amount changed since the last meeting.
The problem most articles skip
Every piece about sales dashboards assumes a well-filled CRM is sitting there ready. Across European mid-sized companies that is the exception rather than the rule.
Eurostat counted 28.51 percent of EU enterprises using CRM software in 2025, and the gap by company size is wide: 24.69 percent among small enterprises against 65.43 percent among large ones. The Netherlands does markedly better than the European average at 54.12 percent, but those figures on e-business software also show that almost half of Dutch companies manage without one.
And having a CRM is not the same as keeping one. Four things turn up in nearly every project:
- Deals get entered after the fact. Often on the day they are won. Your pipeline is then not a forecast but a record, and your sales cycle measures how quickly somebody does admin.
- A stage means something different per rep. For one, “quote” means sent; for another it means discussed. Until that is agreed, your stage conversion is adding apples to pears.
- Lost deals never get closed. They stay open because nobody wants to click them away, and your pipeline gets more optimistic every quarter without anything being sold.
- Amounts never get updated. The value entered at the first conversation stands until the deal closes, while the scope changed twice in between. Your pipeline value is then a sum of first impressions.
None of those four is solved by a prettier screen. They are agreements, and you make them before you build. That is the same order that applies to data-driven working generally: settle what a figure means first, show it second.
The good news is that it is not much work. One two-hour session walking the stages with the team and writing one sentence per stage is enough to prevent most of it. Write those sentences down where the team can find them, not in the notes of whoever ran the session. A definition that lives in one person’s head is the same as no definition at all, and you find that out the week that person is away.
When a sales dashboard is not your first project
There are three situations in which we advise waiting a little longer.
- There is no fixed sales meeting. A dashboard without a moment where it gets discussed does not get discussed. Set that meeting up first, with a manual list if need be, and build the screen once the rhythm holds.
- The CRM is not kept up. Then you are measuring data entry rather than selling, and the dashboard makes that visible in a way that turns the team against it.
- The target is not settled. Without an agreed goal per period, “revenue against target” is an empty tile, and that is the very tile the conversation starts with.
In all three cases the answer is not never, but something else first. What you can do in the meantime: start with one figure instead of a screen. Put pipeline value by stage into a shared file by hand for a few weeks and discuss it at a fixed moment. If that produces a different conversation, you know the screen will pay for itself. If it produces nothing, you are a few hours down rather than a whole project. Our approach opens with the question of which decision has to get better, not with what the screen should look like.
Do you know at the start of the month what you are going to land, or do you hear it at the end? Want to know which KPIs fit your sales process and which sources have to be connected for them? Get in touch, and we will walk your pipeline through with you.
Frequently asked questions
What is a sales dashboard?
A sales dashboard is one self-refreshing screen holding the KPIs you steer your sales on: pipeline by stage, win rate, average deal size, sales cycle and revenue against target. What separates it from a sales report is direction: a report tells you what happened last month, a dashboard shows what is moving now.
Which KPIs belong on a sales dashboard?
Five to eight, split between what you do and what it produces. On the output side: revenue against target, win rate and average deal size. On the effort side: new opportunities, active deals and pipeline value by stage. Sales cycle length and stage conversion describe the speed in between.
How many KPIs should a sales dashboard hold?
As many as fit on one screen without scrolling, which in practice is five to eight. Every tile you add makes the others matter a little less. If you need more, build a second screen for a different role rather than one screen for everybody.
What is the difference between a sales dashboard and a sales report?
A report answers a question somebody once asked, usually about a closed period. A dashboard stays open and shows whether something is changing. In practice you use both: the dashboard for the weekly conversation, the report for the month or quarter close.
Where does a sales dashboard get its data?
Mostly from the CRM for deals and pipeline, topped up with your accounting or ERP system for invoiced revenue and margin. Quoting software, time tracking and marketing tools join in when you want to follow conversion from the first touch. Ready-made connectors exist for most of those systems.
How often should a sales dashboard refresh?
Once a night is enough for nearly any sales team. Pipeline and win rate do not move by the hour, and a figure that keeps jumping invites watching rather than steering. More frequent refreshes only start to pay off with a short sales cycle and high daily volume.
Do you need a CRM for a sales dashboard?
For the pipeline side yes, because that data exists nowhere else. Without a CRM you can still build a revenue dashboard on your accounting system, but then you are only looking backwards. And a CRM that is kept up irregularly produces a dashboard that mainly measures how neatly things were entered.
