Invest1 distinct publisher3 min readUpdated
Revenue rose 28%, RPO rose 44%, and the stock moved 35% in a session. The backlog suggests agents are creating work items, not deleting them, but the FY27 margin guide shows what defending that costs.
The Investor · Invest desk

Compiled by The InvestorSomething wrong?How this is made
Atlassian reported fourth-quarter revenue of $1.766B, up 28% year over year, and remaining performance obligations of $4.817B, up 44% [2][5]. The stock had traded around $84 in early July on the argument that AI agents would write the code, file the tickets and squeeze work-tracking tools out of the middle; it closed at $110.17 on the August 6 print and traded toward $146 the next morning, a 35% single-day move [7][9][8][1].
RPO is the line that speaks to the bear case, because it is contracted revenue not yet recognised. It grew at roughly twice the rate of subscription ARR, which came in at $6.606B, up 23% [5][4]. That is customers committing longer and larger, not trimming ahead of an agent-driven cleanout. SaaStr's reading is that in software development tooling so far, more agents has meant more work items, more branches, more reviews and more governance, and Atlassian sells the coordination layer for all of it [23].
Growth also went up rather than down at scale, which is the uncommon part. Cloud revenue grew 28% for the full fiscal year and 31% in the quarter; total revenue grew 26% for the year and 28% in the quarter [10][11]. Cloud is now about 69% of quarterly revenue [5]. GAAP operating income was $211M against a $28M loss a year earlier [6], across more than 350,000 customers including 85% of the Fortune 500 [14].
One deduction against the headline: reported revenue grew five points faster than subscription ARR [1]. SaaStr argues revenue is the lagging figure here, flattered by contract timing and Data Center renewals, and that 23% is the better read on the underlying run rate [19].
The cost of holding the category shows up in the guide, not the quarter. Atlassian is bundling its agentic capabilities into paid Jira Cloud at no additional charge, including orchestration of third-party coding agents such as Claude Code, Cursor and GitHub Copilot [15]. Rovo is used by more than 80% of the Fortune 500, and Rovo-assisted actions grew 50% quarter over quarter [16]. Non-GAAP operating margin hit a record 36% in the quarter, up from 24% [12], and the company then guided 28.5% for Q1 FY27 and 25% for the full year, with GAAP operating margin of 4.5% against 12% in the quarter [17]. That is 11 points of non-GAAP margin handed back [3], with non-GAAP gross margin trimmed from 88% in FY26 to a guided 86.5% [18]. FY26 free cash flow fell to $1.319B from $1.416B, a decline of about $97M [13][4].
Figma, which reported the day before, is the useful contrast. It grew 48% at a $1.5B run rate, a third consecutive quarter of acceleration, beat and raised, and the stock fell 15%, with attention landing on GAAP gross margin of 84%, down about five points year over year, because inference is a real per-request cost and some of it sits on beta products generating no revenue [20][21]. SaaStr's framing is that AI cost arrives in the P&L one to four quarters before AI revenue does [22]. Atlassian took it in operating margin and guidance; Figma took it in gross margin.
Two things to follow. Whether RPO growth holds near 44% or was pulled forward by long renewals, and whether subscription ARR converges up toward reported revenue or reported revenue decays back toward 23% [5][1][19]. And whether the 25% FY27 margin guide is sandbagging or the honest price of giving agentic features away free inside Jira [17][15].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Atlassian closed its fiscal year on June 30 and reported results on August 6.
Q4 cloud revenue was $1.213B, up 31% year over year, and accelerating.
Remaining performance obligations (RPO) were $4.817B, up 44% year over year.
GAAP operating income was $211M, against a $28M loss a year earlier.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Specific financials, single secondary source
The quantitative spine is unusually concrete and internally consistent (revenue, cloud, ARR, RPO, GAAP operating income, free cash flow, margin guides, stock levels), and the article volunteers a caveat against its own headline. But everything reaches the reader through one publisher's summary of an earnings event with no filing, release or transcript cited, and the load-bearing interpretive claims are the publisher's own.
Broad installed base, vendor-reported AI usage
Deployment scale is real and large: 350,000+ customers including 85% of the Fortune 500, cloud revenue of $1.213B growing 31%, and RPO up 44% indicating contracted future work. AI-specific adoption is weaker evidence: Rovo penetration and 50% sequential growth in assisted actions are company-supplied metrics with no definition of an assisted action, and the agentic bundle ships free, so usage does not yet demonstrate willingness to pay.
Mildly overstated causal read on one quarter
The framing that backlog growth answers the AI-agent bear case runs ahead of what one company's quarter can show: the mechanism (more agents produce more work items and governance) is asserted without volume data, the one-to-four-quarter AI cost lead is a generalization from two prints, and the headline 28% revenue growth exceeds the 23% ARR run rate the article itself calls the better read. The story earns a modest rather than large gap because it discloses the margin give-back and the ARR caveat in the same piece.
Vendor-supplied metrics via a founder-audience publisher
The AI-adoption and packaging figures originate with Atlassian in an earnings context, where the company benefits from showing agents as demand rather than threat, and free bundling with tier upgrades is a commercial strategy being narrated favorably. The publisher writes a recurring 'interesting learnings' format for a SaaS founder and operator audience that rewards a clean growth lesson. Offsetting this, the piece foregrounds the margin guide and the ARR-versus-revenue gap, which cut against a purely promotional read; no sponsorship or financial relationship is disclosed either way.
Reported numbers solid, interpretation single-threaded
Confidence is moderate: the financial and stock figures are precise and mutually consistent, and the story is recent relative to the August 6 print, so the factual layer is likely reliable. The interpretive layer that gives the story its meaning depends on one publisher's reading, with no second outlet, filing or customer-side evidence available in the cluster, and the source text is truncated before the pricing argument concludes.
build
AI-written code fails the same four ways, and every gate you own reports green1 distinct publisher
build
Claude Code now outruns Copilot roughly two to one in JetBrains' survey of 15,000 developers1 distinct publisher
build
The defect tax on in-editor models is a review capacity problem, not a tooling one1 distinct publisher
build
Three tools, three spellings of the same glob: agent rules do not port1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.