Why "We've Already Implemented Salesforce" Is the Most Expensive Sentence in the Building

Every Salesforce project has a finish line. A go-live date, a sign-off email, a small celebration in the Slack channel. Somewhere around that point, most organisations file the system under "done" and move their attention to the next priority. That's the moment the real cost starts building, quietly, and rarely noticed until someone asks why the system that was supposed to solve everything doesn't feel like it's solving much anymore.

Implementation and optimisation are not the same project

Implementation gets a system built and switched on. It answers one question: does this work, technically, as specified? Optimisation is a completely different question, asked on a completely different timescale: does this still match how the business actually operates, given that the business hasn't stood still since go-live?

Most organisations only ever properly resource the first question. The second one doesn't get a budget line, a project sponsor, or a deadline, because nothing about it looks urgent from the outside. Nothing is on fire. Reports still run. Users can still log in. It's only when you look closely, data nobody quite trusts anymore, automation quietly duplicating work, a feature everyone paid for and nobody's opened this quarter, that you see the org sliding, slowly, back toward the exact thing it was originally built to prevent.

The org doesn't announce that it's drifting

This is the part that catches people out. A Salesforce org drifting away from what the business needs doesn't send a warning. It just gets a little more annoying to use, a little less trusted, one small workaround at a time, until eighteen months later someone finally asks the question out loud: why is half the sales team back on a spreadsheet?

I see this pattern constantly, and it's rarely one dramatic failure. It's the accumulation of a hundred small ones nobody flagged because none of them individually seemed worth a meeting. A validation rule that made sense for last year's process and now just gets worked around. A dashboard nobody's opened since the person who built it left the business. A feature switched on during implementation because it was in scope, never adopted because nobody built the habit around it, quietly billing every month regardless.

Optimisation is a discipline, not an event

The organisations that avoid this don't have a better implementation partner or a cleverer initial build. They've simply accepted that a CRM behaves like anything else used daily by real people under changing conditions, it needs periodic attention, not because something's broken, but because the business it's meant to serve keeps changing shape underneath it.

In practice that's less dramatic than it sounds. It's a standing, honest look every so often at what's actually being used versus what's just switched on. It's checking whether the process the system was built to support is still the process people actually follow, or whether it's quietly drifted while nobody updated the fields to match. It's treating "nobody's complaining" as a weak signal rather than a reassuring one, by the time people complain loudly enough to reach you, they've usually already built their own workaround and stopped trusting the system to solve it for them.

The uncomfortable arithmetic

Here's the part worth sitting with: the cost of never doing this isn't zero, it's just invisible. It shows up as licence fees for features nobody opens. As a sales team's real working data living across three spreadsheets instead of the system you paid for. As a rebuild, three years from now, costing more than a few honest hours a quarter would have. None of that appears on an invoice labelled "cost of not optimising." It just compounds quietly, the way any maintenance you skip does, right up until it doesn't.

The fix isn't a bigger implementation. It's treating the system the way you'd treat anything else that has to keep working under real conditions, with the assumption that it needs occasional, honest attention, not a single successful launch followed by silence.

If the last real look anyone took at your org was the go-live meeting, that's worth changing before the drift becomes a project of its own.

Want help understanding what needs to be optimised? fill in the contact form and let's have a chat about your suspected issues and how I can help