- Review platforms are inherently biased (sample bias, incentivized reviews, and vendor marketing). Findings below are patterns and representative quotes, not definitive product performance.
- Gartner Peer Insights
- SAP CPQ appears as a vendor/product in the Gartner Peer Insights "Configure, Price and Quote Applications" market page. (Vendor/product listing on an industry analyst review site)
- Limitations
- Gartner Peer Insights often restricts viewing of full review text without sign-in; in this run, the listing is accessible but extracting multiple full quotes reliably may be limited.
- G2
- SAP CPQ has a G2 reviews page and a "pros and cons" view. (Third-party review and comparison site)
- Limitations
- G2’s anti-scraping and dynamic content can limit direct extraction of multiple full quotes in automated contexts.
- TrustRadius
- SAP CPQ has a TrustRadius reviews page. (Product review site with vendor and competitor comparison pages)
- TrustRadius also provides competitor comparison pages.
- Capterra
- SAP CPQ has reviews on Capterra (listed under legacy product naming consistent with product lineage). (Small-business and software review marketplace)
- Community / social (Reddit) — representative quotes
- Positive-leaning community opinion (architecture praise, anecdotal)
- A community commenter described SAP CPQ as "a superb product with microservice restful api architecture." (Community forum post)
- Negative / churn signal (anecdotal)
- A commenter said: "I am SAP CPQ developer and our company is phasing out SAP CPQ in around 2-3 years as they're going with another CPQ system…" (Community forum post)
- Price/value dissatisfaction (legacy CallidusCloud experience)
- A commenter said they used CallidusCloud and "can’t honestly say I’d recommend it, especially at the price we were paying." (Community forum post)
- Why customers chose this product over alternatives (inferred from sources)
- SAP ecosystem fit
- SAP CPQ is documented as integrating with SAP Sales Cloud, SAP Commerce Cloud, and SAP Service Cloud; buyers operating within SAP landscapes may select it to reduce integration risk within the SAP CX ecosystem.
- Complex configuration needs
- Vendor materials describe handling very large quotes quickly, suggesting the product targets scenarios where simpler quoting tools struggle.
- Why some customers left for competitors (churn reasons)
- Only anecdotal evidence was found in community posts (e.g., "phasing out"); no systematic churn dataset was found in accessible sources.
- Common reasons in CPQ migrations generally include admin complexity, user adoption issues, support quality, and total integration cost—these require validation via reference checks.
- Specific outcomes customers achieved (with metrics when available)
- In the sources retrieved in this run, there were no independently verified case studies with quantified KPIs (e.g., "reduced quote cycle by X%") accessible without deeper SAP case-study digging.
- Deal-breakers and reasons customers didn’t purchase
- Minimum user quantities stated by the vendor for standard editions may disqualify smaller organizations or teams trying to pilot.
- Multi-year contract norms can be a barrier for buyers preferring monthly flexibility.