When not to automate
Automating a broken process doesn't fix it. It scales the breakage. The signals that tell you to stop and fix the underlying problem before touching the workflow.
Every GTM engineer gets asked to automate things that shouldn’t be automated. The person asking is usually in pain and wants it to stop. The reflex to automate is often the wrong response. Three situations come up where building automation makes things worse.
Should you automate a process that isn’t defined yet?
No. Define the play first and automate it second. If the team can’t describe what good looks like in a sequence (what triggers it, what message goes to whom, what the success condition is), automating that process produces consistent bad output at scale. The automation is a multiplier, not a design tool.
Can automation fix dirty CRM data?
No. Enrichment pipelines running on dirty data don’t clean the data. They route bad records to the wrong reps faster. If data quality is below threshold, fix the CRM before building the workflow: data integrity is a prerequisite, and automation running on a broken data layer scales the breakage.
I’ve seen companies automate inbound routing before fixing their CRM and end up with more leads going to wrong reps at higher velocity.
What happens when you automate before the org can operationalise it?
An automated system that fires sequences the rep doesn’t know about creates confusion, not pipeline. Sales ops, the rep, and the system need to be in the same model, and someone has to own what the automation produces. Without an owner it creates noise. Adoption is part of the build scope.
How do you know if a process is worth automating?
Ask what happens if the automation runs perfectly. If the answer isn’t clearly better than what exists today, the problem isn’t a workflow problem. The job is finding the constraint in the revenue motion and removing it, and automation only helps when that constraint is a missing workflow.
GTM engineering isn’t about chasing automation for its own sake. Sometimes the constraint is a missing process definition, a missing data layer, or a missing agreement between sales and marketing. Automation fixes none of those.