You should fix the process before you automate it because automating a broken process just makes it break faster at scale. Every engagement starts with watching how the work actually gets done, fixing the process by hand, and only then automating the clean version.
A client says "I need to automate my follow-up emails" and the instinct is to start building. But automating a broken process just makes it break faster. If the current follow-up happens inconsistently and the messaging is unclear, automating it means sending unclear messages consistently and at scale.
Every engagement starts with watching the client do the work. Not asking them to describe it. Watching. The gap between how people describe their workflow and how they actually execute it is where the real problems hide. "I follow up with every lead within 24 hours" often means "I follow up when I remember, which is sometimes 3 days later."
The sequence: watch the work happen, determine whether the pain is a process problem or a tool problem, fix the process manually, then automate the clean version. This approach almost always uncovers 3 to 4 additional pain points beyond the original request.
This positions the engagement as consulting (high trust, high value) rather than tool installation (commodity). The client sees that you care about their outcome, not just activating software.
The guard rail: do not over-audit simple tasks. If the job is "send a booking confirmation email," that does not need two weeks of process analysis. Match the depth to the complexity.
Topics
Frequently asked
What happens if you automate a broken process?
Automating a broken process just makes it break faster. If the current follow-up happens inconsistently and the messaging is unclear, automating it means sending unclear messages consistently and at scale.
Why watch the work instead of asking about it?
The gap between how people describe their workflow and how they actually execute it is where the real problems hide. "I follow up with every lead within 24 hours" often means "I follow up when I remember, which is sometimes three days later."
What is the sequence for fixing a process before automating?
Watch the work happen, determine whether the pain is a process problem or a tool problem, fix the process manually, then automate the clean version. This approach almost always uncovers three to four additional pain points beyond the original request.
Do simple tasks need a full process audit?
No. Do not over-audit simple tasks. If the job is "send a booking confirmation email," that does not need two weeks of process analysis. Match the depth of the audit to the complexity of the task.
Read next
Want to see these systems in action?
Start with a conversation. We will walk through how these workflows apply to your business.
Get your AI Roadmap