You can usually tell a stalled rollout without opening a single report. It’s the team where reps log into Salesforce on Friday afternoon just long enough to dump their numbers before the pipeline meeting, then don’t touch it again until next Friday. It’s the org where half the custom fields haven’t been filled in months. It’s the sales manager who still keeps his own spreadsheet, because he stopped trusting the dashboard a while back.
None of that shows up as a single dramatic failure. It shows up as a slow, quiet drift and IBM’s most recent State of Salesforce study, surveying over 1,200 customers, found that only twenty six percent actually have most of their business data living inside Salesforce. For the other seventy-four percent, the platform they’re paying enterprise licensing for has quietly become a partial, half-trusted system sitting next to whatever workaround people actually rely on.
What a stall actually costs
The obvious cost is the wasted spend licenses nobody’s using to their full extent, features paid for and switched off in practice if not on paper. But that’s the smaller number. The bigger cost is what happens around the gap. When reps skip logging activity, deal risk goes undetected until it’s too late to fix. When marketing, sales, and customer success all pull from a system that’s only partially populated, cross team visibility breaks down quietly support doesn’t see deal context, finance doesn’t trust the pipeline for capacity planning, and every one of those blind spots compounds the next time someone has to make a call based on numbers they don’t fully believe.
There’s a newer version of this cost too. With consumption based features like Agent force and Data Cloud, an org that isn’t being actively watched doesn’t just sit idle it can quietly burn through a chunk of a year’s credit allocation from one misconfigured flow or an agent processing more than expected, and most teams don’t find out until the bill does the explaining for them.
And there’s a compliance cost that only shows up when someone goes looking for it. Inconsistent use of a system in a regulated environment doesn’t just create messy data. It creates the exact gaps an audit is designed to find.
Why it stalls in the first place
Almost every stalled rollout we’ve seen traces back to the same root cause: it was run as a project with an end date, not a program with an owner.
Training happened once, during go live, for work people wouldn’t actually be doing for another six weeks so most of it was forgotten by the time it mattered. Improvements shipped in big quarterly batches instead of small regular ones, which mostly just taught people to brace for disruption every few months instead of expecting steady progress. And once the initial project team moved on to the next thing, nobody was left with real, ongoing ownership of whether the system was actually being used well.
None of that is a technology problem. It’s a cadence and ownership problem which is actually
good news, because those are fixable in a quarter, not a year.
The one quarter reversal
Month one is diagnosis, and it has to be honest. Login counts tell you almost nothing someone can be logged in all day and still be avoiding the system for anything that matters. Look instead at whether the workflows the platform was bought to support are actually being completed, where the data genuinely stops flowing, and where people have quietly built a workaround instead of using what’s in front of them.
Month two is about momentum, not scope. Pick the two or three fixes that will be felt immediately not the ambitious six month roadmap. Ship something every couple of weeks instead of saving it all for one release, and put guidance inside the workflow itself rather than in a separate portal nobody opens mid-task. The goal isn’t a finished system. It’s a team that’s started trusting that using it gets easier, not harder, over time.
Month three is where it either sticks or slides back. This is the point to name a real owner for adoption not a committee, one person and attach one or two numbers to a recurring leadership review: percentage of deals with activity logged in the last seven days, or the share of records with complete, current data. What gets reviewed on a schedule gets maintained. What doesn’t quietly reverts to the Friday afternoon habit within another two quarters.
The stall is more reversible than it looks
A stalled rollout feels like a bigger problem than it usually is, mostly because it happened slowly and nobody officially declared it a failure along the way. But the fix is almost never a new platform or a new implementation. It’s putting an owner and a cadence back underneath the one you already have and a quarter is genuinely enough time to prove that’s working, if the first month is spent finding the truth instead of assuming you already know it.
