What is CPQ software and when is it useful?
CPQ means Configure, Price, Quote. The software guides a sales representative or customer through an offer, checks whether the selected combination is valid, calculates the right price, and prepares the quote.
CPQ becomes especially useful when a quote depends on many variables: compatible or incompatible options, quantities, dimensions, countries, customer types, existing contracts, discounts, manufacturing costs, or commercial terms. Salesforce currently positions its CPQ capabilities within Agentforce Revenue Management, covering configuration, pricing, approvals, and quoting.
Real complexity must still be distinguished from a simple quote form. If five products each have a fixed price, a standard CRM is often enough. CPQ becomes valuable when rules are numerous enough to create errors, manual approvals, or dependence on a few experienced salespeople.
How do you model products, options, and configuration rules in CPQ?
The configurator must first represent how the offer is actually built. A product may have attributes, such as power, dimensions, capacity, or material, and options that can be mandatory, optional, or incompatible with each other.
Rules may express, for example: `if power > 100 kW, industrial power supply is required`, `option A is incompatible with option B`, or `Premium package automatically includes maintenance and module X`. CPQ solutions already structure catalogs, bundles, hierarchies, attributes, and configuration rules.
In custom CPQ software, these rules should ideally remain configurable in a back office. A commercial change should not require a code change every time a new product or option is introduced.
How do you build a pricing and discount engine in CPQ?
Pricing may come from a fixed list, but it can also depend on quantities, customer segments, geographic areas, options, dates, contracts, costs, or cumulative volumes.
A pricing engine can apply rules in sequence: list price, options, customer price, volume, promotion, sales discount, minimum margin, final price. Rule priority must be explicit. Otherwise, two discounts may stack when they should be exclusive, or a salesperson may generate a price below the approved margin.
CPQ should also preserve the version of the rules used when the quote was created. If the catalog changes a month later, the company must still be able to explain how an older quote was calculated.
How do you manage discounts, margins, and approval workflows?
Not every discount should require a sales director’s approval. The system can define thresholds: 0 to 10%, autonomous; 10 to 20%, manager approval; above 20%, executive approval.
The logic can also depend on margin, total amount, customer type, or a combination of criteria. Market CPQ solutions include discount and approval mechanisms, but the workflow must remain aligned with the commercial rules actually used.
The benefit is twofold: standard quotes move faster while commercial exceptions remain traceable. Each approval can record the person, date, requested discount, and decision.
How do you generate a quote automatically from CPQ?
Once the configuration is approved, CPQ already contains most of the required information: customer, products, quantities, options, prices, discounts, and terms.
The quote can then be generated from a controlled template, with price tables, selected options, contractual terms, validity period, and technical appendices where needed. Several templates can coexist by brand, country, product, or sales channel.
The final document must remain linked to its configuration. If a salesperson later changes a quantity or discount, they should be able to generate a new version without rebuilding a Word or Excel document manually.
How do you connect CPQ to a CRM, ERP, and product catalog?
CPQ should not normally become a new source of truth for every company record. A CRM, Customer Relationship Management, can own accounts, contacts, and opportunities. An ERP, Enterprise Resource Planning, can own items, costs, inventory, orders, and billing. A PIM, Product Information Management, can centralize product information for different channels.
CPQ orchestrates this information to build the offer. After acceptance, the quote can create an order in the ERP and update the opportunity in the CRM.
A clear architecture must determine which system owns each piece of data to avoid maintaining three separate catalogs or three different prices.
How do you manage complex products and impossible configurations?
This is one of the most valuable uses of industrial CPQ. For a configurable piece of equipment, some combinations may be technically impossible: insufficient power, incompatible dimensions, an option requiring another option, or components unavailable in a country.
CPQ can eliminate impossible choices as the configuration is built instead of waiting for an engineering team to reject the quote several days later.
For highly technical products, the system can also produce a commercial or technical bill of materials for the ERP, production, or engineering teams.
How do you manage subscriptions, renewals, and usage-based pricing?
Modern CPQ is no longer limited to one-time product sales. It can manage subscriptions, licenses, renewals, recurring options, or usage-based pricing.
The cycle becomes broader: configuration, quote, contract, order, billing, renewal. This is often called quote-to-cash, the journey from quote to collected revenue.
Salesforce now positions Agentforce Revenue Management across this broader scope. Its public pricing page currently lists Revenue Cloud Growth at €150 per user per month and Revenue Cloud Advanced at €200 per user per month, billed annually. Such a solution should be compared with custom development based on integration and differentiation needs.
CPQ and artificial intelligence: which use cases are genuinely useful in 2026?
AI can assist the sales process without replacing the deterministic rules engine. It can summarize a customer request, extract constraints from a specification, suggest products, or prepare quote commentary.
Guided selling means guiding a user toward a consistent selection through business questions and criteria. AI can help understand the request or search for a configuration, but final validation should remain explainable.
A rule such as “this option is incompatible with this engine” or “margin must never fall below X” should generally remain deterministic. The best approach is often to use AI to understand or assist, then let the CPQ engine validate and calculate.
Salesforce, SAP, Conga, or custom CPQ: what should you choose?
Standard solutions are already mature. Salesforce offers Agentforce Revenue Management with CPQ capabilities, SAP actively maintains SAP CPQ with releases planned in 2026, and Conga offers CPQ covering configuration, pricing, quoting, and asset management.
A standard CPQ is generally preferable when the company already relies heavily on the relevant ecosystem and its commercial rules can be configured in the product.
Custom CPQ becomes more relevant when the difficulty lies in unusual business rules, highly specific products, several legacy systems, or an interface that cannot be reproduced cleanly with the standard solution. The right approach is a fit-gap analysis, comparing native features, configuration, integrations, and remaining custom development.
How do you measure the ROI of a CPQ project?
ROI, or return on investment, should not be reduced to the number of minutes required to produce a quote. Measure average quote creation time, correction rate, back-and-forth with technical teams, approval time, exceptional discounts, pricing errors, achieved margin, and time from opportunity to order.
CPQ becomes particularly valuable when it turns expertise held by a few people into rules usable by the entire sales team.
How much does custom CPQ development cost?
Cost mainly depends on the number of rules and integrations. A configurator with a few dozen products and simple pricing rules is very different from an industrial CPQ handling thousands of combinations, several countries, and ERP/CRM connections.
The main workstreams are usually: product model, configuration engine, pricing, approvals, document generation, integrations, back office, migration of existing rules, and testing.
Testing is especially important because the number of possible combinations can become very large. Critical rules should therefore be covered by automated tests so a pricing change does not silently break another scenario.
How does Koragence develop custom CPQ software?
We start by collecting the rules actually used today: catalogs, Excel files, pricing grids, discount procedures, and decisions usually made by sales or technical teams.
These rules are turned into an explicit model and tested against historical quotes. The prototype should allow a salesperson to reproduce several real cases before the full tool is developed.
Deployment then follows: rule mapping, prototype, configuration engine, pricing, approvals, documents, CRM/ERP integrations, testing, migration, and rollout.
