ERP failures rarely start with dysfunction. They start with confidence. Optimism. The belief that internal teams can lead the charge. But after dozens of rescue projects, we’ve seen the same story unfold: by the time help is requested, the damage is already compounding. This post unpacks what we learned helping teams who didn’t initially want help—how their assumptions formed, why support was often delayed, and what ultimately shaped the design of The Reset. If you’re a CFO overseeing an ERP implementation, this story might be closer to your own than you think.
When we first began helping finance and accounting professionals navigate ERP implementations, we focused on prevention. We wanted to reach teams before failure set in. Before morale dropped. Before systems were live—but unusable.
We warned CFOs and controllers of what could go wrong. We flagged misalignment early. We offered to walk alongside the team from the start.
And most of the time, the answer was the same:
“We’ve got this.”
“Our internal team is strong.”
“We’ve already started the implementation.”
“We’ll call if we need help.”
But ERP failure doesn’t show up overnight. It shows up slowly—then all at once.
We stopped trying to insert ourselves at the beginning. Not because we didn’t see the risk, but because we saw the pattern:
And still, systems went live that nobody trusted. Teams were burned out. CFOs felt blindsided. And the business was stuck with a tool that was supposed to transform operations—but couldn’t even support them.
A 2023 report by EY found that 65% of finance leaders involved in ERP projects underestimated internal readiness, leading to missed deadlines, budget overruns, and delayed benefits.
We started receiving calls six, nine, twelve months in.
By that point, these weren’t just implementation issues. They were trust issues. Culture issues. Strategic issues.
That’s when we stopped trying to help teams “do implementation better” and started helping them recover from what they’d already been through.
The Reset wasn’t a service we came up with in a strategy meeting. It was a direct response to the emotional and operational gaps we saw across dozens of ERP implementations.
We created The Reset to solve for those realities. It gave CFOs a structured way to stop the noise, clarify what mattered, and re-ground the system in how the business actually runs.
It wasn’t about starting over. It was about stabilizing. And then rebuilding with the right foundation.
In 2024, as Reset engagements increased, we published a free resource to support CFOs during active implementations—even if they hadn’t yet hit the “help” stage.
That resource became the 90-Day CFO Implementation Playbook—a practical tool to help finance leaders establish traction, momentum, and measurable clarity early in the project.
It’s not required reading for The Reset. But for teams trying to stay ahead of the breakdowns we’ve seen, it’s a meaningful head start.
We no longer try to convince teams to let us in. Instead, we meet them where the tension breaks:
That’s when we step in.
The Reset exists because too many capable teams were left unsupported. Not because they didn’t care. But because they didn’t know what they didn’t know—until it hurt.
And when they’re ready, we help them move forward.