Asana vs monday.com

Agent access

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

   weight 2 · round to Asana
   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

   monday.com~partialprobed6/10

   monday.com has extensive agent-oriented developer documentation (MCP server docs, agent APIs, webhooks, scopes) confirmed by both docs and a probe verifying the MCP docs page exists, but a direct probe shows no llms.txt file is served (404), so the specific 'point an agent at llms.txt' capability is absent even though broader agent-oriented docs exist. missing for 10: a working llms.txt endpoint, independent confirmation that agent-oriented docs are consumable/structured for LLM ingestion.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   monday.com~partialclaimed6/10

   monday.com exposes a GraphQL API, SDKs, webhooks, and lets you 'run and manage every monday agent programmatically from your own code, anywhere you need it' (monday-docs-9, monday-docs-35, monday-docs-28), which supports scripted/headless automation. However there is no explicit documentation of CI/CD integration, headless test runners, or pipeline examples, and no independent verification that these APIs work reliably in automated pipelines. Missing for 10: explicit CI/CD documentation or examples, independent/hands-on confirmation of headless operation, and any mention of exit codes/scriptable non-interactive workflows.

   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   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

   monday.com—none0/10

   The evidence shows monday.com exposing its own hosted/developer MCP server so external agents (Claude, ChatGPT, etc.) can connect to monday, and monday's agents can be reached via multiple channels including 'our MCP' — this is monday acting as an MCP server/provider, not monday consuming third-party MCP servers to extend its own agents' toolset. There is no documentation of monday's agents importing or plugging in external MCP servers as tool sources.

   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Bring an agent in once and reach it from Slack, WhatsApp, Telegram, Make, our MCP, or the API. One identity, every surface — no rebuilding p…”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”

   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

   monday.com✓fullprobed8/10

   Monday.com documents an official hosted MCP server with a dedicated docs page (confirmed by probe) plus first-party guidance on connecting agents from Claude, ChatGPT, etc. via this MCP endpoint, granular scopes, and managed secrets. Missing for 10: independent/hands-on third-party verification that the MCP server works as documented in practice.

   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [claimed-docs] “Work with tools like Claude, Copilot, and ChatGPT through official integrations or the monday MCP, and keep data secure with trusted AI conn…”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”

   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

   monday.com—none0/10

   The evidence pack covers monday's APIs, SDKs, MCP servers, and apps framework, but nowhere mentions an official CLI tool for developers or AI-native workflows. Since a platform of this kind could plausibly offer a CLI, absence of evidence means the axis is unmet rather than inapplicable.

   ⚑ 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

   monday.com✓fullprobed9/10

   monday.com documents a full GraphQL API (monday-docs-35), SDKs (monday-docs-28), granular OAuth scopes and secret storage (monday-docs-6), webhooks/event subscriptions (monday-docs-7, monday-docs-27), and an official MCP server (monday-probe-2) alongside apps framework docs — giving AI-native users multiple documented, programmatic ways to drive the product. Missing for 10: no independent/hands-on developer corroboration of API robustness or reliability beyond first-party docs.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

   proof ↗⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed7/10

   Docs explicitly describe requesting granular scopes (e.g. boards:read), storing keys in managed secret storage, admin-level scoping of each agent's board access, and audit logging of every action — directly matching scoped/least-privilege credential issuance for agents. Missing for 10: no independent/hands-on verification of scope granularity or credential rotation, and no detail on token expiry/revocation workflows.

   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to monday.com
   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

   monday.com✓fullprobed7/10

   Monday documents official SDKs/tooling for AI-native builders: a GraphQL API, an 'apps framework' for code-first development, an open-source React component library (Vibe) for native-looking UI, and a documented developer MCP server for scaffolding/deploying agents. Together these constitute a real official SDK/toolchain for building AI-native apps and agents on the platform. Missing for 10: independent/hands-on developer corroboration of SDK quality or adoption, and llms.txt returns 404 suggesting incomplete AI-facing doc tooling.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Build with Vibe, monday's open-source React components, and look native instantly.”
   • [claimed-docs] “Match monday with Vibe, our open-source React components, so your app looks native from day one.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed8/10

   Docs explicitly describe webhook subscriptions to real-time board events (create_item, change_column_value, etc.) plus agent-triggering webhooks, backed by a GraphQL API for integration. Missing for 10: independent/hands-on verification of webhook reliability and payload details beyond vendor docs.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”

   proof ↗⚑ flag

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

    weight 1 · round to monday.com
    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

    monday.com~partialprobed7/10

    monday.com documents one persistent agent identity reachable across Slack, WhatsApp, Telegram, Make, MCP, and API 'no rebuilding per channel' (monday-docs-12), plus 2-way sync, webhooks, a unified Models API, and an official MCP server (monday-docs-1, monday-docs-2, monday-docs-17, monday-docs-31, monday-probe-2) that together support handing off work/context between tools and agents. Missing for 10: independent/hands-on verification that context is actually preserved across handoffs (all evidence is vendor docs), and no case study showing a real multi-tool handoff working end-to-end.

    • [claimed-docs] “Bring an agent in once and reach it from Slack, WhatsApp, Telegram, Make, our MCP, or the API. One identity, every surface — no rebuilding p…”
    • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
    • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
    • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
    • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
    • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
    • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

    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

   monday.com~partialclaimed6/10

   Docs claim AI agents can surface deep intelligence, actionable insights, risk/progress gap detection, and automated reports/summaries directly in monday (docs-20, docs-21, docs-22, docs-23, docs-32), which matches the story of in-product AI-generated insights. However, evidence is entirely vendor marketing copy with no independent/hands-on validation of insight quality or accuracy, and community feedback focuses on performance/UX issues rather than AI insight capability. Missing for 10: independent verification of insight quality, concrete examples/screenshots of generated insights, and hands-on user reports confirming the feature works as described.

   • [claimed-docs] “Surface deep intelligence and actionable insights from any subject.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Schedule meetings, summarize calls, and extract action items.”
   • [claimed-docs] “Score our open deals and send proposals to anyone above 80%.”

   proof ↗⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed8/10

   monday.com documents native automations (event triggers like create_item/change_column_value, real-time listeners), plus AI agents that run in isolated sandboxes managed by monday, scoped with permissions, audited, and triggered autonomously by mentions/assignments or scheduled reports (status updates on a set schedule). This directly supports background/autonomous automation setup. Missing for 10: independent/hands-on verification of autonomous background execution reliability and no community corroboration of agent-based automations specifically (community evidence is generic negative sentiment unrelated to this feature).

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “You lead. Agents act.”

   proof ↗⚑ flag

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

   weight 3 · round to monday.com
   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

   monday.com✓fullclaimed8/10

   monday.com offers built-in AI agents that can be messaged, assigned items, and @mentioned to perform real work directly within the product ('Talk to agents like teammates... assign them items'), with docs describing creating custom agents via natural language and managing them from an admin dashboard. Community evidence is generic product criticism unrelated to the AI assistant feature, so it doesn't dispute this capability. Missing for 10: independent hands-on verification of agent quality/reliability and no third-party review of the assistant feature specifically.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “You lead. Agents act.”

   proof ↗⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed7/10

   monday.com documents natural-language operation extensively: users can message, assign, and @mention agents in plain language to kick off real work, and can describe entire workflows in their own words to create agents. This directly matches the story of operating the product via natural-language commands. Missing for 10: independent/hands-on verification that NL commands reliably produce correct actions, and more detail on limits of NL understanding beyond marketing copy.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “You lead. Agents act.”

   proof ↗⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed7/10

   monday's docs describe a dedicated agent-building capability: defining goals/rules in natural language, describing workflows to create custom agents, scoping board access, hosting/sandboxing, granular permissions, and monitoring via an admin dashboard (monday-docs-13, 14, 10, 5, 6, 9). This directly matches the story of building/configuring a custom AI agent within the product. Missing for 10: independent or hands-on verification that the agent builder works as described in practice, and detail on customization limits/complexity for non-technical users.

   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”

   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

   monday.com—none0/10

   The evidence shows monday has a GraphQL API and developer docs, but there is no mention of an interactive API reference, playground, or runnable code examples anywhere in the pack.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”

   proof ↗⚑ flag

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

   weight 2 · round to Asana
   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

   monday.com✓fullclaimed7/10

   monday documents an expressive GraphQL API for developers with public developer docs, which serves as a machine-readable/documented spec analog for programmatic access, though it's GraphQL rather than a formal OpenAPI/REST spec download. missing for 10: an explicit downloadable OpenAPI/Swagger file or schema export, and independent confirmation of spec completeness.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   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

   monday.com~partialclaimed5/10

   Docs mention that agents deploy to 'isolated sandboxes monday manages' and that versions can be scaffolded and promoted from chat, implying a dev/test environment separate from production infra, but there is no explicit description of a sandbox for testing against non-production data or verification this isolation covers board/data-level testing. missing for 10: explicit sandbox/staging environment for data testing, independent or hands-on confirmation that production data is untouched.

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   proof ↗⚑ 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

   monday.com—none0/10

   The evidence pack describes monday's GraphQL API, apps framework, and MCP integrations but contains no mention of API versioning scheme or a documented deprecation policy for its APIs. Missing for 10: explicit versioning scheme documentation, deprecation policy/timeline, changelog or migration guides.

   ⚑ 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

   monday.com—none0/10

   No evidence pack item documents specific API rate limits, request quotas, or concurrency caps for monday's GraphQL API, MCP server, or agent platform; docs mention general scopes and secret storage but never numeric or documented limits.

   ⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com!disputedcontradicted4/10

   monday's GraphQL API, webhooks, and automation triggers (create_item, change_column_value) suggest programmatic bulk item manipulation is possible, but there's no explicit documentation of a batch/bulk operations endpoint, and independent hands-on reports describe the platform struggling and crashing once boards exceed a few thousand items (up to ~20k before failure), directly undercutting claims of smooth operation 'across many items at once'. Missing for 10: explicit bulk/batch API documentation, evidence of large-scale (10k+) item operations succeeding, and any first-party rebuttal to the scaling complaints.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   monday.com✓fullclaimed7/10

   monday.com's automation engine and agent framework support event-based triggers (create_item, change_column_value, real-time events, agent mentions/assignments) that fire automated actions, well documented across native automations and the developer platform. missing for 10: independent/hands-on verification of rule complexity and reliability at scale, and clearer detail on conditional logic depth beyond simple trigger-action pairs.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to monday.com
   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

   monday.com~partialclaimed5/10

   monday's docs mention scheduled automation only in the narrow context of status updates and performance reports ('Automate status updates and performance reports on a set schedule'), which supports recurring job scheduling but doesn't document a general-purpose recurring workflow/job scheduler for arbitrary AI-native automations. Missing for 10: explicit cron-like scheduling API/UI for arbitrary workflows, examples of recurring agent tasks beyond reporting, and independent confirmation of reliability at scale.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”

   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

   monday.com—none0/10

   Evidence covers agent building, deployment, MCP connectivity, and app scaffolding (with 'promote versions from chat' hinting at some deployment lifecycle), but there is no mention of automation version history, review workflows, diffing, or rollback of automations. No documented capability to revert an automation to a prior version.

   ⚑ flag

Ai task automation

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

   weight 2 · round drawn
   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

   monday.com~partialclaimed5/10

   monday.com documents AI agents that can be assigned items, triggered on item creation/column changes, and used to "spot risks and progress gaps" or manage support tickets via Zendesk integration, which supports building an automated triage-like workflow, but there is no explicit documentation of an out-of-the-box 'triage and prioritize bugs' capability or example. missing for 10: a concrete bug/task triage workflow example, explicit prioritization logic, and independent/hands-on evidence that this works in practice.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Connect Zendesk or Active Directory to manage your support tickets in monday.com, helping teams resolve issues faster and keep customers hap…”

   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

   monday.com—none0/10

   The evidence describes monday's AI agents/automation framework (agent creation, MCP, integrations, admin scoping) but nothing about the assistant learning a user's tone, shorthand, or writing preferences to tailor output. Missing for 10: any mention of personalization/memory of user style, adaptive tone learning, or preference-based output customization.

   ⚑ flag

Workflow automation

1. product managerBuild multi-step automations without writing code

   weight 2 · round drawn
   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

   monday.com~partialcommunity6/10

   monday.com's docs describe automation recipes (triggers like create_item/change_column_value, scheduled reports, agent assignment flows) that let a PM configure multi-step automations without code, and its no-code automation builder is a well-known core feature referenced via triggers/subscriptions. However, the evidence pack is heavily focused on the newer AI-agent/developer platform rather than the classic drag-and-drop automation board builder itself, and community feedback raises usability/reliability concerns that could affect building complex automations at scale. missing for 10: direct documentation of the classic visual automation recipe builder UI, independent hands-on validation of multi-step automation reliability, and confirmation that no coding is required for complex branching logic.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   proof ↗⚑ flag

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

   weight 3 · round to Asana
   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

   monday.com~partialclaimed5/10

   Evidence shows trigger/event subscriptions (create_item, change_column_value) and scheduled automations for status updates/reports, which map to trigger-and-action rules, but the pack lacks documentation of monday's classic no-code Automations recipe builder (e.g., cross-board triggers, conditional actions, integration recipes) that engineers would typically use. Missing for 10: dedicated automation-builder documentation, examples of multi-step conditional recipes, and independent/hands-on validation that these rules reliably eliminate manual steps.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”

   proof ↗⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com~partialclaimed6/10

   Docs show scheduled automation for reports/status updates and event-based triggers (webhooks on create_item, change_column_value, agent mentions), which together support building recurring/scheduled workflows for routine work. However, evidence doesn't detail monday's core automation recipe builder, cron-style scheduling controls, or monitoring/error-handling for these workflows. Missing for 10: detailed schedule configuration UI/API, recipe builder specifics, failure/retry handling, and independent confirmation of reliability at scale.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”

   proof ↗⚑ flag

4. 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

   monday.com—none0/10

   No evidence pack item discusses plan limits, rate limits, overage charges, throttling behavior, or hard stops for automation/API usage—only feature and integration descriptions are present.

   ⚑ flag

Cross tool sync

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

   weight 2 · round to Asana
   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

   monday.com—none0/10

   Evidence lists many integrations (Salesforce, GitHub, Slack, Zendesk, communication tools) and a general integrations marketplace, but nothing mentions Figma, Adobe XD, Sketch, or any design-tool-specific integration that would let a designer update project status directly from their design tool.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”

   proof ↗⚑ flag

Docs knowledge

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

   weight 3 · round drawn
   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

   monday.com—none0/10

   The evidence pack covers monday's AI agents, integrations, MCP, and developer platform extensively, but contains no mention of a native Docs or notes feature for organizing shared documents alongside project boards. Absence of evidence for this applicable capability yields 'none'.

   ⚑ flag

In context discussion

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   No evidence pack item mentions commenting on specific text or images within an item's description; all documentation focuses on agents, integrations, boards, and infrastructure rather than inline commenting/annotation features.

   ⚑ flag

Real time sync

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

   weight 3 · round drawn
   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

   monday.com—none0/10

   The evidence pack contains no documentation or claims about real-time sync of board changes across open sessions; all monday-docs items concern the AI agent/developer platform (MCP, webhooks, agents), not live collaborative UI updates. Community evidence discusses performance/slowness but not specifically real-time refresh behavior, so there's no basis to confirm the capability.

   ⚑ flag

Team chat

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

   weight 2 · round to monday.com
   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

   monday.com~partialclaimed5/10

   monday.com's 'Updates' feature (message, @mention, assign items 'in any conversation') is documented as a native in-item communication mechanism, and the platform also integrates with Slack/Teams/Gmail for broader team chat, suggesting engineers can converse without leaving the work-planning surface. However, the evidence pack frames this messaging capability almost entirely around AI agents rather than human-to-human team chat, and no first-party or independent source describes robust native person-to-person chat/threads as a core UX pillar. Missing for 10: explicit documentation of human team chat/threads within boards, independent corroboration of real-time chat usability, and evidence it's used as a primary chat tool rather than via external integrations.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Integrate your org's communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”

   proof ↗⚑ flag

App ecosystem

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   No evidence of a bi-directional sync with GitHub/GitLab/Jira-style issue trackers; docs focus on agents, MCP hosting, and generic integrations but never mention repo issue-tracker sync specifically.

   ⚑ 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

   monday.com—none0/10

   The evidence pack focuses entirely on monday's AI agent framework, MCP hosting, and integration channels for building agents—none of it describes a unified cross-tool task view pulling assigned tasks from multiple external project management tools (e.g., Jira, Asana, Trello) into one dashboard for an engineer. No integration or aggregation feature matching this story is documented.

   ⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed8/10

   monday.com documents native integrations for Slack, GitHub/GitLab, and Google (Drive/Calendar/Gmail) via its integrations directory, plus a broader library of 850+ apps/integrations and GraphQL API/webhooks for custom connections. Community evidence criticizes general performance/UX but does not contradict integration functionality specifically. Missing for 10: independent hands-on verification of these specific native connectors and any noted integration-specific limitations.

   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Work with tools like Claude, Copilot, and ChatGPT through official integrations or the monday MCP, and keep data secure with trusted AI conn…”
   • [claimed-docs] “Integrate your org's communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”

   proof ↗⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed9/10

   monday.com documents an app marketplace/integrations directory with 850+ apps and integrations (Salesforce, Slack, GitHub, Zendesk, etc.), no-code connection options, and flexible APIs/SDKs for custom integrations, directly matching the story. Community evidence cited is about general UI performance/usability complaints, not integrations, so it does not contradict this axis. Missing for 10: independent third-party verification of the marketplace's breadth/quality beyond vendor claims.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
   • [claimed-docs] “Connect Zendesk or Active Directory to manage your support tickets in monday.com, helping teams resolve issues faster and keep customers hap…”

   proof ↗⚑ flag

Extensibility

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

   weight 1 · round to monday.com
   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

   monday.com~partialclaimed6/10

   monday's developer docs explicitly support building custom board/item views, dashboard widgets, and full-page apps, and provide the Vibe React component library specifically to make custom UI 'look native instantly.' However, evidence is limited to vendor docs with no independent/hands-on corroboration of designer experience building these views, and community feedback focuses on core product usability rather than the custom-view/widget building workflow itself. Missing for 10: independent or hands-on verification of the widget-building experience, and details on design constraints/limitations designers encounter when building native-feeling views.

   • [claimed-docs] “Create custom board views, item views, dashboard widgets, and full-page apps.”
   • [claimed-docs] “Build with Vibe, monday's open-source React components, and look native instantly.”
   • [claimed-docs] “Add actions to the item, board, and column menus, right where work happens.”

   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

   monday.com—none0/10

   No evidence pack items mention workspace export functionality, or preservation of comments, attachments, or audit trails during export; all documentation focuses on agents, integrations, and MCP servers. Missing for 10: any documentation of an export feature, evidence of what data (comments/attachments/audit logs) is retained, and any hands-on or community confirmation of export fidelity.

   ⚑ 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

   monday.com—none0/10

   The evidence pack covers monday's developer platform, AI agents, and integrations but contains no mention of a guided onboarding walkthrough or first-time workspace setup flow for engineers. One community comment (monday-comm-10) even notes the product 'required too much setup and customization,' but this is not concrete counter-evidence of a documented walkthrough claim—there simply is no walkthrough feature evidenced.

   • [community] “I used monday.com a few years ago. Back then it was called 'dapulse'... I felt silly every time I said it. I just remember really wanting to…”

   proof ↗⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com~partialclaimed3/10

   Evidence shows monday.com offers many third-party integrations (Salesforce, HubSpot, Zendesk, GitHub, etc.) and flexible APIs/SDKs that could be used to move data in from other tools, but there is no explicit mention of an import wizard, CSV import, or dedicated 'migrate from X' onboarding flow for switching PMs. Missing for 10: explicit import/migration tooling (e.g., CSV/board import, one-click migration from competitor PM tools), independent confirmation that data import actually works smoothly during onboarding.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   proof ↗⚑ 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

   monday.com—none0/10

   The evidence pack contains no mention of pre-built project templates, template galleries, or quick-start project setups for product managers; all docs items focus on AI agents, integrations, and developer/MCP features. missing for 10: any documentation of a template library, template selection during board/project creation, or industry-specific templates.

   ⚑ 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

   monday.com—none0/10

   No evidence in the pack addresses seat minimums or annual billing commitment terms; only a Free-plan credit-card mention is present, which does not answer the story's question about seat/billing enforcement.

   ⚑ 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

   monday.com~partialclaimed6/10

   monday's GraphQL API, webhooks, granular scopes, and apps/MCP framework show broad programmatic access to boards, items, columns, and events, suggesting extensive API coverage of UI actions. However, there is no explicit claim or evidence that every UI capability (e.g., all board customizations, dashboard widgets, admin settings) is exposed via API, and no independent verification of API-UI parity. missing for 10: explicit vendor statement of full API/UI parity, independent test confirming coverage of edge-case UI features.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

   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

   monday.com—none0/10

   The evidence pack contains no mention of a bulk data export feature, open-format export (CSV/JSON backup), or account portability tooling — only a GraphQL API for programmatic integration, which is not the same as a documented 'export everything and leave' capability. missing for 10: explicit data export/backup feature, open-format (CSV/JSON) full-account export documentation, any statement about data portability or account closure export.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   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

   monday.com—none0/10

   monday.com is a closed-source SaaS product; the only open-source item mentioned is 'Vibe' (a UI component library), not the core product's source code. No evidence of the platform's source being available under an open license.

   ⚑ 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

   monday.com—none0/10

   No evidence pack items mention a native mobile app or any mobile-specific functionality/parity claims; all docs focus on web platform, APIs, agents, and integrations. Community comments discuss performance/usability issues on the general product but say nothing about mobile app feature parity.

   ⚑ flag

Task management

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   The evidence pack contains no documentation of dependency-tracking features (e.g., linked items, dependency columns, Gantt/timeline views) that would let a PM coordinate cross-team dependencies; nearly all monday-docs items focus on AI agents/MCP integration, unrelated to planning dependencies. One community comment (monday-comm-4) explicitly states 'Linking tickets to one another in Monday is really bad, data gets lost all the time,' which is negative anecdotal evidence but there's no vendor claim of dependency tracking to formally dispute. Missing for 10: any first-party documentation of dependency/linking features, timeline/Gantt views, or cross-team coordination workflows, and any positive hands-on evidence of this capability working.

   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   The evidence pack is dominated by AI-agent, MCP, and developer-platform documentation and contains no first-party or hands-on evidence describing monday.com's native field/column customization or workflow status editing capabilities for boards. While this is a fair axis for a work-management product, nothing in the pack concretely documents the ability to customize fields or workflow statuses, so it cannot be credited despite being a plausible feature.

   ⚑ flag

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   The evidence pack contains no documentation of monday.com's core board features (status columns, priority columns, owner/people columns) for tracking initiatives; nearly all provided evidence concerns the AI-agent/developer platform (MCP, agents, apps framework) rather than basic work-tracking functionality. Community evidence only speaks to general usability complaints, not specifically to status/priority/owner tracking.

   ⚑ flag

4. engineerPlan and manage sprints for agile software development

   weight 2 · round drawn
   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

   monday.com—none0/10

   The evidence pack contains no mention of sprint planning, backlog management, story points, or agile-specific board templates for monday.com; it only covers AI-agent/MCP features, generic board views, and integrations (e.g., GitHub/GitLab PR linking) that don't address sprint/agile workflow support. Absence of evidence for this applicable planning-tracking capability means it cannot be credited as delivered.

   ⚑ flag

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

   weight 3 · round to Asana
   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

   monday.com—none0/10

   The evidence pack contains no documentation or community reports describing monday.com's core item/task creation, assignee, or due-date fields — nearly all first-party docs here focus on AI agents/MCP integration rather than basic task management, and community comments only vaguely reference 'items' and 'tickets' without confirming assignment/due-date workflows. missing for 10: docs on creating items with owner/assignee columns, due-date column functionality, and any confirmation of this core PM workflow.

   • [community] “Hmm maybe I missed something but isn't Monday some kind of do-all task management system? A client of mine forced us on it and the un-opinio…”
   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   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

   monday.com—none0/10

   The evidence pack contains no documentation of subtask creation or dependency/blocking-order linking features (all docs items focus on AI agents, MCP, and integrations). The only relevant evidence is a community complaint that 'linking tickets to one another in Monday is really bad, data gets lost all the time' (monday-comm-4), which is negative rather than confirmatory, and there is no vendor claim in this pack to set up a dispute.

   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   proof ↗⚑ 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

   monday.com—none0/10

   No evidence in the pack mentions time tracking, time logging columns, or timesheet features against tasks/projects; all citations focus on AI agents, integrations, and app-building framework. Missing for 10: any mention of a time-tracking column, timer widget, or timesheet reporting feature.

   ⚑ 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

   monday.com—none0/10

   No vendor documentation addresses item caps or performance benchmarks at scale; the only relevant evidence is a hands-on community report stating boards would 'struggle and finally crash after a few thousand items,' capping usable scale around 20k items, directly contradicting the story rather than supporting it.

   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”
   • [community] “I tried using Monday.com for a building project I had and the interface become totally unusably slow... no idea if this is fixed but it seem…”
   • [community] “We'd tried it for a little bit for a small 5-6 person team. It was slow as hell. Stopped using it.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   The evidence pack only mentions building custom board/item views and dashboard widgets (developer platform for apps), not the native ability to toggle a single board's data between board, list, calendar, and timeline layouts. No citation confirms this specific multi-view switching capability.

   ⚑ 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

   monday.com—none0/10

   The evidence pack contains no mention of saved filtered views, view sharing, or shareable links for board/item views — all docs entries focus on AI agents, MCP, integrations, and APIs. This is a fair planning-tracking capability for a work OS product, but nothing in the pack demonstrates it.

   ⚑ flag

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   The evidence pack contains no mention of a search feature spanning tasks, docs, and comments, nor any performance/accuracy claims about search; instead it focuses on integrations, AI agents, and developer platform features. Search is a fair and applicable axis for a work management tool, but no supporting evidence exists here.

   ⚑ 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

   monday.com—none0/10

   Evidence mentions general infra security certifications (SOC2, HIPAA, ISO27001) and that data stays on monday's servers, but there is no mention of any region/data-residency selection option for customers. missing for 10: any documentation of selectable data regions, residency controls, or data-locality options.

   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001.”

   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

   monday.com—none0/10

   No evidence pack item addresses opting out of AI model training or data usage policies for AI training; documentation covers security certifications (SOC2/HIPAA/ISO) and agent infrastructure but never mentions training data controls or opt-out mechanisms. Missing for 10: explicit AI training opt-out policy, data usage terms for model training, any admin toggle or contractual guarantee against training use.

   ⚑ 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

   monday.com—none0/10

   No evidence addresses data retention policies, deletion controls, or user ability to purge AI-related data; docs mention secure infra/compliance certifications but not retention/deletion controls specifically.

   ⚑ 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

   monday.com—none0/10

   No evidence in the pack addresses telemetry opt-out or usage-tracking controls for AI-native users; docs cover security/compliance certifications but not user-facing telemetry settings. Missing for 10: any documentation of a telemetry/usage-tracking toggle or opt-out mechanism.

   ⚑ 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 Asana
   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

   monday.com—none0/10

   Evidence covers AI agents, integrations, MCP, and automation but nothing describes a workspace Q&A feature where a user asks a question and receives an answer with citations back to specific workspace content. Vague phrases like 'Surface deep intelligence and actionable insights' or 'Spot risks and progress gaps' do not describe citation-backed instant answers.

   ⚑ flag

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

   weight 2 · round to monday.com
   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

   monday.com✓fullclaimed7/10

   monday.com's own docs explicitly describe automating status updates and performance reports on a schedule, plus AI agents surfacing insights and spotting progress gaps, directly matching the story of AI drafting status updates from activity. Missing for 10: independent/hands-on verification of output quality and more detail on exactly how 'recent activity' data feeds into the drafted update.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Surface deep intelligence and actionable insights from any subject.”

   proof ↗⚑ flag

Dashboards

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

   weight 2 · round to monday.com
   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

   monday.com~partialcommunity6/10

   Monday's own docs explicitly state you can build custom dashboard widgets and views (monday-docs-3) and automate status/performance reporting (monday-docs-21) and surface risk/progress insights (monday-docs-22), directly matching the PM reporting story. However, there is no independent or hands-on validation of dashboard widget usability, and community reports describe severe performance degradation with large boards (thousands of items) which could undermine dashboard reliability at scale. missing for 10: independent corroboration of dashboard-building workflow, evidence dashboards remain performant/usable at scale, concrete examples of widget types used for reporting.

   • [claimed-docs] “Create custom board views, item views, dashboard widgets, and full-page apps.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   monday.com—none0/10

   The evidence pack is almost entirely about monday's AI agents, MCP/developer platform, and third-party integrations, with no documentation of a portfolio-level rollup view aggregating progress across multiple projects/boards. General integration claims (e.g., monday-docs-33) refer to cross-platform data sync, not a PM-facing portfolio dashboard.

   ⚑ flag

Access control

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

   weight 2 · round to monday.com
   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

   monday.com~partialclaimed4/10

   Docs mention admins can 'audit every action' an AI agent takes as part of agent governance, implying some audit logging exists, but there's no evidence of a general admin audit log covering all user/workspace actions (logins, permission changes, item edits) as a PM would expect for security review. missing for 10: evidence of a comprehensive audit log covering human user actions across the workspace, not just AI agent activity; independent/hands-on confirmation of audit log usability.

   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”

   proof ↗⚑ 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

   monday.com—none0/10

   The evidence pack only discusses scoping and auditing AI agent board access (e.g., monday-docs-10, monday-docs-6) and general integration/security certifications, but contains no evidence of human-facing granular roles/permissions (viewer/editor/guest, board-level access control) that a product manager would assign to team members. Missing for full credit: documentation of user role types, board/item permission settings, or admin controls for human collaborators.

   ⚑ 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

   monday.com—none0/10

   No evidence in the pack discusses private sub-teams, member-level board restrictions, or team-based access controls within monday.com's workspace/board permission model; all evidence pertains to AI agents, MCP, integrations, or general product sentiment.

   ⚑ 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

   monday.com—none0/10

   No evidence pack items mention SSO, SAML, identity providers, or authentication standards for organizational access; all docs focus on agents, MCP, integrations, and infra certifications (SOC 2, HIPAA, ISO 27001) rather than SSO/SAML specifically. Missing for 10: any documentation of SSO/SAML support, identity provider integration (Okta, Azure AD, etc.), or admin configuration for enterprise authentication.

   ⚑ 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

   monday.com—none0/10

   No evidence pack item mentions an uptime SLA or a public status page for monday.com; all docs relate to integrations, agents, and infra certifications, not incident transparency. missing for 10: published uptime SLA, public status page URL, real-time incident history.

   ⚑ 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

   monday.com—none0/10

   No evidence in the pack mentions support response times, SLAs, or tiered support commitments for any monday.com plan; the evidence covers product features, integrations, and community sentiment unrelated to support SLAs.

   ⚑ flag