On paper the CRM is fine. There are no error banners or failed syncs, and someone still opens the pipeline dashboard in the weekly meeting. The trouble only shows when you follow individual records.
A demo request comes in from a company that is already a customer. The form workflow sets it to “Lead”, the routing rule sends it to a new-business rep, and the account manager hears about it two weeks later from the client. Elsewhere in the same CRM, a segment called “Active customers” includes everyone who bought in the last three years, so the renewal campaign goes to people who churned in 2024. The pipeline report counts deals in a stage that sales stopped using in the spring.
None of these show up as errors. They show up as missed follow-up, unreliable segments, automation that fires at the wrong moment, reporting that leadership quietly ignores, and customers sitting in the wrong state. A CRM audit traces each of those symptoms back to its cause.
What does a CRM audit include?
A CRM audit reviews how your data, lifecycle stages, workflows, integrations and reporting work together, and whether they still match how your business sells and serves customers. It is not a settings checklist. The useful questions are about connections: which field drives which workflow, which event moves a contact between states, which report depends on a property that three different processes overwrite.
The scope depends on what you run. A B2B team on HubSpot will get more attention on lifecycle stages, lead status, deal pipelines and routing. An ecommerce brand on Klaviyo will get more on events coming from the store, segment definitions, flow filters and suppression. Most audits cover both a CRM and at least one connected marketing or integration platform.
If you’d rather start on your own, our guide on how to audit your CRM walks through the basics.
Who usually asks for one
Audits tend to come at turning points. The most common ones we see:
- You inherited the system. A previous admin, agency or founder built it and left no documentation behind.
- You’re about to invest. Before paying for a large implementation or migration, you want to know what is worth keeping.
- The numbers don’t reconcile. The pipeline total in the board deck and the one on the CRM dashboard are different, and the explanations don’t agree either.
- Growth outpaced the setup. New products, regions or teams were bolted on, and the original structure no longer fits.
- You’re an agency with a client portal that needs an independent review. We also deliver audits white-label through our agency partnership.
Warning signs worth taking seriously
What we review
Six areas, inspected together, because most real problems sit where two of them meet.
Data
Record structure, required and unused properties, duplicates, field ownership, naming, how values get set (form, import, integration, workflow, manual edit) and whether one value is being overwritten by several sources.
Lifecycle
How states are defined and who agrees on those definitions. Whether contacts can move backward, what triggers each change, and whether stages, lead statuses and deal stages are doing separate jobs or overlapping ones.
Automation
A full inventory of workflows or flows: triggers, enrollment criteria, re-enrollment, suppression, conflicts, dead branches, and automation still running for campaigns or products that ended.
Integrations
Which systems write to the CRM, which events and fields actually arrive, sync direction and frequency, error handling, and anything glued together with Zapier, Make or n8n that no one monitors.
Reporting
Whether core reports answer the questions leadership asks, which properties they depend on, and whether those properties can be trusted.
Governance
User permissions, ownership of properties and workflows, change control, documentation, and what happens when someone leaves.
What you receive
The output is written for two audiences: the person who signs off budget and the person who will do the work.
- Executive summary. A short, plain-language read of the system’s condition and the few issues that matter most.
- Current-state findings. What we found in each of the six areas, with evidence.
- Lifecycle map. How contacts and customers actually move through states today, including the paths nobody designed.
- Gap register. Every issue logged with its impact, cause, affected records or workflows, and effort to fix.
- Workflow inventory. Each automation listed with purpose, trigger, status and a keep, fix, merge or retire recommendation.
- System requirements. What the system needs to know and do to support your process, written so any competent admin can build from it.
- Priority roadmap. The order to fix things, grouped into quick corrections, structural changes and longer projects.
- Implementation recommendations. How to approach the fixes on your platform, including what to leave alone.
You own all of it. Some clients take the roadmap to their own team. Some hire us to do part of the work. Both are fine.
Want a clear picture before you spend more on your CRM?
Share your platform, rough database size and what isn't working. We'll come back with a fixed audit scope and price.
How the audit runs
Intake and scoping call
We talk through your business model, sales or purchase process, the systems involved and what prompted the audit. You leave with a fixed scope and price.
Access and stakeholder conversations
You grant access to the CRM and connected platforms, ideally with view-only permissions where the platform supports them. We speak briefly with the people who use the system daily, because they know where it hurts.
Inspection
We review configuration, sample records, trace a handful of real contacts through their history, and map each workflow against the data it reads and writes.
Findings and gap register
Issues are logged, grouped and rated. This is where symptoms get linked to causes, so you don’t fix the same problem in four places.
Roadmap walkthrough
We present the findings live, answer questions and agree the order of fixes. The written report follows, and you can come back with questions after you’ve read it.
Most audits take two to four weeks from access to walkthrough. The main variables are the number of connected systems and how quickly stakeholders are available.
Pricing
CRM audits start from $1,500. That covers a single CRM with a moderate number of workflows and a small set of integrations.
Scope grows with:
- the number of platforms in the review (a CRM plus a marketing platform plus a store is three systems, not one);
- database size and how many record types and pipelines are in use;
- the volume of workflows or flows to inventory;
- integration complexity, especially custom or middleware connections;
- how many teams and regions rely on the system.
You get a fixed quote after the scoping call, before any work starts. Full starting prices for other services are on the pricing page.
What an audit is not
We don’t make changes inside your system during the audit. Fixing things mid-review hides evidence and blurs accountability. If we find something actively causing harm, such as a workflow emailing unsubscribed contacts, we flag it the same day so your team can switch it off.
It also isn’t a pitch for a rebuild. Plenty of audits conclude that the structure is sound and a handful of targeted fixes will do.
How is this different from the free CRM Health Check?
The CRM Health Check is a self-assessment based on your answers. It’s a good way to see which areas may deserve attention. An audit looks at the live system, the records and the workflows themselves, which is where the causes usually turn out to be.
Which platforms do you audit?
HubSpot and Klaviyo are where we spend most of our time. We also audit ActiveCampaign, Zoho, Mailchimp, GoHighLevel and the other platforms listed on our platforms page, along with Zapier, Make and n8n connections around them.
What access do you need?
User access to the CRM and any connected marketing or integration platforms. Where the platform allows restricted or view-only roles, we use them. We don’t need billing access and won’t ask for passwords to be shared by email. See our security page for how we handle access and data.
Will you fix the problems you find?
Not during the audit itself. Afterward, you can implement the roadmap internally, with another partner, or with us through CRM implementation or ongoing optimization. The audit is useful on its own either way.
How often should a CRM be audited?
There’s no fixed rule. A full audit makes sense before major changes, after a period of fast growth, or when trust in the data has slipped. Teams with an active optimization engagement get lighter, rolling reviews instead.
We only set up our CRM a year ago. Is it too early?
Often it’s the best time. First-year systems are small enough to correct cheaply, and the shortcuts taken during launch haven’t yet spread into every workflow.