Why you pay for 100 Jira users when 10 use the app

Your QA team has ten people. They need a test management app inside Jira, so you install one. Then the invoice arrives, and it isn't for ten people. It's for every user on your Jira site: developers, designers, product managers, the support team, and the contractor who logged in once last spring.

This isn't a vendor being greedy, and it isn't a billing mistake. It's how paid apps on Jira Cloud are licensed. Most teams only discover the rule at renewal time, when the app line on the invoice is suddenly as large as Jira itself.

This article explains how the rule works, what it costs in practice, and what you can do about it.

How Jira Cloud apps are billed

Paid apps from the Atlassian Marketplace are licensed per user, per month (or per year on annual billing). The key detail is which users.

For Jira Cloud, the billing base is the highest number of users across all Jira products on your site. If your site has 100 Jira users and 80 Jira Service Management agents, every paid app you install is billed at the 100-user level.

And the licence has to match that tier. You can't buy a 10-user licence for a 100-user site, and you can't choose which people get access for billing purposes. Restricting who can see the app doesn't change who you pay for.

A few related rules are worth knowing:

• Vendors can set a free tier for 1–10 users. Some do, some don't. Once you cross ten users on the site, you pay the full tier for everyone.
• Annual billing is usually cheaper than paying monthly, but it locks in the user tier for the year.
• Every app follows the same rule. Install four paid apps, and you get four separate bills that each grow with your total Jira headcount.

Why the rule exists

To be fair to Atlassian and app vendors, the rule isn't arbitrary. Per-site licensing keeps billing simple, avoids complex per-person entitlements, and matches how Jira itself is priced. In a small team where everyone uses everything, it works fine.

The problem appears when a tool serves one role or one department inside a large Jira site. Test management, time tracking, reporting, Gantt views and document export are classic examples. A few people use them every day. Everyone else is billed for them.

What it really costs

Let's put numbers on it. The figures below are illustrative and don't belong to a specific vendor. Use your own app's Marketplace pricing at your real user tier.

Say an app lists at $5 per user per month:

• Your site has 100 Jira users, so you're billed for 100.
• That's $500 per month, or $6,000 per year.
• Only 10 people actually use the app.
• Your real cost is $50 per active user per month: ten times the list price.

Now repeat that for every role-specific app you run. Industry analyses of Atlassian spend regularly find that Marketplace apps become a line item comparable to the core product once a company has a handful of them installed. The headline price of Jira is rarely the price you actually pay.

The hidden effects

The direct cost is only part of the damage. Per-site pricing also changes how teams behave:

• Teams stop asking for tools. If one team's tool means a company-wide bill, the request often dies in procurement. People go back to spreadsheets.
• Shadow processes grow. Capacity plans, sprint reports and test logs end up in files outside Jira, where nobody else can see them.
• Growth gets more expensive. Every new hire in sales or support raises the cost of the engineering tools they'll never open.
• Renewals become negotiations. The app line is often the least governed part of the Atlassian bill, so it's where budgets get surprised.

How to audit your Jira app spend

You can usually cut this cost without losing anything your teams rely on. Start with a simple audit:

1. List every paid app on your site, with its monthly cost at your current tier.
2. Count real usage for each app. Ask app owners, check app-level activity where the vendor provides it, and talk to the teams.
3. Calculate cost per active user. Divide each app's bill by the number of people who used it last month. This single number makes most decisions obvious.
4. Remove what nobody uses. Old trials, duplicate tools and apps from finished projects are common.
5. Check overlap with what you already have. Jira's built-in features and automation keep improving, and they may cover a simple use case.
6. Look at tools outside the Marketplace billing model for role-specific needs, especially where only a small group needs the tool.
7. Negotiate before renewal, not after. Bring your cost-per-active-user numbers to the conversation.

Do this once a year, ideally a quarter before your Atlassian renewal date.

What LazyScrum does differently

LazyScrum is a layer on top of Jira, not a replacement for it. It reads your Jira data and adds what Jira doesn't do well for Scrum teams: live sprint planning down to 30-minute slots, a Daily Standup that compares progress against the plan, sprint history and reports.

It's licensed on lazyscrum.com, with pricing built around the people who actually run the process:

• Invited members are free. Team members you invite to Planning or Daily sessions join with a link and a code. They aren't billed as seats.
• You pay for active seats. An active seat is a Scrum Master, or any user added without an invitation.

So a team of 50 people with one Scrum Master pays for one seat, while the whole team takes part in estimation, planning and the Daily Standup.

Frequently asked questions

Can I license a paid Jira app for only some of my users?

No. On Jira Cloud, a paid Marketplace app must be licensed at the same user tier as your Jira site. You can limit who has access to the app with permissions, but billing still follows the site's total user count.

Which number does Jira use when I have several Jira products?

The highest user count across all Jira products on the site. If Jira has 100 users and Jira Service Management has 80 agents, apps are billed at the 100-user tier.

Do deactivated users count?

Billing is based on the users who have access to the product. Removing product access from people who have left, or who never use Jira, lowers your tier for Jira and for every app at the same time. It's the fastest saving most companies can make.

Are apps free under 10 users?

Only if the vendor chooses to offer a free tier for 1–10 users. Many do, but not all, and the free tier ends as soon as your site passes ten users.

Is moving to annual billing worth it?

Usually yes for apps you're sure you'll keep, because annual billing is typically cheaper than paying monthly. Do your usage audit first, though. An annual plan for an app nobody uses is a full year of waste.

How do I explain this cost to finance?

Use cost per active user. "We pay $500 a month for this app" sounds acceptable. "We pay $50 a month for each of the ten people who use it" starts the right conversation.

The takeaway

Per-site pricing is fine when everyone uses a tool. It's expensive when only one role does. Before your next renewal, calculate the cost per active user for every app on your site. The answer usually tells you exactly what to keep, what to cut, and what to replace.

Want to see what your Scrum process costs when you only pay for the people running it? Start your free trial of LazyScrum.