Steelbrick implementation cost: Salesforce CPQ, Revenue Cloud and what quotes include

Steelbrick is a name you now meet mostly in metadata. The product Salesforce bought in 2016 became Salesforce CPQ, and its objects still carry the SBQQ prefix in every org that installed it. When someone asks what a Steelbrick implementation costs today, they are really asking one of two questions. What will it cost to keep, fix or extend the Salesforce CPQ we already run? Or what will it cost to move quoting onto Revenue Cloud, which is what Salesforce now sells instead? The answers are different, and so are the bills.

#Where Salesforce CPQ stands

Salesforce stopped selling CPQ to new customers on 27 March 2025. Existing customers can keep using it and renew it, and many will for years, because a working quote engine with a decade of pricing logic inside it is not something a sales operation replaces lightly. New buyers, and existing customers who want the newer architecture, are offered Revenue Cloud.

That changes the cost conversation in three ways. A new CPQ build is no longer something a new customer can buy, so any proposal you receive for a fresh quoting implementation will be priced on Revenue Cloud. Existing CPQ customers face a choice between investing in what they have and planning a move. And because the two products use different data models, a move is a reimplementation, not an upgrade.

We have not found a current public list price for Salesforce CPQ on Salesforce's own pricing pages, so treat renewal pricing for an existing CPQ subscription as quote-only and set by your contract.

#What Revenue Cloud costs, as at October 2026

Salesforce publishes Revenue Cloud prices on its Revenue Cloud pricing page. The figures below were read on 11 October 2026. Both editions are per user per month, billed annually, and the Australian figures are those shown on the page's Australian dollar view.

The same page answers the question buyers most often get wrong: "Revenue Cloud is a paid add-on. It is a separate product that you purchase in addition to your standard Sales Cloud subscription." A footnote adds that it requires a Sales Cloud, Service Cloud or CRM licence. In other words, a sales rep who quotes needs a CRM licence and a Revenue Cloud licence, and the Revenue Cloud cost sits on top of whatever you already pay.

The arithmetic is simple. Forty quoting users on the growth edition is US$6,000 a month at list, or US$72,000 a year, before the CRM licences underneath. The same forty users on the advanced edition is US$96,000 a year at list. The difference between the two editions is mainly about what happens after the quote: contracts, orders, usage-based charging and invoicing. If billing lives in an ERP and will stay there, the growth edition may be all the quoting team needs. If you want invoicing inside Salesforce, the advanced edition is the one Salesforce lists with Consumption and Invoicing.

Count users carefully. Revenue Cloud is licensed per user, so the question is who creates and edits quotes, not who views them. Sales operations, deal desk and finance users who approve or adjust pricing may need a licence; a manager who only reads a dashboard may not. Get your account executive to confirm which roles need which licence before you build a budget around a headcount.

#Staying on Salesforce CPQ: what drives the cost

Many CPQ orgs need work whether or not they ever move. Years of quick fixes leave behind product rules that contradict each other, price rules that fire in an order nobody remembers, and a quote calculator plugin full of JavaScript written by a contractor who left. A remediation project on CPQ is usually smaller than a move, and it has a second benefit: a clean configuration is much easier to reimplement later.

The cost of that work is set by a short list of things.

Products and bundles. The number of products, how many are bundled, and how deep the bundles go. Nested bundles with option constraints take far longer to test than flat price lists.

Product rules and price rules. Validation, selection, alert and filter rules, and the price rules and lookup tables behind them. Count them and ask how many are still in use.

Discount schedules and contracted prices. Volume and term discounts, partner pricing and customer-specific contracted prices all need testing against real deals.

The quote calculator plugin. Custom JavaScript in the calculator is powerful and fragile. Every line has to be understood before it is changed or rebuilt.

Quote templates and document generation. Quote documents with conditional sections, line columns and terms often take more effort than the pricing logic.

Approvals. Advanced Approvals, standard approval processes or custom flows, and the rules that decide who signs off a discount.

Amendments and renewals. Contracted subscriptions, co-termination, amendment quotes and renewal forecasting are where CPQ is hardest to get right, and where most defects show up months after go-live.

Billing. If you also run Salesforce Billing on top of CPQ, its objects and invoicing runs widen the scope considerably.

#Moving to Revenue Cloud: why it is a reimplementation

Revenue Cloud is built natively on the core platform, with its own product catalogue, pricing procedures, configurator and quote and order objects. Salesforce CPQ is a managed package with its own SBQQ objects. Nothing installs over the top of the other. Your pricing logic, bundle structures and rules have to be redesigned in the new model, and that redesign is where most of the effort goes.

The design work is not a translation exercise. Some CPQ patterns map cleanly. Others exist only because of a limitation in the old package, and the right answer in Revenue Cloud is to drop them. A good partner will tell you which is which in discovery, before anyone builds anything.

The hardest part is data in flight. Open quotes can usually be closed out or recreated. Active contracts and subscriptions cannot, because amendments and renewals depend on them. Decide early whether you will migrate active subscriptions into Revenue Cloud, run both products until existing contracts renew, or draw a hard cutover date and convert everything at once. Each choice has a different cost, and each changes how long you pay for both licences. Ask every bidder whether any Salesforce migration tooling applies to your configuration, and what it does not cover.

#Three decisions to make before you ask for a price

The fastest way to get comparable proposals is to settle three questions internally first. Bidders will otherwise answer them for you, differently, and their prices will reflect their assumptions rather than your business.

Fix, extend or move? If CPQ works and the problem is a messy configuration, a remediation project is the honest answer, and some firms will tell you so even though a move would be a larger engagement for them. If you need capabilities CPQ does not have, or your renewal terms make Revenue Cloud attractive, the move is worth pricing. If you are not sure, pay for a short, fixed-scope assessment that ends in a written recommendation, and ask that it be delivered by people who would not automatically win the larger project.

Where does billing live? This decides the edition, the integration scope and much of the testing. Quoting that hands an order to an ERP for invoicing is a smaller project than quoting, ordering, usage rating and invoicing all inside Salesforce. Many organisations find the invoicing question is really a finance decision, and it should be made by finance before the project starts.

How much history comes across? Every year of quotes, contracts and subscriptions you migrate adds mapping, testing and reconciliation. Some businesses need full history for renewals and revenue reporting. Others can archive closed deals and migrate only what is live. The difference in effort can be large, and it is a business decision, not a technical one.

Write the three answers down and send them with the request for proposal. A bidder who disagrees with one of them can say so, and that disagreement is useful information in itself. What you want to avoid is three proposals that each quietly assume a different answer, because then the cheapest quote is simply the one that assumed the least.

There is one more reason to be explicit. Quote-to-cash projects touch revenue reporting, commission calculations and sometimes revenue recognition. Finance and sales leadership will want to know, before go-live, that a deal priced in the new system produces the same total, the same contract dates and the same renewal amount as it would have in the old one. Building that reconciliation into the plan from the start costs far less than discovering the gaps at quarter end.

#The work packages in a quote-to-cash quote

Whether you are fixing CPQ or moving to Revenue Cloud, a comparable quote names the same packages.

Discovery covers the product catalogue, pricing logic, rules, templates, approvals, integrations, and the full life of a deal from quote to renewal. Design produces the target catalogue and pricing model and a decision on billing. Build covers configuration, any custom code, templates and approvals. Data migration covers products, price books, and the open contracts and subscriptions you decide to bring across. Integration links quoting to your ERP for orders and invoices, to a contract lifecycle tool or e-signature service, and sometimes to a tax engine. Testing must use real historical deals, priced in both systems, with differences explained line by line. Training is for sales reps, deal desk and finance, who each use the product differently. Cutover and hypercare follow, ideally timed away from quarter end.

#Hidden costs and the questions to ask

Licence overlap. If you move, you will pay for CPQ and Revenue Cloud together for a period. Agree the overlap with Salesforce before you sign.

A Full Copy sandbox. Testing pricing against real deal volumes needs realistic data. If you do not already have a Full Copy sandbox, price one.

Data storage. Quote lines, subscriptions and asset records add up quickly. Check your storage headroom.

Document generation and e-signature. Licences for a document tool or signature service may sit outside both Salesforce products.

ERP integration changes. If orders and invoices flow to an ERP, the interface changes when the objects change.

People. Sales reps relearn quoting, the deal desk relearns approvals, and admins need new skills; a team certified on CPQ is not automatically ready for Revenue Cloud. Budget for training and for the drop in productivity in the first weeks.

Support. Premier Success is priced as a share of net licence fees, so a larger licence means a larger support line.

When you request quotes, give every bidder the same inventory: user counts by role, product and bundle counts, rule counts, templates, approval chains, active contracts and subscriptions, billing scope and integrations. Ask each to state whether active subscriptions are migrated, how many historical deals they will use to test pricing, and how long both products will run together. Quotes that answer those three questions can be compared.

#Where to go next

Renewal and licence questions are on the Steelbrick licence cost page. The acquisition history is on what happened to Steelbrick, and the product as it stands is described on the Salesforce CPQ page. To choose a firm, read who to hire for Steelbrick. For ERP and billing links, see integrating Steelbrick with Salesforce, and for the stay or move decision, should I migrate from Steelbrick works through the trade-offs. Our Revenue Cloud service page covers how we run these projects.