Start a project

Software for small UK businesses

Custom tools, AI agents for routine admin, and servers you own. One developer, fixed prices, projects from £1,500.

Start a projectSee prices

What I build for small businesses. Software, automation and the servers they run on.

Builds custom software for your team

Booking systems, quoting tools and customer portals, written around how you already work.

bookings reminders/send.ts +3+4−2−3
@@ -38,10 +38,11 @@ function sendReminder(booking, i = 0) {
3838 const shop = loadSettings("reminders");
39 while (i++ < 3) {
39 while (i++ < shop.retries) {
4040 const sent = await sms(booking, 24);
40 const sent = await sms(booking, shop.hoursBefore);
LT Code review 2m Applied
Use shop.hoursBefore so each shop sets its own.
4141 if (sent.ok) return sent.id;
42 await sleep(60000);
42 await sleep(backoff(i));
43 log.warn("retry", booking.id);
4344 }
4445 throw new ReminderError(booking.id);
4546}

Automates routine admin with AI agents

Agents read the inbox, file paperwork and draft replies. Nothing is sent until you approve it.

Inbox agent
Running
Today, 08:02
What came in overnight?
Twelve emails. Five invoices are filed, and three replies wait for your approval. Shared inbox
Ask the agent

Runs your services on servers you own

Docker, backups and monitoring on your own hardware or a UK server, with a written runbook.

office/server bash main
~/office/server$./check --restore
4 of 4 checks
backup/nightly02:14ok
restore/database3 tablesok
certs/renewal61 daysok
disk/usage38%ok
All checks passedin 2.1s
~/office/server$

AI automation with an approval queue

This is the approval queue I build into every automation. The agent reads each message, does the routine part and stops for a yes on anything that leaves the business.

See AI automation

You own the code, the servers and every password. Each project ends with a written handover, so any competent developer could pick up the work without me.

How a software project runs

The same four steps every time, with a fixed price agreed before any code is written.

1. A 30-minute call. Free. You describe the job and how it is done today.

2. A written proposal. Scope, timeline and one fixed price.

3. Weekly demos. Working software every Friday, not a status report.

4. Handover and care. Code, logins and a runbook, then optional support.

See the project steps

Project: booking tool
2 of 5
  • Call about the job
  • Proposal agreed, fixed price
  • Friday demo: SMS reminders
  • Handover and runbook
  • Monthly care, if you want it

Coming to the Journal. Plain reviews of the tools I build with.

Why I host n8n on your own server

Workflow automation you host yourself, and what that costs compared with a monthly plan.

Reach your office server with Tailscale

Reaching the office server from home without opening a single port on your router.

Local AI models for automation, with Ollama

When a model on your own machine is good enough, and when it is not.

Sample entries: the titles show what the Journal will cover while the first articles are written.