The contract nobody drew up on the whiteboard
Pick a random deal in your HubSpot pipeline right now. Odds are it is not a clean monthly subscription. There is a platform fee, a per-seat line, some consumption metric that only matters once the customer is live, and an onboarding fee that sales threw in to close the quarter. That is a hybrid contract, and most finance systems treat it like three separate animals glued together.
This is the shape modern SaaS revenue actually takes. You keep the predictability of a subscription so the board has something to forecast. You let consumption scale because that is where net revenue retention really comes from. And you layer services on top because enterprise buyers want an implementation partner, not a login.
The hard part is not inventing the pricing. The hard part is operating it. One contract, three billing logics, one customer, one invoice, one CRM record. That is where most tools fall over.
Why the old split breaks down
Legacy billing was built around a single dominant model. If you sold seats, you bought a subscription engine. If you sold API calls, you bolted on a metering layer. If you sold services, you wrote manual invoices or lived in a spreadsheet. The operational cost was hidden as long as the pricing was simple.
Hybrid contracts make that cost visible on day one. The sales rep needs to quote a base fee with an included usage allowance, a per-unit overage, and a fixed onboarding line. Finance needs to recognise each component on its own schedule. Customer success needs to see real consumption against the committed allowance before the renewal conversation, not six weeks after. If those three views do not agree, someone is always reconciling.
The pricing model is no longer the product decision. The operating model is.
What hybrid actually looks like inside Plock
Plock was built on the assumption that a single contract will carry several pricing primitives at once. The platform already distinguishes between fixed licensed usage and consumption-based metered usage, and supports flat per-unit billing as well as tiered structures — graduated, volume, or bulk. A subscription is a collection of individual line items, each pointing at its own price plan. That means one Plock subscription can carry:
- A flat monthly platform fee, modelled as a licensed plan
- A per-seat component that scales with headcount from the customer's own database
- A metered line for API calls or events, priced on graduated tiers
- One-off items like implementation, onboarding or professional services, attached on the quote itself
In the product UI, this is the same object your ops team already works with. The subscription editor lets you mix fixed and metered plans on the same contract, and the quote builder handles the services layer in the same flow — without forcing it into a separate system. There is no parallel tool for "the non-subscription stuff."
Usage signals that actually reach the deal
The reason hybrid pricing feels risky is that once the contract is signed, usage-based revenue becomes invisible to the people who should care about it most. Plock closes that loop by piping real product usage into HubSpot the same way it drives invoicing. The deal stays in sync with the live subscription automatically, and a Plock order record is kept against the HubSpot company at all times. Your AE sees what the customer has actually consumed, not the quote they sent three quarters ago.
For the CS side, the same signal system that drives churn and upsell alerts works just as well against metered lines as against fixed ones. If a customer sails past 80 percent of their committed volume, that is not a surprise you want to discover on the renewal call.
Hybrid is a data problem, not a pricing problem
The reason companies stall on hybrid monetization is almost never the commercial design. It is the realisation that none of the usage numbers are trustworthy enough to put on an invoice. Finance is not going to sign off on a billing run that depends on a CSV exported from product analytics.
This is where Plock's ingestion path matters more than the pricing UI. The platform reads usage directly from the customer's product database or warehouse, processes it continuously, and uses that signal for both the invoice and the CRM. There is no shadow pipeline. The number the CFO sees on the revenue dashboard is the same number the CSM sees on the HubSpot record, and the same number that lands on the customer's invoice at the end of the period.
That single source of truth is what makes hybrid contracts operable at scale. Without it, every new pricing component adds another reconciliation job.
What this changes for commercial teams
When subscriptions, usage and services live in one contract object, a few things stop being hard:
- Quoting a mixed deal is one motion. The AE builds a quote with subscription lines, metered plans and one-off services in the same flow, with discount and approval rules applied to the bundle.
- Renewing becomes a conversation about actual consumption against the committed baseline, with the expansion signal already visible in HubSpot.
- Packaging changes no longer require a migration project. Adjusting included volumes, adding a new metered dimension or introducing a services tier is a plan change, not a replatform.
- Forecasting gets honest. Committed ARR, variable consumption and non-recurring services are separable in the numbers, because they were separable in the contract.
The European, HubSpot-native bit
There is a reason Plock has ended up on the revenue stack of so many HubSpot-centric SaaS teams in Europe. HubSpot is the system of record for the customer. Finance is the system of record for the money. Most billing tools force you to pick one and pretend the other is a downstream integration. Plock sits between them on purpose: the commercial surface lives where sales and CS already work, and the billing logic lives where finance can defend it.
Hybrid monetization does not need to be a multi-year infrastructure project. It needs a contract model that assumes mixed pricing from the first line of code, and a pipeline that keeps HubSpot and the ledger telling the same story.
If you are staring at a pricing page that is trying to be three pricing pages at once, we would rather show you than pitch you. Have a look at the charging solution, or get in touch and we will walk through a live contract shaped like yours.