Guide · Reporting

A KPI framework for service businesses

Most service businesses drown in numbers but starve for insight. You do not need a hundred metrics — you need about a dozen that you look at every week, grouped so they tell a story. Here is a simple framework built around four questions: are we making money, are we winning work, are we running well, and are our customers staying?

Updated July 2026 · 7 min read

Money: is the work actually profitable?

Start with the numbers that keep the lights on. Revenue tells you how much you booked, but it hides the truth on its own. Gross margin — revenue minus the direct cost of doing the job — tells you whether your pricing and labor are healthy. Net margin by branch closes the loop by folding in overhead, and it is where multi-location owners usually find the surprise: one branch quietly carries the others.

Watch these weekly, not just at tax time. A margin that slips a few points every month is invisible day to day and brutal by quarter's end. If you track only one thing here, make it gross margin by job type, because it tells you which services to sell more of and which to reprice.

Sales: are we winning the right work?

Sales KPIs answer whether your pipeline is turning into revenue. Average ticket shows how much each job is worth, and nudging it up is often easier than finding new customers. Close rate — the share of quotes that become jobs — reveals whether you are pricing well and following up fast, or leaking estimates that never get a second call.

Pair those with cost per lead so you know what it costs to fill the top of the funnel. When you can see cost per lead next to close rate and average ticket, you can tell instantly whether a marketing channel pays for itself or just looks busy.

Operations: is the field running well?

Operational metrics tell you whether the promises sales made are being kept. Jobs completed is your throughput. On-time rate measures whether you show up in the window you gave, and first-time-fix measures whether you solve the problem on the first visit — the two numbers customers actually feel. A callback or a missed window costs you a truck roll and a little trust every time.

Tech utilization — the share of paid hours that turn into billable work — ties operations back to money. Low utilization usually means routing, dispatch, or scheduling gaps, not lazy techs, and it is one of the fastest levers you have on margin.

Customer: are they staying and coming back?

The cheapest revenue is the customer you already have. Rebooking and retention — the share of customers who schedule again or stay on a plan — is the clearest signal of whether your service earns loyalty. Alongside it, watch receivables and the overdue balance, because revenue you booked but never collected is not revenue at all.

A rising overdue balance is an early warning that your billing process, not your sales, needs attention. Track the aging every week so a slow-paying account gets a nudge at 30 days, not a write-off at 120.

The vanity numbers to ignore

Not every number deserves a spot on the board. Total revenue with no margin behind it, social media followers, website hits, and raw lead volume all feel good and decide nothing. A month of record revenue at a thin margin is worse than a smaller month at a healthy one. The test is simple: if a metric goes up but you would not change a single decision because of it, it is a vanity number — leave it off the weekly review.

Put the dozen on one screen every Monday

A framework only works if the numbers are in front of you. Pick the roughly twelve metrics above, group them by money, sales, operations and customer, and review them the same time every week. The point is not the perfect dashboard; it is the habit of asking the four questions often enough that a small problem is a coaching note, not a crisis.

See the numbers live

Every KPI in this guide, on one command center

Pack Command Center tracks money, sales, operations and customer metrics by branch, department and tech — updated as the work happens, no spreadsheets required.