- crm
- automation
- hubspot
- zoho
Your CRM Already Has Automation Built In. You're Probably Paying for a Second Tool Anyway
Before you add Zapier or Make on top of your CRM, check what Zoho, HubSpot, or Salesforce can already do natively. Here's how to decide, with a worked cost example.
Kamal Farooqi5 min read
The Tool You Already Pay For
A common pattern: a small business buys a CRM, then adds a connector tool to automate things around it, then adds another subscription for email sequences. Meanwhile the CRM has a workflow engine sitting unused in the settings menu.
This isn't a reason to avoid external tools. We use Make and n8n regularly. But the cheapest, most reliable automation is often the one that lives inside the system where the data already is. Fewer moving parts means fewer things that break at 2 a.m.
Before you build anything outside your CRM, spend an hour checking what it can already do.
What Most CRMs Can Do Natively
The names differ by platform, and some features depend on your plan tier, so check yours. The categories are broadly the same:
- Zoho CRM: workflow rules, assignment rules, Blueprint (enforced stage-by-stage process), macros, and scheduled actions.
- HubSpot: workflows, sequences, lead rotation, and task automation. The more advanced workflow features sit on the Professional tier and above.
- Salesforce: Flow, assignment rules, and approval processes.
With these you can usually do the following without any outside tool:
- Assign a new lead to a rep by territory, source, or round-robin.
- Create a follow-up task when a deal moves stage.
- Send an internal alert when a deal sits idle for a set number of days.
- Update a field when another field changes.
- Send a templated email when a contact fills in a form.
- Require certain fields before a deal can move forward.
That list covers a large share of what small teams ask us to automate.
Native vs External: A Quick Decision Table
| Situation | Use the CRM's own automation | Use an external tool |
|---|---|---|
| Action happens entirely inside the CRM | Yes | No |
| Needs data from one other app (e.g. a form tool) | Often, via built-in integration | If no native integration exists |
| Chains three or more apps together | Rarely | Yes |
| Needs custom logic, loops, or data transformation | Limited | Yes |
| Non-technical staff must edit the rules | Yes, usually | Depends on the tool |
| You want one place to debug when something fails | Yes | Harder |
The rule we use: if the trigger and the result both happen in the CRM, build it in the CRM. Reach outside only when you need to cross systems or do something the CRM can't express.
A Worked Example
Take a six-person sales team. Each rep spends about 25 minutes a day on repetitive CRM chores: creating follow-up tasks, updating stages, logging the same notes, and chasing deals that went quiet.
- 25 minutes x 6 reps = 150 minutes a day, or 2.5 hours
- 2.5 hours x 21 working days = about 52 hours a month
- At a loaded cost of $35 an hour, that's roughly $1,800 a month
Say native automation removes two-thirds of that. That's about 35 hours, or $1,200 a month back.
Now the cost side. Setting up assignment rules, stage-based task creation, and stale-deal alerts inside the CRM might take 10 to 15 hours of consultant time. At $120 an hour, call it $1,200 to $1,800 once. The ongoing cost is close to zero, because the CRM subscription is already paid for.
Payback is about one to one and a half months. Doing the same through an external tool adds a monthly subscription, a second place for failures to hide, and more setup. It can still be the right call, but it needs to earn its extra cost.
Where Native Automation Falls Short
Be honest about the limits:
- Plan gating. The feature you need may sit on a tier that costs more than a connector tool would. Price it both ways before deciding.
- Clunky logic. Branching conditions and data cleanup get awkward fast in some CRMs.
- Weak error visibility. Some platforms don't tell you clearly when a workflow fails. If so, add monitoring. Silent failures are the real danger with any automation.
- Lock-in. Workflows built inside one CRM don't move with you if you switch platforms. For most small businesses that's an acceptable trade, but know you're making it.
How to Audit Your CRM in an Hour
- Open the automation or workflow section and list what's already running. Old rules that nobody remembers are common, and they sometimes conflict with new ones.
- Write down the five most repetitive things your team does in the CRM each week.
- For each one, check whether a native rule can handle it. Test with a dummy record.
- For anything that can't be done natively, note which outside apps are involved. That's your shortlist for an external build.
- Turn on failure notifications wherever the platform offers them.
Most teams finish this audit with two or three quick wins they can switch on that week, and a short, clear list of what actually needs a bigger build.
Start Inside, Then Reach Out
The goal isn't to use the fanciest stack. It's to remove repetitive work at the lowest build cost and the lowest ongoing risk. Your CRM's built-in automation often does that better than another subscription would.
If you're not sure what your CRM can do, or whether your current setup is more complicated than it needs to be, book a free call. We'll look at what you have, tell you what can be done inside it, and give you an honest number for what's worth building.