Notion vs monday.com

Agent access

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

   weight 2 · round to Notion
   Notion✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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
   Notion~partialclaimed7/10

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

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

   proof ↗⚑ flag

   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 Notion
   Notion✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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 drawn
   Notion✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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
    Notion~partialprobed6/10

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

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

    proof ↗⚑ flag

    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
   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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
   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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
   Notion✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   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
   Notion~partialprobed6/10

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

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

   proof ↗⚑ flag

   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
   Notion~partialclaimed7/10

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

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

   proof ↗⚑ flag

   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 Notion
   Notion~partialprobed6/10

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

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

   proof ↗⚑ flag

   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 Notion
   Notion✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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 monday.com
   Notion—none0/10

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

   ⚑ flag

   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 drawn
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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 Notion
   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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 to monday.com
   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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 to monday.com
   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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 drawn
   Notion—none0/10

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

   ⚑ flag

   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 to monday.com
   Notion~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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 Notion
   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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
   Notion~partialprobed4/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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 Notion
   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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 to Notion
   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion!disputedcontradicted3/10

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

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

   proof ↗⚑ flag

   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
   Notion~partialcommunity6/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion~partialprobed6/10

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

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

   proof ↗⚑ flag

   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 Notion
   Notion!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Notion—none0/10

   Notion is a cloud-only SaaS with no self-hosted deployment option; community evidence explicitly confirms it is tied to its own cloud service with no way to run it as a standalone/local app, and users express desire for a self-hosted alternative that doesn't exist.

   • [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”
   • [community] “For now I use Notion with the hopes they implement it eventually [offline read-only mode]. I can't consider switching to a self hosted alter…”
   • [community] “I love Notion but the speed, or rather lack of, is killing me daily. Last Friday I was taking some notes, and suddenly the page refreshed an…”

   proof ↗⚑ flag

   monday.com—none0/10

   monday.com is explicitly a managed SaaS/cloud platform — docs state agents and apps run on monday-managed infra ('Your syncs and tools run on our infra, not yours', 'Your data never leaves our secure servers') with no mention of any self-hosted deployment option. No evidence of a self-hostable core product exists in the pack.

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [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

Mobile access

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

   weight 2 · round drawn
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialcommunity3/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialcommunity4/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialcommunity4/10

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

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

   proof ↗⚑ flag

   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 Notion
   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialcommunity3/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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 to Notion
   Notion!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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 Notion
   Notion~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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
   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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 to Notion
   Notion~partialcommunity3/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

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

   proof ↗⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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
   Notion—none0/10

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

   ⚑ flag

   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