Why CPQ implementations fail
Salesforce CPQ (formerly SteelBrick) is powerful but complex. 40% of CPQ implementations miss their go-live date, and 25% require a re-implementation within 18 months. The root cause is rarely the tool — it's over-engineering. Teams try to automate every pricing edge case, build product rules for scenarios that happen once a quarter, and create quote templates that break with every revision. These 5 mistakes are the ones we see in every failed CPQ rescue.
Mistake 1: Over-engineering product rules
Product rules (bundling, exclusions, inclusion) should handle 80% of your quoting scenarios — not 100%. Teams build 200+ product rules for edge cases that occur in <5% of quotes. Each rule adds evaluation time and maintenance overhead. Rule of thumb: if a rule fires on <5% of quotes, handle it with a rep warning (validation rule) instead of a product rule. Target <50 product rules total.
Mistake 2: Cascading price rules
Price rules calculate discounts, markups, and surcharges. When price rules cascade (rule A's output feeds rule B's input), debugging becomes impossible — a 2% discount rule can interact with a volume discount rule to produce unexpected prices. Limit price rule chains to 2 levels max. For complex pricing (tiered, volume, promotional), use price schedules and discount schedules instead of chained price rules.
Mistake 3: Breaking quote document templates
The quote document (the PDF the customer sees) is where CPQ implementations break at the 11th hour. Teams build complex templates with conditional sections, tables, and images — then discover at UAT that the template breaks when a bundle has >10 line items or when a discount >20% is applied. Build the template early (week 2, not week 10), test with edge-case quotes (10+ line items, 50% discount, multi-currency), and use the native CPQ quote template editor over custom Visualforce.
Mistake 4: Ignoring CPQ's data model complexity
CPQ adds 30+ custom objects (Products, Price Books, Product Rules, Price Rules, Discount Schedules, Quote Line Items, Quote Documents). A typical CPQ org has 500-2000 products, each with 10+ attributes. Loading this data manually is impossible — use the CPQ import wizard or Data Loader with the CPQ import templates. Budget 2-3 weeks for data migration alone, and assign a dedicated 'CPQ data owner' to maintain product/price data post-go-live.
Mistake 5: No renewal/amendment strategy
Teams implement new-business quoting but forget renewals and amendments (upsells, downgrades). CPQ has renewal-related fields (Renewal Product, Renewal Pricing) that must be configured at implementation — not after. Without it, renewal quotes start from scratch (losing contract terms, pricing tiers, discount history). Plan the renewal flow during design: auto-create renewal opportunities 90 days before contract end, pre-populate with existing products, and apply renewal pricing (same price, CPI increase, or renegotiated).
"If a product rule fires on <5% of quotes, handle it with a rep warning instead. Target <50 rules total."
Key Takeaway
Don't over-engineer: target <50 product rules, <2-level price rule chains, test quote templates with edge cases early, budget 2-3 weeks for data migration, and configure renewals at implementation — not after.