Published: 2026-10-21 — Ian
Finding an Automation Consultant: What to Look For
Many founders hire an automation consultant based on their toolset expertise or portfolio of flashy integrations, then discover the consultant doesn't understand their actual business operations. The right hire is someone who can map your workflows, ask hard questions about failure handling, and think in systems—not someone who knows the most tools.
Systems thinking matters more than tool breadth
A consultant who thinks in systems understands that automation is about connecting workflows, not just connecting tools. They ask questions like: what happens when this step fails? How will you know it failed? What breaks if this process doesn't complete? Where does data come from, and how do you know it's clean?
A consultant who leads with tools asks: which platform do you use? Can I integrate it with that one? Do you want Zapier or native integration? This is a red flag. Tools are interchangeable. Systems thinking is not.
Look for real integration experience
Integration experience means they've actually had to connect messy, incompatible systems in production and dealt with the reality that data formats don't match, APIs change without warning, and workflows break in ways you didn't anticipate. They've built error handling, monitoring, and recovery logic. They know what happens on day 90 when a system update breaks an integration.
Ask them about a failed integration project. A good consultant will describe what broke, why it broke, and how they fixed it. A weak consultant will gloss over failures or blame the tool.
They should ask about your current workflows first
Before recommending any solution, a good consultant interviews you about how work actually moves through your business. They ask who touches each step, where data lives, what exceptions exist, what breaks most often, and what takes the most time. They document this—not as a sales exercise, but because understanding your workflows is the entire foundation of any automation work.
If a consultant jumps to 'here's what you need' before understanding 'here's what you're actually doing', find someone else.
Reliability and failure handling are their starting point
A consultant focused only on speed and feature count will build automations that fail silently or break when assumptions no longer hold. A good consultant starts every project by asking: what can go wrong, and what should happen when it does? They design for failure, not pretend it won't happen.
Listen for language around logging, alerting, recovery, and monitoring. If they don't mention these unprompted, they haven't built production-grade automations.
What to ask a consultant before hiring
- Walk me through how you document a workflow before automating it. What do you document?
- Tell me about an integration that failed in production and how you diagnosed it.
- How do you design for failure handling? Give me an example from a past project.
- What's your approach to monitoring and alerting once an automation is live?
- How long do you typically spend understanding current processes before recommending solutions?
- Can you explain your most recent integration project in terms of data flows and failure modes, not just the tools you used?
- What do you do if the tool you recommended doesn't fit the workflow after you dig deeper?
Red flags to watch for
Consultants who pitch solutions before understanding problems. Consultants who focus the conversation on tools instead of workflows. Consultants who don't ask about failure modes, monitoring, or what happens after launch. Consultants who suggest automating processes that haven't been documented yet. Consultants who promise speed without discussing reliability.