Asana (ASAN) Q2 2027 Earnings Call Transcript

Asana reported fiscal Q2 revenue of $216.4 million, up 10% year over year and above guidance, while non-GAAP operating margin expanded roughly 300bps to 10.1%. AI Studio and AI Teammates generated 25% of net new ARR, exceeding the prior 15% full-year target, prompting management to raise its AI-product target to 20%; $100,000-plus customer count grew 16% and NRR improved to 98% for core and large customers. However, management guided Q3 revenue to $217 million-$219 million, or 8%-9% growth, and maintained FY2027 revenue guidance of $858.5 million-$863.5 million amid PLG weakness, a $1.2 million consumption-transition timing headwind, and roughly 150bps of second-half gross-margin pressure from AI infrastructure and StackAI.

Analysis

ASAN’s investable debate is no longer whether enterprise demand is stabilizing; it is whether AI monetization can outrun a structurally weakening self-serve funnel without eroding the legacy SaaS margin model. The embedded-AI rollout deliberately exchanges near-term revenue visibility and gross margin for usage data and renewal leverage. That makes the next two quarters poor evidence of product-market fit: the relevant proof point is whether seeded users convert to paid overages and whether enterprise NRR exceeds 100% by FY28.

The key second-order risk is competitive compression. ASAN is moving into service management, client workflow, and engineering orchestration against entrenched vendors such as NOW, CRM, TEAM and Atlassian’s broader suite; its cross-sell thesis requires the work graph to be a meaningful switching-cost asset, not simply a feature layer that incumbents can replicate. Lower AI delivery costs could create operating leverage, but the company has also assumed model-routing risk: a rise in inference intensity, unreliable request-based pricing, or customers exhausting included usage without conversion would turn the launch into a gross-margin subsidy.

Near-term consensus may reward the improving enterprise metrics and modest beat, but the more material catalyst is delayed until post-launch cohort data and renewal behavior emerge over 1-3 months. The contrarian view is that reported growth deceleration may be close to trough if PLG deterioration truly stops and revenue-recognition timing unwinds; however, this is only bullish if deferred revenue/RPO and paid consumption accelerate together rather than merely reflecting enterprise contract duration.

Falsification: reduce exposure if core/large-customer NRR fails to reach 99% over the next two reports, gross margin remains in the mid-80s after launch costs normalize, or FY28 growth guidance does not reaccelerate despite the packaging transition rolling off. A worsening PLG drag beyond management’s stated range would also indicate that ICP retargeting is masking a broader digital-demand problem.

Key Decisions for Investors

• Watch, do not chase ASAN immediately: initiate a tactical long only after the mid-September launch produces evidence of paid consumption conversion or October event commentary confirms stable PLG bookings. Target a 3-6 month holding period; upside requires FY28 revenue reacceleration, while downside is a de-rating if AI mix lowers gross margin without lifting NRR.
• For existing ASAN longs, retain a defined risk limit through the next earnings report: trim if enterprise NRR remains below 99% or if gross-margin guidance falls below the mid-80s exit-rate implied by management. These are the cleanest indicators that AI is cannibalizing economics rather than expanding wallet share.
• Consider a relative-value basket long ASAN / short a broad legacy collaboration-software proxy only after paid AI overage data is disclosed; avoid treating the current AI ARR mix as equivalent to recurring, high-margin subscription ARR. Missing data: conversion of included requests to incremental purchases, request gross margin, and cohort-level renewal uplift.
• Monitor NOW, CRM and TEAM product launches and AI pricing over the next 6-12 months. A bundled agentic-workflow response from these platforms would weaken ASAN’s multiple-expansion case because its adjacent-product TAM depends on consolidation wins, not standalone feature adoption.