A sales manager dashboard. Built for one-to-ones, not the board deck.

The short answer. A manager dashboard answers "who, and why," not "how much."

I'm Lauren Pearson, and the dashboard brief I get most often starts the same way: "we need a sales dashboard for the managers." Almost always, what gets built is a smaller version of the executive one, the same pipeline value and win rate tiles, just filtered to one team. It looks finished and gets opened twice before everyone quietly goes back to scrolling the CRM's own pipeline view instead.

The reason is that a frontline sales manager is not asking the same question as a CRO. An executive dashboard answers whether the quarter is on track. A manager has to answer a sharper question for every individual on their team, several times a week: which rep is at risk of missing quota, why specifically, and what needs to happen in this week's one-to-one to change that. That question needs rep-level detail, not a blended team number, which is exactly what most manager dashboards strip out in the name of keeping things simple.

How it works in practice. Five panels, each built around a person, not a total.

The dashboards that survive past the first month in a founder-led sales team share a shape. They are built per rep first, with a team summary at the top rather than the other way round.

1. Pipeline coverage per rep. Open pipeline value against remaining quota, shown as a ratio (most teams work to 3x to 4x coverage as a rough rule, adjusted for the team's actual close rate). A rep sitting at 1.5x coverage three weeks before quarter end is a conversation today, not a surprise at the forecast call.
2. Deals flagged at risk, with a reason. Not a generic "red/amber/green" the rep sets themselves, which tends to drift optimistic, but a rule-based flag: no activity logged in 14 days, no next step dated, or a deal that has sat in the same stage twice as long as the team's median. The reason matters more than the flag; "stalled, no activity 16 days" tells a manager what to ask about in the one-to-one.
3. Activity paired with its outcome. Call or outreach volume on its own tells a manager someone is busy. Paired with meetings booked or pipeline created from that activity, it tells them whether the busyness is working. A rep making far more calls than the team average with meetings booked below the team average has a conversion problem, not an effort problem, and the two need completely different coaching.
4. Forecast roll-up, built bottom-up from the rep's own commit. Each rep's own category calls (commit, best case, pipeline) rolled into a team total the manager can sanity-check against stage-weighted pipeline, rather than a single number nobody can trace back to an individual deal.
5. Ramp status for anyone still new. Time-to-first-deal and time-to-quota against the team's own historical ramp curve, kept visible until a rep has been through at least one full sales cycle, so a slow start gets coached early rather than discovered at the quarter's end.

Five panels is close to the ceiling, not the floor. A dashboard a manager has to study rather than scan before a back-to-back run of one-to-ones gets skipped the first busy week, and skipped dashboards do not come back into rotation on their own.

The order these panels appear in matters more than it looks. Pipeline coverage and deals at risk belong at the top, because they answer the question a manager is actually walking into the one-to-one to ask. Activity and ramp status belong lower down, as context the manager pulls up only once the risk conversation points towards an effort or onboarding issue rather than a deal-specific one. A dashboard that leads with activity trains managers to open every one-to-one with "how many calls did you make," which is rarely the most useful question and tends to put reps on the defensive before the conversation about an actual stuck deal has even started.

What good looks like. Live, rep-first, and reviewed on a fixed cadence.

A manager dashboard earns its place by being faster to check than opening five separate deal records. That only holds if it pulls live from the CRM rather than a spreadsheet someone updates "when they get a chance." A once-a-week manual refresh is a report, which is a different, slower-moving thing than a dashboard, and calling it a dashboard sets an expectation the tool cannot meet.

Cadence matters as much as content. The most common working pattern is a quick scan before each one-to-one, rather than a dedicated weekly dashboard review meeting that tends to turn into a status read-out. The dashboard's job is to make the manager walk into that one-to-one already knowing which deal to ask about, not to be the meeting itself.

Where attainment sits across a team is worth tracking against a wider benchmark, not just last quarter's internal number. The Bridge Group's 2026 AE Models, Motions and Metrics report, its tenth edition, drawing on survey responses from 158 B2B companies, found 48% of account executives at quota in 2026, down from 51% in 2024, with average ramp time to full productivity at 6.2 months, the slowest point in the study's history. A team sitting meaningfully below 48% is not automatically a coaching failure; it is worth checking first whether quota-setting or territory assignment moved out of step with the market, since a dashboard can surface the gap but cannot tell a manager which lever actually caused it.

That ramp figure is worth sitting with for a moment, because it changes how a manager should read a new rep's early dashboard numbers. A rep six weeks into the role showing thin pipeline coverage looks, on a dashboard built only for established reps, identical to a tenured rep in genuine trouble. Separating the ramp panel out, and benchmarking it against the team's own historical ramp curve rather than a mature rep's steady-state numbers, stops a manager coaching a new starter as though they were underperforming against a bar they have not had time to reach yet.

A worked scenario. Where the activity numbers were lying.

A founder-led B2B team I worked with had a rep whose weekly call volume sat comfortably above the team average, every week, for a full quarter. On a generic activity dashboard, that rep looked like the strongest performer on the team. Pipeline created from those calls told a different story: roughly half the team average, despite close to double the call volume.

The dashboard change that mattered was not adding more metrics. It was pairing the one activity number the manager already had with the one outcome number that gave it meaning, on the same screen, next to each other. Once the two sat side by side, the coaching conversation moved in a week from "keep making calls" to "we need to look at what you're saying in the first ninety seconds," which turned out to be the actual problem: a pitch that opened with company background instead of the prospect's own situation. Call volume alone would never have surfaced that; it would have kept rewarding the wrong behaviour. This is an illustrative pattern I have seen recur across several teams, not a single named client result, but the mechanism, pairing activity with outcome on one screen, is the generalisable fix.

Pitfalls to avoid. Where manager dashboards quietly stop getting opened.

Copying the executive dashboard and filtering it to one team is the most common failure, because it answers the exec's question at a smaller scale rather than the manager's actually different question. If a manager dashboard could be built by just removing a filter from the leadership one, that is usually a sign it was built from the wrong brief.

Letting reps self-report deal health is the second. A manager dashboard built on rep-entered red/amber/green status reflects how the rep feels about the deal, which skews optimistic under quota pressure far more often than it skews pessimistic. Rule-based risk flags, built from CRM activity timestamps and stage duration, do not have an incentive to look good in the one-to-one.

Adding metrics instead of removing them is the third, and the one that kills a dashboard slowest. Every well-meaning request for "just one more number" adds a line a manager has to parse before they can find the one they actually came for. Our revenue operations work on dashboard builds spends more time removing panels than adding them for exactly this reason, and our sales dashboard engagements start every build from the specific decision a manager needs to make, then work backwards to the three or four numbers that decision actually needs. Our companion piece on what belongs on an executive sales dashboard covers the leadership-level version of this same discipline, and our guide to CRM dashboard metrics worth tracking goes deeper on the formulas behind each number above.

The last pitfall is building the dashboard once and never revisiting who it is for. A team that doubles in size, or starts selling a second product line with a different sales cycle, usually needs its risk-flag thresholds and coverage ratios recalibrated, not just more rows added to the same table. A manager dashboard that was right for a five-person team a year ago can quietly stop being right for a team of fifteen without anyone noticing, because the numbers still populate and the panels still look the same; only the thresholds behind them have gone stale.