The forty-quid plumbing firm: what one trades business actually runs

A plumber in Sheffield just answered 47 customer enquiries before his kettle boiled, using a forty-quid-a-month AI stack.

It drafts replies to quote requests, books jobs into his calendar, and chases missed payments – right-sized AI for a one-man UK trades business that barely writes emails. He didn't write a single line of code.

The promise, in one breath:

• Under £40/month, all-in, for a one-man UK plumbing firm's AI workflows.
• Zoho CRM + OpenRouter + a small Next.js app on Railway Hobby.
• Three automations that run themselves: quote replies, calendar booking, late-payment chasing.

Small UK businesses – plumbers, salons, cafes – lose eight to twelve hours a week to admin that right-sized AI can handle in minutes. Open-source and open-weight models now do that work for less than a takeaway coffee per day, closing the gap between a three-person trades firm and a chain with a CRM team. The firms winning right now started small last quarter.

The stack, in plain English

Three monthly services, each under fifteen pounds, that a tradesperson can run from their phone.

Zoho CRM holds every job, every customer, every quote. The plumber types into it the way he always has, on his phone in the van. Nothing changed on his side.

OpenRouter routes the AI calls. Most of the work goes to open-source and open-weight models – MiniMax, DeepSeek, GLM – at roughly a tenth of the cost of a frontier model. When something matters (a complaint, a pricing dispute, a final review before send) the call gets bumped to Claude or GPT. The router picks automatically.

A small Next.js app runs on Railway Hobby, five pounds a month. The only screen the plumber ever opens. Three things on it at any time: unpaid jobs, waiting enquiries, quotes needing a follow-up. No dashboard sprawl.

Total monthly cost: thirty-eight pounds. Less than most tradespeople spend on tools, less than one missed appointment.

AI workflows for a small UK plumbing firm: what runs every morning

Three automations, each running without anyone asking.

1. Drafts replies to incoming quote requests. A customer texts about a leaking radiator. The system reads the message, finds the last three jobs the customer had, pulls standard pricing, and writes a reply in the plumber's voice. He reads, edits if he cares, and presses send. Time saved: about forty minutes a day.

2. Books jobs into the calendar. When a customer confirms a time, the system updates the calendar, sends a WhatsApp reminder the day before, and writes the job onto the invoice when the work is done. Three touch points. Zero manual work.

3. Chases missed payments. Customers fourteen days past their invoice get a polite WhatsApp message. Twenty-eight days gets a firmer email. Forty-two days gets a phone call from the plumber himself. The cheap chore, automated. The harder conversation, kept human.

This is not "AI everywhere". This is three specific tasks, running reliably, paying for themselves.

Cheap AI stack for trades businesses: why the cost stays low

The real cost isn't the model price, it's unanswered customer enquiries and forgotten invoices. For most small UK trades businesses, saving those eight to twelve admin hours a week is worth thousands of pounds a year; the AI stack that does it costs tens.

The price difference between models is small in absolute terms – four pence versus six pence per reply, about forty pence a day, one hundred and fifty pounds a year. Not the money that decides whether to add AI. The money that decides it is the time you stop losing.

Open-source and open-weight models have come far enough that, for ninety percent of the work, the output is indistinguishable from the frontier ones. They don't hallucinate as much. They follow instructions better. They handle UK English without a fight. If you tried them eighteen months ago and were unimpressed, try them now.

Where this stack is not the right tool

Three limits worth being honest about.

Money, contracts, complaints – keep a human in the loop. Open-source and open-weight models get tone and facts right most of the time, but the ten percent they miss is the kind of error that loses a customer.

Up-to-the-minute UK-specific information still needs a search step on top of the model – regulation changes, supplier pricing, local council rules. The model will guess confidently if you let it.

Sensitive personal data needs a careful audit – medical notes, financial advice, safeguarding concerns. The models aren't unsafe, but they aren't pre-tuned for these domains the way dedicated tools are.

In every case where the answer matters, the model is the draftsperson, not the publisher. The plumber reads every reply before it goes out. The salon owner reviews every quote. The cafe manager checks every health-and-safety note. The model writes. The human decides.

How long AI setup takes for small UK businesses

Two to four weeks for a trades firm like the one above. A week to map the actual workflows (not the ones in the brief, the ones the business actually runs), a week to wire the data, a week to train the model on the business's voice and tone, and a week running the system alongside the old way before switching over.

Faster for a service business with a CRM already in place. Slower for a brand-new business with no data history. I wrote about how I scope the work on my approach page.

If you run a small business and wonder whether you can do this yourself, you probably can. The three services above cost about thirty-eight pounds a month. The setup takes a few afternoons. The hard part is having the patience to test the system in production for a fortnight before you trust it.

What I'm watching for in the next twelve months

Voice agents that take a real phone call without an appointment. The technology has improved enough this year that I'm about to deploy two voice agents for UK clients, one for a clinic and one for a trades firm. Both will answer the phone out of hours, take messages, and book jobs for the morning. Watch this space.

Better memory. Every system I build today learns something about the business and forgets it the next morning. The next generation of open-source and open-weight models will let the system remember a customer's preferences across months of conversation without me re-teaching it. That is when the real change happens – most small-business admin is "remember this preference and apply it consistently for the next year", not just "answer this query".

If you run a small UK business and want to know where to start, identify the one admin task that takes the most time each week and run an open-source model on it. Not the whole company. One task. Get that right, then the next one.

You can read about how I build these systems in the Approach section, or see real builds in my Work (Vereby is the multi-tenant platform that powers setups like this one).