Revenue Reporting from Contracts

Ryan took this one first and called it the holy grail - a unified revenue view, in the platform, without a spreadsheet in the middle. The reporting package sits on the Contracts object and covers what was booked and committed, not just what was sold, plus how it moved through expansions, contractions and renewals.

One clarification the room insisted on, and it matters: detailed revenue data has been able to live in HubSpot for a while. What has been hard is reporting on it. A large project just wrapped with a unified revenue view working fine and no contracts anywhere in it. So do not read this as "you must move to contracts" - that is the one caution attached to the whole package, because not every business runs on them.

The history is the reason this lands. HubSpot built above the funnel first - marketing, engagement, demand - then deals and pipelines, then service and tickets. What never had a home was the moment after closed-won: five more seats, a cancellation, a downgrade, a renewal, an invoice that was really an email to someone in finance. That moment is what contracts solve for, and the reporting is what makes it visible.

Two honest limits. It is built SaaS-first - MRR is not a word that gets uttered in industrial manufacturing - and the coming-soon revenue events in the custom report builder and API are what will actually open this up to everyone else. And HubSpot's out-of-the-box reports have a familiar ceiling: the moment you need real customization you are back in fully-custom data model land. Until then, doing this with line items is the wrong tool. You need an orchestrator object; orders is what the room is using in the meantime.