There's a pattern in enterprise technology that almost everyone has experienced but few talk about directly: the gap between what a system was supposed to do and what it actually does two years after go-live.
It happens with Salesforce. It happens with Oracle. The implementation delivers
something functional, the project closes, the team moves on, and the system drifts. Data
quality degrades. Automations break silently. Workarounds accumulate. Users develop
habits that bypass what the system was designed to do. And the organisation gradually
stops getting the value the platform was capable of delivering.
This is not mainly a technology failure. It's a lifecycle failure — the assumption that implementation is the end of the work.
Salesforce and Oracle Cloud are genuinely capable platforms when they're maintained
properly. Salesforce can accelerate sales cycles, cut service resolution times, and
drive revenue through personalisation when it's configured and adopted well. Oracle
Cloud ERP can compress month-end close from weeks to days, surface financial anomalies
that would otherwise go unnoticed, and give procurement the visibility to manage supplier
risk before it becomes a problem. These outcomes are real. They require work to reach and
more work to sustain.
Configuration Discipline Matters More Than Programmes Admit
Both Salesforce and Oracle have extensive standard functionality. Organisations that
over-customise create upgrade risk, maintenance overhead, and technical debt that makes
every subsequent change harder. Choosing standard over custom — even when it requires a
process change nobody wants to make — tends to look like the right call within eighteen
months.
Data Quality Is the Other Underinvested Area
Duplicate customer records, incomplete master data, inconsistently entered transactions
— these are not system problems. They're process problems the system makes visible.
Organisations that address data quality before go-live rather than after have a
noticeably different experience in the first year.
Adoption Is Where Most Value Quietly Disappears
Sales teams that find Salesforce adds burden without visible benefit will work around
it. Finance teams that don't understand Oracle's period-close process will revert to
spreadsheets. Adoption is a design problem — it requires building the system around how
people actually work, training against real scenarios, and measuring usage post-go-live
with the same rigour as technical KPIs.
Post-Go-Live Is Where Most Programmes Stop Paying Attention
Oracle releases quarterly updates. Salesforce releases three major updates a year plus
continuous additions. Treating these as IT maintenance tasks misses what they actually
are: a stream of capability improvements that organisations on active managed services
relationships consistently use more effectively than those running the same
configuration they went live with three years ago.
The value Salesforce and Oracle Cloud deliver is not a function of how well they were
implemented. It's a function of how well they're run after.
