Hand pointing a pen at printed bar and line charts on a desk

Five Numbers That Show the Business Can Run Without You

December 14, 2024•7 min read

Pings per day, escalations per week, owner-touch rate on active jobs, days away without a revenue dip, and exception resolution time. Each one counts a way the business still leans on you, so falling numbers mean the team is carrying more of it. Measure all five against your own starting point, recorded before you change anything.

The operating meeting started without him on a Thursday. Ten minutes on the scoreboard, then the rest of the agenda. Pings per day: 11. Escalations that week: 7. Owner-touch rate on active jobs: 34 percent. Days away since the last revenue dip test: 0. Exception resolution time: 2.4 days average. Four yellows and a red. Nobody called him. The lead changed one rule on exception routing and put a green target next to each line for week twelve.

Feelings about whether the business can run without you are unreliable. Owners feel fine after a quiet Friday and call it freedom. They feel useful after a chaotic Monday and call it leadership. The five numbers cut through both stories.

Which numbers show your business can run without you?

Pings per day. How often people reach out to you for something that is not a true emergency. Baseline what you have. This firm's baseline was 11 a day and the twelve-week target was 3. Count Slack, text, and "got a second" the same. If you only count email you will flatter yourself. Carry a tally for three ordinary days before you set a baseline.

One owner insisted his baseline was "maybe four." Three days of tallies landed at 14, 11, and 9. The fourth day he stopped counting before noon because he was embarrassed. We used 11 as the baseline anyway, since stopping early told us the number was high enough to threaten his story.

How you count matters as much as what you count. He used a simple notes file with five lines and a daily total, updated at 5 p.m. When the file felt embarrassing he wanted a prettier tool. We kept the ugly file, because the habit of writing the number down before you go home was doing the work.

Escalations per week. Issues that truly need owner judgment. Target under 3 once the seats are clear. If escalations are high and pings are low, people are batching fear into one weekly dump. If both are high, you still own the decisions and the interruptions. Write down what counts as an escalation before week one ends, or else every hard conversation becomes one and the number means nothing.

Owner-touch rate. Share of active work that requires your hands or approval before it can move. A firm can look calm in your inbox and still need you on 40 percent of jobs. Drive it down by moving decision rights, not by asking people to bother you less while you keep every approval. A different owner cut pings by being short with people and wondered why owner-touch stayed at 38 percent. They had learned not to ask. They had not learned to finish.

Days away without a revenue dip. Not a vacation fantasy. A measured absence. Seven days with flat or rising revenue is a stronger signal than a year of "I could step away if I wanted." Start with a Friday. Then two days. Then a week you actually leave the laptop closed. Calling in "just to check" voids the test. If you void three tests in a row, the number you should track is how often you break your own experiment.

For what tends to give way first during those absences, see what breaks first when the owner steps away.

Exception resolution time. How long from "this broke the normal path" to "closed with a recorded decision." Slow exceptions are how quality drifts while everyone feels busy. Track the median, not the one horror story. A single three-week nightmare will skew an average and let you ignore the dozen exceptions that quietly took four days each.

How do you review the five numbers each week?

Ten minutes. Same five lines (if you want a sixth, replace one). Baseline, twelve-week target, red / yellow / green from your own thresholds. Review it inside the operating meeting without you in the chair. If the meeting cannot run the scoreboard without you, the scoreboard is still theater.

If the meeting that carries the board still needs you in the chair, start with building a weekly operating meeting that runs without you.

How can the scoreboard mislead you?

Do not turn the five numbers into a compliance chart for staff. These measure owner dependence, and people who feel watched for how often they messaged you will start hiding pings. Week six looked beautiful at this firm, with pings down to 3, until they found the lead had opened a shadow channel for quick questions to the lead instead of the owner.

The pings had moved, not disappeared. They killed the channel, pings jumped back to 8 for ten days, and the lead got decision rights in writing for the ten question types that had filled it. Pretty weeks are suspects.

Another lie: counting only weekday pings while he answered a dozen texts every Sunday night "so Monday would be clean." Sunday texts are pings. Put them on the board.

Under about four staff this dashboard is usually noise. You are still in too many seats for the numbers to mean independence. Build seats first. And if you are in a live cash crunch, fix cash before you optimize ping counts. Come back to dependence when the account is not on fire.

Thursday, week twelve

He read the screenshot of the scoreboard on his phone from a parking lot two towns over, eating a gas station sandwich in the driver's seat because he had left the lead's birthday lunch early. The lead had ordered a cake with the firm's logo on it, which he privately thought was cringe, and he had stood there clapping and checking the time. Pings: 3. Escalations: 4. Owner-touch: 19 percent. Days away: 7, marked that morning. Exception time: 1.4 days. Four greens and a yellow on escalations.

Revenue for the week was $1,800 above the prior average, which proved nothing by itself and still felt better than a dip. He did not drive back to "just check." He sat with the yellow and wondered whether 4 escalations was the floor for his kind of work, or whether he still had one approval habit left to kill. He still does not know.

He keeps a note under the scoreboard photo: "yellow is information." The first month he treated every yellow like a personal failure and overcorrected by jumping back into seats. Pings fell, owner-touch rose, and the board told on him. Now a yellow triggers one experiment for seven days, written down, owned by the lead. If the yellow remains, they change the experiment, not the story about how committed he is.

Frequently asked questions

Who should keep the scoreboard?

The lead who runs the operating meeting. They gather the counts, bring the board and propose the experiment when a line turns yellow. If you keep it yourself, the board measures your attention instead of the team's ownership, and you end up back in the seat it was meant to empty.

Do these numbers matter when selling a business?

They help. A buyer wants evidence that the business holds up without its owner, and a record of falling pings, lower owner-touch and measured days away is easier to trust than a claim. Keep the full history so the trend is there to show. Making a business sellable goes further.

How do I set red, yellow and green lines?

Start from your own baseline. Green is a level you have already reached in a good stretch, red is your worst ordinary week, and yellow sits between them. Move the lines once green becomes normal, so the board keeps pointing at the next habit to change.

What would your own board say today?

If you want help building the five-number scoreboard and the twelve-week targets, start here: systemstoscalegroup.com/getstarted

Book a Free Call

Ezra Dewolfe

Ezra Dewolfe

Ezra Dewolfe is the founder of Systems to Scale Group, which helps established service business owners step out of the day-to-day and grow their profits with systems that scale. He's worked with owners of law firms, med spas, agencies, salons and architecture firms to find where the business depends on them and build systems their teams run without them.

Back to Blog