To get bundles, volume pricing, approval matrices, multi-year subscriptions, and renewals, you install a CPQ (Configure, Price, Quote) product on top of Salesforce. The first-party answer is Salesforce CPQ (part of Revenue Cloud); the alternates are AppExchange packages like Conga CPQ, DealHub, and PandaDoc.
Why CPQ instead of customising
Building CPQ-grade logic with Flow + Apex on top of standard Quotes can be done — and is often started — but the maintenance cost compounds. Bundle rules, tier calculations, ramps, approvals, contract management, renewal generation, and templating all interact. A purpose-built CPQ ships those as one engine that’s already governed-limit-safe and upgradeable.
What Salesforce CPQ adds
| Capability | What it does |
|---|---|
| Product Rules | Validation, alert, selection, and filter rules at quote-line level |
| Price Rules | Adjust prices on the fly based on conditions |
| Bundles | Parent product with required / optional / dependent components |
| Configuration Attributes | Ask the rep questions; the answers drive products/prices |
| Block Pricing & Tiers | Volume-based, slab-based, and unit-based tiers |
| Subscription pricing | Term, ramp, prorate, MDQ (multi-dimensional quoting) |
| Approvals | Native CPQ approval engine on discounts/terms |
| Quote Templates | Rich PDF templates per scenario/language |
| Contracts & Renewals | Auto-generate contracts and renewal opportunities |
| Amendments | Edit a live contract with co-term math |
Architecture overview
Salesforce CPQ runs as a managed package in the same org. Standard objects (Opportunity, Quote, Account) plus CPQ custom objects (SBQQ__Quote__c, SBQQ__QuoteLine__c, SBQQ__ProductRule__c, etc.). The “Quote” you click on a CPQ-enabled Opportunity is the CPQ Quote custom object, not the standard Quote.
AppExchange CPQ alternatives
- Conga CPQ — enterprise-strong configurator, complementary to Conga Composer for documents
- DealHub CPQ — guided selling and DealRoom collaboration
- PandaDoc CPQ — combines CPQ with document generation
- Oracle CPQ (BigMachines roots) — when you live in Oracle as well
- Vlocity / Industries — for telco/insurance/health vertical configurators (now Salesforce Industries Cloud)
Custom-build option (small scope only)
If your need is just “one extra approval level” or “a custom PDF template”, build it on standard Quotes:
- Approval Process for discount thresholds
- Visualforce Quote Template for branded PDFs
- Flow to copy/snapshot a Quote into a Contract
- Lightning Component for a guided product picker
The line where this stops being a good idea is when you start writing bundle / tier / ramp logic from scratch — at that point you’re building CPQ poorly.
How to talk about it in an interview
- Acknowledge what standard Quotes do well (flat catalog, simple discounts).
- Identify the gap (bundle / tier / ramp / approvals / renewal).
- Recommend CPQ — first-party (Salesforce CPQ) is the default; if budget or fit pushes elsewhere, list AppExchange options.
- Mention guarded customisation for one-off enhancements.
Common follow-ups
- How long does a CPQ implementation take? — 3-6 months for mid-market, 6-12+ for enterprise.
- Can CPQ run alongside standard Quotes? — Yes, but you’ll typically pick one as the system of record.
- Is Industries CPQ different from Salesforce CPQ? — Yes — Industries CPQ is built on OmniStudio for vertical industries (telco, utilities, media).
Verified against: Salesforce Help — Salesforce CPQ. Last reviewed 2026-05-17 for Spring ‘26.