Add-ons, apps & AI
Bookings, payments, ordering, customer records and useful AI. Built around your business, connected to what you already use, and owned by you.
No copy-paste. No second subscription. No chasing.
Keep the system, not the subscriptions
A booking tool, review tool and customer list can become three monthly bills that still do not talk to each other. I build the useful parts into one system and leave out the rest.
The usual stack
Stop paying and the useful part stops with it. Your data sits across other companies.
What I build
The domain, hosting, code, content and records stay under your control.
Build your system
Start with the work that wastes time or loses money. Pick as many jobs as you need and the estimate updates beside them.
Three different kinds of build
The label matters less than the job. The build should be as small as it can be, and no smaller.
A focused job inside the website: bookings, payments, reviews, a newsletter or direct ordering.
Best when the website is already the front door.A private working area with logins, records and steps built around how the team actually works.
Best when a spreadsheet has become the business.A useful decision or draft added to a real process: sort, summarise, answer, check or prepare.
Best when the task repeats and still needs judgement.See the handover
Pick a common moment. The customer does one simple thing; the system handles the steps that usually get copied, forgotten or chased.
A booking, from start to done
The diary is filled and the no-show risk is lower.
A lead, while it is still warm
You answer faster without letting AI speak unchecked.
A missed call, recovered
The customer is not left wondering, and the lead is not lost.
Built, not proposed
Apps and in-house plugins already doing their jobs. The number on each card is the proof that exists, not a projection.
A faster local-services marketplace built to treat traders fairly
100+ local service providers and countingView projectEvery business mailbox in one secure, shared workspace
15 small businesses using the platformView projectA private CRM tailored to website, SEO and LLM delivery
20+ active projects managed in one tailored systemView projectOne AI workflow for SEO, structured data and LLM visibility
9 client websites using the pluginView projectAI content, multi-channel publishing and backlink activity on autopilot
5 client websites gaining leads and visibilityView projectTailored articles, images and internal links—from research to publishing
7 client websites using the automatic publishing workflowView projectAI, with the important part explained
AI is a component, not the product. I choose where it runs from the data, the task and the cost - then keep a person in control where a wrong answer matters.
Keep what already works
A new system does not require a ceremonial bonfire of everything you already use. I keep the useful tools, connect them where possible, and replace only the weak link.
From bottleneck to working tool
We start with the job, not a list of features. You see the working shape early, use it, and correct it before the build grows.
One call. We follow what happens now and find the part worth fixing first.
The core route works before polish or edge cases take over the budget.
Your team tries it. I watch where the process helps and where it gets in the way.
It goes live with the access, code and explanation needed to run without me.
Before we map it
Usually, yes. I check the current site, hosting and data first. If the foundation is sound, I add the system without rebuilding the public website. If it is not, I explain the weak point before proposing anything larger.
No. The build is a one-off price and the code and records are yours. Hosting, a domain and any outside payment or AI service still have their own direct costs. Ongoing support is optional rather than a switch that keeps the system alive.
An add-on is enough when the job belongs naturally inside the website, such as bookings, reviews or payments. An app makes sense when staff need logins, private records, permissions or a workflow of their own. I start with the smaller answer.
The process decides the risk. AI can sort, summarise or prepare a draft, but a person stays in control wherever a wrong answer affects a customer, payment or business decision. Important actions are logged and can be checked.
Often. I keep the useful parts of the current setup and connect them through an API, email, an export or a direct integration where the tool allows it. If a provider locks the data away, I will say that before the build starts.
You do. The domain, hosting, code, content and business records sit under your control. You can keep running it without a licence from me, move it, or ask someone else to work on it later.
The next useful step
Twenty minutes is enough to tell whether it needs an add-on, an app, AI - or no new software at all.