Five Salesforce fixes that pay for themselves
Most Salesforce orgs do not need a rebuild. They need a tidy-up. After a few years of quick wins, new fields and half-finished automations, the system still runs, but it is slow to change and nobody quite trusts the numbers.
Here are five fixes we reach for first on a new engagement. None of them is glamorous, and each earns its cost back inside a quarter.
1. Remove the fields nobody fills in
Open any mature org and you will find custom fields that were added for one deal in 2021 and never touched again. They clutter the page layouts, slow the screens down and make reports harder to read.
Pull the field usage report, find the ones with almost no data, and retire them. Start with the page layouts so the screens get simpler straight away, then archive the fields once you are sure nothing depends on them.
2. Untangle automations that fight each other
A workflow rule, a process and a flow all updating the same record is the classic cause of "Salesforce is slow today". They fire in an order no one planned and sometimes undo each other's work.
Map what touches each key object, then move the logic into a single flow per object. The record saves faster, the behaviour becomes predictable, and the next person can actually read how it works.
3. Fix the reports people do not trust
A report nobody trusts usually means nobody owns the numbers.
Agree one definition for the handful of figures the business actually runs on: pipeline, won revenue, active customers. Build those as shared reports, lock the filters, and make them the only version anyone links to. Trust in the numbers is worth more than any new dashboard.
4. Tighten permissions before you add more users
Permissions drift. People change roles, keep their old access, and slowly everyone can see and edit everything. That is a security risk and an audit headache.
Review profiles and permission sets against what each team genuinely needs. Move to permission sets so access is additive and easier to reason about, then take the surprises away one by one.
5. Write down how the org is meant to work
The most expensive thing in most orgs is the knowledge that lives in one person's head. When they are on leave or they move on, every change becomes a guess.
Keep a short, current document covering the objects, the automations and the key reports. What matters is that it exists and that the next person knows where to find it.
Where to start
Pick the one that hurts most this month. A clean org is a habit, not a one-off project. Fix one thing, let people feel the difference, and the case for the next fix makes itself.