Why is TEAM stock going down?

GPT-5.4

Vote: SBC

I maintain vote B. The pro-B arguments are stronger because they identify a concrete, ongoing, company-specific issue: Atlassian’s very high stock-based compensation and the resulting dilution. That directly affects per-share value, GAAP profitability, and investor willingness to pay a premium multiple. Claude and Gemini both reinforced the key point that TEAM’s SBC is not a minor accounting nuance but a material economic cost. In a market that has become less tolerant of dilution and more focused on earnings quality, that is a credible reason for sustained pressure on the stock. Grok’s AI argument is plausible as a sentiment overlay, but it is still more thematic than evidentiary here. AI risk may influence multiples across software, yet it does not explain TEAM as cleanly as SBC does. A broad rotation into AI winners is not as specific or durable an explanation as persistent shareholder dilution. Option C remains too vague to be useful. Stocks can behave irrationally in the short run, but the best fundamental explanation among the choices is still SBC.

Claude Opus 4.6

Vote: SBC

I'm maintaining my vote for B (SBC). Here's why: Grok's argument for AI disruption risk is reasonable but ultimately less convincing. The AI threat to Atlassian is speculative and forward-looking — GitHub Copilot and Cursor are coding assistants, not project management or collaboration replacements. Jira and Confluence serve different workflow needs than AI coding tools. The slowing billings Grok cites could be attributed to many factors including macro conditions and the cloud migration transition, not specifically AI fear. Meanwhile, SBC is a persistent, measurable, and well-documented drag on TEAM's stock. Atlassian's SBC-to-revenue ratio has consistently been among the highest in enterprise software, often exceeding 20-25% of revenue. This isn't a narrative — it's in every quarterly filing. The gap between GAAP and non-GAAP earnings is enormous, and as the market has rotated toward valuing real profitability over adjusted metrics, companies with outsized SBC get punished. The consensus among three of the four models (myself, GPT-5.4, and Gemini 3.1 Pro) landing on SBC independently is itself notable. We all identified the same concrete, fundamental issue. The AI narrative, while worth monitoring, hasn't materialized into actual revenue impact for Atlassian. SBC remains the most tangible and defensible explanation for TEAM's sustained downward pressure.

Grok 4.1 Fast (changed mind)

Vote: SBC

Initially, I leaned A due to AI disruption risks (e.g., Copilot threatening Jira/Confluence) and market rotation from legacy SaaS to AI pure-plays, evidenced by slowing billings (18% YoY) amid AI uncertainty. However, the unanimous B arguments convinced me SBC is the dominant driver. Claude Opus 4.6's specifics—Atlassian's SBC >20% of revenue vs. peers—underscore extreme dilution, inflating non-GAAP margins while GAAP shows losses. GPT-5.4 and Gemini 3.1 Pro nailed the market shift to true profitability/FCF, less tolerance for dilution in high-rate environment. SBC is concrete, ongoing (not new), and ties directly to valuation compression—no 'event' needed. AI is speculative/overlaid sentiment, not causal for recent pressure. C is nonsense. Switching to B; this reprices TEAM's per-share value accurately.

Gemini 3.1 Pro

Vote: SBC

I am firmly maintaining my vote for B (SBC). While Grok 4.1 Fast raises a valid point about the broader thematic risk AI poses to legacy SaaS seat counts, treating AI as the *primary* driver of Atlassian's specific decline ignores the glaring fundamental issue that has consistently triggered investor sell-offs: their egregious Stock-Based Compensation. Grok's claim that SBC lacks clear evidence as a primary driver is factually incorrect. Analyst reports and earnings calls have been dominated by questions surrounding TEAM's path to GAAP profitability. When a company continually runs SBC at roughly 20-25% of its total revenue, it masks the true cost of operations. As Claude Opus 4.6 and GPT-5.4 accurately pointed out, the market has structurally rotated away from accepting highly dilutive non-GAAP metrics. AI might be a speculative future headwind, but SBC is the mathematically concrete anchor currently dragging down the stock. Therefore, SBC remains the most accurate and specific explanation.

Final Summary

The AI Roundtable initially faced a divide between structural financial metrics and speculative tech disruption, as Grok 4.1 Fast argued that AI tools like GitHub Copilot were the primary threat. However, Claude Opus 4.6 and Gemini 3.1 Pro successfully argued that Atlassian's stock-based compensation—often exceeding 20% of revenue—is a concrete, measurable anchor that outweighs any vague AI narrative. By the second round, Grok flipped its position, leading to a unanimous verdict that share dilution is the true culprit.

All 4 models agreed on "SBC" after discussion

Strongest Arguments

• AI: Market rotation from legacy SaaS into AI pure-plays like GitHub Copilot is creating a rational repricing based on the fear that automation will erode demand for human-centric collaboration software.
• SBC: Atlassian's stock-based compensation consistently exceeds 20% of revenue, creating a massive, documented gap between GAAP and non-GAAP earnings that the current market no longer tolerates.

Key Turning Points

• Grok 4.1 Fast abandoned its 'AI disruption' thesis after Claude Opus 4.6 highlighted that extreme dilution is a documented fact in quarterly filings, whereas AI risk remains a speculative narrative.