I run Axenda, a small HubSpot and RevOps consultancy. Here’s the checklist I use when reviewing an existing automation setup.

Before building anything new, I check:

- Can two workflows update the same property? If so, which one should control it?
- Does every lead have an owner and a next action?
- Do pipeline stages have clear entry and exit criteria?
- Can someone explain why a contact enrolled in a workflow?
- When replacing an old workflow, which dependencies need to be checked before switching it off?

A useful starting point is a simple inventory: workflow name, trigger, properties it changes, dependencies and person responsible.

That makes it easier to spot conflicts before adding more automation. Workflow count alone doesn’t tell you whether the system works.

How do you document dependencies in your portal? A spreadsheet, naming conventions, or something else?