Home  /  Research Videos  /  Atlassian
Atlassian · 4:19 · Buyer-side briefing

Atlassian Renewal, Part 2: Negotiation Prep, Three Calls Ahead of the Increase

The negotiation prep from the VendorBenchmark Atlassian renewal briefing: the framing call and its five questions, the deflections word for word, the six moves of the deconstruction call, the close call checklist timed to June or the increase calendar, and how to customize the script for Data Center, migration, and tier cliffs.

Share

The presenters in this briefing are AI generated avatars. The research, figures, and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.

Transcript

Full narration of the briefing. Click a section heading to jump the player to that moment.

Call one: the framing call 0:00

Part one gave the talking points. Now the three calls. I am Claire, Tom is with me, and this is part two of the VendorBenchmark Atlassian renewal prep. Call one, six to nine months out, controls the process and puts your audits on record.

Open with it: we run this renewal as a formal sourcing event, alongside a user activity audit and a marketplace app review; all commercial communication routes through me, including anything through partners; and today I need a like for like quote at current editions and net prices, every announced list increase that touches our renewal window, and your timeline from quote to signature.

Five questions 0:42

Five questions, in order. Will the renewal be quoted like for like at our current editions, tiers, and net prices, in writing. Which list increases are announced or planned that affect us, and what multi year terms lock current pricing. What repackaging applies to us: AI fold ins, edition changes, anything that moves our per user cost.

If we evaluate migration, what dual licensing, credits, and loyalty pricing are available, in writing, before we decide. And when does your fiscal quarter close relative to our renewal date. Question two is the cheapest money: signing ahead of an announced increase is a discount nobody has to approve.

Deflections, and call two opens 1:30

Deflect these word for word. Pricing is standard and non negotiable: the list is standard; terms, timing, tiers, and the enterprise desk are not. They ask about budget: we build the budget after we see your like for like quote. They ask about migration intent: it is under evaluation, and the concessions available will be visible in the evaluation.

Then call two, after the first quote. Never react to numbers in the meeting where you receive them. Open with the baseline: our current estate costs X per year, our audits support Y, your quote is Z; walk me through every product and every band, one at a time.

The six moves of call two 2:08

The six moves of call two. Unbundle everything: every product, edition, and the marketplace on its own line; a blended number is a decline. Drop the band before the rate: the user audit removes the inactive accounts, landing us in the lower tier, and the apps reprice with it. Strike the fold in: current net, the delta as a declinable line; we do not pay a renaming.

Rationalize the marketplace: these apps come out; the rest we negotiate with their vendors. Play the timing or the migration, never neither. And summon the desk: whoever owns enterprise pricing; I do not run final rounds through a portal.

Call three: the close 2:48

Call three, timed to June or the last window before an announced increase. Open with: we sign inside your quarter if the remaining items land; here is the complete list; nothing gets added after today. Per product pricing at audited bands and current net, in the order. A multi year term locked at pre increase list, or the migration package in writing.

Uplift capped at zero to three percent beyond the lock. Successor protection if editions are repackaged or AI refolded. A price hold for added users across one band. Everything co terminated, with a short extension pre agreed as fallback.

Customize the script 3:27

Customize it. Staying on Data Center: take the longest multi year term available, signed before the next increase, with cloud exit economics in writing. Migrating: this is the one moment Atlassian pays you, so extract dual licensing for the full window, credits sized to the project, and loyalty pricing, before anything is announced. Approaching a tier cliff: clean inactive accounts first, and if growth crosses the band anyway, trade the crossing first.

And when it stalls: the cleanup executes either way; the question is whether this lands in your June or after your next increase, unsigned. More briefings at redresscompliance dot com slash research videos.

The research playbook behind this briefing

Atlassian Renewal: Talking Points, Call Scripts, and Negotiation Prep

This briefing is drawn from the full playbook by Vendor Benchmark LLC: the preparation runway, the estate math, the give and get table, the tactics and counters, and the concessions checklist. Read it here, save the PDF, or send it to whoever owns the renewal.

PDF, free, no form. Opens in the page on desktop, or in your browser's own viewer on a phone.

Negotiating a Atlassian renewal this year?

Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.

Talk to a Atlassian negotiator
Browse all 237 research videos