From the November 18th, 2026, edition of How Teams Work
A signed quote gets handed to accounting, and someone notices a clause they've never seen before. Billing doesn't start until the customer goes live. How did that get in there?
Usually, the company was still finding product-market fit, and the sales team was doing whatever it took to close the deal. That's fair. But each exception creates a small discrepancy, and someone has to work around it by hand.
Then someone has to take what the quote says, fit it into the subscription management tool, and get it to match the CRM. That's where the numbers start to drift.
My co-founder Andrew likes to break this down by dates. There's the date the deal was booked, the date the contract starts, the date the subscription actually goes live, the date it's invoiced, and the date it's paid. Sales cares about the booked date. Customer success is trying to get the customer live. Finance cares about when they can invoice, collect cash, and recognize revenue.
Those dates can be months apart. That's the clause from the open. A deal might close today, but if implementation takes a few months, the subscription won't start billing until the customer goes live.
So even when your systems are connected, the numbers won't always match. Part of that is by design. Your CRM is built to track booked revenue. Your finance tools are built to track billed revenue and follow your revenue recognition rules. They're measuring different things at different times.
And the initial sale isn't the hard part. The changes after that sale are. A customer adds seats halfway through their contract. Do they pay the difference now or at renewal? Do they renew at the new price? If they paid annually and then downgrade, is that a credit or a refund?
The tools usually break right here. Proposals start in slides or a spreadsheet, and every rep has their own version. Accounting sets up recurring invoices in Xero or QuickBooks. Stripe works until customers start changing plans mid-contract. Then the team buys a subscription tool, but it isn't connected to the CRM, so someone has to rekey the deals.
The rest of the drift tends to come from a few places:
What changed in HubSpot
For a long time, HubSpot wasn't built for any of this.
The subscription object worked if every product was recurring and billed on the same schedule. If you needed to sell onboarding or training alongside the software, you would run into problems.
Deals were the other option, but deals are designed to capture a single moment: when something closes. Every upgrade or downgrade meant overwriting the original deal, which made ARR and MRR reporting hard to trust.
Teams that used a separate billing platform had to create a place in HubSpot for that data to live, usually a separate deal pipeline or a custom object. It worked, but nothing in HubSpot was built for it.
That changed in June, when HubSpot launched Revenue Hub (formerly Commerce Hub). It builds on Cacheflow, a CPQ and billing company HubSpot bought in 2024, combined with the quotes, payments, and subscriptions HubSpot already had.
At the center of Revenue Hub is the contract object. Unlike a deal, a contract is designed to change over time. When a customer upgrades, downgrades, or renews, the contract is updated, and an order records each change, so you keep the full history. Each line item has its own start date, and one contract can hold one-time services next to subscriptions billed monthly, quarterly, or annually. That go-live start date finally has a place to live.
When a customer accepts a quote, the contract is created automatically, and the billing schedule shows right on the contract. Nobody has to rebuild the quote in a separate billing tool.
Because the contract keeps a record of every change, HubSpot's revenue reports can show how your MRR moved and why. Booked MRR is reported separately from MRR that's in effect. That's two of Andrew's dates, finally in separate columns. Changes break out into new, expansion, contraction, and churn. You can also compare billed revenue against actual revenue each month.
Orders also feed a new attribution report, so you can see which marketing efforts contributed to booked revenue. That's still in beta, but it means the full lead-to-cash journey is now visible in HubSpot, not just the lead-to-deal flow.
Quoting matters here too. Quote rules can require or block certain products from being sold together, and approvals let finance review a quote before it goes out. If your quotes aren't accurate, your contracts won't be either.
Where Revenue Hub fits, and where it doesn't
Revenue Hub was built with software and services companies in mind. That includes B2B software subscriptions without complex configurations, and services sold as retainers or blocks of hours.
It's a strong fit if you're setting up subscription management for the first time. Your contracts and billing live alongside your sales process, and you can still connect to your finance tools.
Plenty of billing platforms handle part of the process well, whether that's quoting, contract changes, billing, or revenue reporting. What's different with Revenue Hub is that every piece connects to the same CRM data.
But there are still a few areas Revenue Hub doesn't handle well yet:
It also doesn't have to be all or nothing. Some companies run quoting or invoicing in another system and bring that data back into HubSpot. One client we work with invoices in seven currencies from NetSuite, because NetSuite handles everything they need for revenue recognition. They just want their reps to see the invoices. So those invoices mirror back into HubSpot, and every team can see what was billed and whether it's been paid.
Whether it fits is the easier question, though.
There's a project before the project.
Something we see often: a company's subscription numbers stop adding up, so they buy a new billing platform before defining their sales process and how they'll handle renewals and amendments.
That order backfires. We've talked with companies that bought a subscription platform and never got it live. Tens of thousands of dollars in software, plus time and services, and they were still on the old process.
In one case, the team couldn't decide how they wanted to package what they sold. So they wanted every option to stay available. The same plan could be evergreen or fixed-term, depending on the deal. The software wasn't built for that.
The gap is usually the product library and the rules around it. What can be sold, how it's packaged, and when customers can upgrade, downgrade, or cancel. Ask where those rules live, and the answer is often inside someone's head and a spreadsheet. Quote rules in Revenue Hub can block a bad quote, but only after someone decides what a bad quote is.
Underneath that is a disagreement between sales and finance. Sales wants flexibility to close deals. Finance needs rules everyone works within, because more flexibility means more complexity on their side. Until the two agree, it's very hard to get the product library and renewal rules to a place you can build on. Everybody's working toward revenue, so both sides need to come in with an open mind.
Company size matters less than you'd think. You might assume the smaller the company, the simpler the project. That's not always the case. One of our solutions architects is working with a large, mature company right now, and the project has been straightforward because they had already agreed on what they sell and the rules around it.
It's not only a sales and finance project, either. Marketing helps shape packaging and terms. Legal weighs in on what you can and can't offer. Product keeps shipping features that have to fit into what you sell. Customer success handles the result. If a customer was told they could downgrade and the rules say otherwise, support and sales both end up pulled back in.
Whether you land on HubSpot or another platform, start with the rules, not the software. When can customers upgrade or downgrade? Can they cancel? Are subscriptions evergreen or termed? Do you charge by seat, by usage, or by product? Some platforms only handle evergreen subscriptions, and Revenue Hub doesn't handle usage-based billing yet, so these answers decide which tools are even on the table.
It also looks different depending on how you sell. A self-serve product where customers change plans on their own needs a very different setup than a contract-driven business where account managers send custom quotes.
Then cut the list down. This is where leadership has to make the call. Say five of your processes drive 90% of your revenue. Can you consolidate the rest? If your head of sales is focused on hitting this quarter's number, the answer is often no, and the project gets bigger. Build for where the business will be in two or three years, not next quarter.
Sometimes the right answer is still more than one system. We're working with a client right now whose first implementation failed a couple of years ago with a different partner. This time, they're taking it slower to make sure they get it right. They have 14 distinct processes across multiple legal entities, so we audited eight to ten different platforms against their requirements. They'll likely end up with four connected systems, and for their business, that's the right setup.
Once the rules are set, the build tends to follow the same order:
If your products and pricing are a mess, everything built on top of them will be too.
Moving existing contracts over is the riskiest step. It's your best chance to clean up data and your easiest way to lose a customer's trust. Nobody likes getting billed twice or wondering why a charge looks different, and missing charges entirely is just as bad. Migration doesn't stop billing in your old system, either. Someone has to turn it off. In Revenue Hub, migrated contracts come in as drafts you review before anything goes live (migration is still in beta), and if you're already on Stripe, customers' payment details can carry over. Switching payment processors can mean asking every customer to re-enter their payment information.
And count the costs that never show up on a vendor invoice. Data cleanup takes real internal time, and only your team knows the edge cases. Saving a few thousand dollars on software can cost far more than that internally.
The most costly mistake we see is picking software first and working out requirements second.
So write down your requirements. Know which ones are non-negotiable and where you're willing to simplify, because no system will match your current process exactly, and forcing it to is where the cost climbs.
Then look at tools. If you sell software or services, Revenue Hub can now hold those changes in your CRM. Just make sure your rules are ready first.
What's the last exception that surprised your finance team? I'd genuinely love to know.
If you're trying to figure out where your subscription revenue should live, I'm happy to talk it through.
Want to get the "How Teams Work" newsletter sent to your inbox? Subscribe Now.