DealHub

What it is

DealHub is quote-to-revenue software for subscription businesses. A rep opens an opportunity in Salesforce, HubSpot or Microsoft Dynamics 365; DealHub configures the quote, routes the approvals, publishes a branded DealRoom the buyer works inside, captures the signature through its CLM layer, and hands the result to subscription management, billing and revenue recognition. That last stretch is new. DealHub acquired Subskribe — a subscription management, consumption metering and billing platform — on November 19, 2025, and now sells the whole chain as an agentic quote-to-revenue platform rather than a CPQ with integrations bolted to its downstream edge. On January 20, 2026 the company raised $100 million led by Riverwood Capital to fund that consolidation; the release does not disclose a valuation.

The AI layer has four named pieces: AI Conversational Quoting builds a quote from natural language instead of SKU picking, AI Pricing Optimization recommends a price from historical deal data, AI Decision Intelligence surfaces deal risk and discounting drift, and Native MCP exposes the revenue workflow to outside agents. DealHub’s framing for all of it is “governed execution” — the claim is that every AI output stays inside the same approval rules a human quote would hit.

Why it shows up in RevOps stacks

• Salesforce CPQ went end-of-sale on March 27, 2025, and that put every CPQ back on the table. Existing licenses carry extended support through March 2027 and Salesforce has announced no end-of-life date, so this is a planning window, not a cliff. But teams that were going to migrate anyway are now comparing a move to Agentforce Revenue Management against a move off Salesforce’s CPQ entirely, and DealHub sells directly into that comparison.
• Configuration instead of a development project. Vendor and partner reports put DealHub live in 4-8 weeks against 3-6 months for legacy Salesforce CPQ. The mechanism is that pricing rules, approval routing and quote logic are configured in a playbook rather than written as code, which also means a RevOps manager can change a discount threshold without a release.
• The quote-to-billing re-key is the point of the Subskribe deal. The standard break in quote-to-cash is a quote that configures cleanly and then cannot be handed to billing without someone retyping it. Owning both sides of that handoff is the strongest structural argument DealHub has against a best-of-category CPQ plus a separate billing vendor.
• Native MCP and a documented public API. DealHub lists MCP as a platform capability, and the developer docs publish an LLM-readable index of the API surface — so the quoting layer is addressable by an agent rather than only by a rep in a browser.

Pricing reality

Nothing is published. The pricing page shows two capability tiers — Growth, described as governed revenue execution, and Scale, described as advanced billing control — with no dollar figure, no seat minimum and no platform fee attached to either. Every number is a quote.

Buyer data fills the gap. Vendr reports a median annual contract of $44,297 across 144 analyzed purchases, a range of $14,839 to $118,130, and average savings of roughly 16% off the opening number. Buyer-reported per-seat pricing lands in the $60-100 per user per month band, which is consistent: at $80 a seat, that median contract is about 45 quoting users. Read it as a mid-market SaaS deal desk paying $40,000 to $50,000 a year, a small team landing near $15,000, and enterprise deployments with billing and revenue recognition in scope running past $100,000.

Best for

RevOps and deal desk teams at subscription companies with roughly 20-100 people who touch a quote, selling a mix of seats and usage on Salesforce, HubSpot or Dynamics, where the bottleneck is approval cycle time and the re-key between quote and invoice. It is the strongest pick when you want one vendor from configured quote through revenue recognition and you are willing to trade some pricing-science depth to get it.

Do not buy it if you sell one or two SKUs at list price — a quote template in your CRM does that job and a CPQ platform is overhead, as the CPQ definition spells out. Do not buy it for industrial or manufacturing configuration either: constraint-heavy physical product configuration is where Tacton and Oracle earn their money, and DealHub is built for subscription commerce.

Versus the alternatives

Agentforce Revenue Management (formerly Salesforce Revenue Cloud) is the incumbent path. Pick it when Salesforce is the system of record, the org is already deep in Salesforce customization, and staying inside one platform’s data model and one vendor’s support boundary is worth more than deployment speed. Pick DealHub when the previous CPQ implementation is the reason you are shopping, and you want the quoting logic out of the CRM’s release cycle.

Conga CPQ got significantly heavier on February 2, 2026, when it completed its acquisition of the PROS B2B business — CPQ, price optimization and rebate management — on top of a base of more than 10,000 customers. Pick Conga when pricing science is the actual requirement: dynamic price optimization, rebates, distributor and channel pricing. Pick DealHub when the hard part is deal flow and approvals rather than computing the right price.

Nue.io is the fastest-growing entrant, with a $20 million Series A led by Inovia Capital in January 2025 and three-fold year-over-year sales growth in 2024 behind a CPQ, billing and revenue recognition platform on a single data model. Pick Nue when you are a Salesforce-native SaaS company leaving Salesforce CPQ and want the newest architecture. Pick DealHub when you need the buyer-facing DealRoom and CLM layers too, or when a heavier customer base and a $100 million balance sheet matter to your procurement risk review.

If none of them fit, the problem is usually upstream: a price book nobody has agreed on. No CPQ can enforce a catalog and a discount policy that do not exist yet, and every one of these vendors will faithfully automate an incoherent one.

Watch-outs

• The Subskribe integration has no published timeline. DealHub says Subskribe will be folded into one platform and one data model, and that existing environments keep running with full support in the meantime — but the announcement names no phases and no dates. Guard: if billing or revenue recognition is part of why you are buying, ask in writing which platform your billing runs on at go-live, what the migration path is, and who pays for it. Buy the CPQ on today’s product; treat the merged data model as a roadmap item, not a feature.
• Every price is a quote, and the average buyer negotiates roughly 16% off. Guard: open with the Vendr band for your seat count, ask for the per-seat rate at the next tier boundary so you can see where volume actually pays, and cap the annual renewal uplift in the order form. A first quote here is an opening position.
• “Native MCP” is a platform capability, not a documented server you can point Claude at today. The dealhub-admin-mcp package on npm is community-built by an individual and covers five version-management tools — not quoting. Guard: if agent access is load-bearing for your plan, ask for the first-party MCP documentation and get it enabled in the trial tenant, then have an agent produce a real quote before you sign.
• AI Pricing Optimization learns from your historical deals, which encodes your historical discounting. A model trained on a team that discounts 30% by reflex will recommend 30%. Guard: set the margin floor and approval thresholds as hard rules before enabling recommendations, and grade the first quarter of AI-recommended prices against policy rather than against what the team used to do.
• The proof points are vendor case studies. Approval cycles cut from days to 8 hours and a 50% faster GTM rollout are DealHub’s own published customer results, with no independent replication. Guard: measure your current median approval cycle time and quote error rate before implementation starts. Without a baseline captured in advance you cannot tell improvement from a rollout honeymoon.
• The 4-8 week deployment assumes a clean price book. The speed comes from configuration, and configuration is fast only when someone has already decided what the products, bundles and approval tiers are. Guard: freeze the catalog before kickoff and count SKUs, bundle rules and approval paths. If that count is unknown, the discovery work is the project and the implementation estimate is fiction — see the deal desk pricing skill for the policy layer that has to exist first.