I've spent twelve years building WordPress sites, integrating CRMs, and lately, setting up AI automation for clients. The conversation around automation always seems to land in the same place: how many jobs will this replace?
That's the wrong question. Or at least, it's an incomplete one.
The best automation I've built doesn't eliminate people. It eliminates the repetitive friction that keeps people from doing their actual job. There's a difference.
What actually happens when you automate well
Last year I set up a GoHighLevel workflow for a coaching client who was spending about 15 hours a week on intake forms, calendar coordination, and follow up emails. Standard stuff. We built a system that handled form submissions, routed them based on service type, booked calendar slots, and sent contextual follow ups.
She still reviews every intake. She still has the first conversation. But now she's doing it with context already in front of her, and she's spending those 15 hours on actual coaching calls instead of administrative ping pong.
Revenue went up 40% in four months. Not because we added AI magic, but because she had time to take on more clients and design a new program she'd been thinking about for two years.
That's what I mean. Automation bought her time to think.
The parts that don't automate well
Here's what I've learned doesn't work: trying to automate judgement calls.
I tried building a HubSpot workflow once that would automatically qualify leads based on form responses and company size. It worked technically. The logic was sound. But it kept mis-categorizing prospects because it couldn't pick up on tone or context in the free text fields.
We ended up keeping the data collection automated but putting a human review step before any lead got routed to sales. That 90 second review saved hours of wasted sales calls and prevented us from dismissing good prospects that didn't fit the rigid criteria.
Decisions need context. Relationships need presence. You can automate the scaffolding around these things, but not the things themselves.
What I automate now and why
These days, most of my AI and CRM automation work falls into a few categories:
- Data entry and transfer between systems (WordPress to Keap, form submissions to HubSpot, Zapier chains that move information so humans don't have to)
- Scheduling and calendar management (because calendar tetris is nobody's idea of meaningful work)
- First pass content drafts (I've got Claude helping with documentation and email templates, but everything gets edited by a human who knows the audience)
- Report generation (pulling CRM data into readable formats weekly instead of making someone build spreadsheets)
Notice what's not on that list: anything that requires reading a room, understanding subtext, making a tradeoff between competing priorities, or building trust.
The real ROI nobody talks about
When I talk to clients about automation, they want to know how much time they'll save. Fair question. But the better question is: what will you do with that time?
I've seen teams automate their reporting and use the freed up hours to actually analyze what the reports mean. I've seen solopreneurs automate their onboarding and finally build the referral program they never had bandwidth for.
The ROI isn't just efficiency. It's optionality. It's having space to notice patterns, try new approaches, deepen client relationships, or just think without your todo list screaming at you.
Automation that just makes people work faster until they burn out isn't automation. It's a treadmill with better software.
Practical takeaway
Before you automate something, ask what you'll do with the time you get back. If the answer is "take on even more of the same work," you're optimizing for throughput instead of growth. Automate the repetitive parts so you have room for the work that requires your brain, not just your hands.
