TL;DR
- A usage quote needs a meter, included units, period, overage rule, commitment and amendment policy. A price printed on a PDF is insufficient.
- DealHub merits evaluation for connected CPQ and subscription billing. Nue is a strong starting point when usage and quote-to-revenue changes are central.
- Salesforce Revenue Cloud fits organisations standardising revenue processes in Salesforce. Conga deserves attention for complex configuration and pricing, with the exact CPQ product and billing scope specified.
- Demonstrate the signed quote becoming the correct billable subscription, including a mid-term amendment and late usage adjustment.
- Price seats, billing scope, implementation and meter operations separately. Do not assume a CPQ licence includes every rating or invoicing obligation.
The quote is a pricing contract
A seller offers a $1,000 monthly platform fee with 50,000 included units and $0.02 overage. The buyer signs. Billing still needs to know what a unit is, when the allowance resets, whether unused units roll over and how usage is assigned to the customer.
CPQ configures the offer, applies pricing rules and produces a quote. Usage billing meters and rates actual consumption. The handoff must preserve the commercial meaning across those systems. A visually accurate proposal can become an incorrect invoice if the meter or effective dates are lost.
Our CRM proposal tools guide owns document generation and signature workflow. The digital sales-room guide covers buyer collaboration. This article concerns the pricing and billing contract behind those documents. The RevOps platform guide provides the wider category context.
Use the RevOps CRM setup playbook to define opportunity, contract, subscription and customer identifiers. A quote number alone cannot reliably join every usage event to the correct amended subscription.
Four product approaches
| Product | Reason to evaluate | Purchasing basis | Requirement to prove |
|---|---|---|---|
| DealHub | Connected CPQ, subscription and billing model | Scoped platform/module offer | Quote terms survive rating and invoicing |
| Nue | Usage-centric quote-to-revenue lifecycle | Scoped offer and usage/billing scope | Meter, pricing tags and change treatment |
| Salesforce Revenue Cloud | Revenue process within Salesforce | Public Growth/Advanced user rates plus scoped billing | Exact product generation and entitled functions |
| Conga CPQ/Smart CPQ | Complex configuration and pricing rules | Exact product, integrations and services quote | Usage contract and billing handoff beyond configuration |
Current documentation was checked on 6 October 2026. No hands-on comparison or invoice-accuracy benchmark is claimed. Products within one vendor's portfolio may have different architecture and entitlements.
Where each provider fits
DealHub: connected quoting and billing
DealHub CPQ describes adaptive price books with fixed, tiered and usage-based structures. Its subscription billing product describes metered pricing and a shared model connecting CPQ, subscription management and billing.
That makes it relevant when the team wants to reduce the translation between sales terms and finance execution. Require a demonstration of the same quote line becoming a subscription with its unit definition, allowance and rating rule intact.
Use a scoped quote identifying CPQ, billing, integrations, users, implementation and support. Choose it when those connected functions match the operating requirement. Avoid assuming a CPQ-only offer includes the complete billing product or every unusual usage commitment. Shared vendor ownership simplifies accountability only if the contract includes the actual end-to-end path.
Nue: usage and lifecycle changes as first-class requirements
Nue's usage billing explanation describes rating events against configured pricing rules. Its Usage API makes transaction, subscription, quantity and event context visible in the interface.
It deserves early evaluation when usage commitments, amendments and several sales motions are central to the purchase. Ask it to show a direct-sales quote, the underlying usage feed, a mid-term change and a corrected invoice. The technical owner should inspect duplicate events, late arrivals and customer-key mapping alongside the seller's quote experience.
No comparable public package price was confirmed in this read. Scope the entire quote-to-revenue offer, including usage volume treatment and services. Choose it for a lifecycle that needs those capabilities; avoid introducing a broad platform merely to replace a static price table for a simple fixed subscription.
Salesforce Revenue Cloud: identify the exact product
Salesforce's Revenue Cloud pricing page lists Growth at $150/user/month and Advanced at $200/user/month, with different scope. Confirm annual billing and the selected functions in the offer, including any separately scoped billing capability.
It is a natural evaluation when Salesforce already governs the product catalogue, sales process and revenue data. Keep the product generation explicit. A legacy Salesforce CPQ implementation and a current Revenue Cloud purchase are not automatically the same architecture or entitlement.
Choose this route when standardisation inside the Salesforce estate is commercially useful. Avoid calculating the entire usage-billing project by multiplying only quote-user seats. Meter ingestion, integration, implementation and finance workflows still need scope and ownership.
Conga: complex pricing with a named configuration
Conga's CPQ portfolio includes current product distinctions, while its service descriptions explain CPQ as configuration, pricing and quote generation. Its Smart CPQ page connects pricing with documents and contracts.
That breadth merits evaluation for a complex catalogue, bundles and pricing rules. Be specific about the product offered, CRM deployment and how the signed usage terms reach the billing engine. A good configurator can still require a substantial integration for rating and invoicing.
Use a tailored offer with licences, implementation, catalogue migration and downstream billing responsibilities. Choose Conga when configuration complexity is the principal constraint. Avoid treating “supports custom pricing” as evidence that the full usage lifecycle works without additional design or modules.
A platform fee and overage example
Use the following hypothetical commercial rule:
- $1,000 platform fee per calendar month.
- 50,000 included processed units per month, without rollover.
- $0.02 for each unit above the included allowance.
- Units counted once when processing succeeds, with a defined correction policy.
At 80,000 units, overage is 30,000 × $0.02 = $600, making the monthly charge $1,600 before tax. At 40,000 units, the charge remains $1,000 under this rule; unused units do not create a credit.
Now compare a tiered offer. If units 50,001–100,000 cost $0.02 and only units above 100,000 cost $0.015, then 120,000 units produce $1,000 + $1,000 + $300 = $2,300. That is graduated pricing. Applying $0.015 to all 70,000 overage units would instead produce $2,050, which is a different volume rule.
The quote must name the rule, not merely say “tiered”. It should also state rounding, minimum increments, measurement period and whether failed processing counts. Customer-facing examples can prevent an apparently small wording difference from becoming an invoice dispute.
A prepaid commitment is another model. Define whether it is a cash balance, a unit pool or a minimum spend, and what happens at expiry. Do not mix a monthly included allowance with an annual commitment unless both reset and drawdown rules are explicit.
Amendments and the billing handoff
A customer upgrades on the 16th. Decide whether the platform fee is prorated, whether included units change prospectively and which usage belongs to the old versus new rate. Calendar days, service days and fixed month conventions produce different amounts; finance should approve the convention.
Persist the signed quote version, order, subscription, price-book version, meter ID, unit definition and effective timestamps. A human-readable description supplements those keys but should not be the only handoff.
For late-arriving usage, preserve event time and receipt time. Rate the event under the applicable period and amendment policy. Deduplicate event IDs so a replay does not bill the same consumption twice. A corrected event should create an inspectable adjustment rather than silently rewriting a settled invoice.
Separate commercial approval from meter correctness. Sales may approve a discount while engineering still needs to prove that the meter measures the agreed activity. A CPQ can enforce the discount policy without establishing the reliability of the underlying event feed.
Budget the operating system
Assume ten Advanced Revenue Cloud users at the public $200 rate: $2,000 monthly equivalent, subject to the selected billing term and scope. This is a licence illustration, not a complete usage-billing quote.
Add assumed meter/integration operations of $300 and eight monthly administration hours at $60. The model becomes $2,780 recurring, before separately scoped billing, taxes and other licences. Initial configuration and acceptance of sixty hours adds $3,600.
For twenty-five quotes a month, recurring cost is $111.20 per quote under this allocation. A team generating 100 quotes sees $27.80, but volume alone does not prove the purchase is better. Count amendments, manual exceptions and invoices requiring correction alongside throughput.
If a vendor offer charges by revenue, usage events or subscriptions, use those units instead of seats. Include annual commitments, implementation milestones, sandboxes and exit exports. Do not compare a small CPQ licence with another provider's complete CPQ-and-billing contract as though the difference were a price premium for the same job.
The decisive buying demonstration is a quote, signed order, usage period, amendment and correction that all reconcile to the same contract. Choose the provider whose scoped product carries that meaning with an operating model your team can maintain.
FAQ
Is usage billing the same as CPQ?
No. CPQ defines and quotes commercial terms; usage billing measures and rates consumption. They can share a platform, but both jobs need explicit scope and a reliable handoff.
What does “tiered” pricing mean?
It can mean graduated bands or a volume rate applied more broadly. Those models can produce different invoices from the same usage. State the exact formula and show examples in the approved quote.
Who should own the unit definition?
Product and engineering should establish what the meter measures, with finance and commercial approval of the billable rule. Sales should not invent a new unit in a free-text quote without a supported measurement path.
Can we change prices mid-contract?
Only within the agreed amendment and contractual rules. Preserve the approved version and effective date, then test usage on both sides of the change. A new price book must not silently rerate old consumption.
