ClickUp vs Notion

Agent access

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

   weight 2 · round drawn
   ClickUp✓fullprobed9/10

   A live probe confirms developer.clickup.com/llms.txt returns HTTP 200 with structured documentation content, and ClickUp also publishes agent-oriented docs (MCP server setup, tool list) explicitly designed for AI assistants to consume. This directly satisfies the story of pointing an agent at llms.txt or agent-facing docs. Missing for 10: independent third-party confirmation that an agent successfully ingests/uses the llms.txt file in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.clickup.com/llms.txt # ClickUp Documentation > ClickUp API empowers you to create custom work…”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”
   • [claimed-docs] “Set up Claude to use the ClickUp MCP server!”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”

   proof ↗⚑ flag

   Notion✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Notion
   ClickUp~partialprobed5/10

   ClickUp exposes a full REST API with personal API tokens and OAuth2 for programmatic, headless task/list/comment management, plus webhook-triggered automations, all of which can be scripted from CI pipelines without any UI. However, there is no documented CI/CD integration, official CLI, or GitHub Action, and the OpenAPI spec endpoint itself 404s in the probe, suggesting automation is possible but not purpose-built for CI workflows. Missing for 10: explicit CI/CD or pipeline integration guide, official CLI/GitHub Action, and independent confirmation of headless use in automated pipelines.

   • [claimed-docs] “Use a personal API token for individual or testing purposes. Personal tokens begin with `pk_`.”
   • [claimed-docs] “To allow others to use your app, implement the OAuth2 flow so each user has their own token for accessing their ClickUp resources.”
   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Automations”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Notion✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickUp—none0/10

   All MCP-related evidence describes ClickUp exposing its own MCP server so external AI assistants (e.g., Claude) can call ClickUp's tools (clickup-docs-2, clickup-docs-36–40, clickup-probe-3) — the opposite direction from the story, which asks whether a user can plug external MCP servers into ClickUp so ClickUp's own AI (Brain²/agents) can use their tools. No evidence shows ClickUp acting as an MCP client or consuming third-party MCP servers. Missing for 10: any documentation of ClickUp's Brain²/agents connecting to or invoking external MCP servers as a client.

   • [claimed-docs] “Connect your AI with ClickUp using our MCP Server.”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”
   • [claimed-docs] “Set up Claude to use the ClickUp MCP server!”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [probe] “official MCP server documented at https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server”

   proof ↗⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickUp✓fullprobed8/10

   ClickUp documents an official MCP server with setup guides (including Claude integration) and a documented set of MCP tools (search, time tracking, reporting), confirmed by both docs and an independent probe. Missing for 10: independent hands-on user reports of connecting an agent via this MCP server and broader third-party client compatibility beyond Claude.

   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”
   • [claimed-docs] “Set up Claude to use the ClickUp MCP server!”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [claimed-docs] “**Track time**: Log time entries and manage timers.”
   • [claimed-docs] “**Build executive reports**: Create release notes, status updates, and portfolio summaries from tasks and docs.”
   • [probe] “official MCP server documented at https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server”

   proof ↗⚑ flag

   Notion✓fullprobed8/10

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

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

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   ClickUp—none0/10

   Evidence shows a Public API, OAuth, MCP server, and OpenAPI spec, but no mention anywhere of an official CLI tool for ClickUp. Absence of evidence for this applicable capability means the story is not delivered.

   ⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickUp✓fullprobed9/10

   ClickUp has a documented public REST API with authentication (personal tokens and OAuth2), interactive try-it docs, endpoints for tasks, comments, views, attachments, and a published OpenAPI spec reference, all clearly aimed at programmatic/automated use. This is well beyond typical vendor claims, though the probe found direct openapi.json paths 404ing, indicating the raw spec isn't trivially fetchable despite doc references. missing for 10: independent third-party corroboration of API robustness/reliability in production use.

   • [claimed-docs] “Build integrations and apps with our Public API.”
   • [claimed-docs] “Use a personal API token for individual or testing purposes. Personal tokens begin with `pk_`.”
   • [claimed-docs] “To allow others to use your app, implement the OAuth2 flow so each user has their own token for accessing their ClickUp resources.”
   • [claimed-docs] “Every API endpoint in our documentation can be tested directly from your browser using the interactive "Try It" panel on the right side of e…”
   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [claimed-docs] “The ClickUp API allows you to view, add, and update or delete comments on tasks, Lists, and Chat views.”
   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Notion✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Notion
   ClickUp—none0/10

   ClickUp's docs describe only two auth mechanisms — a full-access personal token (pk_) and an OAuth2 flow granting per-user tokens — with no mention of scoped permissions, granular scopes, or role/least-privilege restrictions for API credentials or agents.

   • [claimed-docs] “Use a personal API token for individual or testing purposes. Personal tokens begin with `pk_`.”
   • [claimed-docs] “To allow others to use your app, implement the OAuth2 flow so each user has their own token for accessing their ClickUp resources.”

   proof ↗⚑ flag

   Notion~partialclaimed7/10

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

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

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Notion
   ClickUp—none0/10

   The evidence describes ClickUp's REST Public API, OAuth2 authentication, an OpenAPI spec, and an MCP server for AI agents, but nowhere does it mention official client SDKs (e.g., official Python, JS, or other language libraries) for developers to build against. The probe for openapi.json/swagger.json paths also returned 404s, further indicating no packaged SDK artifacts are surfaced.

   • [claimed-docs] “Every API endpoint in our documentation can be tested directly from your browser using the interactive "Try It" panel on the right side of e…”
   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Notion✓fullprobed8/10

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

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

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Notion
   ClickUp~partialclaimed3/10

   The docs mention triggering workflows from ClickUp events and a Public API for integrations, which implies event-based subscription capability, but no evidence explicitly documents a webhooks feature, subscription setup, or event payload/API reference. missing for 10: explicit webhook documentation, event subscription setup instructions, event payload examples, independent confirmation of webhook reliability.

   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Build integrations and apps with our Public API.”

   proof ↗⚑ flag

   Notion✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

    weight 1 · round to ClickUp
    ClickUp~partialprobed7/10

    ClickUp provides a documented MCP server letting external AI agents/assistants read and act on workspace tasks, docs, and folders via natural language, plus a public API, 1,000+ integrations (GitHub, Slack, Jira migration, etc.), and Brain² which claims real-time awareness of tasks/docs/conversations across connected apps—together supporting context-preserving handoffs between tools/agents. However, evidence is entirely vendor-authored with no independent or hands-on confirmation that context/state actually survives a real handoff (e.g., agent-to-agent or tool-to-tool session continuity), and no benchmarks on data fidelity during transfer. Missing for 10: independent verification of lossless handoff in practice, and technical detail on state/session continuity beyond marketing claims.

    • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”
    • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
    • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
    • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
    • [claimed-docs] “Brain² taps Google Drive, GitHub, Salesforce, and more to get you answers and insights.”
    • [claimed-docs] “Sync commits, branches, pull requests, and issues between GitHub and ClickUp to track development progress without switching tools.”
    • [claimed-docs] “Migrate your Jira issues, sprints, and epics into ClickUp seamlessly. Keep dev teams aligned with no data lost in the transition.”
    • [claimed-docs] “Connect over 1,000+ tools to ClickUp for free”
    • [probe] “official MCP server documented at https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server”

    proof ↗⚑ flag

    Notion~partialprobed6/10

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

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

    proof ↗⚑ flag

Agentic features

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

   weight 2 · round to ClickUp
   ClickUp✓fullclaimed7/10

   ClickUp's Brain² is explicitly marketed to surface AI-generated insights and answers from workspace data, docs, tasks, and connected apps (Drive, GitHub, Salesforce), and third-party integrations (e.g., ChatGPT) extend this to give AI-powered insights about tasks/projects/conversations. Missing for 10: independent/hands-on corroboration that Brain² insights are accurate or reliable in practice, and detail on insight quality beyond vendor marketing copy.

   • [claimed-docs] “Brain² picks the best AI model for each job. One subscription. Every frontier model running with full context.”
   • [claimed-docs] “Brain² learns how you and your team talk: your tone, your shorthand, your preferences.”
   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
   • [claimed-docs] “Brain² taps Google Drive, GitHub, Salesforce, and more to get you answers and insights.”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
   • [claimed-docs] “GPT, Claude Opus, Gemini, and more. Every model runs with full knowledge of your work.”
   • [claimed-docs] “OpenAI's ChatGPT can tap into your ClickUp workspace to give you AI-powered insights about your tasks, projects, and conversations.”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp~partialclaimed7/10

   ClickUp documents native Automations, event-triggered workflows, and 'Super Agent' capabilities that work 24/7 with background task delegation, plus custom agent building — directly supporting autonomous background automation. However, evidence is entirely first-party marketing/docs with no independent or hands-on confirmation that these automations reliably run unattended, and general community sentiment raises broader reliability concerns (though not a concrete contradiction of automation functionality specifically). Missing for 10: independent verification of automation reliability/uptime, technical detail on automation triggers/conditions beyond marketing copy.

   • [claimed-docs] “Delegate any task Super Agent Works 24/7 Infinite memory”
   • [claimed-docs] “Automations”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Build your own agent”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickUp✓fullclaimed7/10

   ClickUp explicitly markets a built-in AI assistant ('Brain²'/'Super Agent') that can be delegated tasks, works 24/7, has infinite memory, and includes prebuilt agents like Codegen and Triage plus the ability to build custom agents. This directly matches the story of delegating tasks to an in-product AI assistant. Missing for 10: independent/hands-on verification that delegation actually works reliably (community evidence is general sentiment on ClickUp quality, not specific to the AI assistant) and more detail on limits of autonomous task execution.

   • [claimed-docs] “Delegate any task Super Agent Works 24/7 Infinite memory”
   • [claimed-docs] “Build your own agent”
   • [claimed-docs] “Brain² picks the best AI model for each job. One subscription. Every frontier model running with full context.”
   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
   • [claimed-docs] “Codegen Agent produces quality code”
   • [claimed-docs] “Triage Agent prioritizes bugs”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”

   proof ↗⚑ flag

   Notion✓fullclaimed7/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp✓fullprobed8/10

   ClickUp's Brain² assistant and documented MCP server explicitly let users query, create, and manage tasks, docs, and workflows via natural language (e.g., 'lets external AI agents interact with ClickUp Workspace data...using natural language', 'Ask something complex' answered from workspace context). First-party docs also list concrete NL-driven MCP tools like search, time tracking, and report generation. Missing for 10: independent/hands-on verification of natural-language command reliability and breadth beyond vendor claims.

   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [claimed-docs] “**Track time**: Log time entries and manage timers.”
   • [claimed-docs] “**Build executive reports**: Create release notes, status updates, and portfolio summaries from tasks and docs.”
   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
   • [probe] “official MCP server documented at https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server”

   proof ↗⚑ flag

   Notion~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Notion
   ClickUp~partialclaimed6/10

   ClickUp markets 'Build your own agent' and offers pre-built agents (Codegen Agent, Triage Agent) plus a Brain² AI layer, suggesting some agent customization exists, but the evidence lacks concrete detail on the configuration process, scope of customizability (triggers, tools, permissions), or hands-on confirmation of how flexible agent-building actually is. Missing for 10: detailed documentation of the agent-builder UI/workflow, independent/hands-on verification of building a custom agent, and specifics on what can be configured (triggers, knowledge sources, actions).

   • [claimed-docs] “Delegate any task Super Agent Works 24/7 Infinite memory”
   • [claimed-docs] “Build your own agent”
   • [claimed-docs] “Codegen Agent produces quality code”
   • [claimed-docs] “Triage Agent prioritizes bugs”
   • [claimed-docs] “Brain² picks the best AI model for each job. One subscription. Every frontier model running with full context.”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”

   proof ↗⚑ flag

   Notion~partialclaimed7/10

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

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

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to ClickUp
   ClickUp✓fullprobed8/10

   ClickUp's developer docs explicitly describe a 'Try It' interactive panel available on every API endpoint for testing directly in the browser, plus a raw OpenAPI spec available for each API version, and extensive endpoint documentation (tasks, comments, views, attachments, filters). This directly matches the story of an interactive, runnable API reference. Missing for 10: independent/community corroboration of the interactive console's usability and a live-verifiable OpenAPI spec URL (probe found 404s on standard OpenAPI paths despite docs claiming one exists).

   • [claimed-docs] “Every API endpoint in our documentation can be tested directly from your browser using the interactive "Try It" panel on the right side of e…”
   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”
   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “The ClickUp API allows you to view, add, and update or delete comments on tasks, Lists, and Chat views.”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Notion~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Notion
   ClickUp✓fullprobed8/10

   ClickUp's developer docs explicitly state the raw OpenAPI specification is available for each version of the Public API (clickup-docs-35), directly satisfying the story; probe attempts at guessed standard URLs returned 404 but that doesn't contradict a documented, linked spec location. Missing for 10: independent/hands-on confirmation of the actual spec file download and its completeness/currency.

   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”
   • [claimed-docs] “Every API endpoint in our documentation can be tested directly from your browser using the interactive "Try It" panel on the right side of e…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Notion✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round drawn
   ClickUp—none0/10

   No evidence of a sandbox/staging environment or test workspace that AI-native users could safely test against without touching production data; docs mention personal API tokens for 'testing purposes' but this is just an auth mechanism, not an isolated sandbox environment. Missing for 10: any dedicated sandbox/staging instance, test workspace provisioning, or documented separation between test and production data.

   • [claimed-docs] “Use a personal API token for individual or testing purposes. Personal tokens begin with `pk_`.”
   • [claimed-docs] “Every API endpoint in our documentation can be tested directly from your browser using the interactive "Try It" panel on the right side of e…”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   Evidence confirms ClickUp has a Public API with an OpenAPI spec 'available for each version' (clickup-docs-35), implying some versioning, but there is no documentation of a deprecation policy, sunset timelines, or version lifecycle communication anywhere in the pack, and a direct probe for the OpenAPI spec at standard paths returned 404s.

   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   The evidence pack shows extensive API docs (authentication, tasks, comments, views, OpenAPI spec) and MCP server docs, but nothing documents rate limits, request quotas, or concurrency caps for building automation at scale. No mention of per-minute limits, throttling behavior, or tiered API limits appears anywhere in the pack.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp~partialcommunity5/10

   ClickUp's Public API and MCP tools let AI agents create, update, filter, and search tasks/views/comments programmatically, which could be scripted into bulk operations across many items, and automations can act on events at scale. However, there is no explicit documentation of a dedicated bulk-update/bulk-delete endpoint or batch API, and community feedback questions ClickUp's engineering reliability/performance under heavy use. Missing for 10: explicit bulk-operation API endpoints (e.g., batch create/update/delete), documented rate-limit/performance guarantees for large-scale operations, and independent verification that bulk actions work reliably at scale.

   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “The supported operators for filtering are: * `=`- contains (fuzzy match)”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [community] “Ah yes, ClickUp, the issue tracker that was so sloppy there wasn't a single person at my company who was upset about our switching to Linear…”
   • [community] “I think ClickUp gets the dubious honour of being my least favourite piece of software of all time. Super slow to load, clunky, unbelievably …”

   proof ↗⚑ flag

   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to ClickUp
   ClickUp✓fullclaimed7/10

   ClickUp has a dedicated Automations feature and documented ability to trigger workflows from ClickUp events via API/webhooks, directly matching the rule-based trigger/action story. Missing for 10: detailed documentation of the rule-builder UI (conditions/trigger types), independent hands-on verification of automation reliability, and AI-specific trigger examples beyond generic event-based workflows.

   • [claimed-docs] “Automations”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Build integrations and apps with our Public API.”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to ClickUp
   ClickUp~partialclaimed4/10

   ClickUp advertises native Automations and event-based workflow triggers (clickup-docs-14, clickup-docs-3) plus API/MCP hooks for building custom flows, which could support recurring jobs, but no evidence explicitly documents recurring/scheduled triggers or cron-like automation for AI-native use. missing for 10: explicit documentation of recurring/scheduled automation triggers, AI-agent-specific scheduling examples, and independent confirmation that automations support recurrence.

   • [claimed-docs] “Automations”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”
   • [claimed-docs] “Build your own agent”

   proof ↗⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round drawn
   ClickUp—none0/10

   The evidence pack covers ClickUp's Automations feature, API, MCP server, and Brain² AI, but nothing describes versioning, reviewing, or rolling back automations/workflows. No changelog, history, or revert capability for automations is documented.

   ⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

Ai task automation

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

   weight 2 · round to ClickUp
   ClickUp~partialclaimed5/10

   ClickUp explicitly markets a 'Triage Agent' that prioritizes bugs, backed by automation/workflow-trigger capabilities, indicating the feature exists. However, evidence is limited to a single marketing tagline with no detailed documentation of how triage/prioritization logic works, no independent or hands-on corroboration, and general community sentiment is unrelated to this specific feature. Missing for 10: detailed first-party documentation of triage logic/configuration, independent or hands-on verification that the Triage Agent works as claimed, and integration details with bug-tracking workflows.

   • [claimed-docs] “Triage Agent prioritizes bugs”
   • [claimed-docs] “Automations”
   • [claimed-docs] “Trigger workflows from ClickUp events.”

   proof ↗⚑ flag

   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to ClickUp
   ClickUp~partialclaimed6/10

   ClickUp's Brain² feature is explicitly marketed to 'learn how you and your team talk: your tone, your shorthand, your preferences' and adapts based on real-time context from tasks/docs/conversations, directly matching the story. However, this rests solely on first-party marketing copy with no independent or hands-on corroboration of the tone/shorthand-learning behavior actually working as described. Missing for 10: independent/hands-on verification that output style adapts to user tone, technical detail on how preferences are learned/stored, and user testimonials confirming personalization accuracy.

   • [claimed-docs] “Brain² learns how you and your team talk: your tone, your shorthand, your preferences.”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
   • [claimed-docs] “Brain² picks the best AI model for each job. One subscription. Every frontier model running with full context.”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

Workflow automation

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

   weight 1 · round to ClickUp
   ClickUp~partialclaimed4/10

   ClickUp's MCP server explicitly lists building 'release notes, status updates, and portfolio summaries from tasks and docs' as an AI capability, and GitHub/GitLab/Bitbucket integrations sync commits, PRs, and issues into ClickUp, giving raw material for a changelog. However, this is an on-demand AI query capability, not a dedicated auto-generate-changelog-per-release feature triggered by tags/releases. Missing for 10: a purpose-built changelog/release-notes generator tied to release events, evidence of automatic triggering on deploy/tag, and any independent/hands-on confirmation this workflow actually works well in practice.

   • [claimed-docs] “**Build executive reports**: Create release notes, status updates, and portfolio summaries from tasks and docs.”
   • [claimed-docs] “Sync commits, branches, pull requests, and issues between GitHub and ClickUp to track development progress without switching tools.”
   • [claimed-docs] “Link GitLab commits, branches, pull requests, and issues with ClickUp Tasks for real-time visibility and streamlined development.”
   • [claimed-docs] “Sync Bitbucket commits, branches, and pull requests with ClickUp Tasks for better visibility into development work.”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

2. product managerBuild multi-step automations without writing code

   weight 2 · round to ClickUp
   ClickUp~partialclaimed5/10

   ClickUp explicitly lists an 'Automations' feature and documents triggering workflows from ClickUp events, indicating a native no-code automation builder exists, but the evidence pack gives no detail on multi-step logic, conditional branching, or a walkthrough of building such automations, and no independent/hands-on validation of this specific capability. missing for 10: detailed documentation of multi-step/conditional automation builder, hands-on or independent evidence of a PM successfully creating complex no-code automations.

   • [claimed-docs] “Automations”
   • [claimed-docs] “Trigger workflows from ClickUp events.”

   proof ↗⚑ flag

   Notion~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to ClickUp
   ClickUp✓fullclaimed6/10

   ClickUp explicitly ships a dedicated 'Automations' feature and documents triggering workflows from ClickUp events via its API, directly matching the trigger-and-action automation story. missing for 10: independent hands-on corroboration of building automation rules, and detail on the range of trigger/action types available.

   • [claimed-docs] “Automations”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Build integrations and apps with our Public API.”

   proof ↗⚑ flag

   Notion~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp~partialclaimed5/10

   ClickUp explicitly advertises an 'Automations' feature and the ability to 'Trigger workflows from ClickUp events,' which supports building automated recurring workflows for routine team tasks, but the evidence never specifically confirms schedule-based (time/cron) triggers or recurring-event automation details. Missing for 10: explicit documentation of schedule/time-based triggers, recurring automation examples, and independent/hands-on confirmation that automations run reliably on a schedule.

   • [claimed-docs] “Automations”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Build integrations and apps with our Public API.”

   proof ↗⚑ flag

   Notion~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickUp—none0/10

   No evidence pack item discusses API rate limits, automation execution caps, overage charges, throttling behavior, or hard stops when plan limits are exceeded; docs cover API usage/auth/MCP but not limit policies or consequences.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

Cross tool sync

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

   weight 2 · round to Notion
   ClickUp—none0/10

   ClickUp's only design-tool integration evidenced is embedding Figma prototypes inside ClickUp tasks/docs (clickup-intdir-5), which is the opposite direction of the story — it brings Figma content into ClickUp rather than letting a designer update task status from within Figma without switching apps. No evidence of a Figma plugin, sidebar, or comment/status sync that lets a designer change ClickUp status without leaving their design tool.

   • [claimed-docs] “Embed interactive Figma prototypes in ClickUp Tasks, Docs, and Chat for real-time design collaboration.”

   proof ↗⚑ flag

   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

Docs knowledge

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

   weight 3 · round to Notion
   ClickUp~partialclaimed5/10

   ClickUp explicitly lists a 'Docs' product feature and MCP tools confirm search across tasks, lists, folders, and Docs alongside project data, plus Figma embeds inside Docs show cross-linking with project work. However, evidence is thin—just a one-word feature bullet and indirect MCP references—without detail on doc organization (nesting, permissions, templates, wikis) that a PM would need. Missing for 10: documentation on doc hierarchy/organization structure, sharing/permission controls, and independent hands-on validation of the Docs experience.

   • [claimed-docs] “Docs”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [claimed-docs] “Embed interactive Figma prototypes in ClickUp Tasks, Docs, and Chat for real-time design collaboration.”
   • [claimed-docs] “**Build executive reports**: Create release notes, status updates, and portfolio summaries from tasks and docs.”

   proof ↗⚑ flag

   Notion✓fullcommunity8/10

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

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

   proof ↗⚑ flag

In context discussion

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

   weight 2 · round to Notion
   ClickUp—none0/10

   Evidence covers task comments generally (view/add/update/delete comments via API) but there is no mention of commenting on specific inline text or images within a description, nor annotation/proofing-on-description features. Missing for 10: any documentation of inline text-highlight comments or image markup within item descriptions.

   • [claimed-docs] “The ClickUp API allows you to view, add, and update or delete comments on tasks, Lists, and Chat views.”

   proof ↗⚑ flag

   Notion~partialclaimed3/10

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

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

   proof ↗⚑ flag

Real time sync

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

   weight 3 · round to Notion
   ClickUp~partialcommunity4/10

   ClickUp advertises real-time chat and Brain² 'sees your tasks, docs, and conversations... in real-time,' suggesting some live-update capability, and a community comment confirms real-time chat exists. However there is no explicit documentation or hands-on evidence describing live, no-refresh syncing of task/doc edits across open sessions (e.g., collaborative cursors, instant task field updates), missing for 10: explicit real-time task/doc sync documentation, independent hands-on confirmation of no-refresh updates, evidence of multiplayer editing indicators.

   • [claimed-docs] “Chat”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
   • [community] “FYI, ClickUp does have real-time chat which is I think the only feature you note on the compare page that Upbase has that ClickUp does not.”

   proof ↗⚑ flag

   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

Team chat

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

   weight 2 · round to ClickUp
   ClickUp✓fullcommunity7/10

   ClickUp lists a 'Chat' product module directly in its suite alongside task/docs/sprints ([clickup-docs-17]), and independent community evidence confirms ClickUp has real-time chat built into the platform ([clickup-comm-3]), satisfying the core ask of chatting within the same tool used for planning work. Missing for 10: no detailed documentation of chat features (threads, mentions, task-linking) or hands-on quality feedback specifically about the chat experience.

   • [claimed-docs] “Chat”
   • [community] “FYI, ClickUp does have real-time chat which is I think the only feature you note on the compare page that Upbase has that ClickUp does not.”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

App ecosystem

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

   weight 2 · round to Notion
   ClickUp—none0/10

   Evidence shows only generic API/webhook/MCP capabilities and Brain² pulling data from GitHub for AI answers, but no documentation of a native bi-directional issue-tracker sync (e.g., GitHub/GitLab/Jira issues linking with two-way status updates). missing for 10: dedicated GitHub/GitLab issue sync integration docs, evidence of bi-directional field/status mapping, any hands-on confirmation of sync working.

   • [claimed-docs] “Build integrations and apps with our Public API.”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Brain² taps Google Drive, GitHub, Salesforce, and more to get you answers and insights.”

   proof ↗⚑ flag

   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   Evidence shows ClickUp's public API, MCP server, and Brain² AI features, but nothing about aggregating or syncing assigned tasks from other PM tools (e.g., Jira, Asana, Trello) into a single unified ClickUp view. No integration list or cross-tool task sync is documented.

   • [claimed-docs] “Build integrations and apps with our Public API.”
   • [claimed-docs] “Connect your AI with ClickUp using our MCP Server.”
   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
   • [claimed-docs] “Brain² taps Google Drive, GitHub, Salesforce, and more to get you answers and insights.”

   proof ↗⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp~partialclaimed5/10

   ClickUp explicitly advertises native connections to GitHub and Google Drive (and Salesforce) via Brain² and its Public API/webhooks, but the evidence pack never mentions a native Slack integration, leaving one of the three named tools unconfirmed. Missing for 10: explicit Slack integration evidence, independent/hands-on confirmation of integration reliability, and details on integration setup/scope beyond marketing copy.

   • [claimed-docs] “Brain² taps Google Drive, GitHub, Salesforce, and more to get you answers and insights.”
   • [claimed-docs] “Build integrations and apps with our Public API.”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”

   proof ↗⚑ flag

   Notion!disputedcontradicted3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp✓fullclaimed8/10

   ClickUp documents a marketplace-style integrations directory with 1,000+ tools (Slack, GitHub, HubSpot, Salesforce, Figma, Jira, Asana, etc.) plus a public API/OAuth2 and MCP server for building custom connections, directly matching the story. Missing for 10: independent third-party corroboration of the marketplace's breadth/quality and no direct evidence of an actual 'app store'-style discovery UI beyond the integrations page.

   • [claimed-docs] “Connect over 1,000+ tools to ClickUp for free”
   • [claimed-docs] “Create and update ClickUp Tasks from Slack messages, unfurl links with rich details and actions, and receive real-time task updates in Slack…”
   • [claimed-docs] “Sync commits, branches, pull requests, and issues between GitHub and ClickUp to track development progress without switching tools.”
   • [claimed-docs] “Sync CRM data, tickets, and properties between ClickUp and HubSpot to track pipeline progress and manage projects seamlessly.”
   • [claimed-docs] “Import tasks, projects, and attachments from Asana into ClickUp in minutes—no data left behind. Keep your entire workflow in one place and c…”
   • [claimed-docs] “Migrate your Jira issues, sprints, and epics into ClickUp seamlessly. Keep dev teams aligned with no data lost in the transition.”
   • [claimed-docs] “Use n8n’s open, fair-code workflow automation to connect ClickUp with any app you need.”
   • [claimed-docs] “Build integrations and apps with our Public API.”
   • [claimed-docs] “To allow others to use your app, implement the OAuth2 flow so each user has their own token for accessing their ClickUp resources.”

   proof ↗⚑ flag

   Notion~partialcommunity6/10

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

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

   proof ↗⚑ flag

Extensibility

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

   weight 1 · round drawn
   ClickUp—none0/10

   The evidence shows a Public API that can create/update/filter existing views and dashboards (clickup-docs-33) and integration directory entries, but there is no evidence of an SDK, custom widget framework, or UI-extension mechanism allowing designers to build genuinely custom views/widgets that render natively inside ClickUp's interface — the API only manages ClickUp's own view objects, not custom-rendered components.

   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [claimed-docs] “Build integrations and apps with our Public API.”
   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”

   proof ↗⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

Getting started

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

   weight 3 · round drawn
   ClickUp—none0/10

   The evidence pack shows ClickUp's API can access tasks, comments, and attachments individually, but there is no documentation of a native workspace export feature that preserves full history (comments, attachments, audit trails) as a bundled export capability—only import tooling from other tools (e.g., Asana, Jira) is mentioned, not exporting out of ClickUp.

   ⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round drawn
   ClickUp—none0/10

   No evidence of a guided onboarding walkthrough for setting up a workspace; evidence covers API docs, integrations, and AI/Brain features but nothing about first-time setup guidance or onboarding UX. Community comments even suggest complexity/clunkiness rather than a guided setup experience.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   No evidence describes an import tool, wizard, or documented migration path from other PM tools; only a public API and community anecdote of a user having 'converted' from Jira without detail on how data was migrated. Missing for 10: dedicated import feature docs, supported source tools list, migration guide, or independent confirmation of successful data import.

   • [community] “Uses the same folder-list paradigm as ClickUp, which, as a long time JIRA user recently converted to ClickUp, I find to be a plus... one thi…”
   • [claimed-docs] “Build integrations and apps with our Public API.”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   The evidence pack covers API, MCP, AI agents, integrations, and community sentiment, but contains no mention of pre-built project templates or a template library/gallery for jumpstarting projects.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

Pricing transparency

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

   weight 3 · round drawn
   ClickUp—none0/10

   No evidence pack items address pricing plans, seat minimums, or annual billing commitments; all evidence concerns API/integrations/MCP/features, not billing terms.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp~partialprobed6/10

   ClickUp's Public API and docs show broad coverage—tasks, comments, custom fields, attachments, views, filters, OAuth, webhooks, and an OpenAPI spec—plus an MCP server exposing workspace search, time tracking, and reporting tools, suggesting strong but not exhaustive parity with the UI. However, there's no evidence that higher-end UI surfaces like Whiteboards, Docs authoring, Automations building, Sprints configuration, or Chat are fully API-manageable, and the openapi.json probe returned 404s at the standard paths, undermining full spec accessibility. Missing for 10: documented API/MCP coverage for Whiteboards, Docs creation/editing, Automation rule building, Sprint management, and Chat parity, plus a verifiably reachable OpenAPI spec.

   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “Upload attachments to tasks using the ClickUp API. This guide outlines the key requirements for file uploads.”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [claimed-docs] “The ClickUp API allows you to view, add, and update or delete comments on tasks, Lists, and Chat views.”
   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”
   • [claimed-docs] “Trigger workflows from ClickUp events.”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [claimed-docs] “**Track time**: Log time entries and manage timers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Notion~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Notion
   ClickUp—none0/10

   The evidence pack shows ClickUp has a Public API for reading/writing tasks, comments, views, etc. (clickup-docs-28/33/34) and mentions an OpenAPI spec, but the openapi.json endpoint 404s in the probe (clickup-probe-2), and there is no documentation of a bulk 'export all your data' feature, data-portability guarantee, or open-format (CSV/JSON/Markdown) full-workspace export/leave mechanism. Community evidence is about product quality/UX, not data export.

   • [claimed-docs] “The raw OpenAPI specification for the ClickUp API is available for each version of our Public API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.clickup.com/openapi.json, https://developer.clickup.com/swagger.json, https://deve…”
   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [claimed-docs] “The ClickUp API allows you to view, add, and update or delete comments on tasks, Lists, and Chat views.”

   proof ↗⚑ flag

   Notion!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

3. ai-native userSelf-host the core product

   weight 3 · round drawn
   ClickUp—none0/10

   ClickUp is a SaaS product with no evidence of a self-hostable version; all documentation points to cloud-hosted service with APIs, integrations, and MCP server, but nothing indicates a self-hosted deployment option. Missing for 10: any mention of self-hosted/on-prem deployment, Docker images, or open-source core.

   ⚑ flag

   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

Mobile access

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

   weight 2 · round drawn
   ClickUp—none0/10

   No evidence in the pack addresses ClickUp's native mobile app or its feature parity with desktop; all citations cover web features, AI agents, API, or general product-quality complaints unrelated to mobile. Missing for 10: any documentation or hands-on mention of the mobile app, its feature set, or offline/parity capabilities.

   ⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

Task management

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

   weight 2 · round to Notion
   ClickUp—none0/10

   The evidence pack covers ClickUp's integrations, AI features, and general PM tooling (Sprints, Docs, Views, Automations) but contains no mention of task dependency linking, blocking/waiting relationships, or cross-team dependency visualization/tracking needed to coordinate large launches. Missing for 10: explicit dependency-tracking feature docs, cross-team roadmap/portfolio dependency views, and any hands-on validation of dependency coordination workflows.

   ⚑ flag

   Notion~partialcommunity3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp✓fullcommunity7/10

   ClickUp's API and docs show explicit support for custom fields (moving/adding custom fields to lists) and custom task types, and a Hacker News user (a long-time Jira convert) praises ClickUp specifically for making it fast to reconfigure task statuses versus Jira's rigid workflow engine. Together this shows both first-party capability and independent corroboration that fields/statuses are customizable to match team process. Missing for 10: dedicated first-party documentation on configuring workflow statuses/stages in the UI (only inferred via API custom fields and one community comment), and no hands-on demonstration of full workflow-status editing.

   • [claimed-docs] “You can add the Custom Fields from the task's current List to it's new List, using the `move_custom_fields`request body parameter.”
   • [claimed-docs] “You can use [Create Task] to set the custom task type on a task as you create it.”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [community] “Uses the same folder-list paradigm as ClickUp, which, as a long time JIRA user recently converted to ClickUp, I find to be a plus... one thi…”

   proof ↗⚑ flag

   Notion~partialcommunity4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp~partialcommunity6/10

   ClickUp's task/list hierarchy and API support custom fields, custom task types, and configurable statuses (clickup-docs-28, clickup-docs-30, clickup-docs-31, clickup-comm-1), which are the building blocks for tracking initiatives with status and priority, and tasks can be assigned to teams/users. However, no evidence explicitly shows a first-class 'initiative' object, a dedicated priority field, or a formal team-ownership assignment mechanism — missing for 10: explicit initiative/epic-level object, dedicated priority field documentation, and owning-team assignment evidence.

   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “You can add the Custom Fields from the task's current List to it's new List, using the `move_custom_fields`request body parameter.”
   • [claimed-docs] “You can use [Create Task] to set the custom task type on a task as you create it.”
   • [claimed-docs] “The ClickUp API allows you to view, add, and update or delete comments on tasks, Lists, and Chat views.”
   • [community] “Uses the same folder-list paradigm as ClickUp, which, as a long time JIRA user recently converted to ClickUp, I find to be a plus... one thi…”

   proof ↗⚑ flag

   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

4. engineerPlan and manage sprints for agile software development

   weight 2 · round to ClickUp
   ClickUp~partialcommunity5/10

   ClickUp explicitly lists 'Sprints' as a first-party feature and offers Jira migration that preserves 'sprints and epics,' plus dev-tool integrations (GitHub/GitLab/Bitbucket, Sentry) for tracking progress against tasks, supporting agile engineering workflows. However, the evidence pack gives no detail on sprint mechanics (backlog, velocity, burndown/burnup charts, sprint points) beyond the single word 'Sprints,' and community feedback raises general concerns about ClickUp's engineering/performance quality (though not specifically about sprint planning failing). Missing for 10: detailed documentation of sprint configuration/points/burndown, independent hands-on validation of the sprint workflow specifically.

   • [claimed-docs] “Sprints”
   • [claimed-docs] “Migrate your Jira issues, sprints, and epics into ClickUp seamlessly. Keep dev teams aligned with no data lost in the transition.”
   • [claimed-docs] “Sync commits, branches, pull requests, and issues between GitHub and ClickUp to track development progress without switching tools.”
   • [claimed-docs] “Link GitLab commits, branches, pull requests, and issues with ClickUp Tasks for real-time visibility and streamlined development.”
   • [claimed-docs] “Convert Sentry error reports into ClickUp Tasks, ensuring developers can track and resolve bugs efficiently.”
   • [community] “As a customer of ClickUp, I have very little confidence in their engineering ability. Leader calls for '100x' development, and I think he's …”
   • [community] “I think ClickUp gets the dubious honour of being my least favourite piece of software of all time. Super slow to load, clunky, unbelievably …”

   proof ↗⚑ flag

   Notion~partialcommunity4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to ClickUp
   ClickUp✓fullcommunity8/10

   ClickUp's core product is task management with API docs confirming create/update tasks (clickup-docs-28), assignees and due dates being standard fields manageable via API and UI, plus custom fields, views, and comments support. Community evidence corroborates it as a functioning task/issue tracker despite complaints about bloat/performance. Missing for 10: explicit citation of assignee/due-date fields in the evidence pack and independent hands-on confirmation of assignment workflows.

   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [claimed-docs] “The ClickUp API allows you to view, add, and update or delete comments on tasks, Lists, and Chat views.”
   • [community] “Uses the same folder-list paradigm as ClickUp, which, as a long time JIRA user recently converted to ClickUp, I find to be a plus... one thi…”

   proof ↗⚑ flag

   Notion~partialcommunity5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickUp—none0/10

   The evidence pack covers ClickUp's API, integrations, and AI agent features but contains no explicit mention of subtasks, task hierarchies, or dependency linking (e.g., 'blocked by' relations) that would let an engineer show blocking order. Task-related docs only describe generic CRUD via the API, custom fields, and moving tasks between lists, none of which evidence dependency or subtask functionality.

   • [claimed-docs] “Using the ClickUp API, you can create, update, and manage tasks programmatically.”
   • [claimed-docs] “You can add the Custom Fields from the task's current List to it's new List, using the `move_custom_fields`request body parameter.”
   • [claimed-docs] “You can use [Create Task] to set the custom task type on a task as you create it.”
   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

7. engineerLog time directly against tasks and projects

   weight 2 · round to ClickUp
   ClickUp✓fullclaimed7/10

   ClickUp lists native "Time Tracking" as a core product feature and its MCP server explicitly supports logging time entries and managing timers, confirming engineers can track time directly against tasks/projects. Missing for 10: independent/hands-on corroboration specifically of time-tracking usage, and detailed public API docs for time-entry endpoints beyond the MCP tool mention.

   • [claimed-docs] “Time Tracking”
   • [claimed-docs] “**Track time**: Log time entries and manage timers.”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

Views organization

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

   weight 2 · round drawn
   ClickUp—none0/10

   No documentation or specific data addresses performance characteristics or item/task caps at scale (tens of thousands of tasks); the only related evidence is vague community complaints about general slowness/RAM usage, not concrete data on caps or scale behavior.

   • [community] “Ah yes, ClickUp, the issue tracker that was so sloppy there wasn't a single person at my company who was upset about our switching to Linear…”
   • [community] “I think ClickUp gets the dubious honour of being my least favourite piece of software of all time. Super slow to load, clunky, unbelievably …”

   proof ↗⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Notion
   ClickUp—none0/10

   The evidence pack only generically references 'views' via the API (create/update/delete/group/sort/filter) without naming board, list, calendar, or timeline view types or any UI-level view-switching capability; no documentation or community evidence confirms this specific multi-view experience.

   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”

   proof ↗⚑ flag

   Notion~partialcommunity3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp~partialclaimed4/10

   ClickUp's API/docs confirm views can be created, filtered, sorted and grouped (clickup-docs-33) and that task filtering is supported (clickup-docs-32), which underlies saved filtered views, but no evidence explicitly describes generating or sharing a link to a filtered view. Missing for 10: explicit documentation of view-sharing via link, UI-level confirmation of 'share view' feature, and any community/hands-on corroboration of this specific workflow.

   • [claimed-docs] “You can create, update, delete, group, sort, and filter views at any level of the ClickUp hierarchy using the API.”
   • [claimed-docs] “The supported operators for filtering are: * `=`- contains (fuzzy match)”

   proof ↗⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp~partialclaimed6/10

   ClickUp documents a native 'Search Workspace' capability (via its MCP tool) that searches across tasks, Lists, Folders, and Docs, and Brain² claims to see 'tasks, docs, and conversations' in real time, suggesting broad cross-entity search/AI retrieval. However, evidence does not explicitly confirm comment-level search, nor provide any first-party or independent claims/benchmarks about search speed or accuracy. Missing for 10: explicit documentation that comments are searchable, and evidence of search performance/accuracy (benchmarks or hands-on validation).

   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”

   proof ↗⚑ flag

   Notion!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for ClickUp; the pack covers API, MCP, integrations, and AI agent features only. This is a fair axis for a SaaS productivity platform used by enterprise/AI-native customers, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickUp—none0/10

   No evidence in the pack addresses data-training opt-out, privacy policy controls, or any AI-training exclusion settings for ClickUp; the evidence only covers integrations, API, MCP server, and Brain² AI features. Missing for 10: any documentation of an AI-training opt-out setting, privacy/data-processing policy statement, or enterprise data-usage controls.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   ClickUp—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy/compliance settings for AI features or workspace data; all citations concern API/MCP functionality, integrations, and product features. missing for 10: retention policy docs, deletion/export controls, data-processing/DPA or privacy center references, AI-training opt-out settings.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings, privacy controls, or data collection disclosures for ClickUp or its AI features; the community comments mention 'trackers' in passing but with no concrete detail on opt-out mechanisms. missing for 10: privacy/telemetry documentation, opt-out settings or controls, any first-party statement on data collection for AI features.

   • [community] “I think ClickUp gets the dubious honour of being my least favourite piece of software of all time. Super slow to load, clunky, unbelievably …”

   proof ↗⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

Ai insights

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

   weight 2 · round to ClickUp
   ClickUp✓fullclaimed7/10

   ClickUp Brain² explicitly answers complex questions by checking workspace tasks/docs/conversations and connected apps for insights (clickup-docs-9, clickup-docs-20, clickup-docs-10), and MCP search tool retrieves items across the workspace (clickup-docs-38), supporting instant answers grounded in workspace content. Missing for 10: explicit documentation of inline 'citations' UI in answers and independent hands-on verification of citation accuracy.

   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
   • [claimed-docs] “Brain² taps Google Drive, GitHub, Salesforce, and more to get you answers and insights.”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”
   • [claimed-docs] “Brain² picks the best AI model for each job. One subscription. Every frontier model running with full context.”

   proof ↗⚑ flag

   Notion~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to ClickUp
   ClickUp✓fullclaimed7/10

   ClickUp's MCP server documentation explicitly lists building executive reports, release notes, status updates, and portfolio summaries from tasks and docs, and Brain² is described as seeing real-time tasks/docs/conversations to answer questions without a brief — directly matching the story of AI drafting status updates from recent activity. Missing for 10: independent/hands-on verification that generated status updates are high quality, and no example output or benchmark beyond first-party marketing/docs copy.

   • [claimed-docs] “**Build executive reports**: Create release notes, status updates, and portfolio summaries from tasks and docs.”
   • [claimed-docs] “Brain² sees your tasks, docs, and conversations. It doesn't need a brief because it knows what's happening in real-time.”
   • [claimed-docs] “Ask something complex. Brain² checks your workspace, apps, and the web for answers.”
   • [claimed-docs] “The Model Context Protocol (MCP) is a secure, standardized framework that lets external AI agents interact with ClickUp Workspace data—like …”

   proof ↗⚑ flag

   Notion~partialclaimed4/10

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

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

   proof ↗⚑ flag

Dashboards

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

   weight 2 · round drawn
   ClickUp—none0/10

   The evidence pack lists many ClickUp features (Time Tracking, Whiteboards, Automations, Sprints, Docs, Chat, Proofing) and API/MCP capabilities, but nowhere mentions ClickUp's Dashboards or configurable widgets for reporting on project progress. The closest item, clickup-docs-40, only describes AI-generated 'executive reports' via MCP, not an interactive dashboard-building capability.

   ⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   ClickUp~partialclaimed3/10

   The evidence only shows a passing AI-assistant capability to 'build executive reports' and 'portfolio summaries' via the MCP server, with no documentation of ClickUp's native Dashboards/Portfolio views, cross-project rollup widgets, or multi-project reporting UI. Missing for 10: dedicated portfolio/dashboard feature docs, cross-list/cross-space rollup mechanics, and independent corroboration of a true portfolio view.

   • [claimed-docs] “**Build executive reports**: Create release notes, status updates, and portfolio summaries from tasks and docs.”
   • [claimed-docs] “Search Workspace | Searches for items across the entire ClickUp Workspace, including tasks, Lists, Folders, and Docs.”

   proof ↗⚑ flag

   Notion~partialcommunity3/10

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

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

   proof ↗⚑ flag

Access control

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

   weight 2 · round drawn
   ClickUp—none0/10

   No evidence in the pack mentions an admin audit log or activity/security log feature for workspace actions; documentation focuses on API, integrations, and AI agent features. Missing for 10: any mention of an audit log, admin security/activity tracking feature, or documentation of log export/review.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   The evidence pack contains no mention of ClickUp's permissions/roles system (e.g., role-based access control, custom permissions per space/folder/list, guest permissions) — only API authentication (personal tokens/OAuth), which is developer-integration auth, not workspace user permission/role management. No first-party or community evidence describes granular view/edit access control features. missing for 10: documentation of role-based permissions, custom roles, guest/view-only access, space/folder/list-level permission settings.

   • [claimed-docs] “Use a personal API token for individual or testing purposes. Personal tokens begin with `pk_`.”
   • [claimed-docs] “To allow others to use your app, implement the OAuth2 flow so each user has their own token for accessing their ClickUp resources.”

   proof ↗⚑ flag

   Notion—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round drawn
   ClickUp—none0/10

   No evidence pack items mention private sub-teams, restricted spaces, member-level access controls, or Teams/user groups with restricted membership in ClickUp; the pack covers API, MCP, AI agents, and integrations only. This axis is applicable to a project-management tool but no supporting evidence is present.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

4. engineerSecure organization access with SSO and SAML

   weight 3 · round drawn
   ClickUp—none0/10

   No evidence pack items mention SSO, SAML, or enterprise identity/access management features; authentication docs only cover personal API tokens and OAuth2 for app integrations, not organizational SSO/SAML.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

Trust reliability

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

   weight 3 · round drawn
   ClickUp—none0/10

   No evidence of a published uptime SLA or a public status page for real-time incident status; the evidence pack covers API docs, MCP server, integrations, and product features but nothing about SLA/status page. This is a fair axis for a SaaS product to publish, so absence is 'none' rather than 'na'.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   ClickUp—none0/10

   No evidence in the pack references documented support response times, SLAs, or support tiers for any ClickUp plan; the pack covers API, MCP, integrations, and community sentiment only.

   ⚑ flag

   Notion—none0/10

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

   ⚑ flag