Log the ten-seat Jira renewal before 13 October

The renewal is a decision, not a billing surprise

A small founding team can live with a messy inbox, but a missed software renewal is a different kind of mess. Atlassian, the maker of Jira and Confluence, is moving Cloud list prices across Jira, Confluence, Jira Service Management, and other apps. The Jira price increase in October 2026 is the sixth October move in a row, and the compounding price increase since 2023 is roughly 24 percent. The date belongs in the log, not in memory.

For a small company, the Jira Cloud renewal math is mostly seat hygiene. The plan name matters, the seat count matters, and the owner matters. The renewal decision log is the artifact that keeps the next renewal from becoming a scramble.

The tier check is the part that saves the invoice

The Jira seat tier check is a seat audit. You need to know which plan you are on, how many seats are active, and whether the seat count changes the percentage. If the plan is Standard or Premium and the organization is under 5,000 seats, the list-price move is about 7 percent. If the organization is above that threshold, the move is about 10 percent, and Enterprise list prices move about 8 percent.

Start with the user list, not the invoice. Export the named users, compare the names against the current team, and mark anyone who left, changed roles, or should be on a lower-cost plan. The invoice tells you what you paid. The user list tells you what you should pay.

A departed contractor can sit on a seat for months. A new hire can be added mid-cycle. A guest account can become a named user. The tier check catches those gaps before the next invoice does. The export is the evidence for the seat count. It is the part you can show later. Keep it with the log entry for the next review.

If you want a quick sanity check on the percentage, a 200-user annual Cloud benchmark shows Jira plus Confluence Standard changing from $28,500 to $30,500, about 7.0 percent. The same benchmark shows Premium changing from $55,000 to $59,000, about 7.3 percent. Your small invoice will be smaller, but the shape of the math is the same: current per-seat price, applicable percentage, new per-seat price.

The log entry is the artifact

The log entry is short, but it has to be complete. The vendor and date fields pin the contract. The price and seat fields pin the math. The owner and action fields pin the follow-through. Each field below is testable in a minute, and together they answer who signs the renewal, what changed, and what happens before the price date.

1. Vendor: copy the exact product names from the invoice, including any apps on the same renewal.
2. Renewal date: enter 13 October 2026 as the date the new annual list prices start.
3. Old/new per-seat price: copy the current annual per-seat price, then apply the applicable percentage from the tier audit.
4. Affected seats: count every named user, remove inactive seats, and note the final number.
5. Tier audit result: record the plan, the active seat count, and the applicable percentage.
6. Owner: name the person who signs the renewal and the person who can approve a seat change.
7. Action before the price date: schedule the tier check and renewal approval before the date in the log.

The owner field is where the ritual lives. A founder can sign the first renewal, but the next renewal may happen after a role change, a vacation, or a quiet handoff. The log should name the person who can act without asking permission.

The action field is the only one that creates a deadline. If the tier check is scheduled, the owner is named, and the new per-seat number is written down, the renewal becomes a boring line item. If any of those three is missing, the price date becomes a surprise.

Put the log entry in the same place as the other operating decisions: the same document, the same owner, and the same review cadence. A renewal is a decision with a date, a number, and a name. Keep it visible until the renewal is signed and paid.