Asana B2B GTM Evolution

This is a B2B go-to-market analysis of Asana, Inc., examining how the company evolved from organic bottom-up adoption into a structured sales organization, where the existing model still falls short, and what an updated GTM design could look like to support enterprise traction at scale.

Asana built its early growth engine on something genuinely differentiated: a product so easy to adopt that individual teams signed up, expanded organically, and routinely reached 50–100 user accounts before the sales team noticed. By 2019, that strength had become a problem. Two-thirds of Asana's high-usage accounts had never been touched by sales. Bottom-up adoption was generating real revenue, but enterprise-scale deals remained rare — and with an IPO on the horizon, the lack of a repeatable enterprise motion was a credibility risk for public-market investors who wanted to see structured, predictable growth alongside the product-led story.

The strategic question is not whether Asana's product works — it does — but whether the company can design a sales organization that matches the actual journey customers take through the product, rather than the deal sizes those customers happen to land at.

The Growth Problem at Asana

By 2019, Asana's growth signal was strong but unevenly distributed. Adoption was explosive across teams and individual contributors. Two-thirds of high-usage accounts had never been engaged by sales. Sales targets were being met, but enterprise-scale deals — the kind of multi-hundred-seat MSAs that define category leaders in B2B SaaS — remained rare. With IPO plans intensifying, the pressure was building for a scalable, predictable, repeatable enterprise motion that the existing organization could not yet produce.

The deeper structural issue: Asana's sales organization, before the 2017 revamp, treated all accounts the same regardless of size or maturity. A 10-person sales team with no variable compensation (base + equity only), minimal marketing support, no outbound motion, and follow-ups limited to product-qualified leads (PQLs). Revenue split was roughly 50% self-serve and 50% sales-assisted, but the sales-assisted side was reactive — high-touch on small accounts, untouched on large ones. A reported 58% of sales effort was allocated to deals under 15 seats, while many enterprise opportunities sat dormant.

This is the kind of problem that doesn't show up in the topline numbers right away. Revenue was growing. But the shape of that revenue — small deals, high cost-to-serve, no enterprise traction — was not the shape that a 2020 IPO would reward.

What Oliver Jay Built (2017–2019)

Oliver Jay joined and built what is now the canonical "online revenue engine" structure for product-led B2B companies. The sales motion was segmented along four lines:

• Self-Serve. Convert freemium users with minimal rep involvement. A/B testing, automation, and segment-specific flows handled the conversion logic that previously required manual effort.
• Inbound. Handle high-conversion MQLs (marketing-qualified leads) through real-time chat, email support, and structured onboarding flows.
• Core. Medium-size deals (15–100 seats) handled by reps doing structured outreach and fast-velocity selling.
• Solutions. Large and enterprise deals (100+ seats) handled by senior reps doing strategic engagement and managing long sales cycles.

Several innovations were quietly important. MQLs converted at 30% versus PQLs at just 5% — a 6x ratio that shifted Asana's qualification and routing logic away from product signals alone toward marketing-qualified intent. Segment-specific onboarding journeys reduced time-to-first-value. Live chat and email support were added at points in the funnel where conversion was friction-bound, not awareness-bound. And the company began tracking "graduation potential" — early signals that an account might evolve from self-serve into a multi-team or enterprise customer.

The structural approach worked. Sales scaled to roughly 30 reps. Conversions and revenue from freemium to paid both improved. But large deals remained rare, and enterprise traction was still limited.

This is the point where most B2B SaaS analyses would conclude that the segmentation worked and just needs more time. The argument here is different: the segmentation worked at the level of deal size, but it doesn't match how customers actually move through Asana's product. Deal size is a lagging indicator. The customer journey is the leading indicator. Aligning sales motion to the journey, not to the deal, is the next move.

SWOT

Before recommending the new model, it's worth being explicit about Asana's position relative to where this would land.

The SWOT clarifies the strategic framing: Asana doesn't have a product problem or a demand problem. It has a motion design problem. The model below is built around that diagnosis.

Value Proposition

Before redesigning the motion, the value proposition has to be sharp. The version that emerged from this analysis:

For cross-functional business teams at growing companies — typically 5 to 500 employees — who struggle with scattered workflows, unclear responsibilities, and inefficient status tracking, Asana offers a simple, scalable work management platform that brings structure and clarity to everyday execution. Unlike traditional project management tools that require top-down configuration or IT support, Asana is designed for team leads, operations managers, and project owners to launch and manage their workflows autonomously, with built-in visibility, accountability, and integrations from day one. Asana empowers teams to go from siloed chaos to coordinated progress, without losing speed.

The four pillars that operationalize this value proposition:

• Clarity and visibility. Unified platform for tracking work. Reduces chaos. Transparency across teams without micromanagement.
• Accountability and collaboration. Task ownership, deadlines, and dependencies. Makes work actionable and measurable.
• Frictionless onboarding. No IT involvement needed. Self-serve to freemium to paid, with a low learning curve.
• Scales from teams to enterprise. Starts with a single user or team. Grows into cross-functional adoption with integrations and goals.

The fourth pillar — scales from teams to enterprise — is the one the existing GTM motion does not adequately serve. Pillars one through three are about getting customers in. Pillar four is about getting them to grow with you. The recommendation below addresses that gap directly.

The Customer Journey: Seed → Land → Expand → Explode

Asana customers move through a recognizable progression, and the motion design should map to it.

• Seed. Individuals or small teams sign up. No IT involvement. Use cases are task tracking and team coordination.
• Land. Team-level adoption (5–25 users). Shared goals, timelines, and integrations come online. Internal champions emerge.
• Expand. Cross-functional usage begins. Need for admin controls, workflows, and reporting grows. Teams across operations, marketing, and product onboard.
• Explode. Org-wide deployment. Visibility, compliance, and automation become non-negotiable. Executive buy-in and procurement involvement enter the picture. Often tied to MSA negotiation.

Each stage has distinct buyer behaviors, distinct conversion mechanics, and distinct risks. A sales motion organized by deal size assumes the rep skills required at each stage are interchangeable. They are not. The rep who excels at converting Seed-to-Land does so through fast educational selling and live-support fluency. The rep who excels at Expand-to-Explode does so through executive alignment and procurement navigation. These are different jobs, and conflating them in a single sales motion produces consistent under-performance at the high-value end.

Recommendation: A Journey-Based GTM Model

Replace deal-size segmentation with three customer-stage teams, each with its own sales motion, KPIs, and incentive structure.

Each team specializes in one transition. Each team owns a clear set of KPIs tied to that transition. Each team's compensation aligns with the metrics that define success at its stage. The handoff points between teams are explicit and instrumented, not implicit and inferred.

Pros

• Aligned with customer behavior. Reps match buyer needs at each stage rather than at each deal size. The customer experiences a coherent progression of relationships rather than a hand-off based on contract value.
• Encourages specialization. Each team masters stage-specific playbooks, objection handling, and KPIs. Reps build deep expertise rather than shallow breadth.
• Improves conversion and graduation rates. Faster time-to-value at the Land stage. Stronger MSA pipeline development at the Expand-to-Explode transition.
• Supports scalable, repeatable growth. A clean narrative for IPO investors: each stage has owners, metrics, and a documented motion.
• Creates internal career paths. Reps can grow from Land roles into Explode roles, providing a structured advancement story that improves retention.

Cons

• Sales rep resistance. Restructuring is friction, especially when current reps are comfortable in the existing model. This is real and must be managed explicitly.
• Handoff complexity. Leads can fall through the cracks unless transitions are well-instrumented. CRM stages, shared dashboards, and explicit handoff protocols are required.
• Unproven at scale. Few precedents exist for this model outside of Atlassian. Asana would be partly inventing the playbook in public.
• Role ambiguity at edges. The boundary between Land and Expand (and between Expand and Explode) needs to be defined sharply, or reps will compete for the same accounts.

The cons are real but each has a known mitigation, addressed in the implementation plan and risk-mitigation sections below.

Implementation Plan

A phased rollout reduces execution risk and produces evidence before national commitment.

Months 1–3: Pilot

• Run a small-scale pilot in the San Francisco office with 50 accounts.
• Train Land, Expand, and Explode teams with hypothesis-based handoff protocols.
• Set up KPIs for each team — graduation rate, expansion percentage, MSA close rate.
• Weekly syncs and a qualitative feedback loop to surface friction early.

Months 4–9: Refine and Enable

• Analyze pilot data. What's working? Where are handoffs breaking?
• Scale to additional regions (East Coast, EMEA).
• Build internal playbooks and training materials grounded in pilot insights.
• Adjust compensation structure to introduce variable incentives tied to expansion milestones.

Month 10+: National Rollout

• Roll out the journey-based model org-wide.
• Update Salesforce pipeline stages to match Seed → Explode.
• Launch an enablement hub for new hires.
• Executive alignment work and internal success-story communication to lock in cultural support.

The phasing is conservative on purpose. The goal is to produce evidence before the model has to defend itself in front of skeptical reps, leadership, or (eventually) public-market investors.

KPIs for Success

Each team needs metrics that match its job, not generic sales metrics applied uniformly.

The Land team optimizes for activation. The Expand team optimizes for adoption depth. The Explode team optimizes for organizational commitment. None of these are deal-size metrics.

Risk Mitigation

Four risks dominate the transition. Each has a known mitigation.

The most important mitigation is the simplest: a real pilot with real accounts and real metrics, before the model is asked to defend itself across the entire organization.

Competitive Context

Asana's recommended motion has to land in a market with active competition. The competitive frame matters because the GTM redesign isn't just internal — it's a positioning move against Atlassian, Notion, Monday, ClickUp, and Smartsheet, each of which has a different structural advantage.

• Atlassian is deeply integrated with software development workflows and preferred by engineers. Strong dev-led adoption, weaker cross-functional reach.
• ClickUp is hyper-customizable with one-platform-replaces-everything positioning. Strong in feature breadth, weaker in clarity of use case.
• Notion has flexible documentation and note-taking, adopted bottom-up by creators and startups. Strong organic growth, weaker structured-execution muscle.
• Smartsheet has a familiar spreadsheet-like interface that appeals to Excel-native enterprise users. Strong in enterprise procurement, weaker in modern UX.
• Monday offers a modern UI with collaborative, dynamic project views. Strong UX positioning, weaker in deep workflow.

Against this set, Asana's defensible position is: team-agnostic and cross-functional from day one, prioritizing structured workflows and simplicity, and best-in-class for work management with strong partner integrations rather than trying to be a jack-of-all-trades. The journey-based GTM model reinforces that positioning by selling the way customers actually adopt — across teams, across functions, into the org — rather than the way deals happen to size.

Conclusion

Asana's bottom-up GTM DNA fueled incredible adoption, but growth had plateaued by 2019 in the dimension that mattered most for IPO credibility: enterprise traction. The 2017–2019 segmentation revamp was structurally important, but it segmented by deal size rather than by customer journey, leaving the high-value Land-to-Explode transitions under-served.

A phased rollout of a journey-based GTM model — Land, Expand, and Explode teams aligned with customer stages — addresses the gap directly. With the right enablement, KPI design, and incentive structure, Asana can convert user love into enterprise traction and tell a compelling, repeatable growth story to public-market investors.

This is not just a sales structure recommendation. It's a recommendation about how to design a company that grows with its customers, which is the question public markets will increasingly ask of every product-led B2B company that wants to graduate from PLG narrative to enterprise credibility.

Presentation

18 images

Strategic Takeaways

A few takeaways extend beyond Asana specifically:

Deal-size segmentation is a lagging proxy for customer-stage segmentation. Most B2B SaaS sales orgs segment by ARR thresholds because ARR is easy to measure. Customer stage is harder to instrument but more predictive of which sales motion actually closes the deal. The orgs that figure out stage-based segmentation early get a structural advantage.

The PLG-to-enterprise transition is a motion-design problem, not a marketing problem. Companies often try to solve the enterprise traction gap by adding outbound, hiring senior reps, or launching enterprise marketing campaigns. Those help, but the deeper issue is usually that the existing motion wasn't designed for the enterprise stage. Until the motion is redesigned, the inputs don't compound.

Pre-IPO companies are evaluated on the shape of growth, not just the rate. Two B2B SaaS companies growing at the same rate can be valued very differently if one has a repeatable enterprise motion and the other doesn't. Public-market investors increasingly underwrite the motion, not just the metrics.

Specialization beats generalism in scaled sales orgs. Reps optimized for one stage of the customer journey will outperform reps asked to operate across all stages, because the skills required at Seed-to-Land and Expand-to-Explode are genuinely different. The organizational cost of specialization (more roles, more handoffs) is usually less than the cost of mediocre execution at the high-value end.

Asana's case is, in this sense, a clean illustration of how a successful product-led company has to redesign its sales organization to match its customers' actual progression — and how that redesign becomes the bridge between PLG growth and enterprise credibility in the public markets.