1 min read

[Case Study] Hitting Reset on a Seven-Year ERP Journey.

A $1B+ Produce Company. A Seven-Year ERP That Never Landed. Outcome: 20–30% IT Cost Reduction. ERP Stabilized. Operating Model Reset.
[Case Study] Hitting Reset on a Seven-Year ERP Journey.

Situation

A $1B+ produce company had been running an ERP implementation for seven years.

It was technically live, but operationally unstable. The system never delivered what the business was promised. Costs kept rising. Confidence kept dropping.

A new CFO came in with a simple question: What is actually going on here?

Safebox was brought in to get answers and to get the program back under control.


What We Found

The ERP wasn't failing because of the platform.

It had been customized beyond what the vendor could support. The business kept adding requirements. The technology team kept building. No one was setting limits. No one understood the consequences.

At the same time, the IT organization lacked operating discipline.

Vendors were unmanaged. Work was unprioritized. Accountability was unclear. The business had no reliable way to influence what IT was doing — or understand what it was getting.

Two governance failures. Running in parallel. For years.

It was not going to fix itself.


What We Did

We started by stopping the ERP from getting worse.

We reset the vendor relationship. Imposed hard limits on customization. Forced alignment between business and technology on what the system would — and would not — do.

Then we rebuilt the broader IT organization.

We imposed governance. Enforced real prioritization. Rebuilt the delivery model with a higher-skill hybrid team operated by Safebox.

With clarity and control restored, leadership made the organizational changes they had been deferring.


Outcome

Annual IT spend was reduced by 20–30% on a multi-million-dollar budget, with additional one-time savings.

The ERP is stable and moving forward on a defined path.

What started as an ERP intervention became an operating model reset.

Safebox now partners with the client to manage and run their IT operations and back-office functions. A board member shared that we flipped their IT service levels from worst-in-class to best-in-class.

Three years in, the question is no longer: "What is going wrong?"

It is: "Why didn't we do this sooner?"