top of page

Signs You Should Audit Your Salesforce Org Before You Sign Another Contract

  • Writer: Dan
    Dan
  • Jul 15
  • 2 min read

There's a particular moment that comes up again and again with clients: they're about to sign off on a new phase of Salesforce work, a new integration, a new module, a bigger licence commitment, and something feels off about doing it on top of what's already there. Usually that instinct is right.


The pattern I keep seeing

New work gets scoped against what the org is supposed to do, not what it actually does. Nobody goes back and checks whether the foundations can carry the extra weight, because that's not what anyone's being paid to look at. So the new project gets delivered, and it inherits every quirk and workaround that was already baked into the org, plus a few new ones of its own.

A few signs it's worth pausing before you sign anything new:

  • Reports that different teams don't trust, or that require a manual reconciliation before anyone will present them.

  • Automations that were built by more than one person or partner over time, with nobody fully sure what fires on what.

  • A data model that's been extended sideways to fit processes it wasn't originally designed for.

  • User adoption that's noticeably lower in one team than another, without a clear reason why.

  • Any answer to "why does it work this way" that starts with "historically..."


Why this matters more before a new contract than after

Once a new phase of work is signed and underway, any existing weaknesses become the new project's problem too, and untangling them gets more expensive with every layer added on top. An audit before you commit costs a fraction of what it costs to discover the same issues six months into a project that's now built on them.


It's also a useful gate on the proposal itself. A partner scoping new work against a genuinely understood foundation will usually price and plan it differently, sometimes smaller, sometimes bigger, but always more accurately, than one scoping against an org they haven't actually looked inside.


You don't need to audit every year. But before you add anything substantial on top of what you've already built, it's worth twenty minutes of honest looking to make sure you're building on solid ground.


If you'd like to get some independent advice to get your Salesforce org working optimaly then reach out and let's have a conversation

 
 
 

Recent Posts

See All
What an Honest Salesforce Audit Costs You to Skip

The objection to commissioning a Salesforce audit is almost always the same: it's an added cost, on top of a system you've already paid to build, to tell you things you'd rather not know. That's a fai

 
 
 

Comments


© 2025 Dan Edwards Consultant

Hours of operation 

As clients need me, and deadlines dictate

Availability

Based in South Africa

Supporting Clients Globally

bottom of page