ERP/CRM Postmortem Files

Postmortem notes on startups, ISV apps, and ERP/CRM solutions - what happened, why they changed, and what can be learned from their journey, within and beyond the Microsoft ecosystem.

PROFILE #0007 · Microsoft First-Party Products

Frederick Wildman & Sons

After more than $5 million and two years, a Dynamics 365 Business Central implementation remained unstable, exposing the cost of weak testing and release management.

Status
Recovered
Year
2024
Founded
1934
Funding
Private company

The Idea

Frederick Wildman & Sons is a long-established U.S. importer and distributor of wines and spirits. The company has operated in the industry since the early twentieth century and built a complex distribution business around a large portfolio of suppliers and customers.

Like many established companies, Wildman needed its ERP environment to support increasingly complex operations while maintaining reliable financial and distribution processes.

The company embarked on a Microsoft Dynamics 365 Business Central implementation intended to modernize its ERP environment.

The Rise and Fall

The implementation became a prolonged stabilization project.

According to the published recovery case study, the organization had invested more than $5 million over 24 months, yet the ERP platform remained unstable. The problems caused significant operational disruption and raised a fundamental question: should the company continue investing in the existing implementation or consider starting over?

The reported problems were particularly associated with testing coverage and the release process. Rather than being a single catastrophic failure at go-live, the project entered a state where the organization had already invested heavily but still could not rely confidently on the system.

This is a common but less visible form of ERP failure.

The system may technically exist. Users may even be using it. But if releases repeatedly introduce defects, critical processes are unstable, and the organization lacks confidence in the platform, the implementation has failed to deliver the operational value that justified the investment.

Why It Failed

The central issue was not simply software functionality. It was quality management throughout the implementation lifecycle.

The case highlights two particularly important weaknesses:

  1. Insufficient testing coverage: Critical business scenarios were not sufficiently validated before changes reached production.
  2. Weak release management: Changes could introduce instability into an already complex ERP environment.

This creates a dangerous cycle:

More defects → more fixes → more releases → more regression risk → less confidence → more emergency work.

Once this cycle begins, project teams can spend enormous amounts of time fixing symptoms rather than improving the underlying solution architecture and delivery process.

What Happened Next

Rather than abandoning Business Central, the recovery approach focused on stabilizing the existing implementation.

The case became an example of recovering an ERP project through stronger testing, release management, process discipline, and targeted remediation rather than starting over with a different ERP platform.

Lesson: ERP testing is not a final project phase. It is a continuous risk-management discipline.

For Business Central and other cloud ERP platforms, frequent updates make regression testing, release governance, automated testing where appropriate, and clear ownership even more important.

A system that technically works but cannot be changed safely is not a healthy enterprise platform.

The real measure of implementation success is not simply whether the ERP is live. It is whether the organization can operate, test, change, and release the system predictably without putting the business at risk.

Sources