Asana vs Notion

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Notion
   Asana✓fullprobed8/10

   A probe confirms Asana serves a live llms.txt at developers.asana.com/llms.txt with markdown-append instructions for docs pages, directly enabling agent-native doc consumption, and this sits alongside a full REST API reference, OpenAPI spec repo, and API explorer. Missing for 10: independent/community confirmation of agents actually using llms.txt in practice, and a discoverable OpenAPI JSON endpoint (probe found 404s on standard paths, mitigated by the GitHub-hosted spec).

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.asana.com/llms.txt # Asana Docs Documentation > Documentation for Asana Docs Append .md to …”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”

   proof ↗⚑ flag

   Notion✓fullprobed9/10

   Notion's developer docs site directly serves an llms.txt file (confirmed via live probe returning HTTP 200 with structured markdown links to docs), plus a full OpenAPI spec and agent-oriented MCP guides, meaning an AI agent can be pointed at these agent-native resources to discover and use Notion's API. Missing for 10: independent third-party corroboration that agents actually consume this llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.notion.com/llms.txt # Notion Docs - [Overview](https://developers.notion.com/guides/get-star…”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
   • [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Notion
   Asana~partialclaimed6/10

   Asana exposes a token-authenticated REST API with webhooks and rule-based automation, enabling scripted/headless interactions suitable for CI-like automation (asana-docs-1, asana-docs-2, asana-docs-15, asana-docs-16, asana-docs-17). However, there is no explicit documentation of CI/CD integration, CLI tooling, or headless execution patterns tailored for automated pipelines. missing for 10: explicit CI/CD examples, dedicated CLI or headless runner, evidence of automated pipeline usage beyond generic API/webhook mentions.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”

   proof ↗⚑ flag

   Notion✓fullprobed8/10

   Notion's REST API plus personal access tokens explicitly target 'scripts, CLI workflows, Workers, and tools' and internal connections use static API tokens 'ideal for custom automations and workflows,' which directly supports headless/CI usage; an OpenAPI spec and llms.txt further confirm programmatic access. Missing for 10: an explicit CI/CD pipeline example or independent hands-on report of running Notion API calls in a CI environment.

   • [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Asana—none0/10

   Evidence confirms Asana publishes an official MCP server (asana-probe-3), meaning Asana exposes its own tools to other MCP clients — but the story asks the reverse: whether a user can plug external MCP servers into Asana so its AI (e.g., AI Teammates/AI Studio) can consume their tools. No evidence pack item describes Asana's AI agents acting as an MCP client or supporting configuration of external MCP servers as tool sources.

   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion—none0/10

   All MCP evidence describes Notion exposing an MCP *server* so external clients (Claude Code, Cursor, Codex) can pull Notion's tools in — the opposite direction of the story, which asks whether Notion itself can plug in external MCP servers to use their tools. No evidence shows Notion's AI/agent features consuming third-party MCP servers as a client.

   • [claimed-docs] “Build an MCP client that connects to Notion MCP using OAuth 2.0 with PKCE.”
   • [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
   • [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”
   • [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Asana✓fullprobed8/10

   Asana documents an official MCP server at a dedicated docs page (asana-probe-3: developers.asana.com/docs/using-asanas-mcp-server), confirming a first-party MCP integration for connecting agents. Missing for 10: independent/hands-on community corroboration of the MCP server working in practice, and more detail on setup/auth scope beyond the docs link.

   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

   proof ↗⚑ flag

   Notion✓fullprobed8/10

   Notion documents an official MCP server ('Notion MCP') that agents like Claude Code, Cursor, or Codex can connect to via OAuth 2.0/PKCE, with docs on client setup, security best practices, and workspace admin controls for MCP access. missing for 10: independent/hands-on third-party verification of the MCP server's reliability in production use.

   • [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
   • [claimed-docs] “Build an MCP client that connects to Notion MCP using OAuth 2.0 with PKCE.”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
   • [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”
   • [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”
   • [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Asana—none0/10

   Evidence shows Asana has a REST API, OpenAPI spec, and even an MCP server, but nothing mentions an official CLI tool for interacting with Asana. missing for 10: any documentation of an official Asana CLI, install instructions, or command reference.

   ⚑ flag

   Notion—none0/10

   Evidence shows REST API, PATs, MCP server/client support, and webhooks, but no mention anywhere of an official command-line interface (CLI) tool shipped by Notion; PATs are described as usable 'for scripts, CLI workflows' but that refers to third-party/custom CLIs built by developers, not an official Notion CLI.

   • [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
   • [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Asana✓fullclaimed9/10

   Asana publishes a documented REST API with authentication, resource-oriented endpoints, an in-context API explorer, an official OpenAPI spec repo, a developer sandbox, and deprecation/versioning guidance — clearly enabling programmatic/agentic control of the product. Missing for 10: independent third-party hands-on verification of API robustness/reliability beyond vendor docs.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “the API itself will also alert you of upcoming changes. Shortly after we post communication, the API will begin sending Asana-Change headers…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”

   proof ↗⚑ flag

   Notion✓fullprobed9/10

   Notion ships a well-documented public REST API with OpenAPI spec, PATs/OAuth for internal and public connections, webhooks, and even dedicated Agent APIs and MCP guides for AI-native workflows, confirmed by live probes (openapi.json, llms.txt). missing for 10: independent third-party hands-on developer reports validating real-world API robustness beyond vendor docs.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
   • [claimed-docs] “Public connections use OAuth 2.0 for authentication... Public connections must undergo a Notion security review before being listed on the M…”
   • [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.notion.com/llms.txt # Notion Docs - [Overview](https://developers.notion.com/guides/get-star…”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Notion
   Asana~partialclaimed5/10

   Asana documents token-based API authorization (asana-docs-1) and describes AI Teammates having scoped permissions, identity, and audit trails governed centrally (asana-docs-13), suggesting some notion of least-privilege agent credentials. However, there is no concrete documentation of issuing scoped/limited-permission API tokens or OAuth scopes specifically for third-party agents, nor granular permission configuration UI/API for developer-issued credentials. missing for 10: explicit scoped OAuth/token permission model documentation, developer-facing controls to limit an API credential's access surface, and independent verification that agent credentials can be scoped rather than full-account access.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Notion~partialclaimed7/10

   Notion documents multiple credential-scoping mechanisms relevant to agents: internal connections use a static token scoped to a single workspace, public/OAuth connections let you choose an installation scope, Custom Agent connections only reach agents explicitly shared with them, and MCP security best practices let owners require confirmation before write actions and manage client access per workspace. This shows real least-privilege controls but not fine-grained (e.g. per-resource read/write, expiring/rotatable) scopes explicitly documented. Missing for 10: documented granular permission types (read-only vs write vs admin) for API tokens, token expiration/rotation policy, and independent/hands-on confirmation that scoping works as described in practice.

   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Public connections use OAuth 2.0 for authentication. At creation time, you choose their installation scope”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token.”
   • [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”
   • [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”
   • [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack extensively documents Asana's REST API, OpenAPI spec, sandbox, and deprecation policy, but never mentions officially maintained client SDKs (e.g., Python/Node/Java libraries) for developers to build against. Missing for 10: any documentation or reference to first-party SDK packages, language coverage, or SDK versioning/support.

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.asana.com/openapi.json, https://developers.asana.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Notion✓fullprobed8/10

   Notion publishes a full REST API with OpenAPI spec, official SDK-style access via internal/public connections and PATs, an official MCP server/client guides, webhooks, and Agent APIs with SDK-like session/streaming semantics — all documented first-party and confirmed by live probes (openapi.json, llms.txt, MCP docs). Missing for 10: independent hands-on developer corroboration of SDK usage and no explicit mention of language-specific official SDK libraries (only REST/OpenAPI + MCP tooling), so some ambiguity remains on 'official SDK' vs REST/OpenAPI wrapper.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”
   • [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Notion
   Asana✓fullclaimed7/10

   Asana's platform docs explicitly list webhooks alongside rules and API as a core automation mechanism, allowing external systems (including AI agents) to subscribe to Asana events. missing for 10: no dedicated webhook payload/signature-verification docs or independent hands-on confirmation of webhook reliability in the pack.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

   Notion✓fullclaimed8/10

   Notion's docs explicitly document webhook subscriptions for real-time events (page updates, property changes, new comments) sent as secure HTTP POST requests, configurable per connection. missing for 10: no independent/hands-on corroboration of webhook reliability or event coverage beyond first-party docs.

   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”

   proof ↗⚑ flag

10. ai-native userHand off work between tools or agents without losing context or information

    weight 1 · round drawn
    Asana~partialprobed6/10

    Asana documents shared memory across AI Teammates so context 'carried forward' between agents, governance/permissions for agent handoff, and cross-tool integration via API, webhooks, app components, and an official MCP server enabling handoff to external agents/tools. However, all of this is vendor-documented with no independent or hands-on verification that context is actually preserved end-to-end across tool/agent handoffs. Missing for 10: independent/hands-on corroboration of lossless handoff, concrete example of an agent-to-agent or tool-to-tool handoff preserving full context, and clarity on how MCP server handles context transfer in practice.

    • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
    • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
    • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
    • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”
    • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
    • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

    proof ↗⚑ flag

    Notion~partialprobed6/10

    Notion supports handoff via REST API, webhooks, MCP server/client interoperability (Claude Code, Cursor, Codex), and Agent APIs with session/event history that preserve context across tool boundaries. However, there's no dedicated evidence of cross-agent context preservation guarantees, no independent/hands-on validation of lossless handoff, and community feedback focuses on unrelated pain points rather than confirming this specific capability. missing for 10: independent verification of lossless context transfer between agents/tools, explicit handling of long-running multi-agent handoff scenarios, and hands-on user reports confirming this workflow in practice.

    • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
    • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
    • [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
    • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
    • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
    • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
    • [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”

    proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Asana~partialclaimed6/10

   Asana markets AI Teammates, AI Studio, and 'Asana Dash' as an AI Chief of Staff that surfaces insights and suggestions drawing on Work Graph context and shared memory, which directly matches the story. However, these are vendor claims only—there's no independent/hands-on evidence confirming quality or reliability of these AI-generated insights, and details on how proactive/contextual the suggestions are remain thin. Missing for 10: independent corroboration of AI insight quality, concrete examples of AI-generated suggestions in action, hands-on user reviews of Dash/AI Studio outputs.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

   Notion documents AI-native capabilities like Q&A with citations ('Get answers, instantly—with citations'), always-on agents ('Keep work moving 24/7 with agents'), and Notion Agent APIs/MCP that can search, read, and act on workspace content, implying AI-generated insight generation from user data. However, evidence is largely first-party marketing/docs with no independent hands-on account of the quality or depth of these AI-generated insights/suggestions, and no detail on proactive suggestion generation beyond Q&A/agents. Missing for 10: independent corroboration of insight quality, concrete examples of AI-generated suggestions (not just answers/actions), and detail on proactive analytics/insight surfacing.

   • [claimed-docs] “Get answers, instantly—with citations.”
   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Asana
   Asana✓fullclaimed7/10

   Asana documents rule-based automations, webhooks, and 'AI Studio' for no-code autonomous workflows, plus 'AI Teammates' that run inside workflows with shared memory, scoped permissions, and audit trails — directly supporting background/autonomous automation. Missing for 10: independent/hands-on corroboration that these automations reliably run unattended in production, and more detail on triggers/scheduling beyond marketing copy.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

   Notion's docs claim agent capabilities ('Keep work moving 24/7 with agents') plus a dedicated Agent API with sessions, event history, and Custom Agents that can be tracked/managed via token — suggesting agents that operate somewhat autonomously in the background. Webhooks and internal-connection API tokens also support event-driven automations that fire without user intervention. However, the MCP security guidance recommends requiring human confirmation before content-changing actions, which cuts against true unattended autonomy, and there's no detail on native scheduled/triggered workflow automations or independent verification of 24/7 unattended operation. Missing for 10: documentation of native scheduled/cron-style automations, evidence agents can act without confirmation gates, and independent/hands-on corroboration of reliable background execution.

   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
   • [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Asana✓fullclaimed7/10

   Asana ships pre-built AI Teammates/agents (asana-docs-5,6,12,13) and Asana Dash described as an 'AI Chief of Staff' (asana-docs-8) that work within tasks/workflows with shared memory and governance, directly matching delegation of tasks to a built-in assistant. Missing for 10: independent hands-on reviews or third-party validation of AI Teammates actually performing delegated tasks, and detail on the scope/reliability of delegation beyond vendor marketing copy.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion✓fullclaimed7/10

   Notion markets and documents a built-in AI assistant/agent layer ('Get answers, instantly—with citations', 'Keep work moving 24/7 with agents') plus first-party Agent APIs for sessions, chat, streaming replies, and Custom Agents management, showing the assistant is a native, delegable feature rather than a third-party bolt-on. Missing for 10: independent/hands-on user reports validating real-world task delegation quality and reliability, and more detail on in-app assistant UX beyond marketing copy and API docs.

   • [claimed-docs] “Get answers, instantly—with citations.”
   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
   • [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Asana~partialprobed6/10

   Asana ships AI Teammates/AI Studio and a Chief-of-Staff style agent (Dash) described as operating with shared memory and governance, plus an MCP server enabling natural-language agent interaction, suggesting real natural-language control surfaces exist. However, there is no first-party documentation or hands-on evidence showing an end user issuing free-form natural-language commands directly in the core Asana UI to create/manage tasks; most 'AI-native' evidence is marketing copy without demonstrated workflows. missing for 10: hands-on demonstration or detailed docs of natural-language command execution in the main product UI, independent verification of Dash/AI Teammates handling arbitrary NL requests, and clarity on how MCP server maps to end-user NL commands versus developer/agent use.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

   proof ↗⚑ flag

   Notion~partialprobed6/10

   Notion supports natural-language operation via its AI agents, MCP integration (usable by Claude Code, Cursor, Codex), and Notion Agent APIs that let clients read/create/update content and start chat sessions with streamed replies — a strong agentic surface. However, this is mostly mediated through third-party MCP clients or the Notion AI assistant rather than a built-in native NL command interface across the whole product, and there's no independent/hands-on evidence confirming reliability of these NL-driven actions. missing for 10: independent verification of natural-language command accuracy/reliability, evidence of NL commands operating directly within Notion's own UI (not just via external MCP clients or agent APIs).

   • [claimed-docs] “Get answers, instantly—with citations.”
   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
   • [claimed-docs] “A Notion Skill is a page you own with instructions for a repeatable workflow. You can maintain it yourself or ask an assistant to do it for …”
   • [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”

   proof ↗⚑ flag

5. ai-native userBuild and configure my own custom AI agent within the product

   weight 2 · round to Notion
   Asana~partialclaimed6/10

   Asana markets 'AI Studio' for no-code agent automations and 'custom AI Teammates' built from team expertise, with governance and shared memory features (asana-docs-6,7,12,13), indicating a self-service agent-building capability. However, all evidence is first-party marketing copy with no tutorial, screenshots, or independent hands-on account of actually configuring an agent end-to-end. missing for 10: independent/hands-on verification of building a custom agent, detailed step-by-step configuration docs, community confirmation of the feature working as advertised.

   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion~partialclaimed7/10

   Notion's developer docs describe a distinct 'Custom Agents' capability with session-based chat, streaming replies, action confirmation, and access/usage management (notion-docs-21, notion-docs-22, notion-docs-29), plus marketing language about 'agents' keeping work moving 24/7 (notion-docs-8), indicating users/developers can build and manage their own AI agents in the product. However, the evidence pack lacks detail on how deeply an end user can configure agent persona, tool access, or instructions beyond access-sharing and credit limits. missing for 10: detailed documentation of persona/instruction configuration, tool-selection UI, and independent hands-on confirmation of building a custom agent end-to-end.

   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
   • [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”
   • [claimed-docs] “Keep work moving 24/7 with agents.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Asana
   Asana✓fullclaimed8/10

   Asana's developer docs explicitly state each API endpoint has a built-in, in-context API explorer for making requests and viewing responses (asana-docs-16), backed by a RESTful reference (asana-docs-15) and an official OpenAPI spec repo (asana-supp-openapi-spec, asana-docs-20), plus a developer sandbox for safe testing (asana-docs-17). Missing for 10: independent/hands-on confirmation of the explorer's runnable examples in practice, and a working public openapi.json endpoint (probe found 404s at standard paths).

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

   Notion~partialprobed6/10

   Notion publishes a full OpenAPI spec and a quickstart guide that walks through making a live API request in minutes, indicating a structured, testable API reference exists, but there is no explicit evidence of an in-browser 'try it now' runnable console or interactive playground beyond the openapi.json and quickstart docs. missing for 10: explicit interactive try-it-in-browser console, independent confirmation of runnable examples working out-of-box.

   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Asana✓fullprobed9/10

   Asana publishes an official OpenAPI specification (asana_oas.yaml plus app-components spec) in the Asana/openapi GitHub repo, which is machine-readable and downloadable, and the REST API docs corroborate a resource-oriented JSON API with in-context explorer built from this spec. Missing for 10: a directly hosted openapi.json/swagger.json endpoint on developers.asana.com (probe found 404s at expected discovery URLs), so users must know to fetch it from GitHub rather than a standard API-discovery path.

   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.asana.com/openapi.json, https://developers.asana.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Notion✓fullprobed9/10

   Notion hosts a downloadable OpenAPI spec at developers.notion.com/openapi.json (confirmed HTTP 200 with 'openapi' key), alongside an llms.txt machine-readable docs index, giving AI-native users direct access to a standard, machine-readable API spec. missing for 10: no independent third-party confirmation of spec completeness/versioning beyond the probe check.

   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.notion.com/llms.txt # Notion Docs - [Overview](https://developers.notion.com/guides/get-star…”
   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Asana
   Asana✓fullclaimed8/10

   Asana explicitly documents a developer sandbox — a temporary Asana domain with limited users — for testing purposes, plus feature-flag headers to test upcoming API behavior before it goes live, directly supporting isolated testing without touching production data. missing for 10: independent/hands-on confirmation of sandbox fidelity and any limits (e.g., data reset, scale) that might affect real-world AI-agent testing workflows.

   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “you can test out how the API will behave by sending additional headers in your requests. Sending an Asana-Enable header including comma-sepa…”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”

   proof ↗⚑ flag

   Notion—none0/10

   No evidence of a sandbox/test workspace, staging environment, or mock API for testing separate from production data; the API docs describe only live workspace read/write access with no isolated test mode.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Asana
   Asana✓fullclaimed8/10

   Asana documents a formal deprecation process with Asana-Change headers, Asana-Enable headers for opt-in testing, migration plans, and a deprecation period, plus a public OpenAPI spec repo and REST reference with an interactive explorer, indicating a mature versioned/documented API lifecycle. Missing for 10: independent third-party corroboration of deprecation policy adherence over time and explicit API version numbering scheme details.

   • [claimed-docs] “the API itself will also alert you of upcoming changes. Shortly after we post communication, the API will begin sending Asana-Change headers…”
   • [claimed-docs] “you can test out how the API will behave by sending additional headers in your requests. Sending an Asana-Enable header including comma-sepa…”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”

   proof ↗⚑ flag

   Notion—none0/10

   The evidence pack shows Notion's REST API, OAuth, webhooks, and OpenAPI spec exist, but none of the citations mention API versioning conventions (e.g., a Notion-Version header) or any documented deprecation policy for breaking changes. Missing for 10: explicit version header documentation, deprecation timeline commitments, migration guides for version changes.

   ⚑ flag

5. ai-native userThe documented API rate limits and concurrency caps before building automation at scale

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack covers Asana's REST API, OpenAPI spec, deprecation policy, and developer sandbox, but nothing addresses documented rate limits or concurrency caps for API usage. Since no citation speaks to this specific axis, it cannot be credited even though it's a fair question for an API platform.

   ⚑ flag

   Notion—none0/10

   The evidence pack covers API capabilities, auth models, webhooks, and MCP integration, but nowhere documents specific rate limits, request-per-second caps, or concurrency limits for the REST API. No source states numeric thresholds or throttling behavior that an automation builder would need to plan at scale.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Notion
   Asana—none0/10

   The evidence describes single-task creation via the API, rule-based automation, webhooks, and AI Studio workflows, but nowhere mentions a bulk/batch endpoint or the ability to update many items in one call as an AI-native user. Missing for 10: explicit bulk/batch API operations, multi-item update endpoints, or documented bulk action support.

   ⚑ flag

   Notion~partialclaimed4/10

   Notion's REST API and MCP integration let scripts/agents read, create, and update pages and databases programmatically (notion-docs-1, notion-docs-13, notion-docs-26), which enables looping over many items via custom code, but there is no documented native batch/bulk endpoint or bulk-update mechanism in the evidence pack. Missing for 10: explicit bulk/batch API endpoints, rate-limit guidance for large-scale operations, and independent confirmation that bulk automation works reliably at scale.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
   • [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Asana
   Asana✓fullclaimed7/10

   Asana's native Rules engine plus 'rule actions, webhooks, and API' explicitly supports trigger-based automation on events, and AI Studio adds no-code automations layered on top, with app components allowing custom logic to plug into rules. Missing for 10: independent hands-on verification of AI-native rule-building via API/agent, and detail on the range of triggerable events/conditions.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

   Notion's platform supports event-driven automation via webhooks (subscribing to page/property/comment changes and POSTing to an endpoint) plus a REST API and agent APIs to act on those events, which lets an AI-native user build 'when X happens, do Y' pipelines. However, this requires external code/infra to interpret webhook payloads and execute actions — there's no documented native no-code 'if this then that' rule builder in the evidence, only developer-facing webhook + API primitives. Missing for 10: evidence of a built-in visual automation/rules engine, filtering conditions on triggers, and independent confirmation that webhook-driven automations work reliably in practice.

   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Asana
   Asana~partialclaimed4/10

   Asana's platform docs show general automation via rules, webhooks, API, and AI Studio's no-code automations, which could support recurring workflows, but no evidence explicitly describes scheduling or recurring job triggers (e.g., time-based rule triggers). Missing for 10: explicit documentation of recurring/scheduled triggers, cron-like automation, or examples of automating tasks on a recurring schedule.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”

   proof ↗⚑ flag

   Notion—none0/10

   Evidence shows Notion's API/webhooks support event-driven automation (page changes, comments) and scripted API access via PATs, but there is no documented native mechanism for scheduling recurring/time-based jobs or workflows within Notion itself — webhooks fire on data changes, not on a schedule. Missing for 10: any documented cron-like scheduler, recurring automation trigger, or timed job feature.

   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
   • [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Asana—none0/10

   No evidence of version history, review workflows, or rollback capability for Asana rules/automations or AI Studio workflows; docs cover API deprecation headers and app components, not automation versioning/rollback. missing for 10: version history UI for rules/automations, diff/review workflow before publishing changes, rollback/restore to prior automation version.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”

   proof ↗⚑ flag

   Notion—none0/10

   Evidence shows Notion has automation-adjacent features (API-driven agents, MCP action confirmation) but nothing about versioning automation definitions, reviewing change history, or rolling back automations to a prior state. The closest item (notion-docs-28) only covers per-action confirmation, not version control or rollback of the automation itself.

   • [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”

   proof ↗⚑ flag

Ai task automation

1. ai-native userHave AI automatically triage and prioritize incoming bugs and tasks

   weight 2 · round to Asana
   Asana~partialclaimed5/10

   Asana offers rule-based automation, webhooks/API, AI Studio no-code automations, and AI Teammates described as handling 'complex, coordination-heavy work' with shared memory and governance — these are generic building blocks that could be configured to triage/prioritize tasks, but no evidence explicitly documents a bug-triage or prioritization use case or template. Missing for 10: a concrete documented workflow or template showing AI classifying/prioritizing incoming bugs or tasks, independent/hands-on validation of such a workflow.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion~partialclaimed4/10

   Notion documents AI agents ('Keep work moving 24/7 with agents') and a REST API with webhooks that could be wired to auto-triage or prioritize tasks/bugs in a database, but there is no evidence of an out-of-the-box bug/task triage or prioritization feature — this would require custom building. Missing for 10: dedicated bug/task triage feature, evidence of automatic prioritization logic, and any hands-on confirmation this works as described.

   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”

   proof ↗⚑ flag

2. ai-native userHave my in-app AI assistant learn my tone, shorthand, and preferences to tailor its output

   weight 1 · round to Asana
   Asana~partialclaimed4/10

   Asana's AI Teammates feature claims 'shared memory' where 'every piece of feedback, every preference gets carried forward,' which loosely maps to personalization, but there's no specific evidence of learning tone, shorthand, or writing style, nor any hands-on validation of this personalization actually working. missing for 10: evidence of tone/style/shorthand learning specifically, first-party detail on how preference adaptation works mechanically, and independent corroboration that AI output actually reflects user's individual style.

   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”

   proof ↗⚑ flag

   Notion—none0/10

   Evidence covers Notion's AI agent APIs, MCP integration, and general search/citations features, but nothing describes the AI assistant learning a user's personal tone, shorthand, or writing preferences to tailor output. Notion Skills (notion-docs-27) let users author explicit workflow instructions, but that's manual configuration, not adaptive learning of personal style/preferences.

   ⚑ flag

Workflow automation

1. engineerAuto-generate a changelog for each release so shipping progress is easy to review

   weight 1 · round drawn
   Asana—none0/10

   Asana is a project/task management tool, not a code repository or CI/CD system; nothing in the evidence shows any feature for generating release changelogs from commits, PRs, or version tags. While Asana has APIs, rules, and automation features, none are documented as producing changelogs tied to releases.

   ⚑ flag

   Notion—none0/10

   Notion offers generic APIs, webhooks, and a GitHub integration, but there is no evidence of any changelog-generation feature or template/automation specifically for release changelogs.

   ⚑ flag

2. product managerBuild multi-step automations without writing code

   weight 2 · round to Asana
   Asana~partialclaimed6/10

   Asana explicitly markets 'AI Studio – Powerful no-code automations' and references 'rule actions' as part of its automation platform, directly supporting a PM building multi-step automations without code. However, the evidence pack lacks deeper documentation (e.g., a rules builder walkthrough, examples of multi-step conditional logic, or independent hands-on validation) beyond marketing taglines. missing for 10: detailed no-code rule-builder documentation/tutorial, independent user validation of multi-step automation building.

   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”

   proof ↗⚑ flag

   Notion~partialclaimed3/10

   Notion advertises 'agents' that 'keep work moving 24/7' and 'Notion Skills' as reusable, no-code workflow instructions, plus Custom Agents accessible via API, hinting at some no-code automation capability for non-developers. However, most of the automation-related evidence (REST API, webhooks, MCP servers, PATs) is explicitly developer/code-oriented, and there is no documentation of a native drag-and-drop or point-and-click multi-step automation builder for PMs. Missing for 10: a dedicated no-code automation builder UI, concrete PM-facing multi-step workflow examples, and independent corroboration that non-technical users can chain multiple actions without scripting.

   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “A Notion Skill is a page you own with instructions for a repeatable workflow. You can maintain it yourself or ask an assistant to do it for …”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”

   proof ↗⚑ flag

3. engineerBuild trigger-and-action automation rules to eliminate repetitive manual steps

   weight 3 · round drawn
   Asana~partialclaimed6/10

   Evidence confirms Asana has a rule-based automation surface ("rule actions", app components built on the surface of "rules", and AI Studio's no-code automations) that lets engineers/users automate repetitive steps, and the API/webhooks can be combined with rules for custom triggers. However, the pack lacks first-party documentation detailing the actual trigger types, conditions, or multi-step rule builder UI, so the story is only partially evidenced. Missing for 10: dedicated Rules-builder documentation showing trigger/condition/action configuration, and independent/hands-on confirmation of building such rules.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

   Notion's REST API, webhooks, and internal/public connections let engineers build custom trigger-and-action automations (subscribe to page/property changes, then read/create/update content programmatically), and third-party integrations (GitHub, Loom, Tableau) extend this further. However, this is a DIY/code-first approach via API+webhooks rather than a native no-code trigger-action rules builder inside Notion itself. Missing for 10: evidence of a built-in visual automation/rules engine (if-this-then-that) inside the product, and independent verification that engineers successfully use these APIs for production automation.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
   • [claimed-docs] “Keep your GitHub and Notion workflows in sync”

   proof ↗⚑ flag

4. engineerCreate a workflow that runs on a schedule or recurring event to handle routine team work

   weight 2 · round drawn
   Asana~partialclaimed4/10

   Asana's docs reference rule-based automation ('rule actions, webhooks, and our API') and AI Studio's 'no-code automations,' suggesting engineers can build workflow automations, but no evidence explicitly documents a schedule/time-based or recurring-event trigger mechanism for these workflows. Missing for 10: explicit documentation of scheduled/cron-like or recurring-event triggers in Rules or AI Studio, and any hands-on/independent confirmation that such scheduled automations work reliably.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”

   proof ↗⚑ flag

   Notion~partialprobed4/10

   Notion exposes a REST API, personal access tokens, and webhooks for event-driven automation (e.g., page/database changes), which engineers could wire into external cron jobs or agent workflows for routine team tasks, but there is no documented native scheduling/cron trigger inside Notion itself — webhooks are event-triggered, not time-based. missing for 10: native schedule/cron trigger, built-in recurring-job runner, first-party example of a scheduled automation using the API.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

5. ai-native userWhat happens—extra charges, throttling, or a hard stop—when I exceed my plan's automation or API call limits

   weight 3 · round drawn
   Asana—none0/10

   No evidence describes rate limits, throttling behavior, overage charges, or hard stops for exceeding automation/API quotas; docs cover deprecations, sandbox, and API basics but not usage limits or their consequences.

   ⚑ flag

   Notion—none0/10

   No evidence pack item discusses rate limits, throttling, overage charges, or hard stops for API/automation usage—only general API capabilities, agent 'credit limits' mention without specifics, and integration lists are present. This is an applicable axis for an API-driven product, but no documentation of what happens when limits are exceeded is provided.

   ⚑ flag

Cross tool sync

1. designerKeep project status updated from my design tool without switching apps

   weight 2 · round to Notion
   Asana~partialclaimed3/10

   Asana's API, webhooks, and App Directory (asana-docs-2, asana-docs-11) allow third-party apps to create/update tasks and status without leaving another tool, and app components let external apps surface inside the Asana UI (asana-docs-3/10/14), which is the general mechanism such a design-tool integration would use. However, there is no evidence of an actual Figma/Sketch/Adobe-type design tool integration or of status updates flowing specifically from a design tool into Asana project status. missing for 10: a named design-tool integration (e.g., Figma plugin) syncing project status, and any hands-on/community confirmation it works.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”

   proof ↗⚑ flag

   Notion~partialclaimed4/10

   Notion offers a generic REST API, webhooks, and integrations (e.g. Canva, Sketch) that let designers view/share design assets in Notion and could theoretically be used to sync status via custom automation, but there is no evidence of a built-in, native workflow where a design tool directly updates a Notion project status field without switching apps. Missing for 10: a documented direct integration (e.g. Figma/Canva plugin) that writes status/property updates back to Notion, and any hands-on confirmation that such a workflow works in practice.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “View and share Canva designs in Notion”
   • [claimed-docs] “View and share Sketch designs in Notion”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”

   proof ↗⚑ flag

Docs knowledge

1. product managerCreate and organize shared docs and notes alongside my project work

   weight 3 · round to Notion
   Asana—none0/10

   No evidence in the pack shows a native Asana docs/notes feature for organizing shared documentation alongside project work; the docs and community items focus on tasks, API/dev platform, and AI Teammates, not a wiki/notes capability. One community comment even suggests a competing tool being compared lacks 'free form notes and wiki' relative to Asana/Trello, but nothing confirms Asana itself ships a shared-doc feature.

   • [community] “This seems to just be the boards and task lists without the free form notes and wiki? It pretty clearly replaces Trello and Asana.”

   proof ↗⚑ flag

   Notion✓fullcommunity8/10

   Notion's core product is exactly this: shared docs/notes organized alongside databases and project tracking in 'one system of record,' and community evidence confirms real-world use as wiki, project tracker, and issue tracker alongside notes. Minor caveats exist (comm-6 notes friction at scale, comm-8 a legacy block-limit complaint) but the core capability is well established. Missing for 10: independent benchmarking of doc/project integration depth and resolution of the 'jack of all trades' scaling complaints.

   • [claimed-docs] “Bring everything into one system of record.”
   • [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
   • [community] “We use it to keep track of all of our tasks and projects... notifications are still hit or miss... Search still needs some love... I'd love …”
   • [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”

   proof ↗⚑ flag

In context discussion

1. engineerComment directly on specific text or images within an item's description

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains only API/developer platform docs and general community sentiment; nothing describes inline commenting on specific text or images within a task/item description. Missing for 10: any documentation or hands-on evidence of annotation/inline commenting features on description text or embedded images.

   ⚑ flag

   Notion~partialclaimed3/10

   The evidence only shows that Notion's API can read/create/update generic 'comments' as one of the object types alongside pages and databases (notion-docs-1, notion-docs-13), but there is no documentation or community evidence confirming the specific capability of inline commenting on selected text or images within a page description. Missing for 10: explicit documentation of block/inline text commenting, image-specific comment anchoring, and any hands-on confirmation that comments attach to specific text/image selections rather than whole pages/blocks generically.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more”

   proof ↗⚑ flag

Real time sync

1. engineerSee teammates' changes reflected instantly across open sessions without refreshing

   weight 3 · round to Notion
   Asana—none0/10

   The evidence pack contains no mention of real-time UI sync, live presence, or websocket-based updates in Asana's interface — only API/webhook automation, developer sandbox, and AI Teammate features, none of which address instant cross-session UI updates for engineers viewing shared work.

   ⚑ flag

   Notion~partialcommunity5/10

   Community feedback confirms Notion's real-time collaborative editing is a strong point ('really good real-time collaboration', 'collaborative components feel really powerful'), but other reports describe lag and even a page refresh wiping unsaved work, suggesting real-time sync isn't always seamless. No first-party documentation explicitly describes the live-sync/websocket mechanism for instant cross-session updates. missing for 10: official docs on real-time sync architecture, hands-on verification of instant updates without refresh, resolution of documented lag/data-loss complaints.

   • [community] “For now I use Notion with the hopes they implement it eventually [offline read-only mode]. I can't consider switching to a self hosted alter…”
   • [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”
   • [community] “I love Notion but the speed, or rather lack of, is killing me daily. Last Friday I was taking some notes, and suddenly the page refreshed an…”

   proof ↗⚑ flag

Team chat

1. engineerChat with my team directly inside the same tool I plan work in

   weight 2 · round drawn
   Asana—none0/10

   Asana's evidence pack covers task management, APIs, automations, and AI teammates, but nothing documents an in-app real-time chat/messaging feature for team communication; the closest mention (asana-comm-5) is a vague anecdote about using task comments instead of Slack, not a documented chat capability.

   • [community] “Asana has been around awhile and my team always used it for remote team communication and project management. We never saw the need for apps…”

   proof ↗⚑ flag

   Notion—none0/10

   Evidence covers Notion's API, comments, webhooks, and general collaboration platform claims, but there is no mention of a built-in chat/messaging feature for real-time team communication within Notion. Comments (notion-docs-3) are asynchronous annotations, not chat.

   ⚑ flag

App ecosystem

1. engineerKeep tasks bi-directionally synced with my code repository's issue tracker instead of duplicating data

   weight 2 · round to Notion
   Asana—none0/10

   The evidence only shows generic Asana API/webhook/app-directory capabilities (e.g., asana-docs-2, asana-docs-11) that could be used to build custom sync, but there is no documentation of a specific, ready-made bi-directional sync with a code repository issue tracker (e.g., GitHub/GitLab/Jira issues) that avoids data duplication. Without a named integration or sync workflow for this exact use case, this remains unevidenced.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Notion~partialcommunity5/10

   Notion lists a GitHub integration ('Keep your GitHub and Notion workflows in sync') and offers a general REST API plus webhooks that could be used to build custom bi-directional sync between Notion databases and an issue tracker, but there is no documented native two-way sync of task/issue state (e.g., status changes propagating both directions) — the GitHub integration description is thin and unverified beyond a marketing tagline, and an older community comment even complains Notion 'does not have a GitHub integration.' missing for 10: concrete documentation of bi-directional field/status sync with GitHub Issues (or Jira/Linear), and independent confirmation the integration goes beyond simple embeds/linking.

   • [claimed-docs] “Keep your GitHub and Notion workflows in sync”
   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
   • [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”

   proof ↗⚑ flag

2. engineerSee my assigned tasks from multiple project management tools in one unified view

   weight 2 · round drawn
   Asana—none0/10

   Evidence shows Asana's API/integrations let other apps create Asana tasks or embed components, but there is no evidence of a unified view that aggregates an engineer's assigned tasks from multiple different project-management tools (e.g., Jira, Trello) inside Asana itself. Missing for 10: any documentation of a cross-tool task aggregation/unified inbox feature, evidence of pulling in tasks from other PM tools, or a 'My Tasks' view spanning external systems.

   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

   Notion—none0/10

   Evidence shows Notion's API and integrations directory (GitHub, Loom, Tableau, Mixpanel, Canva, etc.) but none of these are project-management tools like Jira, Asana, or Trello, and there is no documented feature for pulling assigned tasks from multiple external PM tools into a single unified view. Community comments even note the historical lack of GitHub/PM integrations as a dealbreaker, with no counter-evidence of a task-aggregation feature being added.

   • [claimed-docs] “Keep your GitHub and Notion workflows in sync”
   • [claimed-docs] “Extend Notion with connections that sync your data, automate workflows, and connect your favorite tools.”
   • [claimed-docs] “View Mixpanel boards, reports and charts inside Notion”
   • [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”
   • [community] “Notion could as well [integrate with Mattermost/discord] but they are a slow moving beast with different priorities.”

   proof ↗⚑ flag

3. engineerConnect common tools like Slack, GitHub, and Google Drive natively

   weight 2 · round to Asana
   Asana~partialclaimed4/10

   Asana's docs mention a broader integration ecosystem (App Directory apps, app components that 'plug directly into Asana UI', APIs/webhooks for building integrations), implying that tools can connect natively, but no evidence explicitly names Slack, GitHub, or Google Drive as first-party native integrations. Missing for 10: explicit documentation of native Slack/GitHub/Google Drive connectors, hands-on confirmation of their functionality, and any independent corroboration of these specific integrations working out-of-the-box.

   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

   Notion!disputedcontradicted3/10

   Notion's dev docs describe a general integrations framework (public/internal connections, OAuth, webhooks, marketplace) that could support connectors to tools like Slack, GitHub, or Google Drive, but no evidence names these specific integrations as built-in. A direct community report explicitly states Notion lacks a native GitHub integration, calling it a dealbreaker for tech teams, which concretely contradicts any claim of native connectivity to common engineering tools. Missing for 10: explicit documentation or first-party listing of Slack, GitHub, and Google Drive integrations, and independent confirmation they work natively without third-party glue.

   • [claimed-docs] “Public connections use OAuth 2.0 for authentication... Public connections must undergo a Notion security review before being listed on the M…”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Public connections use OAuth 2.0 for authentication. At creation time, you choose their installation scope”
   • [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”

   proof ↗⚑ flag

4. product managerConnect my workspace to thousands of third-party tools via an app marketplace

   weight 2 · round drawn
   Asana~partialclaimed6/10

   Asana docs confirm an 'App Directory' with many third-party apps that create tasks and kick off workflows, plus a public REST API, webhooks, and app components for building custom integrations, which together support a marketplace-style ecosystem. However, no evidence quantifies the marketplace size ('thousands of tools') or shows a browsable marketplace UI/listing, and no independent/community source corroborates breadth of integrations. missing for 10: concrete count/scale of App Directory listings, independent hands-on evidence of marketplace breadth, and marketplace browsing/install UX documentation.

   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Notion~partialcommunity6/10

   Notion's docs confirm a public marketplace model with OAuth-based 'public connections' that undergo a security review before being listed, plus internal connections and webhooks for automations, supporting third-party integration capability. However, there is no evidence pack confirmation of marketplace scale (e.g., 'thousands' of listed integrations), and an older community comment notes a lack of a native GitHub integration, suggesting coverage gaps for some popular tools. Missing for 10: quantitative evidence of marketplace size/breadth, and resolution of specific integration gaps raised by users.

   • [claimed-docs] “Public connections use OAuth 2.0 for authentication... Public connections must undergo a Notion security review before being listed on the M…”
   • [claimed-docs] “Public connections use OAuth 2.0 for authentication. At creation time, you choose their installation scope”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”

   proof ↗⚑ flag

Extensibility

1. designerBuild custom views and dashboard widgets that feel native to the product

   weight 1 · round to Asana
   Asana~partialclaimed5/10

   Asana's developer docs describe 'app components' that let third-party apps plug directly into the Asana UI on the surface of tasks or rules, which supports building native-feeling integrations, but the story's specific asks—custom views and dashboard widgets—are not evidenced; only task/rule surface extensions are documented, with no dedicated widget/dashboard SDK or design guidelines mentioned. Missing for 10: explicit dashboard widget support, custom view builder APIs, design system/UI kit guidance, and independent/hands-on confirmation from designers building such components.

   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

   Notion—none0/10

   Evidence shows Notion's API/integrations let developers sync data, automate workflows, and embed third-party content (Tableau, Mixpanel, Canva) inside pages, but there is no documentation of a widget/dashboard SDK or custom-view framework that lets a designer build native-feeling UI components inside Notion itself — embeds are pre-built partner integrations, not designer-authored native widgets.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “View Tableau charts and dashboards in Notion”
   • [claimed-docs] “View Mixpanel boards, reports and charts inside Notion”
   • [claimed-docs] “View and share Canva designs in Notion”

   proof ↗⚑ flag

Getting started

1. product managerThat exporting my workspace preserves full history—comments, attachments, and audit trails—not just task titles

   weight 3 · round drawn
   Asana—none0/10

   No evidence pack item addresses workspace export functionality, let alone preservation of comments, attachments, or audit trails during export; docs focus on API, automation, and AI Teammates instead.

   ⚑ flag

   Notion—none0/10

   The evidence pack contains no documentation or claims about Notion's workspace export feature preserving comments, attachments, or audit trails; the only tangential comment (notion-comm-16) suggests users find it 'hard to get stuff out' of Notion, which does not support the story. Missing for 10: any vendor documentation of an export function, evidence of comment/attachment preservation on export, or evidence of audit-trail export.

   • [community] “I've started using notion as a kind of personal wiki... My only issue with Notion is that I feel it's hard to get stuff out of it, especiall…”

   proof ↗⚑ flag

2. engineerFollow a guided walkthrough to set up my workspace the first time

   weight 1 · round drawn
   Asana—none0/10

   The evidence pack covers Asana's developer API, OpenAPI specs, MCP server, and general community sentiment about product quality, but contains no mention of a guided onboarding walkthrough or setup wizard for new workspace users. Missing for 10: any documentation of an in-app guided setup flow, first-run wizard, or onboarding checklist for engineers configuring a new Asana workspace.

   ⚑ flag

   Notion—none0/10

   The evidence pack contains developer API/MCP documentation and community sentiment, but no mention of an in-product guided walkthrough or onboarding wizard for setting up a workspace for the first time. The closest item (notion-docs-11) is a quickstart for making an API request, not a workspace setup walkthrough, so it doesn't count as evidence for this specific onboarding story.

   ⚑ flag

3. product managerImport my data from another tool when switching over

   weight 2 · round drawn
   Asana—none0/10

   No evidence describes an import/migration feature for bringing data from other tools (e.g., CSV import, Trello/Jira migration wizards); the pack only covers API access, app directory integrations, and AI teammates, none of which constitute a documented data-import capability for onboarding.

   ⚑ flag

   Notion—none0/10

   The evidence pack covers Notion's REST API, integrations (GitHub, Loom, Tableau, etc.), MCP/agent APIs, and webhook capabilities, but contains no documentation of a native import feature or migration wizard for bringing data over from other tools (e.g., Confluence, Asana, Evernote) during onboarding. Building an import via the API would require custom engineering, not a documented PM-facing onboarding capability.

   ⚑ flag

4. product managerJumpstart a new project using pre-built templates

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack contains no mention of Asana's project templates or template galleries for jumpstarting new projects; all docs entries focus on API, integrations, and AI Teammates. missing for 10: any documentation or community evidence of pre-built project templates, template gallery, or template creation workflow.

   ⚑ flag

   Notion—none0/10

   The evidence pack contains no mention of Notion's templates or template gallery feature for jumpstarting projects; it focuses entirely on API, integrations, MCP, and community feedback unrelated to templates. Although templates are a well-known Notion capability, this evidence pack provides no documentation or citation supporting it, so per the rules it must be judged 'none' rather than assumed from outside knowledge.

   ⚑ flag

Pricing transparency

1. product managerWhether my plan enforces a minimum seat count or annual billing commitment before I subscribe

   weight 3 · round drawn
   Asana—none0/10

   No evidence in the pack addresses Asana's pricing plans, minimum seat requirements, or annual billing commitments; all evidence concerns API/developer docs and general community sentiment.

   ⚑ flag

   Notion—none0/10

   The evidence pack contains no information about Notion's pricing plans, seat minimums, or annual billing commitments — all content covers API, MCP, integrations, and general product sentiment. This is a fair pricing-transparency question for a SaaS product, but no evidence addresses it.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Asana~partialclaimed6/10

   Asana's REST API is comprehensive and well-documented (CRUD on tasks, projects, webhooks, app components, OpenAPI spec, sandbox, explorer), covering most core workflow actions available in the UI. However there's no evidence that newer AI-native surfaces (AI Studio, AI Teammates/Dash) or all UI-specific features are fully exposed via the same API, so full UI/API parity isn't demonstrated. missing for 10: explicit confirmation that AI Studio/Teammates features and all UI settings/admin controls are API-accessible, independent verification of full parity.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”

   proof ↗⚑ flag

   Notion~partialprobed6/10

   Notion's own API docs claim you can 'read, create, and update nearly everything' via REST API, plus OpenAPI spec, webhooks, MCP server, and agent APIs give broad but explicitly non-complete coverage — the vendor's own wording ('nearly everything') signals known gaps versus full UI parity (e.g., view configuration, granular permissions, some formatting/UX-only features). missing for 10: independent verification of true UI/API parity, explicit list of API-unsupported UI features, hands-on confirmation from developers building full-parity integrations.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Asana
   Asana~partialclaimed4/10

   Asana's REST API returns JSON, an open format, so data could in principle be pulled out via API calls (asana-docs-15), and OpenAPI specs are published for structured access (asana-supp-openapi-spec). However, there is no documented dedicated bulk-export/full-account-export feature, no CSV/backup tool, and no explicit data-portability policy in the evidence pack. Missing for 10: a documented full-data export/backup mechanism, guarantees of completeness, and independent confirmation that users can fully migrate away using this API.

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

   Notion!disputedcontradicted4/10

   Notion's REST API (notion-docs-1, notion-docs-11) lets you read/create/update 'nearly everything' via personal access tokens, which could support scripted data extraction, but there is no documented one-click bulk export to open, portable formats in this evidence pack. Community reports directly contradict the 'easy to leave' narrative: users say Notion data is 'hard to get stuff out of it, especially on mobile' and that it is 'tied to its own cloud service' with 'no way to use it as a standalone app storing data locally,' explicitly citing this as a reason to leave/avoid switching. missing for 10: dedicated bulk export-to-open-format documentation (e.g., Markdown/CSV/HTML export), independent verification that exported data is complete and usable outside Notion, confirmation that API access alone suffices for a full data migration.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
   • [community] “I've started using notion as a kind of personal wiki... My only issue with Notion is that I feel it's hard to get stuff out of it, especiall…”
   • [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Asana—none0/10

   Asana is a closed, proprietary SaaS product; the only public repo referenced (Asana/openapi) contains API specification files, not the product's actual source code, and no evidence indicates any open-license release of Asana's codebase.

   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

   Notion—none0/10

   Notion is a closed-source, proprietary SaaS product; the only open-source artifact mentioned is the notion-mcp-server client tool, not Notion's own application source. No evidence anywhere in the pack indicates Notion's core product source is available under an open license.

   • [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”
   • [community] “For now I use Notion with the hopes they implement it eventually [offline read-only mode]. I can't consider switching to a self hosted alter…”
   • [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”

   proof ↗⚑ flag

Mobile access

1. engineerManage my tasks from a full-featured native mobile app without missing desktop functionality

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack contains no mentions of a native mobile app, mobile feature parity, or any mobile-specific capability—only API, developer platform, AI features, and general community sentiment about the web app's performance. Absence of evidence for this applicable axis (mobile apps are a plausible feature for a task/project management SaaS) means 'none'.

   ⚑ flag

   Notion—none0/10

   The evidence pack contains no vendor documentation or claims about a native mobile app with desktop-equivalent task management functionality; instead, community reports mention mobile being 'hard to get stuff out of' and citing 'offline/mobile-first' as a gap serious enough to abandon Notion. No positive evidence supports full mobile parity.

   • [community] “I've started using notion as a kind of personal wiki... My only issue with Notion is that I feel it's hard to get stuff out of it, especiall…”
   • [community] “As a heavy user of both Confluence and Notion... There's a big need in this feature [offline/mobile-first], and something that's best baked …”
   • [community] “I love the product, but the login workflow is awful... a randomly-generated one-time code sent to your email address... A side effect of thi…”

   proof ↗⚑ flag

Task management

1. product managerTrack cross-team dependencies to coordinate large launches

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains no mention of Asana's dependency-tracking, portfolios, or cross-team coordination features (e.g., task dependencies, portfolio views) that would support this story; documentation cited focuses on API access, integrations, and AI Teammates rather than planning/tracking capabilities like dependency management.

   ⚑ flag

   Notion~partialcommunity3/10

   Notion is described as a flexible workspace/'system of record' that teams use for project and task tracking (notion-docs-6, notion-comm-11), which could support dependency coordination, but no evidence specifically documents relation/dependency-tracking features, and one community report notes teams 'quickly reach limits' when using Notion as a project/issue tracker for team coordination (notion-comm-6). Missing for 10: explicit documentation of dependency-linking features (e.g., linked databases, relation properties, timeline/Gantt views), cross-team rollup examples, and independent validation that large multi-team launches are successfully coordinated in Notion.

   • [claimed-docs] “Bring everything into one system of record.”
   • [community] “We use it to keep track of all of our tasks and projects... notifications are still hit or miss... Search still needs some love... I'd love …”
   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”

   proof ↗⚑ flag

2. product managerCustomize fields and workflow statuses to match my team's process

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains only API/developer-platform docs, AI teammate features, and community sentiment about UI/performance — none of it addresses custom fields or configurable workflow statuses, which is the actual subject of this story. Although this is a fair and expected capability for a work-management product like Asana, no evidence in the pack demonstrates it.

   ⚑ flag

   Notion~partialcommunity4/10

   Community feedback describes Notion as highly flexible and configurable enough to serve as a project/issue tracker sitting between rigid PM tools like Jira and unstructured wikis, implying customizable fields/workflows, but the evidence pack contains no first-party documentation specifically describing database property types, status fields, or workflow customization features. Missing for 10: official docs on database property/status customization, screenshots or docs of board/status views, and independent hands-on confirmation of building a PM workflow with custom fields.

   • [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
   • [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”

   proof ↗⚑ flag

3. product managerTrack initiatives with status, priority, and an owning team

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains no mention of Asana's Portfolios/Goals features, custom fields for status or priority, or team ownership assignment for initiatives — it is entirely focused on the developer API, AI Teammates/agents, and general community sentiment. Without evidence of initiative-level tracking with status, priority, and owning team, this capability cannot be credited.

   ⚑ flag

   Notion~partialcommunity5/10

   Community evidence confirms Notion is used as a project/initiative tracker by teams (comm-6, comm-15, comm-3), consistent with its flexible database model that supports custom fields like status, priority, and owner, but the evidence pack contains no first-party documentation explicitly describing status/priority/owning-team properties, and one community report notes hitting limits when using Notion as a project/issue tracker. Missing for 10: explicit docs on database property types (status, priority, person/team fields), and independent confirmation of scaling well for initiative tracking at team level.

   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
   • [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”
   • [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
   • [claimed-docs] “Bring everything into one system of record.”

   proof ↗⚑ flag

4. engineerPlan and manage sprints for agile software development

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains no mention of sprint boards, backlogs, story points, or agile/scrum-specific features in Asana; it focuses on API/developer platform capabilities and AI agent features. Community comments only compare Asana's general UI to Jira without confirming sprint-planning functionality, and some users note Asana lacks features that PMs/engineers need versus Jira for dev workflows.

   • [community] “I've found Asana to be a much, much nicer product to work with than Jira (at least as a developer, not sure about from the management side.)…”
   • [community] “While better than Jira in UI, I haven't been able to like Asana as a product for some reason. In my previous company we moved away from Asan…”
   • [community] “i remember reading about asana on here years ago. wasn't it supposed to be the thing that saved us from JIRA but ended up turning into the v…”

   proof ↗⚑ flag

   Notion~partialcommunity4/10

   Notion's flexible databases (notion-docs-6) can be configured into kanban/sprint boards, and its API/automations (notion-docs-1, notion-docs-3) allow custom workflows, but there is no evidence of native agile/sprint-specific features (backlogs, sprint velocity, burndown, sprint ceremonies). Community feedback explicitly notes it hits limits as a project/issue tracker and lacks GitHub integration, a 'dealbreaker' for tech teams (notion-comm-6, notion-comm-7). missing for 10: dedicated sprint planning primitives, native issue/backlog management, engineering tool integrations (e.g., GitHub/CI), independent evidence of successful agile sprint use.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Bring everything into one system of record.”
   • [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
   • [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”

   proof ↗⚑ flag

5. engineerCreate tasks and assign them to teammates with due dates

   weight 3 · round drawn
   Asana~partialclaimed5/10

   Docs confirm Asana supports creating tasks via UI/API (asana-docs-1, asana-docs-11, asana-docs-15) and that third-party apps can create tasks and kick off workflows, but the evidence pack never explicitly documents the assignee or due-date fields on a task object. Missing for 10: explicit documentation of assignee and due-date task fields, and independent hands-on confirmation of assigning tasks with due dates.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

   Notion~partialcommunity5/10

   Notion's API and product docs confirm creating/updating database items (tasks) and pages (notion-docs-1, notion-docs-6), and community evidence confirms real-world use as a 'project tracker, issue tracker' (notion-comm-6), which implies task creation with properties like assignee/due date. However, no evidence explicitly documents assignee or due-date properties, notifications for assigned tasks, or a dedicated task-management UI walkthrough. Missing for 10: explicit documentation of person/assignee property, due-date property, and confirmation that assigned teammates get notified.

   • [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
   • [claimed-docs] “Bring everything into one system of record.”
   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”

   proof ↗⚑ flag

6. engineerBreak work into subtasks and link dependent tasks so blocking order is clear

   weight 3 · round drawn
   Asana—none0/10

   The evidence pack contains no documentation or community evidence describing Asana's subtask creation or task dependency/blocking-order features—it is entirely focused on API/developer platform capabilities, AI teammates, and unrelated community sentiment about UI/performance/Jira comparisons. Absence of evidence for this applicable, mainstream planning capability yields 'none'.

   ⚑ flag

   Notion—none0/10

   The evidence pack contains no mention of Notion's sub-tasks, relation properties, or dependency-linking features for tasks/databases; it focuses on API access, integrations, MCP, and unrelated community complaints. Since planning/tracking of dependent tasks is a fair expectation for a workspace tool like Notion, but no evidence substantiates this specific capability, it must be scored as none rather than na.

   ⚑ flag

7. engineerLog time directly against tasks and projects

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack contains no mention of time-tracking or time-logging features against tasks/projects in Asana; it covers API, automation, AI teammates, and app components, none of which address engineer time logging.

   ⚑ flag

   Notion—none0/10

   Notion offers databases, APIs, and integrations for general workspace/project data, but there is no evidence of a dedicated time-tracking/logging feature against tasks or projects; any such capability would require a third-party integration not documented here.

   ⚑ flag

Views organization

1. engineerHow the product performs and whether item caps apply in workspaces with tens of thousands of tasks

   weight 2 · round drawn
   Asana—none0/10

   No vendor documentation addresses item caps, workspace size limits, or performance characteristics at scale (tens of thousands of tasks); the evidence pack only contains generic API/AI-feature docs and anecdotal community complaints about poor performance (e.g., 'worst performing web app', suspected O(n^2) algorithms) with no concrete data or documented limits. This is an applicable engineering concern for a task-tracking tool, but no first-party or independent source quantifies scaling behavior or caps.

   • [community] “The funny thing is that Asana is possibly the worst performing web app out of all the ones I use on a regular basis. I have a strong suspici…”
   • [community] “i dont understand why you would even listen to them, their website is such a piece of shit- terrible performance, terrible ui. maybe their i…”

   proof ↗⚑ flag

   Notion—none0/10

   No first-party documentation addresses workspace scale limits, item/block caps, or performance guarantees for large databases; the evidence pack only contains generic API/marketplace docs and unrelated integration listings. Community reports (notion-comm-4, notion-comm-8, notion-comm-13, notion-comm-17) even describe hitting a hard 1000-block limit and persistent sluggishness/data loss, but these are anecdotal complaints, not an official statement Notion could be shown contradicting, so this doesn't rise to 'disputed' — it simply lacks any vendor evidence of delivering predictable performance at tens-of-thousands-of-tasks scale.

   • [community] “I had a really bad experience with Notion, used it for some time, hit some arbitrary 1000 block limit that no matter what I deleted I couldn…”
   • [community] “Notion consuming 10-15% CPU while on idle is a deal breaker to me. I wish they'd devote a bit more resources to fix this. (On macOS)”
   • [community] “There is something about Notion that makes it feel very well-made and coherent... On the flip side the software is a bit slow to start and u…”
   • [community] “I love Notion but the speed, or rather lack of, is killing me daily. Last Friday I was taking some notes, and suddenly the page refreshed an…”

   proof ↗⚑ flag

2. engineerSwitch between board, list, calendar, and timeline views of the same work

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains no mention of Asana's board, list, calendar, or timeline views or any ability to switch between them—only API/developer platform docs and general community sentiment about the product. This is a fair axis for a work-management tool, but no evidence supports it here.

   ⚑ flag

   Notion~partialcommunity3/10

   Community evidence only glancingly confirms Notion supports board/kanban and task-list structures (notion-comm-18), but nothing in the evidence pack explicitly documents calendar or timeline views or the ability to switch seamlessly between all four view types on the same dataset. missing for 10: docs/screens showing calendar view, timeline/Gantt view, and the actual view-switching mechanism on one database.

   • [community] “Notion could as well [integrate with Mattermost/discord] but they are a slow moving beast with different priorities.”

   proof ↗⚑ flag

3. engineerSave a filtered view of work and share it with a link

   weight 2 · round drawn
   Asana—none0/10

   No evidence in the pack addresses saved/filtered views, custom fields/search filters, or shareable links to such views in Asana; the evidence is entirely about API, AI teammates, and general sentiment.

   ⚑ flag

   Notion—none0/10

   The evidence pack covers Notion's API, MCP, integrations, and community feedback, but contains no mention of database views, filters, or the ability to save/share a filtered view via link. This is an applicable capability for a workspace/planning tool, but no evidence supports it here.

   ⚑ flag

4. engineerSearch across all tasks, docs, and comments and get fast, accurate results

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains no mention of Asana's search feature across tasks, docs, and comments, nor any data on search speed or accuracy; it only covers API access, automations, AI teammates, and general product sentiment unrelated to search. This is a fair axis for a planning/tracking tool, but no supporting evidence exists.

   ⚑ flag

   Notion!disputedcontradicted5/10

   Notion advertises workspace-wide search plus AI-powered 'Get answers, instantly—with citations' and MCP search across Notion and connected sources, but a hands-on team user managing tasks/projects explicitly reports 'Search still needs some love,' directly contradicting the fast/accurate claim. missing for 10: independent benchmarking of search speed/accuracy across large workspaces, resolution of the community complaint, and evidence of comments-specific search quality.

   • [claimed-docs] “Get answers, instantly—with citations.”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
   • [community] “We use it to keep track of all of our tasks and projects... notifications are still hit or miss... Search still needs some love... I'd love …”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Asana—none0/10

   No evidence in the pack discusses data residency, regional storage options, or data locality controls for Asana; the pack covers API/dev tooling and AI Teammates features only. missing for 10: any mention of region selection, data residency policy, or geographic storage controls.

   ⚑ flag

   Notion—none0/10

   No evidence in the pack addresses data residency, regional storage options, or geographic control over where workspace data resides; one community comment even notes Notion is tied to its own cloud with no local storage option. This is a fair question for a SaaS platform storing user data, so it applies, but nothing supports it. missing for 10: any mention of region selection, data residency guarantees, EU/US data center choice, or compliance documentation on data locality.

   • [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Asana—none0/10

   No evidence pack item addresses AI training data opt-out, data usage policies for AI/ML model training, or any privacy controls specific to preventing data use in training. Evidence covers API docs, AI Teammates features, and general community sentiment, none of which touches this axis. Missing for 10: explicit documentation of an AI-training opt-out/opt-in setting, data processing terms addressing model training, and any admin control to restrict data use for AI training.

   ⚑ flag

   Notion—none0/10

   No evidence pack item addresses AI training data opt-out or any privacy control preventing user content from being used to train AI models; only general API/MCP/session-recording concerns are present, none of which speak to this specific claim.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Asana—none0/10

   No evidence pack items address data retention policies, deletion controls, or data lifecycle management for AI features/agents; only general API, developer sandbox, and AI Teammate governance mentions (audit trail, permissions) are present, none of which describe retention/deletion controls.

   ⚑ flag

   Notion—none0/10

   No evidence pack items address data retention policies, deletion controls, export/purge tools, or data lifecycle management for AI-native usage; the pack covers API access, integrations, and MCP but nothing about retention/deletion settings. missing for 10: documentation on data retention policies, deletion/purge controls, workspace data lifecycle settings, AI training data retention/opt-out specifics.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Asana—none0/10

   No evidence pack items mention telemetry, usage tracking, opt-out settings, or privacy controls for AI features; the pack covers API/developer docs and general community sentiment only.

   ⚑ flag

   Notion—none0/10

   No documentation or feature in the evidence pack describes a telemetry/usage-tracking opt-out control; the only related signal is a community complaint that Notion embeds undisclosed session-recording (FullStory) tracking, which points the opposite direction from a user-facing opt-out.

   • [community] “I mentioned this before. Notion is great, but the fact that they use fullstory (session recording) for a note taking app is a huge problem f…”

   proof ↗⚑ flag

Ai insights

1. ai-native userAsk AI a question and get an instant answer with citations from my workspace content

   weight 2 · round to Notion
   Asana~partialclaimed4/10

   Asana markets 'Asana Dash — Your AI Chief of Staff' and AI Teammates that draw context from the Work Graph and shared memory, suggesting an in-workspace Q&A assistant, but no evidence describes citation of specific workspace items in answers or an 'ask a question, get instant answer with citations' UX. Missing for 10: explicit documentation of citation/sourcing behavior in AI answers, hands-on or independent verification of accuracy/citations.

   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion~partialclaimed5/10

   Notion's marketing explicitly claims 'Get answers, instantly—with citations' and 'Keep work moving 24/7 with agents,' indicating a Q&A-with-citations AI feature exists, and agent/search APIs (search across Notion and connected sources, agent session APIs) support this. However, there is no detailed documentation, screenshots, or independent/hands-on corroboration showing the citation UX in practice, only marketing taglines and adjacent API references. Missing for 10: hands-on or third-party verification of the Q&A citation experience, detailed docs on how citations are sourced/displayed, and independent confirmation of accuracy/reliability.

   • [claimed-docs] “Get answers, instantly—with citations.”
   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”

   proof ↗⚑ flag

2. ai-native userHave AI draft a project or initiative status update from recent activity

   weight 2 · round drawn
   Asana~partialclaimed4/10

   Asana markets AI Teammates and 'Asana Dash - Your AI Chief of Staff' plus AI Studio automations that could plausibly draft updates from activity, and a developer tutorial exists for generating reports of status updates, but no evidence explicitly confirms an AI feature that drafts a project/initiative status update from recent activity. Missing for 10: a concrete first-party doc or demo showing AI-generated status update drafting, and independent/community confirmation it works as described.

   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

   Notion~partialclaimed4/10

   Notion advertises AI capabilities like Q&A with citations and always-on agents that work across the workspace (notion-docs-7, notion-docs-8), and its Agent APIs let a Custom Agent read/act on workspace content via sessions (notion-docs-21, notion-docs-22), which could plausibly be used to draft a status update from recent activity. However, there is no concrete documentation or example specifically showing AI generating a project/initiative status update from recent activity — missing for 10: a documented status-update/report-drafting workflow, example prompts/templates, or independent evidence that this specific reporting use case works in practice.

   • [claimed-docs] “Get answers, instantly—with citations.”
   • [claimed-docs] “Keep work moving 24/7 with agents.”
   • [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
   • [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
   • [claimed-docs] “Bring everything into one system of record.”

   proof ↗⚑ flag

Dashboards

1. product managerBuild dashboards and widgets to report on project progress

   weight 2 · round to Asana
   Asana~partialclaimed3/10

   The evidence pack only shows API-level access to status updates for building custom reporting apps (asana-docs-4, asana-docs-9), not any native dashboard/widget-building UI for PMs to visualize project progress. Missing for 10: documentation of Asana's built-in Reporting/Dashboards or Portfolio charting features, native widget customization, and any hands-on evidence of PMs actually building such dashboards.

   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool.”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

   Notion—none0/10

   The evidence pack covers Notion's API, developer tooling, and general workspace flexibility, but contains no documentation or mention of dashboard/widget-building features for tracking project progress; one community comment even notes Notion 'quickly reach[es] limits of what is possible automatically' when used for project tracking. Missing for 10: any first-party docs on dashboard/reporting widgets, rollups/charts for progress tracking, or hands-on evidence of PMs building such dashboards.

   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”

   proof ↗⚑ flag

2. product managerRoll up progress across multiple projects into a single portfolio view

   weight 2 · round to Notion
   Asana—none0/10

   The evidence pack contains no documentation or references to Asana's Portfolios feature, cross-project rollups, or multi-project dashboards — only API/developer docs, AI teammate marketing, and unrelated community sentiment. Missing for 10: any docs-1 or product page describing portfolio creation, progress rollup, or multi-project status aggregation.

   ⚑ flag

   Notion~partialcommunity3/10

   Notion is broadly marketed as a flexible system of record and used by teams for project tracking (notion-docs-6, notion-comm-3), but no evidence describes rollup properties, portfolio dashboards, or cross-project progress aggregation specifically, and community feedback notes real limits when using Notion as a project tracker. Missing for 10: explicit documentation of rollup/aggregation properties, portfolio-view templates, or dashboard features summarizing multiple projects' progress, and hands-on confirmation this works at scale.

   • [claimed-docs] “Bring everything into one system of record.”
   • [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
   • [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”

   proof ↗⚑ flag

Access control

1. product managerReview an admin audit log of actions taken across the workspace

   weight 2 · round drawn
   Asana—none0/10

   The evidence only mentions an audit trail scoped to AI Teammate/agent actions (asana-docs-13), not a workspace-wide admin audit log of user actions that a product manager could review for security purposes; no docs on an Admin Console audit log feature are present.

   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion—none0/10

   The evidence pack covers Notion's API, integrations, MCP, and agent tooling extensively, but contains no mention of an admin audit log feature for tracking workspace actions — this is a distinct enterprise security/compliance capability that is entirely unevidenced here.

   ⚑ flag

2. product managerAssign granular permissions and roles to control who can view or edit work

   weight 2 · round drawn
   Asana—none0/10

   The evidence pack contains no documentation of Asana's actual user-level permission/role system (e.g., project privacy settings, member roles, task-level view/edit controls). The closest mention (asana-docs-13) is about governance of AI Teammates/agents, not human-user granular permissions, so it does not substantiate this story. Missing for 10: docs on project/task privacy settings, member role definitions (admin/editor/viewer), and any independent confirmation these controls work as described.

   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

   Notion—none0/10

   The evidence pack covers API/OAuth scopes, webhooks, and MCP connection access controls, but contains no documentation of Notion's actual workspace member roles, page/database-level sharing or edit/view permission settings that a product manager would use to control who can view or edit content. notion-docs-30 only mentions managing MCP client connection access, not user role-based content permissions.

   • [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
   • [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token.”

   proof ↗⚑ flag

3. product managerCreate private sub-teams restricted to specific members

   weight 1 · round drawn
   Asana—none0/10

   No evidence in the pack addresses Asana's team/sub-team structures, privacy settings, or member restrictions; all documentation focuses on API, developer tools, and AI features. This is an applicable axis for a work-management tool but is unevidenced here.

   ⚑ flag

   Notion—none0/10

   No evidence describes creating private sub-teams or restricted membership groups within Notion; the pack covers API tokens, integrations, MCP, and general product feedback but nothing about team/permission structuring like private teamspaces limited to specific members.

   ⚑ flag

4. engineerSecure organization access with SSO and SAML

   weight 3 · round drawn
   Asana—none0/10

   The evidence pack contains no documentation or claims about Asana supporting SSO or SAML for organization access; all docs are about the API, integrations, and AI features. The only tangential mention (asana-comm-4) discusses a competitor's free Azure AD SSO, not Asana's own SSO/SAML capability, and does not confirm Asana ships this feature.

   ⚑ flag

   Notion—none0/10

   No evidence pack items mention SSO, SAML, or enterprise identity/authentication management for workspace access — the pack only covers API tokens, OAuth for connections/integrations, and MCP client access, none of which address organization-wide SSO/SAML.

   ⚑ flag

Trust reliability

1. product managerThe vendor's published uptime SLA and can check real-time incident status via a public status page

   weight 3 · round drawn
   Asana—none0/10

   No evidence pack item mentions an SLA, uptime guarantee, or a public status page with real-time incident reporting; all developer docs focus on API usage, deprecations, and app components rather than platform reliability commitments.

   ⚑ flag

   Notion—none0/10

   No evidence pack item mentions a published uptime SLA or a public status page for incident reporting; the evidence covers API docs, integrations, MCP, and community complaints unrelated to SLA/status transparency.

   ⚑ flag

2. product managerThe vendor's documented support response times for each plan tier

   weight 2 · round drawn
   Asana—none0/10

   No evidence in the pack references support response times, SLAs, or plan-tier support commitments; all documentation relates to API, integrations, and AI features.

   ⚑ flag

   Notion—none0/10

   No evidence pack items mention support response times, SLAs, or plan-tier support commitments; the evidence covers API, MCP, integrations, and community complaints unrelated to support SLAs.

   ⚑ flag