State of the market · 2026/2027 edition

The State of CPQ on Salesforce2026–2027: seven vendors, and what to ask each.

Twenty months after Salesforce stopped selling its original CPQ, the market around it has fewer independent vendors, a successor still earning its place below the enterprise line, and a new judge of architecture: AI. This is our assessment of the seven vendors Salesforce customers shortlist: Salesforce Revenue Cloud, Conga, DealHub, Subskribe, Nue, Zuora and Kugamon.

5 of 7
vendors assessed were acquired, bought a rival, went private or stopped selling a product since January 2025
~15%
of Revenue Cloud Advanced customers migrated from Salesforce CPQ, by Salesforce's own count
5 for 5
active competitors shipped or announced a quoting agent or an MCP server since mid-2025
6×
spread between the lowest and highest three-year cost at 50 users in our cost model

The CPQ market on Salesforce is consolidating faster than its products are maturing. Salesforce CPQ is end of sale. Conga, DealHub, Subskribe and Zuora each changed owners or absorbed a rival; Nue and Kugamon did not. The successor product is winning enterprises while smaller teams weigh a rebuild they did not ask for. Meanwhile every vendor now ships AI agents, which moves the contest from features to architecture: an agent is only as good as the data and the pricing logic it can reach in one place. That favors platforms that keep both inside the Salesforce org (Revenue Cloud and Kugamon, among the seven), and it is the one requirement a custom build cannot shortcut.

About this assessment. Scope: Salesforce Revenue Cloud, Conga, DealHub, Subskribe, Nue, Zuora and Kugamon, plus building in-house. Kugamon is one of the vendors assessed and the author of this report. We cite public sources, label estimates as estimates, and say where competitors are the better fit. Prefer paper? Download the PDF.

Five findings for 2026–2027

  1. The field is consolidating. Salesforce CPQ went end of sale in March 2025. In the same period Zuora was taken private, DealHub bought Subskribe, and Thoma Bravo folded PROS's B2B business into Conga. Five of the seven vendors assessed had a structural change in under two years; Nue and Kugamon did not.
  2. Mid-market traction is still unproven. Revenue Cloud is gaining enterprises and analyst rankings. For SMB and mid-market teams, though, moving from Salesforce CPQ is a rebuild, list price is $150–$200 per user per month before add-ons, and Salesforce says about 15% of Revenue Cloud Advanced customers came from CPQ.
  3. Stability is now a selection criterion. Conga has announced ten C-suite appointments since April 2025. Two of Subskribe's three founders have left operating roles at DealHub. Salesforce renamed its revenue product three times in 27 months. Kugamon has been led by its founder since 2009. Ask who owns the roadmap you are signing for.
  4. AI is settling the native argument. Every active competitor now ships agents or an MCP server, so AI features no longer separate vendors. What separates them is whether the data and the pricing logic an agent needs sit in one place. Platforms that keep both in the Salesforce org (Revenue Cloud and Kugamon in this set) hold the structural advantage.
  5. Build cannot carry complex CPQ. AI makes code cheaper to write, not cheaper to own. Bundles, approvals, amendments, co-termed renewals and proration are where custom builds stall, and an in-house system arrives with no documentation, no roadmap and nothing an AI agent can safely call.
Where each vendor masters revenue records, against the segment it targetsMost vendors sit outside the org or aim at the enterprise. Where each vendor’s revenue records are mastered, against the segment it primarily targets. Kugamon assessment from vendor documentation and stated positioning, October–November 2026; placement is qualitative. Outside Salesforce, synced inSplit, or the vendor’s own objectsInside the Salesforce orgEnterpriseSMB andmid-marketWhere Quotes, Subscriptions and Invoices are mastered →in the org, for smaller teams: thinly servedZuoraDealHubSubskribeCongaSalesforce CPQ (end of sale)NueRevenue CloudKugamon
Figure 1. Most vendors sit outside the org or aim at the enterprise. Where each vendor’s revenue records are mastered, against the segment it primarily targets. Kugamon assessment from vendor documentation and stated positioning, October–November 2026; placement is qualitative.

Consolidation: fewer owners, fewer independent roadmaps

In under two years, the vendor list most Salesforce customers evaluate has been reshaped by one end-of-sale notice, one take-private and two acquisitions of direct competitors. None of these events is a failure, but each changes who decides what your product becomes.

Ownership and product events among the assessed vendors, January 2025 to mid-2027Seven ownership and product events in under twenty months, and two more on the calendar. Events affecting the vendors in this assessment, January 2025 to mid-2027, from company announcements and filings. Dots take each vendor’s colour; the shaded entries are vendor roadmap dates, not shipped product. Kugamon is the band at the foot. PLANNED202520262027Feb 14, 2025Zuora taken privateSilver Lake and GIC, $1.7 billionMar 2025Salesforce CPQ end of saleno new customersNov 19, 2025DealHub acquires Subskribeterms undisclosedDec 9, 2025Thoma Bravo closes PROStake-private, about $1.4 billionFeb 2, 2026Conga absorbs PROS B2Bone owner, two CPQsJul 1, 2026Salesforce closes m3terusage meteringSep 14, 2026“Revenue Cloud” name restoredthird rename in 27 monthsDec 2026CPQ Migration Assistanttarget date; not yet shippedH1 2027m3ter in Revenue Cloudtargeted first half of 2027KUGAMONfounder-led since 2009: no change of owner, no acquisition, monthly releases throughout
Figure 2. Seven ownership and product events in under twenty months, and two more on the calendar. Events affecting the vendors in this assessment, January 2025 to mid-2027, from company announcements and filings. Dots take each vendor’s colour; the shaded entries are vendor roadmap dates, not shipped product. Kugamon is the band at the foot.
Event What changed The open question for customers
Salesforce CPQ end of sale, March 2025 No new customers; the product is in a maintenance phase. Existing customers can renew, add users and get support. No end-of-life date has been announced and there is no forced migration. When to move, and to what. The successor is a re-implementation, not an upgrade.
DealHub + Subskribe, November 2025 DealHub says Subskribe will be fully integrated into one experience and one data model. No date is published; Subskribe's public release notes end on October 25, 2025. Two billing engines today. Which one is the future, and who pays for the move?
Conga + PROS B2B, February 2026 One owner, two CPQs: Conga Advantage CPQ (formerly Apttus CPQ) and Smart CPQ (formerly PROS). In Gartner's 2026 CPQ Magic Quadrant, PROS placed as a Leader and Conga's own CPQ as a Challenger. Which product is being proposed, and which roadmap gets the investment?
Zuora take-private, February 2025 Private under Silver Lake and GIC; the founder remains CEO. Still a Gartner Leader for recurring billing in 2025 and 2026. Fewer public disclosures. Ask for roadmap and price commitments in writing.
Salesforce + m3ter, July 2026 Usage metering was bought rather than built. The first Revenue Cloud capabilities are targeted for the first half of 2027. High-volume consumption billing stays a roadmap item until it ships.
Kugamon, no change Founder-led and customer-funded since 2009. No acquisition, no change of owner and no product line retired in the period; one or more major releases a month. The smallest company in this set. Ask about the team behind the product and continuity of support.
End of sale is not end of life. Salesforce's own FAQ says there is no forced migration and no announced end-of-life date for Salesforce CPQ. The planning question is not "how fast must we leave?" It is "where should our quoting logic live for the next five years, and does getting there require a rebuild?" More in Salesforce CPQ is end of sale.

Traction: the successor is winning enterprises, not yet the mid-market

Revenue Cloud has real momentum: Salesforce reports fast customer growth and holds a Gartner Leader placement for CPQ. The evidence in the SMB and mid-market is thinner.

  • Price before add-ons. $150 (Growth) or $200 (Advanced) per user per month, on top of a Sales or Service Cloud license. Order orchestration and invoice management are sold separately; billing is its own product. There is no free trial.
  • A rebuild, not an upgrade. Salesforce says CPQ objects, pricing rules and scripts "don't map directly." Salesforce states 3–6 months; an implementer says about twelve for a manual migration, and a reference customer's CIO said a year to 18 months is typical.
  • Most of the base has yet to move. About 15% of Revenue Cloud Advanced customers are companies that migrated from Salesforce CPQ (Salesforce, 2026). Salesforce does not publish how many CPQ customers that represents, or a Revenue Cloud customer count.

What SMB and mid-market teams run into

  • Buying small. A customer on r/salesforce reported being unable to purchase a small number of licenses (September 2025).
  • A tool that is not here yet. Salesforce's first-party Migration Assistant is targeted for December 2026: announced, not shipped, with scope and licensing unpublished.
Stated and reported go-live times, by vendorStated go-live times and reported ones diverge most at the top of the market. Months from kickoff to go-live: what each vendor states (solid) and what a practitioner, an executive or a customer reports (hatched). Nue markets “weeks”; its own VP put the average at about 90 days. Kugamon customers riteSOFT and Branch report one month, and seven to eight weeks of onboarding. DealHub states “a few weeks” and Zuora states no figure, so neither is drawn. Kugamon4–8 weeks stated; customers report 1 month and 7–8 weeksSubskribe30 days–4 months statedConga3–6 months statedNueabout 90 days on average, up to a year (its VP)Revenue Cloud3–6 months stated12–18 months reported for a full rebuildStart3 months6 months9 months12 months15 months18 months
Solid = stated by the vendorHatched = reported by practitioners, executives or customers
Figure 3. Stated go-live times and reported ones diverge most at the top of the market. Months from kickoff to go-live: what each vendor states (solid) and what a practitioner, an executive or a customer reports (hatched). Nue markets “weeks”; its own VP put the average at about 90 days. Kugamon customers riteSOFT and Branch report one month, and seven to eight weeks of onboarding. DealHub states “a few weeks” and Zuora states no figure, so neither is drawn.

Slow starts are not unique to Salesforce: Nue's own VP put its average at about 90 days. Ask every vendor for the go-live date in writing. The CPQ to Revenue Cloud migration playbook covers what a rebuild involves.

The field: every vendor has a real strength, and an open question

A fair reading of the market credits what each vendor does well. The right-hand column is what we would ask each one, ourselves included, before signing a multi-year term.

Vendor Where it is strong The open question for 2027
Salesforce Revenue Cloud
Public company · core platform
Enterprise breadth from one vendor: contract management, order orchestration and a consumption-billing roadmap. Shipped agent features and strong analyst validation. The all-in price at renewal once billing and add-ons are included. What the Migration Assistant will not convert. Which changes an admin can make without specialist skills.
Conga
Thoma Bravo (private equity)
Deep contract management and document generation; price optimization from PROS; Fortune 100 references; works with several CRMs. Two CPQs under one brand. Ten C-suite appointments since April 2025. Pricing runs on Conga's own price lists; its engine for large carts prices them off-platform.
DealHub
Venture and growth equity · $100M round, January 2026
Multi-CRM; a buyer-facing deal room with e-signature; a large base of public user reviews. The quote master sits in DealHub's database with a copy synced to Salesforce. Two billing engines until Subskribe is integrated. No published prices.
Subskribe
Owned by DealHub since November 2025
Finance-grade subscription billing and revenue recognition for SaaS; HubSpot support. No public release notes since October 25, 2025. No published integration date. A second migration when the platforms merge.
Nue
Venture-backed
Usage, credit and commit pricing for AI and SaaS companies; quoting inside ChatGPT and Claude; marquee AI-company logos. CPQ is in Salesforce, but billing and usage run on Nue's AWS platform and sync back. About 90 days to go live on average, per its own VP.
Zuora
Silver Lake + GIC (private)
High-volume usage rating; a revenue-recognition subledger; a Gartner Leader for recurring billing. Subscriptions, Invoices and Payments live in Zuora and sync to Salesforce in batches. Priced per package, not per user.
Kugamon
Founder-led since 2009
Every quote-to-cash record in the Salesforce org; published prices and a fixed implementation fee; live in 4–8 weeks; #1 on the Salesforce AppExchange in its four categories (4.9 from 135 reviews). Salesforce-only by design. Lighter contract management. Not built for very high-volume usage rating. A smaller brand with less analyst coverage.
C-suite appointments since January 2025, by vendorLeadership turnover is concentrated where ownership changed. C-suite appointments since January 2025, counted from each vendor’s press releases and leadership pages. Salesforce and Subskribe are not charted; see the note under the chart. Conga10Nue4DealHub2Zuora1Kugamon0
Figure 4. Leadership turnover is concentrated where ownership changed. C-suite appointments since January 2025, counted from each vendor’s press releases and leadership pages. Salesforce and Subskribe are not charted; see the note under the chart.

The appointments counted: Conga's are CEO, President/COO, CFO (twice), CPO (twice), CRO, CMO, CTO and Chief People Officer; Nue's are COO, CMO and the CRO seat twice; DealHub's are CRO and CPO (February 2025); Zuora's is a Chief Product Officer (August 2026). Salesforce is not charted: company-wide, Business Insider reported five senior executive departures between December 2025 and February 2026 and six appointments, and these were not specific to Revenue Cloud. Subskribe is not charted: two of its three co-founders have left operating roles at DealHub, per their public profiles (October 2026).

What the pattern says. The vendors with the most leadership change are the ones in the middle of an integration. Stability cannot be shown in a demo, but it decides whether the roadmap you bought is the roadmap you get. Kugamon sits at the stable end of this chart and is also the smallest company on it, so ask us the same question.

AI features have converged. Architecture has not.

Since mid-2025, every active competitor in this assessment has shipped or announced a quoting agent, an MCP server, or both. When everyone has the feature, it stops being the differentiator. What an agent can reach, in one place and under one set of permissions, becomes the test.

Vendor AI shipped or announced Where the agent's data and logic live
Salesforce Revenue Cloud Agentforce quoting (generally available, Summer '25); Revenue Cloud tools through Salesforce MCP (targeted October 2026) In the org, on the core platform
Conga Quote Agent on Agentforce with a Claude MCP connector (October '26 release); MCP Server (October 14, 2026) In-org package on Conga's own pricing objects; its large-cart engine runs outside
DealHub Conversational quoting; MCP for Admin (announced September 9, 2026) DealHub's platform; a quote copy synced to Salesforce
Nue Nue AI on its MCP server (October 27, 2025); quoting inside ChatGPT and Claude (September 2026) Split: CPQ in the org; billing and usage on AWS
Zuora AI agents and Zuora MCP for all customers (April 16, 2026) Zuora's platform; batch-synced to Salesforce
Kugamon A public AI skills library on GitHub (github.com/kugamon); records readable by Agentforce and Salesforce-native AI tools In the org

On shipped quoting agents the larger vendors are ahead of Kugamon, whose AI position rests on data location and published skills rather than a packaged agent.

Three vendors, three architectures, one argument: AI needs a single data model. They differ only on where it should live.

Disconnected revenue tools create "data chaos that limits the potential of AI and agents."

Salesforce, June 2025

“Quote, order, usage, and billing live on the same model.”

Nue, May 2026

Subskribe will be delivered through a "single user experience and unified data model."

DealHub, November 2025
The path from an AI agent to the revenue record, on one platform and on a split stackEvery system boundary is something an agent has to cross. The path from an AI agent to the revenue record on one platform and on a split stack. A Kugamon illustration of the two architectures the vendors’ own documentation describes. ONE PLATFORMSPLIT STACKAIagentONE SALESFORCE ORGQuote, Order and Invoice recordsPricing rules and approvalsPermissions and audit trailAIagentSalesforcea synced copysyncExternal enginemaster dataand pricing logicsync to wait forsecond permission modelsecond API or MCP serverintegration to maintainone security model · one transaction · current data · nothing to syncthe agent reads a copy, or crosses a boundary to reach the truth
Figure 5. Every system boundary is something an agent has to cross. The path from an AI agent to the revenue record on one platform and on a split stack. A Kugamon illustration of the two architectures the vendors’ own documentation describes.

The data's address decides what an agent can do

A synced copy is a photograph. An agent working from a photograph either acts on stale numbers or calls a second system under a second set of permissions. Each vendor's own documentation shows where that boundary sits.

Where each of seven vendors masters Quotes, Subscriptions, Invoices and PaymentsSeven vendors, seven answers to “where does the record live?” Where Quotes, Subscriptions, Invoices and Payments are mastered, by vendor, from vendor product and developer documentation checked October–November 2026. ALL IN THE SALESFORCE ORGOUTSIDE SALESFORCE, SYNCED INKugamonQuote-to-cashrecords all live inthe orgRevenue CloudCore platform, newdata model; billingsold separatelyCongaIn-org package,own price lists; bigcarts can priceoff-platformNueCPQ in the org;billing and usage onAWS, synced backZuoraSubscriptions andinvoices in Zuora;batch-synced inDealHubQuote master inDealHub’sdatabase; copysynced inSubskribeSeparate app andlogin; synced to itsown custom objects
Figure 6. Seven vendors, seven answers to “where does the record live?” Where Quotes, Subscriptions, Invoices and Payments are mastered, by vendor, from vendor product and developer documentation checked October–November 2026.

What the vendors' own documentation says about the sync

  • Zuora. "Real-time" sync to Salesforce through Zuora 360 / the Zuora Connector for Salesforce CRM runs after 10 change events or 120 minutes by default; a full sync can take hours.
  • Nue. Commerce APIs run on AWS against a replicated copy of the data model and write back to Salesforce asynchronously.
  • DealHub. Quote data is logged in DealHub's database; the Subskribe API is not currently available to DealHub CPQ customers.
  • Conga. When enabled, TurboEngines move cart pricing and configuration to Conga's compute platform, kept aligned by data sync.
  • Kugamon. No sync: Quotes, Orders, Invoices, Payments and Subscriptions are package records in the customer's own org.

What "native" has to mean. Data in the org is necessary, not sufficient. Salesforce argues that its own legacy CPQ package is not agent-ready, because its logic was tied to screens rather than exposed as something an agent can call. The test for any platform is practical: can an agent read the record, run the pricing rule and respect the approval policy without leaving the org? Kugamon is a managed package too, so the same test applies to us: its records sit in the org and its public skills library documents the object model for agents.

Where non-native still wins. Estates that run more than one CRM (DealHub, Conga Smart CPQ). Very high-volume usage rating and a revenue subledger (Zuora; Nue for credit-based AI pricing). Buyer-facing deal rooms as the primary requirement. If one of these is the core need, architecture alone should not decide the shortlist.

Our assessment. For companies that run revenue on Salesforce, AI tips the long-running native versus non-native argument toward native. Agents multiply the cost of every system boundary: each one adds a sync to wait for, a permission model to reconcile and an integration to maintain. One platform removes the boundary instead of managing it. In this set, Revenue Cloud and Kugamon are the two that keep the records in the org; they differ in data model, price and time to adopt.
  • Reporting. Native reports and dashboards run on live records. A split stack reports on the last sync, and the two systems can disagree in between.
  • Automation. One Flow can span Quote, Order, Invoice, Payment and renewal. Across systems, automation stops at each boundary and the logic moves into middleware.
  • Governance. Agents inherit the sharing rules, field-level security and audit trail already governed in the org, not a second directory to keep aligned.

Build vs. buy: a build can produce a quote. It cannot carry complex CPQ.

With the incumbent frozen and AI coding tools everywhere, more teams are asking whether to build their own. For a price list and a quote template, a build is feasible. The trouble starts where CPQ gets complex. Every vendor in this report ships these rules as product; the last column shows Kugamon's.

Complex CPQ requirement What a build must get right, every time Where builds stall Packaged instead: Kugamon's version
Bundles, options and configuration rules Valid combinations, dependencies and exclusions, re-tested on every catalog change Every new product becomes a development ticket Kits and bundles with required and optional members; configuration groups
Tiered, volume and account-specific pricing The order of the price waterfall, rounding, currency and effective dates Exceptions accumulate in undocumented code Tiered, volume and account-specific pricing on Salesforce Price Books
Approvals and discount governance Multi-level routing, delegation and an audit trail Cut from version 1; rebuilt under audit pressure Salesforce approvals and Flow approvals, with the platform's audit trail
Amendments, co-terming and proration Mid-term changes priced to the day and rolled into one renewal Where builds quietly produce wrong revenue numbers Expansion Orders co-term and prorate to the Contract end date
Renewals and price uplifts Renewal opportunities, notices, increases and contract hierarchy Handled by hand, missed, or kept in a spreadsheet Automated Renewal Opportunities, Orders, notices and uplifts
AI readiness A documented object model and logic an agent can call safely No published skills or documentation Records in the org; a public skills library for agents
Relative effort to own a custom build and a packaged platform as CPQ scope grows (illustrative)The effort to own a build rises with every layer of CPQ complexity. Illustrative, not measured: the relative effort to build and maintain each layer, against a packaged platform whose rules ship with the subscription. Effortto ownPrice list and templateBundles and tiersApprovalsAmendments andco-termRenewals and billingCPQ scope, from simple to complex →a build is feasible hereCustom build: every rule is yours to write, test and maintainPackaged platform: the rules ship with the subscription
Custom buildPackaged platform (Kugamon and its peers)
Figure 7. The effort to own a build rises with every layer of CPQ complexity. Illustrative, not measured: the relative effort to build and maintain each layer, against a packaged platform whose rules ship with the subscription.
  • AI lowers the cost of writing code. It does not lower the cost of knowing which proration rule is right, or of owning the result. Generated code still needs an owner, a reviewer and a maintenance budget.
  • The numbers. Our estimate for a custom CPQ: 8–16 developer weeks of code and 2–3 quarters to go live. Nucleus Research (2024) found an average 121% ROI across its CPQ ROI case studies, with payback within 16 months of deployment; that is an average, not a guarantee.
  • Maintenance you cannot defer. Salesforce ships three releases a year. Each is a regression test a vendor runs for its customers, and one a build team runs alone.

When build is right: the capability is your product, no vendor solves it on your platform, and you will fund a permanent team to own it. Quoting, billing and renewals rarely meet that bar. The full argument is in build vs. buy.

Economics: three-year cost separates the field more than list price does

Published per-user prices in this market run from $65 to $200 a month, about three to one. Three-year totals in our model run more than six to one, because implementation and administration, the lines least often quoted, differ far more than licenses do.

Three-year cost comparisonThree-year cost at 50 users, five platforms. Licence, implementation and admin. Kugamon’s licence and implementation are published (solid). Every competitor segment is an estimate (hatched): the midpoint of the low and high cases in our October 2026 competitor research. Run your own numbers in the ROI calculator. Revenue Cloud Advanced$333K$375K$189K$897KConga CPQ$211K$270K$120K$601KDealHub$149K$283KNue$231K$120K$435KKugamon$117K$143K
Solid = published priceHatched = estimate
Figure 8. Three-year cost at 50 users, five platforms. Licence, implementation and admin. Kugamon’s licence and implementation are published (solid). Every competitor segment is an estimate (hatched): the midpoint of the low and high cases in our October 2026 competitor research. Run your own numbers in the ROI calculator.

Reading the model. Fifty users, three years, a three-year term: about $143,500 for Kugamon CPQ, against about $283,000 for DealHub (2.0×), $435,500 for Nue (3.0×), $601,500 for Conga CPQ (4.2×) and $897,000 for Revenue Cloud Advanced (6.3×). Kugamon's license and implementation fee are published; its administration cost is an estimate. Competitor figures are estimates: the midpoint of the low and high cases in our October 2026 competitor research, with every competitor's admin cost counted. Right-size the model to your own seat count in the ROI calculator before using it; the three-year total cost of ownership page shows the working.

Where the comparison differs. Zuora prices by package, not by user: about $538,000 on the same model, against about $266,500 for Kugamon Subscription Billing, the comparable edition (both estimates apart from Kugamon's published license and fee). Kugamon is not always cheapest: below roughly $25 million in annual billings, Subskribe's own calculator puts a 50-seat bundle under Kugamon Subscription Billing.

Two vendors publish a full per-user price list. For the rest, ask for an all-in three-year figure before comparing.

Vendor What is public The published figure
Kugamon Full per-user price list and a fixed implementation fee $65–$125 per user per month by edition; $15,000–$30,000 implementation (pricing)
Salesforce Revenue Cloud Per-user list prices; add-ons quoted $150 Growth, $200 Advanced per user per month, plus a CRM license
Nue A starting price only AppExchange: "starting at $90 per user per month"; platform fee, modules and implementation quoted
Conga No price list on conga.com One priced CPQ offer on AWS Marketplace: $5,400 per user for 36 months; not a list price
Zuora No price list on zuora.com AWS Marketplace packages: $75,000, $175,000 and $250,000 per unit per year, not per user
DealHub Package names and features, no prices Growth and Scale packages; billing only in Scale
Subskribe Calculator estimates after a contact form Estimates, not list prices

Marketplace offers and calculator estimates are not list prices. Vendor websites, Salesforce AppExchange and AWS Marketplace listings were checked October–November 2026.

What to watch in 2027, and what to ask before you sign

The next twelve months will test several promises made in 2026. The questions apply to every vendor in this report, including the one that wrote it.

Seven signals to watch

  1. Does the Migration Assistant ship, and what does it leave behind? Targeted for December 2026. Scope and licensing are unpublished.
  2. Does m3ter metering arrive in Revenue Cloud? First capabilities are targeted for the first half of 2027.
  3. Does DealHub publish a date for Subskribe? Until it does, Subskribe customers are planning around a platform move with no schedule.
  4. Does Conga converge its two CPQs, or keep both? Either answer changes one roadmap.
  5. What will agent calls cost? Salesforce has said agents' MCP and API calls will draw down Flex Credits; the rate is not yet published. This affects every in-org approach, Kugamon's included.
  6. Does CPQ stay a place reps log into? Nue's leadership predicts it will not by the end of 2027. If quoting moves into chat and agents, the system that holds the data matters more, not less.
  7. Does Kugamon close its gaps? Watch for a packaged quoting agent and wider third-party review coverage, the two places it trails the larger vendors today.

Seven questions for any vendor

  1. Where do my Quote, Subscription and Invoice records physically live? Can I run a native Salesforce report on them without a sync?
  2. Which system runs the pricing logic an AI agent would call, and under whose permissions?
  3. What is the all-in three-year price at our user count?
  4. Will you commit to a fixed fee and a go-live date?
  5. Who owns this product's roadmap, and has that changed in the last two years?
  6. Which changes can our own admin make without code or a consultant?
  7. If you merge platforms after an acquisition, who pays for our migration?
Where Kugamon fits Where another vendor is the better choice
Salesforce is your system of record and you want it to stay that way You run more than one CRM, or are moving off Salesforce
A small or mid-market team that wants quoting, billing, subscriptions and renewals in one org Very high-volume usage rating or a revenue-recognition subledger is the core requirement
You want your own admin to run it, at a published price, live in 4–8 weeks Deep contract management and legal redlining lead the evaluation
You want AI agents to work on revenue data with nothing to sync first Price-optimization science or a packaged quoting agent is the deciding feature
The bottom line. The safest CPQ decision for 2027 is the one with the fewest moving parts: one platform for the data and the logic, one owner for the roadmap, and a price you can read before the first call. Consolidation, a frozen incumbent and AI agents each reward the same choice: revenue data and logic kept inside the Salesforce org, on a product with a stable owner.

How this assessment was built

  • Scope. The seven vendors Salesforce customers most often evaluate against one another for CPQ and quote-to-cash, and that Kugamon meets regularly in evaluations. It is not a survey of the whole CPQ market.
  • Evidence. Published means the vendor states it. Reported means a credible third party, a practitioner or a customer said it. Estimate means our model. Ratings carry the date they were captured.
  • Dates. Competitor research: October 2026 (Revenue Cloud addendum November 2026). Facts re-checked against live sources on November 22, 2026. Items marked "targeted" or "planned" are vendor roadmap statements, not shipped product.
  • Disclosure. Kugamon sells a Salesforce-native CPQ and is one of the vendors assessed. Read our conclusions with that in mind, and check the sources. This is the 2026/2027 edition; it is refreshed about every six months.

The PDF edition carries all 35 numbered sources. Product and company names are trademarks of their owners. Gartner and Magic Quadrant are trademarks of Gartner, Inc. This report reflects Kugamon's analysis of public information as of the dates shown and is not an endorsement by, or affiliated with, any vendor named.

SourcesThe State of CPQ on Salesforce, 2026–2027 (Kugamon, PDF with all 35 sources)Salesforce, Salesforce CPQ: End of Sale (Not End of Life)Salesforce, Revenue Cloud pricingSalesforce+, Dreamforce 2026 Revenue KeynoteCRM Hacker, Dreamforce 2026 Revenue Cloud recap (September 17, 2026)Salesforce signs definitive agreement to acquire m3ter (Salesforce newsroom)Salesforce will charge Flex Credits for agentic MCP and API calls (SalesforceBen)Salesforce CPQ migration typical timeline (Forsys)Silver Lake and GIC complete acquisition of Zuora (Zuora newsroom)Zuora AI adds new agents across quote-to-cash (Zuora newsroom)Overview of Zuora CPQ for Salesforce (Zuora documentation)DealHub acquires Subskribe: your questions answered (DealHub)Subskribe API overview (DealHub developer documentation, updated August 24, 2026)DealHub pricing (dealhub.io)Subskribe release notes (subskribe.com)Subskribe pricing and plans (subskribe.com)Thoma Bravo (PROS Holdings acquisition, December 9, 2025)Conga press releases (PROS B2B acquisition, executive appointments, MCP Server)Conga recognized in the 2026 Gartner Magic Quadrant for CPQ Applications (Conga press release, February 5, 2026)About TurboPricing (Conga documentation)Conga Advantage CPQ on AWS MarketplaceYes, Nue CPQ is native to Salesforce (nue.io)Nue's implementation still takes 90 days (SaaStr, sponsored post)Nue on the Salesforce AppExchangeNucleus Research, CPQ benefit areas driving the most value (2024)Kugamon on the Salesforce AppExchangeKugamon on YouTube (riteSOFT and Branch customer interviews)
Common questions

The State of CPQ on Salesforce — questions

All questions →

Kugamon wrote it, and Kugamon is one of the seven vendors assessed. We cite public sources, label estimates as estimates, and say where competitors are the better fit. Read our conclusions with that in mind, and check the sources.

The seven vendors Salesforce customers most often evaluate against one another for CPQ and quote-to-cash, and that Kugamon meets regularly in evaluations: Salesforce Revenue Cloud, Conga, DealHub, Subskribe, Nue, Zuora and Kugamon, plus building in-house. It is not a survey of the whole CPQ market.

This is the 2026/2027 edition. The competitor research dates from October 2026, with a Revenue Cloud addendum in November, and facts were re-checked against live sources on November 22, 2026. Items marked targeted or planned are vendor roadmap statements, not shipped product. We refresh the assessment about every six months.

No. Salesforce CPQ went end of sale in March 2025, which means no new customers. Existing customers can renew, add users and get support, no end-of-life date has been announced, and there is no forced migration.

The findings, exhibits and conclusions are the same. The PDF is the full 11-page report with every numbered source; the web page leaves out the third-party review-site statistics the PDF quotes.

Next step

Ready to see it inside Salesforce?

Thirty minutes on your data with someone who has done this before. No pitch — just honest guidance.