When optimizing performance, should Asana focus on enterprise users or consumers?
How to think through Asana's enterprise versus consumer resource allocation when performance optimization is on the table.
This post is for our Paid Subscribers. If you haven’t subscribed yet,
Clarifying Questions
Before diving in, I would want to align on scope, since “optimizing performance” could mean product performance (speed and reliability), business performance (revenue growth and margin), or overall strategic focus, and the enterprise-versus-consumer tradeoff differs substantially depending on which specific performance dimension is actually under consideration.
Should “performance” here refer to product technical performance specifically, or broader business growth and revenue performance? This distinction matters enormously because a technical performance question would push toward infrastructure investment affecting both segments simultaneously, while a business growth question requires a deliberate resource allocation choice between two meaningfully different strategic paths with different economics.
Should I assume Asana currently serves both segments with roughly comparable investment, or is one segment already the clear operational priority? If enterprise is already receiving the majority of resources, this becomes a question of how much further to tilt the allocation rather than whether to tilt it at all, and that changes the urgency and risk profile of the recommendation.
Is this a near-term resource allocation question covering the next one to two quarters, or a longer-term strategic identity question that would shape Asana’s product roadmap and go-to-market organization for the next three to five years? The answer changes the depth of organizational transformation required and the appropriate pacing for any transition.
Are there any external constraints, such as an upcoming fundraise, a specific revenue milestone commitment, or a recently announced competitive threat, that should shape how quickly Asana can execute this kind of strategic shift? Constraints like these would influence whether a fast reallocation or a phased transition is the more appropriate recommendation.
For this answer I will interpret this as a broader business growth and strategic resource allocation question. I will assume Asana currently serves both segments but has not yet made a fully explicit strategic prioritization choice, and I will treat this as a longer-term strategic identity question given how significantly it would shape the company’s product, sales, and go-to-market direction over the next three to five years. My recommendation will be that Asana should focus primarily on enterprise users.
Product Description
Asana was founded in 2008 by Dustin Moskovitz and Justin Rosenstein, both early Facebook engineers, and went public on the New York Stock Exchange in September 2020 via a direct listing. The company operates as a cloud-based work management and project collaboration platform serving a remarkably wide range of customers, from individual freelancers using its free tier to Global 2000 enterprises running complex, cross-functional programs across thousands of seats. As of its most recent fiscal year, Asana reported approximately 139,000 paying customers and generated roughly 725 million dollars in annual recurring revenue, with customers spending 5,000 dollars or more annually numbering around 21,000 and representing a disproportionately large share of total revenue. This concentration at the top of the account size distribution is one of the clearest signals in the company’s own disclosed financials that enterprise economics already dominate its revenue base even if its user count is still heavily skewed toward smaller accounts.
Asana competes in a crowded work management software category that includes Microsoft Project, Monday.com (which went public in 2021 and now exceeds 900 million dollars in ARR), Notion, ClickUp, Jira, and to some degree Slack and Microsoft Teams for lighter-weight coordination use cases. Its core differentiators have historically been its clean, opinionated UI, its workflow automation capability (Asana Rules and Timeline), and its integrations with over 200 third-party tools including Salesforce, Slack, Google Workspace, and Microsoft 365. Enterprise customers require substantially deeper capability in three specific areas: SOC 2 Type II and ISO 27001 security certifications, administrative controls like custom roles and data residency options, and SSO and SCIM provisioning for large identity management environments. Asana’s Business and Enterprise tiers, priced at roughly 25 dollars and 30-plus dollars per user per month respectively, target this segment directly. The free and Premium tiers (approximately 11 dollars per user per month) serve the individual and small team consumer-style segment. The strategic tension at the center of this question is whether continued investment in a broad, multi-tier product serving both segments simultaneously is the right resource allocation, or whether a sharper enterprise focus would compound faster and more defensibly given where the revenue concentration already sits.
Define Goal
The core problem is that continuing to invest comparable resources across both the consumer and enterprise segments risks diluting Asana’s focus and producing a product that serves neither segment’s specific needs as well as a more clearly prioritized competitor could. In a category where Monday.com, Notion, and ClickUp are all aggressively spending on product and marketing, Asana cannot afford the strategic ambiguity of trying to be the best tool for individual freelancers and the best tool for Fortune 500 program management simultaneously.
The goal I want to focus on is accelerating enterprise account revenue growth and net revenue retention while preserving the lightweight individual user tier only insofar as it demonstrably feeds the enterprise pipeline through validated bottom-up adoption patterns.
My proposed north star metric is net revenue retention (NRR) among enterprise accounts spending 50,000 dollars or more annually, measured quarterly. I define enterprise NRR specifically as the percentage of prior-period enterprise revenue retained and expanded through upsells and seat additions in the current period, excluding new logo revenue. I prefer this metric over total ARR growth because total ARR growth can be flattered by adding many low-value small accounts, which is exactly the dilution risk this recommendation is trying to avoid. I prefer it over gross revenue retention alone because NRR captures the expansion dynamic that is the most valuable characteristic of a well-embedded enterprise deployment. An NRR above 120 percent among this cohort would signal that Asana’s enterprise focus is compounding efficiently; a decline toward or below 100 percent would be an early warning that enterprise customers are not finding enough value to expand.
User Segmentation
Large enterprise organizations (1,000-plus employees) requiring sophisticated administrative, security, and integration capability: typically IT-driven or PMO-driven purchasing decisions with multi-year contract structures, average contract values above 50,000 dollars annually, meaningful switching costs once embedded across multiple departments, and high retention stability when the product is genuinely integrated into core workflows. This segment has the highest lifetime value and the most defensible competitive position given the organizational inertia required to displace an embedded work management platform.
Mid-market companies (100 to 999 employees) with moderate organizational complexity and moderate willingness to pay: typically department-level buying decisions rather than enterprise-wide IT mandates, average contract values in the range of 10,000 to 40,000 dollars annually, meaningful but more moderate switching costs, and moderate retention stability. This segment often represents an important stepping stone toward eventual enterprise-wide expansion and is worth serving as a secondary priority within an enterprise-focused strategy.
Individual users and very small teams (fewer than 10 people) using Asana primarily for personal or lightweight team task organization: average revenue per account well below 1,000 dollars annually, the highest price sensitivity of any segment, and the most intense competitive pressure from free or near-free alternatives like Notion’s free tier, Trello, and ClickUp’s free plan. This segment’s primary strategic value is not its direct revenue contribution but its potential as an organic seeding mechanism for eventual enterprise expansion within larger organizations.
I would focus primarily on large enterprise organizations as the strategic priority, because the combination of higher revenue per account (often 50 times or more the revenue of an individual account), stronger retention and expansion dynamics, and genuine competitive defensibility through switching costs represents the most strategically valuable growth opportunity available to Asana given its current competitive position.
