Salesforce CPQ

Name: Salesforce CPQ
Brand: Salesforce
Rating: 4.2 (1874 reviews)

Leader

We're the #1 AI CRM—where humans with agents drive customer success together.

Est 1999|Valuation $203.1B|Raised $43.2B|150 Ref Customers

LinkedIn 6.7M|Website|Web traffic 78.5M|FTEs 83,334|HQ San Francisco, California, US

MarketsCPQ Software (Configure, Price, Quote)

Published May 19, 2026

01Common complaints

Consider alternatives (or custom quoting solutions) when: - The organization’s sales motion is simple (few SKUs, minimal bundling/rules); lighter CPQ options or native Salesforce quoting features may be sufficient. - There is insufficient capacity to support ongoing maintenance; community feedback often characterizes certain implementations as requiring significant administrative effort. - Performance at scale is critical and quotes routinely include hundreds of lines or complex multi-year structures; multiple community reports describe friction in such scenarios. - A modern, low-friction user experience out of the box is a priority and there is limited appetite for Salesforce page or layout customization. - The technology stack is not Salesforce-centric (for example, the organization is standardized on Oracle ERP/CX or SAP), in which case CPQ from the same suite may reduce integration complexity. - Security or procurement processes require package-level attestations or AppExchange security-review artifacts that are not straightforward to obtain; raise this early in procurement.

Deal disqualifiers (poor fit)

Small teams requiring minimal admin overhead and simple quoting requirements
Organizations lacking Salesforce admin capacity or access to implementation resources
Teams requiring very rapid time-to-value and unable to engage partners or consultants

Frequently cited limitations (from reviews and community posts)

Significant complexity and ongoing rule maintenance required by administrators
Performance and usability concerns reported in certain workflows and heavy-use scenarios
Renewal and amendment edge cases where subscription or pricing details may not carry forward as expected without careful implementation

Vendor-acknowledged limitations / roadmap

No explicit vendor roadmap items or acknowledged limitations specific to CPQ were captured in the sources reviewed for this report.

Practical limitations to anticipate

Dependence on disciplined data governance for product catalogs and price books
Possible need for custom development for specialized quoting scenarios
Additional products or licenses may be required to achieve full quote-to-cash coverage

02Why they buy

Noted advantages (supported by sources)

Salesforce-native workflow alignment: CPQ integrates with Salesforce data model constructs such as Opportunities, providing visibility into quoting and forecasting within Salesforce.
Training and enablement resources: Trailhead provides CPQ learning paths and credentialing, which can support administrator skill development while also indicating product depth and complexity.

Claims requiring validation

Marketing statements about specific performance improvements or deal-size uplift should be validated through customer references, case studies, and agreed pilot metrics prior to use in a business case.

Where competitors may have advantages

Some vendors offer faster deployment or distinct out-of-the-box subscription/consumption pricing capabilities. Oracle and SAP may be stronger where ERP-driven pricing and order orchestration are primary requirements. DealHub and other newer entrants often emphasize simpler implementation and bundled document workflows.

03Field reports

Review platforms: Capterra (examples)

Capterra reviews are mixed, with praise for automation and value in some reviews and recurring notes about rollout complexity in others. Positive (very highly rated on Capterra example): - "Salesforce CPQ is absolutely fantastic software to manage the whole invoicing process… time spent… has gone down drastically… very easy to use… documentation and courses in Trailhead are great!" Constructive/negative (same review): - "The configuration might be quite hard at times… business processes are very complex and they are hard to model." Mixed (well rated on Capterra example): - Pros: "The ease of creating Quote and configurating the product." - Cons: "Initial rollout could be complicated and cumbersome." An older review referencing the SteelBrick-era product comments on evolution and trade-offs.

Community/Social: Reddit (examples)

Reddit threads often include operationally detailed feedback and highlight common failure modes and pain points. Performance and usability pain (Sales subreddit): - Community posts include reports of performance issues, clunkiness, and perceived lack of user friendliness for complex multi-year quotes. Renewals/amendments reliability complaint (Salesforce subreddit): - Some users report that subscription renewals and amendments may require manual intervention for product or pricing carry-forward in certain configurations. Admin workload / maintenance theme (Salesforce subreddit): - Administrators report significant ongoing maintenance for product cataloging and rule sets. Security-review confusion (Salesforce subreddit): - Community threads include questions about AppExchange security review status for CPQ packages; responses suggest Salesforce may use internal review practices for its own packages.

G2 (category-level signals)

On G2’s CPQ category page, Salesforce Revenue Cloud is associated with a substantial review volume and commonly cited pros/cons themes, including automation and visibility benefits as pros, and learning curve and complexity as cons. Buyers scoping a specific CPQ managed package should confirm reviews correspond to the intended SKU or configuration.

Why customers select Salesforce CPQ (observed patterns)

Common reasons cited across sources:

Alignment with Salesforce CRM workflows (quote data residing on the Opportunity and downstream visibility for forecasting and renewals)
Standardizing pricing and discount controls
Replacing manual spreadsheet-based quoting to reduce error-prone processes

Why some customers consider alternatives (observed patterns)

Sources frequently mention:

Complexity and ongoing maintenance burden
Performance issues in heavy quoting scenarios
Community speculation that Salesforce is evolving Revenue Cloud offerings, which some interpret as shifting emphasis away from legacy CPQ (this is opinion and not a confirmed roadmap)

What was found

This review did not locate independently verifiable case studies with hard metrics attributable specifically to Salesforce CPQ implementations.

Vendor-published performance claims (methodology caveat)

Vendor marketing materials include performance and business-impact claims such as increased deal sizes, but these claims are typically presented without detailed methodology, sample descriptions, or attribution and should be treated as marketing statements requiring validation.

Practical takeaway

Prospective purchasers should request CPQ-specific customer references in their industry and complexity tier, obtain implementation partner references, and conduct a representative pilot or proof-of-concept using a realistic product catalog and pricing rules.

04Best fit

Company size

Typically suited to:

Mid-market to enterprise organizations, often with complex global selling scenarios
Organizations with dedicated Salesforce administration or RevOps resources and access to implementation partners

Industries/verticals

Common adopters include:

Manufacturing
Technology and SaaS
Telecommunications
Professional services and complex services bundles

Roles and personas

Decision makers: VP Sales, CRO, VP RevOps, CIO/IT leadership
Implementers: Salesforce Admins, Solution Architects, CPQ Specialists, Sales Ops
End users: Account Executives, Sales Engineers, Deal Desk

Qualification criteria (good fit)

The organization already uses Salesforce Sales Cloud and wants quoting to reside within the same system
There is a need to control discounting and approval workflows
The organization can invest in product catalog data modeling and ongoing governance

05The pitch

What the product does (objective value proposition)

Salesforce CPQ (Configure, Price, Quote) is quoting software designed to assist sales and revenue operations teams in building accurate quotes for complex products and services by enforcing configuration rules, automating pricing and discount logic, routing approvals, and generating quote documents. It is tightly integrated with Salesforce CRM objects and is presented as part of a broader quote-to-cash workflow that can extend into billing, invoicing, subscriptions, and revenue operations processes. Key capabilities referenced in Salesforce materials include guided selling, product bundling, pricing rules and discount controls, approval workflows, and quote document generation. Salesforce also offers related revenue management capabilities under Revenue Cloud, which may include CPQ plus adjacent modules.

Target market and market positioning

Typical fit (in practice): mid-market to enterprise organizations with: - Complex product catalogs (bundles, dependencies, optionality) - Non-trivial pricing (discount policies, contract pricing, multi-currency) - Approval-heavy selling motions (finance/legal/RevOps approvals) - An existing Salesforce Sales Cloud footprint and available admin/developer capacity Positioning: the CPQ offering is presented as a native Salesforce solution (originally SteelBrick) for organizations standardized on Salesforce CRM, and it is commonly evaluated alongside CPQ specialist vendors and enterprise suite providers.

Get a comprehensive analysis of Salesforce CPQ including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published May 19, 2026

01Common complaints

Consider alternatives (or custom quoting solutions) when:

The organization’s sales motion is simple (few SKUs, minimal bundling/rules); lighter CPQ options or native Salesforce quoting features may be sufficient.
There is insufficient capacity to support ongoing maintenance; community feedback often characterizes certain implementations as requiring significant administrative effort.
Performance at scale is critical and quotes routinely include hundreds of lines or complex multi-year structures; multiple community reports describe friction in such scenarios.
A modern, low-friction user experience out of the box is a priority and there is limited appetite for Salesforce page or layout customization.
The technology stack is not Salesforce-centric (for example, the organization is standardized on Oracle ERP/CX or SAP), in which case CPQ from the same suite may reduce integration complexity.
Security or procurement processes require package-level attestations or AppExchange security-review artifacts that are not straightforward to obtain; raise this early in procurement.

Deal disqualifiers (poor fit)

Small teams requiring minimal admin overhead and simple quoting requirements
Organizations lacking Salesforce admin capacity or access to implementation resources
Teams requiring very rapid time-to-value and unable to engage partners or consultants

Frequently cited limitations (from reviews and community posts)

Significant complexity and ongoing rule maintenance required by administrators
Performance and usability concerns reported in certain workflows and heavy-use scenarios
Renewal and amendment edge cases where subscription or pricing details may not carry forward as expected without careful implementation

Vendor-acknowledged limitations / roadmap

No explicit vendor roadmap items or acknowledged limitations specific to CPQ were captured in the sources reviewed for this report.

Practical limitations to anticipate

Dependence on disciplined data governance for product catalogs and price books
Possible need for custom development for specialized quoting scenarios
Additional products or licenses may be required to achieve full quote-to-cash coverage

02Why they buy

Noted advantages (supported by sources)

Salesforce-native workflow alignment: CPQ integrates with Salesforce data model constructs such as Opportunities, providing visibility into quoting and forecasting within Salesforce.
Training and enablement resources: Trailhead provides CPQ learning paths and credentialing, which can support administrator skill development while also indicating product depth and complexity.

Claims requiring validation

Marketing statements about specific performance improvements or deal-size uplift should be validated through customer references, case studies, and agreed pilot metrics prior to use in a business case.

Where competitors may have advantages

Some vendors offer faster deployment or distinct out-of-the-box subscription/consumption pricing capabilities. Oracle and SAP may be stronger where ERP-driven pricing and order orchestration are primary requirements. DealHub and other newer entrants often emphasize simpler implementation and bundled document workflows.

03Field reports

Review platforms: Capterra (examples)

Capterra reviews are mixed, with praise for automation and value in some reviews and recurring notes about rollout complexity in others.

Positive (very highly rated on Capterra example):

"Salesforce CPQ is absolutely fantastic software to manage the whole invoicing process… time spent… has gone down drastically… very easy to use… documentation and courses in Trailhead are great!"

Constructive/negative (same review):

"The configuration might be quite hard at times… business processes are very complex and they are hard to model."

Mixed (well rated on Capterra example):

Pros: "The ease of creating Quote and configurating the product."
Cons: "Initial rollout could be complicated and cumbersome."

An older review referencing the SteelBrick-era product comments on evolution and trade-offs.

Community/Social: Reddit (examples)

Reddit threads often include operationally detailed feedback and highlight common failure modes and pain points.

Performance and usability pain (Sales subreddit):

Community posts include reports of performance issues, clunkiness, and perceived lack of user friendliness for complex multi-year quotes.

Renewals/amendments reliability complaint (Salesforce subreddit):

Some users report that subscription renewals and amendments may require manual intervention for product or pricing carry-forward in certain configurations.

Admin workload / maintenance theme (Salesforce subreddit):

Administrators report significant ongoing maintenance for product cataloging and rule sets.

Security-review confusion (Salesforce subreddit):

Community threads include questions about AppExchange security review status for CPQ packages; responses suggest Salesforce may use internal review practices for its own packages.

G2 (category-level signals)

Why customers select Salesforce CPQ (observed patterns)

Common reasons cited across sources:

Alignment with Salesforce CRM workflows (quote data residing on the Opportunity and downstream visibility for forecasting and renewals)
Standardizing pricing and discount controls
Replacing manual spreadsheet-based quoting to reduce error-prone processes

Why some customers consider alternatives (observed patterns)

Sources frequently mention:

Complexity and ongoing maintenance burden
Performance issues in heavy quoting scenarios
Community speculation that Salesforce is evolving Revenue Cloud offerings, which some interpret as shifting emphasis away from legacy CPQ (this is opinion and not a confirmed roadmap)

What was found

This review did not locate independently verifiable case studies with hard metrics attributable specifically to Salesforce CPQ implementations.

Vendor-published performance claims (methodology caveat)

Practical takeaway

04Best fit

Company size

Typically suited to:

Mid-market to enterprise organizations, often with complex global selling scenarios
Organizations with dedicated Salesforce administration or RevOps resources and access to implementation partners

Industries/verticals

Common adopters include:

Manufacturing
Technology and SaaS
Telecommunications
Professional services and complex services bundles

Roles and personas

Decision makers: VP Sales, CRO, VP RevOps, CIO/IT leadership
Implementers: Salesforce Admins, Solution Architects, CPQ Specialists, Sales Ops
End users: Account Executives, Sales Engineers, Deal Desk

Qualification criteria (good fit)

The organization already uses Salesforce Sales Cloud and wants quoting to reside within the same system
There is a need to control discounting and approval workflows
The organization can invest in product catalog data modeling and ongoing governance

05The pitch

What the product does (objective value proposition)

Key capabilities referenced in Salesforce materials include guided selling, product bundling, pricing rules and discount controls, approval workflows, and quote document generation. Salesforce also offers related revenue management capabilities under Revenue Cloud, which may include CPQ plus adjacent modules.

Target market and market positioning

Typical fit (in practice): mid-market to enterprise organizations with:

Complex product catalogs (bundles, dependencies, optionality)
Non-trivial pricing (discount policies, contract pricing, multi-currency)
Approval-heavy selling motions (finance/legal/RevOps approvals)
An existing Salesforce Sales Cloud footprint and available admin/developer capacity

Positioning: the CPQ offering is presented as a native Salesforce solution (originally SteelBrick) for organizations standardized on Salesforce CRM, and it is commonly evaluated alongside CPQ specialist vendors and enterprise suite providers.

Get a comprehensive analysis of Salesforce CPQ including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →