This weekend is Father’s Day, and I was thinking about something I’ve learned watching kids practice sports.

You cannot ask for speed before they understand the drill.

If the footwork is sloppy, telling them to go faster just creates sloppier reps. If they don’t understand where to move next, more intensity doesn’t help. It just makes the confusion happen faster.

Business sorta works the same way.

A lot of companies are adding automation, AI, workflows, and RevOps tooling hoping it will create more leverage. And… honestly… sometimes it does.

But if the process underneath it is messy, the new tool does not fix the mess. It exposes it. That is the part a lot of teams don’t want to admit.

Here are the excuses I typically hear before a fractional engagement starts.

Sometimes the software really is limited. But a lot of the time, the real issue is much simpler. Nobody mapped the process clearly enough before trying to speed it up.

Where I have seen this go wrong most often is when companies automate before they define ownership.

If those questions are fuzzy, automation does not create clarity. It creates faster confusion. And can potentially erode trust with your team (and clients).

I talked about this in one of my recent podcast interviews. If your process is broken, AI and automation are not going to magically solve it for you. They are just going to reveal the weak spots faster.

That has been true in every company I have seen try to scale with systems.

At one point in a previous in-house role, we were generating a lot of leads with a very lean sales team. The temptation would have been to just automate everything and hope the volume worked itself out.

But that would have been the wrong move.

What we actually had to do first was figure out the journey. We had to understand which leads were worth immediate attention, which ones needed a different follow-up path, and where people were dropping off. We had to look at how messages were being sent, who owned the next move, what counted as a hand-raiser, and how long something could sit before it needed a new action.

Then we built the workflows. That order is more important than you think.

Because once the process was clear, automation became useful. Automated emails from the right inboxes created hand-raisers. Tasks inside the CRM told reps where to focus. Recycled leads created new conversations instead of dying in the system. And the sales team spent more time with people showing real intent instead of treating every contact the same way.

That is the difference.

Good automation is not about removing thought. It is about protecting good process and making it easier to repeat.

The biggest mistake is trying to automate a stage the team does not really understand.

They know they want faster follow-up. They know they want more efficiency. They know they want fewer leads slipping through the cracks.

But they have not actually documented what is supposed to happen. So they build a workflow anyway.

Now the wrong email goes out…

… Or the right email goes out at the wrong time.

… Or sales gets notified too late.

… Or marketing keeps nurturing something sales is already working.

… Or a lead gets recycled with no context.

And then the team says the automation is broken.

Ummm… No. It’s NOT broken. The process was broken before the automation ever touched it.

If I were cleaning this up inside your company right now, I would start with 4 things.

Who owns each stage of the journey? Not in theory. In practice.

If nobody can clearly answer who owns first response, qualification, nurture, recycle, and stage movement, the workflow is going to create friction fast.

What exactly has to happen before something moves forward? If your stage exits are vague, you will automate guesses.

And guesses multiplied by software usually create bad data and bad experiences.

What message goes out first, second, and third? And why?

This is where a lot of lifecycle marketing falls apart. Teams set up drips without thinking hard enough about timing, intent, or buyer context.

The message sequence should reflect the journey, not just the calendar.

What happens when someone does not behave the way the workflow expects?

They reply late. They click but do not book. They ignore every email and then come back two months later.

If the process only works in the ideal scenario, it is not much of a process.

Automation should not be the strategy. It should be the force multiplier.

That means your first job is to map what already works.

Then build around that.

Not around the software demo. Not around whatever AI feature everyone is excited about this week. Around the real buying journey inside your business.

That is what I keep coming back to.

The teams that get the most out of AI and automation are usually not the ones using the fanciest tools. They are the ones with the clearest process.

Once that is true, the software starts to help. Until then, it just makes the mess louder.

If your automation feels clunky right now, I would not start by replacing the platform.

I would start by asking whether the process underneath it is actually clear enough to automate.

Want help building this strategy out? Just reply to this email to schedule a no-obligation consultation. It’s a great chance to see if we’re a good fit for each other and—more importantly—to see if your current strategy is sustainable.

See you next week.

Javy

P.S. — Is there a topic or strategy that you’d like me to unpack? Drop me a line. Let me know what you’re thinking of. And, I’ll get it queued up for an upcoming newsletter.

I recently joined Mason Duchatschek to talk about something a lot of growth-stage companies feel but do not always know how to name: operational chaos.

We got into what chaos actually looks like behind the scenes, why the first step is not to fix everything at once, and how better structure creates room for better creativity instead of killing it. We also talked about finding the one bottleneck that matters most, auditing where leads are getting wasted, and why automation only helps after the underlying journey is clear.

If your team is moving fast but still feels fragmented, this one is worth your time.

Listen and watch on YouTube.

This is the right companion for this week’s newsletter because it gets into the practical side of what a lot of teams miss: automation is not about building something fancy. It is about building something clear enough, useful enough, and repeatable enough that the business can trust it.

If your workflows feel brittle, your CRM feels noisy, or your automations keep creating more cleanup work than leverage, this playbook will help you think about where to simplify, what to map first, and how to make automation support the motion instead of getting in the way of it.

Read it here