Executive Summary
Salesforce CPQ, originally Steelbrick CPQ, is best understood as a mature managed-package CPQ application centered on sales-led quoting, product bundles, pricing rules, approvals, and quote documents. It typically works well when the business process is quote-centric, Sales Cloud is the primary channel, and downstream contract/order/billing capabilities are handled by separate Salesforce, ERP, or billing systems.
Salesforce Revenue Cloud / Agentforce Revenue Management is positioned as a broader revenue lifecycle platform: product catalog, pricing, CPQ, contract/order/asset lifecycle, order orchestration, billing schedules, consumption and invoicing, revenue analytics, and Agentforce-assisted workflows. It is a better fit when the company wants a single CRM-native product-to-cash architecture across sales, partners, self-service, finance, legal, operations, and service teams.
Terminology note: Salesforce branding has moved toward Agentforce Revenue Management and Revenue Lifecycle Management. In this document, “Revenue Cloud” refers to the modern Revenue Cloud / Agentforce Revenue Management family unless a specific older managed package is explicitly mentioned.
Feature Sections
- Platform positioning and architecture
- Product catalog and product model
- Product configuration / bundles
- Pricing, discounts, promotions, and approvals
- Quote creation and quote documents
- Contracts and CLM
- Orders, decomposition, and orchestration
- Assets, subscriptions, amendments, renewals, cancellations
- Billing, invoicing, usage, and wallet
- Analytics, AI, and Agentforce
- Decision guidance
1. Platform Positioning and Architecture
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
Internal sellers, deal desk, sales managers, and CPQ admins create, price, approve, and output sales quotes from opportunities. External usage is usually indirect through partners or customer portals that call CPQ logic with custom UX/integration. The primary journey is Opportunity → Quote → Approval → Document → Contract/Order handoff.
Supports a broader journey: product launch → sell through any channel → configure/price/quote → contract → order capture → fulfillment orchestration → billing/invoicing → renewal/asset lifecycle. Personas include sellers, partners, customers, product managers, pricing managers, legal, finance, fulfillment ops, customer success, and service users.
Licensing requirements
Requires Salesforce CPQ licenses/package plus base CRM licenses such as Sales Cloud/Service Cloud/Platform as contracted. Add-ons are often needed for Advanced Approvals, Billing, CLM, partner/community access, or document generation beyond standard needs.
Revenue Cloud Growth and Advanced are paid add-ons requiring prerequisite CRM licensing. Public pricing as of the generated date lists Growth at USD 150/user/month and Advanced at USD 200/user/month, billed annually; Revenue Cloud Billing is shown as a separately sold add-on.
Data model
Mix of Salesforce standard objects and SBQQ managed-package objects. Standard: Account, Contact, Opportunity, Product2, Pricebook2, PricebookEntry, Contract, Order, Asset depending on setup. CPQ-specific: SBQQ__Quote__c, SBQQ__QuoteLine__c, SBQQ__ProductOption__c, SBQQ__ProductFeature__c, SBQQ__ProductRule__c, SBQQ__PriceRule__c, SBQQ__DiscountSchedule__c, SBQQ__QuoteTemplate__c, SBQQ__Subscription__c, and related rule/action/condition records.
Uses more Salesforce platform-standard revenue objects where available and extends them with Revenue Cloud capabilities. Standard: Account, Contact, Opportunity, Quote/QuoteLineItem or transaction equivalents, Product2, Pricebook2, Order/OrderItem, Contract, Asset. Revenue Cloud-specific or Revenue Cloud-modified areas include product catalog management, attribute/constraint model, pricing procedure/elements, transaction/cart/quote lines, order decomposition/orchestration, asset action, billing schedules, usage rating, invoice/subledger, and revenue analytics objects. Exact API names can vary by edition/package and should be validated in Object Manager.
Automations provided
Quote calculator, product and price rules, guided selling, advanced approvals, quote-to-contract/subscription records, renewal quote generation, amendment quote generation, document generation, quote synchronization, and event hooks/plugins.
Built-in flows/services for guided quoting, catalog/pricing reuse across channels, Agentforce quote assistance, contract/order/asset lifecycle, order decomposition and orchestration plans, downstream initiation for fulfillment/billing/revenue recognition, automated notifications, and analytics.
Configuration effort
Medium to high. Architects configure package settings, quote process, products, options, features, rules, price rules, approval rules, templates, contract/renewal/amendment behavior, and integrations.
High for enterprise implementations because more of the product-to-cash chain is modeled. Setup includes catalog, pricing, configurator, channel, transaction, order, contract, asset, billing, orchestration, analytics, and access model design.
Common customizations
Custom Quote Calculator Plugin, custom Lightning components, custom guided selling screens, custom document output, custom approval conditions, ERP/Billing integrations, custom sync fields, and automation around quote lifecycle.
Custom catalog/channel UX, API integrations with PIM/ERP/fulfillment/tax/revenue recognition, custom pricing functions, orchestration enrichments, custom Agentforce actions, data migration from CPQ/SBQQ, and governance dashboards.
2. Product Catalog and Product Model
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
Best for sales cataloging of products, bundles, options, features, subscription terms, and price book entries. Product admins and CPQ admins maintain bundles used by sellers and deal desk. External users usually consume the catalog through custom Experience Cloud or commerce integrations.
Best when product managers need a unified, attribute-based catalog reusable across sales, partners, self-service, commerce, service, and downstream billing/fulfillment. Supports internal product/pricing teams and external buyer/partner journeys with a more governed product-to-cash catalog.
Licensing requirements
CPQ license for users configuring/administering and usually Sales Cloud for sellers. Partner/community access may need Experience Cloud plus CPQ-compatible integration design.
Revenue Cloud Growth generally covers CPQ/catalog basics; Advanced expands across contracts, orders, consumption, invoicing, AI, and analytics. Billing add-on may be separately required for advanced billing.
Data model
Standard Product2, Pricebook2, PricebookEntry. CPQ-specific: Product Option, Product Feature, Configuration Attribute, Product Rule, Option Constraint, Product Action, Discount Schedule, Block Price, Cost, Subscription Pricing metadata.
Standard Product2/Pricebook foundations plus Revenue Cloud catalog constructs for attribute-based catalog, categories, product relationships/components, compatibility/constraint definitions, selling models, and channel exposure. Some standard product/price book records may be enriched with Revenue Cloud fields and related records.
Automations provided
Bundle expansion, option selection, dynamic option filters, product rules for validation/alert/selection, configuration attributes, and defaulting logic during configuration.
Unified product catalog publication, catalog exposure across channels, constraint builder support, product relationship/compatibility enforcement, and pricing/catalog services invoked by quotes, orders, portals, or integrations.
Configuration effort
Medium. Bundle structure can become complex when many features/options/rules are created directly by CPQ admins.
Medium to high. Requires up-front product modeling discipline: attributes, relationships, constraints, selling models, channel availability, lifecycle/version governance, and integration boundaries with PIM/ERP.
Common customizations
Custom product selection UX, dynamic option filtering logic, QCP-driven defaults, mass catalog maintenance tooling, and integration from external PIM.
Catalog APIs, PIM synchronization, product hierarchy governance, custom constraint functions, custom channel-specific catalog presentation, and migration mapping from SBQQ bundle/options to Revenue Cloud catalog structures.
3. Product Configuration / Bundles
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
Sellers configure bundles inside the CPQ quote line editor, using guided selling and product rules to prevent invalid combinations. Personas: sales reps, solution engineers, deal desk, CPQ admin.
Sellers, partners, customers, or agents configure products using a modern configurator and constraint model. The same configuration logic can support multiple channels and downstream order/fulfillment needs.
Licensing requirements
CPQ license for users performing configuration. Advanced Approvals or Billing separate if needed.
Revenue Cloud Growth includes quoting/configurator capabilities; Advanced adds broader lifecycle capabilities around contracts, orders, consumption, invoicing, AI, and analytics.
Data model
SBQQ bundle objects: Product Option, Feature, Option Constraint, Configuration Attribute, Product Rule, Error Condition, Product Action. Quote output is stored on SBQQ Quote Lines.
Standard Product2 enriched by Revenue Cloud catalog/configuration structures such as components, attributes, constraints, and transaction lines. Configuration output is designed to flow into quotes/orders/assets/billing rather than being quote-only.
Automations provided
Validation, alert, selection, filter, and configuration rules; reconfiguration of existing subscriptions/assets through amendment/renewal flows.
Constraint Builder, configurable pricing engine invocation, product compatibility enforcement, agent-assisted quote creation/update, and downstream preservation of configured commercial/technical attributes.
Configuration effort
Medium. Straight bundles are quick; complex nested bundles and rule-heavy catalogs become hard to govern.
Medium to high. More design effort up front but better suited to reusable, multi-channel, attribute-driven configuration.
Common customizations
QCP, custom option filters, custom line editor columns/actions, custom rules for edge cases, custom “solution builder” interfaces.
Custom constraint functions, custom UI for industry-specific guided configuration, external engineering/configurator integrations, and order-decomposition enrichment based on configuration.
4. Pricing, Discounts, Promotions, and Approvals
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
Deal-specific quoting: list price, contracted price, discount schedules, block pricing, percent-of-total, partner/customer-specific prices, and approvals. Personas: sales rep, deal desk, finance approver, sales manager.
Enterprise pricing strategy across channels and revenue models: configurable pricing engine, reusable pricing procedures, volume/compound/proportional discounts, margin visibility, promotions, and governed approval chains. Personas add pricing managers, product managers, partner managers, and revenue operations.
Licensing requirements
CPQ license; Advanced Approvals may require additional package/license depending on contract. External pricing calls may need integration or platform licenses.
Revenue Cloud Growth for CPQ/pricing basics; Advanced for AI/analytics and broader lifecycle. Pricing add-ons and billing usage may vary by contract.
Data model
Standard PricebookEntry plus SBQQ Contracted Price, Discount Schedule/Tier, Block Price, Cost, Price Rule, Price Condition, Price Action, Lookup Query, Summary Variable, Quote Line price fields.
Standard Product/Pricebook foundations plus Revenue Cloud pricing procedures/elements, price adjustments, transaction line pricing details, approvals, margin/cost inputs, and analytics objects. Revenue Cloud may modify/enrich standard objects with revenue lifecycle fields.
Automations provided
CPQ calculator sequence, price rules, discount schedules, advanced approvals, special price/prorate calculations, subscription term/proration, contracted price lookup.
Configurable pricing engine callable across business processes, systematic pricing sequences, pricing visibility, approval automation, Agentforce quote modifications, pricing analytics, and integration with billing/revenue lifecycle processes.
Configuration effort
Medium to high. Architects must understand CPQ calculator order of operations and governance of price rules and QCP.
High for sophisticated pricing. Requires pricing architecture: procedure design, reusable adjustments, policy ownership, external tax/cost integrations, approval chains, and test data strategy.
Common customizations
QCP for custom math, external pricing calls, custom approval matrices, custom quote line fields, and custom margin/cost logic.
Custom pricing functions/services, external pricing/AI optimization integration, pricing simulation dashboards, custom approval routing, and policy-as-code governance for complex deal controls.
5. Quote Creation and Quote Documents
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
Classic seller journey: create quote from opportunity, add/configure products, calculate, discount, approve, generate PDF, sync primary quote. Primary users are internal sellers and deal desk.
Quote creation can be seller-, partner-, customer-, or agent-assisted. Revenue Cloud positions Agentforce to generate/update/send quotes while respecting rules, product bundling, pricing, and role-based access.
Licensing requirements
CPQ licenses; document generation may be native CPQ templates or external tools such as Conga/DocuSign Gen depending on requirements.
Revenue Cloud license; Agentforce capabilities and document/CLM/e-sign capabilities may require additional entitlements or add-ons depending on scope.
Data model
SBQQ Quote, Quote Line, Quote Document, Quote Template, Template Section/Content, Quote Terms, Proposal Document records, plus Opportunity and Account.
Standard Quote/transaction records plus Revenue Cloud transaction line data, contract/order handoff structures, templates/CLM records where enabled, and Agentforce-generated quote action metadata. Validate exact model in target org.
Automations provided
Quote calculator, primary quote sync, template merge, approvals, amendment/renewal quote generation, document output.
Guided workflows, Agentforce quote creation/update/summarization, role-based access, quote-to-contract/order continuity, quote data reuse for billing and lifecycle analytics.
Configuration effort
Medium. Requires quote process, line editor fields/actions, templates, approvals, sync mapping, and document language/format rules.
Medium to high. Requires quote UX, lifecycle states, agent controls, document/contract integration, order conversion, access, and channel-specific journeys.
Common customizations
Custom quote document templates, additional quote actions, quote validation screens, custom integration status, custom line editor plugins.
Custom Agentforce actions/prompts, custom quote-to-contract generation, external document redlining/e-sign integration, and partner/customer self-service quote UX.
6. Contracts and Contract Lifecycle Management
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
CPQ can create contracts/subscriptions from contracted quotes and supports renewals/amendments. Legal workflows are often handled by an external CLM tool or Salesforce add-on. Personas: seller, deal desk, legal ops, renewals team.
Revenue Cloud positions contracting as a CRM-native lifecycle: create/update contracts, clause libraries, templates, redlining, approvals, e-signature integrations, obligation management, and contract changes tied to renewals/amendments/orders.
Licensing requirements
CPQ license for contract generation from quotes; CLM usually separate if full redlining/clause workflows are needed.
Revenue Cloud Advanced includes contracts in the edition comparison; full CLM/e-signature capabilities may depend on selected Salesforce products/add-ons and third-party integrations.
Data model
Standard Contract plus SBQQ Contracted Price, Subscription, Subscription/Asset relationships, Order/Order Product if order generation enabled.
Standard Contract enriched with Revenue Cloud contract lifecycle records, clause/template/approval/obligation data, and relationships to orders, assets, billing schedules, and lifecycle actions.
Automations provided
Contracted quote conversion, subscription records, renewal opportunity/quote generation, amendment quote generation.
Contract creation/update workflows, template/clause selection, review/approval routing, redlining support, e-signature integration, obligation tracking, and lifecycle-driven contract changes.
Configuration effort
Medium if only CPQ subscription contracts; high when integrating CLM, legal approvals, redlining, and e-signature.
High. Requires legal templates, clause library, lifecycle statuses, permissions by legal/sales/finance, approval policies, e-signature, and obligation governance.
Common customizations
Custom contract fields, renewal/amendment automation, external CLM integration, negotiated term mapping, custom document packages.
Custom clause rules, negotiated-term extraction, obligation triggers, integration to repository/e-sign tools, custom legal intake and exception workflows.
7. Orders, Decomposition, and Orchestration
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
CPQ can generate orders/order products from quotes, but orchestration is usually implemented in Salesforce Flow, MuleSoft, ERP, industry clouds, or external order management. Personas: sales ops, order ops, fulfillment teams.
Revenue Cloud includes order automation, decomposition of commercial orders into technical fulfillment orders, orchestration plans, dependencies, exception visibility, and downstream initiation for fulfillment, compensation, revenue recognition, and billing.
Licensing requirements
CPQ plus Sales Cloud; Salesforce Order Management or external OMS is separate if needed.
Revenue Cloud Advanced lists Contracts & Orders and order/asset lifecycle capabilities; billing/advanced order management may require additional add-ons.
Data model
Standard Order and OrderItem; SBQQ quote/order linkages. Any technical fulfillment task model is usually custom or external.
Standard Order/OrderItem plus Revenue Cloud order decomposition, orchestration plan, fulfillment task, dependency, enrichment, and exception records. Downstream target records can include billing schedules, invoices, assets, and fulfillment-system payloads.
Automations provided
Quote-to-order generation and custom Flow/Apex handoff. Limited native decomposition.
Design-canvas orchestration plans, decomposition rules, adaptive orchestration, exception/fallout handling, execution/enrichment rules, and event-driven downstream task initiation.
Configuration effort
Low to medium for simple order generation; high when building custom orchestration and integrations.
High. Architects define commercial-to-technical decomposition, dependencies, orchestration steps, system integrations, fallout handling, SLAs, and operational dashboards.
Common customizations
ERP order payload mapping, custom fulfillment task objects, Flow/Apex integrations, status sync, retry/error handling.
Custom decomposition enrichment, integration adapters, orchestration step extensions, custom exception queues, SLA dashboards, and order fallout remediation components.
8. Assets, Subscriptions, Amendments, Renewals, and Cancellations
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
Strong subscription amendment/renewal quoting for sales-led renewals. Users see existing subscriptions/assets and generate amendment or renewal quotes. Personas: renewals reps, account executives, customer success, deal desk.
Asset lifecycle is a first-class journey: products/services/entitlements owned by the customer can be amended, renewed, canceled, upsold, or tracked for ARR/NRR and churn risk. Personas include sellers, customer success, service, finance, and account teams.
Licensing requirements
CPQ license; Billing, Service Entitlements, or external subscription billing may require separate licenses.
Revenue Cloud Growth includes subscriptions; Advanced includes broader lifecycle plus consumption/invoicing/AI/analytics. Billing add-on may be required for advanced invoicing/rating.
Data model
SBQQ Subscription records, standard Asset optionally, Contract, Contracted Price, Renewal Opportunity/Quote, Amendment Quote, Order/OrderItem if enabled.
Standard Asset/Contract/Order with Revenue Cloud asset lifecycle/action structures, billing schedule links, subscription revenue measures, product/service entitlement relationships, and renewal/amend/cancel transaction records.
Automations provided
Renewal forecast, renewal opportunity/quote creation, amendment quote creation, co-termination, proration, uplift, and subscription quantity/term changes.
Automated customer notifications, asset action flows, amend/renew/cancel support from account view, MRR/ARR tracking, upsell/churn insights, and synchronized lifecycle changes across contract/order/billing.
Configuration effort
Medium to high. Subscription term, proration, renewal uplift, amendment behavior, evergreen contracts, and co-term logic must be carefully configured.
High. Requires unified lifecycle model and alignment among sales, service, finance, billing, customer success, and data/reporting teams.
Common customizations
Custom renewal forecasting, entitlement sync, customer success dashboards, custom co-term logic, renewal quote templates.
Lifecycle action extensions, custom health/ARR metrics, billing-system sync, automated churn/upsell playbooks, external entitlement provisioning integrations.
9. Billing, Invoicing, Usage, and Digital Wallet
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
CPQ prepares commercial terms and can integrate to Salesforce Billing or third-party billing/ERP. Finance users usually work outside CPQ unless Salesforce Billing is installed.
Revenue Cloud Billing is positioned to unify selling and billing, support charge types/payment schedules, usage rating, digital wallet, invoicing engine/document production, and accounting subledger. Personas: finance, billing ops, revenue accounting, sales ops, customer support.
Licensing requirements
Salesforce Billing or external billing product is separate from CPQ in many contracts.
Revenue Cloud Billing is listed as a separately sold add-on from prerequisite products and requires an annual contract.
Data model
CPQ commercial data: quote lines, subscriptions, orders, order products. Billing-specific objects come from Salesforce Billing package or external billing system.
Revenue Cloud Billing objects for billing schedules, usage, rating, wallet, invoices, invoice documents, payments/adjustments, accounting subledger, and links back to quote/order/asset/contract records. Validate exact object names in installed packages.
Automations provided
Quote/order handoff and custom integration. Native billing automation comes from Salesforce Billing if separately implemented.
Billing schedule generation, usage rating, wallet consumption, invoice generation/document production, subledger creation, and exception/health analytics.
Configuration effort
High when end-to-end quote-to-bill is required, because CPQ-to-billing mapping, tax, revenue recognition, invoices, credits, and ERP sync must be designed.
High. Billing architecture must define charge model, usage ingestion, rating, invoice grouping, tax, payment, revenue recognition/subledger, ERP integration, and operational controls.
Common customizations
Custom billing payloads, tax engine integration, invoice grouping, ERP reconciliation, credit/rebill flows.
Custom usage ingestion pipelines, rating extensions, tax/payment/ERP integration, invoice presentation, revenue recognition integration, custom dispute/adjustment flows.
10. Analytics, AI, and Agentforce
Comparison dimension
Salesforce CPQ / Steelbrick
Salesforce Revenue Cloud
Use case, user journey, personas
Reporting focuses on quote pipeline, discounts, approvals, quote line product mix, renewal forecast, and CPQ operational controls. AI/agentic workflows are usually custom or implemented outside CPQ.
Revenue Cloud positions analytics across pricing, subscription revenue, orders, billing, MRR/ARR, margin, renewal retention, fallout, DSO, invoice health, plus Agentforce quote generation/update/summarization and revenue workflow assistance.
Licensing requirements
Salesforce reports/dashboards included with platform licenses; CRM Analytics/Tableau/AI capabilities may be separate.
Revenue Cloud Advanced includes AI & Analytics in the edition feature list; Tableau Next, CRM Analytics, Agentforce, or Data Cloud entitlements may vary by contract.
Data model
SBQQ quote/line/approval/subscription data, Opportunity, Product, Account, Contract. Analytics often require denormalized reporting objects or data warehouse replication.
Revenue lifecycle data across catalog, pricing, quote, contract, order, asset, billing, invoice, and usage; suitable for cross-functional revenue analytics and agent grounding.
Automations provided
Approval notifications and reports; most advanced analytics require custom reports, CRMA, Tableau, or warehouse modeling.
Pricing analytics, subscription revenue analytics, order analytics, billing analytics, Agentforce-assisted quote workflows, and operational exceptions surfaced throughout the lifecycle.
Configuration effort
Low to medium for basic reporting; high for reliable ARR/NRR/margin analytics across CPQ, Billing, ERP, and finance.
Medium to high. Requires metric definitions, data quality, lifecycle events, security, semantic layer, and governance for AI actions.
Common customizations
Custom report types, snapshot objects, renewal/margin dashboards, data lake exports, custom AI assistants.
Custom Tableau/CRM Analytics apps, Data Cloud harmonization, Agentforce actions/guardrails, metric stores, and operational command centers.
Decision Guidance
Choose / keep Salesforce CPQ when...
- The business need is primarily seller-led quote configuration and pricing.
- Existing SBQQ implementation is stable and not blocking growth.
- Billing, fulfillment, CLM, and ERP are already handled by specialized systems.
- Customization appetite is high and the team already understands CPQ calculator and SBQQ data model.
- Migration risk outweighs benefits of a broader product-to-cash redesign.
Choose Salesforce Revenue Cloud when...
- You need a unified revenue lifecycle platform, not only CPQ.
- Products are attribute-driven, sold across multiple channels, or require stronger catalog governance.
- The roadmap includes order decomposition, orchestration, consumption, billing, wallet, invoicing, or revenue analytics.
- Sales, legal, finance, service, customer success, and fulfillment must work from a shared lifecycle model.
- Agentforce-assisted quote and revenue workflows are part of the target operating model.
Recommended architecture approach
- Inventory the existing CPQ implementation: SBQQ objects, quote calculator plugins, price/product rules, templates, approvals, custom fields, integrations, and renewal/amendment logic.
- Classify each feature: retire, replace with Revenue Cloud standard, migrate with mapping, or rebuild as extension.
- Design the target revenue lifecycle: catalog ownership, pricing governance, quote/channel strategy, contract/order/asset lifecycle, billing handoff, and analytics definitions.
- Run a proof of concept: one representative bundle, one complex pricing scenario, one amendment/renewal, one order orchestration, and one billing/invoice scenario.
- Plan migration in waves: catalog and pricing first, then quote flows, then contract/order/asset/billing lifecycle, with data reconciliation and parallel-run controls.
Object Classification Cheat Sheet
| Area | Salesforce standard objects | Salesforce CPQ / SBQQ-specific objects | Revenue Cloud-specific or modified areas | Architect validation notes |
|---|---|---|---|---|
| Accounts and sales process | Account, Contact, Opportunity, User, Pricebook2 | SBQQ Quote references Opportunity/Account and CPQ user permissions | Standard CRM records enriched by revenue lifecycle processes | Validate access model for sales, partner, customer, finance, legal, and agent users. |
| Catalog | Product2, Pricebook2, PricebookEntry | Product Option, Product Feature, Product Rule, Configuration Attribute, Option Constraint | Attribute catalog, product components/relationships, constraints, selling models, channel exposure | Define authoritative product source: Salesforce vs PIM vs ERP. |
| Pricing | PricebookEntry, CurrencyType, DatedConversionRate | Price Rule, Price Action, Price Condition, Discount Schedule/Tier, Block Price, Contracted Price, Summary Variable | Pricing procedures/elements, price adjustments, transaction line pricing details, analytics | Document calculation sequence and external price/tax/margin calls. |
| Quote | Opportunity, Quote, QuoteLineItem may be used depending on product/version | SBQQ__Quote__c, SBQQ__QuoteLine__c, Quote Template, Quote Document | Revenue transaction/quote records and lines, Agentforce actions, lifecycle links | Confirm whether target uses standard Quote objects, transaction objects, or package-specific records. |
| Contract | Contract | Subscription, Contracted Price, renewal/amendment relationships | Contract lifecycle, clauses/templates, approval/redlining, obligations, lifecycle actions | Align legal data model and document repository. |
| Order | Order, OrderItem | Quote-to-order links and order generation settings | Order capture, decomposition, orchestration plans/tasks, enrichment, fallout | Map commercial lines to technical fulfillment lines. |
| Asset / subscription | Asset, Contract, OrderItem | SBQQ Subscription, amendment and renewal quote records | Asset lifecycle actions, subscription metrics, amend/renew/cancel flows, notifications | Define ARR/MRR/NRR logic and co-term behavior. |
| Billing | May include standard invoice/payment concepts depending on enabled products | Usually Salesforce Billing package or external billing data, not core CPQ | Billing schedules, usage rating, digital wallet, invoices, invoice documents, accounting subledger | Validate package/API names because billing object model varies by installed product. |
Sources and validation notes
- Salesforce Revenue Lifecycle Management / Agentforce Revenue Management product page: used for scope covering pricing, quoting, contracting, billing, order automation, asset lifecycle, analytics, and Agentforce capabilities.
- Salesforce CPQ product page: used for CPQ positioning, quote creation, guided workflows, approvals, discounting, and asset lifecycle positioning.
- Salesforce Revenue Cloud pricing page: used for current public edition/pricing references and billing add-on positioning as of June 8, 2026.
- Salesforce Help and Object Manager in the target org should be used to validate exact object/API names, installed package namespaces, enabled features, and licenses before solution design.
Internal Google Drive search returned no accessible results for this comparison, so the content is intentionally conservative where Salesforce packaging can differ by org, contract, and release.
Prepared as an HTML working document. This comparison is intended for architecture planning, not as a substitute for a Salesforce order form, product SKU matrix, or implementation-specific solution design.