How We Think About Marketing Automation Before We Build a Single Workflow

August 27, 2026
How We Think About Marketing Automation Before We Build a Single Workflow

Most marketing automation doesn't fail because the tool is wrong. It fails because someone opened the workflow builder before anyone agreed on what the automation was supposed to prove.

The pattern is familiar: a company buys HubSpot, or already has it, and the instinct is to start building. A welcome sequence here, a lead-scoring model there, a re-engagement campaign because the last one is looking stale. Six months later there are forty workflows running, nobody remembers what half of them were for, and the sales team still says marketing isn't sending them anything useful.

That's not an automation problem. That's a sequencing problem.

 

The question automation can't answer for you

Automation executes a decision. It doesn't make one.

Before any workflow gets built, three things need to already be true:

You know what a qualified lead actually looks like. Not "someone who filled out a form." A defined combination of firmographic fit and behavioral signal that your sales team has agreed, in advance, is worth their time. If that definition doesn't exist yet, a lead-scoring workflow just automates a guess.

You know what happens after the workflow fires. An automation that routes a lead to sales is only as good as what sales does next. If there's no defined follow-up process on the other end, the automation is just moving the bottleneck, not removing it.

You know what you're trying to prove, not just what you're trying to send. "We should have a nurture sequence" isn't a strategy. "New higher-ed prospects who download our enrollment funnel guide should hear from us three times over two weeks before a human follow-up" is one you can actually build, measure, and defend.

 

What this looks like in practice

Start with the decision, not the tool. Map the actual buyer journey for one specific segment. Where do people get stuck? Where does a human follow-up currently happen too late, or not at all? Automation earns its place at the exact points where a manual process is either too slow to matter or too repetitive to justify a person doing it by hand.

That's a narrower list than most companies expect. It's usually three or four high-leverage moments, not forty parallel workflows running on assumptions nobody's revisited in a year.

Once those moments are identified, the automation itself becomes the easy part. The platform matters far less than the clarity behind what it's supposed to do.

 

The maintenance problem nobody plans for

Automation isn't a one-time build. Buyer behavior changes, offers change, sales processes change, and workflows built two years ago quietly stop matching reality while still running exactly as configured. A workflow that was right when it launched can be actively working against you a year later if nobody's responsible for revisiting it.

Before building anything, it's worth deciding who owns that review, and how often it happens. An automation program without a maintenance owner degrades the same way any unmonitored system does: slowly, quietly, and in ways nobody notices until the numbers stop making sense.

 

Where this fits

Marketing automation is an execution layer on top of a strategy that already exists. It works when the segmentation, the scoring logic, and the handoff to sales are already agreed on, and it fails, expensively, when it's asked to substitute for that agreement.

If the workflows already exist but the results don't match the effort going into them, the fix is rarely a better workflow. It's usually the missing decision the workflow was built to skip.

Author Bio

Eduarda Ayres is a strategist at Stratagon, where she works across marketing, technology, and creative engagements for clients. She specializes in CRM strategy and marketing automation, connecting business goals to the systems and tactics that actually move them.