Published: March 2026 | Author: Clide Butler | Category: Automation Consulting | Read Time: ~9 min
You've heard the pitch before. An automation consultant walks in — or sends a LinkedIn DM — and promises to "transform your operations," "save you 20 hours a week," and "scale your business without adding headcount." The slides look polished. The case studies are compelling. The price makes you wince.
And somewhere in the back of your head, a voice asks: Is this real, or am I about to spend $10,000 on something I could've done with a spreadsheet?
That voice is healthy. You should listen to it.
I'm Clide Butler. I build automation systems for small businesses and I'm telling you flat out: not every business needs to automate, not every automation project delivers ROI, and not every consultant is worth hiring. If you're doing your due diligence before writing a check, this guide is for you.
Here are the five hard questions you should ask — and exactly what to do with the answers.
Question 1: "Can You Show Me the Actual Cost of My Current Process?"
Before any automation conversation can be honest, you need a baseline. Not a vague "you're wasting time" statement. An actual number.
Here's how to calculate it yourself:
- Pick one process you want to automate (e.g., sending invoices, onboarding clients, following up on leads).
- Count the steps. How many people touch it? How many minutes per instance?
- Multiply: minutes × instances per month × hourly labor cost.
- Add error costs: what does a mistake in this process cost you? Rework hours, refunds, lost clients?
A good consultant will walk you through this math before quoting anything. A bad one skips straight to the solution.
What a good answer sounds like: "Based on what you've told me, this process costs you roughly $1,400/month in labor and you're losing one client every two months to slow follow-up — so your real cost is closer to $3,000/month."
What a red-flag answer sounds like: "Businesses like yours typically waste 15–20 hours a week on manual tasks." (Generic. Meaningless. Not your business.)
If a consultant can't help you quantify your actual current cost, they can't prove their solution is worth more than it costs. Walk away.
Question 2: "What Happens When It Breaks?"
Every automation breaks eventually. An API changes. A third-party tool goes down. Someone enters data in an unexpected format and the whole workflow grinds to a halt. This isn't a worst-case scenario — it's Tuesday.
The question isn't whether it'll break. It's: what happens when it does?
Ask the consultant these follow-ups:
- Who monitors the system after launch?
- Do I get alerts when something fails?
- Can my team fix minor issues, or do I need to call you every time?
- Is ongoing support included in the price, or billed separately?
- What's your average response time when a client reports a problem?
What a good answer sounds like: "I build in error notifications so you or your team will know immediately if something fails. I also document every workflow so you're not dependent on me. Monthly check-ins for the first 90 days are included."
What a red-flag answer sounds like: "These systems are very stable, we rarely have issues." That's not an answer. That's avoidance.
If ongoing support isn't discussed before the contract is signed, you'll find out what it costs when you need it most.
Question 3: "Who Owns This When You're Done?"
This is the question most business owners forget to ask — and the one that creates the most painful situations six months after a project ends.
The problem: some consultants build on proprietary platforms, locked accounts, or personal API credentials. When the relationship ends, you're stuck. You can't access your own workflows, can't modify them, and definitely can't hand them to someone else.
Ask directly:
- What tools and platforms will you use?
- Will the accounts be under my name or yours?
- Can I access, edit, and transfer everything without your involvement?
- If I want to hire someone else to maintain this system in 18 months, is that possible?
- Will you provide documentation?
What a good answer sounds like: "Everything runs under your accounts — Zapier, Make, whatever we use, it's yours. I'll deliver a workflow map and documentation. You could hand this to any competent VA or consultant and they'd know exactly how it works."
What a red-flag answer sounds like: "We manage everything on our end so you don't have to worry about it." Translation: you don't own anything.
You're not just buying an automation project. You're buying a business asset. Make sure it's actually yours.
Question 4: "What Does Success Look Like in 90 Days?"
Vague promises are the refuge of people who don't want to be held accountable. "You'll save time." "Your team will be more efficient." "You'll grow faster."
None of those are measurable. None of them tell you whether the investment worked.
A credible consultant should be able to define success in specific, testable terms before work begins.
Push for numbers:
- By what date will the system be live?
- What's the target reduction in manual task hours?
- What error rate do you expect vs. what we have now?
- What's the trigger for us to know the project succeeded or failed?
What a good answer sounds like: "By day 30, the onboarding workflow will be live. By day 60, we'll review whether client setup time dropped below 2 hours. By day 90, we'll have baseline data on whether the automation actually saved what we projected."
What a red-flag answer sounds like: "It depends on a lot of factors, but most clients see improvements within a few months." That's not a success metric. That's a disclaimer.
No metrics, no accountability. No accountability, no incentive to actually deliver.
Question 5: "Can I Talk to Three Clients Who Had a Similar Problem?"
References are table stakes. But most business owners either forget to ask or accept a testimonials page as a substitute.
A testimonials page is marketing. A real reference call is data.
What to ask actual references:
- Did the project come in on budget? If not, why?
- Was the timeline accurate?
- What broke, and how was it handled?
- Would you hire them again for a larger project?
- What would you have done differently before signing the contract?
That last question is the most revealing. People who've been burned will tell you — if you make it comfortable enough to be honest.
What a good answer sounds like: "Absolutely. Here are three clients you can call directly. One had a very similar CRM integration project. I'll give you their numbers."
What a red-flag answer sounds like: "We have lots of happy clients. I can send you some testimonials." Or: "Our clients are pretty private about their business results." Or any version of "no."
If a consultant has no references willing to take a 10-minute call, ask yourself why.
Consultant vs. In-House vs. DIY: How to Actually Decide
Once you've done the interrogation, you still need to decide who does the work. Here's the real breakdown — not the version consultants tell you, not the version software vendors tell you.
DIY (Do It Yourself)
Best when:
- Your process involves fewer than 3 steps and 1 tool
- You have at least 10 hours to learn a tool like Zapier or Make
- The failure cost is low (a missed Slack message, not a missed invoice)
- Your volume is under 100 instances per month
Real cost: $20–$100/month in software + your time. If your time is worth $100/hour and you spend 20 hours figuring it out, your DIY automation cost you $2,000 before it ran once.
The trap: People underestimate their own time. "I'll just YouTube it" turns into three weekends and a system that half-works.
In-House (Hire Someone)
Best when:
- You have enough ongoing automation work to justify a part-time or full-time role
- You need someone who understands your whole business, not just one workflow
- You're building a long-term capability, not solving a single problem
Real cost: A capable automation specialist costs $55,000–$85,000/year for a full-time hire. A part-time VA with automation skills runs $25–$45/hour. If your automation needs are intermittent, this gets expensive fast.
The trap: Hiring before you know what you actually need. Most businesses hire someone to "handle the tech stuff" and end up with a glorified data entry role.
Consultant (Hire a Specialist)
Best when:
- You have a defined, high-value problem (a specific process that costs real money)
- You need a working system delivered, not a project that takes six months
- You don't want to be the one maintaining it long-term
- Your needs are intermittent — you want to call someone when something needs building or fixing
Real cost: Honest range for a quality automation project: $1,500–$15,000 depending on complexity. Simple three-step Zapier workflows: $1,500–$3,000. Multi-system CRM integrations with conditional logic and error handling: $5,000–$12,000+. Ongoing retainer for maintenance and new builds: $500–$2,000/month.
The trap: Cheap bids that turn into expensive change orders. Anyone quoting $300 for a "full business automation" either doesn't understand the scope or doesn't plan to finish it.
Red Flags in Proposals: What to Watch For
You've done the interrogation. You're reviewing proposals. Here's what sends up a flare:
🚩 No discovery phase. If someone quotes you without asking detailed questions about your current process first, they're guessing at your problem.
🚩 Everything's included, nothing's defined. "Full automation of your business" is not a deliverable. Look for specific workflows, tool names, expected outputs, and timelines.
🚩 No mention of your existing tools. Real automation connects to what you already have — your CRM, email platform, scheduling tool. If the proposal doesn't mention your current stack, they're building in a vacuum.
🚩 Payment front-loaded with no milestones. Paying 100% upfront removes accountability. Look for milestone-based payments tied to deliverables.
🚩 No documentation included. "We'll set it up and manage it" without documentation means you're renting, not buying.
🚩 Unrealistic timelines. A fully automated client onboarding system in two days? A CRM integration by end of week? Either they're cutting corners or they don't understand what they've committed to.
🚩 Pressure to sign fast. "This pricing is only good through Friday." Real consultants don't need to manufacture urgency. Your due diligence timeline is your call.
Realistic Timelines: What to Actually Expect
Here's what honest project timelines look like:
| Project Type | Realistic Timeline |
|---|---|
| Simple 2–3 step workflow (e.g., form → CRM → email) | 3–7 days |
| Multi-step lead nurture sequence | 2–3 weeks |
| CRM integration with data mapping | 3–5 weeks |
| Full client onboarding automation | 4–8 weeks |
| Multi-department workflow overhaul | 2–4 months |
Add 1–2 weeks for testing, revisions, and UAT (user acceptance testing). Anyone skipping testing is skipping quality.
The Bottom Line for Skeptics
Your skepticism is a feature. It's what separates business owners who get lasting results from the ones who chase the next pitch.
Automation done right is one of the highest-ROI investments a small business can make. Automation done wrong is an expensive lesson in vendor selection.
The questions in this guide aren't designed to trip up good consultants — they're designed to help good consultants prove their worth. If someone gets defensive when you ask for references, clarify ownership rights, or want a real success metric, that defensiveness is your answer.
The right consultant will welcome every one of these questions. They'll have documented answers, real references, and a clear proposal that spells out what you own when the project is done.
Ready to Ask These Questions to Me?
I built this guide because I'd rather lose a client who's not a fit than take on work that won't deliver results. If your business has a real process problem and you want an honest conversation about whether automation makes sense — and if so, what it should cost and how long it should take — let's talk.
Book a free 30-minute consultation →
No pitch. No PowerPoint. Just an honest look at your situation and a straight answer on whether automation is the right move.
Have a question this guide didn't answer? Drop it in the comments or reach out directly. I read everything.
About the Author: Clide Butler is an automation consultant based in Detroit who helps small businesses build systems that actually work — and stay working. Learn more at askclide.com.