Why CPQ Projects Fail

Most CPQ failures aren’t technical. They’re conceptual.

Years ago, I was asked to help implement CPQ at a large global market research firm after an internal audit flagged a material weakness in pricing governance and contracting discipline. The thinking was simple: we’ll implement CPQ and it will enforce consistency.

Our implementation partner asked for a few things to get started: our product catalog, pricing guide, discount authority structure, quoting templates, and approved contracting terms.

There was just one problem.

None of it existed.

We had grown from a small sales team with a paper rate card into a global organization with hundreds of sellers across regions and verticals. Consistency used to come from shared relationships and experience — but that doesn’t scale.

For the next six months, we had to build the commercial system we thought we already had:

• Naming and defining products
• Documenting configuration rules
• Establishing pricing logic
• Creating discount governance
• Standardizing quotes and contracts

Only then could we implement CPQ.

And when the system finally launched, it was painful — because we weren’t automating what people were already doing.

For many sellers, it was the first time they had ever seen the rules or felt them.

That experience taught me a few things:

1. If you can’t document your process, you’re not ready to automate it.

2. CPQ doesn’t create governance — it exposes whether governance already exists.

3. The hardest part of CPQ isn’t technology. It’s organizational change.

CPQ can be incredibly powerful.

But it shines a very bright light on whether your commercial system actually exists.