Your car gets a service every year whether it’s making a funny noise or not. Your Salesforce org, the system running your pipeline, your customer data and a fair chunk of your revenue, probably hasn’t had a proper inspection since the day it went live.
And here’s the uncomfortable bit: it’s not in the same condition it was on go-live day. No Salesforce org is.
Salesforce orgs don’t break. They decay.
That’s what makes this problem so easy to miss. A broken system announces itself. Pages error out, people complain, someone gets a phone call. Decay is quieter. It looks like this:
A report takes a little longer to trust, so someone rebuilds it in a spreadsheet. A field stops being useful, so the sales team starts typing the real information into the notes section. A workflow built by a contractor in 2021 keeps firing, and nobody remembers why, and everybody’s too nervous to turn it off.
None of these is a crisis. Each one is a workaround, and workarounds are how capable people cope with a system that’s drifting away from how the business actually works. The org still “works”. It just works a bit less every quarter.
The industry has a name for this: technical debt. It’s the accumulated cost of every quick fix, every unused field, every automation layered on top of an older automation. And in Salesforce it builds unusually fast, because the platform makes change so easy. You don’t need a developer to create debt in Salesforce. A few well-intentioned clicks will do it.
What silent decay actually costs
This isn’t a hypothetical. The numbers on technical debt are genuinely confronting.
In a McKinsey survey of CIOs, technology leaders reported that 10 to 20 per cent of the budget meant for new products gets diverted into fixing tech debt instead. The same CIOs estimated debt amounts to 20 to 40 per cent of the value of their entire technology estate. Think about that against what you’ve spent on Salesforce since go-live.
Forrester went as far as coining a term for it, the “Salesforce@scale dilemma”: as an org grows, every change risks breaking one of hundreds of customisations, integrations and add-ons, so every change needs longer analysis and testing, and the responsiveness that made Salesforce attractive in the first place slowly evaporates. Salesforce Ben has documented organisations forced to freeze all changes for six months or more just to get their debt under control.
And decay compounds the original adoption problem. Research consistently puts CRM project failure somewhere between 30 and 70 per cent, with poor user adoption as the leading cause. When the system gets harder to use, people use it less. When people use it less, the data gets worse. When the data gets worse, leaders stop trusting the reports. That spiral doesn’t start with a bang. It starts with one rep keeping their real pipeline in a notebook.
There’s a newer cost too. If AI is anywhere on your roadmap, and for most Australian businesses it is, your org’s condition is now the gating factor. Tools like Agentforce and Einstein can’t function reliably on fragmented data and tangled automations. Technical debt used to slow innovation down. Now it blocks it outright.
How do you know if your Salesforce org is degrading?
You don’t need admin access to spot the symptoms. You just need to watch your people. The signs we see most often across Australian orgs:
- Simple changes take weeks. Adding a field or tweaking a rule used to be a same-day job. Now it needs a meeting, an impact analysis and a prayer.
- Spreadsheets are creeping back. If your team exports Salesforce data to “do the real work” in Excel, the org has stopped serving them.
- Nobody can explain why something exists. Automations, fields and reports with no known owner are the clearest fingerprint of decay.
- You’re paying for licences nobody logs into. Silent shelf-ware is one of the most common findings when someone finally looks.
- Your reports and your gut disagree. When leaders quietly stop trusting the dashboard, the data problem became a decision problem a while ago.
If two or more of those sound familiar, your org isn’t fine. It’s coping. There’s a difference.
Why hasn’t anyone told you?
Fair question. Part of the answer is structural. If your implementation partner built the org, they’re not exactly motivated to volunteer that it’s ageing badly. If your internal team is stretched (and whose isn’t), keeping the lights on beats archaeology every time. And Salesforce itself ships three major releases a year, which means an org that stands still is actually moving backwards against the platform underneath it.
Nobody is lying to you. It’s just that nobody’s job is to tell you the truth about the whole org. So nobody does.
What looking under the hood actually involves
A proper look isn’t someone eyeballing your setup for an afternoon. It means reading what the org itself says: the metadata. That’s where the honest story lives. Which fields are actually used. Which automations conflict. Where access has quietly sprawled beyond what anyone approved. Which of your licences are earning their keep.
For most organisations, a periodic, independent review is a sensible start. It’s the annual service: someone who didn’t build the engine telling you what state it’s in.
For enterprises, especially in regulated industries, a once-a-year look isn’t enough anymore, because the org changes every week. That’s why we built 8SSure, our continuous assurance platform for enterprise Salesforce. It turns your platform metadata into ongoing, executive-grade evidence of security, governance and operational health. Not a snapshot. A live read on whether the platform your business runs on is actually secure, governed and trusted, that you can put in front of a board or an auditor.
We’ve delivered over 1,000 Salesforce projects across Australia, and a decent share of them started exactly here: with someone finally asking what condition the org was really in. In almost every case, the answer surprised them. In almost every case, they wished they’d asked a year earlier.
The cheapest time to look is now
Decay never gets cheaper to fix. Every quarter you don’t look, the workarounds multiply, the dependencies tangle further and the eventual clean-up bill grows. The businesses that avoid the six-month change freeze are the ones that popped the bonnet while things still seemed fine.
Your org isn’t going to send you a warning light. Consider this article the closest thing.
Wondering what’s really going on under your hood? Start a conversation with 8Squad. We’ll tell you the truth about your org, even if the truth is that it’s in good nick.
