Sales dashboard
A sales dashboard tells the sales lead each week whether open pipeline still covers the target left to close, and which deals need effort before the period ends. Win rate counts decided deals only, and slipped deals come from the CRM's close-date history, so a deal moved into next quarter still shows as a slip.
Pipeline coverage by team, example
Enterprise coverage falls from 3.5× to 1.75× once stale deals come out
-
New business
£400K3.5× all, 3.0× fresh, needs 2.5×
-
Account management
£300K2.2× all, 2.0× fresh, needs 1.7×
-
Enterprise
£492K £600K3.5× all, 1.75× fresh, needs 2.5×
£630K of £1,260K has sat past its stage ageNeeds 2.5×: 1 ÷ 40% win rate by value
| Team | Target | Closed won | Left to close | Open pipeline due this quarter | Past stage age | Fresh pipeline | Win rate by value | Coverage needed | Coverage, all | Coverage, fresh |
|---|---|---|---|---|---|---|---|---|---|---|
| New business | £400K | £180K | £220K | £770K | £110K | £660K | 40% | 2.5× | 3.5× | 3.0× |
| Account management | £300K | £195K | £105K | £230K | £20K | £210K | 60% | 1.7× | 2.2× | 2.0× |
| Enterprise | £600K | £240K | £360K | £1,260K | £630K | £630K | 40% | 2.5× | 3.5× | 1.75× |
Show the numbers
| Team | Target | Closed won | Left to close | Open pipeline due this quarter | Past stage age | Fresh pipeline | Win rate by value | Coverage needed | Coverage, all | Coverage, fresh |
|---|---|---|---|---|---|---|---|---|---|---|
| New business | £400K | £180K | £220K | £770K | £110K | £660K | 40% | 2.5× | 3.5× | 3.0× |
| Account management | £300K | £195K | £105K | £230K | £20K | £210K | 60% | 1.7× | 2.2× | 2.0× |
| Enterprise | £600K | £240K | £360K | £1,260K | £630K | £630K | 40% | 2.5× | 3.5× | 1.75× |
| Team | Closed won | End of fresh band | End of hatched band | Target |
|---|---|---|---|---|
| New business | £180K | £444K | £488K | £400K |
| Account management | £195K | £321K | £333K | £300K |
| Enterprise | £240K | £492K | £744K | £600K |
Sales KPIs and how to calculate them
Your CRM's opportunities and their stage history feed all eight rows, and coverage adds the target file.
| KPI | Formula | A good reading | The common mistake |
|---|---|---|---|
| Will we hit the period | |||
| Pipeline coverage | Open pipeline with a close date in the period ÷ (target − closed won to date) |
At or above 1 ÷ the team's win rate by value, counting only pipeline that isn't past its stage age | Dividing by the full target. Coverage then looks worse each time a deal is won, though the gap to close has shrunk. |
| Pipeline past stage age | Value of open deals that have sat in their current stage longer than the stage's limit ÷ open pipeline value. On this page the limit is the time four in five won deals spent in that stage. |
Low, and every deal past its age has a dated next step | Measuring age from the day the deal was created. A deal can be young and stuck or old and moving, and only time in the current stage tells them apart. |
| Slipped deals | Open deals whose expected close date moved out of the period they were due in, counted and valued each week from the close date's change history |
Each slip has a reason logged, and a deal that slips twice gets raised in the pipeline review | Reading only today's close dates. A deal moved from 30 November to 15 January looks like a January deal, and the slip leaves no trace. |
| How the team wins | |||
| Win rate on decided deals | Won ÷ (won + lost), by count, for deals closed in the period, split by the stage each deal entered the pipeline at. Win rate by value is the same sum on deal values, value won ÷ (value won + value lost), and it is the rate that sets coverage needed. |
Steady within each entry stage, read apart from the others | Mixing deals created at proposal stage with deals created at first meeting. Late entries win more and lift the rate for everyone. |
| Stage conversion | Deals that reached the next stage ÷ deals that left this stage, for each stage |
Read against the same stage last quarter, from stage history | Working it from each deal's current stage. Deals that skipped a stage, or went back one, vanish from the step they passed through. |
| Average deal size | Closed won value ÷ number of won deals, in the period |
Steady within each team, with any change traced to price or to the mix of deals | Averaging open deal values, which reps set before any price is agreed |
| Sales cycle length | Median days from deal creation to closed won, for deals won in the period. This row uses the median. |
Steady or shortening within each team and entry stage | Taking the mean. One deal that sat open for a year drags the mean, and the median barely moves for one deal. |
| Sales velocity | (Open opportunities × win rate × average deal size) ÷ sales cycle length in days, in pounds a day |
Rising for a reason the team can name | Working one figure across teams that sell at different speeds. It then moves when the mix of teams moves, with nobody selling faster. |
Example data, velocity for Enterprise: 42 open opportunities × 40% win rate × £30,000 average deal ÷ a 105-day cycle = £4,800 a day.
How to build a sales dashboard
Data sources
CRM opportunities with their stage history and close-date history, the target file by team and period, and which team each rep belonged to on each date.
Grain
One row per opportunity per stage change, with the dates it entered and left the stage. Stage age, stage conversion and cycle length all come from this one table.
Refresh cadence
Daily, overnight. Targets change only when sales leadership changes them, and each version is kept.
When a deal counts as lost
When someone marks it closed lost. The dashboard doesn't guess from silence. A deal that has gone quiet stays open and shows in pipeline past stage age until the sales lead decides.
Which date sets the period
Closed won counts on the date the deal was marked won. Pipeline counts on its expected close date as it stands at the time of reading. If your CRM keeps a history of changes to the close date, slipped deals can be counted back over past quarters. If it doesn't, start a nightly snapshot of open deals now, because last quarter's slips can't be rebuilt afterwards.
Questions a sales dashboard should answer
Sales forecasting answers a separate question, whether the quarter's forecast proved right, by measuring accuracy afterwards. What a qualified lead cost is on the marketing KPIs page, and which existing customers to go back to for an upgrade is customer analytics work. Subscription software companies read this pipeline beside MRR, as SaaS analytics shows.
A win rate that counts open deals as lost falls every time the team adds pipeline.
Sales metrics in each tool
Power BI
A Power BI sales dashboard keeps stage history as its own fact table, one row per opportunity per stage, with Opportunity, Team and Date as dimensions. Targets are a second fact table at team and month grain, filtered by the same Team and Date tables. Coverage is then a measure over pipeline divided by a measure over targets.
Data Studio (formerly Looker Studio)
Data Studio connects directly to BigQuery. If the nightly stage history lands there, the coverage page reads it with no export. Work out stage age in the warehouse table, which holds every deal's full history.
Excel
If targets are set in Excel, keep one row per team per month and leave closed won out of the file. Closed won comes from the CRM, so the target file never holds a second, older copy of it.
Google Sheets
A sheet suits the weekly slip review: one row per slipped deal, its old and new close dates, and the reason in the rep's own words. At quarter end the reasons can be counted, and the most common one becomes the next pipeline review's first item.
Enterprise's coverage halves once stale deals come out, and that figure rests on two written rules: when a deal counts as lost, and how long each stage may run. Through our dashboards and BI service, we agree both rules with your sales lead before anything is built on your CRM.
Questions about coverage and slipped deals
How do you set the stage age limit?
It comes from your own won deals, one limit per stage. On this page a deal is past its stage age once it has been in its current stage longer than four in five of the team's won deals were. Count age from the day the deal entered that stage, and recheck each limit once a quarter.
How much pipeline coverage do we need?
You need enough that your team's own win rate turns it into the target left to close. Divide one by the win rate by value on decided deals: a team that wins 40% of the value it decides, as in the example data, needs 2.5 times what is left. Count only pipeline that isn't past its stage age.
Should lost deals include ones that went quiet?
No, not until someone marks them lost. A dashboard that guesses from silence moves the win rate whenever the guessing rule changes. Quiet deals show up in pipeline past stage age, where the sales lead can close them as lost or give each one a dated next step.
How do we track deals that keep slipping?
Compare each deal's close date today with its close date when the period began. Take it from the CRM's change history if it keeps one, or from a nightly snapshot of open deals if it doesn't. Count a slip each time the date leaves the period it was due in, and log the reason beside it.
Can a sales dashboard forecast the quarter?
Only roughly, because it shows what the pipeline can produce at the team's win rate. A real forecast weighs each deal by stage and age and is checked against what actually closed, period after period. That checking is our sales forecasting work, which measures accuracy on periods the model never saw.
Is your coverage real once stale deals come out?
A pipeline export from your CRM with stage dates is enough to split each team's coverage into fresh and stale.