HubSpot marketing automation.
Workflows built to a model, not to a whim. Nurture, drip campaigns, lead routing, lifecycle transitions and internal alerts. Easy to build one at a time and, built that way, guaranteed to be conflicting with each other within a year.
Two hundred workflows. Nobody knows what fires.
Each one was reasonable when it was built. Together they are an undocumented system where three workflows write to the same property, two enrol the same contact in competing sequences, and one has been erroring since a property was renamed in April.
Three workflows. One property.
Automation — the collisionAutomation that stays readable.
One property, one writer
Each property has exactly one thing that sets it. The most boring rule in the discipline and the one that prevents the most damage.
Enrolment and suppression designed together
Who enters, who is excluded, and what happens when someone qualifies for two things at once. Suppression is the half nobody builds and the half that causes complaints.
Nurture that reacts to behaviour
Branching on what someone actually did rather than a fixed sequence of five emails on a timer. The difference between a programme and a countdown.
Routing with a clock on it
Assignment by territory, segment or round robin with an SLA and an escalation, because speed to first contact is the variable that converts inbound.
Naming and documentation
A convention, a description on every workflow, and a named owner. This is what makes the system maintainable by whoever arrives next.
Monitoring for silent failure
Workflows fail quietly when a property changes or an integration stops. Alerting on enrolment anomalies catches it in days rather than at the quarterly review.
Audit, architect, build, hand over.
Audit
The portal read end to end — objects, properties, automation, permissions, integrations and the reports leadership actually opens.
Architect
The model written down before it is built: objects, lifecycle, ownership and the definitions every report has to agree on.
Build
Configuration, automation and integration built to that model, in a sequence that leaves the team working throughout.
Hand over
Documentation, enablement for the people who run it daily, and a period operating alongside your team until it is genuinely theirs.
Automating a process nobody agreed.
Automation makes a process faster and more consistent. If the process was never defined, it makes an undefined process faster and more consistently wrong, at a volume that makes it much harder to unpick. Define first. Then automate.
What people ask before they commit.
We have hundreds of workflows. Where do we start?
An inventory: what is active, what enrolled anyone this quarter, and what writes to properties your reports depend on. Usually a large share can be retired outright, which makes the rest comprehensible.
How many workflows should we have?
Fewer than you do. Most portals have several workflows doing variations of one job, which consolidate once there is a shared data model behind them.
Can workflows handle our lead routing rules?
Usually yes, including territory, round robin and capacity. Genuinely complex routing sometimes wants a custom-coded action, which is still inside HubSpot and has no per-task cost.
What about AI in workflows?
Useful for summarisation, drafting and classification where a human reviews the output. Not useful as a substitute for a model that was never defined, which is what it is most often asked to be.
How long does a rebuild take?
Three to eight weeks including the audit. The audit is the part that determines whether the rebuild is small or large.
Where people go from here.
Automation somebody can read.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.