If a customer has negotiated prices, a quote should begin with those prices—not with a salesperson remembering which spreadsheet to open. The challenge is deciding which agreement applies, when it expires and whether a later discount is allowed on top.

For sales operations teams, the most useful options are governed CPQ systems rather than a document template with an editable price table. DealHub, Conga, Salesforce Revenue Management, Oracle CPQ and Experlogix are five credible directions, with different product and implementation boundaries.

Who needs a customer-specific price book?

This requirement appears when the same product has different contracted rates by account, customer group, region or period. A one-off negotiated discount is not necessarily a price book. Nor is a product-information catalogue that publishes retail prices to a website.

Before selecting software, define the precedence: standard price, customer agreement, quantity tier, currency and discretionary discount. Then define who can change it. Our comparison uses official documentation and current product descriptions, not hands-on quoting tests or claims of recovered margin.

Candidate	Relevant pricing direction	Best starting scenario	Boundary to confirm
DealHub	CPQ with account/deal context and pricing configuration	Sales-led configuration across commercial terms	Which fields and rules the implementation must configure
Conga	Smart CPQ and Advantage CPQ product family	Contract/tier pricing in a governed quoting process	Named product, add-ons and price-agreement scope
Salesforce Revenue Management	Salesforce Pricing and current revenue platform	Customer terms inside a Salesforce-led revenue process	Current licences; not the same product as legacy managed-package CPQ
Oracle CPQ	Layered pricing models, including customer-specific pricing	Negotiated prices combined with configuration rules	Pricing-engine configuration and connected Oracle components
Experlogix CPQ	List, contract and tiered pricing	Complex configured products and contractual pricing	Proposed CRM/ERP integration and rule ownership

DealHub: carry the account context into quoting

DealHub’s integration guidance describes carrying customer-specific discounts and pricing context through configured fields. Its CPQ guidance describes account-specific pricing as part of the quoting direction.

That makes it relevant when the buyer wants sales operations to manage a controlled quoting process. Ask for your exact customer agreement to be demonstrated. A field capable of carrying a negotiated rate is not proof that the precedence, expiry and approval policy have already been implemented. Establish which system owns the agreement before importing another copy into the CRM.

Conga: name the CPQ product in the proposal

Conga now presents Smart CPQ and Advantage CPQ within its CPQ family. Its service descriptions include customer-specific price agreements and tiered pricing in the relevant product descriptions.

Investigate Conga when price agreements sit inside a broader governed product-to-contract process. Require the quote to identify the actual product and optional capabilities: features described across the family should not be combined into an imaginary single base plan. Demonstrate an expired agreement as well as an active one, because silent reuse of yesterday’s price is an operational risk.

Salesforce: use the current revenue product names

Salesforce’s current pricing-model documentation refers to Revenue Management, formerly Revenue Cloud, and describes Salesforce Pricing. Its licence comparison separates the available functional areas.

This is a sensible direction when Salesforce is already the commercial operating environment. Do not assume a Sales Cloud licence includes the full quoting and pricing implementation. Also do not mix current Revenue Management capabilities with instructions for the older managed-package Salesforce CPQ product. Ask for a contract-specific pricing demonstration in the exact proposed edition.

Oracle CPQ: inspect the pricing layers

Oracle’s CPQ pricing documentation distinguishes base, list and net price and explicitly includes customer-specific and matrix-based pricing. Its pricing-engine overview describes layered pricing rules and models.

That makes it a strong candidate to investigate when account agreements interact with product configuration and several pricing methods. Require an explanation of the calculation, not merely its final number. Check whether a result came from a supported pricing model or custom code, and who will maintain it when a contract changes.

Experlogix: test contract pricing alongside the configured product

Experlogix’s pricing and discounts offering describes list, contract and tiered structures, regional logic and discount routing. Its CPQ product is aimed at governed configuration and quoting.

Investigate it where the quoted product or service is complex enough that price validity depends on the configuration. Treat broad marketing assurances as vendor claims. The proposal should identify the supported CRM/ERP route and show what happens when a salesperson requests a configuration or discount outside the approved rules.

The demonstration that separates a price book from a spreadsheet

Create two fictional customer accounts buying the same item. Give one a dated contract price, the other a volume agreement. Add an expired agreement and a quote copied from an earlier period. Ask the vendor to explain every resulting line price and who may override it.

Then change the underlying agreement after a draft quote has been approved. Does the quote preserve a valid agreed version, require recalculation or clearly flag the difference? There is no universal answer, but the behaviour must match your commercial policy. Avoid tools that can only show the right number when a demonstrator manually chooses the right spreadsheet.

If an approved price change must also reach existing customers, map the customer price-change notice handoff separately. Updating the price book, delivering a notice and recording any required acceptance are different outcomes.

Costs and an independent recommendation

Compare user licences, pricing modules, implementation, integration, maintenance and training. Public list prices rarely describe the whole governed-pricing project. A smaller team with occasional bespoke quotes may need a simpler approval process, not enterprise CPQ.

Shortlist according to your existing commercial systems and hardest pricing rule. None of these vendors is a universal winner, and no sponsorship determines its position. The business case is fewer ambiguous pricing decisions, not an unsupported percentage improvement.

For the resulting contractual record, see contract management software. For an adjacent sales decision, customer expansion and upsell explains why a commercial opportunity should not itself authorise a new customer price.

Official sources checked 20 October 2026. Research-based selection; no hands-on testing or paid inclusion.