Atlassian (TEAM) Deep Dive: From a “Jira company” to the “operating system for team work”—how far can it become foundational in the AI era?

* This report is prepared based on data as of 2026-02-07.

What does this company do? (An explanation a middle schooler can understand)

Atlassian (TEAM) makes business software that helps teams run the full loop of “request work, track progress, document what happened, share it, and resolve issues”—all in one place. It’s not a consumer app company; it’s better thought of as an enterprise “toolbox for getting work done.”

Who uses it (customers)

• Software development teams (builders): manage development tasks and bug fixes
• Business teams such as planning, design, sales, and HR (non-builders): run projects and handle requests
• IT departments and IT operations teams: run internal issue intake
• Large enterprises: many departments and a desire to standardize/control tools

The basic idea is simple: as teams get bigger, communication gaps and rework tend to rise. Atlassian’s suite becomes more valuable as organizations scale and coordination gets harder.

What it sells (core product suite)

Atlassian’s core offering is a set of standard tools for moving work forward. Each product can stand on its own, but the platform tends to deliver more value when multiple products are connected and run as a shared “operating model.”

• Task and project management: like Jira, which “turns work into tickets” and makes owners, deadlines, and progress visible
• Knowledge and document management: like Confluence, which keeps meeting notes, specs, and rules in a searchable format
• Inquiry handling and service management: like Jira Service Management, which standardizes “intake → prioritization → processing → recordkeeping” (and can extend beyond IT into general affairs, HR, and operations)
• Explain and share via video: like Loom, which speeds up explanations and reviews through short screen recordings

How it makes money (revenue model)

The model is straightforward: usage-based enterprise subscriptions. Customers pay monthly or annually based on seat count and plan tier (including admin and security features), and the product design supports expansion in revenue per customer as more products are adopted together.

A notable recent go-to-market emphasis is strengthening “collections” (bundling) across multiple products. Teamwork Collection bundles Jira, Confluence, and Loom with the AI product Rovo (discussed below), positioning it as a core team package.

Why it is chosen (value proposition)

In middle-school terms, Atlassian is strong at “traffic control for work.”

• Work is less likely to get lost: it reduces misses by turning work that might otherwise live in hallway conversations or chat threads into tickets
• Explanations and rules are searchable: putting decisions in one place makes handoffs and onboarding easier
• The larger the company, the more it helps: as departments multiply, friction rises—so a standard operating model becomes more valuable

Analogy (just one)

Using a school festival analogy, Atlassian is trying to put “a to-do whiteboard,” “a shared notebook,” and “a question intake counter” into the same classroom—and then add “a smart staff member (AI).”

Future upside: Cloud × Enterprise × Bundling, and AI (Rovo)

From here, the investment call depends not just on what Atlassian sells today, but where it’s trying to go. The company is doubling down on cloud migration and deeper enterprise penetration, while using bundling to capture “operational standards” across teams.

Growth drivers (three tailwinds)

• Cloud-first: Atlassian can deliver updates and new features more easily, while customers reduce operational overhead. It is also strengthening AWS collaboration and migration support to accelerate enterprise migrations.
• Deepening Enterprise: the more departments a company has, the greater the value of tool standardization, and the easier it is to expand product footprint per customer
• Bundling (collections): create “install this and it runs cross-functionally,” like Teamwork Collection, to make adoption and expansion easier

Separately, the phased reduction timeline toward end-of-support for Data Center products has been clarified. That can raise the pressure to migrate to cloud (by forcing decisions) and will likely shape the forward narrative.

Future pillars (areas that could reshape in the AI era)

Atlassian’s direction is evolving from “a ticketing tool” toward “a place where company work information can be leveraged across functions.” Two pillars sit at the center: the AI product Rovo and broader, company-wide service management.

• Rovo (use AI to find internal information and move work forward): an “AI assistant (agent)” concept that searches, summarizes, and proposes actions using internal knowledge and work information, and helps with simple tasks. While pointing toward a future that connects not only Atlassian products but also external tools, it emphasizes permission-aware design—handling only information users are allowed to see.
• Prioritizing Rovo adoption (penetration over monetization): rather than pricing Rovo as a standalone add-on, there are signs Atlassian is prioritizing broad adoption by embedding it into existing cloud contracts. The intent appears to be getting it “into the workflow” rather than maximizing near-term ARPU.
• Service Collection (from IT to company-wide): expand service management from an IT tool to “all departments that handle inquiries,” such as Ops, HR, and customer support. If it scales, the “front door” for company issues can increasingly route through Atlassian.
• Data foundation build-out (reported Secoda acquisition): an acquisition of Secoda in the data catalog space has been reported to strengthen Rovo. This points to building the foundation for smarter AI (where internal data lives and what it means).

A critical “internal infrastructure” separate from the business: a Teamwork Graph-like foundation

Atlassian frames its AI edge as the ability to leverage data across “how teams work.” Using a factory analogy, it’s like having a “blueprint of the production line.” The stronger this foundation is, the faster search can be, the more accurate summaries become, and the smarter next-step recommendations get—an area where AI feature quality can improve meaningfully.

Long-term fundamentals: Revenue and FCF grow, but EPS clouds the “pattern”

Over the long arc, Atlassian’s fundamentals are defined by strong revenue growth and expanding cash generation (FCF). At the same time, accounting profitability (net income and EPS) has remained negative for extended periods, which is not the profile of a typical “steady profit compounder.”

10-year and 5-year growth: Revenue and FCF are high-growth

• Revenue CAGR: ~32.2% over 10 years, ~26.4% over 5 years (FY2013 ~$0.149B → FY2025 ~$5.215B)
• Free cash flow CAGR: ~36.0% over 10 years, ~21.3% over 5 years (FY2013 ~$0.047B → FY2025 ~$1.416B)

EPS: Often negative over the long term, making it difficult to define as a growth rate

EPS was positive in some years from FY2013–2016, but has been broadly negative since FY2017, with FY2025 at -0.98 dollars. As a result, 5-year and 10-year EPS CAGR is difficult to assess over this period, which makes TEAM hard to classify under a Lynch-style framework built around “stable EPS growth.”

Profitability: Gross margin in the 80% range, but operating margin and ROE are not stable

• Gross margin: in the 80% range over the long term, consistent with software (FY2025 82.8%)
• Operating margin: has swung between positive and negative depending on the year (FY2025 -2.5%)
• ROE: -19.1% in the latest FY (often negative over the long term)
• FCF margin: has generally been relatively high on an annual basis (FY2025 27.1%, FY2024 32.5%, FY2021 38.5%)

What the latest TTM looks like (note the period differs from FY)

On the latest TTM basis, revenue is ~$5.760B, net income is approximately -$0.189B, EPS is -0.72 dollars, free cash flow is ~$1.268B, and FCF margin is ~22.0%. Differences between FY and TTM can simply reflect period timing; rather than treating them as contradictions, it’s best to interpret results within the same time frame.

Long-term view of capital structure: BVPS increases, share count also increases

• BVPS: increased from FY2016 3.78 dollars → FY2025 5.14 dollars
• Shares outstanding: increased from FY2013 ~0.209B shares → FY2025 ~0.262B shares, implying a setup where per-share earnings growth can be diluted by share count growth

Viewed through Lynch’s six categories: a “hybrid” that is hard to classify cleanly

Atlassian has delivered strong revenue and FCF growth—very “growth stock-like”—but with net income and EPS negative over long stretches, it doesn’t fit cleanly into Fast Grower or Stalwart (stable profit growth and sustained profitability).

So this article treats TEAM as a hybrid: “revenue growth looks closer to Fast, but profits are immature/accounting profits are unstable, while FCF is positive.” The numerical anchors are revenue 10-year CAGR ~32.2%, 5-year CAGR ~26.4%, and FCF 5-year CAGR ~21.3%.

Checks for cyclicality / turnaround / asset play characteristics

• Cyclicals: from FY2013 to FY2025, revenue increased almost consistently, and clear “peaks and troughs” in revenue are not prominent
• Turnarounds: since FY2017, net income and EPS have remained negative, so it’s hard to argue a long-term turnaround has been completed via sustained profitability (TTM EPS and net income are also negative)
• Asset Plays: PBR is ~39.51x in the latest FY, which does not align with an “asset undervaluation” thesis

Does the “pattern” hold in the short term (TTM): Revenue is strong, but profit and FCF momentum are weak

The question here is whether the long-term hybrid profile has broken over the most recent year. The takeaway: the pattern largely holds, but near-term momentum looks “decelerating.”

Five-metric check on the latest TTM (consistency with the pattern)

• EPS (TTM): -0.72 dollars, YoY -45.8% (deterioration). The long-term feature of negative EPS remains.
• Revenue (TTM): $5.760B, growth +20.1%. Below the long-term 5-year CAGR (~26.4%), but still solidly high-growth.
• FCF (TTM): $1.268B, FCF margin 22.0%. However, YoY -8.4% and trending soft (FCF is positive, but not smooth).
• ROE (latest FY): -19.1%, consistent with weak accounting profitability
• PER/PEG: cannot be calculated because TTM EPS is negative. The challenge of valuing the stock on earnings multiples remains.

Momentum call: Decelerating

Across multiple metrics, the latest year (TTM) growth rates are running below the 5-year averages, supporting a “decelerating” momentum read. That said, revenue is still growing at +20.1%, so this is not framed as a clear, broad-based stall.

Supplement: Operating margin trend over the last 3 years (FY) (avoid mixing FY and TTM)

On an FY basis, operating margin improved from FY2023 -9.8% → FY2024 -2.7% → FY2025 -2.5%, with losses narrowing. That’s progress on an FY view, but margins remain negative as of FY2025; paired with TTM EPS deterioration, the cleanest framing is still “profitability has not yet stabilized.”

Financial health: Net-cash-leaning indicators coexist with weak interest coverage

Atlassian’s near-term financial profile has “two sides.” It’s not most naturally read as a highly levered company facing immediate liquidity stress; instead, the more practical interpretation is that profit volatility is showing up in the ratios.

• Debt ratio (equity ratio): ~92.1% in the latest FY (not a low-leverage profile)
• Net Debt / EBITDA: -70.65x in the latest FY (the negative value suggests a net-cash-leaning position within what the metric indicates; note it can swing materially with denominator volatility)
• Cash ratio: ~92.3% in the latest FY (a near-term cash cushion)
• Interest coverage: -2.24x in the latest FY (not an easy-to-label “healthy” level. Alongside net-cash-leaning indicators, this may be more about P&L instability than the absolute level of debt)

From a bankruptcy-risk perspective, net-cash-leaning indicators and a cash cushion can support resilience. But years of weak interest coverage can still become a debate point, particularly if it shows up as decision rigidity (for example, more defensive cost cutting).

Where valuation stands today (historical comparison vs the company only)

This section does not compare TEAM to peers; it only places today’s valuation against Atlassian’s own history. Because PER/PEG are hard to use for this company, cash-flow and balance-sheet metrics carry more weight in the discussion.

1) PEG: Cannot be calculated (because PER does not hold)

With negative TTM EPS, PEG cannot be calculated, and building a meaningful historical distribution is difficult over this period. In that sense, the inability to discuss “valuation relative to growth” via PEG is itself a defining characteristic of the name.

2) PER: Cannot be calculated (cannot be positioned on earnings multiples)

PER (TTM) cannot be calculated because EPS is negative, and positioning it historically over the past 5 or 10 years is also difficult within an earnings-multiple framework.

3) Free cash flow yield: Positioned above the historical range

FCF yield (TTM) is 6.27%. That’s above the typical range over the past 5 years (1.15%–2.61%) and also above the typical range over the past 10 years (1.23%–2.33%). A higher yield can reflect either “price down” or “FCF up,” so the point here isn’t to attribute the driver—it’s simply to note that the metric sits on the “higher than historical” side of the distribution.

It’s also relevant that FCF over the last 2 years has a 2-year CAGR of -0.18%—flat to slightly down—so it’s hard to describe this as a period of rapid FCF expansion.

4) ROE: Negative, but on the shallower-loss side of the historical distribution

ROE in the latest FY is -19.08%. It sits toward the upper end (less negative) within the past 5-year range (-166.22% to -27.10%), and remains within the past 10-year range (-121.95% to -11.01%). It’s still not a “high-ROE company,” but relative to history it leans more toward improvement—while remaining negative.

5) FCF margin: Positioned below the historical “normal band”

FCF margin (TTM) is 22.02%, below the past 5-year typical range (26.18%–33.67%) and also below the past 10-year typical range (26.18%–33.63%). FCF is positive, but the cash-generation “thickness” in the latest TTM is lighter than what has been typical historically.

6) Net Debt / EBITDA: As an inverse metric, it breaks out to “more negative” (net-cash-leaning)

Net Debt / EBITDA is an inverse metric: the smaller (more negative) the value, the more it tends to indicate a “closer to net cash” position where cash exceeds interest-bearing debt. The latest FY value of -70.65x is below (more negative than) the past 5-year typical range (-45.93x to 2.28x) and also below the past 10-year typical range (-46.66x to 2.28x). In historical context, it sits firmly on the side of lower financial-leverage pressure (though that alone does not imply an investment conclusion).

Cash flow tendencies: How to read a company where EPS and FCF diverge

Over time, Atlassian has shown a clear divergence: revenue grows, FCF is positive, but EPS remains negative. Rather than treating that as a simple “weak business” signal, it’s more useful to view it as a company where accounting profits have been hard to stabilize, alongside a SaaS-like ability to generate cash.

That said, in the latest TTM, while FCF is positive ($1.268B), it is down -8.4% YoY, and FCF margin is also below the typical bands of the past 5 and 10 years. Whether cash-generation “thickness” returns becomes a key quality debate. Without claiming whether this reflects temporary investment dilution, a shift in business momentum, or something else, the practical approach is to track it through the “observable variables (KPIs)” outlined next.

Shareholder returns and capital allocation: Dividends are unlikely to be a primary theme

On the latest TTM basis, dividend yield cannot be obtained, and data such as dividend per share and payout ratio are also insufficient on a TTM basis, so dividends are unlikely to be a primary investment theme within this scope. Meanwhile, TTM free cash flow is ~$1.268B (~22.0% of revenue), confirming meaningful cash generation; for shareholder returns, this is more likely a story about reinvestment for growth and non-dividend capital policies than about dividends.

Why this company has won (the core of the success story)

Atlassian’s core value is that it turns organizational work into “recordable and traceable” artifacts, reducing the friction that grows with scale (rework, key-person dependency, and communication gaps). It’s not just a communication tool; it’s closer to infrastructure that enforces operating discipline (a standard operating model).

• Persist tasks as tickets: lock work into a form that can be audited later, supporting audits, handoffs, and quality control
• Place knowledge where it can be searched: convert scattered information into a shared organizational asset
• Workflow inquiry handling: make “intake → routing → processing → recordkeeping” easy to replicate across teams

Because of that role, even when replacement happens, it often looks like a phased transition paired with operating changes—not a clean “rip-and-replace.” That dynamic contributes to stickiness (switching costs).

Is the story still intact: Can integration and AI enter “day-to-day execution”?

Without overstating what has changed over the last 1–2 years, two shifts stand out: AI moving from optional to expected, and a pivot from single-product strength toward bundled adoption. Both are consistent with the broader success story of becoming an operating OS.

Organizing the narrative drift

• AI moving toward standard functionality: broaden Rovo rollout by including it in cloud contracts, shifting from “an add-on for those who choose it” to “a baseline experience for all users”
• Bundling becoming central vs single products: increased emphasis on an integrated experience via Teamwork Collection
• Consistency with the numbers: over the past year, revenue growth has held up, while profits are weak and FCF margin has moved to the thinner side versus historical norms—an asymmetry that stands out

In this phase, it’s easy to describe the future as “more value through integration and AI,” while near-term execution tends to come down to pricing, bundling mechanics, and how migrations are actually pushed through. Externally, there are also observed comments that bundling and price changes are increasingly part of the framing—not as “sentiment,” but as a debate about adoption quality.

Invisible Fragility: Not a sudden collapse, but gradual drift

Atlassian’s downside mode is less about a sudden break and more about slow erosion—where partial substitution and execution slippage compound over time. The same elements that read as strengths (enterprise expansion, integration, AI) also introduce operational friction and the risk of partial fragmentation.

• 1) Heavier execution as enterprise mix rises: slower decision-making, governance requirements, and longer migrations increase adoption friction. During cloud migration cycles, deals can stretch out or pause based on customer circumstances, making “adoption momentum” harder to read.
• 2) Rapid shifts in the competitive landscape (single-function × AI accelerates substitution): as lighter, faster experiences proliferate in each category, department-level “local optimization” switching becomes more likely. Because Atlassian wins through integration, if partial fragmentation advances, cross-product data can be lost and AI context can weaken in a chain reaction.
• 3) Loss of differentiation (risk that bundling looks like life extension): if bundling is increasingly perceived as “price adjustment” rather than “adoption expansion,” the core story weakens. Externally, there are phases where organic growth deceleration and bundle dependence are discussed more often; that can be an early warning signal (not asserted as a conclusion).
• 4) External dependence in the AI layer (a practical “supply chain”): software has fewer physical constraints, but as AI becomes more central, external models, compute resources, and cost design (usage caps, potential future usage-based pricing, etc.) can more directly shape the user experience.
• 5) Deterioration in organizational culture: negative reporting around recent workforce reductions and organizational changes, and employee reviews suggesting distrust and friction post-layoffs, have been observed. If culture is damaged, execution in migration support, admin experience, and support quality can weaken, increasing the odds of partial switching.
• 6) Gradual deterioration in profitability (profit and cash-generation thickness): if “revenue grows but profits don’t improve / cash thickness doesn’t return” becomes the steady state, it becomes harder to see payback from AI and integration investments.
• 7) Financial burden shows up less as bankruptcy risk and more as decision rigidity: while indicators suggest ample cash on hand, years of weak interest coverage can push more defensive cost cutting and potentially reduce product value by limiting quality investment.
• 8) The industry’s subject shifts from “management” to “automation”: if customers increasingly want “work to move forward automatically,” not just “a place to record it,” then Rovo can’t stop at search and summarization. The key question is whether it can advance execution with permissions, context, and audit trails.

Competitive landscape: Category fragmentation × department adoption × AI shifts differentiation

TEAM competes in enterprise software that supports “how work gets done,” a market defined by fragmented categories, decentralized adoption, and AI-driven shifts in differentiation. Atlassian’s strategy is less about being best-in-class in any single function and more about delivering an “operating OS” that runs tickets + knowledge + intake under one operating philosophy.

Major competitive players (representative examples)

• ServiceNow: targets standardization through enterprise service management and company-wide workflows (governance, extensibility, horizontal rollout)
• Zendesk: often compared in inquiry handling (especially external support)
• Freshservice (Freshworks): IT service management for mid-market to growth companies (ease of deployment, cost, speed to launch)
• Monday.com: work management for non-engineering functions (UI/flexibility, visibility)
• Asana: project operations centered on business functions (visibility from goal management to execution)
• ClickUp: all-in-one orientation and often a department-level replacement option (improving integrated experience including AI)
• Notion: frequently raised as a replacement candidate for Confluence in documents/knowledge

Atlassian’s efforts to build migration paths from other tools (Asana / ClickUp / Monday / Trello, etc.) suggest competition is increasingly being fought on the assumption that switching will happen.

Competitive issues by domain (structure)

• Task management: lightweight usability for anyone vs operational robustness that holds up in complex environments; design from department adoption to company-wide rollout
• Documents: ease of creation, searchability, permissions/audit, and whether it connects to tasks (audit trails)
• Service management: whether it can expand horizontally from IT to non-IT departments; governance, automation, and integrations matter
• Loom (video sharing): standalone recording is easy to substitute; the question is whether it becomes embedded in workflows
• AI: differentiation is less about having features and more about delivering outcomes by tying into permissions, audit, evidence trails, and operational data

Moat: Not algorithms, but embedded “operations, permissions, audit trails, and integrations”

TEAM’s moat is less about having the best standalone AI algorithms and more about being embedded in how organizations operate—through operating design, permissions, auditability, integrations, and template libraries. Once it’s in place, replacement tends to become an implementation/migration project rather than a simple feature comparison, which supports stickiness.

That moat, however, depends on the customer’s operational maturity. It’s strongest where the integrated experience is truly established, and weaker where usage is fragmented by department (the more partial replacement progresses, the more cross-product data is lost and the more value can erode).

Structural position in the AI era: From apps toward the middle layer, targeting the “connection point” in an external-AI world

In an AI-driven world, TEAM’s positioning is less about “winning search and summarization” and more about staying core by connecting AI to a governed foundation of work data—complete with evidence trails, permissions, and auditability—even as external AI tools proliferate.

Structural elements (organized based on evidence)

• Network effects: not social-network-like; instead, operating standards become entrenched as tickets, documents, and intake accumulate. As connections with external AI clients build, switching costs can rise.
• Data advantage: context across request → execution → discussion → agreement → record persists, and AI accuracy tends to improve for customers with deeper operational usage.
• AI integration depth: move AI from convenience features toward the center (search, chat, agents, automation), with external tool connectivity as a premise. Governance features such as audit logs are also being strengthened.
• Mission-criticality: Jira and service management sit close to frontline operations that can’t easily stop. Documents and video are more exposed to standalone competition, and their importance increases when tied into integrated operations.
• Barriers to entry: less about algorithms and more about embedded operations, permissions, audit, and integrations. The push to offer external AI connectivity as a “standard connection port” aims to make phased/partial replacement harder.
• AI substitution risk: surface-level search and summarization can commoditize. Even if work shifts toward external AI, the question is whether Atlassian remains the underlying operational foundation.
• Position in the structural layer: today, the app layer is the main battlefield, but there is a move to increase the weight of the middle layer by providing connection points and governance. There are also reports of an acquisition agreement that brings the work entry path (an AI browser) into scope, which could push it further toward an OS-like position (though this is a transition point).

Management, culture, and governance: Founder-led strength creates both “consistency” and “fragility”

Atlassian’s north star is “enable every team to move work forward,” which aligns with the core idea of running tickets (audit trails), knowledge (search), and intake (processing) under one operating philosophy.

Changes in top leadership (not abrupt change, but a shift in center of gravity)

• Scott Farquhar (co-founder) stepped down as co-CEO, leaving the co-CEO role on August 31, 2024, and remaining as a director
• Thereafter, Mike Cannon-Brookes (co-founder) becomes sole CEO

The cleanest way to read this is not as a change in vision, but as a shift in the center of gravity—from co-governance to a single CEO.

Management style (a “pattern” inferred from public information and business alignment)

• Priorities: cloud-first experience and governance, integrated experience across multiple products, and making AI “assumed to be used” (adoption-first)
• What could be deprioritized (risk): excessive near-term defensiveness to stabilize accounting profits, and over-optimizing for winning single-function categories (which could blur the integration axis)

Persona → culture → decision-making → business strategy (linked causally)

A founder-led structure often creates strong mission consistency, but it can also make culture more sensitive to shifts in top-level decisions and personnel. In practice, that tends to favor decisions that prioritize integration (multi-product) and governance (enterprise requirements), and that move AI from the edge to the center—supporting a strategy that builds switching costs, while also introducing friction around bundling, Rovo adoption, and enterprise cloud migrations.

Generalized patterns in employee reviews (how to observe)

• Positive: flexible ways of working; a good fit for those aligned with the mission
• Negative (warning signals): reduced trust after layoffs and reorganizations, inter-team friction, and slower decision-making are frequently cited

If these patterns intensify, execution could weaken in areas that are not flashy but often decisive—migration support, admin experience, and support quality.

Executive turnover (observation points for adaptability and execution accountability)

• Planned President departure (2025年12月31日)
• CRO appointment (2025年1月1日)
• Planned CFO departure (2026年6月30日)

This cannot be treated as a definitive trigger for sudden cultural change. Still, leadership transitions while simultaneously pushing “enterprise go-to-market” and “AI/integration product execution” can influence priorities—how much to invest, and where to tighten—making it a reasonable monitoring point for long-term investors.

Fit with long-term investors (culture and governance lens)

• Good fit: investors who understand the power of software that embeds into operations, don’t rely solely on earnings multiples, and view AI as a competition for a governed work foundation with evidence trails and permissions
• Poor fit: investors who require near-term accounting profit visibility, and those who dislike periods when price changes and bundling appear to be the main drivers of growth

The “instrument panel” investors should have: Follow causality with a KPI tree

Because Atlassian can deliver revenue growth even when EPS is unstable, it’s risky to think you understand the business through any single metric. In causal terms: revenue is driven by customer count and revenue per customer (seats, tier mix, multi-product adoption); switching costs and differentiation are driven by depth of integrated usage and the stickiness of cloud migration; friction is reduced by support, migration assistance, and admin experience; and competitive durability is shaped by cash conversion efficiency and how investment is allocated.

Intermediate KPIs (Value Drivers)

• Growth in customer count (number of adopting companies)
• Expansion in revenue per customer (seats, higher-tier mix, multi-product adoption)
• Depth of cross-product usage (degree to which tasks + knowledge + intake run under the same operating model)
• Progress and stickiness of cloud migration
• Penetration of pricing and packaging design (bundling)
• Quality of support, migration assistance, and admin experience
• Cash conversion efficiency (ability for revenue to remain as cash)
• Continuity of investment in integration, AI, and migration support

Constraints: If these clog, growth slows

• Early-stage burden of building the “operating model” (workflow design, permission design, template build-out)
• Management becomes heavier as products increase (difficulty of operations and cost justification)
• Friction in cloud migration (compatibility, governance, existing operating realities)
• Intensifying competition within individual categories (local-optimization switching)
• If the integrated value experience is weak, cross-product data is missing (strengths erode)
• AI operating costs and external dependence can increase
• Organizational cultural volatility can affect execution
• There can be phases where profitability and cash-generation thickness do not return (asymmetry vs revenue)

Bottleneck hypotheses (Monitoring Points): What to watch to detect “drift” early

• Whether integrated value is being experienced on the ground (not reverting to a collection of standalone usage)
• Whether bundling is accompanied by expanded usage scope (not starting to look like a contract-form change)
• Whether cloud migration friction is slowing the pace of expansion
• Whether AI is stopping at search and summarization (whether it is entering execution such as ticket creation, classification, assignment, change management, and knowledge updates)
• Whether admin experience (permissions, audit, governance) is being maintained as a competitive win condition
• Whether support and migration assistance quality is deteriorating (including cultural factors)
• Whether the “smoothness” of profits and cash generation is improving (whether asymmetry vs revenue growth is becoming entrenched)

Two-minute Drill (summary for long-term investors): The backbone of the TEAM investment thesis

The core long-term question with Atlassian is whether it can remain not as a set of “convenient single-function tools,” but as a governed operational foundation where work evidence trails (tickets), knowledge (documents), and intake (service management) accumulate. Revenue has grown rapidly over both 10 and 5 years (revenue 10-year CAGR ~32.2%, 5-year CAGR ~26.4%), and FCF has expanded, while EPS has remained negative over the long term; even in the latest TTM, EPS is -0.72 dollars with YoY -45.8%, leaving profitability weak.

In the near term, revenue growth (TTM +20.1%) continues, while FCF is positive but down -8.4% YoY, and FCF margin (TTM 22.02%) is below the typical bands of the past 5 and 10 years. Put differently, the hybrid profile remains: growth persists, but the momentum and “thickness” of profits and cash are volatile.

The win path is clearing the heavy lift of cloud migration and enterprise governance, expanding cross-product usage through bundling, and pushing Rovo beyond search and summarization into execution (ticket creation, recommendations, automation)—strengthening the integrated experience. The lose path is data fragmentation from department-level partial substitution, failure to realize integrated value, bundling starting to look like life extension rather than adoption expansion, and weaker execution in migration support and admin experience due to cultural and execution volatility.