Asana
Sorbet currently classifies Asana as the dark_horse in its Dev work bucket. The detailed selection note is not yet available.
No recent material read
Based on 0 material signals in the last 30 days: 0 positive, 0 negative.
Evidence summary, not a buy / sell rating
Latest approved decision: hold · 2026-07-17
The role and pillars explain what job this holding has inside the System-of-Record basket—not whether it suits an individual investor.
Asana earns its dark-horse seat in the Dev Work bucket because its core data model is unambiguously records-first: every task is a durable, typed object carrying an owner, a status, a due date, dependencies, and a full edit history — the exact substrate an autonomous coding agent needs to read and mutate work state without ambiguity. That positions Asana firmly on Pillar 1 (records, not content) and Pillar 2 (state machine, not labels), since task transitions in Asana are explicit and enforced rather than inferred from free-text comment threads. The dark-horse designation reflects competitive reality — Atlassian and Linear own more of the developer-native surface today — but Asana's differentiation is its cross-functional reach: engineering work that touches design, marketing, and operations lives in Asana's graph, giving agents a wider ownership and dependency map than a pure dev-tool can provide. That breadth of durable records is precisely what makes Asana a structural bet rather than a momentum play: the more an organisation consolidates cross-team work into Asana's object model, the richer the substrate becomes for agent traversal. If agent adoption accelerates the consolidation of work onto fewer, cleaner SoR platforms, Asana's existing installed base of structured task graphs becomes a compounding moat rather than a commodity.
A smaller, higher-uncertainty paper position testing an emerging or less-consensus expression of the bucket thesis.
The thesis properties this holding is selected to test. These labels are portfolio classifications, not standalone proof.
Durable records
Explicit state machine
The thesis breaks for Asana specifically if one or more of the following structural conditions materialise, distinct from any share-price drawdown. First, if Asana fails to ship a credible agent-consumption SKU — one where autonomous agents read and write task records, state transitions, and dependency graphs via a stable API or MCP server — while peers like Atlassian and ServiceNow accelerate that monetisation, the company forfeits its P1/P2 positioning and becomes a UI layer without substrate status; watch for agent ARR remaining zero or immaterial in back-to-back earnings calls. Second, open-source SoR clones (Plane, OpenProject, or a well-capitalised fork) demonstrably erode Asana's pricing power in the SMB and mid-market segments that anchor its growth — the observable signal is sustained gross-margin compression below 85% alongside accelerating logo churn outside enterprise tiers. Third, Microsoft bundles comparable project-record functionality deeper into Teams and the M365 Copilot control plane at no incremental price, triggering a measurable shift in new-logo attach rates away from standalone Asana; the falsifying signal is two or more consecutive quarters of net new seat growth turning negative in the commercial segment. Finally, if a foundation-model provider ships a native task-record layer with enforced ownership, typed state transitions, and queryable audit history — satisfying P1 and P2 without Asana — the moat Asana relies on collapses at the substrate level, not merely the application layer. Underperformance relative to the basket, a soft guidance quarter, or a CEO transition alone would not constitute falsification under ADR 0016; only these structural breaks warrant an exit proposal.
Daily closes are shown for context. Reference levels are deterministic outputs of Sorbet's published ATR method, not analyst targets or advice.
2025-07-28 → 2026-08-31
$10.26
Short-term levels use 14d ATR and the 200d average. The 3y projection compounds the current revenue-growth rate with no multiple expansion. Missing inputs stay blank.
Revenue growth + FCF yield, not the conventional FCF-margin formulation. Visible for judgment, but not wired into selection.
The available history does not support a directional trend classification.
| Quarter | Revenue YoY | Gross margin | FCF margin | Operating margin |
|---|---|---|---|---|
| 2026-01-31 | 5.96% | 87.84% | 11.76% | -16.53% |
| 2025-10-31 | 5.57% | 88.90% | 6.68% | -34.81% |
| 2025-07-31 | 6.88% | 89.73% | 17.97% | -25.11% |
| 2025-04-30 | 4.99% | 89.73% | 2.13% | -23.44% |
| 2025-01-31 | 6.70% | 89.59% | 6.55% | -33.76% |
| 2024-10-31 | 6.66% | 89.23% | — | -32.73% |
Asana's trajectory in the agent economy hinges on whether it can extend its confirmed strengths in durable records (P1) and explicit state machines (P2) into the ownership and verifiability pillars the thesis demands — specifically, typed assignee fields with enforced permissions (P3) and a stable, machine-readable API surface that exposes every state transition back through time (P5). The company has built genuine structural cleanliness in how it models work — goals cascade into projects into tasks into subtasks, each with an owner and a status — but it has not yet demonstrated the kind of MCP-server or agent-callable verb layer that Atlassian shipped over Jira, leaving Asana a step behind on the control-plane narrative. To compound as substrate, Asana must ship a first-class programmatic interface that lets agents not just read task state but execute named domain verbs — complete, reassign, block, escalate — with auditable receipts, and it must do so before customers standardise their agent architectures around competitors who already have. What remains unproven is whether Asana's predominantly mid-market, cross-functional positioning translates into the kind of deep, permission-layered, developer-adjacent workflows that autonomous coding and ITSM agents actually touch — or whether its gravitational pull stays in the softer project-management layer where agent ROI is harder to measure and defend.
No material signals for ASAN in this period.
positive signal but thin coverage (only P5) — hold for confirmation.
Earnings in 1 day(s). Defer trim/add proposals through the print.
96.0%
Reviewed disclosure · quarter ending 2025-12-31