The weekly numbers meeting: eight figures on one page beat a dashboard nobody opens

The eight numbers

• Calls and form submissions received. The top of everything. Counted, not estimated — and separated between new customers and existing ones, because the two mean different things.
• Booking rate. Of those inquiries, how many turned into a scheduled job. This is the single most diagnostic number in a service business, and almost nobody tracks it. A drop here with steady call volume is a phone problem, not a marketing problem.
• Quotes issued and quote value. For companies that estimate before working. Both the count and the dollars, because ten small quotes and three large ones are different weeks.
• Quote close rate. Measured on quotes issued at least two weeks ago, not on this week's, or the number is meaningless.
• Jobs completed and revenue billed. The lagging core, split by job type if the mix matters.
• Average ticket. Moves slowly and reveals a great deal — a falling average ticket with rising job count is a company working harder for the same money.
• Booked hours for next week. The clearest forward view a service company has. Below a threshold, it triggers action this week rather than an empty calendar next week.
• Cash collected and accounts receivable over 30 days. Revenue billed is not money. The gap between the two is where service businesses fail while looking profitable.

Eight is not arbitrary. A page with fifteen numbers stops being read within a month, and one with four cannot diagnose anything. Eight fits on a screen, takes fifteen minutes to review and covers the whole chain from inquiry to cash.

The meeting: thirty minutes, same time, same order

The meeting is what makes the numbers work, and its value comes almost entirely from being boring and unmissable.

The format that holds up: same day and time every week, thirty minutes with a hard stop, the same eight numbers in the same order, each read aloud with the prior week and the target beside it. Whoever owns a number reports it — the person answering the phone reports calls and booking rate, the estimator reports quotes, the office reports cash and receivables. That distribution is the point: a number with an owner gets watched all week, and a number the owner reads out alone gets watched on Fridays.

Three rules keep it from decaying. Do not solve problems in the meeting — identify, assign, and move on, because one long discussion turns a thirty-minute rhythm into a ninety-minute meeting people avoid. Do not add numbers casually; the page grows by replacement, not by accumulation. And never skip it in a busy week, since the busy weeks are exactly the ones where the leading indicators are about to turn.

A worked example

A residential plumbing company with four technicians and one office person built the page and ran it for a quarter. Week one looked like this: 94 inquiries, 61 booked for a 65% booking rate, 22 quotes issued worth $41,300, close rate of 38%, 78 jobs completed, $52,400 billed, $672 average ticket, 118 booked hours for the following week, $47,900 collected and $28,600 over 30 days.

Two things were visible immediately that had never been visible before. The booking rate of 65% meant 33 inquiries a week — roughly $22,000 of potential work at the average ticket — were arriving and not converting. And $28,600 sitting past thirty days was more than half of a week's revenue.

Neither problem was new; both had been invisible. The company made two changes. Calls that went unanswered were routed to a second phone and returned within fifteen minutes, and every job over $800 required a deposit at scheduling rather than payment at completion.

Twelve weeks later: booking rate at 79%, inquiries roughly unchanged at 91, jobs completed up to 89, revenue billed at $61,700 and receivables over 30 days down to $11,400. No additional advertising, no additional technician, and roughly $9,300 a week of additional revenue from work that had already been calling.

Who owns which number

Assigning ownership is the step that converts a report into management. The pattern that works in a small service company: whoever answers the phone owns inquiries and booking rate; whoever estimates owns quotes issued and close rate; whoever schedules owns booked hours for next week; whoever runs the field owns jobs completed and average ticket; whoever invoices owns cash collected and receivables.

In a very small company one person may own five of the eight, and that is fine — the ownership still matters, because it changes the question from "why is revenue down" to "what happened to booking rate this week", which is a question with an answer.

One caution: ownership is not blame. A booking rate that falls because a competitor cut prices is not the receptionist's failure. The moment the meeting becomes a place where people are criticized for their numbers, the numbers start being adjusted before the meeting, and the whole system is worse than useless.

Where the numbers come from without buying software

The most common reason a scorecard never gets built is the belief that it requires a system the company does not have. It does not. Every one of the eight numbers can be captured with tools already in the business, and starting on paper is better than waiting for software.

• Inquiries. A tally sheet by the phone with two columns, new and existing. Ugly, accurate and free. If calls come through a tracking number or the phone system has a log, use that instead — but the tally sheet works and starts today.
• Booking rate. The same sheet with a third column: booked, yes or no. The value of this number comes from the noes, and the noes are the ones nobody writes down.
• Quotes and close rate. A row per quote in a spreadsheet with date, customer, amount and status. Close rate is calculated against quotes at least two weeks old, so the sheet needs the date more than anything else.
• Jobs, revenue and average ticket. Already in the invoicing system, whatever it is. Average ticket is revenue divided by job count — no tool required.
• Booked hours for next week. Counted off the calendar every Thursday, which takes about five minutes and is the highest-value five minutes of the week.
• Cash and receivables. The aging report from whatever accounting the company uses, or a list of unpaid invoices sorted by date.

Field service software makes this easier and eventually worth buying, but the sequence matters: companies that adopt software before knowing which numbers they manage by end up with a system full of reports nobody reads. Run the page manually for a quarter, find out which numbers actually change behavior in your company, and then buy the tool that produces those.

Five mistakes with scorecards

• Measuring only lagging indicators. It turns the meeting into a post-mortem instead of a steering wheel.
• Too many numbers. A page nobody finishes reading is a page nobody reads.
• Setting targets before measuring. Invented targets are ignored; targets built from four weeks of real data are believed.
• Solving problems inside the meeting. One long tangent kills the weekly rhythm permanently.
• Using the numbers to assign blame. The data becomes unreliable the moment reporting it is dangerous.

Getting started this week

Pick the eight numbers, decide who owns each one, and put a thirty-minute meeting on the calendar at the same time every week. Spend four weeks measuring without reacting. Then set targets from what you actually saw, and hold the meeting even in the weeks when you are too busy for it — especially in those weeks. Within a quarter the page will have found something that was costing real money and hiding in plain sight, which is what happened to every company that has ever built one.

Frequently asked questions

Which KPIs should a small service business track weekly?

Eight, covering the whole chain from inquiry to cash. Calls and form submissions received, counted rather than estimated and split between new and existing customers. Booking rate — how many of those inquiries became a scheduled job — which is the most diagnostic number in a service business and one almost nobody tracks. Quotes issued and quote value, both count and dollars. Quote close rate, measured on quotes issued at least two weeks ago. Jobs completed and revenue billed. Average ticket, which moves slowly and reveals a lot, since a falling ticket with rising job count means working harder for the same money. Booked hours for next week, the clearest forward view a service company has. And cash collected plus receivables over 30 days, because revenue billed is not money and that gap is where profitable-looking companies fail.

What is the difference between leading and lagging indicators?

A lagging indicator reports what happened — revenue, gross margin, jobs completed. A leading indicator predicts what is about to happen — calls received, quotes issued, jobs scheduled next week, technician hours booked. Almost every scorecard a small service business builds is entirely lagging, which turns it into a history lesson: revenue was down last month, and the causes were four to six weeks earlier in a week when calls dropped and nobody noticed because nobody counted calls. A useful page has both, with the leading numbers at the top. If calls, quotes and booked hours are healthy this week, revenue in three weeks is largely determined; if they are down, you have three weeks to react instead of finding out at the monthly close. The test for whether a number belongs: if it moved 20% this week, would you do something differently on Monday?

How should the weekly numbers meeting be run?

Same day and time every week, thirty minutes with a hard stop, the same eight numbers in the same order, each read aloud with the prior week and the target beside it. Whoever owns a number reports it — the person answering the phone reports calls and booking rate, the estimator reports quotes, the office reports cash and receivables — because a number with an owner gets watched all week while a number the owner reads alone gets watched on Fridays. Three rules keep it from decaying. Do not solve problems in the meeting: identify, assign and move on, since one long discussion turns a thirty-minute rhythm into a meeting people avoid. Do not add numbers casually, because the page grows by replacement and not accumulation. And never skip it in a busy week, since busy weeks are exactly when the leading indicators are about to turn.

How do you set targets for these numbers?

By measuring first and setting targets second. Spend four weeks simply recording the eight numbers without setting goals, without reacting and without changing anything. Four weeks of honest data show the actual range of the business, and targets built from that range are the only ones anyone believes — targets invented in week one get ignored by week three. It also matters that ownership is not blame: a booking rate that falls because a competitor cut prices is not the receptionist's failure. The moment the meeting becomes a place where people are criticized for their numbers, the numbers start being adjusted before the meeting and the whole system becomes worse than useless. The goal is to change the question from why is revenue down to what happened to booking rate this week, which is a question with an answer.

What kind of result does a weekly scorecard actually produce?

It surfaces problems that were never new, only invisible. A residential plumbing company with four technicians started with 94 inquiries a week, 61 booked for a 65% booking rate, $52,400 billed, a $672 average ticket and $28,600 sitting past thirty days. Two facts became visible immediately: 33 inquiries a week were arriving and not converting, roughly $22,000 of potential work at their average ticket, and past-due receivables exceeded half a week of revenue. They made two changes — unanswered calls routed to a second phone and returned within fifteen minutes, and a deposit required at scheduling on any job over $800. Twelve weeks later the booking rate was 79%, jobs completed had risen to 89, revenue billed to $61,700 and receivables over 30 days had fallen to $11,400, with no added advertising and no added technician.