01
When a small business actually needs an automation consultant
Most owners hire too early (before there's a real process to automate) or too late (after a year of duct-tape spreadsheets). The right window is narrow but recognizable.
- You have a repeatable process that runs at least weekly.
- The same data is being typed into 2+ tools by hand.
- An owner or senior person is spending 5+ hours/week on a workflow that doesn't require judgment.
- You've already tried fixing it with a tool subscription and the tool sits unused.
- The cost of the manual work is now more than $20k/year in salary + opportunity cost.
Bottom line — If 3 or more apply, the ROI math works. If fewer, you probably need a better single tool — not a consultant.
02
What a small-business automation consultant should do
- Map your real process — not the one in your head — by watching it run.
- Find the 1–2 highest-leverage automations and ignore the rest.
- Quote fixed-fee on a defined scope, not hourly with no ceiling.
- Use tools you already pay for when possible.
- Ship a working automation, documentation, and a 30-day support window.
- Train one person on your team to own it going forward.
Bottom line — If they want to build everything they see in the discovery call, that's not consulting — that's billable expansion. Good consultants narrow the scope, not expand it.
03
What you'll pay (and what's fair)
A single automation project for a small business typically runs $4k–$15k fixed-fee, 2–4 weeks. A connected set of automations across a full workflow (e.g. lead → booking → reminder → invoice → review) runs $10k–$25k, 3–6 weeks. Ongoing monitoring + small changes runs $500–$2,000/month. If someone quotes 'discovery' as a separate $5k phase before they'll quote the build, that's a red flag — discovery should be free or rolled into the build quote.
04
How to vet one in a single call
- Ask them to describe a past project — what they built, what tools, what the outcome was. Vague answers = vague work.
- Ask if they'll talk to a past client. If the answer is 'we keep clients confidential' for everything, walk.
- Ask what tools they default to. 'We pick the right tool for the job' is a non-answer — good consultants have opinions and tradeoffs.
- Ask what happens after launch. If there's no documentation or handoff plan, you're buying a dependency.
- Ask for the proposal in writing with scope, price, timeline, and out-of-scope items explicit.
Bottom line — Five direct questions on a 30-minute call will tell you more than three discovery sessions. The right consultant answers them comfortably; the wrong one deflects.
05
Engagement red flags
- Hourly billing with no estimated ceiling.
- Building on a proprietary platform you can't migrate off of.
- No documentation deliverable in the scope.
- 'Discovery' priced separately at >10% of the expected build.
- Slow response times during the sales process (it only gets worse after signing).
Bottom line — Any single one is a yellow flag. Two or more = end the conversation politely and keep looking.
06
When NOT to hire a consultant
- Your process isn't actually defined yet — automating chaos just makes chaos faster.
- The 'manual work' is judgment work (pricing, customer triage, exceptions). Don't automate decisions you haven't made yet.
- You're under 3 employees and the owner does the manual work — you'll save time, but the project is rarely worth the cost at this size.
- You're about to switch tools — automate the new stack, not the one you're leaving.
Bottom line — Fix the process first. Switch tools second. Automate third. Skipping a step turns a $15k investment into a $15k mistake.
related