Asana (ASAN) Q1 2027 Earnings Transcript

Asana reported Q1 revenue of $205.1 million, up 9.5% year over year and above the high end of guidance, while non-GAAP operating margin expanded 720 bps to 11.5% and adjusted free cash flow reached $34.4 million. AI adoption is accelerating: AI product bookings were 17% of net-new ARR, in-quarter NRR improved to 97%, and AI Studio customers showed the strongest retention and expansion trends. Management also announced the $75 million upfront acquisition of Stack.ai, raised Q2 revenue guidance to $213 million-$215 million, and reaffirmed FY27 revenue growth of 8.2%-9.2% with at least 9.75% operating margin.

Analysis

The key change is not the headline growth rate; it is the mix shift toward products that raise switching costs and expand wallet share. If AI Studio and teammates are already pulling customers into higher-seat, higher-retention behavior, the next-order effect is that Asana is no longer just a workflow seat vendor but a control layer that can defend pricing and improve net expansion even in a sluggish IT spend environment. Stack.ai matters because it moves the company from task orchestration inside a system of record to orchestration across systems of action, which is where budget ownership starts to migrate toward operations, AI transformation, and governance teams rather than traditional collaboration buyers.

The market is likely underestimating how much of the upside is now coming from retention quality rather than logo adds. That matters because retention-inflected re-acceleration tends to show up with a lag in revenue but almost immediately in RPO quality, multi-product attach, and the willingness of larger customers to expand into adjacent use cases. The second-order winner is the enterprise AI workflow ecosystem around Asana: implementation partners, systems integrators, and potentially adjacent data/governance vendors benefit if Stack.ai becomes the bridge between collaboration and enterprise automation stacks.

The biggest risk is execution dilution, not demand. This story requires product integration, packaging, and field enablement across three motions at once; if that creates sales friction, the company could end up with more product breadth but no faster conversion, especially while PLG remains a headwind. Another risk is that AI functionality gets rapidly commoditized by larger platform vendors, forcing Asana to prove that its differentiated work graph and multiplayer governance actually command premium willingness to pay over the next 2-4 quarters.

For trading, this is a better relative-long than an absolute chase. The cleanest expression is long ASAN versus NOW or WDAY on the thesis that an AI-native workflow layer can re-rate before the incumbents fully translate their agent narratives into measurable retention lift. Near term, the risk/reward favors call spreads rather than outright stock because the next catalyst is the June events plus Q2 commentary, but the guide implies management is still sandbagging AI contribution; upside should come if the company can raise FY27 AI attach assumptions without a margin reset.

Key Decisions for Investors

• Go long ASAN vs short WDAY in a 3-6 month pair trade: thesis is Asana’s AI-driven NRR improvement can inflect faster than a larger incumbent’s re-acceleration; stop if ASAN fails to widen RPO/NRR metrics next quarter.
• Buy ASAN Jan-2027 call spreads on pullbacks: use a defined-risk structure to express a 6-12 month re-rating if AI Studio/teammates convert into higher ARR productivity without a major margin hit.
• Take profits selectively if ASAN rallies into the June investor event: the near-term setup is catalyst-driven, so upside is best monetized before the market demands proof on Stack.ai integration and AI monetization.
• Watch CRWV and FDX as secondary beneficiaries: both are proof points for enterprise AI workflow adoption; if their own commentary shows deeper Asana usage, it supports a broader adoption theme and can be used as sentiment confirmation for ASAN longs.
• Avoid chasing MSFT on this print: the incremental read-through is that specialized workflow orchestration can coexist with platform AI, which is mildly negative for bundled collaboration narratives if ASAN keeps demonstrating better ROI in mission-critical use cases.