May 21, 2025
Pricing decides whether a quote closes or stalls. Salesforce CPQ supports three pricing models that growing software and B2B companies rely on: block pricing, subscription pricing, and usage-based pricing. Each one charges customers a different way. Block pricing sets a flat price for a quantity range. Subscription pricing bills on a repeating schedule. Usage-based pricing charges for what customers actually consume. The model you pick shapes every quote your sales team sends.
Most sales teams still quote the hard way. They copy last quarter's spreadsheet, change a few numbers, and hope the math holds. That works until a customer asks for tiered volume pricing, a mid-year upgrade, or a bill based on real usage. Then the workarounds break, deals slow down, and revenue leaks. Salesforce CPQ replaces that guesswork with pricing rules the system enforces on every quote. This guide shows how each model works and how to set it up.
By the end, you will know when to use each model and the fields to configure for it. You will also see how to keep your setup accurate as Salesforce moves CPQ into Revenue Cloud Advanced, and where the right implementation partner saves months of trial and error.
Salesforce CPQ controls price with one setting on each product: the Pricing Method field. Change that field, and CPQ charges a different way. The connection between Salesforce and CPQ pricing lives right here. Standard options include list pricing, cost-plus markup, percent of total, and block pricing, plus subscription and usage-based billing for recurring products. Most teams use two or three at once across their catalog.
This guide focuses on the three models that fit modern software and B2B selling: block, subscription, and usage-based pricing. Each answers a different buyer question. How much for this volume? What does it cost per month? What do I pay for what I use? Get these three right, and your quotes match how customers actually buy.
Block pricing sets one fixed price for a whole quantity range instead of a per-unit rate. Buy anywhere from 1 to 50 seats, and you pay one price. Buy 51 to 100, and you pay the next price. Customers see a clear number that matches their volume. The model fits software seats, license bundles, and packaged services well.
Block pricing also speeds up quoting. Reps stop doing per-unit math and stop second-guessing discounts. The price for each block is set once and applied every time. That consistency cuts quoting errors on large orders.
Setup happens on the product record. Follow these steps in order:
Simple block pricing fits a standard rollout. More advanced setups need overage rules for quantities above the top block, plus automation to handle edge cases. A skilled team gets these rules right the first time, so a quote never returns a blank or wrong price. For a hands-on view, this block pricing walkthrough shows the fields in action.
Block pricing works best when you sell in tiers and want predictable numbers. Volume licensing, seat bundles, and fixed service packages all fit. It helps less when every unit carries the same price, or when consumption changes month to month.
Subscription pricing charges customers on a repeating schedule, usually monthly or yearly. It suits any product people use over time, such as software, media, or support plans. Salesforce CPQ handles the recurring terms and the proration math for you. Teams do less manual work, and customers get steady, predictable bills. The business gains recurring revenue it can forecast. Community guides like these subscription setup tutorials cover the common term settings.
Configure subscription pricing on the product and the quote:
Salesforce CPQ then prorates partial terms on its own. A customer who starts mid-month pays only for the days they get. That accuracy matters most when you bill thousands of contracts with different start dates. Clean proration and billing-system links are where a Revenue Cloud implementation partner earns its keep.
Usage-based pricing, or pay-as-you-go, charges for what customers actually consume. There is no flat monthly fee. Customers pay for the API calls, gigabytes, or minutes they use. The model feels fair and clear, which builds trust with startups and large enterprises alike. It is common in cloud software, telecom, and utilities, where usage swings month to month. You can see practical usage-based billing examples in most CPQ developer write-ups.
This model needs more moving parts than the other two:
Accurate metering is the hard part. If usage data lands late or double-counts, the bill is wrong and trust drops. This is an integration and data-quality problem, not just a CPQ setting. The right Salesforce integration work keeps every invoice defensible.
No single model wins for every product. Many companies run all three across one catalog. A seat-based tool might use block pricing, its support plan might use subscription pricing, and its API might bill on usage. The table below shows how each model charges, who it fits, and how the quote looks. Use it as a quick gut check before you build, then confirm the details with a short pricing review.
Once the model is set, the rules still need upkeep as products change. Many teams hand ongoing rule changes to a managed services team so pricing stays accurate without pulling admins off other work.
Salesforce has renamed and repackaged this product line. New CPQ capability now ships under Revenue Cloud Advanced, part of what Salesforce calls Agentforce Revenue Management. Existing Salesforce CPQ orgs keep running, and most admins still call the tool "Salesforce CPQ," or CPQ SFDC in day-to-day chat. So the pricing models in this guide still apply. The names on Salesforce's product pages have simply moved on.
Two takeaways follow. First, when you research setup steps, expect to see both the old and new names side by side. Second, if you are weighing a move, plan the pricing rules early. Product records, block prices, and subscription terms all need to map cleanly, which is the heart of migrating from legacy CPQ to Revenue Cloud Advanced. Salesforce changes this roadmap often, so check its current product and pricing pages before you commit. Treat any dated figure you find, including in this article, as something to verify at the source.
Software gets you the fields. A plan gets you accurate quotes. The gap between the two is where most projects stall. Picking the right Salesforce CPQ solution means matching the model to how you sell, then building rules the system can enforce without a rep watching every deal.
Good Salesforce CPQ services cover more than clicks. A capable partner maps your product catalog, sets overage and proration rules, connects billing, and tests edge cases before go-live. Ask any team how they handle a mid-term upgrade, a usage spike, or a block boundary. The answer shows how deep their engineering goes. Strong Salesforce implementation services also document the setup, so your own admins can maintain it later.
Watch for three warning signs during a build. Quotes that need manual fixes point to missing rules. Prices that differ between reps point to weak governance. Renewals that take hours point to poor proration setup. A good partner closes these gaps before go-live, then hands you a system your team can run without constant help.
Salesforce CPQ offers list pricing, cost-plus markup, percent of total, and block pricing, plus subscription and usage-based billing. You set the method per product with the Pricing Method field. Most catalogs mix several methods across the product list.
Yes. Existing orgs keep running. Salesforce now sells new capability as Revenue Cloud Advanced under Agentforce Revenue Management. The pricing models work the same way. Check Salesforce's current pages for the latest packaging.
Salesforce does not publish a single fixed price. Cost depends on edition, user count, and setup work, and it is quoted per company. Ask Salesforce or a partner for a current quote rather than trusting a figure you read online, including older blog posts that may now be stale.
Match the model to how customers buy. Use block pricing for volume tiers, subscription pricing for recurring access, and usage-based pricing for pay-as-you-go consumption. A short discovery with a Salesforce CPQ consulting team settles most cases.
Flexible pricing only pays off when the setup holds under real deals. That is the work Minuscule Technologies does as a Salesforce engineering partner. We build block, subscription, and usage-based pricing that quotes cleanly at scale, not just in a demo.
Our teams bring pricing Accelerators and Starter Packs that shorten setup, plus pre-built components for overage rules, proration, and billing integration. A tested implementation framework keeps your rules documented and your admins in control, whether you stay on Salesforce CPQ or move to Revenue Cloud Advanced.
Ready to match your pricing to how customers actually buy? Book a free strategic Salesforce call, and we will map the right model for your catalog and your team.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
