How to read a price increase before it cuts your margin

The effective date decides which price you pay

You are about to renew a software subscription, and the vendor's notice may lead with a percentage. The date decides which price you pay; the percentage only shows the size of the change. Atlassian's updated Cloud list prices take effect on October 13, 2026, and they apply to new purchases, renewals, and upgrades.

Price notices often lead with the percentage because it is easier to read. Your renewal date is the one that matters for the money you keep. Ask for the effective date in writing when the notice is vague. Use a calendar note with the new-price start date and your renewal date to make the comparison clear.

A quote date can save the old price

Start with the quote date and its expiration date. Quotes made before October 13, 2026 keep the old price until the expiration date stated on the quote, while quotes made after that date use the new prices.

Renewal purchases are allowed only inside a 90-day renewal window, so a customer whose annual term ends in March cannot immediately lock in the old price. Early in the window, ask whether a quote can be generated now. A late window makes the quote date the only thing you can control.

Customers need to pay before an Atlassian quote lapses to retain the quoted price, and no extension can push the deadline past November 11, 2026. Ask for the quote date and expiration date in writing. A payment deadline earlier than the quote expiration date is the safe version.

The seat count and plan set the rate

Next, look at the seat or volume threshold. For Jira Cloud, Confluence Cloud, and Teamwork Collection, Standard and Premium list prices rise 7% below 5,000 seats and 10% at 5,000 seats or above.

When a Jira or Confluence Cloud renewal crosses from below 5,000 seats to above 5,000 seats, the entire renewal moves into the 10% band, not just the extra seats. Reducing a subscription to below 5,000 seats may bring the increase down from 10% to 7%.

Count active seats, not licensed seats, before you ask for a quote. A seat means the person who uses the tool, not the license that sits unused. Near the limit, list the people who actually use the tool and remove seats that are not needed before the quote is generated. Write the seat count next to the renewal date, with the applicable rate beside it, to make the choice easier.

Match the plan level before you accept the number. Jira Software and Confluence Teamwork Collection Enterprise list prices rise 8% no matter the seat count. Jira Service Management and Service Collection list prices rise 7.5% on Standard and Premium plans and 10% on Enterprise. Bitbucket Cloud Premium list prices rise 10%, Standard has no listed increase, and the five-user minimum goes away.

The margin impact is the real decision

Finally, weigh the margin impact on your renewal, the money you keep after the tool cost. Put the new annual cost next to the revenue that depends on the tool. Small percentages can matter when the tool is a large part of the cost. When the increase eats a meaningful share of the margin, you have a decision to make: negotiate, remove unused seats, or accept the higher cost.

Customer-facing tools need the promise next to the cost. Internal tools need the time saved next to the cost. Write the number down. Changing the seat count or the quote date means running the same checks again.

Keep the note with the quote. If the vendor changes the number, you can point to the date, the seat count, and the plan name. Use a one-line note showing whether the renewal still leaves enough money to keep.

Keep the four-question price-notice checklist:

• When does the new price start?
• What are the quote date and expiry?
• Which seat or volume threshold applies?
• How much margin does the renewal keep?