Custom AI solutions
Software that does the boring part
I do not sell "AI strategy". I build concrete tools that do automated work in your business - and I start delivering in weeks, not years.
What can actually be fixed
These jobs repeat every day and cost time every single time. They can be automated.
Customer enquiries
The system answers the repetitive questions and collects what the job needs: the property, the address, the time. Only the enquiries that cannot be answered automatically reach you.
Invoice and document data
Supplier, amount, VAT and due date are read off the invoice or the delivery note and written into a spreadsheet or your accounting system. Nothing is retyped by hand and nothing is lost in the paperwork.
Preparing quotes
A few fields produce a quote with the right price and the right deadline. All that is left for you is to check it and send it — no digging through old files and correcting dates by hand.
Internal document search
Contracts, estimates and manuals become one list where the answer is found immediately, rather than by asking "where is that file?".
How it works
Four steps, and at each one you know what happens next. You can stop at any of them.
A conversation
Half an hour about how the job is done today: who does it, how long it takes, and what happens when it is not done on time.
I map what repeats
I go through one real case — one enquiry, one invoice, one quote — and lay out the steps that repeat every time. That shows what is worth automating and what is not.
A first version, fixed scope
You get it in writing: exactly what I will build, how long it takes and what it costs. The first version finishes one job end to end rather than doing half of everything.
I ship it and we iterate
I put the system to work, show you how to use it and leave the documentation. After that we change what does not work the way we assumed it would.
An example: from the enquiry to the settlement
A system I built and put live for a locksmith business in the United Kingdom. The office and the locksmiths both use it every day.
The company allocated work by text message and worked out its weekly settlements by hand. I built one system that covers the whole path: the enquiry, the job, the locksmith's report from site, the invoice, the card payment and the weekly settlement. It is a Next.js 16 application, the data sits in a SQLite database on the same server, and a payment records itself once the bank confirms the money has arrived.
The report works on a phone
The locksmith opens a link on his phone and submits the report in one tap — no app store, no password to remember. The report is on the office screen straight away.
Payments and invoices without the typing
When the bank confirms the payment it is recorded by itself, and the invoice is raised from the same figures. A repeat notification of the same payment does not double the money.
A week that adds up
VAT, the locksmith's share and the parts he bought add up into one week's figure, rather than a separate spreadsheet somebody fills in on a Friday. The figures agree with the money that moved.
I do not publish the client name or their data here. If you would like a reference, I will ask their permission.
Common questions
What happens to our data?
The data stays where it already is: in the inbox, in the accounting system, on your server. The system reads it and writes back to it. If part of the work has to be done by an outside model, I say so in advance and name exactly what is sent; where that is not acceptable, I build it so the data never leaves your network.
Do we own the code?
Yes. You get the code and the documentation; it does not stay with me and it is not rented. If you want it, I hand over the repository too, so another developer can carry on without me.
Can it run on our own machines?
It can. That needs one computer or server that is always on. If you do not have one, I will tell you what is required and what it means for the working day. A hosted version is possible as well — we decide it by where your data already is.
What if our tools have no API?
Then the simplest route is closed. There are three options: import a file, automate what a person does in the browser, or keep one step manual. Screen automation works, but it breaks whenever the other side updates their software, so I say that in advance rather than after.
Who maintains it afterwards?
The system is handed over to you with the documentation. If you want, I stay on to maintain and change it under a separate agreement; if not, I hand over the code and explain what to do when something fails. There is no condition that nothing can be changed without me.
Got a job that repeats every day?
Tell me how it is done at the moment. I will tell you whether it is worth automating and what that would involve — you get the exact scope and the price in writing.