HubSpot Revenue Hub: Everything you need to know

What it is, what it does, who it’s for, where revenue leaks, and how to know if your business is ready.
HubSpot launched Revenue Hub on 16 June 2026. For mid-market businesses running on HubSpot, it represents a genuine change in what is commercially possible across CPQ, billing and payments connected inside the CRM for the first time.

But the announcement has generated a lot of noise. What exactly is Revenue Hub? Who is it actually built for? What does it cost? The question that matters most before any technology decision, is your commercial operation ready to benefit from it? Here is everything you need to know.

What Revenue Hub actually is
Revenue Hub is HubSpot’s new quote to cash platform. It brings three commercial capabilities – Configure-Price-Quote (CPQ), billing and payments – into HubSpot as a connected, native system.

The simplest way to understand it: Revenue Hub is what happens after a deal is won. Everything from the moment a quote is sent to the moment cash is collected and then through renewal and expansion, managed inside HubSpot, connected to the customer data already there.

It is a rebrand of Commerce Hub, but the rebrand reflects a genuine architectural change. The new Contracts object sits at the centre of Revenue Hub and acts as the single source of truth from signed quote through to renewal. Every subsequent commercial action – billing, invoicing, payment, amendment – flows from that record automatically.

This is what makes Revenue Hub structurally different from a billing integration. An integration translates data between systems. Revenue Hub eliminates the translation layer entirely.

The problem it was built to solve
Most mid-market businesses manage their commercial process across a fragmented set of systems. The sales team works in the CRM. Quotes are built in a separate tool or a spreadsheet. Contracts sit in email threads and shared drives. Billing is managed by finance on an accounting platform that does not connect to sales. Payments are tracked manually. Renewals are flagged when someone remembers to flag them.

Each part of this system works, more or less, in isolation. The damage happens at the joins and according to HubSpot’s own launch survey data, the impact is significant.

78% of revenue teams say data living in siloed systems actively limits their ability to make decisions.
Revenue Hub Launch Survey

72% report that their AI tools do not have access to the complete, accurate revenue data they need to act.
Revenue Hub Launch Survey

When revenue data is fragmented, four things consistently go wrong across the commercial operation.

Sales loses deals.
Manual quoting is slow. When reps have to navigate multiple tools to pull together a quote, time is lost — and time kills deals. Inconsistent pricing and errors in quotes create problems that take longer to fix than they took to make.

Customer success walks into renewals blind.
When CS has no visibility of what the customer bought, what they are currently paying, or when their contract ends, renewal conversations start from the wrong position. Churn that could have been prevented is not, and expansion opportunities that should have been obvious are missed.

Finance reconciles manually.
When billing lives in a separate system, someone has to bridge the gap between what sales closed and what finance invoices. That takes time, introduces errors, and delays collections — before a single invoice has been sent.

Revenue Operations fights integration fires.
Connections between systems break. Data goes missing at handoffs. What should be an automated flow requires constant manual intervention — consuming capacity that should be spent on commercial strategy.

Where revenue actually leaks 
Revenue leakage is the gap between the revenue a business should collect and the revenue it actually collects, on time, in full, without manual intervention. It is almost always larger than Revenue Leaders estimate — and almost always invisible until someone goes specifically looking for it.

These are the six places we consistently find it.

1. Slow and inconsistent quoting
Every hour between a commercial conversation and a quote in the prospect’s inbox is an hour for the deal to cool. When quoting requires a rep to find current pricing, check product configurations and adapt a previous document manually, the process is slow and the output is inconsistent.

Real example: A SaaS business with a 48 hour average quote turnaround
A 50-person SaaS business was losing deals at the proposal stage without understanding why. When they mapped the process, they found reps were spending an average of four hours assembling each quote, pulling pricing from a rate card spreadsheet, adapting a Word template, and waiting for a manager to review. By the time the quote arrived, two competitors had already responded. The deals were not being lost on price. They were being lost on speed.

2. Contract and approval bottlenecks
A deal that is won verbally but stalls in the contracting process is revenue that is not yet secure. Internal approval chains, legal review queues, and time spent locating the right contract template all extend the gap between commercial agreement and booked revenue. In most businesses, this gap is longer than anyone realises — and completely invisible on the pipeline report.

Real example: A professional services firm with a 12-day average time from verbal close to signature
A 120-person professional services business was hitting its pipeline targets consistently but missing its cash collection targets quarter after quarter. When they analysed the gap, they found that the average time from verbal agreement to signed contract was 12 days — during which deals sat in an approval process managed entirely by email. Three of those 12 days, on average, were simply waiting for someone to notice the approval request. The revenue was in the pipeline. The cash was not in the bank.

3. Invoicing lag
When billing is managed by finance on a system that does not connect to the CRM, invoices are raised after a manual communication from sales or operations. That handoff introduces delay. In businesses where invoices are raised on a fixed schedule rather than triggered by contract signature, the cash cycle is structurally elongated — regardless of how quickly the deal was won.

Real example: A recurring revenue business invoicing two weeks after signature
A 200-person software business with predominantly annual contracts was raising invoices at the start of each month, regardless of when the underlying contract was signed. A deal signed on the 3rd of the month would not be invoiced until the 1st of the following month — nearly four weeks later. Across 40 new contracts per month, this was deferring over £300,000 in receivables at any given time. Nobody had designed the billing schedule this way. It had simply never been questioned.

4. Missed renewals and expansion
In recurring revenue businesses, the renewal is where the commercial relationship is either extended or lost. When renewal dates are not tracked in the CRM, or when customer success teams do not have visibility of contract terms and payment history before the conversation, the outcome is predictable: more churn than necessary and less expansion than the customer relationship warrants.

Real example: A SaaS business losing 15% of renewals to administrative failure
A 300-person SaaS business with a strong NPS score was seeing higher churn than its satisfaction data suggested it should. When they audited the renewals that had lapsed in the previous 12 months, they found that 15% of churned customers had not received a renewal conversation at all — the contract end date had simply passed while it sat in a spreadsheet that no one had checked. The customers had not decided to leave. They had been allowed to drift.

5. Payment collection without context
When payments are not integrated with the invoice workflow, collections become a manual exercise managed by someone who does not have full commercial context. Reminders go out late or inconsistently. Disputes take longer to resolve because the information needed to resolve them lives in a different system. And overdue invoices do not surface automatically — they surface when someone looks.

Real example: A services business with 45-day average payment collection on 30-day terms
A consulting business operating on 30-day payment terms was averaging 45 days to collect. When they looked at why, they found that first payment reminders were going out on day 35 — five days after the invoice was already overdue — because the person responsible for chasing had to manually export the invoice list, cross-reference it against the bank, and then send individual emails. The process took half a day each week. Tightening it to send reminders automatically on day 28 reduced average collection time to 33 days within two months.

6. Reporting that is always behind
When commercial reporting requires manual reconciliation across systems, the picture it presents is always out of date. By the time the board pack is assembled from CRM pipeline data, finance billing records, and CS renewal tracking, the numbers it contains reflect a reality that no longer exists. Decisions made on lagging, manually assembled data are decisions made with incomplete information.

Real example: A business where the sales number and the finance number never matched
A 150-person technology business was going into every board meeting with two different revenue numbers, one from the CRM and one from finance, and spending the first 20 minutes of the meeting explaining the difference. The gap was not due to fraud or error. It was due to timing differences between when sales recorded a deal as closed and when finance recognised the revenue against the invoice. The data was correct in both systems. It just described two different versions of commercial reality. Without a single connected record, there was no way to reconcile them without manual work.

The three components and what they do
Revenue Hub is structured around three modular components. Customers can adopt one, two, or all three though the full commercial value comes from using them together, connected through the Contracts object.

CPQ – Configure, Price, Quote
HubSpot’s AI-powered quoting tool, native to the CRM. Reps create quotes directly from a deal record using Breeze AI, generating cover letters and executive summaries from deal data, applying pricing rules, and configuring products without leaving HubSpot. Quotes are branded, consistent, and trackable. Approval workflows, quote rules, and e-signature are all built in.

CPQ requires Revenue Hub Professional ($95/seat/month) or Enterprise ($140/seat/month). Sales Hub customers receive 30% off Revenue Hub.

Billing – Automated Revenue Billing
When a quote is accepted, HubSpot creates a Contract record automatically. That record becomes the source of truth for everything that follows, billing schedules, invoice generation, subscription management, amendments and renewals. Billing connects natively to QuickBooks Online and Xero. Automated sales tax is applied by buyer location.

Billing is currently included at no additional cost. A pricing model is expected in September 2026.

Payments – Integrated Payment Collection
Buyers pay directly from a quote, invoice, or payment link, without being redirected to an external system. Every transaction is connected to the CRM record. Stored payment methods support automated recurring collection. Multi-method support covers cards, ACH, SEPA, BACS, Apple Pay, and Google Pay. HubSpot Payments is available in the US, UK, and Canada. Stripe processing is available globally.

Payments is transaction based pricing only. No monthly fee, no minimum.

What it does not do… yet

• Mobile quote building is not currently supported
• API support for change and renewal quotes is on the roadmap but not yet available
• E-invoicing for EU regulatory compliance is in development but not live
• Automated VAT and GST is planned but not available – VAT can be applied manually using Tax Rates
• Direct Contract creation or editing without going through a quote is in development
• Migrating legacy quote data to the Contracts object requires a manual migration process

None of these are reasons to delay adoption. But they are important context for scoping an implementation, particularly for businesses with EU billing requirements or a large volume of existing quote data.

How to know if your business is ready
Revenue Hub is not right for every business at the same moment. These are the signals that suggest it is the right time to move.

Signs you are ready and will benefit quickly

• You are already on HubSpot and using Sales Hub for pipeline management
• Quoting takes more than 24 hours on average, or produces errors that require manual correction
• Billing is managed outside HubSpot, creating a lag between close and invoice
• Renewals are tracked in a spreadsheet, a calendar, or not reliably at all
• Finance and sales report different revenue numbers and reconciliation is a recurring exercise
• Payment collection is manual and your average collection time exceeds your payment terms

Signs you need to diagnose before you implement

• Your quoting process is inconsistent but you have not mapped what it should look like
• Your pricing model is complex and is not currently documented in a structured way
• Your contract terms vary significantly by customer and are managed informally
• You have a large volume of existing data in external billing systems that would need migrating

The second category is not a reason to wait. It is a reason to start with a diagnostic rather than an implementation. Understanding the current state of your commercial operation before making technology decisions is the difference between an implementation that works and one that replicates existing problems at speed.

The right way to approach it
HubSpot’s own implementation guidance is clear on this point: Revenue Hub is implementation-heavy, RevOps and finance-dependent, and configuration-intensive across the entire quote-to-cash process. The implementation approach is not incidental — it determines the outcome.

The right sequence is consistent regardless of the size or complexity of the business.

1. Diagnose. Map the current commercial operation end to end. Identify where it breaks down and what it is costing the business.
2. Design. Define what the commercial operating system should look like before configuring any technology.
3. Deploy. Implement the designed process inside Revenue Hub, with the configuration, automation and governance it requires.
4. Optimise. Measure commercial performance, identify what needs to improve and compound the value over time.

Businesses that implement Revenue Hub without the Diagnose and Design stages will go live faster. They will also find themselves three months later with a sophisticated platform sitting on top of the same operational complexity they had before.

The bottom line
Revenue Hub is a genuine step forward. For mid market businesses on HubSpot, it closes the gap between the commercial system they have – fragmented, manual, held together by effort – and the one they need.

But the technology is only part of it. The leakage examples in this article are not unusual. They are representative. Most scaling businesses have at least three of these six friction points active in their commercial operation right now. The question is not whether Revenue Hub can fix them. It is whether the business is ready to implement it in a way that will actually fix them.

That starts with understanding the current position.

Want to know where your commercial operation stands?
The Revenue Flow Diagnostic maps your Quote-to-Cash process, identifies where revenue is at risk and produces a prioritised scorecard you can act on – whether or not you are ready to implement Revenue Hub today. Book your diagnostic with the Heyoo team.