Automation is a good fit for a task that is understood, repeatable, observable, and safe to retry. It is a poor fit for a process that still depends on unspoken judgment or produces consequences nobody knows how to reverse.
Before choosing a tool, run the task manually and write down what actually happens. The hidden exceptions are usually more important than the happy path.
Describe the trigger and the outcome in business language
“Automate leads” is not a workable specification. “When an approved website form creates a valid inquiry, add one contact to the CRM, preserve the original source, and notify the assigned person” is closer. It names a starting event, a result, and an owner.
Define which system is authoritative for each fact. If the website, CRM, email platform, and accounting system all appear to own the same customer status, the automation will copy confusion faster.
Find the decisions a person is making
Watch several real examples without moving private information into an unapproved tool. Record where a person interprets free-form text, recognizes a duplicate, applies an exception, asks for missing information, or refuses the task.
Some decisions can become explicit rules. Others should remain human checkpoints. A useful automation doesn’t have to eliminate the person; it can prepare the record, flag uncertainty, and wait for authorization.
Define failure before implementation
List what can happen when a connection times out, a destination rejects the record, a field changes, or two events arrive together. Decide how you will distinguish succeeded, failed, and unknown outcomes. “Try again” isn’t a complete failure policy.
Give each business action a stable reference when the systems support it, preserve logs that exclude secrets, and design a reconciliation step. Keep a change record for updates to the workflow so later behavior can be tied to an actual version.
Test the task safely before automating live work
Test normal input, missing input, a duplicate, a rejected destination, delayed response, and an authorized retry in an isolated environment. Confirm the record in the destination rather than trusting only the automation’s success screen. Verify notification and human follow-up separately.
Set limits on what the workflow may read, write, and trigger. The same approval principle used for AI website work applies here: authorization should match the consequence, not the tool’s maximum capability.
Know when the task is ready
The task is ready when its inputs are defined, ordinary exceptions are named, ownership is clear, success can be observed, failures reach a responsible person, and a safe stop or rollback exists. If those pieces are missing, improve the manual process first.
Automation should make a dependable process easier to operate. It should not be the first place the business tries to decide what the process means.
TechDex Presents…
Flashback to the ’90s
Get 2026 services at 1990s prices.
For a limited time, I’m rolling prices back on six focused small-business services. Choose one service for $800, or choose two for $1,200. Nothing is purchased here—I’ll review your request and confirm the scope with you first.
For related website work, explore this Rewind service:
The campaign form lets you choose one or two services and request a follow-up. It isn’t a checkout, and you won’t be billed when you submit it.