Approach
Put AI at the centre by starting with what's in the way.
Most companies are sold AI as a strategy — decided at the top, arriving as a platform. It demos well and dies in two quarters, because the work it was meant to automate was never written down, and the systems holding that work were never fixed.
We go the other way. Replace what's in the way. Get every record into one shape. Put it in one place. Then the AI core is worth building, and it earns its place from the first week.
01The ladder
Four rungs. In order.
Each one is only possible because the one below it is done. That's the whole claim.
01
Replace what's holding you back
Most companies don't have an AI problem. They have a system from 2011 that everything depends on and nobody wants to open.
So this is first, and it's rarely as bad as it looks. The first week is spent finding out what's actually true — which usually shrinks the job rather than growing it.
Four Innova apps became one. The merge was a weekend, because we counted first.
02
One shape
Companies don't have a data problem. They have five front doors. A request by phone is handled one way, the same request by email another. Nobody is doing it wrong — there was never one right way.
Pick the shape the work should take. Make every channel a translator into it. Unglamorous, and the whole foundation: you can't measure what you can't count.
Five Innova intake channels now produce one identical service request.
03
One source
The data isn't missing. It's in a CRM, a job tool, an inbox, and a spreadsheet someone keeps out of self-defence. No two agree.
One database is the hub. Everything feeds it. Corrections a person makes are locked field by field. When the hub disagrees with upstream, it records the conflict and changes nothing — software that picks a winner for you is software you stop trusting the first time it picks wrong.
One Innova contact holds our phone number and their email at once, on purpose.
04
The core, at the centre
Which vendors actually reply. What a warranty call really costs from first contact to closed. What we quoted this client eighteen months ago and everything said since.
Getting here means the rungs below were done properly. Skipping to it is what most AI pilots do, and it's why they demo well and die in a quarter.
Five years of Innova's mailbox, ingested and attached to the jobs it belongs to.
02How we build
Six things true of everything we ship.
These are the actual product. The code is downstream of them.
Count before you cut
The first week is spent finding out what's true. Twice that has changed the plan — once because the obvious next step would have broken a live system real people were using.
Dangerous things ship switched off
Anything with a blast radius — a mass email, a push to your system of record, a delete — is built visible and inert. Every action recorded, every output rendered for review, nothing leaving until a flag is deliberately flipped.
The database enforces it
A greyed-out button is a suggestion. Rules that matter go where they can't be routed around.
Copy is not code
Text, prices and opening hours live in one place and are edited by you. If changing a sentence needs us, it never gets changed.
Say what happened
When a form fails to send it shows the phone number, not a success message. Software that hides its failures is how a business hears about them from a customer.
Write down why
Every project comes with the reasoning, not just the code — what was considered, what was rejected, what breaks if you change it. The difference between owning software and hosting it.
03Working together
Three ways in.
Most start with the first and end at the third. Not a funnel — just what happens once something ships and gets used.
The first week
Fixed fee, one week
We read what you have — the code, the accounts, the way a job actually moves through the office — and hand back what's true, what's about to break, and the two or three changes worth making first.
Best when: You know something's wrong. The shape of it keeps moving.
A build
Fixed scope, quoted up front
One thing, defined, shipped to your real domain and used by real people. You get the repository, the deployment, and a written record of every decision and why it went that way.
Best when: You already know what needs building.
Ongoing
Monthly, capped hours
What most of this settles into. Something ships, gets used, and reveals the next thing. Steady progress against a list you reorder any month.
Best when: Software is now part of how the business runs.
The first week is the one
that changes the plan.
Every engagement so far has turned up something nobody knew was there. Twice it changed what got built.