We have tools. Are they doing anything?
A number agreed before the work starts is worth ten opinions after it. We define the measure with you (cycle time, error rate, revenue per enquiry, cost per output), instrument it in your systems, and report it honestly, including when the answer is that a tool should be switched off.
Set up A$2,200 fixed for up to three measures; reported monthly as part of managed operations, or quarterly on its own from A$600.
A measurement plan, the instrumentation, and a monthly page you can put in front of a board or a bank.
Never headcount. Freed hours are a fact we record, not a saving we claim.
What it is
Most AI tools in small businesses are judged by whether people like them. That is how a tool that costs more than it returns survives for two years. A measure agreed before the work, taken from your own systems, ends the argument either way.
We choose measures that a CFO would accept and a team cannot game: time from enquiry to quote, error rate on invoices, cost per published article, revenue per enquiry. We instrument them where the data already lives, and we put the number on one page every month with the honest note underneath.
This is for you if
- You have bought tools and cannot say what they changed
- You need a page for a board, a bank or a partner meeting
- You want the pilot judged on a number, not a demonstration
Not for you if
- You want a dashboard with forty charts
- The measure you care about is hours saved and nothing else
- You do not have access to the systems the numbers live in
How it runs
- 1 · week 1
Define
One to three measures, each with a baseline, a source system and an owner. Written down.
- 2 · week 1 to 2
Instrument
Pulled from the systems the numbers already live in. No new data entry.
- 3 · monthly
Report
One page: the number, the trend, the honest note. Sent, not dashboarded.
- 4 · quarterly
Decide
Keep, adjust or switch off, on the evidence.
In writing, before we start
Three sentences that hold on every engagement. They are the method, written as promises.
The measure, the budget cap and the point at which we stop are set in the written scope before anything is billed. Nothing moves the goalposts afterwards.
Everything we build runs in your accounts and is yours: code, configuration, documentation and measurements. We hand over; there is no dependency on us.
If the pilot does not hit the measure we agreed first, we keep working at no further cost until it does, or we stop and say so in writing. You will not be sold the next step by the first one.
What you receive
Questions
Can you measure something we already have running?
Yes. A baseline can be taken from history where the system holds it, and from the next month where it does not.
What if the number says the tool is not working?
Then the page says so and recommends switching it off or changing it. That is the point of the service.
Is this analytics?
It is smaller and more useful. Analytics shows everything; measurement shows the three numbers the decision depends on.
What would prove it worked?
Tell us the tool or the pilot and we will propose the measure, its baseline and its source in three business days.