A prospect downloads a pricing guide at 2:10 pm and signs up for the newsletter at 2:25 pm. By the next evening they have received five emails from three different workflows: a sales nurture triggered by the pricing download, a newsletter welcome series, and a “content follow-up” built for a 2023 ebook launch whose trigger was set to any form submission. The person who built that last one left in 2024.
Each of those workflows does what it was built to do. The problem only appears when you look at them together, which rarely happens, because workflows get added one campaign at a time, by different people, over years, and looking at the whole set isn’t anyone’s job. A workflow audit makes it someone’s job for a few weeks.
How is a workflow audit different from a CRM audit?
A workflow audit looks only at the automation layer, in depth. A CRM audit looks at the whole system: data structure, lifecycle stages, integrations, reporting and governance, with automation as one part of it.
The difference is depth versus breadth. In a full CRM audit we inventory workflows and flag the obvious conflicts, but we don’t open every branch of every workflow and test its edge cases. In a workflow audit we do exactly that, and we spend less time on property architecture or reporting design except where a workflow depends on them.
A workflow audit is usually the better choice when:
- you already know the trouble is automation, such as duplicate emails, stages jumping around, tasks created twice;
- you’ve inherited a portal or account from an agency or a former admin and need to know what’s running before you touch it;
- you’re about to migrate or rebuild and want to know which logic is worth carrying over;
- the workflow count has grown to the point where the team is afraid to switch anything off.
If the symptoms are broader, like reports the leadership team argues about or lifecycle stages that mean different things to different teams, start with the full audit. The causes are rarely only in the workflows.
What we check inside each workflow
Every workflow answers the same handful of questions, whether it’s a HubSpot workflow, a Klaviyo flow, an ActiveCampaign automation, a Zoho workflow rule or a Salesforce Flow. We go through them one by one.
Triggers
What actually starts it. We look for triggers that are broader than the workflow’s purpose (“any form”, “any property change to lifecycle stage”), triggers based on fields that several processes write to, and triggers that depend on an integration event that may no longer arrive.
Conditions and branches
Whether the if/then logic covers the real data. A branch that splits on country will quietly send everyone with a blank or misspelled country down the “else” path. We check what the else path does and how many records actually land there.
Delays
Fixed delays that assumed a date that has since moved. Business-hours delays that ignore time zones. “Wait 3 days” steps that hold a contact in place long after their situation has changed, so the next email arrives after they’ve already bought, booked or canceled.
Re-entry
Whether a record can go through the workflow more than once, and whether it should. Re-enrollment that is switched on without a reason sends welcome emails to people who joined years ago. Re-enrollment that is switched off when it should be on means a returning customer never gets the onboarding steps a second time.
Exclusions and exits
Who should never be enrolled, and what takes someone out early. Customers in a prospect nurture. Unsubscribed contacts still getting internal-notification-driven sales emails. Leads who booked a meeting still receiving “Did you get a chance to look?” on day six. In HubSpot this means checking suppression lists and unenrollment triggers; in Klaviyo it means flow filters and how they interact with profile properties that change mid-flow.
What we look for across the whole set
Individual workflows can be correct and still cause harm together. This is where most of the findings come from.
Ownership and reporting
Two questions sit around the workflows rather than inside them.
Who owns each one? For every workflow we record who built it, who last edited it, and who should be accountable for it now. Often there’s no real answer, which explains why no one is comfortable turning anything off. We propose an owner per workflow, or per group, and a simple rule for who approves changes.
How would you know it’s working? Most workflows have no defined outcome. We note which ones have a goal or conversion you can report on, which ones could, and which ones you’d only find out were broken when a customer complains. For important automation like lead assignment or deal-won handoffs, we suggest a check that would surface a failure within days rather than months.
Afraid to switch anything off?
We'll map every active workflow against the records it touches and the fields it writes, so you can retire automation with evidence instead of guesswork.
What you receive
The output is built to be used, by your team or by whoever does the fixing.
- Workflow inventory. Every active and recently paused workflow, with its object, trigger, enrollment volume, last edit, owner, what it sends and what it writes.
- Property write map. For each critical field, every workflow and integration that can change it, so collisions are visible on one page.
- Conflict and risk register. Each issue described with the records affected, the likely cause and the effort to fix. Anything causing active harm is marked for immediate action.
- Keep, merge, rebuild or retire. A recommendation for every workflow, with the reasoning.
- Test plan for the risky changes. Which test records to run, which branches to check, and what to watch after the change goes live.
You can use our workflow QA checklist to keep new automation from drifting back into the same state.
How the audit runs
Context and access
A short call about how leads and customers are supposed to move through the system, then read-only or limited access to the platform. We ask which workflows people are already nervous about.
Inventory
We export or document every workflow and flow, including paused ones and automation running in connected tools that writes back into the CRM.
Trace real records
We pick contacts and deals that have been through common paths and some unusual ones, and read their history. This shows what fired, in what order, and what changed.
Map collisions and gaps
Workflows are grouped by the records and fields they touch. Overlaps, dead ends and missing steps become visible once they sit side by side.
Review session
We walk through findings with whoever owns the system, agree priorities, and hand over the inventory and register.
We don’t edit workflows during the audit. If we find something actively causing harm, for example a workflow emailing contacts who unsubscribed, we tell you the same day so your team can pause it.
Pricing and what happens next
Workflow audits are scoped by platform and the number of active workflows, and you get a fixed price before we start. A system with a few dozen workflows on one platform is a smaller job than a HubSpot portal and a Klaviyo account with hundreds of automations between them and several integrations writing into both.
After the audit, some teams fix things in-house using the register. Others ask us to do the rebuild as a CRM automation project, or to keep the system tidy through CRM optimization. If the audit points to deeper problems in the data or lifecycle definitions, we’ll say so and explain whether a full CRM audit is worth it.
How many workflows is too many?
There’s no fixed number. The useful question is whether someone can explain what each workflow does and why it exists. Fifty clearly owned workflows are healthier than fifteen that only a former admin understood. Warning signs are duplicates with names like “copy”, workflows untouched for years that still enroll new records, and several workflows writing to the same field.
Do you audit Klaviyo flows and marketing automation, or only CRM workflows?
Both. Klaviyo flows, ActiveCampaign automations and similar marketing automation get the same review: triggers, filters, delays, re-entry and how they overlap with each other and with campaigns. If your CRM and email platform both send to the same people, we look at them together.
Will the audit change anything in our account?
No. We work with read-only or limited access and document what we find. Changes happen afterward, once you’ve agreed what to fix, so nothing is lost and every change can be traced.
What level of access does the review need?
Enough to view workflow configuration, enrollment history and record timelines. On most platforms a restricted user with view permissions is sufficient. We’ll tell you exactly what’s required for your platform before we start.
We’re migrating to a new CRM. Is a workflow audit still worth doing?
Usually yes, and before the migration rather than after. It tells you which logic is still needed, which can be dropped, and which hidden rules your team relies on without realizing. That makes the new build smaller and avoids recreating old conflicts. See CRM migration for how we handle the move itself.
Will you make the fixes as well?
If you’d like. The register is written so anyone competent could act on it, though it often makes sense for us to handle the high-risk changes and test them properly. That is quoted separately once you know what needs doing.