On June 16, 2026, HubSpot renamed Commerce Hub to Revenue Hub. Changing a name is rarely trivial for a software vendor, and here the word states the intention. “Commerce” suggested a one-off transaction: a payment link, an isolated invoice. “Revenue” refers to a continuous flow, that of B2B companies that constantly renew, expand and renegotiate contracts. Most of our clients live in this second world, not the first.
What drives this shift is not a new button. It is a data object. Since April 2026, HubSpot has had a native Contracts object that acts as the structural anchor between the quote, billing and renewal. It is what turns a series of isolated events into a cycle that stays up to date. The rest (enhanced CPQ, connected billing, built-in payments) is organized around this backbone.
This article is for sales, finance and RevOps leaders who want to understand what Revenue Hub actually covers, separate what has been delivered from what is still on the roadmap, and know what this change implies for a HubSpot portal already in production.
One figure sums up the problem this shift aims to solve. According to HubSpot's State of B2B Revenue 2026 study, 76% of revenue leaders say they miss renewals because their revenue data lives somewhere other than the customer record, and only 32% of finance and sales teams close the month from the same figures (source: State of B2B Revenue 2026, HubSpot). This is not a team problem. It is a context problem: the data exists, but not in the right place.
Presenting Revenue Hub as a standalone launch would be inaccurate. It is the result of a trajectory HubSpot has followed through three milestones.
In September 2025, the vendor delivered an advanced CPQ, able to handle more complex pricing configurations than the old quotes. In April 2026, the native Contracts object arrived: this is the real turning point, the one that allows quote data to become live revenue data. In June 2026, the rebranding made it all official and connected billing and payment schedules directly to the contract.
Why does this timeline matter to you? Because it shows where to focus your attention. The topic is not “a new Hub to buy”. The topic is: your quote-to-cash can now live natively in HubSpot, provided your data model is ready to accommodate this Contracts object and the associations it requires.
Revenue Hub brings together three building blocks that many organizations currently manage in separate tools: quote configuration and editing (CPQ), contract-based billing, and payment collection. The value is not in placing them side by side, but in continuity: a signed quote becomes a contract, the contract carries the billing schedule, invoices are paid, and renewals or expansions start again from the existing contract.
The new quote editor drops the old multi-tab format for a single-page drag-and-drop interface. Sales reps generate personalized, branded quotes directly from a deal record.
Breeze, HubSpot's AI assistant, can produce a sales cover letter or an executive summary based on the customer data already in the CRM. The assistant appears directly in the editor, at the level of the module being written.
In substance, CPQ brings capabilities the old quotes lacked: tiered pricing (volume, graduated or stairstep), standard and advanced approvals, quote activity tracking (who opened it and when), attachments, and quote rules that block or warn when a product combination or discount goes outside the limits. Basic conditional logic, such as product dependencies or discount rules, is now available.
This is where the Contracts object comes into its own. When a quote is accepted, a contract is created automatically and provides visibility on ACV, ARR and MRR. Changes (upgrades, scope reductions, renewals) are managed from this contract, with traceability between the renewal contract and the original contract. Invoices are generated from HubSpot, with schedules, credit notes and automatic reminders.
The last link closes the loop. Payments are collected in HubSpot via HubSpot Payments (available only in the United States, the United Kingdom and Canada) or via Stripe wherever Stripe operates. In France, HubSpot Payments is not available, so native collection goes through Stripe. Payment links, invoice payments, saved payment methods, dispute and refund management, automatic retries of failed payments: every transaction stays attached to the CRM record.
Here is our position, and it is not neutral. Revenue Hub brings HubSpot closer to the world of finance and billing, but it does not turn HubSpot into an ERP. This is a distinction we maintain on all our projects, and one that product marketing has little interest in stating.
HubSpot remains an agile CRM suite, designed for day-to-day interactions with prospects and customers across all channels. An ERP handles a different kind of complexity: cost accounting, inventory management, fine-grained usage-based billing, supply chains, advanced tax constraints. The best architectures we deploy aim for the best of both worlds: an ERP optimized for business complexity, backed by HubSpot for customer relationships.
What Revenue Hub brings that is new is therefore not a replacement for your ERP. It is bringing the revenue context back to where the customer context already lives. Before, your teams had the “who” (the contact, the history, the pipeline) without the “how much” (what was bought, paid, what is coming up for renewal). Revenue Hub brings the two together. This is valuable. It is not the same thing as replacing a financial system.
A practical consequence: if your real need is usage-based billing, inventory management in the quote or full guided selling, HubSpot CPQ does not yet cover these cases. The vendor acknowledges this itself. These needs call either for an ERP or for a third-party CPQ connector, and they will be the subject of a dedicated article.
One limitation needs to be stated clearly for the French market, and HubSpot's launch materials do not mention it. Revenue Hub's native billing is not an electronic invoicing solution compliant with the French reform.
From September 1, 2026, all companies will have to receive their B2B invoices in a structured electronic format (Factur-X, UBL or CII), and large and mid-sized companies will also have to issue them via a certified e-invoicing platform (PDP, Plateforme de Dématérialisation Partenaire). SMEs and very small businesses will follow on September 1, 2027. Standard PDF invoices will no longer be accepted for domestic B2B transactions.
HubSpot generates invoices, not structured electronic invoices transmitted via an approved PDP. The consequence is concrete: Revenue Hub remains relevant for managing the quote, the contract and collection in the CRM, but issuing the compliant legal invoice will go through a PDP or a connected ERP. This is an architecture topic to scope upfront, not to discover in September 2026. The same logic applies to collection: since HubSpot Payments is not available in France, Stripe takes over.
A useful article has to make a distinction that launch materials rarely make: separating what you can activate today from what has been announced. Revenue Hub is being rolled out gradually, by portal and by edition. And some of the most frequently cited features are in beta or planned.
| Status | Capabilities |
|---|---|
| Available and usable | New CPQ editor, drag-and-drop quote templates, tiered pricing, standard and advanced approvals, quote activity tracking, e-signature, quote rules, Contracts object, billing, payments (HubSpot Payments or Stripe) |
| In beta / private beta | Price Books (private beta, GA targeted for end of June 2026), Breeze Closing Agent, Revenue Agent (private beta, public beta to come), Customer Agent on billing questions, customization with React modules |
| Announced / roadmap | Automated tax, write access via MCP for AI agents, dedicated pricing model for billing |
Indicative table as of June 17, 2026, to be cross-checked with the current HubSpot documentation: the rollout is gradual by portal and by edition.
Our recommendation fits in one sentence: evaluate Revenue Hub on what has been delivered, not on the roadmap. HubSpot says so explicitly in its own disclaimers: a purchasing decision should not rely on announced features that may change at any time.
Many organizations still use Sales Hub's legacy quotes. Moving to Revenue Hub's CPQ should be planned, because it is neither automatic nor without trade-offs.
Three points to anticipate. First, templates do not transfer: a legacy quote template cannot be reused as is in the new tool and has to be rebuilt. Second, some capabilities remain specific to legacy quotes today: payment schedules set directly on the quote, and templates fully coded in HubL. The new CPQ uses a different advanced customization logic, based on React modules (in beta), which is more modular but different. Finally, access to the new CPQ requires a Revenue Hub Professional or Enterprise edition and seats assigned to the users who create or send quotes.
The good news: coexistence is possible. An account can keep access to legacy quotes while activating the new ones. Sales Hub Starter, Professional and Enterprise accounts keep access to legacy quotes. But coexistence does not mean no decision is needed: leaving two quote experiences open without a clear rule creates inconsistency in sales data, which is exactly what CPQ is supposed to prevent.
Revenue Hub's most ambitious promise is not fast quoting. It is the idea that your revenue context, once centralized in HubSpot, can be queried by any AI via API, MCP and CLI. Asking an agent “which accounts renew this quarter and how much do they pay?” and getting a usable answer.
This promise rests on a silent assumption: that revenue data is clean, structured and governed. This is the assumption that most often turns out to be false. The mechanism is the same as for Breeze agents: AI does not check the data, it consumes it. A poorly associated Contracts object, duplicate products, ambiguous lifecycle stages, and the agent querying your revenue produces wrong answers with complete confidence.
Our conviction, which applies to revenue as much as to the rest of the portal: AI amplifies what already exists. On a clean base, it multiplies teams' capacity. On disorganized data, it reproduces errors at scale. This is why we approach Revenue Hub as a RevOps project before a tool project: scoping the revenue data model, structuring the Contracts object and its associations, governing permissions on a quote's sensitive fields, then activation. This is the work we carry out in our SalesOps and Data consulting.
Revenue Hub is aimed first at B2B SaaS and services companies with recurring or contractual revenue that currently manage their quote-to-cash in scattered tools. For this profile, the value is real as soon as three conditions are met: a well-controlled product catalog, quoting and approval processes that can be formalized, and a commitment to maintaining revenue data over time.
Conversely, two situations call for caution. Organizations whose core need falls under ERP (inventory, fine-grained usage billing, complex product configurator) will quickly reach the current limits of CPQ. And portals whose data is not governed would do well to address that first before adding a transactional layer, or they risk turning a quoting problem into a revenue problem.