Quote-to-cash has moved inside HubSpot, and the change deserves more attention than it received. On 16 June 2026 HubSpot renamed Commerce Hub to Revenue Hub and expanded it from a billing and payments tool into a full quote-to-cash suite. Configure-price-quote built from live deal data, contracts, e-signature, subscription billing, invoicing and payment collection now sit on the same Smart CRM records as the opportunity that produced them. There was no press release, no keynote moment and no changelog entry on the day it shipped. A community post did the announcing.
That understatement is worth correcting, because the underlying move is one of the more useful things a CRM vendor has done for commercial teams this year. The join between a won deal and a sent invoice is one of the most expensive seams in B2B revenue architecture. It is where pricing gets re-keyed by hand, where discount approvals disappear into email threads, and where the finance system and the CRM quietly stop agreeing about what a customer actually bought. Closing that seam natively removes a category of work that mid-market teams have been paying integration specialists to patch for a decade. The capability is genuinely good news. The interesting question is not whether it works, but how much of your commercial model fits inside the envelope HubSpot has drawn.
What changed when Commerce Hub became Revenue Hub?
HubSpot Revenue Hub is the renamed and expanded version of Commerce Hub, announced on 16 June 2026. Where Commerce Hub handled payments, invoices and subscriptions, Revenue Hub covers the full quote-to-cash cycle: configure-price-quote generated from CRM deal data, AI-assisted quote drafting through Breeze, e-signature, contracts, recurring billing, invoicing and payment collection. All of it runs on HubSpot’s Smart CRM data model rather than as a bolted-on commerce layer, and connectors carry the output through to QuickBooks, NetSuite and Xero. A revenue agent for invoice follow-up and renewal management has been signalled as coming.
The July release wave filled in the detail, and the detail is telling. Sales tax now calculates in real time on quotes based on line item category and buyer address. Quote templates can be locked so that a representative can only edit the modules you allow. Reminder emails go out automatically before a quote expires. Paid and partially paid invoices accept line-item edits with automatic balance recalculation. Failed subscription payments can be retried manually rather than written off to a support ticket. Buy-now-pay-later arrived through Klarna and Affirm with the seller paid upfront, and HubSpot Capital added working capital financing for customers in the United States and the United Kingdom. Individually these are small features. Collectively they describe a product being built for finance teams, not just for marketers.
What is CPQ software, and what does HubSpot’s version cover?
CPQ stands for configure, price, quote. CPQ software takes a product catalogue, a set of pricing rules and a set of approval rules, then turns a salesperson’s selection into an accurate, approved, sendable quote without manual calculation. Good CPQ prevents the two failure modes that cost B2B companies the most money: quoting a configuration that cannot actually be built or delivered, and quoting a price that erodes margin below what the business ever approved. HubSpot’s native CPQ inside Revenue Hub builds quotes from live deal data, applies product library pricing, handles bundles and fixed or percentage discounts, and routes approvals before the quote leaves the building.
What makes the native version interesting is not the feature list but the provenance of the data. The quote is assembled from the deal record itself, not from an export that someone dropped into a separate quoting tool and then reconciled afterwards. That single architectural choice removes a surprising amount of daily friction. Representatives stop maintaining two versions of the truth. Sales managers stop asking which number is current. Finance stops receiving quotes that reference products the catalogue retired two quarters ago. For organisations that have spent years syncing a CRM to a quoting system and a quoting system to an accounting package, the appeal of collapsing three integrations into none is obvious and entirely rational.
Why the contracts object matters more than the new name
The most consequential piece of the release is not the rebrand at all. It is the contracts object arriving as a first-class citizen in the data model. A signed quote now becomes a contract record, and that contract flows into billing without anyone re-entering terms. A name change is cosmetic. A new object in the CRM schema is architectural, and it changes what questions the system can answer.
Consider how most mid-market companies currently answer the question of what they committed to. The answer usually lives in a signed PDF in a shared drive, cross-referenced against a line in the finance system, interpreted by whoever negotiated the deal. None of that is queryable, reportable or safe from staff turnover. A contracts object gives renewals, amendments, and revenue reporting a single anchor that sits next to the account and the deal. For revenue operations teams, this is the difference between inferring committed value from deal stage and reading it directly. Forecast accuracy tends to improve quickly when the forecast stops being an interpretation exercise.
What does HubSpot Revenue Hub cost?
Revenue Hub follows HubSpot’s usual tiering. The free tier covers invoices, payment links and subscriptions, which is enough for a small company that simply needs to get paid. Professional, listed at roughly 95 US dollars per seat per month, is where quoting, contracts, CPQ and e-signature unlock. Enterprise, listed at roughly 140 US dollars per seat per month, adds advanced approval workflows and expanded e-signature. Payment processing is charged separately per transaction rather than as part of the seat price. Native HubSpot Payments is available in the United States, the United Kingdom and Canada, with other regions routed through Stripe.
The practical budgeting question is not the headline seat price but the size of your quoting population. If every account executive builds quotes, the seat maths looks very different from an organisation where a small deal desk produces every quote on behalf of the field. European buyers should also plan around the payments geography carefully, because routing through Stripe is perfectly workable but changes the reconciliation picture and the working capital options available. None of this is a barrier. It simply means the cost model deserves a spreadsheet rather than an assumption.
How should a manufacturing company judge whether native CPQ is enough?
Start with the shape of your pricing, not the brand on your CRM. HubSpot’s native CPQ is built for standard product libraries, straightforward bundles, and fixed or percentage discounts. If your quotes are assembled from a catalogue and priced as list minus discount, native CPQ will very likely carry you comfortably. If your quotes depend on engineering configuration rules, multi-year ramps, usage-based components, guided selling logic, multi-entity legal structures or formal revenue recognition treatment, you will meet the edge of the native envelope and should scope a dedicated CPQ alongside it. The honest test takes an afternoon: pull your ten most complex quotes from last year and try to rebuild them.
For manufacturers the answer is usually more encouraging than people expect, because it is rarely all or nothing. Dimension-driven pricing, tooling and freight recovery, dealer and distributor price structures, and rules that stop a configuration being sold when it cannot be produced all sit outside what a general-purpose CRM quoting engine is designed to model. That is not a criticism of HubSpot, it is a description of what specialist configurators exist to do. What has genuinely improved is that this is now a clean two-tier decision rather than a build-it-yourself project. Many mid-market manufacturers will find that the large majority of their quote volume fits the native tooling perfectly well, while the genuinely complex configurations belong in a specialist product. Running that split deliberately is far cheaper than forcing every quote through the most expensive path available.
What does this mean for RevOps teams already running quote-to-cash?
Revenue operations is the discipline of running sales, marketing and customer success on one shared set of processes, data and systems so that revenue is managed end to end rather than function by function. Revenue Hub matters to RevOps specifically because quote-to-cash has historically been the stretch of the revenue cycle that RevOps could see but not control. Quoting lived in one tool, billing in another, and the handover between them belonged to nobody. Pulling that stretch onto the same platform as the pipeline puts it inside the RevOps remit for the first time in most organisations.
The migration deserves respect rather than caution. A full Revenue Hub rollout is closer in complexity to a CRM migration than to a settings toggle, and existing Stripe subscriptions require a payment-token migration that can pause billing temporarily. That is not something to attempt in a quarter-end week. The sequencing that works is deliberately unglamorous: bring quoting across first and prove the product catalogue and approval rules on live deals, adopt the contracts object next so renewal and committed-value reporting has an anchor, and move billing last once the first two are stable. Teams that follow that order tend to be live and reporting cleanly within a quarter. Teams that start with billing tend to spend that quarter reconciling.
There is also a straightforward early win available to anyone not ready for a full migration. Locked quote templates and automated tax calculation solve two problems that cost real margin, namely representatives editing terms they should not touch and tax errors surfacing after a quote has been accepted. Those are worth adopting on their own merits regardless of where the rest of your quote-to-cash stack eventually lands.
The Sirocco perspective
We think this release is a good thing for the mid-market, and we would rather say so plainly than perform scepticism. Vendors absorbing adjacent capability usually benefits customers who were previously paying integration tax for basic continuity between a deal and an invoice. Our reservation is not about the product, it is about the decision method. We see organisations reach for whichever quoting tool their CRM vendor most recently shipped, without first describing the shape of their own pricing. That is the step that determines whether native CPQ is a saving or a ceiling, and it takes days rather than months.
Because we work across Salesforce, HubSpot and Dynamics 365 without a quota attached to any of them, our advice on this question changes depending on what your quotes actually look like. Sometimes the right answer is that Revenue Hub covers everything you need and the specialist CPQ you were about to buy is unnecessary. Sometimes it is that your configuration logic genuinely requires a dedicated engine and the sensible design runs both, with a clear rule for which quotes go where. Both answers are good outcomes. The only bad outcome is discovering which one applies to you halfway through an implementation. If you are weighing that decision now, schedule a consultation and we will work through your quoting model with you.
Get in Touch
If you are weighing whether HubSpot’s native CPQ can carry your quoting model, or whether complex configuration still needs a dedicated tool alongside it, tell us what your hardest quote looks like and we will give you a straight answer.
