HubSpot Revenue Hub brings quoting, contracts, subscriptions, invoicing, and payments together in HubSpot, making it easier to manage what happens from the moment a customer agrees to buy through the revenue that follows, without relying on as many disconnected tools or manual processes.
In June 2026, Commerce Hub became Revenue Hub.
Beyond the name change, the shift brought more of the revenue process into HubSpot, expanding beyond billing and payments to include quotes, contracts, subscriptions, invoicing, and payments.
There’s a lot packed into Revenue Hub, but not every part of it will matter to every business. And if you already have a quoting or contract process that works well, there may not be a reason to replace it.
This guide will help you sort through it all…what changed, how the major pieces of HubSpot Revenue Hub work together, and when they actually make sense for your business.
HubSpot Revenue Hub is HubSpot’s unified quote-to-cash platform. It brings the major steps involved in turning a deal into revenue into one connected system.
The flow looks like this:
CPQ → Contracts → Subscriptions → Invoicing → Payments
That connection is what makes Revenue Hub different from a collection of standalone tools. Products and pricing can move from the deal into the quote. Once the buyer accepts, a Contract record can be created when that setting is enabled, carrying the process forward into the next stages of the customer relationship.
HubSpot officially launched Revenue Hub on June 18, 2026. Rather than starting from scratch, HubSpot built on the foundation of Commerce Hub and widened its role in the revenue cycle.
Commerce Hub centered more heavily on billing and payments. Revenue Hub reaches further upstream, adding CPQ and Contracts alongside Subscriptions, Invoicing, and Payments.
The result is a broader path through HubSpot, starting with how a business structures and sells an offer and continuing through how that revenue is managed after the sale.
The easiest way to understand HubSpot Revenue Hub is to follow the records as a customer moves through the revenue process:
Company + Contact → Deal → Products + Line Items → Quote → Contract → Subscription/Invoice → Payment
It starts with the Company and Contact records tied to a Deal. Products and Line Items capture what the customer is buying and at what price, and those details can then be used to create the Quote the buyer receives.
Once that Quote is accepted, the process can keep moving without losing the connection to the original sale. When automatic Contract creation is enabled, HubSpot can create a Contract tied to the Deal and Quote. That Contract becomes the record for what was agreed to, including the Products, dates, and other details needed to manage the agreement over time.
From there, the Contract can connect to subscriptions and invoices, with payments completing the flow. If something changes along the way, Change Quotes and Renewal Quotes give teams a way to manage those updates while keeping them tied to the existing Contract.
That connection between records is an important part of how Revenue Hub works. Rather than treating pricing, quotes, contracts, renewals, and billing as separate processes, each one can build on the information that came before it.
Some of the biggest changes in HubSpot Revenue Hub happen before a quote ever reaches the buyer. Teams now have more ways to structure pricing, control which prices sellers can use, build quotes, and carry the final agreement into a Contract.
For companies with quantity-based pricing, a simple Product Library can get complicated fast. One way to handle different quantity ranges is to create separate versions of the same Product at different prices. As the number of Products and pricing scenarios grows, so does the amount of information the team has to maintain.
Tiered Pricing gives teams another way to handle that complexity. Instead of creating a different Product for every quantity range, pricing can change based on how much the customer buys.
HubSpot Revenue Hub supports three models:
With volume-based pricing, reaching a quantity tier sets the unit price for every unit purchased.
For example, if the price drops once a customer reaches 100 units, buying 100 units means all 100 are priced at that new per-unit rate.
Graduated pricing works differently. Each portion of the purchase is priced according to the tier it falls into.
So if a customer buys enough to reach multiple tiers, the units in the first tier keep that tier’s price, while the units that fall into the next tier use the next price.
Stair-step pricing uses the quantity range to determine one flat amount rather than a per-unit price.
Once the customer’s quantity falls within a particular range, the flat price attached to that range applies.
The real benefit is being able to handle quantity-based pricing without building a Product Library full of separate variations of the same offer.
That matters because manual quoting leaves more room for mistakes. Across modern CPQ implementations, organizations have reported 20–30% reductions in quoting errors, showing the potential impact of replacing manual or spreadsheet-based quoting with a more structured process.
Tiered Pricing can help by keeping the pricing logic with the Product instead of relying on sellers to sort through multiple versions or calculate the right price themselves. That can mean less Product duplication, less manual pricing work, and a cleaner Product Library
Tiered Pricing gives teams more flexibility when prices change based on quantity. Price Books take that flexibility a step further by helping teams manage different approved prices and terms for the same Products.
Instead of creating duplicate Products for every scenario, a Price Book lets you keep the same underlying Product and apply the pricing and terms that make sense for each sale. A company could use different Price Books based on customer segment, region, partner, currency, or another part of how it sells.
For sellers, that means they don’t have to sort through a long list of nearly identical Products to figure out which one applies. The Price Book can narrow the options and help guide them toward what they should be selling for that particular Deal.
A Price Book can define more than the price attached to a Product. Teams can configure which Products are included, their pricing, currency, billing frequency, and terms. They can also set assignment rules and determine who is allowed to select or override the Price Book.
The goal is to put the approved selling options in front of the seller without rebuilding the Product Library every time a different pricing scenario comes up.
Price Books can be assigned based on Deal information, helping match a Deal with the right Products, pricing, and terms from the start. That can make the process more guided instead of relying on the seller to know which option to choose every time.
There is one limitation to plan around. HubSpot can assign a Price Book when a Deal is created, but it doesn’t automatically reevaluate that assignment later if the properties used to make the decision change. For example, if the assignment depends on information from the Deal or associated Company and that information changes later, the original Price Book won’t automatically update with it.
That makes it important to think through not only which Price Books you need, but also when the information used to assign them becomes reliable in your sales process.
Quotes aren’t new to HubSpot, but Revenue Hub Quotes expand what teams can do with them. They work more like a native CPQ system, connecting pricing, Line Items, approvals, buyer acceptance, Contracts, and other parts of the revenue process.
Approvals can become a bottleneck quickly. Standard quote approvals often take 4–24 hours, while escalated approvals can stretch to 2–5 days. Revenue Hub’s approval workflows give teams a structured way to route Quotes through the right review process before they reach the buyer.
The process starts with the Deal and its Line Items. When a Quote is created, those Line Items are pulled into the Quote so the buyer can review the Products, pricing, terms, and other details of the offer.
Quote templates give teams a reusable starting point instead of rebuilding the same structure for every Deal. Depending on how your quoting process works, templates can account for branding, how Line Items appear, commercial terms, expiration, approvals, how the buyer accepts, and the payment experience where relevant.
Revenue Hub also supports different template types for new Quotes, Change Quotes, and Renewal Quotes. That gives teams a way to shape the Quote around what the customer is actually being asked to agree to, whether it’s the initial purchase or something happening later in the Contract.
How a buyer accepts a Quote is set at the template level. Revenue Hub supports three options: print and sign, e-signature, or accept without a signature. Once an Acceptance Method is set on the Quote Template, any Quotes created from that template inherit it.
This lets teams standardize how Quotes are accepted instead of having sellers make that decision each time they create one.
One important thing to understand is that a Quote is a snapshot of the Deal’s Line Items, not a live view that changes every time the Deal does.
When a Quote is created or last edited, the Line Items at that point are captured in the Quote. If someone goes back and changes the Deal afterward, those changes do not automatically update the existing Quote.
That separation matters when a Deal is still changing. Teams need to make sure the Quote reflects what they actually intend to send rather than assuming later Deal updates will carry over automatically.
A lot of the standard Quote experience can be handled with Revenue Hub’s templates and built-in modules. The complexity starts to increase when the Quote needs to go well beyond those standard options.
Heavily customized designs, custom modules, conditional presentation, integrations, or significant custom logic can turn the Quote into a more technical build. In those cases, it’s important to understand the requirements before assuming they can be handled through standard Quote configuration alone.
One of the bigger additions covered in HubSpot Revenue Hub is the new Contracts object. It gives teams a central place to track what a customer has committed to, including the Products they purchased, revenue information, important dates, renewals, and any changes that happen along the way.
That visibility matters when contract information is spread across the business. Contract data is scattered across an average of 24 internal systems, while poor contract management practices can cost organizations roughly 9% of annual revenue.
The Contracts object gives that information a more centralized place to live in HubSpot. As the customer relationship changes, the record can continue to reflect what’s active now and what’s coming next.
A HubSpot Contract record does not replace the actual legal contract or MSA between you and the customer.
Think of it as the structured CRM record for the commercial relationship. It gives teams a place to track the details they need to manage that relationship over time without treating the legal document itself as the working record.
Contracts can pick up where the quoting process leaves off:
Deal → Quote → Buyer Acceptance → Contract
When automatic Contract creation is enabled, accepting a Revenue Hub Quote can create a Contract and associate it with the Quote and related Deal, Contact, and Company records. That keeps the agreement connected to the CRM records that led up to it instead of starting a separate process after the sale.
Once created, the Contract gives teams a place to see and manage key information about the agreement. That includes the Contract status, effective and start/end dates, current and upcoming Line Items, billing-related information, and changes made over time.
The Contract can also serve as the starting point for what happens later. If a customer changes what they’re buying during the term or reaches renewal, those next steps can stay connected to the existing Contract rather than being handled as unrelated transactions.
Customer agreements don’t always stay the same from start to finish. A customer might add more of what they’re already buying, purchase something new, reduce quantities, or change the pricing or terms of the agreement. Change Quotes give teams a way to handle those updates without losing the connection to the active Contract.
A Change Quote can be created from an active Contract and used for upgrades, added Products, quantity changes, downgrades, pricing changes, and term changes. Once accepted, the changes can be reflected in the Contract so teams can keep track of how the agreement has changed over time.
Revenue Hub can also account for proration when a change happens partway through a billing period. Depending on how the process is configured, that can account for the charges or credits tied to the remaining portion of the period rather than treating the change as if it happened at the beginning.
Say a customer starts a Contract with 50 seats and later needs 75. Instead of creating an entirely separate agreement, the team can create a Change Quote from the active Contract to capture the additional 25 seats.
That keeps the change tied to the Contract the team is already managing and provides a clearer record of what the customer originally purchased and what changed during the term. If proration is part of the setup, it can also account for the timing of that change within the billing period.
Renewals work a little differently from changes made during an active Contract. A Change Quote is used when a customer needs to update their current agreement, while a Renewal Quote is used to manage what the next Contract term will look like.
Change Quote = modify the current Contract
Renewal Quote = manage the next Contract term
Once the Renewal Quote is accepted, HubSpot can create the next Contract and associate it with the previous one. That keeps each new term connected to the customer’s Contract history rather than starting over with an unrelated record.
There’s also the work that needs to happen before a customer actually renews. HubSpot Revenue Hub can help teams manage renewal timing, ownership, Renewal Deals, pipelines, Renewal Quote Templates, and automation around the process.
That structure matters when revenue is on the line. Businesses can lose 5–10% of ARR to renewal process inefficiencies, including late outreach, missed renewals, and poorly tracked auto-renewals.
Teams can decide when an upcoming renewal should be flagged and whether a Renewal Deal should be created automatically. That Deal can move through the appropriate pipeline and eventually lead to a Renewal Quote for the customer’s next term. Workflows can support the process so upcoming renewals aren’t dependent on someone manually tracking every Contract end date.
This gives renewals a clearer path inside HubSpot while keeping the next Contract tied to the agreement that came before it.
Pricing, Quotes, and Contracts are a big part of HubSpot Revenue Hub, but they aren’t the whole picture. Revenue Hub also extends into Subscriptions, Invoicing, and Payments, carrying the revenue process beyond the initial agreement..
There’s a real cost to keeping those steps disconnected. 12% of invoices contain errors caused by manual data entry from contracts into billing systems, while CPQ deployments have been shown to shorten the quote-to-cash cycle by 30–50%.
Revenue Hub brings more of that process together, reducing the need for manual handoffs as a customer moves from an accepted agreement into billing and payment.
HubSpot Revenue Hub can be a strong fit when the way a company sells and manages revenue has become more complicated than it needs to be. That could mean pricing is handled manually, sellers have too many Product options to sort through, or Quotes and Contracts live across different systems with no easy way to connect them.
Revenue Hub is especially worth considering for companies that want to bring quoting and Contract management closer to HubSpot. Tiered Pricing and Price Books can give sellers more controlled pricing and Product options, while accepted Revenue Hub Quotes can create structured Contract records that stay connected to the original sale.
It can also make sense when managing what happens after the initial agreement has become difficult to follow. Change Quotes can support upgrades, downgrades, and other mid-contract changes, while Renewal Quotes give the next Contract term its own path. The Contract cycle can also account for how agreements are renewed or terminated.
The common thread is connection and visibility. When Sales, RevOps, Finance, and other teams need a clearer view of what was sold, what the customer agreed to, and what happens next, Revenue Hub gives more of that information a place to live together in HubSpot.
Having more of the revenue process in HubSpot can be useful, but that alone isn’t a reason to change a process that already works. Revenue Hub makes the most sense when it solves a real problem, not simply because the functionality is available.
If your team already has a mature quoting or e-signature process in a tool like PandaDoc, DocuSign, or DealHub, moving it into Revenue Hub isn’t automatically an upgrade.
The better question is whether Revenue Hub would actually improve the process enough to justify making a change. If your current setup is working well, replacing it just to move more of the process into HubSpot may not make sense.
Tiered Pricing and Price Books are useful when there’s real pricing complexity to manage. If every customer buys the same Products at straightforward prices, adding more pricing rules can create complexity that wasn’t there to begin with.
The pricing setup should match how the business actually sells. There’s no benefit in building a more sophisticated structure simply because Revenue Hub makes one possible.
Revenue Hub Quotes can handle a lot through templates and standard modules, but highly customized requirements are a different story.
Custom designs, modules, conditional presentation, integrations, or significant custom logic can make the Quote experience much more technical. Those requirements need to be understood before assuming they can be handled through standard Quote configuration.
Revenue Hub also shouldn’t be treated as the answer to every system involved in the revenue process. Complex ERP integrations, migrations, and deeper contract requirements such as CLM or redlining can extend beyond the scope of a standard Revenue Hub setup.
In those cases, Revenue Hub may still have a role, but that role needs to make sense within the larger system architecture rather than trying to force every part of the process into HubSpot.
A good HubSpot Revenue Hub setup starts before anything gets built. The decisions around Products, pricing, Quotes, and Contracts all affect one another, so getting those pieces clear upfront can prevent problems later in the process.
Start with what you sell and what causes the price to change. That could include quantity, customer type, region, or another part of the sales process.
Those decisions need to come before configuring Tiered Pricing, Price Books, Quotes, or Contracts. If the Product and pricing structure isn’t settled, it can hold up everything that depends on it.
Before building Quote templates, work through how quoting actually needs to happen.
Answering those questions first makes it easier to decide how Revenue Hub Quotes should be configured instead of building templates and rules before the process itself is clear.
The same thinking applies once a Quote is accepted. Teams need to decide when a Contract should be created, how its start and end dates are determined, who owns it, and how changes, renewals, and termination should work.
These decisions shape how Contracts are managed after the initial sale and what happens as the customer’s agreement changes over time.
Revenue Hub rarely exists in isolation. A business may already use CPQ, e-signature, billing, payment, ERP, or other systems that handle parts of the same process.
Those systems should be accounted for before deciding what belongs in HubSpot. An existing tool doesn’t need to be replaced simply because Revenue Hub can handle some of the same work. The goal is to determine where Revenue Hub fits within the process and where the systems already in place should continue doing their job.
Revenue Hub opens up more of the revenue process inside HubSpot, but there are a few details that can have a real impact on how everything works once it’s live.
Price Books can be assigned when a Deal is created based on information from the Deal or associated Company. The important catch is that HubSpot doesn't automatically reevaluate that assignment if those properties change later.
If a Deal is assigned one Price Book at creation and the information behind that assignment changes afterward, the Price Book won't automatically switch with it. That makes it important to think about when those properties are populated and how reliable they are at the time the Deal is created.
Accepted Quotes currently can't be deleted, which is especially important to know when testing the Quote-to-Contract process.
Acceptance testing should happen in a sandbox rather than production. That gives teams room to test what happens from Quote acceptance through Contract creation without leaving behind test records that can't be removed.
E-signatures also have monthly usage limits, and the amount available depends on the Revenue Hub subscription.
That gives Revenue Hub Professional accounts 50 e-signatures per month across two users, while Enterprise accounts get 250 per month across five users. Additional capacity can be purchased if needed.
If e-signature will be a major part of the quoting process, these limits are worth accounting for upfront rather than discovering them once Quotes are already in use.
Revenue Hub is still new, and the functionality is changing quickly. Features, availability, and limitations that apply today may change as HubSpot continues developing the product.
That makes current HubSpot documentation especially important when planning an implementation. Anything that could affect how the system is built (particularly feature availability, usage limits, or current product behavior) should be checked before the final setup is locked in.
To understand and implement HubSpot Revenue Hub effectively, teams should focus on:
HubSpot Revenue Hub is HubSpot’s unified quote-to-cash platform. It connects CPQ, Contracts, Subscriptions, Invoicing, and Payments so businesses can manage more of the process from an initial Deal through the revenue that follows within HubSpot.
HubSpot Revenue Hub evolved from Commerce Hub in June 2026. Commerce Hub focused more heavily on billing and payments, while Revenue Hub expands further upstream by adding CPQ and Contracts alongside Subscriptions, Invoicing, and Payments.
Yes. Revenue Hub includes CPQ capabilities that connect Products, pricing, Line Items, Quotes, approvals, and buyer acceptance. Features such as Tiered Pricing, Price Books, Quote Templates, and approval workflows give teams more control over how offers are priced and quoted inside HubSpot.
When automatic Contract creation is enabled, an accepted Revenue Hub Quote can create a Contract associated with the original Deal, Quote, Contact, and Company. The Contract acts as the structured CRM record for the commercial relationship and can track Products, dates, Line Items, revenue information, changes, and renewals over time. It does not replace the actual legal contract or MSA.
Revenue Hub can be a strong fit for businesses that want to bring quoting, pricing, Contracts, renewals, billing, and payments into a more connected process inside HubSpot. It is especially useful when manual pricing, disconnected systems, complicated Product options, or difficulty tracking changes and renewals are creating problems, but companies with mature CPQ, e-signature, ERP, or CLM processes should first determine whether moving those processes into HubSpot would actually improve them.