The Moving Parts of a UBB Transition


Many modern software companies want to test usage-based billing, but the transition can feel risky or overwhelming. Transforming the way your business goes to market is a hard operational change to pull off and not every part of a product is ready to be metered. Hybrid pricing is the standout solution.
In a hybrid model, the bulk of your platform’s capabilities are available by paying a standard seat or license fee, and certain elements are like specific AI agents are metered. It’s a common setup for companies that are just dipping their toes into AI because it allows a specific agentic product line to capture the benefit of usage-based pricing without completely overhauling the GTM motion.
And it works. According to the 2026 Pricing AI Agents report, 95% of AI Agent products use hybrid pricing already.
The choice to pursue hybrid pricing is becoming the default starting place of the transition to usage-based pricing. But while it’s a fantastic stepping stone that mitigates much of the risk of big price changes, understanding how to go about it is still a major transition.
At Orb, we have spent years studying how modern companies price, especially as AI and usage-based models reshape monetization. Across research, customer conversations, and work on billing infrastructure, one pattern shows up repeatedly: the best first hybrid models are designed intentionally, without patching things together.
If you are moving toward hybrid pricing, start by making four decisions in order.
Every hybrid model needs a stable base layer. This is the part of the price that creates predictability for both your business and your customer. This is likely what you are already offering under a standard license, but it’s worth rethinking on a few angles:
For example, a fake company, Acme Corp, is launching their first AI agent. They know they want to charge for it as a metered capability. But how does it fit into their price model? There are two schools of thought:
Maximize availability to drive adoption: Make the agent available under every tier to get more users trying it. Excellent for PLG companies and those that need early social proof that what they’re building is correct. This is very common for first AI agent launches or for newer use cases.
Opt for exclusivity to drive incremental upsells: Making an add-on available only to customers that pay for a more advanced tier can help your account management team land upsells. It’s more common for products that are already business-critical for certain use cases, like specific integrations or data export features.

Next, the usage metric should be a reflection of both customer value and cost exposure, which is clearly defined by how measurable, understandable, and durable it is over time.
First, start by using a value metric as the unit that best represents the value a customer receives from your service. Then, measure your COGS, which are your direct costs your business incurs for that usage. The ideal usage metrics sit at an equal intersection between the two.
Returning back to the case of Acme Corp, if the team decides to meter their agent , it needs to determine specifically what customers should pay for. This could include agent runs, credits used, or other units that reflect usage. The right metric should support the adoption or expansion strategy.
Examples of services or features that might be relevant include:
A strong approach is choosing one usage metric that is significant for the customer and pressure-testing that metric with how the product's given value. With this change to pricing a usage-based service, customers now have full clarity on what drives their bills and as a business, can capture upside as usage grows without creating blind spots. Sometimes, adding small complexities to your pricing actually encourages users to see your differentiators and think of them in terms of value.

This is the step that makes hybrid pricing feel usable rather than risky. Hybrid pricing works best when customers understand where the boundaries are. Guardrails are what make a usage component feel acceptable to finance teams, GTM teams, and customers who are worried about unpredictability.
Returning to the previous example, Acme's AI agent is metered by agent runs, workflows, or credits, the right guardrails will depend on whether they are prioritizing broad adoption or an expansion motion. But, the goal is the same: reduce surprise without removing the upside of usage-based pricing.
Guardrails can take several forms:
In most cases, one or two strong mechanisms are enough to make the model feel safer without removing the upside of usage-based pricing.
The right question to ask is simple: where does this model feel riskiest to the customer, and what would reduce surprise without undermining the economics? With the right guardrails in place, customers feel protected from unpredictable costs, finance and GTM can explain the model with confidence, and it’s flexible enough to adopt.
A successful hybrid pricing model only works when a strong launch plan is established. There’s a risk of underestimating the difficulty involved when rolling out this new model. Without planning workflows like customer migration, testing, communication, and internal readiness, models can still fail.
Making rollout part of the design process from the start includes:
The first version of a pricing model is rarely the final, and teams who iterate on these can launch successfully without any internal confusion, customers understand what’s changing and why, and the company can refine the model over a period of time so they can avoid managing a messier version.
With a combination of the fixed component creating predictability, the usage layer capturing value and cost, guardrails creating trust, and the rollout plan successfully executing this change, it’s possible to define a strong hybrid pricing model.
Avoiding Common Pitfalls
A few patterns show up again and again when teams rush this process:
When beginning to think about hybrid pricing think about:

A strong hybrid pricing model gives teams and customers a clear starting point with enough structure to evolve into a successful motion.
If you’re building your first hybrid pricing model, the hardest part can be designing a model you can actually test, explain, and roll out with confidence. Orb helps teams operationalize hybrid pricing without turning every pricing change into an engineering project. Talk to Orb to see how to build, launch, and iterate on a hybrid model that fits your business.



See how AI companies are removing the friction from invoicing, billing and revenue.