The dashboard that runs the business without you

A small business dashboard is one page of ten indicators at most that the team updates every week and discusses without you. Every number has an owner and an alert threshold. Done well, it replaces the habit of checking everything yourself: you see the company's health in five minutes, and the team knows what to do when a number slips.

Why a dashboard makes the business independent

In many small businesses, the dashboard is the owner. He knows whether the month is going well because he sees the orders come in, signs the cheques and talks to the clients. Nobody else has that overall view. When he goes on vacation, the company is flying blind.

A real dashboard changes that in two ways. First, it makes information visible to the team, who can act without waiting for you to read it. Second, it lets you lead from a distance: you look at the numbers, you ask questions, you no longer need to be everywhere. It's the last piece of step 4 of our path, the one that confirms the systems you've built hold up.

For a buyer, it's proof too. A company that has tracked its numbers weekly for years is run with method. That's reassuring, and it makes due diligence easier.

Which indicators to choose

There's no perfect list. But most small businesses find their indicators in five families.

Money

• Cash on hand and a forecast a few weeks out.
• Overdue receivables, by age.
• Gross margin for the month, against budget.

Sales

• Quotes sent and win rate.
• Order backlog: how many weeks of work are already sold.

Operations

• On-time deliveries.
• Returns, rework or quality complaints.

People

• Overtime and absences: early signs of wear.

Clients

• Share of sales from the largest clients, to track concentration.

Pick ten at most. The right test: if this number changed sharply, would someone have to do something this week? If not, it doesn't belong on the page.

Three rules that make it work without you

1. One owner per indicator. The controller supplies cash, the sales manager the backlog, the production manager deliveries. Each knows their number and explains it. If you compile everything, you stay the owner bottleneck.

2. An alert threshold and a planned action. For each indicator, write down what's normal, what's worrying, and what happens then. Example: if overdue receivables pass a set amount, the controller calls the three biggest late payers that week. The team doesn't need your permission to react.

3. A short meeting, every week, at the same time. Thirty minutes, standing if possible. Go through the numbers, note the actions, get back to work. One day, someone else runs the meeting. Then you're no longer in it.

Eight numbers, Monday morning, in Joliette

Set the example in Joliette, at an excavation and landscaping company that doesn't exist: $8 million in sales, 40 employees in season, an owner aged 59. He "feels" the business: he visits the job sites, talks to clients, checks the bank balance every morning. Nobody else knows whether the season is going well until year-end.

He sets up a spreadsheet with eight indicators: cash, overdue receivables, quotes sent, win rate, backlog in weeks, jobs finished on time, overtime and equipment breakdowns. Each has an owner. On Monday mornings, the meeting lasts thirty minutes.

For the first few weeks, numbers come in late and some are rough. He doesn't fix them himself: he asks the person responsible for each number to fix their source. A few months later, the controller runs the meeting. The owner reads the dashboard Monday at noon, even on vacation, and sends two or three questions by email. Later, some of the numbers are pulled automatically from the accounting system. This example is made up; the approach applies to most small businesses.

Set it up in a month

Week 1: choose. List every number you look at today, even in your head. Keep about ten using the "someone has to act this week" test.

Week 2: assign. Give each indicator to one person. Write down its exact definition, its source and its alert threshold. One line per indicator, for example: "Receivables over 60 days | controller | alert above the set amount | action: call the three biggest late payers that week". See how to document business processes simply.

Week 3: test. Hold a first meeting. The numbers will be imperfect; that's normal. Note what's missing.

Week 4: stabilize. Set the day and time of the meeting and the spreadsheet format. Then change nothing for three months.

Only then think about automating the data collection. The methods in small business automation apply: you automate what's stable.

What a dashboard doesn't replace

A dashboard shows you where to look; it doesn't always tell you why. When a number slips, someone still has to go to the shop floor, talk to the client or to the team. It doesn't replace your accountant's monthly financial statements or the annual budget either. It complements them, on a weekly rhythm.

And it doesn't replace judgment. One weak week isn't a crisis, and one good week doesn't fix a deeper problem. What matters is the trend over several months, and the team's ability to react without waiting for your signal. That's also what a buyer will want to confirm: that good decisions get made even when you're not in the room.

What kills a dashboard

Too many indicators. Thirty numbers is a report, not a dashboard.

Numbers without action. An indicator nobody uses to decide eventually stops being updated.

The owner compiling everything. The most common trap.

Changing the format every month. You lose the history, which is exactly what a buyer wants to see.

Do it with a pro

Alone, choosing the right indicators and keeping them alive week after week takes discipline that's hard to sustain while running the business. Our regional partner builds the dashboard with your team, connects the sources on site and helps you run the first meetings. See how it works.

How it works