Field guide · August 2026
CPQ is the software that turns a valid product configuration into an accurate price and a quote a customer can sign. People land here to understand the work, not to hire a vendor.
In plain English: some products cannot be sold from a catalog page. A switchgear lineup, a truck body, a pump skid, a telecom bundle, a service contract with options — each deal is a combination. Someone has to decide what is allowed, what it costs, and what the customer is being asked to buy.
CPQ is the system that holds those three decisions together. Configure keeps the combination valid. Price applies the right money to that exact combination. Quote writes it down so sales, the channel, finance, and the factory are looking at the same thing.
It is not CRM. CRM knows the account and the pipeline. It is not ERP. ERP knows cost, inventory, and how to fulfill an order. CPQ sits between them: the moment a possible product becomes a priced offer.
The category is older than the acronym. Industrial sellers ran configurators and quote desks long before “CPQ” was a product name. The software formalized a job that already existed: stop selling invalid products at unofficial prices on documents nobody can rebuild.
Simple products do not need CPQ. A single SKU with a price book can live in CRM or ecommerce. CPQ shows up when the product is a system, the price is conditional, or the quote is a promise the plant has to keep.
A configurable machine can have more legal variants than anyone will pre-build as items. Encoding the rules once is cheaper than maintaining a fantasy catalog — and cheaper than letting every rep invent a valid product in a spreadsheet.
List, contract, channel, volume, attribute, and approval-gated discounts are not a markup column. Manufacturers use CPQ so the price of a configuration is computed, not negotiated from memory, and so margin floors are enforced before a quote leaves the building.
On engineered or assembled products, the quote is the first draft of the BOM, the drawing pack, and the order. If configuration is wrong here, engineering rework and missed ship dates show up later. CPQ is used to make the sales document manufacturable.
That is why the buyers are manufacturers, distributors with configuration, industrial OEMs, and companies whose “product” is a bundle of hardware, software, and services. The common trait is not company size. It is that a wrong quote is expensive.
Treat them as jobs, not tabs in a UI. Most failed CPQ programs over-invest in one verb and hand-wave the other two.
Verb 01 · validity
Configuration is constraint. Attributes, options, quantities, and child products are chosen so the result can exist — electrically, mechanically, commercially, or contractually. Rules hide illegal combinations, force required ones, and explode a sales structure into parts.
This is where nested configurables live: a line that opens another configurator, a parent model that launches child models, a bundle that contains another bundle. It is also where a shearlist earns its keep — a parts list cut down to what is still eligible given the current answers.
Without configuration, sales either over-simplifies the product or sends engineering a wish. The output is not a pretty UI. It is a structure the rest of the quote can trust.
Verb 02 · money
Pricing takes that exact structure and applies money. List price is the book. Net is what the customer is asked to pay after contract prices, discounts, promotions, and adjustments. The gap is margin. The gap is also where approval workflows exist.
Good pricing engines are boring on purpose: matrix lookups, attribute modifiers, volume breaks, price rules. Bad pricing engines hide policy in one irreplaceable script. Salesforce people meet that script as QCP. Oracle people meet it as BML in the commerce process or the pricing engine. The language changes; the temptation does not.
If configuration is wrong, price is fiction. If price is tribal knowledge, the quote is a negotiation, not a calculation.
Verb 03 · the offer
A quote is both a document and a record. The document is what the customer sees: lines, options, terms, drawings, sometimes a 3D view. The record is what the company keeps: status, approvals, version, who discounted what, and what should happen if the deal is won.
This is the commerce process — draft, pending approval, approved, ordered — and the handoff into CRM opportunity, ERP order, CLM contract, or a CAD/BOM pack. Platforms differ in which of those they treat as native.
If you cannot rebuild the quote from the record six months later, you do not have CPQ. You have a PDF generator.
These are the names people actually mean when they say “enterprise CPQ.” No scores. No leader quadrant. What each is actually good at, from how they are used — not from a brochure.
Formerly BigMachines · acquired 2013
Born to configure and quote industrial machines in a browser. The commerce process (quotes as stateful transactions with actions and libraries) and the configurator (product families, models, recommended items, BOM mapping) still sit on one platform. Scripting is BML; data-table work is BMQL.
Good at Deep multi-level configuration, quote workflow, and CRM-agnostic deployments. The place shearlists, nested models, and commerce libraries are first-class.
Not the default for Teams that want quoting as just another Salesforce object and a two-week setup. Implementation is a program. The UI is as good as the investment you put into it.
Steelbrick lineage · two generations now
Classic Salesforce CPQ (Steelbrick) lives inside the CRM: products, options, product rules, price rules, quote line editor. When the rule objects run out, people write QCP — JavaScript that runs on calculate. Revenue Cloud is the newer quoting and revenue stack (catalog, context, a different object model). Both exist in the wild; they are not the same product.
Good at CRM-native quoting for companies already on Salesforce. Opportunity-to-quote-to-order is the path. The ecosystem of specialists is large.
Not the default for Engineer-to-order depth (3D, CAD, shop-floor BOM) unless you add another configurator. QCP becomes a dumping ground. The classic-CPQ versus Revenue Cloud split is a real migration problem, not a rename.
CallidusCloud lineage · acquired 2018
The CPQ you buy when SAP is already the system of record. Quote 2.0, tenant setup, and customizations through Python global scripts. It is meant to sit with SAP CRM/C4C and S/4, and to be adjacent to variant configuration rather than replace the ERP.
Good at SAP-centric landscapes, SSO and master-data gravity, quoting that must land cleanly in SAP order management.
Not the default for Best-of-breed selection by a team with no SAP estate. The independent practitioner community is smaller than Oracle’s or Salesforce’s; you usually arrive here because you already arrived at SAP.
Formerly KBMax
A configurator that thinks in pictures and in the plant. SNAP is a visual, block-based, Turing-complete rule language. The distinctive work is 3D/visual configuration and CAD automation: the quote is allowed to become a drawing, a cut list, and an ERP BOM, not only a PDF.
Good at Engineer-to-order and make-to-order manufacturers who cannot quote without geometry. SNAP is approachable for product people and deep enough for real algorithms.
Not the default for Pure software, subscription, or document-heavy professional-services quoting. If there is nothing to draw, you are buying the wrong center of gravity.
Infor Configure Price Quote · CloudSuite / LN / M3 worlds
Configuration and quoting that travels with Infor ERP — CloudSuite Industrial (SyteLine), LN, M3, and the Infor CRM/ION neighborhood. Rules-based configuration, enterprise quoting, and the assumption that the order already has a home in Infor.
Good at Infor shops that want configuration without standing up a second platform religion. ION and workbench integrations are the native path.
Not the default for A greenfield “pick the best configurator, ERP later” decision. You rarely choose Infor CPQ if you are not already an Infor customer.
Apttus CPQ + Conga · documents and CLM adjacency
Salesforce-native quoting with a center of gravity in document generation and the contract. Composer, CLM, and the quote-as-proposal are the reasons people stay. Configuration exists; it is not a manufacturing configurator that wants to own the BOM.
Good at Proposal-heavy, contract-adjacent revenue processes on Salesforce. When the quote is a document that must become an agreement, Conga is in its own house.
Not the default for Deep physical-product configuration, CAD, or plant-floor BOM explosion. If your pain is a shearlist, this is the wrong aisle.
No ratings, share numbers, or “leader” badges. Platforms change names faster than they change engines. If you are choosing one, match the verb you are worst at — configure, price, or quote — to the product that treats that verb as native.
Terms you will actually hear in implementation rooms. Not a vendor dictionary.