Hubsessed Office Hours Recap: Unified Revenue View, October 8, 2026

In week two of Office Hours for Unified Revenue View, we stayed with the earned bucket of booked, billed, earned and paid. Ryan Ginsberg and Chris Carolan started from one post-sale email and worked outward: what the person who answers it needs to see, why a unified customer view comes first, and why HubSpot can be the context layer for every team. This is the written recap of the session. You can watch the replay on the session page.

Booked, billed, earned and paid, one more time

Chris opened by naming the four buckets again: "I figure if I say it enough, it's just gonna sink in what these buckets are. Booked, billed, earned, and paid revenue." He added that since last week he has heard lots of different words used for those four. He also flagged the earn date: "…thinking hard about the earn date, right? It's the one thing that contracts doesn't come equipped with out of the box right now."

One email, three months after the sale

Ryan brought a scenario he worked out on a walk. "Okay, so, post-sale, your customer is three months into a relationship and they either call you or they email you with a question, with a need, with a problem." In a company of 50 people, nobody knows in advance who will get that email, at what time of day or on what shift. So what does that person need to know to help?

Ryan listed what he has seen in the portals he has been into. Is the contact connected to the right company? Is the company connected to the deal? Does the deal use line items? Is there a pile of documents to dig through, another tool, emails somewhere else, an account manager to ping for context? He put the test this way: "…all of those little connection points of how did this customer become a customer and what are they paying for and am I enabled in that moment to provide value?"

Agents help when the data can be trusted

Ryan saw a LinkedIn post that day about nine post-sale agents someone had built. His take: "…all of these are great if your data is trustworthy and if the agent can access what it needs to do." He added a second test, which is cost. The steps and tokens behind an answer you can rely on could cost $10, he said, depending on the model. "…you can't just throw AI and say, go do AI stuff."

The model is the Amazon buying experience

Ryan asked Chris what he recommends when someone cannot see what they need to see in the moment. Chris said that today they call anybody and everybody else internally, or they log into all the different systems. His answer to where to start: "…if you could just stop overthinking it, the Amazon buying experience, go do that."

He spelled out what that experience gives you: where things are in the process, what happened, the invoice, when it shipped, the tracking number, even a picture of the front door. Then comes the part that matters for service: "And I know that I don't need to go look at my email, I don't need to call Amazon, but if I do, it's super easy for them to help." Chris added, "…if you truly want Unified Revenue View, this is what you need to solve for."

Earned means we did something for them

Today's focus was the earn spot, which Chris tied to the internal customer: the order manager, the customer service person, the customer success person, even accounting. As he put it, "…earned means we did something for them, and that's what they care about, obviously. What did we do for them lately, right? What's in it for me?"

HubSpot has made billable milestones easy, Chris said, but the work behind them lives somewhere else: "But most of those payments relate to earned, which are not touching that system, often owned by a completely different team that may not interact with the other team, probably doesn't interact directly with the customer often, right?" And handoffs between those teams are where it breaks. "We know handoffs is one of the worst things in most businesses that equals a poor experience because people can't see what they need to see to take the handoff." In most businesses, what fills that gap is an hour-long meeting just to share context.

Three processes, three owners, one earn date

Chris told a story from his last in-house role. One of their biggest customers needed an hour-long call each week with a project manager on the client side, because on a project that lasts two years, where things ship changes depending on when they ship. The team was just starting a spreadsheet of all of that customer's projects, around 20 line items and four shipments over two years, with supply chain mixed in. They could not fill it out from the ERP's data.

Ryan asked why not. Chris said the person in charge of supply chain was not putting that information anywhere. Vendor communication does not go in the CRM, where sales is supposed to be, and it does not go in the ERP, where operations and invoicing come from. The only way it reached the ERP was if somebody downloaded an email and attached the file, which does not make it any more accessible. That person owned pricing management with vendors and suppliers. If a battery shipment is due and the supplier changes the date, the earn date changes too, because the team cannot deliver on the promise. "And there's like three processes in one there owned by three different people that make the earn date true or false."

Usually the real communication happens on the weekly call, Chris said, and hopefully the data gets updated afterward. He noted that even now those transcripts could be used to get the system updated, but people have been doing it the old way for so long that they are probably not going to ask the system. He put the permission side plainly: "I've had to give people permission to put human relationships into HubSpot that are not sales." And the data model does not stretch to cover it. "This doesn't all fit on a deal. You don't want it to be, sales usually wants to know the information, but they're not responsible for it."

Processes nobody designed

Chris asked Ryan, from his customer success background, whether SaaS built a lot of siloed systems that let people avoid working inside one system together, so all the real communication happens outside of it. Ryan said that in the normal businesses he has worked in, no process was ever designed on purpose for any system. People got thrown into a role and did what they could to keep the wheels on the bus. That was fine before AI, he said, but "…now we can curate and design the process that we need on top of an infrastructure that's shared across the whole business."

Do you know who your customers are?

The playbook's prerequisites checklist starts with a question, and Chris read it out: "Do you have a unified customer view? If you don't have that, it's very hard to get to the unified revenue view because we don't know what's going on with the customer in all aspects."

Ryan paused him to share a call from a few weeks back. He had asked a company about its tech stack, then whether they know who their customers are. One person said yes, they are in this system. The person on the customer success side said no, the customers are here and they are updated over there. Ryan's read: "I'm like, okay, so no, we don't know who our customers are." He added that a list of closed won deals or an accounting system still does not tell you who is current, such as who is logging in and who has stopped paying.

Built around the contact record

Chris said he always came at this from the marketing side, before he had any RevOps language, and explained why HubSpot fits: "…HubSpot is built around the contact record, right?" An ERP is different. "Guess what that [ERP] customer record never is, a human. It is a company." Then there are orders, and you end up pushing contact information onto objects that are not people, because you still need to communicate with the people.

Document what exists before you configure what is new

Chris said business-to-business buyers do not ask for this experience for a simple reason: "B2B doesn't ask for an Amazon-like buying experience, not because they don't love it, but because they're not used to it. They don't know what's possible, right?" The closest thing they know is a vendor portal, he said, and everybody hates those. Still, "…everybody wants a unified revenue view. Every single company, every single leadership team, they've never been able to get it like this before."

The checklist that follows is about documenting your existing processes before configuring new capabilities. Chris walked it: deal pipeline stages, the quote and proposal process, the product catalog and pricing models, approval workflow requirements, order fulfillment, the invoice and payment process, and how recurring revenue is tracked. If you are lucky, he said, deal pipeline stages is the only one most HubSpot customers have documented. The rest sit with different hats in the org, from sales and product management to customer success, service and accounting. "So seven different checkboxes that touch different hats of the org. They all might have some documentation somewhere." Then the catch: "But none of it speaks to each other, so they all have different language and it makes it very, very hard to bring it all together to unify a view."

Can HubSpot support all of that?

Ryan asked how many people think HubSpot can support all that. Chris: "If AI's any indicator, not many, because AI doesn't think it, right?" Ryan said it can, with the native objects, and offered this as the message he wants out in the world: "…HubSpot has become the business operations and the context layer for all teams in that list to be successful without needing to go elsewhere and without overcomplicating." He added, "There's a road. That road is a lot shorter than it was three years ago, right?"

Chris closed on why. "It's because it's built around a contact record and it's better at managing communication in all of its forms and channels than any other system, ever, because it was built to do that first." And then: "Doesn't mean replacing every other system, but we can unify it over in HubSpot very successfully."

Next session

This session ran 30 minutes. From here on, Office Hours run an hour. Our next Unified Revenue View session is Thursday, October 15, 11:00 AM Central, and October sessions are open to subscribers. Join us in the room or see everything on the Unified Revenue View lane page.

Send your questions to community@hubsessed.io.