Proje vitrini hazırlanıyorPreparing project showcaseПодготавливаем витрину проекта

Reporting & Analytics

Designing a sales dashboard: the right metric for the right role

Build each screen to answer one question: separate dashboards for the rep, the manager and the owner. How to design a sales dashboard that drives decisions.

Rocketly · 2026-07-17

Most sales dashboards make the same mistake: they show everything and decide nothing. Twelve charts, three colored rings, a wall of percentages. The person looking thinks "not bad," closes the tab, and carries on with the day exactly as before. A sales dashboard that looks busy but moves no one is decoration, not a tool.

This article takes a different starting point: every screen should answer a single question, and that question should change with the role of the person reading it. One view for the rep, one for the sales manager, one for the owner. The goal is not to show the same data three times, but to give each role the one metric that actually changes what they do tomorrow.

A dashboard's job is to trigger a decision, not display data

There is a simple test for any dashboard. Next to every number, quietly ask "so what?" If it triggers an action, keep it; if not, it's ornament. Total website visitors is a pleasant feeling, but on its own it never makes anyone do a specific thing.

A good dashboard behaves less like a spreadsheet and more like a traffic light: green means carry on, amber means pay attention, red means step in. Whoever looks should get the answer to "is everything on track, and if not, where do I look?" in three seconds. Interpret a chart for thirty seconds and the dashboard isn't doing its job.

If a number on your screen can't change what you do tomorrow, it doesn't belong on the screen.

One screen, one question, one role

Even in a small team, people don't share the same worry. The rep out in the field is thinking "who do I call today?" The sales manager is asking "where is the team getting stuck?" The owner wants to know "are we going to hit the number this month?" Try to cram all three onto one dashboard and each person ends up hunting for their answer inside everyone else's noise.

The fix is three lean views by role instead of one "everything included" screen. Each locks onto the single question in one person's head and deliberately leaves the rest out.

SalesdashboardRepManagerOwner
Not one screen, but three views, each answering a single question.

Picking the right metric for each view is its own skill; a list of the KPIs worth tracking is a good starting point, but the art is choosing by role, not pouring all of them onto one screen. Even a one-person business benefits from the split, because "what do I do this morning" and "did we make money this quarter" are genuinely different frames of mind.

The rep's dashboard: "what's next?"

The rep's dashboard should be a to-do list for today, not a report card for last quarter. It serves one question: where do I put my energy in the next few hours? So its weight has to sit on things the rep can actually influence today.

  • Follow-ups due today: Calls to make, quotes to send, and replies owed should live in one list so nothing slips through a crack.
  • Deals that have gone quiet: Open deals with no contact for a set number of days need to surface, because a forgotten deal is a lost deal.
  • Deals with no next step: Any deal without a defined next move on the calendar is quietly on its way to dying.
  • Personal activity pace: Leading counts like calls made and quotes sent this week show today's effort without waiting for the result.

Be careful what you don't put here. A quarterly revenue target or a team-wide conversion rate paralyzes a rep; they can't move those numbers alone, so all it produces is guilt. That's why the weight on a rep's screen belongs on leading indicators you can still change, not results already set in stone.

Picture a company selling PVC windows. The salesperson's morning screen needs two things: customers quoted yesterday and due a callback today, and warm deals gone quiet for three days. Everything else — quarterly revenue, team averages — can leave, because it won't change what their hands do today.

The manager's dashboard: "where is the team stuck?"

The manager doesn't care about individual calls; they care about the shape of the pipeline. This is a coaching screen: which rep is stuck where, which stage is leaking deals, and is there enough in the field to hit the number this month.

  • Conversion by stage: Seeing where deals melt away tells the manager where to spend coaching time and where the process itself is broken.
  • Pipeline coverage: The total size of open opportunities against target warns early whether quota is realistic or a fantasy.
  • Stalling deals: Deals sitting in the same stage past a threshold are exactly where a manager should step in.
  • Rep comparison: Who opens a lot and closes little, and who does the reverse, is a pattern that tells you where coaching should go.

Whether there's enough in the field to make target is a question the pipeline coverage ratio answers better than gut feel. And instead of eyeballing which deals are stuck, a deal health score flags the ones that are aging or losing signals before they quietly die.

The owner's dashboard: "are we going to make the number?"

The owner's dashboard should hold few numbers and a big picture. A founder doesn't want individual calls every morning; they want to know whether the business is healthy. This screen looks at one question: are we hitting target this month and this quarter, and is the foundation solid?

  • Revenue against target: Where we are in the month and how much of the target closed business covers — this is the owner's first glance.
  • Forecast: A projection of where the open pipeline lands by month-end flags surprises while there's still time to react.
  • Win rate and average deal size: The trend in these two says whether growth is healthy or bought with discounts.
  • Repeat revenue and customer value: Whether we're chasing new logos or growing existing ones is a signal of long-term health.

Building that forecast on real pipeline behavior rather than a hunch is what matters here. Moving forecasts from gut feel to real behavior keeps the owner's dashboard from becoming a wish list.

On the owner's dashboard, the real skill is subtraction. A founder can see every metric but doesn't have to; daily call counts aren't their concern, cash and target are. The less you put on the screen, the faster they decide.

Turn CRM data into decisions

Rocketly's reporting builds role-based sales dashboards from your real pipeline instead of hand-filled spreadsheets.

See the dashboards

Cutting the noise: what you leave off

A dashboard is defined more by what you leave out than by what you put in. If everything is important, nothing is. Total lead count, total activities, social likes — these "indicator" metrics feel good but tell no one what to do.

Here's what to consider taking off the screen:

  • Vanity metrics: If you look at a number, feel proud, and then do nothing, that metric is decor, not a decision.
  • Numbers without context: "142 leads" on its own is neither good nor bad; without a target or last month to compare against, it can't be read.
  • Ambiguous charts: A chart everyone reads differently produces debate, not a shared decision.

Choosing the chart is a skill in itself: knowing what each one is good at and what to trust. When report literacy is weak, even clean data gets misread. And, to be honest, a business closing five deals a month doesn't need a fancy dashboard at all — a list will do. A dashboard earns its place once complexity crosses a threshold; before that, it's a time sink.

Build the dashboard in the right order

A good dashboard starts with a question, not a list of metrics. First ask "whose screen is this, and which question does it answer?" The metrics come after.

1Pick the question2One metric3Add context4Set a threshold5Review weekly
A dashboard that decides is built in this order.

It works like this. Nail down the role's single question, then pick the metric that answers it most directly. Add context — a target, a prior period, a benchmark — because a number without context is silent. Set a threshold so the screen knows "fine" from "step in." Finally, review it weekly, because a dashboard nobody looks at rots.

The threshold is the most-skipped step. Without a number for "good" versus "bad," the dashboard means something different to everyone — twenty open deals feels plenty to one person, thin to another. Set a threshold and the screen stops being interpretation and becomes a signal.

Picture a two-person real-estate office. The rep screen says "which listing gets a callback today." The owner screen says "how many closings this month, and how much revenue." Two screens, two questions, zero noise.

Frequently asked questions

How many metrics is ideal?

Five to seven per screen is usually plenty. The goal is a three-second decision, not completeness; the more you cram in, the less clarity you get.

Does a small business even need a dashboard?

Not always. If you close a handful of deals a month, a list is enough. A dashboard earns its keep as deal volume and team size grow and manual tracking gets hard.

Does the dashboard need to be real-time?

For most sales teams, no. A disciplined weekly review produces more decisions than a live screen nobody watches.

Can't I just show everyone the same dashboard?

You can, but it costs you: everyone hunts for their answer in everyone else's noise. Three lean views by role beat one big screen almost every time.

In the end, a good sales dashboard is not a work of art; it's a decision tool. Build each screen around a single question, a single role, and a handful of metrics that matter, and leave the rest out on purpose. Because reporting in a CRM like Rocketly already sits on top of your pipeline data, splitting these three views for the rep, the manager, and the owner without hand-filling spreadsheets is doable. But the thing that comes before the tool is discipline: ask the question first, pick the metric second.