Jira Service Management prices on agents, not on the customers who raise requests. Customers (your end users) are unlimited and free; you pay only for agents who work tickets. That single distinction is where most JSM overspend hides, because organizations license people as agents who never actually need agent access. This calculator models the gap. It sits under our ITSM total cost of ownership calculators toolkit and pairs with the Freshservice agent cost calculator by plan tier.
Book a contract negotiation review →
The default rate is an example only. Replace it with the effective per-agent rate on your own quote or order form. JSM list pricing is volume-tiered, so the per-agent rate decreases as the agent count increases; confirm your tier against Atlassian's current pricing.
How is the Jira Service Management cost calculated?
The formula is simple: paid agents multiplied by the per-agent monthly rate, multiplied by twelve. The right-sized figure removes the agents you can reclassify as free customers, then applies the same rate. The saving is the difference. The reason this works is that JSM, unlike platforms that meter every requester, charges only for agents, so every person who only raises requests and never works a ticket should be a customer, not a paid agent.
The default values are illustrative. The accuracy of the result depends entirely on entering your real effective rate, which is the number after any volume tier and negotiated discount, not the published list rate for a single seat.
Why does the per-agent rate change with volume?
Atlassian prices Jira Service Management in volume bands rather than at a single flat rate. As your agent count crosses a tier boundary, the marginal per-agent price drops, so a 50-agent estate pays a different effective rate than a 5-agent or 500-agent one. This matters for two reasons. First, your effective rate is the only number worth modeling, so pull it from your quote. Second, sitting just below a tier boundary can mean a small increase in agents lowers your effective rate, which is worth checking before you buy. The volume-band mechanics across platforms are covered in per-agent vs per-fulfiller vs flat, which model wins by org size.
What drives the savings in a JSM estate?
- Reclassifying agents to customers. The largest and most common saving. Anyone who only submits requests should be a free customer. Audit who actually transitions, comments on or resolves tickets.
- Right-sizing the agent count. Remove dormant agents and seasonal seats that were never released.
- Tier choice. Standard, Premium and Enterprise differ in price and capability. Pay for Premium only if you use the features that justify it, such as advanced incident management or higher automation limits.
- Volume-band timing. Buy at a count that sits efficiently within a band rather than just over a boundary.
How accurate is this calculator?
It is a planning estimate, not a quote. It assumes a single blended rate and does not model tier mix, Atlassian Marketplace apps, Rovo AI add-ons or annual versus monthly commitment differences. Treat the output as a directional figure to size the opportunity, then validate against your order form. For the full negotiation context, see the Jira Service Management platform page and the Jira Service Management negotiation guide.
How do you confirm your effective per-agent rate?
Read it off the order form, not the website. Your effective rate is the annual agent subscription divided by the number of paid agents, after any volume tier and negotiated discount. The published single-seat price is almost never what a multi-agent estate pays, so using it overstates the bill and understates the saving. If you cannot find a clean per-agent figure, take total annual JSM spend and divide by paid agents; that blended rate is the number to enter.
What does the calculator deliberately leave out?
Several real costs, because they are estate-specific. It does not model the Rovo AI add-on, Atlassian Marketplace apps, the split between Standard, Premium and Enterprise tiers, or the difference between monthly and annual commitment. Marketplace apps in particular can add meaningfully to the per-agent cost and are easy to forget at renewal. Treat the output as the licensing baseline and add these lines separately when you build your full total cost of ownership.
How does this connect to the renewal?
The saving figure is your opening target, not your final number. Once you have the right-sized agent count, the next moves are confirming your volume tier, scoping the AI add-on to real users, and capping the annual uplift so the saving does not erode. Reclassifying agents to free customers is usually the largest single reduction on JSM, but a capped uplift is what protects it across the term.
How does JSM cost compare to per-fulfiller pricing?
The two models reward different estate shapes. Jira Service Management charges per paid agent and makes requesting customers free, which suits organizations with a large user base and a contained team of agents. A per-fulfiller platform like ServiceNow works on similar logic but counts fulfillers, and its list rate per unit is typically higher, justified by deeper enterprise capability. For a mid-market IT team, JSM's agent model and volume bands often produce a lower total cost; for a large enterprise with complex workflows, the per-fulfiller platform may justify its premium on capability. The calculator above models the JSM side; to compare across models, hold the unit definition constant and count the people who actually work tickets, because that is the number both models ultimately charge for.
What if your agent count is growing?
Model the band you are heading into, not just the one you are in. Because Jira Service Management prices in volume tiers, a growing estate can cross a boundary mid-term and change its effective rate, and a multi-year commitment locks in the band you negotiate now. If you expect to add agents, price the deal at the projected count and negotiate the rate for the band you will occupy, rather than buying at today's smaller count and paying a higher marginal rate as you grow. Run the calculator at both your current and projected agent numbers to see the gap.
Validate the JSM number.
We reconcile your agent count, confirm your volume tier and negotiate the rate. Fixed fee or gainshare.
Book a contract negotiation review →What to do next
Replace the default rate with your quoted effective rate, enter the agents you could reclassify, and use the saving figure to scope your renewal target. For buyer-side help validating the count and negotiating the rate, our contract negotiation service works on fixed fee or gainshare.
Frequently asked questions
- How is a JSM bill calculated?
- Paid agents multiplied by the effective per-agent monthly rate, multiplied by twelve. Customers who only raise requests are free, so the bill should reflect only people who work tickets.
- Why does the JSM per-agent rate vary?
- Atlassian prices JSM in volume bands, so the rate falls as the agent count rises. Your effective rate after the tier and discount is the only figure worth modeling; confirm it on your quote.
- What is the biggest saving in a JSM estate?
- Reclassifying paid agents who should be free customers, followed by removing dormant agents and choosing the right tier.