In usage-based billing, customer trust is everything, and one of the biggest drivers of trust is transparency into what a given customer is spending and what factors are contributing.
One of the most pronounced trends we've noticed over the past few years is that the customer dashboard is rapidly changing from a "nice to have" to a table stakes offering that every company needs to have to meet the baseline for trust their customers have come to expect.
But not all dashboards are created equal.
Customer dashboarding: from good to great
We chatted recently with an AI company that provides medical records retrieval services to legal teams. They had a basic billing system that could provide visibility into how much a customer was spending. But they had started running into customer complaints about invoices that felt unclear.
Their customers -law firms- found that the charges felt cryptic and the layout felt complicated. And the platform level charges they were receiving didn't mesh with their own system of billing by case, meaning finance and billing teams spent hours in spreadsheets reconciling charges to make sure each client was being billed for their share.
So, this company knew they needed a system that could:
- Tell a clear story across different charge types and value metrics. Credits for different actions like drafting a chronology or retrieving a record are charged differently, and customers need to understand what actions are contributing to their total charges.
- Give visibility into prepaid credits drawdowns to give both customers and account managers insight into potential overages or upsell opportunities.
- Differentiate between their own charges and pass-through fees charged by the hospitals providing the original records - this helps customers clearly understand the true cost of their services vs the baseline cost of doing business with hospitals.
- Segment charges by legal case and other non-billable dimensions to simplify their customers' internal billing. This is tricky for most billing platforms, as this information isn't directly related to how much the customer is being charged, but rather an additional piece of event data that much be made queryable by the system.
Granularity is critical, and event architecture holds the key
All of these system requirements boil down to granularity. Can the billing platform support this level of segmentation in its event data? This is a tricky challenge for most billing platforms to support.
That's because ingesting a large volume of events takes a massive infrastructure investment. And the more detail each event carries, the tougher it is.
Each event you pass to your billing system typically carries properties with it. Simple ones like date and time, but often more complex and custom ones too. Our customer from the example above passed case IDs and hospital IDs on their events to help route fees to the correct places.

Does your billing system care about the story, or just the number?
This leads to a trade off in billing systems. Preserving more of this event data gives us more richness and more visibility into what's driving spend. But it also means that we need the infrastructure resources to ingest and store all of that data.
There are two leading philosophies of how to handle this: A streaming architecture, or a raw event architecture.
A streaming architecture relies on a process called aggregation to chunk events together into tallies, making them easy to store. But in doing so, it drops many of the associated properties. A raw event architecture preserves every event and all of its properties individually.
Both can produce an invoice that accurately tells a customer how much they owe. But a raw event architecture offers customers the opportunity to see the underlying story. These event properties might not change the final amount we invoice, but they help your end customer understand how to bill their own customers or how to optimize usage across their teams.

For our customer above, that means moving beyond an account-level total to show what a case cost and where provider fees came from. The same event can carry the context needed to explain those charges by case or hospital.
From event detail to customer dashboard
For this customer, the solution was a dashboard that brought together remaining credits, usage for the billing period, overages, charges by line item, and links to invoices in Orb.
The standout view grouped cost by case, so a law firm could follow a case’s costs over time instead of seeing only one total for its account. That depends on keeping useful context—such as a case or hospital identifier—attached to usage events. If those events are reduced to one account-level number too early, the detail needed to explain costs by case is lost.
Orb’s APIs provide different views of the same billing data for different jobs. The credit balance summary shows available credits, credits pending payment, and the next expiration; the credit ledger shows how the balance changed, while credit blocks expose details such as individual expiration dates. For usage analysis, Evaluate Multiple Prices calculates selected prices over a time range using ingested events, and can group or filter results by event properties such as case or hospital. That lets a product present costs at the level its customers need without maintaining a separate copy of the pricing rules.

Orb’s usage dashboard guide explains how to choose the right endpoint for each view.
Transparency is the new customer experience standard, and the underlying data holds the key
For a usage-based company, giving your customers—and their customers—insight into how their money is being spent is critical. But transparency means more than showing a balance or invoice total. Customers need to understand what usage drove a charge, how it maps to their work, and which costs they may need to pass through.
That clarity starts with the data. When billing events retain useful context, teams can explain costs by case, hospital, line item, or time period—and build customer views around those dimensions. When that context is discarded, no dashboard can reliably bring it back.
This dashboard shows what this makes possible: a law firm can see cost in the context of a case, while the Orb customer can build on the usage and pricing data it already maintains for billing. That’s the larger point: a billing system isn’t just a place to calculate what a customer owes. The event data underneath it determines whether teams can make costs understandable and turn billing into a useful customer experience.

