Operations
AI consultant for small business: when to hire one, and when not to
What an AI consultant does for a 15 to 60 person business, six reasons to wait, what you should own at the end, and ten questions to ask anyone selling it.

That's what someone will pay to get in front of you before you've said a word to them. Nineteen dollars, for the chance to talk.
So read that whole results page, this article included, with one hand on your wallet. RunSimpler sells all three of the things described below. We'll still tell you where each one is the wrong purchase. You can check that against your own week, and we'd rather you did.
What an AI consultant actually does
Take the word consultant apart and three jobs fall out.
Train your people. Someone works with your staff on the jobs they already do, then leaves them able to use the tools without help. You keep the skill in the building, and the cost on your side is your people's hours, which is a real cost nobody puts in the quote. There's a first-month version of that you can run yourself.
Build the system. Someone builds one specific thing. A quote that drafts itself from your job notes. A follow-up that goes out without anyone remembering to send it. You own the thing when it's done. What it costs you is somebody inside your company answering questions and signing off, every week, for as long as the build runs.
Do the work. Someone runs it for you every month and your team never opens the software. What it costs you is that nobody in the building learns how, so the day you stop paying you're back where you started.
Picking which one thing to hand over is its own job. There's a way to score your own tasks on paper before anyone quotes you.
Those three cost different amounts and they go wrong in different ways. A firm that only does one of them will find a reason you need that one.
Figure 1 / Matrix
Three routes, and what separates them is what you are holding when everybody leaves.
What you hold at the end of each route
| The question | Train your people | Build the system | Do the work |
|---|---|---|---|
| Who does the work afterward | Your people, using the tools without help. | The thing that was built, with somebody inside your company signing off while it runs. | Someone else, every month. Your team never opens the software. |
| What you own at the end | The skill, in the building. | The thing itself, with a plain English note on how to change it and how to switch it off. | Nobody in the building learns how. |
| What happens if you stop paying | You keep the skill in the building. | You own it when it's done. | You're back where you started. Ask what you keep, and put the answer in the agreement. |
Six reasons not to hire anyone yet
Work through these before you take a call. If more than two of them land, a consultant isn't your next purchase.
1. You can't finish the sentence
"I want to stop spending my own time on ______."
If that blank stays blank, don't buy yet. Whoever you hire will fill it in for you, and they'll fill it in with the thing they happen to sell.
2. You haven't tried the free version
Say you run a plumbing company with six trucks, which has its own version of this list. Before anyone quotes you for a system, take the last five estimates you wrote yourself and write them again with a free chat tool. Time both. Then read what came out the way a customer would read it.
What you're measuring isn't the minutes. It's whether the one you wrote by hand was better, and by how much. If it wasn't better, you've learned something uncomfortable and useful about the hour you spend on it every night.
3. The work only exists in one person's head
If your senior tech is the only one who knows how a boiler swap gets quoted, there's nothing for AI to follow. It will invent the parts it doesn't know.
The first invoice from any competent consultant will be for writing that down. You can do that part. Getting it out of their head takes an hour, and the prompt and the checklist for writing it up are free. Sit with the person who does the job and write the steps as they say them. Then watch them do it once and fix what you got wrong.
4. Nobody uses the software you bought last year
Check this one first. The field service system you pay for every month might be half configured. Your techs might still be texting photos to the office. Shelfware is the polite word for it. AI on top of that gives everybody a second thing to ignore.
The check takes ten minutes. Open the admin screen on the thing you pay for every month and put last month's active users next to the seats you're billed for. Most of us have never looked.
Fix what you already own.
5. You wouldn't be able to tell if it worked
Pick the number before you spend anything. Hours you personally spend on quotes each week. Calls that went to voicemail. Days from job finished to invoice sent. Count it by hand for two weeks, on paper if that's easiest.
Skip that step and you'll be told it worked. You won't have any way to disagree.
6. Somebody at a trade show mentioned it
Or a supplier newsletter did, or a competitor did on a call. Pay attention to that feeling. It still isn't a business case.
Say you run a dental practice. The office across town putting in an AI phone agent doesn't change your front desk's Monday morning. The hygiene recall list still needs working. Tomorrow's schedule still has holes in it. There's more than one way to get those two done, and only some of them cost money.
Figure 2 / Sequence
Six checks before you take a call, and if more than two of them land a consultant is not your next purchase.
Six reasons not to hire yet
You can't finish the sentence
"I want to stop spending my own time on ___." If the blank stays blank, don't buy yet.
You haven't tried the free version
Rewrite your last five estimates with a free chat tool, then read them as a customer would.
The work only exists in one person's head
There's nothing for AI to follow. It will invent the parts it doesn't know.
Nobody uses the software you bought last year
AI on top of half-configured software gives everybody a second thing to ignore.
You wouldn't be able to tell if it worked
Skip the count and you'll be told it worked, with no way to disagree.
Somebody at a trade show mentioned it
That feeling is data. It still isn't a business case.
Naming your own bottleneck
Here's the awkward part. Every test above needs you to say what's actually slowing the business down. That's a harder question than it sounds. Not for lack of knowing your own business. The thing slowing you down moves while you're busy, and nobody stands still long enough to watch it move.
A consultant will name it for you. That's part of what a first invoice buys. Notice the incentive, though. The person naming your problem is also selling the fix.
We built a free AI readiness check for that exact question, because we wanted the answer before a sales call instead of after one. Twenty questions, one tap each, about four minutes. Your finding and all five areas show up on screen the moment you finish. It names the one thing most likely holding AI back in your business. It also tells you what it ruled out. That part is worth reading twice.
It won't tell you who to hire. It will tell you what you're hiring about.
Then take the result into any sales call you have after it. Watch whether the person argues with the specifics or talks over them.
What you should own when the work is done
Six lines. Put them in the agreement before the first payment.
- Get the written procedure in your words, in a file you can open without asking anyone.
- Put every account in the business name on a business email address, not a staff member's personal login and not the consultant's.
- Keep the prompts somewhere your team can read and edit them.
- Take whatever got built with a plain English note on how to change it and how to switch it off.
- Measure the number from before the same way afterwards.
- Name one person inside your company who can run it when the consultant stops answering the phone.
If any line on that list gets pushback, you've learned something useful about what you'd be buying.
In practice it's the accounts line that gets it. A firm holding your logins is a firm you can't leave on a Tuesday, and some of them know that. Ask for it in writing and watch the answer rather than the explanation.
One page of rules keeps that list true after the consultant leaves.
How the money works
Three ways they'll charge you. Know which one you're being offered before the price comes up.
| How they bill | Honest for | Where it bites you | Ask this before you sign |
|---|---|---|---|
| Hourly | Advice, and anything genuinely unknown | The meter runs while they learn your business | What am I paying to have you learn? |
| Fixed project | A build with a shape you can both describe | The argument at the end is about what done meant | Read me your written definition of done |
| Monthly | Anything that has to keep running | You can be paying for something nobody opens | What do I keep if I stop paying? |
Go back to that results page and count how many of the first ten pages show you a price. We don't publish ours either. The honest reason is that the number depends on the task. The less flattering reason is that a page without a price gets more phone calls. Both are true.
What you can control is how big the first piece is, and that's worth more than arguing the rate.
Ten questions to ask anyone, us included
- What's the one thing you'd fix here first, and why that one?
- What do I own at the end? Read me the list.
- Who inside my company has to do work for this to succeed, and how many hours of it?
- Which number should move, and when should I expect to see it move?
- What would make you tell me not to buy this?
- Walk me through the first two weeks, day by day.
- Where does my customer information go, and who at your end can see it?
- What happens when the tool you built on changes or shuts down?
- Who checks the output before a customer reads it, you or me?
- What does it cost me to stop?
Ask number five, then wait. How long the silence runs is the answer.
Question seven is the one you won't be able to grade on the spot, so ask for that one in writing afterwards. The answer you want names the tool, names where your customer data physically sits, and names who at their end can open it. An answer that says enterprise grade and stops hasn't answered.
Don't skip question two. Someone who can read that list back without hesitating has handed work over before.
If you do hire, keep the first piece small
One task. One person inside your company who owns it. A fixed price and a date.
Small enough usually means something you could go back to doing by hand on Monday if it fell over. If the first piece can't be undone by hand, it isn't the first piece.
Then look at the number you counted before, and decide about the second piece with that in front of you.
Figure 3 / Flow
The first piece is one task, one owner and one date, and the second piece gets decided against a number you counted before anybody started.
The first piece, kept small
Needs a person
One task
Small enough to go back to doing by hand on Monday if it fell over.
Needs a person
One person who owns it
Inside your company.
Recorded
A fixed price and a date
With a written definition of done.
Then decide
Decide the second piece
Against the number you counted first, before anybody started.
- Needs a person
- Recorded
- Affirmed
Where we fit
We train teams, we build systems, and we run them. You know how we get paid now. Weigh the rest of this against that.
If the honest answer today is wait, then wait. The check is free and it'll still be here.
If you'd rather talk it through, twenty minutes on the phone costs nothing. We'll say on the call if one of the six reasons above applies to you. That's cheaper for us than selling you something that sits unused.
