Atlassian [TEAM]
As of 2026-07-29. Framework v1.5.1. Tier-2 memo, cluster member (data & dev infrastructure).
Cluster analysis: reports/clusters/Data_Dev_Infrastructure_Cluster_2026-07-29.md
This memo issues no position verdict. The book decides.
Never fabricate a date. Every entry below is either (a) an exact date stated in a filing, or (b) an expected window inferred from the company's own filing history, with that history shown so the inference can be checked. Nothing here is invented, and where only a window is available it is labelled a window.
| Date | Event | Source | Why it matters |
|---|---|---|---|
| 2025-09 | Data Center end-of-life announced | 10-Q, repeated in four places | Start of the pull-forward. Data Center growth went from +15.8% (H1 FY26) to +44% (Q3 FY26). |
| 2025-10-20 | The Browser Company of New York acquired — $488.3m ($481.5m cash), plus $8.2m replacement RSUs and $97.0m of retention RSUs to key employees | 10-Q, Business Combinations note | $105m of retention equity on a $488m purchase — future SBC. No revenue contribution disclosed. |
| 2025-11-10 | "A Software Company" (DX) acquired — $720.4m, all cash | 10-Q, Business Combinations note | Engineering intelligence, folded into "Collections". No revenue contribution disclosed. |
| 2026-03 | No further Data Center term licences to NEW customers | 10-Q | This is the quarter Data Center revenue spiked 44%. |
| 2028-03 | Data Center term licences and EXPANSIONS to existing customers cease | 10-Q | The hard cutoff driving the pull-forward. Data Center growth goes structurally negative from here. |
| 2029-03 | Data Center maintenance and support end (with a ~three-year extension for certain customers) | 10-Q | Data Center revenue — 31.4% of the current total — goes to zero. |
Q4 and FULL-YEAR FY2026 (fiscal year ended 2026-06-30) — expected early August 2026 — the NEAREST catalyst in the cluster.
Basis for the inference: this company's own earnings-release 8-K filing dates (item 2.02) in prior years were 2025-08-07 (Q4/FY25). This is a pattern-based window, not a company-confirmed date. No date has been fabricated; if a confirmed date is required before acting, it must be taken from the company's investor-relations announcement.
Why this print is the one that matters for this name:
This is the fiscal-year-end report — Atlassian's year ended 30 June 2026 — and it is the nearest catalyst in the entire cluster. It is the first print that will show whether the Data Center pull-forward reversed. Three specific lines to read, in order:
Jan-2027 implied volatility is 78–85%, the highest in the cluster. The stock fell 28% in June 2026 and rose 34% in July with no filing in between. The market is positioned for this print.
Type: MEASURED. Time works for a long, so a dated event is not required to own this name — unlike a short.
| Dated events that would confirm or refute the implied path | yes — see §1 and §2 |
| Nearest catalyst | early August 2026 — the NEAREST catalyst in the cluster |
| Result | scored |
What the calendar deliberately does not contain: no product-launch dates, no conference dates, and no analyst-day dates have been included, because none was found stated in a filing. A fabricated catalyst date is worse than an absent calendar, and the absence is recorded rather than filled.
Type: MEASURED. Logged and scored on every name; it does not reject the name.
Named cause: the Data Center cliff arriving faster than Cloud replaces it, with the pull-forward reversing first.
| Scenario | Implied price | vs spot | Probability |
|---|---|---|---|
| Data Center to -10%, Cloud to 20%, multiple FLAT at 4.31x | $115.00 | +10% | not assigned |
| Same, multiple to post-2024 min of 3.1x | $82.50 | -21% | 30% |
| Cloud to 12%, Data Center to -20%, multiple 3.1x | $78.00 | -25% | not assigned |
| Migration failure, multiple to 2.5x | $63.00 | -40% | 12% |
Going-concern: not argued. See §9 of the research document for the balance-sheet basis.
Full reasoning, the mechanism, and why the probabilities are what they are: TEAM_Research.md §9.