Hubsessed Office Hours Recap: HubSpot Super Admin, October 9, 2026

An attendee brought one question to this session, and it carried most of it: how do contracts work together with orders and deals in HubSpot? George B. Thomas and Chris Carolan talked through the four revenue buckets, built a contract live, asked when a business needs contracts at all, and finished on Breeze. This is the written recap of the session.

Get the language right first

George opened by asking Chris whether he had dived into contracts yet. Chris knows them in theory, and he started with words, because "finding this language" is so important. Booked revenue is closed won, or an order. Billed is invoiced. Collected is paid. Those three are covered on the contract object, as dates stamped on line items associated with contracts and orders.

Earned is the hard one. Chris ties it to the deliverables object: once the people who own that process can say it shipped on this date, the earned date can be stamped on a line item. He talked to the HubSpot product manager, and "they are trying to figure out earn date specifically right now." What he asked for was just the property. For now, the closest option is associating contracts, orders and projects. His rule for whatever process you use: it should stamp the date "in a way that somebody's not typing in earned dates." Watch Stamp the earned date, don't type it.

Does your business need contracts?

George had asked his own agent how contracts would work at Sidekick Strategies. Its answer: the way they bill, they don't need them. So he put the question back to the attendee. One organization can have revenue coming from several places, so how complex is the invoicing, billing and quoting with customers, and how much historical data comes in with new customers?

Building a contract live

Chris built one on screen, billed to George's company: a fix per month, so twelve one-time line items, plus an ongoing advisory line at a monthly rate for twelve months.

He made a point for anyone watching without a Revenue Hub seat: "The contracts object comes with the CRM, right? Does not require a Revenue Hub seat just to be able to put data on a saved contract record." Without the seat you don't get this interface, so line items and orders have to get there another way, and UI extensions open a way to do it. Watch Contracts come with the CRM.

The saved record showed the start and end, total and annual contract value, the billing schedule, current and upcoming line items, an order and a subscription. Nothing connected the orders automatically. In Chris's own builds, a deal moving to closed won creates the orders and deliverables. The architecture, in his words, "is understanding that line items have the reporting data on them, especially dates related to these four buckets," and the contract "is the umbrella object" where you go to see where you stand with a customer. Watch Contracts is the umbrella object.

The hardest part is teaching a new object. People still decide term length, how often, and how many times price gets negotiated, so they need the interface. Otherwise that work stays in a spreadsheet.

Contracts are not for everybody

George put it plainly: "I don't know if contracts are for everybody, but when you immediately see that it's right for you, you know it's right for you." He wondered whether a contract is a better home for documents than a deal, such as twelve monthly quotes in one place, and said another object "means two things. Maximum flexibility and also maybe a little bit of complexity that you have to figure out along the way." Watch Another object means two things.

His team keeps month-to-month partnerships "dumb simple." Deals sit in three columns each month (holding, sent and closed), with invoices, and a quote only the first time. They put deals in place two or three months ahead to forecast, and delete one if a client changes hours, since no invoice exists yet.

Chris answered that a lot of reps would not want to delete deals. Contracts start to matter "once you need to know payment status and fulfillment status of the thing," especially when one-time and ongoing work are owned by different teams. Change orders go through an updated quote, and "that audit trail allows for the reporting that people want that doesn't mess with the original promise," so MRR and ARR show what they should. Watch When contracts come into play. George added project work with split payments: a kickoff invoice, one at 50 percent done and a final one, all visible on one contract.

Three deliverables, one earn date

Chris went back to why the deliverable object came about: a $150,000 installation you can't invoice until it is installed, everybody is trained and the warranty is checked off. Put one deliverable or project record each on training, installation and warranty activation, often owned by three different people, and when each one closes, the earn date lands on the line item "and now everybody knows." The contract object handles all of that, but not on its own. "Deals feel simpler until you try to force all that complexity into them." Watch Three deliverables, one earn date.

His advice for anyone explaining this: "don't ask AI about whether or not you should do this in HubSpot. It's not going to tell you the truth." Ask instead whether the process is documented for each revenue stream, because the person who owns each process has to be on board. Watch Don't ask AI whether you need it.

As Chris said, "Data model questions every single Hubsessed Office Hour so far. Doesn't matter the topic."

Breeze for super admins

We closed on a follow-up to last week's conversation. Chris opened a page of Breeze prompts sorted by seat, picked admin, spun the wheel and landed on companies, Data Studio and "spot the risk before it costs us." He doesn't have Data Studio, and starting from a tool you don't have puts AI in a bad spot, but Breeze could still read the company data. Its first risk was trusting outdated risk signals, which Chris traced to context his own agents had added that doesn't update like the rest of the CRM. His advice: "just start talking to Breeze if you're a super admin. Please, please just ask your questions," and "Don't follow all of the directions without asking questions back." Watch If you're a super admin, just ask Breeze.

Asked about a Breezy super admin guide, George said, "I don't think it's a guide. All right. I think it's a tool." He pictures a Breeze translator: answer a few questions, then get the right Breeze prompt for your portal. Watch Not a guide, a tool: a Breeze translator. And when you ask AI about your portal, "buckle up because it might tell you some stuff that you don't want to hear," then ask it what you've been doing wrong. Watch Buckle up, then ask what you've been doing wrong.