Most Salesforce orgs don’t break in one go. They drift. A dashboard stops matching the finance numbers, someone starts a spreadsheet “just for now”, and a year later nobody is quite sure what the system does.
The usual response is to add something: a new app, a new field, a new automation. On top of a drifting org, that tends to make things worse. These are the seven signs we see most often that it’s time to look underneath first.
Key takeaways
- Most of these signs point to data, ownership and documentation, not to missing features.
- Automations and integrations that nobody owns are the most common hidden risk.
- “Nobody touched it” rarely means nothing changed: releases and connected systems move on.
- None of these automatically means you need a new CRM.
- A few checks you can run yourself show where to look first.
1. Your dashboards stopped making sense
If leadership asks why the pipeline dashboard doesn’t match the forecast, and the honest answer is “it changed at some point”, that’s the first sign.
The causes are usually mundane: a field that was reused for something else, a filter on a value that no longer exists, a process change that never reached the report. A common finding in our audits is the reverse problem: the implementation is fine, but nobody built the management dashboards, so there is no way to measure what the system is for.
2. Someone keeps correcting a report by hand
When a report is exported every week and fixed in Excel before anyone sees it, the report isn’t the problem. The data behind it is.
Typical culprits are missing values, free-text fields where a picklist belongs, and two different ways of recording the same thing. If your team needs a spreadsheet to explain what’s happening in your CRM, it’s worth asking what’s missing from the CRM.
3. The same customer appears more than once
Duplicates creep in through imports, integrations that create new records instead of matching existing ones, and missing duplicate rules.
They matter more than they look. History is split across two records, the same person gets two emails, and any AI feature that summarises a customer will summarise half of them.
4. Automations nobody owns, or nobody knows about
Every automation made sense to whoever built it. The risk is the total: when nobody can say what happens to a record when its status changes, every change becomes a gamble.
In one org we reviewed, the team knew of four flows. There were 287 running. Several people had system administrator rights, some flows had been generated with AI around existing Apex code, and nobody was the CRM owner. Nothing was wrong with any single piece. Together, they were unmanageable.
If you’re planning to let AI build or change automations in your org, this is the sign to take most seriously. AI makes it faster to add automation, not to keep track of it.
5. Work happens outside the system
Side spreadsheets, quotes sent as email attachments, customer notes in a chat channel. Each one is a small vote of no confidence in the CRM.
People rarely do this out of habit alone. Usually the system makes the task slower than the workaround, or doesn’t support it at all. Finding out which is half of the fix.
Recognise two or three of these?
Start with a free 20-minute health check. Bring the three things that annoy you most in your CRM.
6. “Nobody touched it, and it still broke”
This is one of the most common things we hear. It’s rarely true that nothing changed; the change just happened somewhere else.
Salesforce ships three major releases a year, and features get retired along the way. Connected systems update on their own schedule. So a document generator starts producing odd output, or the Outlook sync starts attaching emails to the wrong opportunities. These problems usually trace back to a retired feature, a changed integration or a setting nobody wrote down.
7. Licences nobody is sure you need
Licence packages are often put together by an internal decision, without anyone who knows the options well. The result is paying for capabilities nobody uses, or missing ones you need.
We’ve seen companies on a consumption-based licence pay several times what their usage required, and find it hard to scale back. Renewals have their own logic too: reducing the number of licences doesn’t always make the package cheaper. It’s worth reviewing well before the renewal date, not the week before.
None of these means you need a new CRM
Usually the opposite. Most orgs showing these signs have a sound base that needs clearing up, an owner and some documentation. Replacing Salesforce to escape a mess tends to rebuild the same mess somewhere else, with a migration on top.
A long list of findings can also become one more thing nobody has time for. What helps is knowing which two or three problems cost you the most, and fixing those first.
Five checks you can do yourself this week
You don’t need a partner to get a first impression. An administrator can do these in an afternoon:
- Count the active flows. In Setup, open Flows and filter for active ones. Compare the number with how many your team thinks exist.
- List your system administrators. Check which users have the System Administrator profile, and whether each of them still needs it.
- Look for duplicates. Run a report on contacts grouped by email address and see how many appear more than once.
- Compare licences with active users. Company Information in Setup shows the licences you have; the user list shows who logged in recently.
- Ask three people about their spreadsheets. Which file do they keep next to Salesforce, and why?
If the answers surprise you, that’s useful in itself. It tells you where to look first, and it makes any conversation with a partner shorter.
What a CRM audit looks at
A CRM audit checks whether your org was built well, whether it still fits how you work, and whether it’s ready for what’s next, including AI. It tests your business requirements and includes a full technical review. Depending on the scope, it covers:
- data security, sharing and visibility;
- the data model and data quality;
- licence level and how much of it is used;
- automations, code and Agentforce agents;
- integrations, and which system is the master for what;
- AppExchange packages;
- release compatibility and retired features;
- the development process and environments.
We agree the scope before we start, tell you straight away if something extra comes up, and you can stop after any phase.
Frequently asked questions
How long does a Salesforce audit take?
It depends on the size of the org and the scope we agree. We fix the scope before we start, flag anything extra as soon as we see it, and you can stop after any phase.
Is an audit the same as a health check?
No. The health check is a free 20-minute conversation that gives you an honest first view. An audit is a structured review of your requirements and the technical setup, with documentation and recommendations.
Do you audit CRMs other than Salesforce?
Yes. An audit is always about an existing CRM, and we also review HubSpot and MiniCRM setups and the systems around them.
What happens after the audit?
You get documentation of what we found and what’s worth fixing, in order of impact. Then you decide: fix it with your own team, with us, or leave it. Refactoring or rebuilding is a separate step.
