Conga › CPQ
Conga CPQ
implementation services
Product modelling, pricing, guided selling and approvals. On the Conga Advantage Platform, inside Salesforce, or across both. Including the migration between them.
Which Conga CPQ, and where does it run?
Two separate decisions, and they get collapsed into one more often than not. Get the second one wrong and you inherit an architecture nobody chose.
Decision one: which product
| Advantage CPQ | Smart CPQ | |
|---|---|---|
| Lineage | The Conga line, hosted on the Conga Advantage Platform | The engine that came in with the PROS B2B business, February 2026 |
| Reach | Synchronises across CRM environments and out to ERPs such as SAP and Oracle through standard APIs | Runs natively on both Salesforce and Microsoft Dynamics 365, API-first to SAP and Oracle |
| Suite fit | Connected natively to Conga CLM, Composer and Billing on the same platform | Integrates with Conga document automation, CLM and price optimisation |
| Distinctive strengths | Deep product configuration, constraint modelling, asset-based ordering and amendments | AI-led pricing and win-rate probability, guided configuration, quotes past 10,000 line items |
Both now reach across CRMs and ERPs, so this is not a Salesforce versus everything-else choice, whatever the product pages imply. It turns on how your product model and pricing governance actually work, and on which suite you want the rest of your revenue lifecycle sitting in.
Where the engine runs is a separate decision
This is the one most often assumed rather than decided, and the assumption is usually wrong in the same direction. Advantage CPQ is not a Salesforce-only product. It is hosted on the Conga Advantage Platform, it functions outside Salesforce entirely, and Conga is explicit that you can deploy on any CRM or third-party solution. Salesforce is one front end option among several.
| Deployment shape | Where the engine sits | Choose it when |
|---|---|---|
| CPQ for Salesforce | A managed package inside your own Salesforce org. TurboEngines offload heavy pricing and configuration to Conga compute when the cart outgrows the org | Your product model fits comfortably inside Salesforce and you want a single org to administer |
| Advantage Platform, Salesforce front end | On the Conga platform, with your Salesforce org connected through the CPQ bridge package. Sellers never leave Salesforce | You want platform-grade configuration and pricing without moving your sales team, which is the most common enterprise shape |
| Advantage Platform, standalone or another CRM | Engine and interface both on the Conga platform, synchronised to Dynamics, SAP or Oracle, or to no CRM at all | Salesforce is not your system of record, or quoting genuinely does not belong inside the CRM |
The decision is also not permanent. Conga documents a route where the managed package stays in Salesforce while the platform picks up the heavy work, which turns a migration into a sequence rather than a single cutover. In most enterprises that is the right way to do it.
What we build
Product modelling and catalogue
Multi-level hierarchies, bundles inside bundles, option groups, and the constraint rule sets that most implementations quietly avoid. We have modelled around 2,500 product master records from SAP down to a sellable catalogue.
Pricing
Price lists and tiers, matrices, volume and currency handling, customer-specific and partner discount structures, mass price updates, and asset-based bottom-up pricing driven by live asset queries at quote time.
Guided selling and cart
Configuration flows people will actually use, cart totalling and summary groups, custom and formula fields on cart line items, and cart performance tested at scale rather than assumed.
Approvals
Approval rules and flows, search-filter approvals driven off deal-value fields, and escalation patterns that match how your commercial governance really works rather than how the org chart looks.
Asset-based ordering and amendments
Renewals, amendments and change orders against an installed base, including the service rules that decide what a customer is allowed to change and when.
Quote documents
The document that leaves the building. Generated from the cart, on brand, and correct, through Conga Composer or X-Author.
Migrating CPQ from Salesforce to the Advantage Platform
We are doing this now, on a live programme at a Finnish industrial manufacturer, keeping Salesforce as the front end. The work is more specific than a lift and shift, and the specifics are where the risk sits.
- Pricing callbacks. Turbo pricing callback classes rebuilt as platform pricing callback classes, then behaviour-diffed against the source implementation rather than assumed equivalent.
- Constraint rules. Replicated and tested against the original, including option-group expansion behaviour, on bundles carrying more than 100 rules each.
- Configuration at scale. Two bundles in the current proof of concept carry 200 to 300 options across multiple option groups, with bundles nested inside bundles.
- Cart performance. Validated at around 1,500 line items, because a migration that is functionally correct and unusably slow has not succeeded.
- Proof before commitment. A scoped proof of concept on your most difficult products first, so the full migration is planned against evidence rather than optimism.
Questions
How long does a Conga CPQ implementation take?
Our fastest go-live on the Advantage Platform was 120 days from kick-off, for a single business unit with a well-understood product model. A multi-business-unit programme with ERP integration and asset-based ordering runs across quarters. We give a not-to-exceed number at the end of Phase Zero rather than a range at the start.
Is Advantage CPQ a Salesforce product?
No, and this is the most common misconception we meet. Advantage CPQ is hosted on the Conga Advantage Platform and functions outside Salesforce entirely. Conga is explicit that you can deploy on any CRM or third-party solution. Salesforce is one front end option, and a popular one, but it is not a requirement.
Can we keep Salesforce as the front end and put CPQ on the Advantage Platform?
Yes, and it is the most common enterprise shape. Your Salesforce org connects to the platform through the CPQ bridge package, the heavy configuration and pricing run on Conga compute, and your sellers stay where they already work. We have live programmes running exactly this.
What are TurboEngines, TurboPricing and TurboConfig?
TurboEngines are microservice compute engines that move heavy work off Salesforce. TurboPricing handles pricing calculation, TurboConfig handles configuration, and TurboEngines Data Sync moves data between Salesforce and Conga. They are the answer when your cart has become slow rather than a default install.
Our Conga managed package is several releases behind. Is that a problem?
It is the most common condition we find and it is fixable. Conga publishes upgrade paths between seasonal releases. The work is in regression testing your customisations rather than in the upgrade itself, which is why it gets deferred and then compounds.
Can Conga CPQ replace Salesforce CPQ?
It can, and we have done that migration. Whether you should depends on where your complexity actually lives. If your pain is product configuration and pricing logic rather than the quoting UI, the case is stronger.
Explore the rest of the Conga practice
Tell us where the quoting process breaks.
A CPQ health check is a short, fixed piece of work that ends in a document you own. It does not commit you to an implementation.