The dashboard nobody looks at twice
It's easy to build a sales dashboard. Modern CRMs will happily plot every field you own — deals by stage, by rep, by source, by month, by day of week — and the result looks impressive in a screenshot and changes no one's behavior. A sales dashboard is supposed to answer, at a glance, "how are we doing and what should I do about it?" The cluttered version answers neither, because a screen with twenty numbers has no point of view, and a chart nobody acts on is decoration with a refresh rate.
The discipline of a good dashboard is subtraction. The hard question isn't "what can I show?" — it's "what would change what someone does today?" Every tile that doesn't pass that test is noise crowding out the few that do.
Start from the decision, not the data
The mistake is building a dashboard from the metrics that are available. Build it instead from the decisions the viewer makes. For a small sales team, those decisions are concrete: Who do I call first today? Which deals are about to stall? Are we going to hit the number this quarter? Is our pipeline big enough to bother?
Every tile should map to one of those questions. If you can't say which decision a chart informs, it doesn't belong — no matter how interesting it is. "Interesting" is the enemy here; a dashboard is not a museum, it's a control panel.
This is also why a dashboard is different from the broader question of which sales metrics actually matter. That article is about understanding the metrics; this one is about staging the handful of them that should be in front of someone every day, arranged so the story reads itself.
The metrics that earn a tile
For most small sales teams, a working dashboard needs surprisingly few numbers — and a mix of outcome metrics (where you landed) and leading metrics (what predicts where you'll land). The outcome metrics tell you the score; the leading ones let you change it before the period ends.
A defensible core:
- Weighted pipeline vs target. The single most important tile: total open pipeline weighted by stage probability, set against the quota. This is the "are we going to make it?" number, and it belongs top-left where the eye lands first.
- Pipeline coverage. Open qualified pipeline divided by what's left to close. Below roughly 3–4x coverage and the target is at risk no matter how hard anyone works — a leading indicator you can act on while there's still time.
- Deals stalled by stage. A count of deals that haven't moved in longer than they should. This is the most action-producing tile on the board, because each one is a specific deal to go rescue today, not an abstraction. It pairs directly with re-engaging stalled deals.
- Win rate and average cycle length. The two ratios that drive every forecast. A slipping win rate or a lengthening cycle is an early warning the headline revenue number won't show until it's too late.
- Sales velocity. The one composite that ties pipeline, win rate, deal size, and cycle length into a single trend — covered in depth in sales velocity.
Five or six tiles. If you're adding a tenth, ask which of the first nine it's more important than — and if the answer is none, don't.
Lay it out so the story reads in five seconds
A dashboard is a visual argument, and layout is most of the argument. A few rules that separate a glanceable board from a wall of charts:
- Most important, top-left. Eyes start there. The "are we going to hit it?" number goes first; the supporting detail flows down and right.
- One idea per tile. A chart trying to show three things shows none. If a tile needs a paragraph to explain, split it or cut it.
- Compare against something. A number alone is trivia. Revenue against target, this month against last, a metric against its trend — comparison is what turns a value into a judgment.
- Pick the right shape. Trends over time want a line; parts of a whole want a bar; a single status ("$84K weighted vs $120K target") often wants nothing but a big number and a color. Resist the pie chart.
The five-second test is the bar: a viewer should grasp the headline state of the business before they've consciously read anything. If they have to study it, it's a report, not a dashboard.
Build one per audience, not one for everyone
The reason most dashboards bloat is that they try to serve everyone, so they serve no one. A rep and a founder are asking different questions, and a single shared board compromises on both.
The rep wants a today view: who to call first (lead score ordered), which of my deals are stalling, what tasks are due. It's operational and personal — the answer to "what do I do in the next hour?"
The founder or manager wants a position view: weighted pipeline vs target, coverage, win-rate trend, velocity across the team. It's strategic and aggregate — the answer to "are we going to be okay this quarter, and where's the risk?"
Same underlying data, two different framings. Building both is cheap once the data is clean; forcing both audiences onto one board is what produces the twenty-tile monster nobody trusts.
Make it live, not a Monday export
A dashboard you rebuild by hand every week is a dashboard you'll stop rebuilding by March. The whole value is that it's current — a real-time read on the business you can glance at any moment, not a snapshot that's stale by Tuesday. That requires the numbers to roll up automatically from the records reps already touch.
In Hitt CRM, weighted pipeline, win rate, deal outcomes, and stage movement roll up from live deal and contact data into reports you don't have to assemble, so the dashboard reflects what's true right now rather than what was true at the last export. Because the pipeline and lifecycle stages feeding it are derived from real activity, the board stays honest only to the degree your pipeline hygiene and data hygiene do — a dashboard built on mis-staged deals is confidently wrong, which is worse than no dashboard at all.
The one-sentence version
A sales dashboard earns its keep only when every tile maps to a decision someone actually makes, the five or six metrics that drive behavior are arranged so the headline state reads in five seconds, you build a separate operational view for reps and position view for the founder instead of one bloated board for both, and the whole thing rolls up live from clean pipeline data — because a dashboard you can't trust or won't read is just decoration with a refresh rate.