Pricing is becoming more dynamic, and billing has to help teams move quickly without losing control.
Two realities sit behind that challenge. First, usage-based companies change their products, packaging, and prices often. They need to experiment and respond to the market, while still controlling when a price change takes effect and who it affects.
Second, billing needs to remain a reliable source of truth. Pricing spans teams, so companies need shared definitions, clear ownership, and a useful history of change. Pricing should be easy to understand, explain, and manage over time.
But often, these two realities can feel at odds. Rapid experimentation and frequent changes create chaos and sprawl that cause downstream billing and finance operations to suffer from tough to audit data and pricing that feels hard to grok.
Pricebook is a first step toward reconciling these two needs: define products and prices once, reuse them across plans, and keep pricing easier to understand and govern.
What is Pricebook?
Pricebook is a shared product and pricing catalog inside Orb.
It introduces a product-first way to organize pricing. Teams start with the products they offer and the prices that define them, then build plans around those shared building blocks. That more closely reflects how teams think about their pricing journey: first define what they sell, then decide how to package it for different customers and use cases. We then centralize information about how products are being priced, who is making changes and when, and where overrides are taking place.
Reducing sprawl simplifies your source of truth
As companies grow, pricing can spread across plans, spreadsheets, CRMs, and internal documents. The same price may exist in several slightly different versions. Teams then spend time figuring out which one is correct and recreating work that should only happen once.
Pricebook reduces that sprawl. A shared price means fewer copies to maintain, fewer chances for definitions to drift, and a clearer place to start when teams need to understand or update pricing.
That makes pricing easier to manage today and creates a stronger foundation for safer changes over time.
A collaborative pane of glass increases accountability
At many of the companies we work with, pricing decisions are distributed across product, finance, sales, engineering, and customer success. It's one of the biggest points of friction we tend to hear: the problem of usage-based pricing often lacks an official owner, and is instead shared across pricing committees.
That cross-functional nature can make accountability hard to trace: when a price shows up on an invoice months later, who changed it, and what was the context?
Pricebook addresses that with a feed of pricing changes and adjustments. It gives teams a running view of what changed across their catalog, when it changed, and who made the change. The idea is similar to git blame for pricing: instead of asking who remembers why a number changed, teams can connect the change to the person responsible for it and investigate the surrounding history.
That makes pricing easier to review and explain. Teams can trace an unexpected invoice back to the underlying price, understand who owns the decision, and preserve the context that would otherwise get lost across messages, spreadsheets, and meetings.
A bird’s-eye view of pricing helps inform the roadmap
Pricing does not stand still. Prices are adjusted, reused across plans, and applied across a growing set of subscriptions. As that happens, pricing strategy teams need more than a catalog—they need to see how pricing is changing as a system.
Pricebook gives teams a centralized view of pricing changes and adjustments over time. They can see how a price is used across plans and subscriptions, follow its history, and understand who made each change.
That bird’s-eye view makes it easier to spot patterns, assess the impact of pricing decisions, and keep pricing strategy connected to how pricing is actually implemented. It turns pricing from a collection of plan-level decisions into something teams can monitor, explain, and improve over time.
