Revenue Hub · which businesses it fits
Which businesses Revenue Hub fits, and what their product library looks like
Most pages about Revenue Hub tell you what it can do. This one is about whether it fits the business in front of you, and what the product library has to look like if it does. Three shapes it carries today, built out row by row — and an honest list of the businesses it cannot carry yet.
One question decides it
“change quotes can only update recurring line items, not one-time line items.”
Read what that does to a catalog. Everything recurring stays alive after signature — repriceable, expandable, renewable, with the platform handling proration and minting an order for the change. Everything one-time freezes at signature, and changing it means a new quote and a separate motion somebody has to own.
So the test for any business is: after the customer signs, what changes? If the answer is mostly recurring — seats, sites, machines under cover — it fits, and it is one of the three shapes below. If the answer is mostly one-time — change orders, milestones, deposits, progress claims, retention — it does not fit yet.
Which is why the businesses where complex quoting is most unavoidable are the ones Revenue Hub is least able to hold right now. That is worth saying to somebody before they buy, not after.
Three shapes it holds today
Out of thirty-eight segments scored on whether the complexity is unavoidable and whether Revenue Hub can carry it now, three came back as leads. Two of the three share a shape, so this is two shapes and three skins rather than three unrelated builds.
How to read a catalog
- Product
- The name as the person in accounts payable will read it eleven months from now, not as the picker sorts it. That name is copied onto the quote, then the invoice, then keyed into the customer’s own accounting system.
- Class
- Standalone, variant, or bundle. A catalog of nothing but standalone rows is expressing variants and bundles as separate products, which is where a library of five hundred comes from.
- Type
- Inventory, non-inventory, or service. This is what routes the notification after the sale — an inventory line tells a warehouse, a service line tells a delivery owner.
- Pricing
- Flat, volume, graduated, or stair-step. Volume reprices every unit at the band the total reached; graduated prices each unit inside its own band and sums; stair-step is one flat fee for the band you land in.
- Rhythm
- Billing frequency and term, which are two questions people answer as one. Monthly on a twelve-month term, annually on a twelve-month term, and monthly with no term are three different agreements.
- Quantity carries
- What the number means. If a row here would read "always 1", the model is wrong — the count has been written into the product name, where nothing downstream can read it.
The rule under all three
If a product name contains a count, the row is wrong. Quantity is a number the whole chain reads — operations provisions it, finance reports on it, and a customer growing from eighteen to twenty-two is a quantity change rather than a different product. A count inside a name is a string only a human can parse, and operations gets 1 on every line.
Sales-led B2B SaaS
50 to 1,000 employees. Seats, tiers, an annual or multi-year term, and expansion that has to land co-termed with the original agreement.
This is the shape the contract object was built for, and it shows. The customer buys seats on a term, adds more halfway through, and the addition has to end when the original does — which is the one motion the platform does natively and does well.
It is also the most crowded field. Every partner has a launch guide for it. What almost nobody works on is the installed base: the migration of agreements that already exist, the amendments, the renewals. That is where the work actually is.
Show the catalog — 9 rowsHide the catalog
| Product | Class | Type | Pricing | Rhythm | Quantity carries |
|---|---|---|---|---|---|
| Platform — Professional, per user | standalone | service | graduated | annually · 12 months | users |
| Platform — Enterprise, per user | standalone | service | graduated | annually · 12 months | users |
| Platform — Professional, per user, 3-year | variant | service | graduated | annually · 36 months | users |
| Onboarding and implementation | standalone | service | flat | one-time | engagements |
| Data migration | standalone | service | flat | one-time | engagements |
| Premium support | standalone | service | flat | annually · 12 months | one per account |
| Additional sandbox environment | standalone | service | flat | annually · 12 months | environments |
| API call allowance, per 100k per month | standalone | service | graduated | annually · 12 months | 100k blocks |
| Training — administrator, per seat | standalone | service | volume | one-time | attendees |
A design, not an export. Nobody’s real catalog is on this page.
Six things this catalog decides
- One seat product, priced by band
- Never a product per seat count. Graduated prices each user inside its own tier and sums them; volume reprices every user at the band the total reached. Pick on how the business actually discounts, and say which out loud — customers crossing a threshold notice.
- Term is a variant, not a text field on the deal
- The three-year row is the same product classified as a variant with a different term. The term is then a property of the thing sold, which the billing schedule reads, rather than a note that will disagree with the line item inside a quarter.
- A ramp is not a tier, and it is not a product
- Year one low with step-ups in years two and three is configured on the quote when the line is added. Nothing in the catalog expresses it. A business that models ramps as products ends up with a five-hundred-row library in a different costume.
- The one-time rows are the trap, and they are here on purpose
- Onboarding, migration and training are one-time, so they cannot be added by a change quote later. Mid-term services are a separate quote. Model them now, name the limit in the same breath, and design that motion before go-live rather than after the first customer asks for it.
- The API allowance is a commitment, not metering
- There is no rating and no credit balance anywhere in the platform. That row sells a committed block annually. A real overage is a manual true-up, or it is a different system — say which, early.
- Unit cost on the service rows, or margin is fiction
- Implementation and training have a real cost; the platform rows may not. Populate what is true and leave the rest empty. An empty column is honest; a guessed one propagates into every margin rollup on the line item.
What works natively
Adding seats mid-term. The seat row is recurring, so a change quote updates it, proration is a per-change choice, the platform mints an order carrying the delta, and the renewal quote generates the successor contract. This is the single motion Revenue Hub does best.
What does not
A one-time services line added after signature. A discount expressed in dollars on a contract line — percentage only, so somebody converts every time. Usage-based anything.
Industrial equipment makers with service and parts
A machine sold once, then a multi-year service agreement per asset, parts on a replenishment rhythm, and often a dealer channel that prices differently from direct.
The machine is one-time and the service agreement is the annuity, and the annuity is the part that fits. Coverage grows as the customer buys more machines, renews with an uplift, and the contract holds both the money and the record of what is installed.
Nobody has published a Revenue Hub case in this industry. The analysts do not have HubSpot in the CPQ conversation at all, and the buyers who need heavy configuration go past native CPQ to an app — which leaves the contract layer behind it unowned.
Show the catalog — 10 rowsHide the catalog
| Product | Class | Type | Pricing | Rhythm | Quantity carries |
|---|---|---|---|---|---|
| Machine — Model K, base unit | standalone | inventory | flat | one-time | units |
| Machine — Model K, high-capacity | variant | inventory | flat | one-time | units |
| Option — extended hopper | standalone | inventory | flat | one-time | units |
| Option — remote telemetry module | standalone | inventory | flat | one-time | units |
| Model K with telemetry and install | bundle, closed | inventory | fixed bundle price | one-time | packages |
| Installation and commissioning | standalone | service | flat | one-time | machines |
| Preventive maintenance — per machine | standalone | service | flat | annually · 36 months | machines under contract |
| Extended warranty, years 2–3, per machine | standalone | service | flat | annually · 24 months | machines covered |
| Wear parts replenishment, per kit | standalone | inventory | volume | quarterly · 12 months | kits per delivery |
| Priority parts availability | standalone | service | flat | annually · 12 months | one per account |
A design, not an export. Nobody’s real catalog is on this page.
Six things this catalog decides
- A closed bundle at a fixed price is a governance choice, not a technical one
- Closed means a rep cannot alter the components, which is right for a machine configuration that has to be buildable. But a fixed bundle price stops component price changes reaching the bundle, so margin drifts quietly. Pricing calculated from components keeps it honest and lets the rep see the arithmetic. Pick deliberately, and re-check the bundle whenever a component reprices.
- Product type is what makes the handoff after the sale routable
- The machine and the options notify a warehouse; the maintenance agreement notifies a service planner. If every row in the catalog is one type, the post-sale handoff runs on a human reading a PDF, which is where most of these businesses are today.
- Maintenance is per machine, and the quantity is the installed base
- This is the whole reason the shape fits. Growing from four covered machines to six is a quantity change on a recurring line, which is a change quote, which works. Model coverage as a count and expansion is native; model it as "maintenance, four machines" and expansion is a rebuild.
- Dealer pricing is a price book, not a fork of the catalog
- Price books are per-currency and per-segment, and they are assigned per deal rather than per company. So the dealer discount is a book selection plus an approval rule, and nothing in the catalog duplicates. Two things to know first: price books carry no tiered volume pricing, and they cannot be imported, cloned, or used in workflows.
- Wear parts is the row that earns tiered pricing
- Kits ship in quantity, the discount is genuinely bulk, and volume pricing — one unit price across all units, set by the total — is the model that matches how the business already talks about it.
- Warranty years two and three is a term product with a delayed start
- The line item carries billing start delay in days or months natively. Use it, rather than a workflow that creates the line later — a workflow that runs late produces an invoice nobody expected.
What works natively
The service annuity in full. Coverage changes, the renewal quote with an uplift, proration on a mid-year addition, and one contract holding both the recurring maintenance and the record of what was installed.
What does not
The machine itself. A one-time equipment line cannot be change-quoted, so a specification change after signature is a new quote. CPQ quotes carry no payment schedules, so a deposit-and-progress structure on a capital sale is not on that path at all. Pay-per-use or outcome pricing is usage billing, which is claimed nowhere.
Fire, security and HVAC service contractors
An install that is one-time and messy, then a monitoring or planned-maintenance annuity per site that grows as the customer adds buildings and renews with an uplift.
Adding a site is the motion these businesses do constantly, and almost all of them do it in a spreadsheet. It is a quantity change on a recurring line, which means the platform handles it natively, prorates it, and mints the order — and that one motion is most of why this industry is on the list.
The install is the other half and it is where the limits bite. Three partner practices run on HubSpot in this space and none has touched Revenue Hub, so there is no published case to point at either way.
Show the catalog — 10 rowsHide the catalog
| Product | Class | Type | Pricing | Rhythm | Quantity carries |
|---|---|---|---|---|---|
| System design and survey | standalone | service | flat | one-time | surveys |
| Control panel — addressable, 4-loop | standalone | inventory | flat | one-time | panels |
| Detection device, supplied and fitted | standalone | inventory | volume | one-time | devices |
| Installation labour, per engineer day | standalone | service | flat | one-time | days |
| Commissioning and certification | standalone | service | flat | one-time | systems |
| Monitoring — per site | standalone | service | flat | monthly · 36 months | sites monitored |
| Planned maintenance visits — per system, per year | standalone | service | flat | annually · 36 months | systems covered |
| Out-of-hours response cover | standalone | service | flat | annually · 36 months | sites covered |
| Reactive callout, per visit | standalone | service | flat | one-time | visits |
| Spares and consumables, per kit | standalone | inventory | volume | one-time | kits |
A design, not an export. Nobody’s real catalog is on this page.
Six things this catalog decides
- Devices are one product with a quantity, always
- This is where the device-count catalog gets built, because a quote for eighteen detectors feels like a thing being sold. It is one product, quantity eighteen. Get it wrong and operations provisions one, nobody can state average devices per site, and a customer growing from eighteen to twenty-two is a different product rather than a quantity change.
- Monitoring is per site and maintenance is per system, and those are not the same count
- One site can hold three systems. Two rows, two quantities, and two things the customer will query on an invoice — which is a good reason to get the names right before the first one goes out.
- Adding a site is the motion that works
- A quantity change on a recurring line is a change quote. The platform mints the order and prorates it. For most of these businesses this is the first time the thing they do every week is a native motion rather than a spreadsheet and a memory.
- The install is one-time, and the install is where variations live
- Extra devices, an extra floor, a rerouted cable — a variation mid-project is a one-time change, and one-time lines cannot be change-quoted. So the install is quoted and every variation is another quote, and somebody has to own that motion. This is the most consequential fact for this industry, and it is a thing to design before you build rather than a reason to walk away.
- Indexation has no native mechanism
- A contract with an annual CPI or RPI uplift is a renewal quote somebody raises with a new price, which means somebody has to know the index and the date. Model the uplift as a renewal step, put the date where a human will see it, and be honest that nothing is calculating it.
- Reactive callouts sit beside the contract, not on it
- They are one-time rows against a customer who has an agreement. Keeping them separate is what lets the business see planned-maintenance revenue and reactive revenue as two numbers — which is usually the number they are trying to get and currently cannot.
What works natively
The annuity. Sites added and removed, the annual renewal, one record holding what is covered and until when, and — for the first time in most of these businesses — a renewal date that is a field rather than a calendar reminder.
What does not
Install change orders. Indexation. Metered monitoring, where the charge is per signal or per event. Retention held back on an install, which is a payment-schedule shape CPQ quotes do not carry.
What it cannot hold yet
These have the need — often more sharply than the three above — and the platform cannot carry the money today. Each one re-scores when something specific ships, so the honest answer is a trigger rather than a maybe.
| Business | What blocks it | Re-score when |
|---|---|---|
| Project subcontractors — mechanical, electrical, fit-out | Change orders, progress billing and retention: the exact three gaps | Milestone billing generally available, plus one-time change quotes |
| Consulting and professional services on statements of work | One-time change orders, milestone billing, no time tracking anywhere in the platform | Milestone billing, or a contract-plus-time-app architecture with the gap designed around |
| Usage and hybrid SaaS, AI credit vendors | No rating, no credit balances, no true-ups | Usage billing ships |
| Wholesale distribution and B2B commerce | Price books are per deal rather than per customer; no volume tiers on a book, no rebates or surcharges; the goods are one-time | Customer-scoped price books with volume tiers |
| Engineered-to-order machinery | No rules engine, milestone payments, percentage-of-completion recognition | Not natively — a specialist configurator plus a HubSpot contract layer |
| Facilities management | Call-offs against a schedule of rates are usage; service-level credits have no shape | Usage billing |
| Contract research and lab services | Milestone, unit and pass-through pricing on one study | Milestone and usage billing together |
| Telecom, UCaaS and CCaaS | Taxes and fees on quotes, non-recurring-charge changes, call-record rating | Fees and taxes on CPQ quotes, plus usage |
Where to next
Run the nine questions
Free, five minutes, on your own portal. Nothing captured, nobody emailed.
Decide before you configure
The seven decisions that get signed before anyone touches a setting.
The same three catalogs, from the builder’s side
Ryan’s own write-up: why each row is shaped the way it is, and what he reads before designing one.
Where this comes from
- Thirty-eight segments scored, 2026-09-04. Each on whether the complexity is unavoidable, whether Revenue Hub can hold it today, how dense the segment is on HubSpot, and what demand evidence exists.
- The product schema, read live 2026-09-05. Every class, type, pricing model and billing frequency named here came back from a real portal on the day, not from a feature page.
- A production migration of about four hundred agreements, August 2026. Anonymised. The source of the catalog decisions each section walks through.
What we do not know yet
- Product bundles were in private beta as of April 2026, with visual grouping and rollup pricing still in development. The properties are in the schema; whether the feature is on in a given portal is a portal question.
- Milestone billing is marketed on the Revenue Hub product page and documented nowhere. A switch for it exists on the line item object. That is a schema hook, not a shipped feature.
- Licensing moves. Every seat and tier statement here was true on the day it was read, and has to be checked against live pricing when you scope.
Building one of these, or working out whether yours is on the list?
Come walk it through on the show and we will work it out on air, weekday mornings.