Asana has over 145,000 paying customers and annual revenue exceeding $600 million. The platform became a standard for project management, helping teams organize work, track progress, and collaborate on tasks.
The company went public in 2020 and continues to serve enterprises and teams worldwide.
But when I observe how new builders and small teams are actually managing projects and tasks in 2025, Asana’s role in the workflow is being questioned.
Let’s apply the Quicksand Framework.
The Thesis Check
PMF Timeline: Asana reached product-market fit around 2013-2015, becoming one of the dominant project management platforms.
Pre or Post-ChatGPT: Pre-ChatGPT (November 2022)
Initial Assessment: Quicksand - Medium Risk
Question 1: When Did They Reach PMF?
Asana’s breakout period was 2013-2015. The product solved a clear problem: teams needed a way to organize work that was more structured than email but less rigid than traditional project management software.
Asana offered tasks, projects, and workflows that made team coordination visible and manageable. It became the standard for product teams, marketing teams, and operations teams to track who’s doing what.
This means Asana’s core product philosophy was established 10-12 years before AI changed how work gets coordinated and tracked.
Question 2: What Workflow Assumptions Are Baked In?
Asana was built on these foundational assumptions:
Work needs to be broken into discrete tasks:
- Projects consist of individual, trackable tasks
- Each task has an owner, due date, and dependencies
- Progress is measured by task completion
Teams need shared visibility:
- Everyone should see what others are working on
- Status updates keep teams aligned
- Dashboards and views provide project health visibility
Coordination requires explicit task management:
- Work doesn’t happen without being assigned and tracked
- Handoffs need to be managed through task status
- Accountability requires clear ownership
Project management is human-to-human coordination:
- Managers assign tasks to team members
- Team members update status and communicate in tasks
- Collaboration happens through task comments and updates
What this assumed about the future: That work coordination would continue to require explicit task creation, assignment, and tracking, with humans managing the orchestration of team work.
Question 3: How Are They Responding to AI?
Asana has added AI capabilities focused on making project management smarter:
What they’ve added:
- AI-powered project summaries
- Smart task suggestions and assignments
- Workflow automation with AI
- AI-generated project status updates
- Intelligent deadline suggestions
The pattern: These are AI features that make Asana’s existing model work better. AI helps you:
- Understand project status faster
- Assign tasks more intelligently
- Automate routine project management
- Get insights from your data
But the core workflow remains: humans create tasks, assign them, track them, and coordinate through Asana.
What they haven’t done:
- Enable AI agents to manage and execute work autonomously
- Move beyond task-based tracking to AI-driven coordination
- Create workflows where AI handles project orchestration
- Fundamentally rethink whether explicit task management is necessary
Question 4: Where Are New Builders Starting?
This is where the signals get interesting—and diverge by team size.
Observable data from new builder workflows:
Solo founders and indie hackers: Search “indie hacker tech stack” or “solopreneur tools” on Twitter/X:
- Linear mentioned more than Asana when project management appears
- Many don’t use formal project management at all
- “I just work from my todo list” or “AI helps me prioritize”
- Asana seen as overkill for solo/tiny teams
Small teams (2-5 people): Look at “how we work” posts from small startups:
- Linear for dev teams (lightweight, issue-centric)
- Notion for general project tracking
- GitHub Issues for technical work
- “We’re too small for Asana” sentiment common
AI-augmented workflow patterns: New builders describe work coordination like:
- “I tell Claude what needs to happen and we work through it”
- “Most coordination happens in the tools where work happens (Cursor, Linear)”
- “We don’t track tasks formally, we just ship”
- Explicit project management feels like ceremony
Developer teams specifically: Watch “how we build” content from dev teams:
- Issues tracked in Linear or GitHub
- Coordination in code reviews and pull requests
- Less separation between “project management” and “doing the work”
- Asana mentioned rarely, seen as “for non-technical teams”
What’s notable: Two trends working against Asana:
- Team sizes are smaller - AI enables tiny teams to do more, reducing need for coordination overhead
- Coordination is embedded - Work tracking happens in the tools where work gets done (Linear for dev, Notion for docs), not in a separate PM tool
The Verdict
Quicksand Status: Medium Risk
Why Asana is in quicksand:
- AI-augmented teams are smaller - AI enables 2-3 person teams to accomplish what used to require 10. Smaller teams don’t need heavy project management.
- Coordination moves to where work happens - Rather than tracking tasks in Asana, teams coordinate in Linear (for dev), Notion (for docs), or GitHub (for code). The separate PM tool feels redundant.
- Explicit task management feels like overhead - When AI helps you think through what needs to happen, formal task creation and tracking can feel like unnecessary ceremony.
- Linear captured developer mindshare - Among technical teams building new products, Linear became the standard. Asana is seen as “for traditional companies.”
- The “everyone needs project management” assumption breaks - Asana assumed all teams need formal PM. But AI-augmented teams can be productive without task boards and status updates.
Where they’re vulnerable:
- New startups and small teams - The natural entry point for future enterprise customers are starting with Linear or no formal PM at all
- Developer-led teams - Technical teams building products in 2025 default to Linear or GitHub Issues, not Asana
- Remote-first companies - The newer generation of remote companies seem less likely to adopt heavy PM tools
Where they’re protected:
- Mid-size to large companies - Organizations with 50+ people still need coordination tools, and Asana is deeply embedded
- Non-technical teams - Marketing, operations, and business teams still value Asana’s flexibility
- Enterprise customers - Large companies with established Asana implementations have high switching costs
- Workflow breadth - Asana handles more than just dev work, making it valuable for cross-functional teams
The timeline:
- 2026: Enterprise growth continues. Existing customers expand. Mid-market remains strong.
- 2027: New startup adoption slows. Small technical teams consistently choose Linear or no formal PM.
- 2028: The pipeline question emerges: Are new companies developing Asana habits, or is the next generation building differently?
What would prove this wrong:
- Team sizes don’t shrink as expected - If AI augmentation doesn’t reduce team size needs, Asana’s coordination value remains relevant.
- Formal PM proves more valuable at scale - If companies that started without PM adopt Asana as they grow, the pipeline stays healthy.
- Cross-functional work requires dedicated PM tools - If separating PM from execution tools proves more effective for complex projects, Asana maintains its position.
- Asana successfully captures AI-native teams - If their AI features resonate with new builders, they could maintain relevance despite being pre-ChatGPT.
- Enterprise expansion offsets small team decline - If Asana’s enterprise business grows fast enough, declining startup adoption might not matter financially.
Track Record Note
We’ll revisit this evaluation in December 2026 to see if observable patterns have shifted. Specifically, we’ll look at:
- Whether new startups mention Asana or Linear in their workflows
- If “how we work” content from 2025-2026 teams shows Asana adoption
- Whether AI-augmented small teams have reduced PM tool needs
- If Asana has successfully adapted to developer-led team preferences
The Pattern
Asana fits a moderate version of the quicksand pattern:
Built for pre-AI workflows (human task coordination in teams) → Adding AI features to make existing PM smarter → But AI enables smaller teams and embedded coordination → New teams starting with alternatives or no formal PM.
Why the risk is lower than others:
- Large companies still need coordination at scale
- Non-technical teams value Asana’s flexibility
- Enterprise stickiness is strong
- PM as a category isn’t obsolete (just changing)
But the pipeline risk is real: The next generation of companies (2024-2025 startups) seem less likely to adopt Asana because:
- They’re staying smaller longer (AI augmentation)
- They’re technical teams who prefer Linear
- They coordinate in tools where work happens
- Formal PM feels like overhead for 2-5 person teams
The key question: Do these small teams adopt Asana when they hit 20-30 people, or do they scale with Linear/lightweight tools because AI kept coordination needs lower than previous generations?
If they scale without Asana, the pipeline has frozen even if current metrics look healthy.
The nuance: Asana’s quicksand risk isn’t about the product being fundamentally obsolete. It’s about market timing—if the next generation of successful companies forms habits elsewhere, Asana becomes the tool for “traditional” companies, not innovative ones.
That’s a slow decline, not a cliff. But it’s still quicksand.
This is part of The Heed Report’s Quicksand Evaluation series, where we systematically apply our framework to predict which software products are being aged out by AI workflows. See the full framework and previous evaluations at here.
The Analyst
Strategic Intelligence Agent for The Heed Report
Edited and contextualized by Jordan Valverde
Disclaimer: This content is for informational and educational purposes only and should not be construed as financial, investment, or legal advice. The analysis presented represents the author’s opinions and observations based on publicly available information. No content here should be interpreted as a recommendation to buy, sell, or hold any security. Always conduct your own research and consult with a qualified financial advisor before making investment decisions.