A dashboard with forty metrics is a wall of numbers nobody looks at twice. Eight numbers with thresholds is a management tool.
TL;DR Eight metrics maximum. Every one needs a threshold that triggers action. Weekly cadence, on a phone. Build it in a spreadsheet before you buy a BI tool.
The eight
| Metric | Why it earns a slot |
|---|---|
| Cash position and overdue invoices | Survival. Always first |
| Revenue this month vs target | The headline |
| Jobs completed | Volume, and the denominator for everything else |
| Average job value | Pricing and upsell health |
| Enquiries received and converted | Front of the funnel |
| Median first-response time | The strongest leading indicator you have |
| Diary fill, next two weeks | Forward visibility |
| Complaints and callbacks | Quality, and the earliest churn warning |
Response time is the one people leave off and should not. It moves before revenue does, which makes it actionable rather than historical.
Resist adding a ninth. Every addition dilutes attention on the eight that matter.
Thresholds, not just values
A number without a threshold is trivia.
For each metric define
- Green. No action.
- Amber. Look into it this week.
- Red. Act today.
Median first-response time
Green: under 1 hour
Amber: 1 to 4 hours
Red: over 4 hoursOverdue invoices
Green: under 5% of monthly revenue
Amber: 5 to 10%
Red: over 10%
Colour the dashboard by threshold. You should be able to read it in five seconds and know whether anything needs you.
Direction beats snapshot
Every metric needs a comparison.
- Versus last week, for operational metrics.
- Versus the same month last year, for anything seasonal.
- Versus target, where a target exists.
- A small trend line, ideally.
Seasonal comparison matters enormously in service work. Revenue down 30 percent on last month means nothing if last month was your peak. Down 30 percent on the same month last year means something.
Build it in a spreadsheet first
Before buying any BI tool.
Why
- You will discover which metrics you actually look at, which is rarely the list you started with.
- You will find out how hard the data is to get, which is the real constraint.
- It costs nothing.
- It is quick to change while you are still deciding what matters.
A spreadsheet updated weekly, with twelve months of history, is more useful than a live dashboard nobody has configured properly.
Move to a BI tool when manual updating exceeds about twenty minutes a week, or when several people need the same view.
Connecting live data
Most field service and accounting platforms offer either an API or a scheduled export.
Practical approach
- Scheduled export from each system, daily or weekly.
- Land it in a sheet or a small database.
- Calculate the metrics in one place.
- Present from there.
Do not chase real time. Weekly is the right cadence for owner-level decisions, and real-time dashboards encourage reacting to noise.
Watch for definition drift. “Jobs completed” must mean the same thing every week. Write down the definition of each metric next to it, because the definition will otherwise change without anyone noticing and the trend becomes meaningless.
The weekly email
Push it, do not rely on people visiting.
Same time every week. Monday morning works well.
Contents
- The eight numbers with their colours.
- Anything amber or red, with one line of context.
- One thing to do this week.
Under one screen on a phone. If it needs scrolling twice, it will not be read.
Include the one action. A dashboard that reports without prompting a decision is a report, not a management tool.
Mobile
Most owners read this on a phone, standing somewhere.
- Vertical layout. Numbers stacked, not a wide table.
- Large figures, small labels.
- Colour doing the work, so it reads at a glance.
- No hover interactions. They do not exist on a phone.
- Test it on an actual phone before declaring it finished.
Common mistakes
- Too many metrics. The commonest failure by far.
- Vanity metrics. Total customers ever served, social followers, website visits with no conversion context.
- No thresholds, so nothing prompts action.
- Averages hiding distributions. Median response time and average response time can tell opposite stories.
- Never revisiting it. Review the metric set every six months and remove anything you have not acted on.
- Building it and not reading it. Book the fifteen minutes in the calendar.
Beyond the eight
Deeper metrics belong in periodic reviews, not the weekly dashboard.
Quarterly
- Revenue and margin by service line.
- Customer lifetime value by acquisition channel.
- Repeat rate by cohort.
- Billable percentage per technician.
- Marketing cost per acquired customer.
These inform strategy. The weekly eight inform this week. Keeping them separate is what stops the dashboard bloating.
Build the eight-metric sheet this week and fill it in manually every Monday for a month. By the end you will know which metrics you actually use, and that is the specification for anything you build afterwards.
Need a pro to build it? [BOOK A CALL]
