You find out how the month went three weeks after it ended.
The numbers exist. They are in Xero, in the job system, in a spreadsheet someone updates on Fridays. We bring them into one plain view that is right every morning, so decisions stop waiting for the report.
Three ways late numbers cost you.
Someone exports from Xero, someone else pulls the job numbers, and the two get married in a spreadsheet. By the time it lands, the month it describes is three weeks gone and nothing in it can be changed.
Both were right the day they were built. Then one got a new column and the other didn’t. Now every number has to be argued about before it can be used, and the argument takes longer than the decision.
Your instinct is usually right, and it is what has kept the business going. Relying on it is also why a job type that loses money can run for six months before anyone spots it.
Put your own numbers in.
Five hours a week of building reports, at what a manager’s hour actually costs, is a bit over $21,000 a year. What it buys you is numbers that were already old when they arrived. The decision you put off for three weeks because the report wasn’t ready cost more than the report did.
$475 a week. Time a system could give back.
Listen. Build. Measure.
We spend a day with your team working out which numbers actually change what you do, and where each one lives today. You get a short written plan naming those numbers and a date by which you’ll see them. Most dashboards fail because they show 40 things nobody acts on.
We connect the sources, write down what each number means, and build one view that fits on a screen. You see a draft in the first week, so the argument about definitions happens early instead of after launch.
We check the hours against the promise, in your numbers, not ours. If it paid for itself, we talk about the next one. If it didn’t, we fix it.
Before you book a call.
Do we need a data warehouse?
Most businesses your size don’t. If your numbers live in Xero and two or three other systems, we build straight off them and keep the running cost close to nothing. We’ll tell you the day that stops being true, which is usually somewhere past a few million rows.
Which tools do you use for dashboards?
Usually Metabase, or Power BI if your team already lives in Microsoft, though that one needs its own licence on top of Microsoft 365. A dashboard nobody opens is not worth a licence fee, so we pick the one your team will actually look at rather than the one that demos best.
What if our data is messy?
It is. Everyone’s is, and we have never opened a customer list that didn’t have three spellings of the same name. We clean what matters for the numbers you asked for and leave the rest alone, because a full data cleanup is a project of its own and rarely pays for itself.
Who maintains it?
You can, and we build it so that is possible: definitions written down, sources named, nothing hidden in a formula only we understand. If you would rather we looked after it, that is a small monthly arrangement. What we won’t do is build something that quietly needs us forever.
Can the numbers be wrong?
Yes, and at the start some of them will be. Every view we build gets checked against a report you already trust before anyone relies on it, and each number says where it came from and when it last updated. If a source stops feeding, the screen says so instead of showing yesterday’s figure as though it were today’s.
Tell us what you can’t see.
A sentence or two is plenty. We read every message ourselves and call you back within one business day.