Starting December 3, Atlassian’s Usage-Based Pricing (UBP) model moves from a usage report in Atlassian Administration to a line item on the invoice.
Key Takeaways
- Starting December 3, Atlassian Usage-Based Pricing (UBP) moves from a usage report in Atlassian Administration to a line item on the invoice.
- UBP doesn’t fundamentally change how organizations license Atlassian products; usage-based charges apply only when consumption exceeds the monthly allowances included with a plan.
- Usage meters fall into three categories (Activity, Stock and Outcome), and each needs a different response.
- Before turning anything off, identify which meters drive consumption, which usage ties to business outcomes, and which exists because nobody has revisited the design.
- Cprime’s Assess, Right-size and Sustain approach helps manage UBP without slowing delivery or limiting adoption.
Most conversations about UBP have focused on cost, which is understandable because nobody likes surprise charges. However, in conversations with customers, we’ve noticed a different concern emerging. While most people understand they’ll pay for overages, they’re less certain about what those overages actually mean and whether they represent a problem that needs to be addressed.
An invoice can tell you what was consumed, but it can’t explain whether that consumption helped teams work more effectively, accelerated delivery, or improved service outcomes. That’s where interpretation becomes more important than the charge itself.
How to Interpret Atlassian Usage Meters
Not all usage meters behave the same way, which is why overages need to be evaluated differently depending on what is being measured.
| Category | Examples | You pay when | The fix |
| Activity | Rovo credits, automation steps, Bitbucket build minutes | Something runs | Design and habits |
| Stock | Assets objects, Bitbucket storage | You keep it, every month | Hygiene and retention |
| Outcome | CSM AI agent resolutions | A request is resolved without a person | Quality and unit economics |
A spike in any of these categories can trigger an overage, but the appropriate response depends on what is actually being measured.
What Atlassian Usage-Based Pricing Is and Isn’t
Usage-Based Pricing doesn’t fundamentally change how organizations license Atlassian products. Most customers will continue to pay for subscriptions based on their existing plans, with usage-based charges applying only when consumption exceeds the monthly allowances included with those plans.
The bigger shift is that platform usage becomes more visible and measurable. Activities that were previously viewed as background operations, such as automation execution, AI interactions, asset growth, and build consumption, now have a direct connection to operating costs. That visibility can help organizations make better decisions, but only if the data is viewed in context.
For example, a spike in Rovo usage may indicate strong AI adoption, while increased automation consumption could point to both business growth and opportunities to simplify workflows. The objective isn’t to eliminate usage or keep every meter below its allowance at all costs. It’s to understand which activities support business outcomes and which patterns indicate inefficiencies that should be addressed. As teams, processes, and systems continue to evolve, managing usage becomes an ongoing operational responsibility rather than a one-time optimization effort.
What to Do First About Atlassian UBP Overages
The instinctive reaction to a potential overage is to start looking for things to turn off. That’s rarely the best place to start.
Before making any changes, we recommend answering three questions:
- Which meters are driving consumption?
- Which consumption is tied to business outcomes?
- Which consumption exists simply because nobody has revisited the design?
Those questions become the foundation of our Assess, Right-size, and Sustain approach.
Assess
The first step is establishing a baseline. Organizations need to understand which meters are consuming the most resources, who is driving that consumption, and whether it supports meaningful work or simply generates additional platform activity.
For larger environments, this usually requires collaboration between administrators, platform owners, and business stakeholders. The goal is to determine which usage supports business outcomes and which activities can be reduced without affecting delivery, service, or development work.
Right-size
Once consumption patterns become clear, opportunities for improvement are usually easier to identify. Development teams often find opportunities within Bitbucket where adjustments to pipeline design, build frequency, and storage practices can reduce consumption without affecting delivery outcomes. Administrators reviewing Automation Steps frequently uncover legacy rules, duplicate automations, or inefficient workflows that continue to consume resources long after their original purpose has been forgotten.
Adoption data becomes equally important at this stage because usage metrics alone don’t explain whether people are deriving meaningful value from the capabilities they’re consuming.
Through Cprime’s System of Work Accelerator, organizations can compare platform usage against adoption patterns. That makes it easier to determine whether a source of consumption reflects meaningful business value or simply ongoing platform activity, helping teams avoid cutting capabilities they genuinely rely on.
Sustain
This is usually the step organizations underestimate. While allowances reset every month, usage patterns continue to evolve as teams create new workflows, adopt AI capabilities, expand projects, and connect additional systems. Organizations that stay ahead of UBP tend to establish clear ownership of key meters, review consumption trends regularly, and provide guidance that helps administrators and users make better decisions as the environment evolves.
Ready for December 3? Prepare for Atlassian UBP
The organizations that get ahead of UBP won’t necessarily be the ones with the lowest consumption. They’ll be the ones that understand what their usage is telling them and have a plan for acting on it.
Cprime is offering a UBP Readiness Solution to help organizations understand their exposure before overages appear on invoices, identify the biggest drivers of consumption, and establish a practical plan that balances cost management with continued adoption of AI, automation, and service management capabilities.
Take Control of Atlassian Usage-Based Pricing
Understand your usage exposure, identify high-impact opportunities to optimize costs, and build a practical plan to manage Atlassian Usage-Based Pricing without slowing delivery or limiting adoption.
Frequently asked questions (FAQs)
When does Atlassian Usage-Based Pricing start appearing on invoices?
Starting December 3, Atlassian’s Usage-Based Pricing (UBP) model moves from a usage report in Atlassian Administration to a line item on the invoice.
Does UBP change how Atlassian products are licensed?
No. UBP doesn’t fundamentally change how organizations license Atlassian products. Most customers continue to pay for subscriptions based on their existing plans, with usage-based charges applying only when consumption exceeds the monthly allowances included with those plans.
What are the Atlassian usage meter categories?
There are three: Activity meters (such as Rovo credits, automation steps and Bitbucket build minutes) charge when something runs; Stock meters (such as Assets objects and Bitbucket storage) charge when you keep something every month; and Outcome meters (such as CSM AI agent resolutions) charge when a request is resolved without a person.
What should I do first if I expect an overage?
Don’t start by turning things off. First identify which meters are driving consumption, which consumption is tied to business outcomes, and which exists simply because nobody has revisited the design.
What is the Assess, Right-size and Sustain approach?
It is Cprime’s three-step approach to managing UBP: establish a baseline of consumption (Assess), reduce inefficient usage without cutting capabilities teams rely on (Right-size), and assign meter ownership and review trends regularly (Sustain).
Does an overage always mean something is wrong?
No. A spike in Rovo usage may indicate strong AI adoption, while increased automation consumption could point to business growth as well as opportunities to simplify workflows. The goal is to understand which usage supports business outcomes, not to keep every meter below its allowance at all costs.



