Building an owner's KPI dashboard you can actually trust

Step 1: choose 8 to 12 numbers that drive decisions

Pick numbers that would change what you do this week if they moved. A KPI that never triggers a decision is decoration.

A practical starter set for a service business:

1. Revenue invoiced (month to date and versus the same month last year)
2. Gross margin %
3. New enquiries
4. Quote-to-win rate
5. Average job or order value
6. Backlog (signed work not yet delivered)
7. Accounts receivable over 60 days
8. Cash on hand
9. Jobs completed on time %
10. Customer callbacks or rework rate

Balance the list between leading and lagging measures. Revenue, margin and receivables tell you what already happened; enquiries, quote-to-win and backlog warn you about the next two or three months. A dashboard made only of lagging numbers tells you about a slow quarter after it is too late to respond, while one made only of leading numbers can look busy while cash runs short.

For each candidate KPI, ask what you would actually do if it moved 10% in the wrong direction. If the honest answer is "nothing", leave it off the owner's view.

That is ten. Most owners don't need more at the top level. If marketing performance needs its own detail, keep it in a separate view underneath.

Step 2: write a definition for every KPI

Every KPI needs a short written definition that answers five questions: what is counted, what is excluded, which system it comes from, when it is measured and who owns it. This prevents the most common dashboard argument, which is two people with two different numbers for "revenue".

Notice the small but important choices: "before GST/HST", "by invoice date", "60-day window". Each one removes a future disagreement. Write the rest of your list the same way before building anything.

Step 3: the worked mismatch, and how to reconcile it

The most common surprise is a dashboard revenue figure well above the accounting figure. Here is a worked example for October.

• The CRM dashboard shows $412,000 in "closed-won" deals for October.
• The accounting system shows $368,000 of revenue invoiced in October.
• The gap is $44,000, about 11%, and the owner wants to know which number is right.

Both are right; they measure different things. Reconciling them line by line:

Check it: $412,000 − $38,000 = $374,000, then − $6,000 = $368,000.

Two fixes follow. First, the dashboard's revenue tile should come from accounting, using the written definition above, and the CRM figure should be renamed "sales won" so it isn't confused with revenue. Second, the sales team needs a rule for cancelled deals so they are moved out of "won" promptly.

A third cause appears often enough to check every time: if your CRM deal amounts include GST/HST and your accounting revenue does not, a business charging 13% HST in Ontario would see the CRM run about 13% higher for that reason alone. Your accountant should confirm how revenue and tax are recorded in your books.

Step 4: set the refresh cadence and the review rhythm

Refresh each number as often as you would act on it, and review on a fixed schedule. A dashboard that is updated irregularly stops being trusted.

• Daily: cash, enquiries and revenue month to date, if the feeds are automatic.
• Weekly: pipeline, backlog, quote-to-win, AR over 60 days, on-time completion. Review in a 30-minute leadership meeting.
• Monthly: gross margin, callbacks, and the revenue reconciliation, after the books are closed.

Show the "last updated" time on the dashboard itself. If a feed fails, people should see that the number is stale rather than act on old data.

Step 5: keep the data clean at the source

Most dashboard problems start with how data is entered, not with the dashboard. A few rules at the source fix a lot.

• Required fields in the CRM for deal value, close date and status.
• One customer, one record. Merge duplicates monthly.
• Consistent job or product codes across quoting and accounting.
• A named owner for each system who checks a short exception report each week.

If your systems don't share data at all yet, the connection project may need to come first; our guide on prioritising digital projects shows how to sequence that.

Step 6: a four-week build plan

Most owner dashboards can be specified and running within about four weeks if the source systems are in reasonable shape.

1. Week 1: agree the KPI list and write the definitions in a shared document. Owner signs off.
2. Week 2: map each KPI to a source field and test a manual calculation for last month.
3. Week 3: build the dashboard in the chosen tool and run the first revenue reconciliation.
4. Week 4: hold the first weekly review using the dashboard, then fix what confused people.

Keep a short change log. When someone changes a definition, record the date and reason, because next year's comparison depends on it.

Common dashboard mistakes

These are the patterns that make owners stop opening the dashboard.

• Building charts before definitions. The first argument about a number ends trust in all of them.
• Too many tiles. Forty numbers means no one knows which three matter.
• Mixing sources for one KPI. Revenue from the CRM one month and accounting the next is worse than either.
• No reconciliation. Without a monthly check against the books, small errors grow quietly.
• No owner. Feeds break, fields change, and nobody notices.

How we help

Our data and reporting service writes the KPI definitions with your team, maps each one to a source system, sets up the reconciliation and specifies the dashboard, whether in your existing tools or a dedicated one you buy directly. If the numbers depend on new connections between systems, implementation oversight keeps that work on track. Our results page shows what measured reporting looked like in our HVAC work. Text (604) 632-4959 with the one number you trust least, and we will start there.