I build the tools that take repetitive work off your team
A small number of custom-built tools that take manual, repetitive work off your team and cut errors that come with it.
I write the code, and I have done the operational work myself.
You deal with the person who builds the tool, not a reseller fitting you to a platform.
Why?
I spent years in financial services. Watching skilled people do work a machine could do faster and more accurately, freeing up time for work that needs a human touch.
So I automated it.
I’ve seen first hand what a select number of well-built tools can do for a team under load, and that’s what I build for businesses now.
What I build?
I build a small number of well-made automation and AI tools that take manual, repetitive work off your team and cut the errors that come with it. The work is bespoke: fitted to the process you already run, not an off-the-shelf product you have to reshape your business around.
In practice, that usually means work like:
Data copied by hand between systems, moved across automatically and checked as it goes.
Reports rebuilt by hand every week or month, produced to the deadline without the manual assembly.
Figures reconciled across spreadsheets, so discrepancies surface earlier rather than later.
Approvals and sign-offs that stall in inboxes, routed and tracked so nothing sits waiting unseen.
I build a few tools properly rather than a sprawl of fragile ones, so what I deliver keeps working long after handover.
Where this comes from
My delivery record is primarily within financial services: investment-operations processes automated where the figures had to be right and the reporting deadline did not move. Manual, error-prone work, replaced with tools that ran accurately and to time.
My current work centres around process automation with the considered and careful implementation of AI: assessment and marking tools that remove hours of manual review, and conversational AI built for career coaching.
The pattern is not tied to one sector. The same manual, repetitive, error-prone tasks turn up in any business that runs on operations, whatever it makes or sells.
How the work runs
There are three ways to work with me:
Advise. A scoped review and a written plan you own outright: what to build, what it will take, and whether to build it at all.
Build. End-to-end delivery of the agreed tool, tested, documented and handed over.
Run. Ongoing operation of a live system: monitoring, fixes and changes as the business grows.
See Services for what each tier includes.
What to expect:
I start with the problem, not a product. Scope, systems touched and success criteria are agreed in writing before any build.
I test before anything touches live work. Edge cases get found in development, not in production.
Every build is handed over with documentation, so the tool does not depend on my memory.
I am one person. That means direct access to the person who builds it, and no account-management layer. It also means agreed response targets rather than resolution guarantees, declared leave, and no pretence of 24/7 cover.
Start with the problem
If your team is spending hours on work a tool could do, tell me what the work is: what it does, where it goes wrong, and what it is costing. If it is something I can help with, I will tell you how. If it is not, I will tell you that too.