Reflections from Episode 12 of the D365 Insights Podcast

In our twelfth episode — and the final recording of the year — we explored ERP delivery from two vantage points that rarely get equal airtime: the Microsoft partner and the end‑user client.

To bring those perspectives to life, we welcomed Jim Farmer, a senior finance consultant and solution architect with a decade of ERP delivery experience, and Chris Jones, a seasoned end‑user leader who has managed three full D365 implementations across telecoms, healthcare, and service industries.

What followed was an honest, grounded conversation about what “successful delivery” really looks like, why expectations matter more than methodology, and how the partner–client relationship can make or break an implementation.

What Does a Successful ERP Delivery Look Like?

Jim opened with a partner‑side view: success is multi‑dimensional.

• A scalable, robust solution that automates intelligently

• A project that meets scope and timeline

• A system that users genuinely adopt, not just one that goes live

For Chris, the client perspective adds another layer: Success depends on knowing why the ERP is being implemented in the first place. Without clear intent — in finance, supply chain, operations — there’s no meaningful way to measure whether the system is delivering value months or years later.

Go‑live is important, but it’s only the beginning. True success is what the business experiences six, twelve, or thirty‑six months down the line.

The Biggest Challenge? Expectations — and the Space Between Them

Chris didn’t hesitate: the hardest part of ERP delivery is setting expectations.

Stakeholders, C‑suite leaders, internal IT teams, and partners all come into the project with assumptions. When early sales conversations over‑promise timelines or outcomes, the project starts on uneven ground — and trust becomes fragile.

From the partner side, Jim highlighted a different but related challenge: process ownership and decision‑making.

Partners work to fixed timelines. Clients often juggle project responsibilities with BAU firefighting. When decisions are delayed or unclear, rework increases and momentum slows. The partnership suffers.

Both perspectives point to the same truth: ERP delivery succeeds when expectations are aligned early and revisited often.

Post-Go‑Live: The Part We Don’t Talk About Enough

Chris emphasised something every experienced ERP leader knows: Go‑live is a milestone, not the finish line.

Enhancements, adoption, optimisation, and continuous improvement are where the real value emerges. This is why roles like Finance Systems Manager are becoming so critical — organisations need people who can help them get the most out of their system long after the project team has stepped away.

Listen to the Full Conversation

Episode 12 is a thoughtful, practical discussion for anyone involved in ERP delivery — whether you’re leading a programme, supporting BAU, or partnering with clients to bring their systems to life.

👉 Catch the full episode of the D365 Insights Podcast to hear Jim and Chris share their experiences first‑hand.