The proposed CPQ seat count exceeded the number of people who actually quote by 20 to 45 percent
A CPQ seat prices the act of building a quote. Most proposals price the sales organisation, and the two populations are not the same size.
Prepared by Redress Compliance · August 17, 2026 · Salesforce advisory. 20 to 30 Salesforce CPQ and Billing deals advised, 2024 to 2025.
Executive summary
The proposed seat count exceeded active quoting users by 20 to 45 percent. Because the proposal is sized from the sales headcount, and only a subset of a sales organisation ever builds a quote.
Buyers who tied CPQ seats to active quoting roles cut 15 to 30 percent of the initial proposal. The test is behavioural rather than organisational: who has produced a quote, not who sits in sales.
Billing volume tiers were set on optimistic invoice forecasts that ran 30 to 50 percent high. A tier bought against a forecast rather than a measured run rate is paid for whether or not the volume arrives.
Both errors share one cause. The sizing input is a plan in each case, and the correction in each case is a measurement you already hold.
What each line is actually sized on
Both products are priced against a population, and in both cases the proposal reaches for the larger of two available numbers.
| Line | Sized on | Should be sized on |
|---|---|---|
| CPQ seats | The sales organisation | People who have built a quote |
| Billing volume tier | The invoice forecast | Measured invoice run rate |
| Growth allowance | Assumed inside both numbers | Priced separately as an option |
| The correction | Available before the quote | Reads as a tactic after it |
Both rows fail the same way, which is what makes this a sizing problem rather than two separate negotiations. A plan is always larger than a measurement, and a plan is always the number that is easiest to produce. Sales headcount is in the HR system; the quoting population requires pulling who actually generated a quote. An invoice forecast comes from the business case; the invoice run rate comes from the billing data. In both cases the accurate number exists and is simply harder to reach for.
A CPQ seat prices the act of quoting, not the job title
Across roughly 20 to 30 Salesforce CPQ and Billing deals advised between 2024 and 2025, the seat count proposed exceeded the count of active quoting users by 20 to 45 percent. That gap is not an aggressive proposal so much as a mis specified one. CPQ prices the act of configuring, pricing, and producing a quote. In most sales organisations that act is performed by a subset: deal desk, sales operations, some named account owners, and a portion of the field. The rest of the organisation consumes quotes rather than building them, and consuming a quote is not what a CPQ seat is for.
The correction is a behavioural test rather than an organisational one. Buyers who tied CPQ seats to active quoting roles cut 15 to 30 percent of the initial proposal, and the evidence for that is a report of who has actually generated a quote in the trailing period. It is unusual among licensing corrections in that the seller has no strong counter argument: the question of who builds quotes is answerable from the system, and the answer is the same number whoever asks.
Billing repeats the pattern on a different axis. Volume tiers were set on optimistic invoice forecasts that ran 30 to 50 percent high, which means the tier was bought against a business case rather than against a measured run rate. A volume tier does not refund the difference when the volume does not arrive, so an optimistic forecast converts directly into paid capacity. The measured run rate is available in the existing billing data and it is the number the tier should be sized against, with expected growth priced as a separate option rather than assumed inside the commitment.
What links the two is that the accurate input exists in both cases and is simply less convenient to produce. Sales headcount sits in the HR system; the quoting population requires a report. The invoice forecast comes from the business case; the run rate comes from the billing records. Pull both before the proposal is priced, because a seat count reduced after the quote reads as a negotiating tactic while the same reduction made beforehand is simply the specification. The commitment floor question sits in minimums and true ups, the renewal sequence in the renewal playbook, and the library in the Salesforce practice.
- Usage exports analysed: inactive accounts, plan right sizing, per user reassignment
- Your quote benchmarked against 500,000+ real closed deals, adjusted for size, region, and industry
- Every risky clause flagged with the exact quote, the page, and the replacement language
The Salesforce licence optimisation brief
The estate audit, the renewal timeline, the uplift cap targets, and the buyer side moves across the full Salesforce estate.
Get the brief →Sizing it correctly
- Pull the report of who has actually generated a quote, which is the behavioural test that cut 15 to 30 percent from the initial proposal.
- Do not size CPQ from sales headcount, since most of a sales organisation consumes quotes rather than building them.
- Size the billing volume tier on measured invoice run rate, not on the forecast, which ran 30 to 50 percent high across the deals reviewed.
- Price expected growth as a separate option rather than letting it be assumed inside either number.
- Do the work before the proposal is priced, because a reduction after the quote reads as a tactic and the same reduction before it is the specification.
- Recheck the quoting population at each renewal, since the deal desk composition changes and the seat count rarely follows it downward.
What the CPQ and Billing deals showed, 2024 to 2025
Across roughly 20 to 30 Salesforce CPQ and Billing deals advised:
How far the proposed CPQ seat count exceeded the number of users actually building quotes in the trailing period.
How far optimistic invoice forecasts ran above real volume, with the billing tier bought and paid against the forecast.
Buyers who tied CPQ seats to active quoting roles cut 15 to 30 percent of the initial proposal. The evidence is a report of who generated a quote, which is answerable from the system and gives the same answer whoever asks.
A volume tier does not refund the difference when the volume does not arrive, so an optimistic forecast converts directly into paid capacity.
Watch the briefing · 4:44Shrinking a Salesforce EstateWhy the population you size against decides the bill before any discount does.
Your first five moves
- Run the report of who generated a quote in the trailing period, and treat that as the CPQ population.
- Compare it to the proposed seat count and quantify the gap before responding to the proposal.
- Pull the measured invoice run rate and size the billing tier against it rather than the forecast.
- Price growth as a separate option on both lines instead of embedding it in the commitment.
- Do all of it before the quote is priced. The Salesforce practice builds the population with you.
Frequently asked questions
How oversized are CPQ proposals?
The proposed seat count exceeded active quoting users by 20 to 45 percent across the 20 to 30 deals advised. It is a mis specification rather than simply an aggressive proposal.
Why does that happen?
Because the proposal is sized from the sales organisation. CPQ prices the act of configuring and producing a quote, which a subset performs: deal desk, sales operations, and a portion of the field.
What is the right test?
Behavioural, not organisational. Who has actually generated a quote in the trailing period, which is a report rather than an org chart, and gives the same answer whoever asks.
How much does that save?
Buyers who tied CPQ seats to active quoting roles cut 15 to 30 percent of the initial proposal. The seller has little counter argument because the question is answerable from the system.
What goes wrong with Billing?
Volume tiers were set on optimistic invoice forecasts that ran 30 to 50 percent high, so the tier was bought against a business case rather than against a measured run rate.
Does an unused volume tier refund?
No. A volume tier does not return the difference when the volume does not arrive, which is why an optimistic forecast converts directly into paid capacity for the term.
What should the tier be sized on?
The measured invoice run rate, which is already in the billing data, with expected growth priced as a separate option rather than assumed inside the commitment.
Why is the accurate number not used?
Because it is less convenient to produce. Sales headcount sits in the HR system and the forecast comes from the business case; the quoting population and the run rate both require pulling a report.
When should this work happen?
Before the proposal is priced. A seat count reduced afterwards reads as a negotiating tactic, while the same reduction made beforehand is simply the specification you asked to be quoted.
Should we recheck at renewal?
Yes. Deal desk composition changes over a term, and the seat count rarely follows it downward on its own, so the gap reopens quietly between renewals.
