Revenue Intelligence vs CPQ

CPQ software (configure, price, quote) makes sure quotes are put together correctly: the right products, the right prices and only approved discounts. It works before the signature. Revenue Intelligence works after it: it checks whether what was agreed in the quote and the contract is also invoiced, indexed and renewed that way. CPQ prevents errors in making the agreement. Revenue Intelligence finds errors in carrying it out.

What does CPQ do?

In companies with many products, options or pricing agreements, putting a quote together is error-prone. A salesperson picks a combination that is technically impossible, uses an out-of-date price list or gives a discount nobody approved. CPQ solves that with three functions:

• Configure. The software knows which products and options can go together. A salesperson cannot choose a combination that cannot be delivered.
• Price. Prices come from a central price list, with rules for volume tiers, customer groups and currencies. Discounts above a threshold go through an approval route.
• Quote. The quote is generated automatically in a fixed format, often directly from the CRM.

CPQ is often a module of, or integration with, the CRM. Salesforce and HubSpot offer their own versions, and there are standalone CPQ packages. For companies with complex products or pricing structures, it mainly delivers speed and consistency.

Where does CPQ stop?

CPQ is done as soon as the customer signs. The quote is correct, the discount approved, the deal goes to the CRM as won. What happens next is outside CPQ's reach.

And that is exactly where things often go wrong:

• The order is re-keyed by hand. The quote from CPQ is entered again in the ERP, with a typo or a forgotten line.
• The discount stays on. An introductory discount for the first year is entered in billing as a fixed price and runs on for years.
• Indexation is not applied. The contract, based on the quote, includes an annual price adjustment. Nobody puts it into billing.
• Changes outside CPQ. A customer expands through a phone call with the account manager. No new quote is produced, so no correct price either.
• Additional work. During the project, work is added that was not in the quote. CPQ knows nothing about it.

CPQ guarantees that the agreement is right. It does not guarantee that execution follows the agreement. How to check that second step is described in How do you check that contracts are billed correctly?.

Side by side

How do CPQ and Revenue Intelligence reinforce each other?

CPQ and Revenue Intelligence fit together well. CPQ produces structured agreements: which products, which price, which discount, for which period. That is exactly the data Revenue Intelligence needs to check invoices.

Without CPQ, agreements have to be extracted from PDF quotes and contracts, sometimes with the help of AI that reads text. With CPQ, they are already in fields. The comparison then becomes simpler and more exact: quote line next to order line next to invoice line.

Conversely, Revenue Intelligence shows where CPQ is being bypassed. Deals without a CPQ quote, discounts that are higher in billing than in the quote, prices adjusted by hand after the quote. That is information the CPQ administrator needs to tighten the rules.

Worked example: approved discount, wrong duration

Worked example: suppose a business software supplier uses CPQ. Every discount above 15 percent requires approval from the sales director. That works: not a single quote goes out with an unauthorised discount.

Some of the discounts are intended for the first contract year only: "20 percent introductory discount in year 1". The quote states this correctly. In billing, the discounted price is entered as a fixed annual price.

• Suppose there are 40 such contracts, with an average list price of EUR 15,000 a year.
• The discount is EUR 3,000 per contract per year.
• After year 1, those 40 contracts should have moved to full price. That does not happen. Missed revenue: EUR 120,000 a year, for as long as nobody notices.

CPQ did its job: the quote was correct and approved. The leak is in the translation to billing. The figures are made up to show the mechanism. More on this pattern in Revenue leakage from wrong prices.

Five places between quote and invoice where things go wrong

If you have CPQ, the first link in the chain is in order. These are the links that follow, with what to watch at each step:

1. Quote to order. Check that the number of lines, the quantities and the price per line in the order match the signed quote. A forgotten option line is the most common deviation.
2. Order to billing schedule. For recurring revenue: check start date, term, invoicing frequency and whether temporary discounts have an end date.
3. Contract to price adjustment. Is indexation set up as a rule in billing, with the right index and effective date? Is it actually carried out? See Revenue leakage from missed price indexation.
4. Delivery to invoice line. Additional work, extra usage, extra licences: are they recorded and invoiced at the rate in the quote?
5. End of term to renewal. Is a contract renewed at the price then applicable, or does it quietly run on at the old one?

At every link, the same holds: CPQ recorded the right agreement. Whether that agreement survives the link depends on integrations and people.

Do you need CPQ for Revenue Intelligence?

No. Revenue Intelligence also works with quotes and contracts that do not come from CPQ. It does become more important that agreements are recorded in a structured way somewhere, or that the system can extract them from text.

Do you need Revenue Intelligence if you have CPQ? If your billing is set up by hand or through a different route from the quote, there is a good chance of differences arising that CPQ does not see. CPQ plus an automatic link to billing reduces that chance but does not cover everything: additional work, indexation, changes outside CPQ and renewals stay out of view.

The wider comparison with BI, CRM, ERP and other systems is in Revenue Intelligence vs Business Intelligence. How the whole chain from quote to payment runs is explained in Quote-to-cash explained.

Checklist: does your quote carry through to the invoice?

Use these questions to see where things can go wrong between quote and invoice:

1. Does every won quote automatically become an order, or is it re-keyed?
2. Are temporary discounts recorded in billing with an end date?
3. Are indexation clauses from the quote or contract set up as a rule in billing?
4. Do expansions for existing customers always go through a new quote in CPQ?
5. Is additional work during a project recorded and invoiced at the agreed rates?
6. Is it checked periodically whether the invoiced price per customer equals the most recent approved quote?

Frequently asked questions

Is CPQ a form of Revenue Intelligence?

No. CPQ is a sales tool that produces quotes. Revenue Intelligence checks the revenue chain afterwards. They share data but have a different purpose.

Does CPQ prevent revenue leakage?

It prevents part of it: wrong prices and unauthorised discounts in quotes. Leaks that arise after the signature, such as missed indexation, uninvoiced additional work or discounts that keep running, fall outside it.

We don't have CPQ. Is that a problem?

Not necessarily. Many companies with simple products do not need it. What matters more is that agreements are recorded somewhere they can later be compared with invoicing.

Can Revenue Intelligence monitor the discounts in CPQ?

It can see whether the discount on the invoice matches the approved discount in the quote, and whether a temporary discount was ended when it expired. The approval itself stays in CPQ.