Your numbers, reconciled overnight and explained by 07:00.
Not a wall of charts you have to interpret. A short, written answer to the questions you already ask every Monday, with the working shown.
Short is the hard part. Behind three paragraphs sits every row reconciled against your own records, so what reaches you is the conclusion rather than the homework.
Vercel
Supabase
ClaudeA template shows you charts and leaves the thinking to you. This is built the other way round.
Template tools start with the data and hope a chart answers something. This starts with your questions, in your words, and builds backwards to the data that answers them.
"Who stopped buying?" becomes a row in your system, owned by you and editable by you. Add one and it is answered from the next morning.
If you call them jobs and not projects, and the busy season is "the run-up", the briefing says that. It reads like someone who works there wrote it.
Every figure links back to the rows it came from, so you can check it before you act on it. Each answer stores how it was calculated, so it can be checked and argued with.
Not "debtors up 12%". Ring these four accounts today, in this order, and here is why this one first.
What the first build actually found.
Numbers from a real reconciliation, kept anonymous at the client's request. Their existing reporting looked fine. Checking it line by line against the source records is where all of this came from.
Open the live demo ↗ Sample company · real engine · click anything
How it gets built.
Roughly four weeks from first call to the first briefing landing in your inbox, most of which is me working rather than you.
Written down properly: the questions you need answered every Monday, your words for things, your anchor clients and seasons, and where you suspect money is escaping.
Read-only connections to the systems you already use. Nothing re-typed, nothing moved, nothing you have to change about how you work.
The unglamorous week. Figures matched to source records until they tie. This is where the findings appear, and it is the part most reporting tools quietly skip.
The dashboard goes live and you get a written document showing what was wrong and what it was worth. The findings usually cover the fee.
Four things exist at the end. All four are yours.
Not features. These are the actual objects a build leaves behind, sorted by how you come across them, because a thing you open and a thing that arrives are not the same kind of thing.
-
You open it
The dashboardIts own addressSigned in, nobody else can reach it
A private site, yours alone, showing the questions you set in discovery answered against last night's data. Not a template with your logo on it: the panels are the questions you actually asked.
-
You ask it
The advisorInside the dashboardAsk in plain English
A question box that answers in sentences, against your figures rather than general knowledge. It says what changed, what it thinks caused it, and what it would do, and it shows the rows it used so you can disagree with it.
-
You read it once
The findings documentA document you keepYours whatever happens next
Everything the reconciliation turned up on the way in, priced and referenced so it can be checked. This is the one that pays for the build, and it is written to be read by somebody who was not in the room.
-
It arrives
The Monday briefingEmail, 07:00Weekly, or whatever rhythm suits
The short version, in your inbox before you sit down. Three things, what they cost, and which ones need a call. There is a real one further down this page, reproduced exactly as it lands.
All four are handed over outright, in your own accounts, on infrastructure billed to you rather than to me. If you stop the retainer tomorrow, none of it switches off. The dashboard keeps running, the findings document is still yours, and the only thing that stops is me maintaining it.
Three things this morning.
Mercer has not ordered in 255 days. That is £1,157 a month against last year, and they have not been chased.
Call todayThe spring campaign paid. £2,434 out, £7,612 billed back to it. Worth running again before the season turns.
No actionTwo invoices tipped past 60 days overnight. Both Halden, £9,240 between them. Terms were agreed at 30.
Ring themThen it keeps going without you asking.
A dashboard built once starts dying immediately: prices change, a system gets swapped, a question stops mattering and a new one starts. The £250 a month is what stops that happening.
Every month the data refreshes, the questions recompute, the briefing gets written, and I read it before you do, so a wrong answer is caught by a human rather than by you. New questions get added as they occur to you, and small changes are included rather than quoted.
Cancel any time. You keep your data, your access and the findings. It is a retainer because the business keeps moving, not because the software needs babysitting.
First month included with the build
When I'll tell you it's the wrong thing to buy.
If the underlying records are inconsistent, a dashboard renders that inconsistency beautifully and confidently. The £300 audit comes first, at a fifth of the price.
If you have thirty customers and you know all their names, you do not need overnight reconciliation. You probably need two hours of admin taken off you instead.
Enough volume that patterns hide in it, and a question you work out by hand every week: who is slipping, what is actually profitable, who owes us. That is when this pays for itself.
The rungs below this one.
Most people should start here. It costs a fifth as much and tells us both whether the big build is worth doing.
How your systems get plugged in, what leaves your building and what does not.
Once the dashboard spots something, an automation can be the thing that acts on it.
Bring the question you re-answer every week.
Twenty minutes. I will tell you honestly whether a build is worth it, or whether £300 of audit gets you most of the way for now.
Book an intro call£1,500 fixed build · £250 a month · cancel any time