A major US and Canadian lighting manufacturer discovered their Configure, Price, Quote system migration was fundamentally broken halfway through the build. The original consultant's architecture couldn't scale. Six months later it was rebuilt, migrated, and running — and supported for three more years after that.
Client details have been fictionalized to protect confidentiality under NDA. The project, timeline, and results are real.
The client is a manufacturer and distributor of high-end lighting products with approximately $150 million in annual turnover, operating across North American continents. Their distribution model combines direct-to-consumer sales through a nationwide network of sales agents with wholesale distribution channels — a complex, multi-layered sales operation that requires precise, reliable quoting and pricing at every level.
To manage that complexity, the business ran a Configure, Price, Quote system — specialist software that allows sales agents to build accurate, consistent quotes across a product range of significant depth and complexity. A CPQ system done right is a competitive advantage. A CPQ system done wrong is a liability that touches every sale in the business.
Theirs was done wrong.
The client had engaged a consultant to rebuild and migrate their existing CPQ system — a significant project given the size and complexity of their product range and sales network. The project was progressing and approximately halfway through the build when errors started appearing at scale.
The errors weren't isolated bugs. They were symptomatic of something more fundamental — the underlying architecture the consultant had built was structurally flawed. It worked in isolation and at small scale, but as the product migration progressed and volume increased, the design wasn't flexible enough. The errors multiplied because the foundation architecture was wrong.
Discovering a fundamental architecture problem at 50% completion is one of the worst positions a technology project can be in. You've already invested heavily. You're not close enough to the end to push through. And the cost of going back to fix the foundation feels enormous — but not as enormous as the cost of completing a system you know won't work.
The client made the right call. They stopped the project and looked for someone who could fix it properly.
After reviewing the existing build, my assessment was unambiguous — patching the flawed architecture wasn't viable. The structural problems were too deep to fix incrementally. The only reliable path forward was to scrap the existing work entirely and rebuild from the correct foundation.
That's not a recommendation any consultant makes lightly. It means telling a client that a significant investment has to be written off. But delivering a broken system to protect sunk costs isn't integrity — it's just a more expensive way to fail.
The rebuild started from scratch with the correct architecture for the client's specific product structure, pricing model, and sales agent workflow. Everything the previous build had attempted was re-examined, redesigned where necessary, and rebuilt properly.
The rebuilt system was designed around how the business actually worked — not a generic CPQ template, but a configuration built for a manufacturer with a complex product range, constantly changing requirements, tiered pricing across direct and wholesale channels, and a distributed sales agent network operating across two countries.
The product migration was completed correctly this time — every product, every pricing rule, every configuration option structured in a way that the system could handle at full scale without errors. The sales agent network in both the US and Canada could generate accurate, consistent quotes across the full product range. Pricing integrity was maintained across both distribution channels — direct and wholesale — without manual intervention or workarounds.
The full rebuild and migration was completed and live in six months. A system that had been half-built incorrectly was replaced with one that worked correctly — at scale, across two countries, for a sales network that depended on it daily.
The engagement didn't end at launch. Following the successful rebuild and migration, the relationship continued for a further three years of ongoing system support — maintaining, refining, and evolving the CPQ system as the business changed.
That extended engagement is significant for two reasons. First, it demonstrates that the rebuilt system worked — a system that needed constant firefighting doesn't generate three years of stable support work. Second, it reflects a consistent approach to client relationships: the build is the starting point, not the end point. Systems need to evolve as business requirements change, and the ongoing support relationship is where that happens.
A CPQ system supporting a $150 million business across two countries and a nationwide sales agent network isn't something you build once and walk away from. The three-year support engagement ensured it kept working as the business grew and changed.
That longevity matters. A system that gets abandoned after launch degrades as the business around it changes. Products get added. Pricing structures evolve. Sales agent requirements shift. The ongoing support relationship meant those changes were absorbed continuously rather than accumulating into a problem that eventually requires another expensive rebuild.
This engagement covers ground that most small business automation work doesn't — enterprise-scale systems, complex multi-country sales operations, specialist CPQ software, and the kind of architectural decision-making that determines whether a major technology project succeeds or fails.
The skill that made the difference here wasn't familiarity with one specific tool. It was the ability to walk into a failing project, diagnose what was fundamentally wrong, make the difficult call to start again, and then build it correctly. That diagnostic capability — understanding why something isn't working and knowing what it would take to fix it properly — is transferable across systems, industries, and scales.
CPQ systems are specialist software. This wasn't a domain I had years of prior experience in. It was a domain that needed to be understood quickly, diagnosed accurately, and rebuilt correctly — which is a different skill entirely from simply knowing the software. The ability to walk into any business system, understand how it's supposed to work, identify where it's broken, and fix it is more valuable than deep expertise in any single tool. Tools change. That diagnostic capability doesn't.
Whether the problem is a paper-based ordering system for a small service business, a broken Excel billing process for a consultant writing off revenue every month, or a failed CPQ migration for a $150 million manufacturer — the approach is the same: understand the business, find the real problem, fix it properly, and keep it working. The scale changes. The methodology doesn't.
Sometimes the most valuable thing is an honest second opinion on what's actually broken and what it would genuinely take to fix it. Free 30-minute call, no pitch.
Book a free 30-minute call. Let's fix that →The same problem-first approach applied to different business challenges.
Book a free 30-minute call and we'll look at exactly what's costing you the most time.
Book a free call →