Five Signs Your Salesforce Org Needs an Audit Before You Build Anything Else

Most Salesforce problems get solved by building more. Another flow. Another dashboard. Another custom object. And most of the time, that's the wrong answer.

In my experience, organisations that keep adding to a Salesforce org that isn't working don't end up with a better system, they end up with a more complicated broken one. The underlying issues don't go away. They just get harder to find and more expensive to fix.

Before you invest in the next phase of your Salesforce journey, here are five signs that an independent audit should come first.

1. Your users don't trust the data

If your team regularly checks Salesforce and then checks somewhere else to verify what they found, you have a data integrity problem. This usually isn't a technical issue, it's a symptom of processes that don't match the system, fields that aren't being used consistently, or automation that was built for a version of the business that no longer exists.

More configuration won't fix it. Understanding why the data is wrong will.

2. Adoption is low and nobody can explain why

Low adoption is always blamed on users. Rarely is it actually a user problem. When a system doesn't reflect how people actually work, they find ways around it, and those workarounds quietly become the real process. If your Salesforce org requires people to do extra steps that don't feel useful, they won't do them. That's not resistance. That's feedback.

3. Reports and dashboards don't reflect reality

If leadership has stopped relying on Salesforce reports to make decisions, something has broken down between the data going in and the information coming out. This could be a data quality issue, a reporting design issue, or a process issue, but you need to know which one before you try to fix it.

4. Every new requirement feels harder than it should

When a simple change takes longer than expected, or when your admin consistently tells you that something "isn't possible" that sounds like it should be, you're likely carrying technical debt. Shortcuts taken during the original implementation compound over time and make every subsequent piece of work slower and riskier.

5. You're about to start the next phase of your implementation

This is the most important one. If you're planning to expand your Salesforce footprint, new modules, new integrations, more users, and you haven't independently validated that the existing foundation is sound, you're building on uncertain ground. The cheapest time to find a problem is before you build on top of it.

What an audit actually looks like

A good implementation audit isn't a box-ticking exercise. It's an honest, independent assessment of what's been built, how it's being used, and where the gaps are between what the system does and what the business needs. You should come out of it with a clear findings report and a prioritised remediation plan, not a list of things to sell you.

If any of the five signs above sound familiar, it's worth having a conversation before you commission the next phase of work. Feel free to get in touch at dan@danedwardsconsultant.com.