What goes on a sales team dashboard?
A sales team dashboard gives reps and managers one shared view of how the quarter is going — how much pipeline is coming in, how deals convert stage to stage, and how long the whole thing takes. This page is the hub: a live example you can click around, the dashboards a sales team typically builds, and the metrics worth putting on them.
For: sales leaders, sales ops, RevOps, and AEs. What’s inside: a live public Metabase dashboard, six dashboards a sales team builds, ten metrics that belong on them, and a five-step build order.
Explore a live sales dashboard
This is a real Metabase, not a screenshot. Click into any card to see the question behind it, change the filters, hover the series, or drill from a bar down to the underlying rows — it behaves exactly the way your own dashboard would.
Which dashboards does a sales team build?
Sales dashboards divide neatly by time horizon: what is in the pipeline now, what will close this quarter, what activity is feeding next quarter, and what renews after that. Build the pipeline view first — every other page reads it from a different angle.
Which metrics belong on a sales team dashboard?
Ten that earn their place on the hub. Roughly in funnel order: what comes in, how it converts, what it is worth, and how reliably you can predict it.
- Meetings booked — first meetings set this period, the earliest input you control. Track it against the no-show rate, since a booking that never happens is not a meeting.
- Pipeline created — new opportunity value added this period, by rep, segment, and source. It is the leading indicator for the quarter after this one, and the first thing to drop when the team is busy closing.
- Pipeline coverage — open pipeline divided by the quota still to be made. Most teams want 3–4x; what the number is worth depends entirely on whether the pipeline in it is real.
- Stage conversion rate — the pass-through rate between each pair of stages. This is where the funnel names its own problem: a healthy top with a collapsing stage-three conversion is a qualification issue, not a volume one.
- Win rate — the share of opportunities that close won. Cut it by source and segment before you read it; a blended win rate mostly tracks which segment you sold into that quarter.
- Sales cycle length — days from first contact to closed won, as a median rather than a mean. Watching it drift is how you catch a deal-desk or procurement change before it hits the forecast.
- Average deal size — the typical value of a won deal. Read it alongside cycle length: bigger deals that take proportionally longer are fine, bigger deals that take twice as long are a capacity problem.
- Customer lifetime value — the long-run value of the account, not the first contract. It is what tells you whether a low-ACV segment is worth the same rep hours as a high-ACV one.
- Deal slippage rate — the share of deals whose close date moves out of the period. Slippage is the honest early warning that a forecast is soft, and it only exists if you snapshot opportunities.
- Forecast accuracy — how close the committed number lands to actuals, tracked over quarters. A team that is consistently 15% under is more useful than one that is randomly right.
How do you build it?
- Land the CRM in the warehouse and snapshot opportunities daily. Metabase can query the CRM’s replicated tables directly, but slippage, coverage history, and “what did the pipeline look like on the 1st” all need the snapshot — start it before you need it, because you cannot backfill history.
- Agree the stage definitions and the quota table. Write down what makes a deal stage three, when an opportunity is created, and which deals count toward whose number, and put it in one Metabase model — otherwise coverage and win rate will disagree with the CRM’s own reports and every meeting starts with that argument.
- Build the pipeline spine first: pipeline created, open pipeline by stage, coverage against quota. Those three cards answer most of what a weekly pipeline review asks.
- Add the conversion and velocity layer — stage conversion, win rate, cycle length, average deal size — then the two forward-looking cards, slippage and forecast accuracy.
- Add filters for period, owner, segment, and source, set an alert on deals with no stage movement in 21 days, and schedule the dashboard to the sales channel before the Monday pipeline call.
Related
Integrations
Other team dashboards
FAQ
How is a sales team dashboard different from a forecast?
A forecast answers one question — what will we close this quarter — and it is a commitment, reviewed with finance and versioned week over week. A sales team dashboard is the operating view underneath it: pipeline created, stage conversion, cycle length, win rate, and activity, so the team can see which of those is causing the forecast to move. Build the team dashboard first; a forecast without a coverage and conversion view behind it is a number nobody can debug.
Who owns a sales team dashboard?
Sales ops builds and maintains it, the VP of sales owns what is on it, and reps should be able to filter it to themselves. That last part matters more than it sounds — a dashboard reps cannot see their own numbers in becomes a management artifact, and CRM hygiene quietly rots because nobody downstream of the data entry ever looks at the result. One dashboard with an owner filter beats one dashboard per rep.
How often should it refresh?
Daily, with the review weekly and the pipeline inspection at whatever cadence your cycle length justifies. CRM data changes continuously, but a dashboard that refreshes hourly encourages people to watch it instead of selling. What genuinely benefits from being fast is alerting: a scheduled alert on deals that have not moved stage in 21 days, or on coverage dropping below target, gets you the value of real-time without the temptation.
Why don't the numbers match Salesforce reports?
Usually because of history. Salesforce reports on the current state of a record, so when a rep edits a close date or an amount, last week's report changes retroactively. If you snapshot opportunities daily into the warehouse, you can hold both views: the live state, and what the pipeline looked like on any past date. Do that early — it is the only way to measure slippage or explain why the forecast moved. The Salesforce and HubSpot guides cover getting the export landed.
Should reps' individual numbers be on the shared dashboard?
By rep, yes; ranked as a leaderboard, be careful. Per-rep pipeline, conversion, and cycle length are how a manager finds the coaching conversation, and hiding them makes the dashboard useless for that. What backfires is a page whose top card is a public ranking on a single metric, because rep-level numbers on small deal counts are noisy — a rep with four deals can move from first to last on one push. Show the per-rep cuts, quote the deal counts alongside them, and keep the ranking out of the header.
How do you keep it from turning into a CRM report dump?
Cap it and route the rest. Ten to twelve cards on the hub, each answering a question the weekly meeting actually asks, and everything else linked out to pipeline, lead funnel, or activity dashboards. Metabase makes the drill cheap — click a bar in the stage conversion card and you get the underlying opportunities — so the hub does not need to carry detail it can hand off in one click.