What a systems audit actually looks at
Ask most teams what a systems audit covers and they describe a software review: is the CRM configured correctly, is the automation platform set up well, are the integrations connected. That is not what finds the leak. A software review checks whether the pieces work. An audit checks whether the pieces work together, for the deals that are actually moving through them this month.
The difference matters because most revenue loss does not live inside a single tool. It lives in the gaps between them, and a tool-by-tool review cannot see a gap.
What actually gets traced
Ten to twenty real deals, start to finish. Not a process diagram, the reality: pick recent deals (won, lost, and still open) and walk each one from first touch to its current state. Where was the lead captured? Who saw it first, and how long after it arrived? Which stage changes happened on time, and which ones happened three weeks late because someone remembered to update the record?
Every hand-off, named. A lead moves from a form to marketing, from marketing to sales, from a first call to a proposal. Each of those is a hand-off with an owner, a system of record, and a maximum acceptable delay. An audit writes down what actually happens at each hand-off, not what the org chart says should happen. Most leaks are sitting in a hand-off nobody assigned.
What the data can and cannot answer. Can the team say, without guessing, which channel produced the deals that closed at the best margin? Can a manager see which stage a deal has been stuck in the longest, and for how long? If the honest answer is “not without exporting to a spreadsheet and eyeballing it,” the systems are recording activity, not producing decisions.
Where the record and reality disagree. Pull the current stage of each deal from the system, then ask the salesperson what stage it is really in. When those two answers do not match, the CRM has stopped being a shared source of truth and become a formality someone updates before a meeting. An audit counts how often that mismatch shows up, because the count is a better predictor of pipeline accuracy than any dashboard.
Why this differs from a health check
A health check asks whether the software is configured well. An audit asks whether a real deal, followed from first touch to close, ever falls through a gap that nobody owns.
Those are different questions with different answers. A CRM can be perfectly configured, every field validated, every automation rule firing correctly, and still lose deals at the one hand-off where ownership was never assigned. Software review tools would call that system healthy. Tracing an actual deal through it would not.
That is also why an audit has to start with real deals rather than a feature checklist. A checklist tells you what the system can do. Tracing a deal tells you what the system actually did, this week, for a customer who was waiting on a reply.
If a systems audit sounds like the missing step before your next CRM decision, whether that is a first build, a rescue, or a rebuild, that is exactly the work our CRM implementation service starts with.