Competitive Intelligence · August 2026

Asana:
The Human-Agent Bet

An in-depth market analysis, product audit, technology deep-dive, PM critique, and mock product strategy document for Asana, Inc. — the work management incumbent rebuilding itself around AI Teammates while its core seat-based business shows the first cracks.

HEADQUARTERSSan Francisco, CA
FOUNDED2008
PAYING CUSTOMERS131,000+
STATUSPublic (NYSE: ASAN)
COVERAGEasana.com
$790.8M
FY2026 Revenue
9.5%
Q1 FY27 Rev. Growth YoY
96%
Trailing 4Q Net Retention
817
$100K+ Customers
2x
AI Studio ARR, QoQ
$75M
StackAI Acquisition

Who Is Asana, Today?

Asana was founded in December 2008 by Facebook alumni Dustin Moskovitz and Justin Rosenstein, who had built internal collaboration tooling at Facebook and Google, respectively, and set out to sell that "secret sauce" to every company. The product launched commercially in 2012 and the company went public via direct listing in September 2020 at a $5.5B valuation. For most of its life, Asana has been a founder-led, product-led, SMB-and-mid-market-heavy work management company that grew primarily through free-to-paid self-serve conversion and organic search.

That company no longer fully exists. Over an 18-month stretch from March 2025 to May 2026, Asana replaced its founder-CEO with an external enterprise-software operator, reframed its product identity around AI agents rather than task lists, and acquired an AI workflow-automation startup to fill a capability gap it could not build fast enough internally. This report treats FY2026–FY2027 as a distinct chapter: not the Asana of the 2020 direct listing, but a company mid-transition, betting its next decade on being the substrate — the "Work Graph" — that both humans and AI agents operate on.

Core Thesis Asana's technical asset (the Work Graph) is genuinely well-positioned for the agentic era — it is one of the few work management data models built as a graph rather than a flat list of tasks in containers. But its business model (per-seat licensing) is structurally exposed to the same AI agents it is now selling, and its historic growth engine (SMB self-serve via organic search) is exposed to AI-mediated discovery bypassing search entirely. The next 18 months will determine whether Asana out-runs its own disruption or gets caught by it.

Leadership & Corporate Structure

👤

Dan Rogers — Chief Executive Officer

Became CEO July 21, 2025. Previously CEO of LaunchDarkly (2023–2025) and President at Rubrik; earlier ran marketing at ServiceNow and Symantec, with stints at AWS, Microsoft, and Salesforce. Harvard MBA. Installed specifically for enterprise go-to-market experience and AI-era repositioning.

👤

Dustin Moskovitz — Co-Founder & Board Chair

Announced retirement as CEO in March 2025 (stock fell 25% on the news); transitioned to non-employee director and Board Chair effective July 2025. Remains Asana's largest individual shareholder and its public voice on AI safety and the future of work.

👤

Justin Rosenstein — Co-Founder

Built early collaboration tools at Google and Facebook before co-founding Asana. Stepped back from day-to-day product leadership years ago but remains closely associated with the company's mission-driven, "work about work" framing.

👤

Tony Rosinol & Bernard Aceituno — AI Leadership (via StackAI)

Co-founders of StackAI (Y Combinator W23), acquired by Asana in May 2026 for $75M. Now leading cross-system AI agent execution — the technical piece Asana lacked to move from AI suggestions to AI actions.

Asana reports roughly 1,700–2,300 employees depending on source and reporting date; the company does not break out AI/engineering headcount separately in public filings.

Evolution Timeline

2008
Founded by Dustin Moskovitz & Justin Rosenstein
Ex-Facebook and ex-Google engineers set out to productize internal collaboration tooling for every company.
2012
Commercial launch
Self-serve, freemium go-to-market becomes the primary growth engine for the next decade.
2020
Direct listing on NYSE
Lists at a $5.5B valuation without a traditional IPO — an unusual, founder-preference-driven structure.
2023–2024
Asana Intelligence and Work Graph enterprise push
First generation of AI features (smart fields, status summaries) layered onto the existing Work Graph data model; parallel investment in enterprise admin, security, and governance controls.
March 2025
Moskovitz announces retirement as CEO
Stock drops ~25% on the news — the market's clearest signal yet that it saw founder-led growth as running out of room.
July 2025
Dan Rogers becomes CEO
First outside CEO in company history. Enterprise GTM and AI-era product repositioning become the explicit mandate.
Winter–Spring 2026
AI Teammates and AI Studio ship broadly
Prebuilt, role-specific AI agents ("Campaign Brief Writer," "Bug Investigator," "Sprint Coach," and 18 others) and a no-code workflow builder for inserting AI steps into existing processes.
May 2026
Acquires StackAI for $75M
No-code AI agent-builder (YC W23) adds cross-system execution — agents that can act in Salesforce, Slack, and other tools, not just inside Asana. Framed by the company as building "the operating system for human-agent teams."

Industry Landscape & Competitive Positioning

Market Context — and a Caution About the Numbers

Third-party sizing for "work management software" is genuinely inconsistent: figures from different research firms for adjacent categories (work management, workspace management, workforce management) range from roughly $3.5B to $17.5B depending on what is bundled in and which year is used as the base. These categories are frequently conflated in vendor marketing and SEO-driven research content, and none of the major analyst firms appear to publish a clean, singular "work management software TAM" figure that is safe to cite without caveats. Treat any single TAM number in this space — including ones Asana itself might cite in investor materials — as directionally useful, not precise.

Category Crowding

Asana competes simultaneously against dedicated work management tools (monday.com, ClickUp, Smartsheet, Wrike), dev-centric platforms (Atlassian/Jira), knowledge tools expanding into PM (Notion), and bundled incumbents (Microsoft Planner/Project inside Microsoft 365).

Seat-Based Pricing Under Pressure

Industry-wide, seat-based pricing adoption fell from roughly 21% to 15% of SaaS vendors in twelve months, while hybrid (seat + usage/agent-based) pricing rose from about 27% to 41% over the same period, as AI agents begin substituting for human seats.

AI-Mediated Discovery

A growing share of software discovery now happens via AI chat answers rather than search-engine result pages — the same zero-click dynamic reshaping SEO-dependent businesses across categories threatens Asana's historically strong organic/self-serve SMB funnel.

Competitive Map

CompanyModelMoatAsana OverlapThreat
monday.comVisual, flexible "Work OS"Best-in-class onboarding UX, fastest time-to-value for non-technical teamsMid-market cross-functional work managementHIGH
ClickUpAll-in-one, feature-maximalist suiteAggressive pricing (~$7/user), 500+ AI agent "skills," power-user feature densitySMB and price-sensitive mid-marketHIGH
Atlassian (Jira + Rovo)Dev-centric PM + enterprise AI agent layerTeamwork Graph, deep developer-tool integration, enterprise incumbencyEnterprise cross-functional and technical teamsHIGH
Microsoft Planner / ProjectBundled into Microsoft 365Effectively free at the margin for existing M365 seats; Teams/Outlook integrationSMB and mid-market cost-sensitive buyersMEDIUM
NotionFlexible workspace / knowledge base expanding into PMBeloved UX, strong in documentation-heavy teams and startupsEarly-stage teams and knowledge-work overlapMEDIUM
Smartsheet / WrikeEnterprise-grade reporting and resource managementDeeper analytics, portfolio, and resource-management depth than AsanaEnterprise ops and PMO buyersMEDIUM
Zapier / OpenAI / Anthropic agent toolingHorizontal AI automation and agent-building platformsNot tied to any single system of record; can automate around Asana entirelyThe exact "cross-system agent execution" space StackAI was acquired to compete inMEDIUM

Industry Trends Shaping Asana's Fate

🤖

Agentic AI Is Cannibalizing Seat-Based Revenue

Across the SaaS sector, companies whose AI agents actually reduce headcount-per-workflow are starting to see net revenue retention fall below 100% as seat expansion turns negative even while logo retention holds. Atlassian has already shown this pattern. Asana is explicitly selling AI Teammates that do the work of a team member — the same pricing model it depends on for growth is the first thing its own product roadmap threatens.

🔍

SMB Discovery Is Moving Off Search

Asana's SMB and self-serve motion has historically leaned on organic search and word-of-mouth. As buyers increasingly ask AI assistants "what's the best project management tool for my team" instead of Googling it, top-of-funnel becomes a function of being recommended by someone else's AI — a channel Asana does not yet control or measure.

🏢

Enterprise Buyers Want Governed Agents, Not Autonomous Ones

Enterprise security and compliance teams are the gating factor on agent adoption, not capability. Asana's public AI framing — "context, checkpoints, and controls" — and its Asana Gov product for regulated buyers are a direct response to this, and are arguably better positioned for enterprise trust than more autonomy-forward competitors.

🧩

Consolidation of the "System of Record" Layer

As AI agents need a shared, structured substrate to reason over, the value is shifting from "which app has the prettiest board view" to "whose data model is rich enough to give an agent real context." This favors companies with genuinely graph-structured data — Asana's Work Graph, Atlassian's Teamwork Graph — over flatter competitors.

Key Success Factors in This Domain

Companies winning the next phase of work management need to execute on four fronts simultaneously:

Context-Rich Data Models

Flat task lists don't give AI agents enough structure to act reliably. Graph-based models that capture relationships between work, goals, and people are the prerequisite for trustworthy agent behavior.

Cross-System Execution

Agents that can only read and suggest inside one app are demos, not products. Real value requires writing back into Salesforce, Slack, email, and other systems of action.

Pricing Model Innovation

Vendors that cling to pure per-seat pricing while marketing labor-replacing AI agents create an internal contradiction buyers will eventually notice and negotiate against.

Distribution Beyond Search

SMB growth engines built on SEO and self-serve conversion need a second channel — agent marketplaces, AI-assistant integrations, or partner ecosystems — as AI reshapes discovery.

What Asana Actually Sells — and How It's Built

Asana's product is best understood in three layers: the work management core (the tiered SaaS product most customers buy), the Work Graph (the underlying data model that differentiates it technically), and the AI layer (AI Studio, AI Teammates, and the newly acquired StackAI execution layer) that the company is now betting its next chapter on.

Layer 1 — The Work Management Core

TierPriceWho It's ForKey Capabilities
PersonalFree (up to 10 users)Individuals, very small teamsBasic task and project tracking
Starter$10.99/user/moSmall teams needing structureTimeline, custom fields, automation rules
Advanced$24.99/user/moMid-market and cross-functional ops teamsPortfolios, Goals, Workload management
Enterprise / Enterprise+Custom (~$35+/user)Large orgs, regulated industriesSSO, SCIM, advanced admin controls, Asana Gov

Layer 2 — The Work Graph (Technology Deep-Dive)

Data Model
Graph-structured, not container-structured

Unlike flat list/board tools where a task lives in exactly one project, Asana's Work Graph treats tasks, projects, goals, people, portfolios, conversations, and files as nodes that can be "multi-homed" — a single task can belong to multiple projects and roll up to multiple goals simultaneously. This is architecturally closer to a graph database or object-oriented model than a traditional relational task list, and it is the single most defensible technical asset in Asana's stack.

Access Model
Declarative, object-oriented permissioning

Engineers reportedly define object properties and access-control rules in configuration files rather than imperative code, which lets Asana extend the graph (new object types, new relationship types) without re-architecting the permission system each time — relevant as AI agents become new "actors" that also need scoped, auditable access to the graph.

AI Studio
No-code AI workflow builder

Lets admins insert AI "nodes" into existing workflows — intake triage, compliance checks, prioritization — without writing code. This is the governance-forward, workflow-embedded counterpart to a general-purpose chatbot: AI that acts inside a process Asana already understands the structure of, rather than a standalone assistant bolted on top.

AI Teammates
Prebuilt, role-specific agents you @mention

A gallery of 20+ named agents — Campaign Brief Writer, Launch Planner, Copywriter, Competitive Market Researcher, Pricing Strategist, Status Reporter, Workflow Optimizer, Compliance Specialist, Bug Investigator, Sprint Coach, and others — scoped to specific functions (Marketing, Ops, IT) and buildable no-code for custom use cases. The framing is deliberately anthropomorphic: agents are "teammates," not features.

StackAI (Acquired May 2026)
Cross-system execution layer

StackAI's no-code agent-builder connects to external systems (Salesforce, Slack, Gsuite) and lets agents actually write back into them, not just read from them. This closes Asana's biggest previous gap: AI Teammates that could suggest and summarize but couldn't reliably act outside Asana's own walls. It also puts Asana in more direct competition with Zapier and the agent-tooling layers being built by OpenAI and Anthropic.

AI Strategy & Readiness Assessment Asana's AI strategy is more coherent than most incumbents': it is grounded in a real technical differentiator (the Work Graph as agent context), backed by actual revenue traction (AI Studio ARR more than doubled quarter-over-quarter), and reinforced by an acquisition that fills a specific, named capability gap rather than a vague "AI-washing" purchase. The governance-first "context, checkpoints, controls" framing is also a credible enterprise-trust play. The open question is not whether the AI product is real — it is — but whether Asana can monetize it fast enough to offset the seat-pricing pressure that its own AI Teammates create, and whether "15% of net-new ARR from AI" (management's own target) is enough to matter at Asana's current growth rate.

Recent Performance

📊

$790.8M FY2026 Revenue

Up roughly 9% year-over-year. Q1 FY2027 revenue of $205.1M grew 9.5% YoY, above the top end of guidance, with 88% gross margin.

📈

Non-GAAP Operating Margin: 7% → 11.5%

Improved from -6% in FY2025 to 7% for FY2026, then to 11.5% in Q1 FY2027 (+720bps YoY) — the clearest sign of Rogers-era operational discipline so far.

⚠️

$100K+ Customer Cohort Flat Sequentially

817 customers spending $100K+ annually, up 12% YoY but sequentially flat quarter-over-quarter — a yellow flag for the exact enterprise-expansion motion Rogers was hired to accelerate.

🔁

96% Trailing Net Retention

Below 100%, meaning the existing customer base is shrinking in dollar terms before new-logo growth is added back — improving (in-quarter NRR hit 97%, up for four straight quarters) but still a structural drag.

Who Asana Serves, and What It Solves for Them

Asana's 131,000+ paying customers span three broad tiers, each with a distinct problem, solution shape, and monetization profile. The tension in Asana's current strategy is that its historic strength (SMB self-serve) is its most AI-search-exposed segment, while its growth mandate (enterprise) is the segment where its newest AI capabilities are least proven at scale.

SegmentPlanProblem SolvedSolutionPerformance Signal
SMB / IndividualPersonal, StarterScattered tasks across email, chat, and spreadsheets; no shared source of truth for small teamsFree-to-low-cost task and project tracking with fast self-serve onboardingHistoric growth engine; now exposed to AI-mediated discovery bypassing organic search
Mid-Market Ops & MarketingAdvancedCross-functional visibility — who owns what, how it rolls up to goals, where bottlenecks arePortfolios, Goals, Workload, automation rules; increasingly AI Teammates for campaign and ops workflowsCore customer revenue (customers spending $5K+/yr) is 76% of total revenue, up 10% YoY — the durable middle of the business
Enterprise & RegulatedEnterprise / Enterprise+, Asana GovGovernance, security, and compliance requirements around who can see and act on sensitive work — now including AI agents as new "actors" needing scoped accessSSO, SCIM, admin controls, Asana Gov, AI Studio's governed workflow-embedded AI model817 customers at $100K+ ARR, up 12% YoY but flat sequentially — the segment Rogers was hired to scale, still finding its footing
The Segment Asana Doesn't Talk About: Reviewer Sentiment Across Capterra and G2 reviews, the most consistent complaints are a steep onboarding learning curve, feature and notification overload, automations that are "tough to use or stuck behind paywalls," and slow customer support response times. None of these are fatal, but they suggest the product's complexity — the same graph flexibility that makes it powerful — is also a real adoption tax, particularly for the SMB segment Asana most needs to defend.

Product Strategy Assessment: What's Real, What's Risk, What's Missing

Asana has done something genuinely rare for an incumbent SaaS company: it identified its own disruption thesis (AI agents reduce demand for per-seat software) before being forced into it by a competitor, and it reorganized leadership and M&A around addressing it. The critique below is about execution risk and internal contradiction, not strategic direction — the direction is broadly right.

⚠ Structural Risk
Asana Is Selling the Product That Undermines Its Own Pricing Model
AI Teammates are explicitly marketed as doing the work a human team member would do. If they succeed, the natural outcome is fewer human seats per workflow — exactly the dynamic already visible in Atlassian's NRR trend. Asana still prices AI Teammates and AI Studio largely as add-ons layered on top of per-seat plans rather than as a genuine alternative pricing axis. Every quarter this isn't resolved, Asana is asking its own sales motion to sell a product that shrinks the thing it gets paid for.
◈ Strategic Gap
No Visible Answer to AI-Mediated SMB Discovery
Asana's SMB growth has leaned on organic search and self-serve conversion for over a decade. As more buyers ask an AI assistant to recommend a project management tool instead of searching for one, Asana has no publicly stated strategy for being the answer an external AI gives — no GEO (generative engine optimization) program, no agent-marketplace presence, no MCP-style integration that would put Asana inside the answer surface itself. This is the same structural exposure that defines SEO-dependent businesses across categories, and Asana has not yet named it as a risk in investor materials.
◈ Execution Gap
Enterprise Expansion Is Stalling Right When It's Most Needed
Dan Rogers was hired specifically for enterprise go-to-market credibility. One year in, the $100K+ customer cohort grew 12% year-over-year but was flat sequentially quarter-over-quarter — a warning sign that the enterprise motion hasn't yet found traction, not proof of failure, but exactly the metric that should be under the most scrutiny over the next two to three quarters. If this doesn't inflect, the "enterprise CEO" hiring thesis itself comes into question.
⚠ Positioning Risk
"AI Teammates" Is a Crowded Claim, Not a Differentiated One
Atlassian Rovo, ClickUp Brain, monday Sidekick, and Notion AI all claim the same outcomes: agents that write status updates, summarize threads, and predict risks. Anthropomorphizing agents as "teammates" is a marketing choice every competitor in this space has independently made. Asana's actual differentiation has to be proven in outcome quality — grounded in the Work Graph's genuine structural advantage — not asserted through naming conventions that every rival uses identically.
✦ Opportunity
The Work Graph Is a Real, Underexploited Technical Moat
Most competitors (monday.com, ClickUp, Notion) are built on flatter, container-based data models. A graph structure where work, goals, and people are richly interconnected is precisely what makes an AI agent's context reliable rather than hallucinated. Asana talks about this in developer-facing content but does not yet market it aggressively as the reason its AI Teammates should be trusted more than a competitor's — this is a stronger, more defensible claim than "teammates," and it's underused.
✦ Opportunity
StackAI Closes the Right Gap, at the Right Time
Buying cross-system execution capability rather than building it from scratch was the correct call — it's a narrow, well-scoped acquisition (not a scattershot AI-washing purchase) that directly answers the most common critique of AI Teammates before StackAI: they could suggest but not act. The integration risk now is whether StackAI's founders and technology get fully absorbed into the Work Graph's permission and governance model, or remain a bolted-on layer that undermines the "checkpoints and controls" trust story.
◈ Leadership Risk
A Brand-New CEO With an Ambiguous Track Record on Turnarounds
Rogers' enterprise GTM pedigree fits Asana's stated needs, but independent management analysts have flagged that his prior company brought back its own founder as CEO shortly after his departure — a pattern worth watching, not dismissing. Combined with a founder who moved to Chairman rather than exiting entirely, Asana now has two very engaged, very different voices (an operational enterprise-GTM CEO and a mission-driven founder-chair) that need to stay aligned through a genuinely difficult pricing and product transition.

Strengths, Weaknesses, Opportunities, Threats

Strengths
  • Work Graph is a genuine structural differentiator vs. flat competitors
  • 131,000+ paying customers; 76% of revenue from core ($5K+) customers
  • Operating margin improving sharply — 7% FY2026, 11.5% Q1 FY2027
  • AI Studio ARR more than doubled quarter-over-quarter
  • StackAI acquisition closes a real, specific capability gap
  • Enterprise-credible new CEO with relevant GTM background
  • Governance-first AI framing resonates with security-conscious buyers
Weaknesses
  • 96% trailing net retention — below 100%, still net-shrinking existing base
  • $100K+ customer cohort growth stalled sequentially
  • Per-seat pricing model in direct tension with AI Teammates' value prop
  • Steep learning curve and feature/notification overload per user reviews
  • Automations reportedly hard to use or paywalled behind higher tiers
  • Slow customer support response times cited repeatedly in reviews
  • Leadership transition still less than 18 months old — unproven under pressure
Opportunities
  • Market Work Graph explicitly as "why our AI can be trusted"
  • Pioneer a genuine usage/outcome-based pricing tier ahead of forced adoption
  • Build GEO / agent-marketplace presence to defend SMB discovery
  • Fully integrate StackAI's cross-system execution into core governance model
  • Asana Gov as a wedge into regulated, high-trust enterprise buyers
  • Convert AI Studio's early ARR momentum into a durable second growth engine
Threats
  • AI agents compressing seat counts industry-wide — Asana especially exposed
  • AI-mediated discovery eroding the organic-search SMB funnel
  • Atlassian, monday.com, ClickUp all shipping comparable "AI teammate" claims
  • Microsoft Planner effectively free at the margin for M365 customers
  • Horizontal agent-building platforms (Zapier, OpenAI, Anthropic) could route around Asana entirely
  • Reported customer churn to competitors in some vendor data sets (directional, not confirmed at company level)

Product Strategy 2026–2028: From Task Manager to Trusted Agent Substrate

Document Type This is a mock product strategy document written from the perspective of a Senior PM/CPO at Asana. It is directionally grounded in real company data but represents analytical recommendations, not Asana's actual internal roadmap.
01

Strategic Vision & North Star

Vision: Asana becomes the trusted context layer every work-related AI agent — Asana's own, or a customer's, or a third party's — reasons over before taking action, because its Work Graph is the most reliable map of how work actually happens inside an organization.

North Star Metric: Agent-Verified Outcomes — the number of AI Teammate or AI Studio actions per month that are completed, cross-system, without human correction. This reframes success away from seats and toward outcomes, which is the only metric that survives a shift to usage-based pricing.

The Strategic Pivot: From "software you assign seats to" to "infrastructure you grant agents access to." This requires Asana to make peace with, and get ahead of, seat compression rather than treat it as a threat to be minimized in earnings calls.

02

Three Strategic Bets (2026–2028)

Bet 1: Launch a Genuine Usage-Based Pricing Tier — Before It's Forced

Rather than defend per-seat pricing until AI-driven seat contraction erodes it anyway, launch an opt-in "Agent Actions" pricing tier priced on verified AI Teammate task completions, sold alongside (not instead of) per-seat plans. This lets Asana capture revenue from customers who reduce headcount using AI Teammates, instead of losing that revenue outright.

Why This First Every quarter Asana delays, a competitor or the customer's own procurement team is more likely to force a worse version of this change — a straight seat-count renegotiation with zero new revenue capture. Pilot on the top 20 AI Studio customers in Q4 2026.

Bet 2: Make the Work Graph Externally Queryable (Open the Substrate)

Expose a governed, MCP-compatible API surface so that external AI agents — a customer's internal copilot, or a third-party agent from OpenAI or Anthropic's ecosystems — can query the Work Graph for context (with the same checkpoints-and-controls governance Asana already applies internally). This turns Asana from "an app that competes with agent platforms" into "the context layer agent platforms depend on," which is a far more durable position given how fast the agent-tooling layer itself is commoditizing.

Bet 3: Defend SMB Discovery With an Explicit GEO and Agent-Distribution Program

Stand up a dedicated function — mirroring the SEO discipline Asana already has — focused on being the recommended answer when a buyer asks ChatGPT, Claude, or Copilot "what project management tool should my team use." This includes structured content optimized for AI retrieval, and pursuing listing/integration in agent and assistant marketplaces as a first-class distribution channel, not an afterthought.

Why This Matters SMB and self-serve customers are 24% of revenue but likely the majority of new-logo volume that feeds the mid-market and enterprise pipeline over time. Losing this funnel to AI-mediated discovery would compound quietly for years before showing up in quarterly numbers.
03

Prioritized Initiative Roadmap

INITIATIVE
PRIORITY / TIMELINE
SUCCESS METRIC
Agent Actions Pricing Pilot
Usage-based tier for verified AI Teammate/AI Studio task completions, sold alongside seat plans.
P0 · Q4 2026
20 pilot accounts; 15%+ incremental revenue vs. seat-only baseline
StackAI Governance Integration
Fully absorb StackAI's cross-system execution into Work Graph's permission model.
P0 · Q1 2027
100% of StackAI-powered actions logged and auditable in Work Graph
GEO & Agent Distribution Program
Dedicated function for AI-mediated discovery; marketplace listings for major AI assistants.
P1 · Q1 2027
Measurable share of new SMB signups attributed to AI-assistant referral
Work Graph External API (MCP-Compatible)
Governed, queryable context layer for third-party agents.
P1 · Q2 2027
25+ verified third-party integrations consuming the API
Enterprise Land-Expand Reset
Diagnose and fix the sequential stall in $100K+ customer growth.
P2 · Q2 2027
$100K+ cohort resumes sequential growth for two consecutive quarters
Onboarding Simplification
Address the steep learning curve and feature-overload complaints from reviews.
P3 · 2027
Time-to-first-value cut by 30%; support ticket volume for onboarding down 25%
04

OKRs — 12-Month Targets (2026–2027)

O1: Prove Usage-Based Pricing Can Coexist With Seat-Based Revenue
  • KR1: Agent Actions pricing live with 20+ paying accounts by Q1 2027
  • KR2: Blended revenue per account up 10%+ for pilot cohort vs. seat-only comparison group
  • KR3: Net retention on pilot accounts exceeds company-wide 96% baseline
O2: Establish the Work Graph as External Agent Infrastructure
  • KR1: MCP-compatible API in general availability by Q2 2027
  • KR2: 25+ third-party integrations consuming the API
  • KR3: Zero governance/security incidents from external agent access
O3: Defend and Measure AI-Mediated SMB Discovery
  • KR1: Attribution system live for AI-assistant-referred signups by Q1 2027
  • KR2: Listed in top-tier marketplaces/plugins for at least 3 major AI assistants
  • KR3: SMB new-logo growth rate stabilizes or improves vs. FY2026 baseline
O4: Re-Accelerate Enterprise Expansion
  • KR1: $100K+ customer cohort grows sequentially for 2 consecutive quarters
  • KR2: Non-GAAP operating margin reaches 9.75%+ (FY2027 guidance) without sacrificing enterprise growth
  • KR3: Asana Gov reaches 10+ new regulated-industry logos
05

Key Risks & Mitigations

RiskSeverityLikelihoodMitigation
AI Teammates cannibalize seat revenue faster than usage-pricing can offsetHIGHMEDIUMMove Agent Actions pricing from pilot to general availability quickly; track blended revenue per account, not seats, as the core health metric.
AI-mediated discovery erodes SMB funnel before GEO program maturesHIGHMEDIUMStand up attribution and marketplace presence in parallel, not sequentially; treat this with the same urgency as historic SEO investment.
Enterprise expansion stall persists past Q2 2027HIGHMEDIUMRoot-cause the sequential flatness in $100K+ cohort now — pricing friction, competitive losses, or sales execution — before adding new enterprise initiatives on top of an unresolved base problem.
StackAI integration remains a bolted-on layer, undermining governance storyMEDIUMMEDIUMRequire all StackAI-powered actions to flow through Work Graph's existing permission and audit model before broad rollout, not after.
CEO/Chair alignment breaks down under pricing-transition pressureMEDIUMLOWFormalize decision rights between CEO and founder-chair explicitly for pricing and AI-product calls, given the unusual dual-leadership structure.
06

Strategic Don'ts (What to Stop or Avoid)

Don't market "AI Teammates" as the differentiator

Every competitor uses near-identical language. Lead with the Work Graph's structural advantage instead — it's a claim rivals with flatter data models genuinely cannot match.

Don't defer the pricing-model question another year

Waiting for AI-driven seat compression to show up clearly in NRR before acting means responding from a position of weakness instead of designing the transition on Asana's own terms.

Don't chase enterprise logos at the expense of SMB defense

Rogers' enterprise mandate is necessary but insufficient alone — if the SMB funnel that feeds the whole business erodes quietly, enterprise wins won't be enough to offset it.

Don't ship AI features faster than governance can absorb them

Asana's best current differentiation with enterprise buyers is trust and control, not raw agent capability. Outrunning that trust story with autonomy features would trade a real advantage for a commodity one.

The Verdict

Asana enters its second act with a genuinely rare asset for an incumbent: a technical foundation, the Work Graph, that is well-suited to the exact shift — AI agents needing structured context to act reliably — reshaping its entire category. Combined with a real acquisition (StackAI) that closes a specific gap rather than papering over one, and margin discipline that has moved faster than most analysts expected, this is not a company drifting through disruption. It is a company that saw the disruption coming and is actively restructuring itself around it.

The risk is not strategic misjudgment — it's execution speed against two clocks running simultaneously. One clock is the seat-based pricing model, which Asana's own AI Teammates are quietly working against every quarter a usage-based alternative isn't live. The other is SMB discovery, which is shifting away from the organic search channel Asana has depended on for over a decade, with no publicly visible replacement strategy yet. Both clocks are patient for now — NRR at 96% and $100K+ cohort growth at 12% YoY are not crises — but neither improves by waiting.

Dan Rogers was hired to run toward exactly this problem. The next two to three quarters — whether the $100K+ cohort resumes sequential growth, whether AI Studio's ARR momentum turns into a genuine second pricing axis, and whether StackAI gets meaningfully integrated rather than bolted on — will show whether Asana becomes the trusted substrate the agentic era needs, or a well-architected task manager that modernized its marketing faster than its business model.

Bottom Line Asana's technology is ahead of its business model. The strategy to close that gap is clear: price for outcomes, not seats; open the Work Graph as infrastructure other agents can trust; and defend SMB discovery with the same discipline that built the organic-search engine in the first place. The window to do this on Asana's own terms, rather than a competitor's or the market's, is roughly 18–24 months.

Sources: Asana investor relations (Q2 FY2026, Q1 FY2027 earnings releases and call transcripts), TechCrunch, Business Wire, CNBC, Stratechery, Paragon Intel / ManagementTrack, SoftwareReviews, TechTarget, Capterra, stockanalysis.com, industry pricing surveys on seat-based vs. usage-based SaaS pricing. Analysis as of August 2026. Some third-party vendor-data figures (e.g., customer churn/switching rates) are directional and not independently verified against Asana's own disclosures.