{"id":334915,"date":"2025-10-20T16:13:40","date_gmt":"2025-10-20T16:13:40","guid":{"rendered":"https:\/\/experlogix.com\/bravo-pros-what-it-means-for-cpq\/"},"modified":"2026-02-24T16:18:17","modified_gmt":"2026-02-24T16:18:17","slug":"bravo-pros-what-it-means-for-cpq","status":"publish","type":"post","link":"https:\/\/experlogix.com\/de\/bravo-pros-what-it-means-for-cpq\/","title":{"rendered":"Bravo, PROS! What It Means for CPQ\u00a0"},"content":{"rendered":"\n[et_pb_section fb_built=”1″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_text _builder_version=”4.27.5″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” sticky_enabled=”0″]

Thoma Bravo Buys PROS: What the Conga Merge Means for CPQ Customers<\/h1>\n

Thoma Bravo is splitting PROS into two paths: a travel-focused platform investment and a B2B pricing + CPQ stack that merges into Conga. Here\u2019s the practical read on what that implies for product focus, integration reality, and CPQ roadmaps.<\/p>\n

\"\"<\/p>\n

What was announced<\/h2>\n

Thoma Bravo has acquired PROS Holdings for about $1.4 billion.<\/p>\n

Here\u2019s the structural split they announced: PROS\u2019 B2B pricing and CPQ business will merge with Conga (another Thoma Bravo portfolio company known for revenue lifecycle management), while PROS\u2019 travel business has been separated out as an independent platform investment for Thoma Bravo.<\/p>\n

The marketing vision vs. the operating reality<\/h2>\n

The combined Conga + PROS vision is being positioned as a \u201csuper revenue platform,\u201d aiming to deliver end-to-end CPQ and contract lifecycle automation.<\/p>\n

The promise sounds simple: bundle CPQ and contract automation into a single, integrated revenue workflow. The problem is that \u201ccombined solutions\u201d often read better in press releases than they run in the field.<\/p>\n

The uncomfortable truth about PROS\u2019 core<\/h2>\n

PROS\u2019 core has always been passenger revenue optimization software (it\u2019s literally where the PROS name originated). Historical investments show a strong center of gravity around strengthening travel-sector capabilities, with a few outliers along the way\u2014CPQ being one of them.<\/p>\n

Thoma Bravo\u2019s decision to split travel from B2B pricing + CPQ signals what they likely believe: passenger revenue optimization is the \u201creal\u201d durable platform business, and the non-core investments were dilutive to that focus.<\/p>\n

In that framing, the CPQ and B2B pricing pieces aren\u2019t the crown jewel\u2014they\u2019re the remainder being folded into Conga. \ud83d\ude2c<\/p>\n

\u201cSuper platform\u201d or just more integration work?<\/h2>\n

Despite the \u201csuper platform\u201d messaging, injecting acquired product pieces into an already \u201ccombined solution\u201d does not automatically create a cohesive platform. Sometimes it creates a larger collection of capabilities that still require significant services, integration work, and operational compromise to behave like one product.<\/p>\n

Even if contract automation and CPQ become tightly integrated over time, the overall value collapses if the CPQ capabilities still fall short where customers actually need them.<\/p>\n

CPQ gaps that still matter<\/h2>\n

If a CPQ tool can\u2019t handle complex bundles, struggles with high-volume quotes, or requires heavy implementation coding to model real-world product and pricing logic, organizations end up with familiar outcomes: more spreadsheets, more workaround processes, and more operational friction across sales and delivery.<\/p>\n

When the CPQ system can\u2019t carry the full configuration and pricing detail, teams compensate by pushing complexity into side systems. The result is less control, less auditability, and more quoting risk\u2014regardless of how polished the \u201cplatform\u201d story sounds.<\/p>\n

CPQ or d\u00e9j\u00e0 vu?<\/h2>\n

This pattern is not new: an investor finds the strongest core business, then salvages and repackages the rest.<\/p>\n

PROS has done its own version of this over time. After acquiring Chameleon for CPQ in 2013, PROS refocused again on travel by acquiring additional travel-focused companies, plus a pricing analytics software firm. The travel side accelerated (pun intended), while the rest is now being recycled into Conga\u2019s stack.<\/p>\n

This also echoes a familiar CPQ arc: Salesforce CPQ. After Salesforce acquired Steelbrick CPQ in 2015, Salesforce became a major CPQ presence largely due to CRM scale. But despite early hype, customers have watched Salesforce CPQ stagnate for years, and re-implementation pressure has become the headline reality.<\/p>\n

Salesforce is an extreme example, but you don\u2019t need a platform sunset to get boxed in. A \u201cgood enough\u201d CPQ that stops evolving still creates compounding cost: manual work, extra services, and missed automation opportunities.<\/p>\n

Where to expect innovation investment<\/h2>\n

Credit where it\u2019s due: airline carriers kept renewing PROS because the travel platform works. Revenue management, digital selling, demand forecasting, and yield discipline\u2014tailored to travel\u2014created real value.<\/p>\n

By keeping the travel business as an independent platform investment, Thoma Bravo is giving that core space to breathe. Travel customers should expect a clearer roadmap and more focused product innovation now that it\u2019s no longer carrying the weight of large CPQ and other non-core codebases that weren\u2019t returning the same value.<\/p>\n

What\u2019s in store for PROS CPQ customers<\/h2>\n

There are two broad paths from here, and both have implications that customers should pressure-test early.<\/p>\n

Path 1: Combine Conga CPQ and PROS CPQ into one<\/h3>\n

Conga could attempt to unify the PROS and Conga CPQ products under one solution. That is a multi-year effort and requires sustained investment to catch up to market leaders across configurator depth, performance at scale, and admin UX.<\/p>\n

Path 2: De-emphasize PROS CPQ and migrate customers<\/h3>\n

Conga could instead maintain PROS CPQ just long enough to steer customers toward an \u201cupgrade\u201d (read: re-implementation) onto Conga\u2019s existing CPQ. This can make sense for Conga economically, but it can leave customers with higher costs, fewer fit-for-purpose capabilities, and less CPQ-specific innovation if CPQ remains secondary to Conga\u2019s CLM-first positioning.<\/p>\n

If CPQ becomes an afterthought, the risks are predictable<\/h3>\n