Announcing o11's backing from Y Combinator.](/content/blog/announcing-backing-from-y-combinator/index.html)

# AI for Asana

## AI that triages tasks where they live.

- Triage tasks and re-assign owners in place.
- Roll up portfolio status without manual writeups.

### o11 for Asana: an AI agent layer for cross-functional work

o11 is an AI execution layer that runs inside Asana. The agent triages tasks, rolls up project status, and cleans dependencies — without sending a PM into a side panel to translate a status note back into task edits.

If you have searched for **AI for Asana**, an **Asana AI agent**, or an **alternative to Asana AI** for actual workflow execution, the difference comes down to one question: does the AI summarize the project or move the project?

### What teams use o11 for in Asana

- **Task triage.** Re-assign owners, fix due dates, set sections, and clear stale tasks across busy projects in one pass.
- **Project status rollups.** Generate portfolio updates from real task and milestone data, not from a separate doc that goes out of sync.
- **Dependency cleanup.** Find broken or circular dependencies, propose fixes, and apply them across the project tree.
- **Cross-project handoffs.** Spin tasks out of meetings, briefs, and Slack threads into the right project, with the right custom fields populated.

### Why o11 differs from Asana AI

Asana AI ships in-product as smart fields, status summaries, and writing assistance. The execution still ends with a human editing the task, fixing the field, or moving the dependency. o11 is built to drive those edits. The chat is the control surface, Asana is where the work lands.

### Built for teams that live across systems

Asana is one part of a much larger stack — usually paired with Slack, GitHub, Jira, and a CRM. o11 is positioned to act across all of them. A planning meeting can become a set of Asana tasks, a Slack handoff to the design lead, a GitHub issue, and an updated portfolio status doc without anyone re-typing the same intent into four tools.

### Where Asana teams typically start with o11

- **PMs** with weekly task hygiene and milestone updates.
- **Marketing ops** with campaign briefs and intake-to-task conversion.
- **Client services** with onboarding plans and engagement rollups.
- **Cross-functional leads** with portfolio status and dependency maps.

### How o11 respects Asana permissions

The agent operates with the user’s own account. Project membership, team visibility, and field-level access apply exactly the way they do for that user in the UI. Nothing is bypassed. That is what makes o11 deployable in organizations that cannot trust a tool that runs as an over-privileged service account.

### FAQ

**How is this different from Asana AI?**  
Asana AI focuses on summaries and smart suggestions; o11 executes the task edits and rollups end-to-end.

**Who is it for?**  
PMs, ops, marketing, and any team running cross-functional work in Asana.