Quoting in Salesforce: standard Quotes, CPQ or Revenue Cloud?

If your products have list prices, a handful of price books covers your markets, and discounts need only a simple approval, Sales Cloud’s standard Quotes are usually enough. You need a configure-price-quote tool when product rules, pricing logic, subscriptions or discount governance outgrow what reps can get right by hand. On Salesforce, the current product for that is Revenue Cloud, sold in Growth and Advanced editions, while many existing orgs still run the earlier Salesforce CPQ.

What standard Quotes already do

Standard Quotes are included in Sales Cloud and are underused. A quote is built from the products on an opportunity, priced from a price book, and turned into a customer-facing document. Price books handle different markets or currencies, products can carry one-time or recurring prices, and approval processes can route a quote to a manager when a discount crosses a threshold you set.

That is enough for a lot of companies. A multi-region technology-services firm we worked with needed a product catalog and multiple price books for US and Middle East markets, covering both one-time and recurring revenue. That was delivered as Sales Cloud configuration within a 20-hour Jumpstart, a reminder to check what standard quoting can do before buying more.

Signs you have outgrown standard quoting

• Products depend on each other: some options require, exclude or include others, and reps get the combinations wrong.
• Price depends on a calculation, such as quantity tiers, measurements, term length or usage, rather than a fixed list price.
• Quotes are built in spreadsheets and pasted into Salesforce, so the quote and the opportunity disagree.
• Discount approvals happen in email or chat, and nobody can say who approved what.
• Subscriptions, renewals and mid-term changes are tracked outside Salesforce.
• Finance re-keys every closed deal into billing or ERP.

One or two of these can often be solved with configuration and Flow. Several together are the usual signal that a CPQ tool will pay for its complexity.

Look downstream as well as at the quote itself. If the accepted quote has to become an order, a contract, a subscription and an invoice, decide early which of those live in Salesforce and which belong to your ERP or billing system. A CPQ tool that produces a perfect quote but hands finance a spreadsheet has only moved the problem. The integration pattern between Salesforce and the ERP is usually the part of the scope with the most unknowns, so design it before configuring pricing rules, not after.

The current Salesforce quoting lineup

Salesforce has renamed and repackaged its quoting products more than once, so check names and editions with your account team before you budget. As of this review, the lineup looks like this:

Salesforce describes Revenue Cloud as built on a single, attribute-based product catalog with a configurable pricing engine. If you run the earlier Salesforce CPQ today, the practical question is not whether to replace it immediately but whether new work should be built there or planned around Revenue Cloud. That is worth settling before starting a large redesign.

Scoping the product catalog

Catalog design decides how painful every later change will be. Model products the way customers buy them, not the way the ERP stores them, and separate the things that change often (prices, promotions) from the things that rarely do (what a product is and what it requires). A painting and construction company we worked with kept separate product catalogs and pricing for its painting, drywall, construction and mold-remediation divisions, with guided selling that calculated labor and materials from square footage by job type. Each division sold differently, and the catalog reflected that.

• List every product, bundle and option you actually sold last year; retire the rest before migrating anything.
• Write down every configuration rule: what requires, excludes or includes what.
• Identify every input that drives price: quantity, term, region, measurement, customer tier or usage.
• Decide which system owns the product master, Salesforce or the ERP, and how changes flow between them.
• Name an owner for catalog changes after go-live, usually in sales operations or product marketing.

Pricing and approval rules

Pricing logic usually lives in a few people’s heads and a spreadsheet nobody else fully understands. Get it written down and agreed before configuration starts: the order in which discounts apply, which are automatic and which are negotiated, and the floor below which a deal needs approval. Then design approvals around risk. A rule that routes every quote to the CFO will soon be worked around. Tiered thresholds by discount level, deal size or non-standard terms keep approvals meaningful, and an audit trail on the quote shows exactly who approved each exception.

Quoting from the field

Quoting does not have to happen at a desk. For the painting and construction company, estimators produce professional quotes on iPads with in-field e-signature, and approved timesheets flow into work orders and opportunities so managers see job costs against the estimate. The lesson carries over to most CPQ projects: the quote is the start of the revenue process, so design how it connects to orders, delivery and billing, not only how it looks.