In this article
- Before building: what the data can support
- Start with management decisions rather than available charts
- Define pipeline, activity, conversion and forecast measures
- Data definitions, refresh cadence and action thresholds
- Management sales-dashboard specification
- Mistakes, and what a used dashboard does
- Questions owners ask
Before building: what the data can support
A dashboard reads the CRM, and reads only what is there. If deals lack values, stages are moved on feeling, sources are not recorded and activities are not logged, the dashboard will be precise about nothing. Check the data quality first: required fields complete, stages honest, sources tagged, next actions present. A month of discipline before the dashboard is better than a dashboard that teaches the owner to distrust the CRM.
Decide who builds and maintains it — the CRM champion or the RevOps owner — and who reads it and when: the owner weekly for fifteen minutes, the sales lead daily for the operational view.
Start with management decisions rather than available charts
Write the decisions first, as questions the owner actually asks: Is this quarter covered, and if not by how much? Which salesperson needs help, and at which stage? Which three deals would change the month if they closed, and what is stuck? Which source is producing customers, not just enquiries? Are we responding fast enough? Is discounting creeping? Each question maps to one or two numbers; anything on the dashboard that does not answer a question the owner asks is removed. The result is usually eight numbers, and it fits on one screen or one page.
Then the audiences: the owner’s page is decisions and trends; the sales lead’s view is operational — today’s overdue actions, this week’s stuck deals; the salesperson’s view is their own list. One dashboard for everyone is a dashboard for no one.
Define pipeline, activity, conversion and forecast measures
Pipeline: qualified pipeline value dated in the period against the target, as coverage; deals by stage with count and value; aged deals past their stage threshold. Activity, used sparingly: new qualified opportunities created per week by source, and response time to new enquiries — the two activity numbers that predict revenue, rather than calls made, which predicts calls. Conversion: stage-to-stage conversion over a rolling quarter, win rate by source and by salesperson, and average sales cycle — the numbers that locate where coaching goes. Forecast: commit, best case and pipeline for the period, against target, with the change from last week and last month’s forecast accuracy beside it.
Add gross margin per deal or discount rate as the ninth, because a team hitting revenue by discounting needs to be seen doing it. Each measure gets one line on the page: this period, last period, target, and a one-word reason for a move.
Data definitions, refresh cadence and action thresholds
Definitions, written down beside the dashboard: “qualified opportunity” means a deal that passed the written standard and reached stage two; “response time” is median hours from enquiry timestamp to first logged attempt; “win rate” is won divided by won plus lost, decided in the quarter, excluding no-response closures; “coverage” is dated qualified value times historical stage probability, divided by target. Without the definitions, two people read the same number and argue; with them, the argument is about the business.
Refresh: the operational view live or daily from the CRM; the owner’s page weekly, on Monday morning, with the numbers frozen so that the week’s comparison is stable; the forecast weekly after the pipeline meeting. Thresholds: for each number, the level at which it becomes an action — coverage below three times target triggers a prospecting push; response time over two hours triggers a coverage check; a salesperson’s stage conversion a third below the team’s triggers a coaching conversation; a deal aged past its threshold appears on the sales lead’s list. The thresholds are what make the dashboard a management system rather than a report.
Decision table · use it here or print it
Management sales-dashboard specification
Eight measures, each tied to the decision it informs. Start from the decision column; a measure that informs no decision is a chart, not a dashboard.
| Measure | Definition | Refreshed | The decision it informs | Act when |
|---|---|---|---|---|
| Qualified leads by source | Enquiries that passed qualification, by first source, this month | Weekly | Where next month’s marketing money goes | A source’s qualified count falls two weeks running |
| Speed to first contact | Median minutes from enquiry to first attempt, by person | Daily | Whether the response standard is being kept | Median above the standard for a person or a day |
| Pipeline by stage | Count and value of open deals per stage | Weekly | Whether there is enough, and where it is stuck | Coverage under 3× target; one stage holds over 40 per cent |
| Stage conversion | Share moving from each stage to the next, trailing quarter | Monthly | Which stage to coach | One stage well below the others, or falling |
| Win rate | Won ÷ (won + lost), by person and by source | Monthly | Coaching, and source quality | Below the team average for two months |
| Forecast vs target | Weighted forecast and commit against the period target | Weekly | Whether to act now on the gap | Forecast under 90 per cent of target with half the period gone |
| Activity | Calls, meetings, proposals per person, this week | Weekly | Whether the inputs are there — never a target in itself | Activity normal but conversion low → quality, not effort |
| Lost reasons | Lost deals by six reasons, trailing quarter | Monthly | Price, product, process or people | One reason above 40 per cent |
Data definitions live with the dashboard, in writing, so that two people reading “qualified” mean the same thing. One page, refreshed automatically from the CRM; if it needs a spreadsheet to build, it will stop being built.
Free to print and share with your team.
Mistakes, and what a used dashboard does
The mistakes: thirty charts from the CRM’s gallery; activity counts as the headline; no definitions, so every number is disputed; a dashboard on dirty data; no thresholds, so nothing triggers anything; one view for everyone; and the owner not reading it, which the team notices in a fortnight. A safeguard: for each number on the page, write the decision it changed last month; if none, take it off.
A used dashboard is read for fifteen minutes on Monday, produces two or three actions, is trusted because its definitions are written and its data is clean, and shows the quarter’s shortfall in week three. This is the dashboard work we do with SMEs — the decision questions, the eight measures, the definitions, the CRM views for each audience, the thresholds, and the weekly review run with the owner for a quarter — and the free audit starts by asking which decision the owner made last week from a number, and which they made from a feeling.
Questions owners ask
Do we need a separate dashboard tool?
Not below several managers reading live. A CRM’s saved views for the operational level and a one-page weekly sheet for the owner cover most SMEs. Tools help when the numbers must combine CRM, accounts and marketing data live.
How many numbers should be on the owner’s page?
Eight or nine: coverage, deals by stage, aged deals, new qualified opportunities, response time, stage conversion, win rate, cycle length, forecast — and margin or discount. Each answers a question the owner asks.
Should salespeople see the same dashboard?
No. They see their own list — today’s actions, their deals, their numbers against their targets. The owner’s page is for decisions across the team; showing it to everyone turns it into a ranking.
How often should it refresh?
Operational views daily or live; the owner’s page weekly, frozen on Monday morning so the week’s comparison is stable; the forecast after the weekly pipeline meeting.
What if the CRM data is not good enough yet?
Fix that first: required fields, honest stages, sources tagged, next actions. A month of discipline, then the dashboard. Built on dirty data it teaches the owner to distrust the system.
What does GullySales do?
The decision questions with you, the measures and written definitions, the CRM views per audience, the thresholds and what they trigger, and the weekly review with the owner for a quarter. Scoped in the free audit and priced in writing.