Seven signs your Salesforce org needs an audit
Most orgs degrade quietly rather than breaking outright. These are the symptoms we see most often — and what each one usually means.
Salesforce rarely fails loudly. It degrades: a workaround here, an unused field there, until one day nobody trusts the pipeline report.
1. Nobody trusts the forecast
If leadership keeps a parallel spreadsheet, the org has already lost. Usually the cause is stage definitions that mean different things to different teams.
2. Reports are built, not reused
Hundreds of personal reports and a handful of shared dashboards is a sign that the standard reporting does not answer the real questions.
3. Data entry happens after the fact
When reps update records on a Friday afternoon to keep management happy, the system is not part of the workflow — it is overhead.
4. The admin backlog never shrinks
A permanent backlog of small changes usually means no release process, not a lack of capacity.
5. Integrations fail silently
If you find out about a failed sync from a customer complaint, monitoring was never built.
6. Custom code nobody understands
Apex written by a departed contractor, with minimum test coverage and no documentation, is technical debt with interest.
7. Adoption drops after launch
A spike at go-live followed by a slow decline is the clearest signal that training addressed features rather than the job people do.
If you recognise three or more of these, an audit will pay for itself.
Want this looked at in your own org?
We will review your setup and tell you what we would change — no charge for the first conversation.
Book a free review