A service business dashboard needs nine numbers that follow work from first enquiry to paid invoice: enquiries, conversations, bookings, open work, stuck work, response time, revenue against pipeline, money owed and open issues. Define each one once, pull it from the system that owns the data, and look at it every week.
Most dashboards I see have too many charts and too few answers. Website visits and social followers sit next to revenue, and nobody can say what changed this week or what to do about it. These are the KPIs every service business dashboard needs, with a plain formula for each, so you can build yours in whatever tool you already use.
Dashboards should answer what moved
A good dashboard answers three questions on a Monday morning: what came in, what's stuck and what's owed. If you can't answer those in under a minute, the dashboard is decoration.
This is a common gap. The ONS measures how UK firms with ten or more staff use key performance indicators, and in its 2023 survey KPI use scored lowest of the four management practices it tracks. That's not because owners don't care. It's usually because the numbers live in four tools and pulling them together takes half a day.
So I'd start small. Nine numbers, one screen, reviewed weekly. You can add more later, but you'll probably find you don't need to.
The nine numbers
Each number below has a plain formula. "This week" can be any period you like, as long as you keep it consistent.
- New enquiries. Count of new enquiries created this week, from all channels. Count people, not messages, so a customer who emails twice is one enquiry.
- Enquiries reaching a conversation. Enquiries this week that led to a real two-way conversation (call, meeting or reply), divided by new enquiries.
- Bookings created and attended. Two numbers: bookings created this week, and bookings attended divided by bookings due this week.
- Open jobs in delivery, by stage. Count of jobs that are started but not finished, grouped by stage (for example, scheduled, in progress, awaiting sign-off).
- Jobs stuck longer than SLA. Count of open jobs that have sat in their current stage longer than the time you've promised or set yourself for that stage.
- Average time from enquiry to first response. For enquiries this week: the time of your first reply minus the time the enquiry arrived, averaged. Track the slowest one too, because averages hide the customer who waited three days.
- Revenue recognised against pipeline open. Revenue recognised this period (work delivered and billable), shown next to the total value of open, qualified opportunities.
- Outstanding invoices or unbilled completed work. Value of invoices past their due date, plus the value of jobs marked complete that haven't been invoiced yet.
- Customer issues open, and the age of the oldest. Count of open complaints or support issues, and the number of days the oldest one has been open.
Number eight deserves a special mention. In FSB research for GoCardless published in 2025, 60% of small businesses said late payment was holding back their growth and 63% said they spent time chasing overdue payments. Unbilled work is the same problem, except the delay is yours.
Rules that keep numbers honest
A dashboard is only useful if people trust it. These rules do most of the work:
- One definition per number, written down. If "enquiry" means something different to sales and to the office, the number is meaningless. Keep a short glossary next to the dashboard.
- One source system per number. Enquiries come from the CRM, revenue from the accounts package, jobs from the job system. Don't let a number be typed in by hand if it can be pulled.
- One owner per number. Someone checks it looks right each week and chases when it doesn't.
- Change definitions in the open. If you change how something's counted, note the date, or you'll compare apples with pears for months.
- Show the trend, not just the total. This week next to the last eight weeks tells you far more than a single figure.
Say you run a lettings agency. If "jobs stuck longer than SLA" counts repair requests that have sat at "awaiting contractor" for more than two working days, the property manager knows exactly which ones to chase on Monday. If it just says "repairs open: 14", nobody knows whether that's good or bad.
Put the numbers in one place
If producing these nine numbers means exporting from four tools every Friday, that's a symptom of disconnected tools, and fixing the plumbing comes first. Our guide on what to automate first is a good place to start. If a key number lives in a spreadsheet only one person understands, see which spreadsheets should be software.
Once the data flows, the dashboard itself is the easy part. Building it so it updates itself and everyone sees the same figures is what we do with Dashboards and reporting, and there's more in our guides.
Questions people ask
What are the KPIs every service business dashboard needs?
The nine above, which follow work from enquiry to paid invoice. If that's too many at once, start with the three that answer "what came in, what's stuck and what's owed": new enquiries, jobs stuck longer than SLA, and outstanding or unbilled work. Add the other six once those three are reliable.
How often should I review my dashboard?
Weekly for most small service businesses, ideally at the same time each week. Response time and stuck jobs may be worth a daily glance if you're busy.
Can I build this in a spreadsheet?
Yes, to start. The risk is that someone has to update it by hand. Once the numbers come straight from your systems, people start trusting them.
Why not include website traffic or social followers?
They can be useful for marketing, but they don't tell you whether work is flowing or money is coming in. Keep them on a separate marketing report.
Sources
- Management practices in the UK: 2016 to 2023 (Office for National Statistics)
- Late payments and payment methods in small businesses (Federation of Small Businesses)