What I can help you with
Three jobs, in the order they actually happen.
1. Work out what's worth automatingusually a week
Before anything gets built, we find out whether it should be. I look at how your operation actually runs — where work queues up, where people repeat themselves, where enquiries go cold — and come back with a short list: what's worth automating, what isn't, and roughly what each one is worth to you.
Often the answer is “two of these fifteen steps, and leave the other thirteen alone.” At the dental clinic the thing worth fixing turned out not to be the booking software at all — it was that nobody could answer the phone after six.
2. Get it builtmost builds run two to six weeks
Then I build it. Phone agents that answer and book. WhatsApp and email systems that onboard, remind, invoice and chase. Order taking, follow-ups, the whole path from first enquiry to paid.
It runs on your systems and in your accounts, not mine. One person does the thinking and the building — you're not managing a consultant and a developer who blame each other. The dental clinic's phone line took three weeks from first call to live.
3. Keep it running and improvingmonthly
AI systems drift. Information goes stale, odd cases turn up, your business changes. I stay on monthly to keep it working and keep extending it.
Where I can, I build things you can update yourself. The dentist changes his own receptionist by sending it a WhatsApp voice note — if he's out on Thursday, he tells it, and it reschedules the patients itself. That's why keeping his system healthy takes me about two hours a week instead of two days.
What this costs
I don't have a price list, because the same system is worth very different amounts to different businesses. Instead we work out together roughly what it'll be worth to you — hours it gives back, or revenue that currently leaks away.
The build is priced at something you'd expect to recover within two or three months of that. Ongoing support runs at roughly a tenth of what the system brings in each month. Half up front, half on delivery.
And if we can't estimate the value together with a straight face, that's usually a sign I shouldn't be building it.
Everything runs in your name
The server, the API keys, the subscriptions — all of it sits in your own accounts, and you pay those vendors directly. I don't resell you infrastructure or put a margin on it, and I don't hold anything hostage.
It means you can see exactly what the system costs to run. And if you ever stop working with me, you keep all of it and can hand it to anyone.
Where the free part stops
The first piece is free and it stays free — you keep it whatever you decide. But it's the first piece, not the project. If it works and you want the rest built, that starts the normal way: half up front, half on delivery.
I build one thing free to show you I can. I don't build the whole thing free and hope.
Who this probably isn't for
I'm probably not your person if you want AI added because it sounds good rather than because something specific is broken.
Or if the process you want automated changes every month — automation needs something reasonably stable underneath it.
And if we can't work out together, with a straight face, what a system would actually be worth to you, that's usually a sign I shouldn't build it.
Not sure which of the three you need?
Start with a call. That's the first one, and it's free.
Book a free 30-minute call