Tell us what’s not working. We’ll tell you if we can fix it.
No proposal deck up front. Send the problem, we look at it properly, and if there’s a fit, we show you on your own material.
Four steps, and you can stop after any of them.
Tell us the problem
A few lines is enough. If you can, add a short Loom: two or three minutes of you doing the job and talking us through it in your own voice. Watching tells us more than a page of description, and nothing has to leave your machine as a file. If we need a file later, we’ll ask for it by email.
Discovery
We read what you sent and tell you straight whether it’s a fit. If it is, we get on a short video call — twenty minutes, camera on, no deck. We walk through the actual workflow and the actual data, and you get to work out whether you want to deal with us before any money or any files change hands.
We build it
If there’s a fit: a working proof, built on your real material. This can take the shape of a focused working session, a workflow design, a full build, or a team enablement session, whichever the problem calls for.
You decide
See it done, then choose: build it properly, licence the proof as it stands, or walk away. If we build, you own the result: documentation, a clean handover, and a walkthrough so you can iterate it yourself without needing us for every tweak. An optional support retainer is available if you’d rather we keep maintaining it.
Often it’s one person who is the whole business.
A good part of our work is with sole practitioners and small partnerships — lawyers, accountants and auditors, engineers, architects, plumbers and electricians. The people who do the billable work and then do the admin after hours because there is nobody else to hand it to.
The quoting. The scheduling. The job sheets. The invoices nobody chased. The compliance pack. The report that eats an evening. It is the same work we take off a company’s desk, at a different size, and it is usually worth more per hour to the person doing it alone.
That work tends to sit in files you cannot hand to a stranger: client matters, tender pricing, someone’s tax return, a patient list, drawings under NDA. So we do not ask you to hand them over. Where the job allows it, we build the tool to run on your machine or inside your own network, against your files where they already are. Nothing is uploaded, nothing is copied to a server of ours, and nothing you own is used to train anything. You can pull the plug and the tool still works, because it was never ours to switch off.
Some jobs need an outside model to do the heavy lifting, and local-only will not do them. When that is the case we say so upfront, tell you exactly what would have to leave the building and where it would go, and you decide before a single file moves. That conversation happens before the work, not after.
Six things that don’t change, whatever the job is.
Single-purpose tools
Small tools and dashboards that do one job well, not a platform your IT team inherits.
Human judgement on the AI output
AI does the heavy lifting, then a person applies human judgement to what it produced — checking the accuracy and the nuance a model flattens. Someone owns that call.
Security shaped to your data
Where it matters, nothing leaves your network — open-source models run on your own infrastructure. Otherwise we work on masked or redacted copies. Agreed before any real data moves.
Analysis, not regulated advice
Forensic, contract and financial work supports you and your advisors. It isn’t legal, financial or tax advice.
Software as an asset
You own what we build, outright, and we teach you to change it so it grows with the business. Not a licence you rent forever.
It isn’t done until it’s adopted
A tool nobody uses is a failed job. So enablement is part of the build: we hand over to people who have used it on their own work and know how to change it.