Most businesses don’t have an automation problem. They have a “nobody noticed how much time this takes” problem. The work that eats the most hours is rarely dramatic — it’s the daily re-keying, forwarding, checking and chasing that everyone has learned to live with.
Here are the five signs we look for when we audit a business for automation, and what we usually fix first.
1. The same data is typed into more than one system
A lead comes in through the website form. Someone copies it into the CRM. Someone else adds it to a spreadsheet for the weekly report. Later it’s typed again into the invoicing tool.
Every re-key is time, and every re-key is a chance for a typo that becomes a wrong invoice or a lost lead. If data moves between your systems by hand, that is the single highest-value thing to automate. Connecting website → CRM → billing is usually a few days of work and it pays back immediately.
2. Customers wait on manual steps
“We’ll send that over once the team gets to it.” If a quote, a confirmation, a booking or an onboarding email depends on a person remembering to do it, there’s a delay in it — and your competitors’ delay might be zero.
Response time is one of the strongest predictors of whether a lead converts. Automating the first touch (acknowledge, assign, follow up) doesn’t replace the human conversation; it makes sure the conversation starts.
3. The weekly report is assembled by hand
Someone spends Friday afternoon pulling numbers from four tools into a spreadsheet, formatting it and emailing it to the team. By Monday it’s out of date.
If your reporting is a ritual rather than a dashboard, you’re paying a skilled person to be a very slow integration. Automated reporting — pulling live data into one view — removes the ritual and, more importantly, means decisions are made on current numbers.
4. Your tools “don’t talk to each other”
This is the phrase we hear most often. The CRM doesn’t know about the invoice. The support desk doesn’t know the customer’s plan. The warehouse doesn’t know the order changed.
Every one of these gaps gets bridged by a human — a Slack message, a phone call, a sticky note. Integration work closes the gaps so the systems share what they know, and the humans deal with exceptions instead of routine.
5. You’ve hired to keep up with admin, not with demand
The clearest sign of all. If the last role you added exists mostly to move information between systems, you have an automation opportunity worth at least one salary a year. The person is usually relieved — nobody enjoys re-keying.
What to automate first
Don’t start with the most complex workflow. Start with the one that is:
- frequent — happens daily, not monthly;
- boring — follows the same steps every time;
- low-risk — a mistake is annoying, not catastrophic;
- measurable — you can count the hours it saves.
Lead intake is the classic first win: form submission → CRM record → assignment → acknowledgement email → task for follow-up. It’s visible, it’s fast to build, and it gives the team confidence to automate the next thing.
The mistakes that make automation untrustworthy
Automation fails when nobody notices it failed. The difference between automation people rely on and automation people route around comes down to three things:
- Fail loudly. If an API is down or a record is missing a field, someone should get a message — not discover it three weeks later.
- Log everything. “What happened to the lead from Tuesday?” should be answerable in ten seconds.
- Keep a human in the loop for judgment calls. Automate the routing and the paperwork; let people handle the exceptions and the relationships.
Tools or custom code?
Both, usually. No-code platforms like Make, n8n and Zapier are excellent for simple, low-volume flows and let your team see and tweak them. Custom services make sense for high volume, complex logic, sensitive data, or when a flow is critical enough that you want it tested and monitored like real software. We pick per workflow, not per project.
A quick self-assessment
Ask three people in your team: “What’s the most repetitive thing you did this week?” If the answers involve moving information between systems, you’re ready. Tell us what they said and we’ll map out where the hours are going and what it would take to get them back.