CPQ with 30 people is a factory for a bakery
At some point the word comes up. A proposal was wrong yet again, discounts are running wild, and someone heard at a conference that what you need for this is CPQ. Configure, Price, Quote, sounds like exactly the missing piece. The reseller happily confirms and sends a quote: licenses from 75 euros per user per month, six-figure implementation, project runtime six to nine months.
For an enterprise with 400 sellers, 12,000 SKUs, and configuration rules where product A excludes variants C and F, that is money well spent. You have 30 people and a price list that fits on two pages. You do not need a factory. You need a clean recipe.
Because the real problem is almost never the tool. It is the pricing logic that does not exist. Which discount tiers apply at which volume? Which products get bundled, and what does the bundle actually cost? Twelve, 24, or 36 months of term, and what is the price difference? If these questions have no fixed answers, every AE answers them himself, fresh every day. A CPQ system changes none of that. It only forces you to pour the chaos into rules, in the middle of an expensive project, under time pressure, with an implementation partner who bills by effort and earns on every extension. The standardization you keep dodging catches up with you inside the project. It just costs five times as much there.
So the order flips. First, nail down the pricing logic: discount rules, bundles, terms, documented and signed off by the executive team. That is uncomfortable work, a few hard internal discussions, not a single license. Then you look at what is needed to implement it, and at 20 to 200 employees the answer is almost always soberingly simple: the suite’s native quoting, a maintained price book, discount approvals as a process, proposal generated with one click. All included in editions you are probably already paying for.
The uncomfortable part of this truth: you cannot buy it. Ordering a tool feels like progress, enforcing price rules feels like conflict. Which is why so many companies have a half-implemented CPQ nobody uses sitting next to a price list nobody follows.
If your pricing logic fits on a sheet of paper, why run a project that lasts longer than your fiscal year?
