"Our ROI deck looks great, but half the reps still quote in Excel." I hear this line in almost every steering meeting. The dashboards say green. Field reality is red.

I’m Magnus. I’ve lived inside CPQ programs for two decades. The pattern is consistent: when adoption is high, everything compounding and good happens. When adoption is low, everything noisy and expensive happens.

Adoption is the only metric that matters.

The Real Cost of Low Adoption

Teams often measure CPQ success through ROI slides, feature lists, or a go-live date. Familiar, safe, and wrong. Those are inputs. The outcome is whether sellers actually choose CPQ over their old shortcuts when the clock is ticking.

Low adoption doesn’t fail loudly. It fails quietly - through workarounds. You still get quotes out, but the system never becomes the place where product, price, and learning meet. Pricing stays tribal. Data stays stale. Support tickets rise. The CFO wonders why the benefits never showed up.

What looks like a training problem is usually a design and ownership problem. If CPQ isn’t faster than the best workaround and clearer than the old cheatsheet, reps won’t move. According to Gartner research on digital initiatives, adoption is the top determinant of realized value - not the existence of the technology itself. I see that in the field every week.

CPQ doesn’t win by control. It wins by being the fastest path to a correct quote.

Why This Moment Is Different

There’s a quiet shift happening. The bar for seller experience is a lot higher than it was five years ago. The rep who buys groceries on their phone won’t tolerate a 9-step wizard and a loading spinner to add a motor option.

At the same time, product complexity is up. More variants. More localization. More commercial rules. If you try to solve complexity by adding rules without fixing ownership and explainability, adoption drops. If you surface logic transparently and make updates safe and frequent, adoption rises.

AI adds pressure in both directions. It can speed interaction, but it does nothing for trust if the underlying constraints and price policies aren’t explicit. I’ve watched teams bolt chat on top of brittle logic and wonder why reps still call engineering. The apprentice is fast only when the expert’s structure is solid.

If reps can’t see why a configuration or price is valid, they won’t trust it.

Engineering Adoption: Four Rules That Hold Up

Rule 1: Measure behavior, not licenses. Count weekly active sellers who create or revise quotes in CPQ. Split by depth of use: configuration touched, price adjusted, proposal sent. Add two leading indicators: time-to-first-valid-config for new reps and median time-to-proposal for typical deals. Example: One manufacturer I worked with had 600 licenses and only 80 weekly active sellers. After redesigning the top three flows and publishing a visible change log, they hit 290 in eight weeks.

Rule 2: Be faster than the best workaround. Set a performance target against the current Excel champion. Take three representative scenarios - simple, standard, complex - and time end-to-end: from opportunity to signed proposal draft. If CPQ isn’t winning on the clock, it will lose in the field. Anti-pattern: Demo-Grade CPQ - screens look great in a conference room, but the three clicks that matter are slow or buried.

Rule 3: Make the system explain itself. Don’t just show a red error. Show the constraint. Don’t just output a number. Show why the price is what it is - base, adds, discounts, approvals. If a rep can explain the quote to a customer without calling someone, adoption grows. One Tacton client added inline “why” links on key choices and cut “is this allowed?” calls by half in a month.

Rule 4: Own the change loop. Faster change beats perfect rules. Give explicit owners for product constraints, price policies, and document templates. Ship small updates on a two-week cadence. Publish what changed and why in a place sellers actually read. Anti-pattern: Hero Admin - everything routes to one person, so nothing routes at scale. Adoption stalls because the system can’t keep up with the field.

Every rule you add is a tax on future change - charge it carefully.

From Theory to Habit: What To Do This Quarter

1) Establish an adoption scoreboard the field respects. Keep it simple and visible:

  • Weekly active sellers by region and business unit
  • Median time-to-proposal for three named scenarios
  • Percent of quotes generated fully in CPQ vs exported to Excel
  • Top 5 friction logs from support and sales each week

Review it in sales leadership and product meetings. Tie recognition to behavior change, not tool evangelism. This moves the conversation from “we rolled out CPQ” to “we sell differently now.”

2) Remove one workaround every week. Pick a specific friction and kill it with intent. Example targets: default values that match 80% of deals, a preconfigured kit for the most common bundle, a one-click price view that includes customer terms. Publish the fix in a living change log. I’ve seen this alone turn skeptics into regular users.

3) Run field drills - not training. Training talks at reps. Drills prove that CPQ is the fastest path under pressure. Pick five real deals. Put a sales manager, a product owner, and a CPQ admin in the room. Time the flow, capture blockers, fix immediately where possible. Rerun the same drill in two weeks to show measurable gain. It’s amazing how much credibility you earn when a rep sees their quote go out faster with fewer calls.

4) Make logic explainable at the point of use. Add simple “why” affordances next to constrained choices and price lines. For complex products, include a one-page “how this product decides” guide inside CPQ. According to analyst coverage of configure-price-quote platforms, explainability is a key driver of seller trust and self-sufficiency. In practice, it’s the difference between a system sellers endure and one they defend.

5) Create a safe sandbox for sales to experiment. Give reps a flagged play environment with realistic data and no approval hooks, so they can test scenarios and learn limits quickly. Adoption rises when curiosity isn’t punished.

The Compounding Advantage

Here’s what I see in programs that treat adoption as the north star:

  • Pricing gets better, faster. More quotes in CPQ means better data on discounts, wins, and pockets of margin. You start operating with a weather map, not a thermometer. The team spots patterns and adjusts policy with confidence.
  • Engineering gets fewer interruptions. When logic is visible and validated in CPQ, the expert phone calls drop. Engineers focus on product, not rescue missions.
  • New hires ramp faster. If CPQ feels like having the best product expert in every call, your time-to-first-valid-config shrinks. This shows up in quota attainment and manager sanity.
  • Governance gets lighter. When change is continuous and safe, you don’t need a project to ship an update. The organization stops routing around the system.

And the alternative? Quiet irrelevance. Quotes originate elsewhere, CPQ is a documentation step, and the ROI story depends on assumptions instead of behavior. Nobody complains loudly because the workarounds kind of work. That’s the trap.

If Excel is still the fastest path to a correct quote, your CPQ isn’t finished.

I care about adoption because it’s mercilessly honest. It cuts through roadmaps, vendor slides, and internal politics. Either sellers choose CPQ in the moment that matters, or they don’t. Everything else is commentary.

The good news: adoption isn’t magic. It’s a set of choices you can make this quarter - about speed, clarity, ownership, and change. Make those choices, and the ROI deck will write itself.

Adoption is the only metric that matters.