Two weeks. One straight answer about your systems
What's working, what's quietly costing you, and whether AI would do anything for you at all.
You already know something's off. You just can't point at it
Nobody rings us because their systems are perfect.
They ring because a job slipped and nobody's sure where. Because the same number is in three places and two of them are wrong. Because the quote went out late and the only person who'd know why is on annual leave.
Most of the time it isn't one big broken thing. It's forty small ones, and they've been there so long they just look like the job now.
That's the bit an audit is for. Not to tell you it's bad. To tell you exactly where it is.
Most AI doesn't fail because the AI is bad
By now someone's sold you something with AI in the name. Maybe it stuck. Usually it didn't.
That's rarely the AI's fault. Point it at data that lives in four places, half a spreadsheet and one person's memory, and it'll do exactly what you'd expect. It'll give you wrong answers, faster.
There's no shortage of people who'll wire thirty automations into your business by Friday. Whether any of them should exist is a different question, and not one they're paid to ask.
So we ask it first. Part of the audit is a straight answer on which of your data an AI could actually do something useful with, and which of it needs sorting out before anyone points a model at it.
That's what we're here to figure out.
What we actually look at
Two weeks, inside the business, with the people who do the work.
Where the work moves, and where it stops.
Every job has a point where it sits waiting. Usually nobody's tracking it because nobody's job it is.
What's being retyped.
The same information, keyed into a second screen by a person. We count it. It's always more than anyone expects.
What only lives in someone's head.
Every business has one. The person who knows why that client gets different pricing. What happens when they're off.
What your data could actually support.
Which records are structured enough for something to read and act on. Which are just notes fields with a decade of context buried in them.
What you're paying for and nobody opens.
The tool bought in 2022 to fix a problem that went away in 2023.
Where the follow-up drops.
The enquiries, the invoices, the approvals. The ones that don't get chased because chasing is somebody's fifth priority.
What lands on your desk
A written map of how work actually moves through your business. Not the org chart version. The real one.
A list of what's leaking, and what each leak costs you in hours or money.
A straight answer on your data: what an AI could usefully touch today, what it couldn't, and what would need to change first.
A build recommendation. What's worth building, in what order, and roughly what it costs.
And the parts we'd tell you not to build.
The price
$2,500. Two weeks. Fixed scope, fixed fee.
If you go on to build with us, it comes off the first invoice.
If you don't, the report is still yours.
Sometimes the answer is that you're fine
Not every business needs a custom system. Some of them need one process changed and a tool they already own set up properly.
If that's you, we'll say so, and the audit will say so in writing.
It's the less profitable thing to say. Which is roughly how you know we mean it.
No obligation attached
The audit isn't a sales call with a price tag on it.
The report is yours. Take it to another developer, hand it to your in-house team, or sit on it for six months. That's fine, and it happens.
We'd rather you had the map and used someone else than didn't have the map at all.
What it usually turns up
A food manufacturer thought their purchase order process was slow. It was. The slow part turned out to be one duplicate check that nobody had told the team about, so they were doing it twice by hand.
A childcare operation was chasing each other for updates in a group chat. They didn't need AI. They needed one board that everybody could see.
A property business had four systems and a spreadsheet. Three of the systems were fine. The spreadsheet was doing the work of a database and nobody had noticed.
None of these were the problem anyone rang us about.
Don't book this if:
- You're pre-revenue. Go and get customers. Come back later.
- You're three people and one tool, and it's holding up fine.
- Nothing's actually broken and you're just curious. Keep your $2,500.
Come back when the spreadsheet has tabs nobody understands.
Let’s build yours
Start with a call, not a brief. No salesperson, no discovery deck — you talk to the person who writes the code.
If we’re not the right fit, we’ll say so. That’s cheaper for both of us.