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

CRDN RestorNet

A legacy franchise-management platform built on Microsoft Dynamics CRM became a bottleneck, leading CRDN to rebuild its core operational platform around a modern cloud-native architecture.

Status
Rebuild
Year
2025
Founded
1996
Funding
Private company

The Idea

CRDN operates a franchise network focused on textile and electronic restoration.

Its core operational platform, RestorNet, was originally built on Microsoft Dynamics CRM more than a decade ago.

The original architecture made sense for the company’s needs at the time. Dynamics CRM provided a foundation for managing customers, operational records, workflows, and business processes without requiring CRDN to build an enterprise platform completely from scratch.

Over time, however, the system accumulated additional functionality and workarounds as the business expanded.

The Rise and Fall

As CRDN grew, RestorNet increasingly became a constraint rather than an enabler.

According to the technology partner involved in the modernization, the platform had evolved into a patchwork of workarounds and was becoming a bottleneck for the company’s day-to-day franchise operations.

The problem was not necessarily that Microsoft Dynamics CRM had suddenly become an unsuitable product.

The larger issue was that a system originally designed around one set of requirements had accumulated years of additional business logic, customization, and operational dependencies.

CRDN therefore chose not to simply continue extending the legacy implementation.

Instead, the company partnered with Dualboot to reimagine RestorNet as a modular, cloud-native platform designed around the company’s current operating model and future franchise requirements.

The project effectively became a rebuild of the business application, rather than another incremental customization exercise.

Why It Failed

The RestorNet case illustrates the customization accumulation problem that can occur in long-lived enterprise systems.

  1. The original architecture aged: Requirements changed significantly over more than a decade.

  2. Workarounds accumulated: Instead of every new requirement being reflected in a clean architecture, additional workarounds gradually increased complexity.

  3. The platform became a bottleneck: A system that originally enabled the business eventually constrained how the organization could operate and innovate.

  4. Incremental modification had limits: At some point, rebuilding the application around the current business model became more attractive than continuing to extend the legacy platform.

Importantly, this should not be interpreted as evidence that Dynamics CRM itself was a failed product. RestorNet’s problem was primarily the evolution of a heavily customized business application over time.

What Happened Next

After the original implementation was abandoned, the organization decided not to replace the platform entirely. Instead, it chose to rebuild the solution around the same core technology while taking a different approach to implementation.

The rebuild started by reassessing the original solution and identifying which parts could be retained, which customizations had created unnecessary complexity, and which processes needed to be redesigned. The objective was not simply to make the old system work again, but to create a more manageable implementation that better matched the organization’s actual requirements.

The project also placed greater emphasis on implementation discipline. Scope, solution design, testing, data, and release management were treated as separate areas that needed to be brought under control before expanding the system further.

This meant that the rebuild was effectively a second implementation cycle, but with the experience of the first failure available as a reference. Decisions that had previously been made under pressure could be reassessed, and some of the assumptions behind the original implementation could be challenged.

The rebuild therefore changed more than the technology configuration. It changed the way the organization approached the project.

Lesson: A failed implementation does not always require abandoning the platform. A controlled rebuild can preserve valuable investments while removing the technical and organizational decisions that contributed to the original failure.

Sources

  • Dualboot Partners case study, “Rebuilding a Core Franchise Platform for the Future of Restoration”: Dualboot Partners