You answer the same five questions forty times a week.
Enquiries, quotes, follow-ups, bookings, the same details typed into three places. I build small automations that take those jobs off your desk, on top of a website I host and look after.
- One developer, no account managers
- You own the accounts and the code
- A fixed quote before anything starts
I am Bart, a UK web developer. I look after sites for businesses across the UK: accountants, tradespeople, food businesses. I do all of this myself, so there is no team, no account manager and no ticket queue. More about me.
The work worth moving off your desk
Every one of these is a real piece of work a small business does by hand.
- Someone asks what it would cost
- An answer drafted within the minute, from your own notes and prices. You send it or change it first.
- The same enquiry you have answered a hundred times
- An assistant answers from your own pages and documents, and hands over the moment it does not know.
- Chasing people who never replied
- Follow-ups go out on the schedule you set and stop the moment someone replies. Nobody gets chased twice.
- Typing the same details into three different places
- The enquiry, the calendar and the invoice take the details once, from one form, and stay in step.
- Reading documents to pull out the same few fields
- Invoices, timesheets and order forms get read automatically, and the figures land where you work.
- Calls at eleven at night you never get back to
- Bookings taken overnight, confirmed on the spot, with reminders so the slot does not go to waste.
None of this replaces the part of the job you are good at. It removes the part you resent. Tell me which one of these you recognise.
Related services
The base layer
Websites and hosting
Automation sits on a site that is fast, yours, and findable. If yours is not, that gets fixed first, and you own all of it.
The free first step
Google Business Profile
Not in the map results for what you do? The call goes to whoever is. Check in ten seconds; if you are missing, I set it up free.
How a build actually goes
One message from you. I do the working out.
-
Tell me the job you keep repeating
One message is enough. The thing you do most often that you wish you did not, and roughly how often it lands. No form to work through, no discovery call, nothing to sign.
-
I come back with what I would automate, and what I would not
You get a fixed quote and a plain description of what will run, where it will run, and what it touches. If the base needs work first, you hear that now rather than halfway through.
-
I build it, then watch it on real traffic
It goes live, I watch it for the first couple of weeks, and I fix what actual customers break. Then it either keeps running on its own or I look after it, whichever you prefer.
You own everything. Always.
Every automation I build runs in your accounts, under your logins, on keys billed to you. Same with your domain, your site files, your content and your Google Business Profile. I make no claim on any of it and you have full access from day one.
That includes being able to read what the automation did. No black box you have to ask me about, and no part of the setup that only works while I am still involved.
Ask me for your transfer codes at any point and you get them. No exit fee, no rebuild, no ransom.
Fair questions
The honest answers, including the ones that talk you out of paying me.
Is this just ChatGPT with my logo on it?
No, and that distinction is the whole job. A chatbot that knows nothing about your business will confidently invent your opening hours. What I build is wired to your own material: your pages, your prices, your documents, your calendar. It answers from those or it does not answer. The useful part is rarely the conversation anyway, it is what happens afterwards without you: the enquiry logged, the follow-up scheduled, the details in the right place.
What happens when it gets something wrong in front of a customer?
It is built to hand over rather than guess. Anything outside what you have given it goes to you instead of being answered, and you see every conversation it has had. I watch it on real traffic for the first couple of weeks, because the real world always asks something the test did not. If a job is too risky to automate, I tell you that rather than sell it to you.
Could I not wire this up myself?
Some of it, yes, and if you enjoy that sort of thing you can get a long way in an afternoon. Two things tend to go wrong: it works until the month it quietly stops and nobody notices for six weeks, and the joins stall when the automation meets a site you do not control. If you would rather build it yourself, build it.
I already have a website and I like it.
Then it stays. Plenty of automation can be bolted onto a site I did not build. What I need is access to it and somewhere reliable for things to run. If your site is fine but nobody can reach the person who built it, that is the part worth sorting, not the design.
How small is too small?
If you repeat a job more than a few times a week and it takes more than a couple of minutes each time, it is worth looking at. The automations that pay off fastest are embarrassingly small. The ones that disappoint are usually the ambitious ones that try to replace judgement you are good at.
What does this cost?
It depends on what you actually need, and I would rather give you an honest number than publish one that fits nobody. Tell me what you have got and you get a straight figure back. No discovery call, no proposal deck, no account manager. Rolling monthly on the ongoing work, no long lock-in.
Tell me what your business repeats.
Quickest: send me the job and roughly how often it happens, on WhatsApp. I reply within 24 hours.
Message on WhatsAppOr use the form. Same person reads both, same reply time.
- One developer, no account managers
- You own the accounts and the code
- A fixed quote before anything starts
What happens next
- I reply with two or three questions.
- You get a plain description of what I would build, and a fixed quote.
- If it is not worth automating, I tell you that instead.