How does Asana make money in 2027?

The renewal meeting that explains the whole business model

Picture a 200-person marketing agency that adopted Asana in 2021 during the hybrid-work scramble. They started on a free workspace, hit the 10-user ceiling inside a quarter, and upgraded to what is now the Starter tier. By 2023 they needed Timelines for client campaign schedules and Forms for creative intake, so they moved to Advanced. Today they hold roughly 190 paid seats at list pricing near $24.99 per user per month on annual billing — call it $57,000 a year before whatever discount their account executive negotiated.

Now it is renewal week in 2027. The agency's operations lead has three tabs open. One is a ClickUp quote at roughly half the per-seat price. One is a Monday.com board demo their creative director built over a weekend. One is an email from IT noting the agency already pays for Microsoft 365, which bundles Planner, To Do, and Loop at no incremental cost. The Asana rep's job in that meeting is to prove that $57,000 buys something the free bundle does not.

This is the entire Asana revenue model compressed into one conversation, and it is why the company's growth curve looks the way it does. Every dollar Asana earns is a dollar a customer chose to spend on a category specialist instead of a bundled commodity. When the answer is yes, Asana books high-margin recurring revenue with gross margins around 90%. When the answer is no, the seats do not churn dramatically — they contract. The agency drops from 190 seats to 140, keeps the tool for the teams that genuinely depend on Goals and Portfolios, and Asana's net revenue retention slides another point.

That contraction dynamic, repeated across thousands of accounts, is the single most important fact about how Asana makes money. Net revenue retention peaked above 130% during the 2021 expansion cycle, when every existing customer automatically bought more seats each year and Asana barely had to sell. By fiscal 2024 that figure had compressed to roughly 100-105%. Revenue growth followed the same path: 67% in FY22, 45% in FY23, roughly 19% in FY24, then into low double digits and below. The product did not get worse. The expansion motion that used to do the selling for free simply stopped.

So the 2027 revenue question is not "does Asana have a business model." It plainly does — a clean, high-margin, recurring SaaS model that most software companies would envy. The question is whether the money comes from a customer base that grows on its own or from a sales organization that has to win each seat individually against cheaper and bundled alternatives. Asana has spent the last several years rebuilding around the second assumption, and every strategic move — Enterprise+, AI Studio, vertical templates, partner channels — is a response to it.

For any RevOps team studying this, the agency renewal is the whole case study. It shows where the revenue originates (seats), what threatens it (bundle math and price competition), and what defends it (feature depth that only matters above a certain organizational complexity).

How the money actually flows from free signup to enterprise contract

Asana's revenue engine is a product-led funnel bolted onto an enterprise sales motion, and the two halves work on very different economics.

The free Personal tier is the top of the funnel. It supports up to 10 collaborators with unlimited tasks and projects, list, board, and calendar views, and no time limit. It exists to acquire users at effectively zero marginal cost. Tens of millions of people have touched it. The conversion rate from active free user to paid seat runs in the low single digits over a twelve-month window, which sounds terrible until you multiply it against a base that large and account for a customer acquisition cost that lands in the low hundreds of dollars per seat.

Paid conversion typically happens on one of three triggers. The workspace crosses the collaborator limit. Someone needs Timeline or Gantt to communicate a schedule to a stakeholder. Or an admin needs a real permission model because the workspace now contains client data. Each trigger maps to a specific tier upgrade, which is the actual design intent behind the feature gating.

The Starter tier — around $10.99 per user per month annual, higher on month-to-month — unlocks unlimited collaborators, Timeline, basic Workflow Builder automation, Forms, and project dashboards. It is aimed at teams of roughly 10 to 50 and represents a meaningful slice of paid revenue but a small slice of dollars, because the seat counts are small.

The Advanced tier — near $24.99 per user per month annual — is where the money concentrates. It adds Goals for OKR tracking, Portfolios for program-level rollup, advanced Workflow Builder with multi-step rules, approvals, time tracking, advanced search and reporting, and the Asana Intelligence smart features. Goals and Portfolios are the specific features that make Asana defensible; they are what a VP of Operations needs and what a kanban board fundamentally cannot provide.

Enterprise and Enterprise+ are custom-priced, typically negotiated in the $25-$40 per-user-per-month range depending on volume and term. Enterprise adds SAML single sign-on, SCIM provisioning, audit logs, custom branding, service accounts, and a dedicated customer success manager. Enterprise+ adds data residency options, advanced data-loss-prevention controls, deeper audit capability, customer-managed encryption keys, and the compliance certifications regulated buyers require — SOC 2 Type II, ISO 27001 and its siblings, HIPAA configuration.

That last tier is the strategic bet. A 5,000-employee financial services firm running 1,200 Asana seats on Enterprise+ with data residency and CMEK is a $400,000 to $800,000 annual contract, and it is a contract Microsoft Loop cannot easily take away, because the buying committee's requirements are compliance requirements rather than feature requirements.

Underneath all of it sits the integration ecosystem — several hundred named connections including Slack, Microsoft Teams, Google Workspace, Salesforce, Adobe Creative Cloud, Figma, GitHub, Jira, Tableau, and the no-code connectors like Zapier and Power Automate. Asana charges nothing for these. They generate revenue indirectly, by raising switching costs. Once Asana is wired into a company's Slack notifications, Salesforce records, and Google Drive attachments, ripping it out becomes an operational project rather than a procurement decision, and that friction is worth real retention points at renewal.

Professional services is deliberately kept small — implementation, migration off Jira or Smartsheet or Microsoft Project, workflow design consulting, bundled CSM time at the top tier. Keeping it in the low single digits as a percentage of revenue protects the software gross margin and pushes implementation work to partners like Accenture, Deloitte, and Slalom, who in turn source enterprise pipeline back to Asana.

The numbers that define the 2027 revenue picture

Start with the disclosed history, because it frames everything. Asana went public in September 2020 through a direct listing on the NYSE at a $27 reference price. Revenue climbed from roughly $76 million in FY18 to $143 million, $227 million, $379 million, $548 million, $653 million, and roughly $724 million in FY24. The growth rates attached to those figures — 88%, 59%, 67%, 45%, 19%, 11% — are the real story. That is a decay curve, not a plateau, and it does not fully reverse in any credible 2027 scenario.

The customer metrics tell the same story from a different angle. Paid customer count grew from roughly 50,000 to over 150,000 organizations. Customers spending more than $5,000 per year grew from a few thousand to over 20,000. Customers above $100,000 per year reached the several-hundred range. The absolute counts keep rising; the growth rate of spend per customer is what compressed.

Gross margin sits around 90%, which is excellent and stable — Asana's cost of revenue is hosting, support, and the professional services line, and none of those scale linearly with seats. The problem was never gross margin. It was operating expense. Sales and marketing consumed roughly 64% of revenue at the FY22 peak, an unsustainable figure that only made sense when every dollar spent returned expanding cohorts. Two rounds of workforce reduction — roughly 5% in late 2022 and roughly 9% in early 2023 — plus hiring restraint brought that ratio toward 50%, with continued pressure to reach the low 40s.

R&D runs in the high-20s to low-30s as a percentage of revenue, with the largest single allocation going to AI. GAAP operating losses remained substantial through FY24, driven heavily by stock-based compensation, while adjusted operating margin and free cash flow moved toward and across breakeven. That distinction matters: Asana can be free-cash-flow positive and GAAP-unprofitable simultaneously, and in 2027 that is the likely state.

For unit economics, the ranges practitioners should hold in mind: inbound product-led acquisition costs a few hundred dollars per seat and pays back inside a year. Mid-market outbound costs a few thousand dollars per seat with payback closer to two years. Enterprise field sales costs five figures per customer with payback stretching past two years, offset by much larger and stickier contracts. The blended payback of roughly two to two-and-a-half years is workable but well behind best-in-class enterprise SaaS.

A reasonable FY27 base case: revenue somewhere in the $900 million to $1.1 billion range, growth in the 10-15% band, adjusted operating margin positive in the single digits to mid-teens, free cash flow solidly positive, and net revenue retention hovering around 100-105% with the $100,000-plus cohort running meaningfully higher, near 110-115%. The bull case requires AI monetization to break out and Enterprise+ to compound, pushing growth back toward 20%. The bear case is flat-to-single-digit growth with net retention slipping below 100% — actual dollar contraction — which is roughly what a mid-single-digit revenue multiple already implies the market expects.

One more number worth internalizing: the market capitalization has spent recent years around the $4 billion mark, against a 2021 peak many multiples higher. Asana trades at a revenue multiple well below both the SaaS peer median and Monday.com's. That gap is the market's stated opinion on the durability of Asana's revenue, and no amount of product narrative changes it until net retention does.

The trade-offs behind every pricing decision

Asana faces three pricing squeezes at once, and each one forces a genuine trade-off rather than a clean answer.

The first squeeze is discount competition. ClickUp's paid tiers sit meaningfully below Asana's for broadly comparable feature breadth, and ClickUp ships features quickly. For an SMB or a mid-market team without compliance requirements, the price gap is hard to argue away. Asana's options are to cut price and destroy the margin that makes the business work, to hold price and lose the price-sensitive segment, or to justify the premium through depth in Goals, Portfolios, Workload, and reporting. Asana has chosen the third path, which means deliberately conceding parts of the low end.

The second squeeze is bundle math, and it is the harder one. An enterprise already paying Microsoft in the range of $50-plus per user per month for a premium 365 package with Copilot gets Planner, To Do, and Loop at no incremental line item. Adding Asana at $30-plus per user per month on top means the CIO must defend a multi-million-dollar incremental spend at scale. The honest differentiators exist — cross-functional workflows that span outside the Microsoft tenant, Goals and Portfolios capability that Planner simply does not have, external collaborator support, and deep non-Microsoft integrations with Adobe, Figma, Salesforce, and Slack. Whether those justify the incremental spend depends entirely on how much genuine cross-functional program management the organization does. For a company whose "projects" are task lists, the bundle wins. For a company running a regulatory transformation portfolio across a dozen business units, it does not.

The third squeeze is AI pricing, where Asana made an unusual bet. Rather than adding a flat per-seat AI surcharge like the $30-per-user-per-month model Microsoft uses for Copilot, Asana built AI Studio around consumption credits — customers get an allotment by tier and buy more as agents execute work. The trade-off is real in both directions. Consumption pricing is more honest: customers only pay when the AI does something, which lowers the barrier to adoption and avoids the shelfware problem that plagues flat AI surcharges. But it introduces forecasting anxiety. A procurement team that cannot answer "what will this cost us next year" will cap spend defensively, and every sales rep and CSM has to teach credit economics before the revenue materializes. Consumption revenue also recognizes less predictably than seats, which public-market investors dislike.

There is a fourth trade-off that sits above the other three: who controls the company. Asana operates under a dual-class share structure that gives co-founder and CEO Dustin Moskovitz voting control disproportionate to his economic stake. He co-founded Facebook before starting Asana in 2008 with Justin Rosenstein, and he has repeatedly bought Asana shares on the open market. The practical effect on the revenue model is patience. A conventionally governed public company with this growth profile would face intense pressure to cut R&D, maximize near-term margin, or sell. Asana can fund a multi-year AI and enterprise bet through a period of decelerating growth. That is a genuine strategic asset — and also a genuine risk, because it removes the external forcing function that would otherwise demand the company confront a failing strategy quickly.

Where operators get this wrong

The most common mistake is reading Asana's revenue model as a growth story when it is a retention story. Practitioners evaluating the company — as an investment, an acquisition target, a vendor, or a case study — fixate on new logo counts and total customer growth. Those numbers still look fine. Net revenue retention is the metric that actually determines the revenue trajectory, because in a per-seat business the existing base is the growth engine. When net retention was 130%, Asana grew 60% with modest sales effort. At 100%, every point of growth must be manufactured by the sales organization at full customer acquisition cost. Watch net retention and the $100,000-plus customer cohort; ignore headline logo counts.

The second mistake is treating the free tier as a marketing expense rather than a revenue mechanism. It is not charity, and it is not a loss leader in the retail sense. The free workspace is where product qualification happens — usage patterns identify which accounts are ready to convert, at what tier, and on what trigger. Kill or over-restrict the free tier and you do not save money; you starve the cheapest acquisition channel and push all customer acquisition onto sales reps whose payback period is two to three times longer. The correct discipline is to gate features that correlate with organizational complexity — collaborator count, Timeline, permissions, admin controls — rather than gating basic usability.

The third mistake is misjudging the bundle threat in one direction or the other. Some analysts treat Microsoft's inclusion of Planner and Loop as an extinction event; others dismiss it because those tools are less capable. Both readings are wrong. The bundle does not kill Asana; it caps Asana's addressable market at the segment where project complexity genuinely exceeds what a bundled kanban board can handle. That is a real and defensible segment — regulated industries, multi-business-unit portfolios, cross-company collaboration, creative operations with heavy non-Microsoft tooling — but it is smaller than the segment Asana served during the free-money expansion years. Planning revenue against the larger number produces exactly the disappointment Asana has been posting.

The fourth mistake is expecting AI revenue to arrive on a software timeline. Consumption-priced AI does not convert like a feature upgrade. It requires the customer to redesign a workflow, measure a result, and then decide to buy more credits. That is a services-paced motion wearing a product's clothing. Organizations that budget for AI revenue as though it behaves like a seat upsell consistently miss, then over-correct by discounting credits, which destroys the pricing model's central virtue. The right expectation is a slow ramp measured in quarters, gated by enablement capacity rather than product capability.

The fifth mistake is ignoring geographic concentration. Asana derives roughly 70% of revenue from North America, which is more concentrated than peers like Monday.com or Atlassian. That is simultaneously a weakness — one macro environment drives most of the revenue — and an unexploited opportunity. But international expansion is not a marketing campaign. It requires localized sales teams, local-language product quality, regional compliance certifications under GDPR and equivalent regimes, local data residency, and local-currency billing. Each market takes eighteen to thirty-six months before meaningful revenue. A company in cost-discipline mode structurally underinvests here, which is why the concentration persists.

The last mistake is assuming a controlling founder guarantees a good outcome. Voting control protects independence and enables patience. It does not produce net revenue retention. If the base case plays out — modest growth, positive cash flow, stable retention — patient capital is exactly right. If the bear case plays out, that same control structure means the market cannot force a correction, and the resolution comes only when the founder decides it should, whether that is a private-equity partnership, a strategic sale, or another several years of grinding independence.

What a RevOps team should actually take from this

Strip away the ticker symbol and Asana is a clean teaching case in per-seat SaaS mechanics, which is why it is worth studying regardless of whether you use the product.

First, feature gating is revenue architecture, not packaging trivia. Asana's tiers are not arbitrary bundles; each gate corresponds to an organizational threshold. Collaborator limits gate team size. Timeline gates stakeholder communication. Goals and Portfolios gate multi-team programs. SAML and audit logs gate IT governance. Data residency and encryption keys gate regulated industries. Build your own tiers the same way — find the moment a customer's organization changes shape and put the gate there. Gates placed on arbitrary usage counters generate resentment; gates placed on organizational maturity generate upgrades.

Second, the expansion engine and the acquisition engine have completely different unit economics, and conflating them destroys forecasting accuracy. Asana's product-led motion and its field sales motion differ by roughly an order of magnitude in cost per seat and by years in payback period. When expansion revenue is strong, blended metrics look great and hide how expensive new acquisition really is. When expansion softens, the true cost surfaces all at once. Model the two separately from day one so you know which engine is actually carrying the number.

Third, net revenue retention is the leading indicator and everything else is lagging. Revenue growth, market multiple, sales efficiency, and hiring plans are all downstream of whether the existing base expands or contracts. Instrument it by cohort, by segment, and by contract size — Asana's overall figure of roughly 100-105% obscures a large-customer cohort running near 110-115% and a long tail contracting below that. The aggregate number tells you very little; the spread tells you where to invest.

Fourth, integration depth is a retention product, not an engineering nicety. Asana gives away hundreds of connectors and earns the return in renewals. Count how many of your customers' other systems you touch, and treat that count as a retention forecast. The customers wired into five of your integrations churn at a fraction of the rate of the customers wired into none.

Fifth, when you introduce consumption pricing alongside seat pricing, budget for enablement as a first-class cost. The pricing model is only as good as the customer's ability to forecast against it. Every AI Studio-style motion needs credit calculators, ROI templates, and a CSM conversation before the first invoice — otherwise procurement caps spend defensively and the elegant pricing model produces less revenue than a crude surcharge would have.

Finally, know which fight you are in. Asana is not losing to a better work-management tool; it is competing against a free line item inside a suite the customer already bought. That is a fundamentally different competitive problem than feature parity, and it demands a different answer — depth the bundle cannot economically replicate, compliance the bundle cannot certify, and cross-boundary collaboration the bundle is not architected for. Any specialist facing a platform vendor's bundle needs to identify that defensible ground explicitly, price to it, and stop trying to win the segment where the bundle is genuinely good enough.

Related questions

Does Asana make more money from small teams or large enterprises?

Large customers dominate the dollars. Although Asana has well over 150,000 paying organizations, the customers spending above $5,000 annually — roughly 20,000-plus of them — and the several hundred spending above $100,000 drive the majority of revenue and nearly all the growth.

Is Asana profitable in 2027?

On a GAAP basis, likely not — stock-based compensation keeps reported operating results negative. On an adjusted operating margin and free cash flow basis, the company has guided toward and reached positive territory. Both statements can be true at once, which is common in public SaaS.

How does Asana's AI monetization compare to competitors?

Asana charges for AI Studio through consumption credits allocated by tier, rather than a flat per-seat surcharge like Microsoft's Copilot pricing. Credits are more customer-friendly and lower the adoption barrier, but they convert to revenue more slowly and forecast less predictably than seat-based AI fees.

What would break Asana's revenue model?

Net revenue retention falling durably below 100%. At that point the installed base shrinks in dollars every year, and Asana must acquire new revenue faster than it loses existing revenue just to stay flat — at full sales cost, with no product-led tailwind.

Why does Asana trade at a lower multiple than Monday.com?

Growth rate and retention. Monday.com has grown substantially faster with stronger net dollar retention and better international mix. Multiples price expected forward growth, so a durable gap in growth and expansion translates directly into a durable gap in revenue multiple.

FAQ

What percentage of Asana's revenue comes from subscriptions?

The overwhelming majority — roughly 85-90% of total revenue is per-seat subscription fees across the paid tiers. Professional services accounts for a low single-digit percentage, kept deliberately small to preserve software gross margins near 90%. AI-related revenue is growing but remains a modest slice, and the integration ecosystem generates no direct revenue at all.

How much does Asana cost per user?

List pricing runs roughly $10.99 per user per month for Starter on annual billing and near $24.99 for Advanced, with month-to-month pricing meaningfully higher. Enterprise and Enterprise+ are custom-quoted, typically negotiated in the $25-$40 range depending on volume, contract length, and required security features. Real enterprise deals routinely land well below list after volume and multi-year discounts.

Is the free tier actually free forever?

Yes. The Personal tier supports up to 10 collaborators with unlimited tasks, projects, and messages, plus list, board, and calendar views, with no trial expiry. It exists as the product-led acquisition channel. The economics work because acquisition cost is near zero and even a low single-digit conversion rate against a very large free base produces meaningful paid revenue.

Why did Asana's growth slow so much?

Three forces compounded. Net revenue retention fell from above 130% to roughly 100-105% as customers stopped automatically adding seats. Price competition from lower-cost alternatives capped the low end. And bundled project tools inside Microsoft 365 and similar suites removed the easy incremental purchase. None of these are product-quality problems; all of them are market-structure problems.

Does Asana's dual-class structure affect how it makes money?

Indirectly but significantly. Voting control concentrated with co-founder Dustin Moskovitz means Asana can sustain a multi-year investment in AI and enterprise capability through a period of decelerating growth without facing the activist or takeover pressure a conventionally governed company would. It also means no external party can force a strategy change if the current one is not working.

What should I watch to know if Asana's model is working?

Net revenue retention first, especially within the $100,000-plus customer cohort. Then the growth rate of that large-customer count, which measures whether the upmarket motion is compounding. Then sales and marketing as a percentage of revenue, which measures whether growth is getting cheaper or more expensive to buy. Headline customer counts and total revenue are lagging indicators of all three.

Sources

• https://investors.asana.com/
• https://asana.com/pricing
• https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&company=asana&type=10-K&dateb=&owner=include&count=40
• https://ir.monday.com/
• https://www.nyse.com/quote/XNYS:ASAN
• https://asana.com/product/ai
• https://developers.asana.com/docs
• https://www.microsoft.com/en-us/microsoft-365/planner
• https://clickup.com/pricing
• https://asana.com/company

Related on PULSE

• How does Monday.com make money in 2027?
• What is net revenue retention and why does it matter?
• How do SaaS companies price AI features?
• What is product-led growth and when does it stop working?
• How do you defend against a platform vendor's bundle?
• How does Atlassian make money in 2027?