What a small business automation consultant actually does (and what one should cost)

“Automation consultant” is a vague title, and the people who use it do very different work. Some build software. Some sell a platform. Some sit at a desk with your office manager and figure out why an invoice takes three people to send. This piece is about that last kind, because it is the kind most 5 to 100 person businesses actually need.

Here is what the job involves, what an honest engagement looks like, the warning signs, and what the market charges for it as of August 2026.

The five processes an automation consultant usually touches

Walk into most small businesses and the same five jobs are eating the hours. They are not glamorous. They are the reason people stay late.

1. Quote follow-up. An estimate goes out and then nothing happens unless someone remembers. The fix is usually a simple rule: if a quote has not been answered in three business days, a follow-up goes out from the same person’s address with the quote attached. The consultant’s job is to find where the quotes live, confirm who should own the follow-up, and wire the reminder to the tool the team already uses. No new platform.

2. Intake to CRM. A lead arrives by web form, phone, or text, and someone re-types it into the CRM, or into a spreadsheet that is standing in for a CRM. The consultant maps each intake channel, decides what the minimum record needs to contain, and connects the channels so the record creates itself. When intake arrives as free text, such as an email describing a job, a small amount of AI reads it and fills the fields, with a person checking before it saves.

3. Scheduling confirmations. Appointments get booked and then confirmed by hand, rescheduled by phone, and no-showed anyway. The consultant connects the calendar to a confirmation message, adds a reminder the day before, and routes replies back to a person. The hard part is not the software. It is agreeing on the wording and on what happens when a customer replies “can we do Thursday instead.”

4. Invoice reminders. Invoices go out on time and get paid late, partly because nobody wants to make the awkward call. Most accounting tools already have reminder features that nobody turned on. The consultant’s first job is to check that. The second is to connect the accounting tool to whatever system knows the job is actually finished, so the invoice goes out the day the work is done rather than at month end.

5. Reporting. The owner wants to know, every Monday, how many jobs are open, what is unbilled, and who is overloaded. Someone builds that in a spreadsheet by hand. The consultant pulls the numbers from the tools that already hold them and puts a plain report in the owner’s inbox on a schedule.

What the work looks like week to week

The first thing a good automation consultant does is not automation. It is watching. They sit next to the person who does the job, ask them to do it the normal way, and take notes. This is where most of the value comes from, and it is the part that gets skipped on a discovery call.

After that, a short engagement tends to follow one shape. The numbers below are typical for a single workflow and line up with our own Implementation Sprint.

• Week 1: map and agree. Write down the current process with the people who run it. Settle which version is correct when there are several. Agree the finish line in writing, including what “done” looks like and who owns it afterward.
• Week 2: build and test on real data. First working version, run against recent real records rather than a clean sample. Expect surprises: a customer with two email addresses, a job with no close date. They are the reason this is not a one-week project.
• Week 3: fix and add checkpoints. Repair what real data broke. Add the human review steps where a mistake would cost money, such as anything that sends a message to a customer or changes a dollar amount.
• Week 4: train and hand over. Train the people who will run it, on their own accounts. Hand over documentation in plain English. Watch it run unattended for a few days before signing off.

Notice what is absent: a roadmap deck, a platform migration, a six-month phase two. In a 20 person business they mostly delay the day something starts working.

What a fair engagement includes

A good quote is short enough to read and specific enough to hold someone to. It should contain:

• A written scope. Which process, which tools, which people. What is in and, just as important, what is out.
• A fixed price. Anything with a clear finish line can be priced. If it cannot be, the scope is not clear yet, and the first job is clarifying it.
• Training. Named people, real accounts, real work. Not a recorded walkthrough.
• Handover. Documentation your team can follow without calling anyone, and a named internal owner.
• An honest no. Somewhere in the engagement, the consultant should be willing to say “this one is not worth automating yet.” If everything is worth doing, nothing has been evaluated.

We have written more about the order of operations in fix the process before you buy software.

Red flags

A few patterns that, in our experience watching small business owners shop for this, tend to end badly.

• The proposal arrives before anyone has watched the work. That is a guess with a price on it.
• Every answer is the same platform. Plenty of firms are resellers, and some are open about it. Ask directly whether they earn anything when you buy a particular product.
• Custom software is the first suggestion. Custom software and automations are sometimes the right answer, but they should come after the cheaper options have been tried and found wanting.
• Training is a line item you can remove. A change nobody on your team can run without the consultant is not finished.
• Hourly with no cap. Fine for support after a build. Not fine for the build itself.
• Nothing ships in the first week. You should see something concrete in days, even if it is small.

What it should cost

These are market ranges as of August 2026, taken from our longer piece on what AI consulting costs a small business. They are what independent consultants and small practices publicly quote, not a promise about any specific firm.

Engagement	Market range, as of August 2026
Independent consultant, hourly	$150 to $300 per hour
Fixed-price project, one workflow	$2,000 to $20,000
Typical four-week automation build	$4,000 to $15,000
Half-day assessment	From $750
Monthly support retainer	$1,500 to $5,000 per month

Where a single workflow lands inside the $4,000 to $15,000 range depends on three things: how many systems are involved, how messy the inputs are, and whether a tool with no usable integration has to be worked around. Two tools with decent integrations and clean data sit near the bottom. Three or more systems and data that needs cleaning before it can be used sit near the top.

A quote far below the range usually means testing on real data or training has been left out. A quote far above it usually includes a platform you may not need. Either way, ask.

The retainer row is the one to be careful with. It is fair when a built system needs someone watching it. It is not fair as a standing meeting. Under 100 employees, buy a project first, and add support only if the thing you built turns out to need it.

Where to start

Pick the one of the five processes above that makes someone on your team sigh. Write down how it works today, in a few lines, before you talk to anyone. Then find a consultant who will come and watch it happen, quote a fixed price for fixing that one thing, and tell you plainly if it is not worth fixing.

That is the whole job.

Common questions

Is an automation consultant the same as an AI consultant?

Mostly, for a business under 100 people. The automation consultant connects the tools you already own and removes the re-typing. AI shows up inside that work when something unstructured, like an email or a scanned form, needs to be read before it can be moved. Anyone selling one without the other is usually selling a product.

How long does a typical engagement take?

A half day to assess, then about four weeks to build one workflow end to end, test it on real data, and train the people who will run it. If the first proposal is measured in months, it was written for a bigger company.

Do we need custom software?

Less often than people expect. Most small business automation is two or three existing tools connected with a small amount of logic between them. Custom software makes sense when nothing off the shelf fits, and a good consultant will say which case you are in before quoting.

What should we have ready before hiring one?

A written version of the process, even a rough one. If three people do the job three ways, the consultant spends paid hours settling which way is correct. Writing it down first lowers every quote you get, and sometimes the writing turns out to be the fix.