A good AI consultant's day buys you three things: a map of where hours and enquiries leak out of your business, a short list of which leaks software can plug and which it cannot, and one working fix built before they leave. If you get slides instead of a map, a plan instead of a fix, or a tool recommendation with nobody to run it, the day was wasted. Most small businesses do not need a consultant. They need one leak fixed and someone who owns it.
What is an AI consultant, in plain terms?
An AI consultant is a person you pay by the day to work out where artificial intelligence, software that reads, writes, talks and decides well enough for routine work, would save you money, and then to show you how. The term covers a wide range: a strategist with slides, a hands-on builder who leaves with something running, and a salesperson for one platform. The day rate tells you nothing about which you are getting. The output does.
We have not quoted a day rate in this article because no consultant's rate card was something we could fetch and check tonight, and a guessed figure would be worse than none. What you can check is what the day produces, and that is the test that follows.
The problem in your money
Before you pay anyone, price the leak. Here is a worked example for a small firm with an office team, a letting agency, a clinic, a trade with two people in the office. It is an example: use your own figures and your own hourly cost.
Two staff each spend six hours a week re-keying: copying enquiries from email into a spreadsheet, typing the same customer details into the job system and the invoicing tool, chasing quotes by hand. Say their loaded cost, wages plus the on-costs that come with them, is £20 an hour. You should replace that with your own number.
2 people x 6 hours x £20 x 48 working weeks = £11,520 a year
That is the re-keying alone. It does not count the enquiry that sat in an inbox for two days because nobody copied it across, or the quote that was never chased because the reminder lived in someone's head. Now you have the number the consultant's day has to beat. If the day costs more than a quarter of the annual leak and does not leave a fix behind, the arithmetic is against it.
What the data says (13 October 2026)
"ai consultant" and "ai consultancy" are each searched 1,850 times a month in the UK (2026 run-rate). "automation consultant" gets 299, "crm consultancy" 126, "hubspot implementation" 39, "crm setup" 21, "zapier consultant" 11 and "n8n consultant" 10. The advertised cost per click shows what the trade thinks a buyer is worth: £81.64 for "crm setup", £110.02 for "crm integration services" and £95.02 for "sales pipeline software". Those are among the highest in our whole data set. In plain terms, consultants pay a great deal to meet you, which means the first hour of any consultant conversation is a sales call whether it is labelled one or not.
Locally, there is nobody. The Google Maps pack for "crm consultant" from Shepperton on 13 October 2026 returns firms in Manchester, Peterborough, London, Beaconsfield, Harrogate and Dublin. "crm consultant" plus any Surrey town shows effectively zero searches. A business in Walton or Weybridge buying a consultant's day is buying it remotely from someone who has never seen the office, which makes the output test below the only protection you have.
On the tools, the prices we could check tonight all start at nothing. Zapier's pricing page lists a Free plan at $0 with 100 tasks a month and two-step automations only (zapier.com/pricing, 13 October 2026). Make's pricing page gives its Free plan 1,000 credits a month (make.com, 13 October 2026). n8n publishes a self-hosted Community Edition on GitHub with no price stated, and its hosted Starter plan at 20 euros monthly billed annually (n8n.io/pricing, 13 October 2026). For a single small automation, the software is free. What you are paying a consultant for is knowing which one, and building it so it does not break in March.
What a good day actually produces
Judge the day on four deliverables. Each has a plain meaning, a way to check it, and a reason it matters.
| Deliverable | What it means | How you know you got it | Why it matters |
|---|---|---|---|
| A leak map | Every place an enquiry, a customer or an hour falls out, with a number next to it | One page, your figures, ranked by money | Without it you buy a tool for the loudest problem, not the dearest |
| A can and cannot list | Which leaks software fixes, which need a person, which need a process change | At least one item they tell you not to automate | A consultant with no "cannot" is selling, not advising |
| One working fix | The smallest leak, built and running before they leave | You watch it run on a real enquiry that afternoon | Proves they can build, and starts paying on day one |
| A named owner and a check | Who in your business keeps it running, and the one number they watch | A name and a number written down | Automations that nobody owns stop silently and nobody notices |
Our piece on what happens in an AI workflow audit walks through the first two deliverables hour by hour, and what an automation consultant actually gives you covers the third and fourth.
Your three options
Option 1: Free tools and a weekend
What it means. You or a capable member of staff pick the one worst re-keying job and automate it with a free plan: a form that writes to a spreadsheet, an email that creates a job, a text that fires when a call is missed. Zapier's Free plan at 100 tasks a month and Make's at 1,000 credits a month (both checked 13 October 2026) cover one small automation comfortably.
How you know it works. The six hours a week drops. You can measure it with a stopwatch in week two.
Where it falls down. Two places. The free limits run out the moment the automation is useful, and the person who built it on a Sunday is the only one who understands it. When they are on holiday and it stops, nobody knows. Our £700 automation mistake is what that looks like in practice.
Right for. A firm with one clear repetitive job, fewer than a couple of hundred enquiries a month, and someone who enjoys this. At that size this is the honest answer and no consultant is needed.
Option 2: A consultant's day
What it means. One paid day, scoped to the four deliverables above, with the working fix as the non-negotiable.
How you know it works. You hold the leak map and watch the fix run before they leave. The day pays back when the fix saves more than the fee within a quarter.
Where it falls down. Day rates reward days. A consultant paid per day has no reason to finish, and a strategy-only day leaves you with a document and the same leak. It also falls down when the leak is bigger than a day: a CRM, the one list of every customer and job, connected to your phone, your email and your invoicing is a build, not a day.
Right for. A firm that has priced the leak, knows it is in the low tens of thousands a year, and wants an independent map before committing to a build. Also right when you have three quotes from agencies and need someone to tell you which one is honest.
Option 3: An agency build with an ongoing owner
What it means. A specialist builds the connected system (phone, enquiries, CRM, follow-up) and keeps running it, measured on the number from your leak map. The CRM integration page describes what that looks like when the leak is in follow-up.
How you know it works. Monthly, one number: hours saved, enquiries answered, quotes chased. If they cannot report it, they are not running it.
Where it falls down. Cost against a small leak. If your annual leak is £11,520, a build and a retainer have to come in well under that to make sense, and for some firms they will not. A build also fails when it is sold before the leak map exists, which is how firms end up with a chatbot on a website whose problem was the phone.
Right for. A firm already spending on marketing, with a leak in the tens of thousands, that wants it fixed and kept fixed without owning the plumbing.
Our recommendation
Bottom line: price the leak first; under about £10,000 a year, do option one; above it, buy a day only on the condition that it ends with something running; and buy a build only after the map exists.
The reason is simple arithmetic. A day has to save more than it costs inside a quarter, and the only way to know is to have the leak priced before the day is booked. Firms that skip the pricing step buy the consultant's enthusiasm. Firms that do it either discover they can fix it on a Sunday with a free plan, or they walk into the day with a number, get a map and a working fix, and know exactly what a build would have to earn. If a consultant will not agree to leave something running, do not book the day. That rule alone removes most of the waste.
How to prepare for and run the day this week
- Monday: time the re-keying. Ask each office person to note, for one day, every time they copy information from one place to another and how long it took. A sticky note is fine. Multiply up by five and by 48. Done looks like: one annual figure in hours and pounds.
- Tuesday: list the tools. Write every system the business uses: phone, email, calendar, job system, invoicing, spreadsheets, WhatsApp. Note which ones already talk to each other. Done looks like: a list of under fifteen names, each with a login owner.
- Wednesday: write the brief. Three lines. "Our biggest manual job is X and costs roughly £Y a year. We use these tools. By the end of the day we want one automation running on a real enquiry." Send it to the consultant before booking. Done looks like: a reply confirming they will build on the day, in writing.
- Thursday: the day. Morning: the leak map, built with your figures, ranked by money. Midday: the can and cannot list, with at least one thing they tell you not to automate. Afternoon: the fix, built in the free tier of whichever tool fits, tested on a real enquiry while you watch. Last hour: a name and a number written down for who owns it. Done looks like: you can describe the fix to a colleague without the consultant in the room.
- Friday: the check. Open the tool's run history (Zapier: Zap History; Make: the scenario's History tab; n8n: Executions) and confirm it ran overnight. Put a monthly calendar reminder for the owner to open that same screen. Done looks like: one green run, one reminder, one name.
Mistakes we see
- Booking the day before pricing the leak. You cannot judge the fee without the number it has to beat.
- Accepting slides as the deliverable. A strategy document does not save six hours a week. A running automation does.
- Automating the loudest complaint. The dearest leak is often quiet: the quote nobody chased. Rank by money, not by who moans.
- No named owner. The automation stops in March, nobody notices until June. The check in step five is the whole protection.
- Buying a platform on day one. Every tool we checked tonight has a free tier. Build the first fix there and pay only when the limit is hit.
Want the leak map done before you book anyone?
If you want the Monday and Tuesday steps done with you, your figures turned into a ranked leak map, and an honest verdict on whether the right answer is a free plan, a day, a build or nothing, that is a short piece of work and you keep the map whichever way you go. Want me to map where the hours are leaking? If the answer comes back "a weekend and a free plan", I will say so. Here is what each system does, so you can see what a build would be if the number justified it.
