Tracking Token Consumption
Product Design | 2025
As the sole product designer supporting a new business initiative, I helped align cross-functional stakeholders on an MVP of a new admin feature on a no-code developer platform.
From custom quotes to tiers. Each tier comes with tokens that apps draw down monthly.
Transitioning from bespoke pricing to usage-based billing.
Depending on the needs of an application (API calls, data storage, etc.), it would require a certain amount of “tokens” to run.
Once tokens rolled out, clients would need visibility into their application's token consumption.
One number up top: how many tokens you have for the year.
Tokens were a new way to pay, and the back end was being built alongside the design. The hard part was deciding what to leave out. I worked with engineering and dev ops to cut anything that looked precise but wasn’t reliable yet, and narrowed the dashboard to business users planning their budgets. Alerts and deeper diagnostics became fast follows.
What shipped answers two questions: am I on track, and where should I pay attention?
Every environment at a glance, with the total on top.
Usage by environment, so teams can see their own share.
Month by month, so a past launch can size the next one.
The MVP was built for one moment: someone planning next year’s budget who needs to know whether what they have will cover what’s coming. From the usage history, they can see how a past launch actually drew tokens and use that to size a new one. They can see whether there’s any room left in their allocation, and which teams are using what. What it doesn’t tell them is what more tokens would cost. That was deliberate. The dashboard gets them to the conversation with their account team, it doesn’t replace it.
In the meantime, check it out: https://career-decoder-tool.netlify.app/