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 #0013 · Microsoft First-Party Products

Hadley Group CRM

After multiple stalled CRM implementation attempts, Hadley Group replaced the delivery approach and recovered its Microsoft Dynamics CRM project in four months.

Status
Recovered
Year
2017
Founded
1970
Funding
Private company

The Idea

Hadley Group, a UK manufacturer, wanted a CRM platform that could support its growing sales and marketing operations.

The organization selected Microsoft Dynamics CRM and began implementation work.

The intended architecture was broader than CRM alone. The system needed to connect customer and sales information with the company’s existing Baan ERP environment and marketing tools.

On paper, this was a conventional enterprise CRM transformation: introduce a central customer platform while integrating it with existing business systems.

The Rise and Fall

The implementation did not progress as planned.

According to the implementation partner that later rescued the project, Hadley Group had made multiple attempts to implement the CRM platform. Earlier efforts stalled because of problems with delivery and a lack of sufficient expertise.

The situation became increasingly important because the CRM project was considered business-critical.

Rather than abandoning Dynamics CRM completely, Hadley Group changed its implementation approach and engaged a new partner.

The recovery team focused on simplifying the solution, prioritizing the most important business functionality, involving users earlier, and integrating Dynamics CRM with the existing Baan ERP system and ClickDimensions marketing platform.

The recovered implementation reached a working state and was ready for go-live within four months.

Why It Failed

The initial failure appears to have been primarily a delivery and implementation problem, rather than evidence that Dynamics CRM could not meet the organization’s requirements.

  1. Multiple implementation attempts: Previous projects had stalled before reaching a usable result.

  2. Insufficient delivery expertise: The later implementation partner identified lack of expertise and poor delivery as important contributors to the earlier problems.

  3. Over-engineering risk: The recovery approach deliberately focused on the critical business functions instead of attempting to solve every requirement simultaneously.

  4. User involvement: Earlier implementation problems were addressed by bringing users into the process and focusing on how the system needed to work in practice.

  5. Integration was treated as part of the solution: The CRM was designed to work with the existing Baan ERP and marketing environment rather than becoming an isolated application.

The project was therefore recovered without abandoning the original CRM platform.

What Happened Next

Hadley Group did not abandon the CRM project after the initial implementation problems. Instead, the project was taken through a recovery process focused on stabilizing the system and bringing the implementation back under control.

The recovery involved reviewing the existing configuration, addressing the most critical issues, and establishing a clearer approach to implementation and ongoing support. Rather than continuing to add changes on top of an unstable foundation, the team focused on getting the core processes working reliably before moving forward.

The implementation was eventually stabilized and returned to productive use. The experience also led to a more structured approach to governance, requirements, testing, and change management.

The recovery did not come from replacing the entire platform. The existing CRM investment remained the foundation, but the way the system was implemented and managed had to change.

Lesson: When an enterprise implementation starts to fail, abandoning the platform is not always the only option. A controlled recovery can preserve the original investment, provided the organization is willing to address the underlying implementation and governance problems rather than simply adding more changes to an unstable system.

Sources

  • Transparity case study, “CRM project rescue and transformation for Hadley Group”: Transparity case study