Attio vs Twenty
free-tier · subscription-per-seat · enterprise-custom
·open-source · subscription-per-seat · usage-based
Twenty wins · 10–29 (10 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnAttio directly hosts a working llms.txt at docs.attio.com/llms.txt (verified via probe returning HTTP 200 with structured doc links), confirming agents can be pointed at agent-oriented documentation, and this is corroborated by an official MCP endpoint for AI tool integration. missing for 10: independent third-party confirmation beyond the direct probe.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”
- [probe] “official MCP server documented at https://attio.com/mcp”
- [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
A direct probe confirms llms.txt is live at docs.twenty.com/llms.txt returning HTTP 200 with structured navigation content, and Twenty's docs are also organized in agent-friendly markdown (.md endpoints) referenced throughout the evidence pack. Missing for 10: no independent/community confirmation of an agent successfully consuming llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.twenty.com/llms.txt # Twenty Documentation ## Getting Started ### Welcome - [Why Twenty](https:/…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to AttioAttio exposes a REST API, OAuth, webhooks, and SQL query access that let developers script and automate workspace actions headlessly outside the UI, and probes confirm a real API/docs surface (llms.txt, MCP server) rather than pure marketing. However, there is no mention of a CLI, SDK for CI pipelines, or any CI-specific tooling/guide, so the 'run in CI' half of the story is unevidenced. Missing for 10: CLI or CI-pipeline integration guide, examples of scheduled/headless jobs, official SDK usable in build pipelines.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “Building an OAuth flow for your app”
- [claimed-docs] “Run SQL queries against your workspace data.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
Twenty can be self-hosted via a single Docker Compose command and exposes full REST/GraphQL APIs (including a Metadata API) for programmatic, UI-less interaction, which supports scripted/automated deployment and data operations. However, there is no explicit documentation of a headless mode, CI pipeline integration, or automated testing workflow — the evidence only covers deployment and API access, not CI-oriented usage. Missing for 10: explicit CI/CD examples, headless execution mode, automated test-runner support, and independent confirmation of running unattended in pipelines.
- [claimed-docs] “Run Twenty on your own infrastructure with a single Docker Compose command.”
- [claimed-docs] “Install the latest stable version of Twenty with a single command: bash <(curl -sL https://raw.githubusercontent.com/twentyhq/twenty/main/pa…”
- [claimed-docs] “This guide provides step-by-step instructions to install and configure the Twenty application using Docker Compose.”
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “when you add a custom object (say Invoice), it immediately gets REST and GraphQL endpoints identical to built-in objects like Company or Per…”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnAttionone0/10Evidence shows Attio ships its own MCP server so external AI tools (Claude, ChatGPT) can connect to and control Attio (attio-docs-3, attio-probe-3), but this is the reverse of the story — there is no evidence Attio itself can plug in and consume external MCP servers' tools.
- [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
- [probe] “official MCP server documented at https://attio.com/mcp”
Twentynone0/10The only MCP-related evidence is a pricing table line item 'MCP server | Yes' (twenty-docs-32), which indicates Twenty exposes an MCP server for others to call its own tools — not that Twenty acts as an MCP client that can plug in external MCP servers so its AI agents can use their tools. No documentation describes configuring or connecting external MCP servers within Twenty's AI agent framework (twenty-docs-5, twenty-docs-18, twenty-docs-56 describe agents but only mention internal actions like enrichment, not external MCP tool integration).
- [claimed-docs] “MCP server | Yes | Yes | Yes”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “Ask questions about your data in natural language. The AI chatbot can query your CRM records, summarize information, and help you find what …”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
ai-native userConnect an agent via an official MCP server
weight 3 · round to AttioAttio documents an official MCP server (attio.com/mcp) explicitly enabling connection of Claude, ChatGPT, or other AI tools to search, update, and manage the workspace, and a probe confirms this page exists. Missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice and more detail on setup/auth specifics.
- [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
- [probe] “official MCP server documented at https://attio.com/mcp”
Twenty's pricing page explicitly lists 'MCP server | Yes | Yes | Yes' across all plans, confirming an official MCP server offering that would let AI agents connect. However, this is the only evidence — there's no dedicated documentation page explaining setup, capabilities, or authentication for the MCP server, and no independent/hands-on corroboration of it working. Missing for 10: dedicated MCP server docs/setup guide, independent verification that it works, details on scope/permissions for MCP connections.
- [claimed-docs] “MCP server | Yes | Yes | Yes”
ai-native userUse an official CLI
weight 2 · round to TwentyAttionone0/10Attio is a CRM SaaS platform whose ecosystem could plausibly ship an official CLI, but the evidence pack contains no mention of a CLI tool anywhere—only REST API, webhooks, SQL query access, and an MCP server for AI assistants. Absence of evidence for this applicable capability yields none.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Run SQL queries against your workspace data.”
- [probe] “official MCP server documented at https://attio.com/mcp”
Twenty ships an official CLI (`npx create-twenty-app`, `npx twenty app:publish`) documented in the GitHub README for scaffolding apps and defining objects/fields/views as code, satisfying the 'official CLI' axis. Missing for 10: independent/hands-on corroboration of the CLI's reliability, and documentation of broader CLI capabilities beyond app scaffolding/publishing (e.g., data or workflow management from the CLI).
- [github] “Scaffold a new app with the Twenty CLI: npx create-twenty-app my-app ... Define objects, fields, and views as code”
- [github] “npx twenty app:publish --private”
- [github] “npx create-twenty-app my-app ... npx twenty app:publish --private”
- [github] “Scaffold a new app with the Twenty CLI: npx create-twenty-app my-app”
- [github] “Define objects, fields, and views as code”
ai-native userDrive the product through a documented public API
weight 3 · round drawnAttio documents a REST API for reading/writing workspace data, OAuth flows, filtering/sorting, rate limiting, and webhooks, giving AI-native users a fully documented public API to drive the product; llms.txt and docs.attio.com confirm developer-facing documentation. missing for 10: no discoverable OpenAPI/Swagger spec (probe found 404s) and no independent/third-party corroboration beyond vendor docs.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
- [claimed-docs] “Building an OAuth flow for your app”
- [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
Twenty documents a developer-first public API with both REST and GraphQL endpoints, auto-generated per-workspace docs, a Metadata API for programmatic schema changes, batching support, and scoped API keys — plus community confirmation that the REST API works hands-on. missing for 10: independent verification of documentation completeness/quality (probe found no discoverable OpenAPI spec at standard paths) and more third-party corroboration beyond one HN comment.
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “when you add a custom object (say Invoice), it immediately gets REST and GraphQL endpoints identical to built-in objects like Company or Per…”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
- [claimed-docs] “Keys can be scoped to a specific role under Settings → Members → Roles → Assignment tab to limit what they can access.”
- [claimed-docs] “Both REST and GraphQL support batching up to 60 records per request — create, update, or delete. GraphQL also supports batch upsert”
- [claimed-docs] “when you add a custom object (say `Invoice`), it immediately gets REST and GraphQL endpoints identical to built-in objects like `Company` or…”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.twenty.com/openapi.json, https://docs.twenty.com/swagger.json, https://docs.twenty.com/…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to TwentyAttionone0/10Attio documents a general OAuth flow for third-party apps (attio-docs-7) and an MCP server for AI tools (attio-probe-3), but there is no evidence of granular, least-privilege scopes or agent-specific API credential issuance — no mention of scope lists, permission levels, or restricting an API key/token to specific objects/actions for an AI agent.
- [claimed-docs] “Building an OAuth flow for your app”
- [probe] “official MCP server documented at https://attio.com/mcp”
Twenty's docs explicitly state API keys can be scoped to a specific role to limit access (twenty-docs-24), backed by granular RBAC at object/field/record level (twenty-docs-7, twenty-docs-39, twenty-docs-54) and an explicit permission model constraining AI agents to only what the user/role can view (twenty-docs-19, twenty-docs-5). This directly supports issuing least-privilege credentials for an agent. Missing for 10: independent/hands-on verification that role-scoped keys work as documented, and no explicit agent-specific key-issuance workflow beyond general role scoping.
- [claimed-docs] “Keys can be scoped to a specific role under Settings → Members → Roles → Assignment tab to limit what they can access.”
- [claimed-docs] “Role-based access control at every level — objects, fields, and individual records. Configure SSO with SAML or OIDC.”
- [claimed-docs] “Role-based access control at every level — objects, fields, and individual records. Configure SSO with SAML or OIDC. Audit logs track who di…”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
ai-native userBuild against official SDKs
weight 2 · round to TwentyAttio documents a REST API, OAuth flow, webhooks, and a TypeScript-based 'Apps' framework for building on the platform, which functions as a developer toolkit, but there is no explicit mention of dedicated official client SDKs (e.g., named Node.js/Python/Go libraries), and the OpenAPI spec probe returned 404s, suggesting no auto-generated or downloadable SDK artifacts. Missing for 10: named official language SDK packages/libraries, published SDK versioning/changelog, and independent developer corroboration of SDK usage.
- [claimed-docs] “This allows developers to embed Typescript React applications within the Attio interface and run server functions with access to our REST AP…”
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Building an OAuth flow for your app”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
Twenty offers a developer-first REST/GraphQL API with auto-generated docs, a Metadata API, an official CLI (`create-twenty-app`) for scaffolding apps as code, and an MCP server offering (listed on pricing), all of which support AI-native builders. However, there is no explicit 'official SDK' (e.g., published npm/pip client library) mentioned, and a probe found no discoverable OpenAPI spec, undercutting the auto-generated-docs claim. Missing for 10: named official SDK packages in specific languages, independent/hands-on confirmation of building against these APIs, and a working OpenAPI/schema endpoint.
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “when you add a custom object (say Invoice), it immediately gets REST and GraphQL endpoints identical to built-in objects like Company or Per…”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
- [github] “Scaffold a new app with the Twenty CLI: npx create-twenty-app my-app ... Define objects, fields, and views as code”
- [github] “npx create-twenty-app my-app ... npx twenty app:publish --private”
- [claimed-docs] “MCP server | Yes | Yes | Yes”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.twenty.com/openapi.json, https://docs.twenty.com/swagger.json, https://docs.twenty.com/…”
ai-native userSubscribe to events via webhooks
weight 2 · round to AttioAttio's REST API docs explicitly describe webhook subscriptions for real-time change events, including signed payloads for verification, which directly satisfies subscribing to events via webhooks. Missing for 10: independent/hands-on corroboration beyond vendor docs, and details on event-type granularity/filtering for webhook subscriptions.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “We cryptographically sign every webhook request using your webhook secret, and include it as HTTP header called `Attio-Signature`”
Twenty's workflow engine can trigger on record changes/schedules/incoming webhooks and chain an 'HTTP request' step (e.g., Slack alert on deal stage change), effectively enabling outbound webhook-style notifications for events — but there's no documented first-class 'webhook subscription' API where an external AI agent registers a URL to be notified of arbitrary CRM events. Missing for 10: explicit webhook subscription/registration endpoint or events API, documentation of supported event types/payloads for outbound webhooks, and independent confirmation this works reliably.
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
- [claimed-docs] “Workflows let you automate repetitive tasks and connect Twenty to external tools — without writing code (though you can if you want to).”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to TwentyAttio's AI platform docs describe in-product AI features like buying-signal detection, call transcription and analysis, account briefs, AI-driven workflow agents (scoring, routing, web research), and 'search, update, create with AI' surfaced directly in the CRM, which match the story of AI-generated insights/suggestions from workspace data. Missing for 10: independent/hands-on verification of these AI insight features in real use (all evidence is vendor marketing copy) and detail on underlying model/accuracy.
- [claimed-docs] “Search, update, and create with AI.”
- [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
- [claimed-docs] “AI records, transcribes, and logs every call as you speak.”
- [claimed-docs] “AI picks up buying signals, blockers, or requests during the call, not days later.”
- [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
- [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
- [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
- [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
Twenty ships a natural-language AI chatbot that queries CRM records, summarizes information, and finds answers without building filters, plus AI agents that enrich records and execute multi-step tasks autonomously within permission boundaries. This directly delivers AI-generated insights/suggestions from the user's own data inside the product. Missing for 10: independent/hands-on validation of the AI chatbot and agent quality (only vendor docs), and no evidence of proactive/unprompted suggestions beyond query-driven and record-enrichment use cases.
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “Ask questions about your data in natural language. The AI chatbot can query your CRM records, summarize information, and help you find what …”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to TwentyAttio documents workflow automations with triggers (e.g., new deal created) and AI-driven 'agents' (Web Agent, Routing Agent, Scoring Agent) that run automatically in the background, plus webhooks for real-time event handling. However, there's no independent/hands-on evidence of true autonomous multi-step agentic execution or scheduling reliability beyond first-party marketing copy. Missing for 10: independent verification of autonomous background execution, details on failure handling/monitoring of these automations, and evidence beyond vendor marketing pages.
- [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
- [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
- [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
- [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
- [claimed-docs] “When a new deal is created / Trigger when a new deal record is created.”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
Twenty's workflow engine supports triggers on schedules, record changes, and webhooks, chaining actions including AI Agent steps, code execution, and delays—enabling automations that run autonomously in the background without user intervention. Docs further describe AI agents executing multi-step tasks autonomously (enrichment, chat) within a permission model. Missing for 10: independent/hands-on verification that scheduled/background workflows run reliably at scale, and detail on monitoring or retry/error handling for failed autonomous runs.
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
- [claimed-docs] “Workflows let you automate repetitive tasks and connect Twenty to external tools — without writing code (though you can if you want to).”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to TwentyAttio has built-in AI features that act as an assistant: search/update/create with AI, drafting follow-ups, updating records, scheduling next steps, building account briefs, and even building workflows by describing a goal, plus AI call transcription and signal detection. This shows delegable AI assistant tasks embedded in the product, but evidence lacks detail on a dedicated chat-style assistant UI, task delegation scope, or independent hands-on confirmation of reliability. missing for 10: independent/hands-on validation of assistant behavior, clarity on assistant UI/interaction model, and limits/scope of delegable tasks.
- [claimed-docs] “Search, update, and create with AI.”
- [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
- [claimed-docs] “AI records, transcribes, and logs every call as you speak.”
- [claimed-docs] “AI picks up buying signals, blockers, or requests during the call, not days later.”
- [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
Twenty documents built-in AI agents that operate autonomously within the CRM—answering questions, enriching records, and executing multi-step tasks—scoped by the user's permission model, plus a natural-language AI chatbot for querying data, both delegated to within the product itself. Missing for 10: independent/hands-on verification of the AI assistant's real-world reliability and no community evidence corroborating this specific AI feature (community feedback predates the AI feature and is unrelated).
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “Ask questions about your data in natural language. The AI chatbot can query your CRM records, summarize information, and help you find what …”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
ai-native userOperate the product with natural-language commands
weight 2 · round to AttioAttio explicitly documents natural-language control via AI: connecting Claude/ChatGPT to search, update and manage the workspace, an official MCP server, and AI features to search/update/create records and build workflows just by describing goals. This directly matches the story of operating the product via natural-language commands, though evidence is vendor-documented without independent hands-on verification. missing for 10: independent/third-party confirmation of natural-language command reliability, and depth on limits/edge cases of NL command coverage.
- [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
- [claimed-docs] “Search, update, and create with AI.”
- [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
- [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
- [probe] “official MCP server documented at https://attio.com/mcp”
Twenty's docs describe a built-in AI chatbot that lets users 'ask questions about your data in natural language' to query records, summarize info, and avoid building complex filters, plus autonomous AI agents that execute multi-step tasks within the CRM under the user's permission model. This directly satisfies the natural-language operation story for an AI-native user. Missing for 10: independent/hands-on verification of the chatbot's reliability and no community reports confirming it works as documented in practice.
- [claimed-docs] “Ask questions about your data in natural language. The AI chatbot can query your CRM records, summarize information, and help you find what …”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to TwentyAttionone0/10The docs describe REST API concepts (filtering, webhooks, rate limits, OAuth) but there is no mention of an interactive API reference or runnable/try-it examples, and a probe found no discoverable OpenAPI spec at any standard path, suggesting no such interactive console exists.
- [claimed-docs] “Building an OAuth flow for your app”
- [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
Docs mention a 'developer-first API' with 'auto-generated documentation per workspace' for both GraphQL and REST endpoints (twenty-docs-8), implying some interactive per-workspace API reference, but there is no explicit description of runnable/try-it-out examples, and a probe for a standard OpenAPI/Swagger endpoint at the docs domain returned 404s (inconclusive since it wasn't the per-workspace endpoint). Missing for 10: explicit confirmation of an interactive 'try it out' console, screenshots or docs describing runnable code examples, and independent corroboration that the auto-generated docs are interactive rather than static.
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.twenty.com/openapi.json, https://docs.twenty.com/swagger.json, https://docs.twenty.com/…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to TwentyAttionone0/10Direct probes for OpenAPI/Swagger spec files at Attio's docs domain all returned 404, and no evidence pack item references a downloadable machine-readable API spec despite extensive REST API documentation.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
Docs state the API is REST + GraphQL with 'auto-generated documentation per workspace' (twenty-docs-8), implying some machine-readable spec exists, and the Metadata API can describe the schema programmatically (twenty-docs-23/43). However, no evidence confirms a concrete OpenAPI/Swagger file is downloadable, and a direct probe for standard OpenAPI paths on the docs site returned 404s, leaving the claim unconfirmed. Missing for 10: a documented/downloadable OpenAPI or GraphQL SDL export endpoint, and hands-on confirmation that the 'auto-generated documentation per workspace' is actually machine-readable (e.g., JSON schema) rather than just human-readable docs.
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
- [claimed-docs] “Metadata API — Schema management: create/modify/delete objects, fields, and relations. This is how you programmatically change your data mod…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.twenty.com/openapi.json, https://docs.twenty.com/swagger.json, https://docs.twenty.com/…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnAttionone0/10No evidence of a sandbox/test workspace or staging environment separate from production; docs cover API, objects, workflows, and MCP but nothing about sandbox testing without touching live data.
Twentynone0/10No evidence of a sandbox/staging environment, test workspace, or non-production mode for safely testing AI agents or workflows separate from live data. Self-hosting via Docker Compose could theoretically allow spinning up a separate instance, but this is never documented as a sandbox testing feature. missing for 10: dedicated sandbox/staging environment, data seeding/test-mode tooling, documentation of testing AI agents against non-production data.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnAttionone0/10No evidence of API versioning scheme or a documented deprecation policy; the docs cover REST API features (filtering, webhooks, rate limits, OAuth) but nothing about version numbers, changelogs, or deprecation timelines. OpenAPI spec probes also 404'd, further suggesting no clear versioned contract is published.
- [claimed-docs] “Building an OAuth flow for your app”
- [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
Twentynone0/10Evidence documents REST/GraphQL APIs with auto-generated docs and metadata endpoints, but there is no mention of API versioning scheme or a documented deprecation policy anywhere in the pack; probe results even show openapi spec endpoints returning 404.
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “when you add a custom object (say Invoice), it immediately gets REST and GraphQL endpoints identical to built-in objects like Company or Per…”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.twenty.com/openapi.json, https://docs.twenty.com/swagger.json, https://docs.twenty.com/…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to TwentyAttio's REST API supports filtering/sorting to narrow record sets and has SQL query access, and its API/MCP integration could enable scripted bulk updates, but there is no explicit documentation of a bulk-update/bulk-create/bulk-delete endpoint or batch operation limits for AI-driven mass edits. missing for 10: explicit bulk write/update API endpoints, documented batch size limits, and evidence of AI agents performing bulk operations across many records at once.
- [claimed-docs] “Run SQL queries against your workspace data.”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
- [claimed-docs] “Filtering and sorting > Searching for just the records you need”
- [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request.”
- [probe] “official MCP server documented at https://attio.com/mcp”
Twenty's REST and GraphQL APIs explicitly support batching up to 60 records per request for create/update/delete, plus GraphQL batch upsert, and CSV/XLSX/API import with unlimited records for large-scale migrations, alongside export up to 20,000 records — directly enabling bulk operations across many items. Missing for 10: independent/hands-on verification of batch API limits in practice and no documented bulk-delete-via-filter or bulk-edit-in-UI feature beyond import/export and API batching.
- [claimed-docs] “Both REST and GraphQL support batching up to 60 records per request — create, update, or delete. GraphQL also supports batch upsert”
- [claimed-docs] “Import data from CSV files or via API. Field mapping, duplicate detection, and error handling built in. Export your data anytime — no loc…”
- [claimed-docs] “API Import — Large-scale migrations, automation — Unlimited”
- [claimed-docs] “Export your workspace data for backups, reporting, or migration. ... Export limits: Up to 20,000 records per export.”
- [claimed-docs] “Map your columns to Twenty fields ... Review errors (highlighted in yellow) and fix them, directly editing in the UI”
- [claimed-docs] “You can import data for any object using CSV, XLSX, or XLS files. Each file should contain only one type of object (e.g., only People record…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to TwentyAttio's Workflows platform explicitly supports event-based triggers (e.g. 'trigger when a new deal record is created') that fire automated actions/agents (routing, scoring, web research agents), and webhooks/REST API allow custom event-driven automation. Missing for 10: detailed documentation of the full trigger/condition/action rule-builder UI, and independent/hands-on verification of complex multi-step automation reliability.
- [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”
- [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
- [claimed-docs] “When a new deal is created / Trigger when a new deal record is created.”
- [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
- [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
- [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
Twenty's Workflows feature explicitly supports rule-based automation: triggers on record changes, schedules, manual actions, or incoming webhooks, chaining actions like record operations, HTTP requests, code, branches, AI Agent steps, Slack alerts, and enrichment — a clear rules-trigger-actions automation engine documented with concrete examples (deal stage → Slack alert, new contact → enrichment). Missing for 10: independent hands-on verification of workflow reliability/complexity limits beyond docs and one general community note about alpha-stage issues (not specific to workflows).
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
- [claimed-docs] “Workflows let you automate repetitive tasks and connect Twenty to external tools — without writing code (though you can if you want to).”
- [claimed-docs] “Code — Run custom JavaScript for complex logic”
- [claimed-docs] “Workflows let you automate repetitive tasks and connect Twenty to external tools — without writing code”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to TwentyAttio's workflows platform supports event-triggered automations (e.g., 'when a new deal is created') and AI agents that run continuously (routing, scoring, web research), implying ongoing/ongoing-scheduled automation, but there is no explicit documentation of cron-like recurring/time-based scheduling of jobs. Missing for 10: explicit recurring/scheduled job trigger (e.g., 'run every day/week'), documentation of interval-based automation, and independent confirmation of scheduling reliability.
- [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”
- [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
- [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
- [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
- [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
- [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
Twenty's workflow engine explicitly supports schedule-based triggers alongside record changes, manual actions, and webhooks, and workflows can chain multi-step actions (HTTP, code, branches, AI agent, delay) enabling recurring automation chains. Missing for 10: independent/hands-on confirmation of recurrence configuration (e.g., cron intervals) and no community validation of schedule-trigger reliability.
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Workflows let you automate repetitive tasks and connect Twenty to external tools — without writing code (though you can if you want to).”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnAttionone0/10No evidence of version history, review workflows, or rollback for Attio's automations/workflows; docs describe building and triggering workflows but nothing about versioning or reverting them. missing for 10: version history for automations, change review/approval process, rollback mechanism, audit trail of automation edits.
Twentynone0/10The evidence describes Twenty's workflow builder (triggers, chaining actions, code steps) but contains no mention of version history, change review, or rollback capability for workflows/automations. Missing for 10: any documentation of workflow version tracking, diff/review UI, or rollback/undo mechanism for automations.
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Workflows let you automate repetitive tasks and connect Twenty to external tools — without writing code (though you can if you want to).”
- [claimed-docs] “Code — Run custom JavaScript for complex logic”
Automation workflows — building automations — triggers, actions, branching, schedulingAutomation workflows
Building automations — triggers, actions, branching, scheduling
Workflows
ops userRoute new leads to the right owner automatically with assignment rules or round-robin
weight 2 · round to AttioAttio's Workflows platform explicitly includes a 'Routing Agent' that 'routes every lead to the right rep or channel' and a 'Scoring Agent' that assigns fit based on ICP criteria, directly supporting automated lead assignment; workflows can also trigger on new record creation. However, evidence is all vendor marketing copy with no configuration detail on round-robin logic, tie-breaking, or capacity balancing, and no independent/hands-on confirmation. Missing for 10: detailed documentation of round-robin/assignment rule configuration options, independent or hands-on validation of the Routing Agent in practice, and evidence of load-balancing or fairness logic.
- [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
- [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
- [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
- [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”
Twentynone0/10Twenty's workflow engine (record-change triggers, branches, record operations, code) could theoretically be scripted to assign owners, but there is no documented assignment-rule or round-robin lead-routing feature anywhere in the evidence pack.
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
ops userBuild trigger-based workflows that update records, create tasks, and send notifications automatically
weight 3 · round to TwentyAttio documents workflows platform with triggers (e.g., 'when a new deal is created') and automated agents that route leads, score leads, and update records, plus webhooks for real-time notifications and REST API for record updates — covering the core story elements. However, evidence is mostly marketing-page descriptions rather than detailed workflow-builder documentation showing task creation or multi-step conditional logic, and no independent/hands-on confirmation of reliability. Missing for 10: detailed docs on workflow builder UI/logic, explicit task-creation trigger actions, and independent verification of automation reliability.
- [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
- [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
- [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
- [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “We cryptographically sign every webhook request using your webhook secret, and include it as HTTP header called `Attio-Signature`”
- [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”
Twenty's docs directly describe trigger-based workflows (record changes, schedules, manual, webhooks) that can chain record operations, send email, HTTP requests, code, branches, and specifically cite examples like Slack alerts on deal stage changes and auto-enriching contacts, matching the ops story's update/create/notify pattern. Missing for 10: independent hands-on validation of workflow reliability in production (community evidence flags general 'alpha' rough edges) and no explicit dedicated 'create task' workflow action example beyond generic record operations.
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
- [claimed-docs] “Workflows let you automate repetitive tasks and connect Twenty to external tools — without writing code (though you can if you want to).”
- [claimed-docs] “Code — Run custom JavaScript for complex logic”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
Contacts companies — stories about contacts companies in this arenaContacts companies
Stories about contacts companies in this arena
Ai crm ops
ai-native userHave an agent enrich a new lead end-to-end via the API or MCP server — creating the record, filling company data, and assigning an owner
weight 3 · round drawnAttio has a documented REST API for creating/updating records (attio-docs-2, attio-docs-8/9/14) and an official MCP server (attio-probe-3, attio-docs-3, attio-docs-12) letting AI tools search, update and create records, and separately advertises 'automatic data enrichment' (attio-docs-26/45/47). However, there is no explicit documentation showing an end-to-end workflow of creating a lead, auto-filling company data, and assigning an owner in one API/MCP call chain — owner-assignment and enrichment-via-API/MCP specifics are unevidenced. Missing for 10: explicit API/MCP example of owner assignment, documented enrichment endpoint/field mapping, and a hands-on end-to-end example combining all three steps.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
- [claimed-docs] “Search, update, and create with AI.”
- [claimed-docs] “Real-time contact syncing Automatic data enrichment”
- [claimed-docs] “Real-time contact syncing Automatic data enrichment Up to 3 seats”
- [claimed-docs] “Automatic data enrichment”
- [probe] “official MCP server documented at https://attio.com/mcp”
- [claimed-docs] “Create the exact data model your business needs with custom objects.”
- [claimed-docs] “Link objects to make your data actionable and insightful with our powerful graph model.”
- [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
Twenty documents an MCP server (twenty-docs-32) and AI agents that can 'enrich records with data from external sources' and execute multi-step tasks (twenty-docs-56, twenty-docs-5), plus a developer API capable of creating custom-object records (twenty-docs-8, twenty-docs-22) and workflows that 'auto-enrich new contacts with data from external APIs' (twenty-docs-14). However, there is no explicit documentation of an agent assigning a record owner as part of this flow, nor a concrete end-to-end example (lead creation + enrichment + owner assignment) via API or MCP, and no independent/hands-on confirmation that the MCP server performs this workflow. Missing for 10: explicit owner-assignment step in agent/API flow, a documented end-to-end example combining all three actions, independent verification of MCP server behavior.
- [claimed-docs] “MCP server | Yes | Yes | Yes”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “when you add a custom object (say Invoice), it immediately gets REST and GraphQL endpoints identical to built-in objects like Company or Per…”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
Data quality
ops userHave contact and company records auto-enriched with firmographic and contact data
weight 2 · round drawnAttio's pricing page explicitly lists 'Automatic data enrichment' and 'Real-time contact syncing' as features, and the platform data page mentions prospect context 'automatically drawn from 100' (sources, cut off), suggesting some enrichment capability. However there's no detail on what firmographic/contact data sources are used, how enrichment is triggered/configured, or coverage/accuracy — missing for 10: documentation of enrichment data providers, configuration/setup details, coverage scope, and independent/hands-on verification of enrichment quality.
- [claimed-docs] “Real-time contact syncing Automatic data enrichment”
- [claimed-docs] “Real-time contact syncing Automatic data enrichment Up to 3 seats”
- [claimed-docs] “Automatic data enrichment”
- [claimed-docs] “Real-time contact syncing”
- [claimed-docs] “Get the context you need for every prospect, automatically drawn from 100”
Docs mention enrichment only as an example built via custom Workflows (HTTP request to an external API) and via AI Agents that can 'enrich records with data from external sources,' but there's no evidence of a built-in, native firmographic/contact enrichment provider or one-click integration—it requires the ops user (or a dev) to configure a workflow or agent with a third-party data source. Missing for 10: a native/pre-built enrichment integration (e.g., built-in data provider), independent/hands-on confirmation that enrichment works as advertised, and detail on what firmographic data fields are actually populated.
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
ops userDetect duplicate contacts or companies and merge them without losing data
weight 2 · round to TwentyAttionone0/10No evidence pack item mentions duplicate detection or record merging for contacts/companies; docs cover objects, lists, filtering, webhooks, and AI features but nothing about dedupe/merge workflows.
Docs confirm duplicate detection during CSV/API import (twenty-docs-9), but there is no evidence of a dedicated merge tool or workflow for combining existing duplicate Contact/Company records without losing data — only prevention-at-import is documented. missing for 10: explicit merge UI/feature for existing duplicates, data-preservation guarantees during merge, independent/hands-on confirmation of merge behavior.
- [claimed-docs] “Import data from CSV files or via API. Field mapping, duplicate detection, and error handling built in. Export your data anytime — no loc…”
- [claimed-docs] “Map your columns to Twenty fields ... Review errors (highlighted in yellow) and fix them, directly editing in the UI”
Record management
ops userManage contacts and companies as linked records with a full activity timeline on each
weight 3 · round to AttioAttio's data model natively supports People and Companies as linked objects connected via a graph model, with custom fields, list/table views, and full interaction history surfaced per record (e.g., 'Link objects to make your data actionable' and 'Get instant visibility into the full history of every interaction'). This directly matches the ops story of managing linked contact/company records with activity timelines. missing for 10: independent/hands-on corroboration of the timeline UI itself (only first-party marketing/docs cited), and no explicit screenshot or detailed description of the timeline feed contents.
- [claimed-docs] “Link objects to make your data actionable and insightful with our powerful graph model.”
- [claimed-docs] “Get instant visibility into the full history of every interaction.”
- [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
- [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
- [claimed-docs] “Customize fields to capture exactly what you need to track.”
- [claimed-docs] “From kanbans to tables, visualize your data the way that works for you.”
Twenty's docs confirm core CRM objects (Company/Person) with custom relations, email/calendar auto-linking to records, and workflow/API support, which supports linked-record management, but there is no explicit documentation of a unified 'activity timeline' feature showing notes, emails, calls, and tasks chronologically per record. Community evidence is limited to general alpha-stage caveats, not specific timeline testing. Missing for 10: explicit documentation or screenshots of an activity timeline UI per record, independent/hands-on verification of timeline behavior, and confirmation of what activity types (calls, notes, tasks) populate it.
- [claimed-docs] “You can create custom relations between any objects, including many-to-many relationships.”
- [claimed-docs] “Connect your **Google Workspace** or **Microsoft 365** mailbox. Once connected: Emails are automatically linked to the matching Company and …”
- [claimed-docs] “Emails are automatically linked to the matching Company and People records”
- [claimed-docs] “Emails and calendar events automatically appear on the relevant CRM records.”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
Customization — bending the product to your needs — settings, theming, extension pointsCustomization
Bending the product to your needs — settings, theming, extension points
Data model
ops userAdd custom fields and build filtered, sorted, and shared views without an admin project
weight 2 · round to TwentyAttio's docs confirm custom fields ('Customize fields to capture exactly what you need to track'), filtering/sorting capabilities, and object/list data modeling that ops users could use to build views without engineering, but evidence is API/docs-centric rather than showing the actual no-admin UI workflow for creating and sharing saved views. missing for 10: explicit documentation of the UI-level 'shared views' feature and permission model confirming non-admin ops users can create/share views without admin involvement.
- [claimed-docs] “Customize fields to capture exactly what you need to track.”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
- [claimed-docs] “Filtering and sorting > Searching for just the records you need”
- [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”
- [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
- [claimed-docs] “From kanbans to tables, visualize your data the way that works for you.”
Docs clearly show custom objects/fields (20+ types, unlimited custom objects), table/kanban/calendar views with AND/OR filtering, multi-field sort, grouping, and saved custom views — all configurable in-app without dev involvement, plus community corroboration that customization was 'very promising' and easy to set up. Missing for 10: explicit documentation of 'sharing' a saved view with specific teammates/permissions (only role-based permissions and workspace-level dashboard sharing are documented, not view-sharing specifics) and independent hands-on confirmation of the filter/sort/save-view workflow itself.
- [claimed-docs] “Create custom objects, add custom fields with 20+ field types, and build relationships between any objects.”
- [claimed-docs] “Switch between table views, kanban boards, and calendar views. Filter with AND/OR logic, sort by multiple fields, group records, and save cu…”
- [claimed-docs] “You can create custom relations between any objects, including many-to-many relationships.”
- [claimed-docs] “You can also create custom objects for anything your business needs — projects, support tickets, products, contracts, or anything else.”
- [claimed-docs] “Custom objects get the same first-class treatment as built-in ones — including API endpoints, views, permissions, and workflow triggers.”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
developerModel custom objects with fields and relationships beyond the built-in contacts, companies, and deals
weight 3 · round to TwentyAttio's docs explicitly support creating custom objects with custom fields, and linking objects via a graph model to build relationships beyond the standard people/company/deal objects (attio-docs-8, attio-docs-9, attio-docs-46, attio-docs-29). This is corroborated by API-level guidance for objects and lists as domain modeling primitives. missing for 10: independent/hands-on third-party confirmation of custom object creation limits or relationship types, and deeper API reference detail on relationship/field-type configuration.
- [claimed-docs] “Create the exact data model your business needs with custom objects.”
- [claimed-docs] “Link objects to make your data actionable and insightful with our powerful graph model.”
- [claimed-docs] “Customize fields to capture exactly what you need to track.”
- [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
- [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
Twenty's docs extensively cover creating custom objects, custom fields (20+ types), and building custom relations (including many-to-many) between any objects, with custom objects receiving first-class treatment (API endpoints, views, permissions, workflows) identical to built-ins. This is corroborated by hands-on community feedback praising the customization as 'very promising.' Missing for 10: deeper independent/hands-on verification of complex relationship modeling beyond a single HN mention, and no third-party technical review of the metadata/schema API in practice.
- [claimed-docs] “Create custom objects, add custom fields with 20+ field types, and build relationships between any objects.”
- [claimed-docs] “You can create custom relations between any objects, including many-to-many relationships.”
- [claimed-docs] “Custom objects get the same first-class treatment as built-in ones — including API endpoints, views, permissions, and workflow triggers.”
- [claimed-docs] “You can also create custom objects for anything your business needs — projects, support tickets, products, contracts, or anything else.”
- [claimed-docs] “when you add a custom object (say Invoice), it immediately gets REST and GraphQL endpoints identical to built-in objects like Company or Per…”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
Email sync — stories about email sync in this arenaEmail sync
Stories about email sync in this arena
ops userSync my calendar so meetings appear on contact and deal timelines
weight 2 · round to TwentyAttionone0/10No evidence describes a calendar sync feature that surfaces meetings on contact/deal timelines; mentions of 'real-time contact syncing' and call logging/transcription do not address calendar/meeting sync specifically.
Docs describe connecting Google Workspace/Microsoft 365 accounts so calendar events automatically appear on relevant CRM records (contacts/deals), with filtering controls; calendar view is also supported in record timelines. missing for 10: no independent/hands-on confirmation that calendar sync specifically (vs. email sync) populates deal timelines, and no explicit mention of deal-object calendar linking beyond Company/People.
- [claimed-docs] “Connect your Google Workspace or Microsoft 365 account. Emails and calendar events automatically appear on the relevant CRM records.”
- [claimed-docs] “Emails and calendar events automatically appear on the relevant CRM records.”
- [claimed-docs] “You control what gets imported — filter by date range or sender to avoid pulling in irrelevant emails.”
- [claimed-docs] “Connect your **Google Workspace** or **Microsoft 365** mailbox. Once connected: Emails are automatically linked to the matching Company and …”
- [claimed-docs] “Emails are automatically linked to the matching Company and People records”
ops userConnect Gmail or Outlook so emails sync two-way and log automatically to the right records
weight 3 · round to TwentyAttionone0/10Evidence pack shows general contact syncing/enrichment claims and API/webhook infrastructure, but no mention of Gmail or Outlook two-way email sync or automatic email logging to records anywhere in the docs or probes.
Twenty's docs explicitly describe connecting Google Workspace or Microsoft 365 accounts so emails and calendar events automatically appear on and link to matching Company/People CRM records, with filters to control what gets imported. This is documented first-party functionality directly matching the story, though there is no independent/hands-on confirmation of two-way sync reliability specifically for email. Missing for 10: independent or hands-on verification of the email sync feature itself (the community evidence found only mentions general alpha rough edges, not this feature specifically).
- [claimed-docs] “Connect your Google Workspace or Microsoft 365 account. Emails and calendar events automatically appear on the relevant CRM records.”
- [claimed-docs] “You control what gets imported — filter by date range or sender to avoid pulling in irrelevant emails.”
- [claimed-docs] “Connect your **Google Workspace** or **Microsoft 365** mailbox. Once connected: Emails are automatically linked to the matching Company and …”
- [claimed-docs] “Emails are automatically linked to the matching Company and People records”
- [claimed-docs] “Emails and calendar events automatically appear on the relevant CRM records.”
Outreach
ops userSend templated emails or multi-step sequences to prospects from inside the CRM
weight 2 · round to TwentyAttionone0/10Attio is a CRM with data model, workflows, AI agents, and API/webhook capabilities, but the evidence pack contains no mention of templated email sending or multi-step outbound sequence/cadence functionality for prospects; only 'draft follow-ups' via AI assistant is mentioned, not automated sequences.
Twenty's workflow engine can chain a 'Send email' step with Delay and Branch steps, which could technically be assembled into a multi-step email sequence, and email sync auto-links messages to CRM records — but there is no documented email-template feature, no dedicated 'sequence/cadence' tool for prospects, and no hands-on evidence this is actually used this way. Missing for 10: dedicated templated-email/sequence builder for outbound prospecting, evidence of template management, and independent confirmation of ops teams using workflows this way.
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Code — Run custom JavaScript for complex logic”
- [claimed-docs] “Connect your **Google Workspace** or **Microsoft 365** mailbox. Once connected: Emails are automatically linked to the matching Company and …”
- [claimed-docs] “Emails are automatically linked to the matching Company and People records”
Integrations — connecting to other tools — breadth and depth of built-in integrationsIntegrations
Connecting to other tools — breadth and depth of built-in integrations
Api depth
developerSync records bidirectionally through the API at scale, with documented rate limits, upserts, and change detection
weight 3 · round to AttioAttio's docs confirm a read/write REST API, documented rate limits (429 + Retry-After) and webhooks for real-time change detection, which together support much of the story. However, there is no explicit documentation in the evidence pack of upsert/assert-style endpoints or guidance on syncing at scale (batching, pagination limits, throughput), so the story is only partially covered. missing for 10: explicit upsert endpoint docs, scale/batch sync guidance, independent corroboration of reliability at scale.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “We cryptographically sign every webhook request using your webhook secret, and include it as HTTP header called `Attio-Signature`”
- [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
- [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”
Docs show REST/GraphQL batching (up to 60 records) with GraphQL batch upsert, a Metadata API, and workflow triggers on record changes/webhooks that could support change detection, plus import/export capabilities for large-scale sync. However, no documented API rate limits are provided anywhere in the evidence, and community feedback flags the REST API as 'alpha' with unspecified issues, undercutting confidence in scale reliability. missing for 10: explicit documented rate limits, dedicated change-detection/webhook-for-sync documentation beyond generic workflow triggers, independent verification of sync at scale.
- [claimed-docs] “Both REST and GraphQL support batching up to 60 records per request — create, update, or delete. GraphQL also supports batch upsert”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
- [claimed-docs] “API Import — Large-scale migrations, automation — Unlimited”
- [claimed-docs] “Export your workspace data for backups, reporting, or migration. ... Export limits: Up to 20,000 records per export.”
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
Ecosystem
ops userInstall prebuilt integrations (Slack, support desk, marketing, data warehouse) from an app marketplace
weight 2 · round to TwentyAttionone0/10Evidence shows Attio has a developer platform for building custom apps, REST API, webhooks, and OAuth, plus an AI/MCP connector, but there is no mention of a prebuilt app marketplace with ready-made Slack, support desk, marketing, or data warehouse integrations that ops users can simply install.
- [claimed-docs] “This allows developers to embed Typescript React applications within the Attio interface and run server functions with access to our REST AP…”
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Building an OAuth flow for your app”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”
Twenty supports connecting to external tools via Zapier (5,000+ apps) and lets developers build/publish apps for the community, plus workflow actions like Slack alerts, but there's no evidence of a curated app marketplace with one-click prebuilt integrations specifically for Slack, support desk, marketing, or data warehouse tools — these have to be built as workflows or via Zapier rather than installed as packaged apps. Missing for 10: a dedicated marketplace UI, named prebuilt connectors for support desk/marketing/warehouse categories, and evidence of one-click install rather than custom workflow/code setup.
- [claimed-docs] “Zapier | Connect to 5,000+ apps without code”
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
- [claimed-docs] “Developers can build full-featured apps on top of Twenty — adding custom UI, server-side logic, and deep integrations. Apps can be published…”
- [github] “npx twenty app:publish --private”
- [github] “npx create-twenty-app my-app ... npx twenty app:publish --private”
Onboarding migration — stories about onboarding migration in this arenaOnboarding migration
Stories about onboarding migration in this arena
Imports
ops userMigrate from another CRM with my records, owners, and history intact
weight 2 · round to TwentyAttio references migration mostly via marketing-chat snippets promising deal history mapping and an onboarding migration checklist, but there is no documented import tool, CSV/CRM connector, owner-mapping mechanism, or independent verification that records/owners/history transfer intact. missing for 10: a documented migration tool or CRM-specific importer, evidence of owner/user mapping during migration, independent case studies or hands-on confirmation of successful full-history migration, and details on handling of activity/history data beyond a marketing anecdote.
- [claimed-docs] “we'll map it during onboarding, and I'll include a migration checklist.”
- [claimed-docs] “Can we bring our existing deal history across too? ... Yep — we'll map it during onboarding, and I'll include a migration checklist.”
- [claimed-docs] “Yep — we'll map it during onboarding, and I'll include a migration checklist.”
- [claimed-docs] “Get instant visibility into the full history of every interaction.”
Twenty documents CSV/XLSX/API import with field mapping, duplicate detection, and error handling, plus relation-matching via unique fields (id, email, domain) to preserve links between records like Company/Person — covering the core 'records and relationships' part of migration. However, there's no documented mechanism for preserving record owners (assigning imported records to specific users) or historical activity/timeline data during import, and no case study of an actual CRM-to-CRM migration succeeding end-to-end. Missing for 10: explicit owner-field mapping/preservation during import, migration of activity history/notes/timestamps, and independent evidence of a successful full CRM migration.
- [claimed-docs] “Map your columns to Twenty fields ... Review errors (highlighted in yellow) and fix them, directly editing in the UI”
- [claimed-docs] “You need to reference the related object using a unique field from this object: the id, the email for People and Workspace Members, the doma…”
- [claimed-docs] “You can import data for any object using CSV, XLSX, or XLS files. Each file should contain only one type of object (e.g., only People record…”
- [claimed-docs] “You can import data for any object using CSV, XLSX, or XLS files.”
- [claimed-docs] “API Import — Large-scale migrations, automation — Unlimited”
- [claimed-docs] “Import data from CSV files or via API. Field mapping, duplicate detection, and error handling built in. Export your data anytime — no loc…”
founderImport my spreadsheet of contacts and deals with field mapping and validation, without losing rows silently
weight 3 · round to TwentyMarketing chat snippets mention that Attio will 'map it during onboarding' and provide a 'migration checklist' for bringing over existing spreadsheet/deal data, implying some import support, but there is no actual product documentation describing a CSV/spreadsheet import tool, field-mapping UI, validation rules, or safeguards against silently dropped rows. missing for 10: dedicated import/CSV mapping feature docs, validation/error-reporting behavior, evidence of row-loss prevention, independent user confirmation of successful large imports.
- [claimed-docs] “we'll map it during onboarding, and I'll include a migration checklist.”
- [claimed-docs] “Can we bring our existing deal history across too? ... Yep — we'll map it during onboarding, and I'll include a migration checklist.”
- [claimed-docs] “Yep — we'll map it during onboarding, and I'll include a migration checklist.”
- [claimed-docs] “Everything's in spreadsheets right now and it's getting unmanageable. I'd like the whole team moved over by Monday if we can.”
Docs describe CSV/XLSX/XLS import with column-to-field mapping, duplicate detection, and an error-review UI that highlights bad rows in yellow for in-place fixing rather than silent dropping, plus API-based bulk import for larger migrations. Missing for 10: independent/hands-on verification that no rows are silently lost during real-world large or messy imports, and no detail on what happens to unresolved/invalid rows beyond the UI flagging step.
- [claimed-docs] “Import data from CSV files or via API. Field mapping, duplicate detection, and error handling built in. Export your data anytime — no loc…”
- [claimed-docs] “Map your columns to Twenty fields ... Review errors (highlighted in yellow) and fix them, directly editing in the UI”
- [claimed-docs] “You need to reference the related object using a unique field from this object: the id, the email for People and Workspace Members, the doma…”
- [claimed-docs] “You can import data for any object using CSV, XLSX, or XLS files. Each file should contain only one type of object (e.g., only People record…”
- [claimed-docs] “You can import data for any object using CSV, XLSX, or XLS files.”
- [claimed-docs] “API Import — Large-scale migrations, automation — Unlimited”
Time to value
founderGo from signup to a working pipeline with my real data in under an hour, without an implementation partner
weight 2 · round to TwentyAttio ships default People/Companies objects and optional Deals that can be enabled instantly (attio-docs-14, attio-docs-13), and marketing copy references a migration checklist and same-week team migration (attio-docs-38, attio-docs-39, attio-docs-44), suggesting some self-serve speed. However, these quotes describe 'we'll map it during onboarding' which implies vendor/human-assisted setup rather than a pure self-serve under-an-hour flow, and there is no evidence of a guided import wizard, templates, or time-to-value benchmarks. Missing for 10: concrete self-serve CSV/import tooling, onboarding time benchmarks, evidence that no implementation partner or vendor assistance is needed.
- [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
- [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
- [claimed-docs] “Can we bring our existing deal history across too? ... Yep — we'll map it during onboarding, and I'll include a migration checklist.”
- [claimed-docs] “Everything's in spreadsheets right now and it's getting unmanageable. I'd like the whole team moved over by Monday if we can.”
- [claimed-docs] “Yep — we'll map it during onboarding, and I'll include a migration checklist.”
Docs show fast signup ('spin up a workspace in under a minute'), CSV/XLSX/API import with field mapping and dedup, quick custom-object/pipeline setup via kanban/table views, and one-command self-host — all consistent with rapid, self-serve onboarding without a partner. However, there's no explicit case study or benchmark confirming an actual 'under one hour to working pipeline with real data' outcome, and a hands-on HN review notes Twenty felt 'pretty alpha-version' with small issues that prevented it from fully working for their use case, tempering confidence in a frictionless first hour. Missing for 10: a concrete time-boxed onboarding case study/testimonial, and independent confirmation that data import/pipeline setup reliably completes in under an hour without hitting the rough edges the community mentioned.
- [github] “Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.”
- [claimed-docs] “Import data from CSV files or via API. Field mapping, duplicate detection, and error handling built in. Export your data anytime — no loc…”
- [claimed-docs] “Map your columns to Twenty fields ... Review errors (highlighted in yellow) and fix them, directly editing in the UI”
- [claimed-docs] “You can import data for any object using CSV, XLSX, or XLS files. Each file should contain only one type of object (e.g., only People record…”
- [claimed-docs] “Switch between table views, kanban boards, and calendar views. Filter with AND/OR logic, sort by multiple fields, group records, and save cu…”
- [claimed-docs] “Install the latest stable version of Twenty with a single command: bash <(curl -sL https://raw.githubusercontent.com/twentyhq/twenty/main/pa…”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to TwentyAttio's REST API covers core CRUD on objects/lists, filtering/sorting, webhooks, and OAuth, and there's an official MCP server for AI agent access, suggesting broad parity with UI operations for data management. However, evidence doesn't confirm API parity for newer AI-native workflow builder features (natural-language workflow creation, AI call recording/insights, routing/scoring agents) or reporting/visualization capabilities, and no OpenAPI spec was found to verify full endpoint coverage. Missing for 10: explicit confirmation that all UI-exposed features (AI agents, workflow builder, reporting/dashboards) are API-accessible, and a published OpenAPI spec proving endpoint completeness.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
- [claimed-docs] “Building an OAuth flow for your app”
- [claimed-docs] “Filtering and sorting > Searching for just the records you need”
- [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
- [probe] “official MCP server documented at https://attio.com/mcp”
- [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
- [claimed-docs] “Analyze live data any way you like, from line charts and bar graphs to geospatial mapping.”
Docs claim strong API parity — custom objects get identical REST/GraphQL endpoints, views, permissions, and workflow triggers as built-in objects, plus a Metadata API to programmatically change the data model itself, and API-based imports/exports (twenty-docs-8,12,22,23,41,59). However, no evidence explicitly confirms full API control over dashboards, view configuration (kanban/calendar), or workflow authoring — these are described only as UI-driven, and one community report notes the REST API 'worked ok' but the product was 'pretty alpha-version' with unspecified small issues. missing for 10: explicit docs/proof that dashboards, saved views, and workflow definitions can be created/edited via API rather than only through the UI, and independent confirmation beyond one mixed community report.
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “Custom objects get the same first-class treatment as built-in ones — including API endpoints, views, permissions, and workflow triggers.”
- [claimed-docs] “when you add a custom object (say Invoice), it immediately gets REST and GraphQL endpoints identical to built-in objects like Company or Per…”
- [claimed-docs] “Metadata API — /rest/metadata/ and /metadata/ Schema management: create/modify/delete objects, fields, and relations. This is how you progra…”
- [claimed-docs] “when you add a custom object (say `Invoice`), it immediately gets REST and GraphQL endpoints identical to built-in objects like `Company` or…”
- [claimed-docs] “API Import — Large-scale migrations, automation — Unlimited”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to TwentyAttio's REST API (attio-docs-2, attio-docs-4, attio-docs-6) lets a developer read/write and query workspace data, which could technically be used to script a full data export, but there is no documented native 'export all data' feature, no mention of open export formats (CSV/JSON dump), and no explicit portability/exit guarantee. Missing for 10: a documented bulk export/backup feature, explicit open-format export (CSV/JSON), and any statement about data portability upon leaving the platform.
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Run SQL queries against your workspace data.”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
Twenty explicitly documents export of workspace data for backups/migration with 'no lock-in', supports CSV/XLSX export/import, self-hosting via Docker, and open REST/GraphQL APIs for full data access, giving AI-native users a clear path to extract data in open formats and leave. Missing for 10: independent hands-on verification of export completeness/fidelity and no mention of export format limits beyond CSV (e.g., no JSON/SQL dump documented) or corroboration outside vendor docs.
- [claimed-docs] “Import data from CSV files or via API. Field mapping, duplicate detection, and error handling built in. Export your data anytime — no loc…”
- [claimed-docs] “Export your workspace data for backups, reporting, or migration. ... Export limits: Up to 20,000 records per export.”
- [claimed-docs] “Export your data anytime — no lock-in.”
- [claimed-docs] “You can import data for any object using CSV, XLSX, or XLS files. Each file should contain only one type of object (e.g., only People record…”
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “Run Twenty on your own infrastructure with a single Docker Compose command.”
- [claimed-docs] “Privacy-conscious organizations — you need to self-host and own your data end to end. Regulatory, contractual, or just principle.”
Pipeline management — stories about pipeline management in this arenaPipeline management
Stories about pipeline management in this arena
Ai crm ops
ai-native userHave an agent update deal stages and next steps from email and meeting signals via the API or MCP server
weight 3 · round to AttioAttio has a documented MCP server that lets AI tools search, update and manage workspace data (attio-probe-3, attio-docs-3, attio-docs-12), plus REST API with read/write access and webhooks for real-time signals (attio-docs-2, attio-docs-5), and deals/next-steps fields exist as standard objects (attio-docs-13, attio-docs-30). AI features mention drafting follow-ups and updating records, and call AI picks up buying signals (attio-docs-22, attio-docs-24), suggesting the pieces exist, but there's no concrete documentation of an agent workflow specifically ingesting email/meeting signals to update deal stage/next-steps fields end-to-end. Missing for 10: explicit documented workflow/recipe connecting email or meeting transcript signals to automated deal-stage/next-steps updates via API or MCP, and independent/hands-on confirmation of this specific automation working.
- [probe] “official MCP server documented at https://attio.com/mcp”
- [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
- [claimed-docs] “Search, update, and create with AI.”
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
- [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
- [claimed-docs] “An object to represent deals involving people & companies”
- [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
- [claimed-docs] “AI picks up buying signals, blockers, or requests during the call, not days later.”
Twenty documents the necessary building blocks — an MCP server (twenty-docs-32), REST/GraphQL API with full CRUD on custom fields like deal stage (twenty-docs-8, twenty-docs-22), automatic email/calendar linkage to CRM records (twenty-docs-4, twenty-docs-52, twenty-docs-58), and AI agents that 'execute multi-step tasks autonomously' including enriching records (twenty-docs-5, twenty-docs-56) plus workflow triggers on record changes (twenty-docs-3, twenty-docs-13). However, no evidence explicitly describes an agent reading email/meeting content and then updating deal stage or 'next steps' fields specifically — this exact pipeline-management workflow is not documented as a first-party example. Missing for 10: an explicit example/workflow showing an agent parsing email or meeting signals and writing deal-stage/next-steps updates via API or MCP, and any independent/hands-on confirmation this works end-to-end.
- [claimed-docs] “MCP server | Yes | Yes | Yes”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
- [claimed-docs] “Connect your Google Workspace or Microsoft 365 account. Emails and calendar events automatically appear on the relevant CRM records.”
- [claimed-docs] “Connect your **Google Workspace** or **Microsoft 365** mailbox. Once connected: Emails are automatically linked to the matching Company and …”
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [claimed-docs] “Trigger workflows on record changes, schedules, manual actions, or incoming webhooks.”
Deals
ops userRun multiple pipelines with different stage sets for different products or motions
weight 2 · round drawnAttio's docs describe lists as a mechanism to 'aggregate records and model business processes' distinct from objects, implying that multiple lists (each potentially with its own stage/status field) can serve as separate pipelines for different products or motions, and deals is an optional, configurable object. However, there is no explicit documentation confirming per-list custom stage sets or multiple concurrent pipelines with distinct stages for different motions. Missing for 10: explicit docs on creating multiple pipelines with independent stage sets, UI screenshots or guides showing per-list stage configuration, and any customer/hands-on evidence of running distinct pipelines for different products.
- [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
- [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
- [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
- [claimed-docs] “Create the exact data model your business needs with custom objects.”
Twenty's docs show building blocks that could support multiple pipelines — unlimited custom objects with custom fields (twenty-docs-1, twenty-docs-33), kanban/table/calendar views with grouping and saved views (twenty-docs-34), and workflow triggers per object (twenty-docs-12) — but there is no explicit documentation of a native 'multiple pipelines with distinct stage sets' feature (e.g. a dedicated Opportunities/Deals module supporting several independently configured pipelines). missing for 10: explicit docs describing a pipeline/deal-stage object with support for multiple named pipelines each having its own stage set, and confirmation this works out-of-the-box rather than via manual custom-object/kanban configuration.
- [claimed-docs] “Create custom objects, add custom fields with 20+ field types, and build relationships between any objects.”
- [claimed-docs] “You can also create custom objects for anything your business needs — projects, support tickets, products, contracts, or anything else.”
- [claimed-docs] “Switch between table views, kanban boards, and calendar views. Filter with AND/OR logic, sort by multiple fields, group records, and save cu…”
- [claimed-docs] “Custom objects get the same first-class treatment as built-in ones — including API endpoints, views, permissions, and workflow triggers.”
founderTrack deals on a visual pipeline with customizable stages and drag-and-drop updates
weight 3 · round to AttioAttio ships a native Deal object for pipeline tracking (attio-docs-13,30,33), supports kanban board views alongside tables (attio-docs-34), and lets users customize fields/stages via custom objects and lists that model business processes (attio-docs-8,29,46). This directly matches the pipeline-with-customizable-stages story, though evidence never explicitly names 'drag-and-drop' interaction or shows independent hands-on confirmation. Missing for 10: explicit drag-and-drop UI documentation, independent/third-party hands-on review confirming the kanban interaction works as described.
- [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
- [claimed-docs] “An object to represent deals involving people & companies”
- [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin”
- [claimed-docs] “From kanbans to tables, visualize your data the way that works for you.”
- [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
- [claimed-docs] “Customize fields to capture exactly what you need to track.”
- [claimed-docs] “Create the exact data model your business needs with custom objects.”
Docs confirm kanban board views alongside table/calendar views, customizable fields/objects for building deal stages, and workflows that can trigger on stage changes (e.g., Slack alert when 'a deal reaches a certain stage'), which together support a visual pipeline with configurable stages. However, no evidence explicitly confirms drag-and-drop interaction on the kanban board itself, and community feedback flags the product as 'pretty alpha-version' with unspecified issues. Missing for 10: explicit documentation/screenshot of drag-and-drop card movement between stages, and independent hands-on confirmation that pipeline stage customization works smoothly in practice.
- [claimed-docs] “Switch between table views, kanban boards, and calendar views.”
- [claimed-docs] “Switch between table views, kanban boards, and calendar views. Filter with AND/OR logic, sort by multiple fields, group records, and save cu…”
- [claimed-docs] “Send Slack alerts when a deal reaches a certain stage * Auto-enrich new contacts with data from external APIs”
- [claimed-docs] “Workflows can chain any combination of: Record operations... Send email... HTTP request... Code... Branches... Iterator... AI Agent... Delay…”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
Forecasting
founderForecast revenue from pipeline value, stage probabilities, and close dates
weight 2 · round to TwentyAttio's Deal object provides pipeline data (stage, value, close date) and its reporting engine supports custom visualizations/analytics, which could underpin revenue forecasting, but no evidence explicitly documents a forecasting feature, stage-probability weighting, or a forecast report type. Missing for 10: explicit probability-weighted forecast feature, documented forecast reports/dashboards, and any customer/independent evidence of forecasting use.
- [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
- [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
- [claimed-docs] “An object to represent deals involving people & companies”
- [claimed-docs] “Attio's powerful engine allows you to find whichever insights you're looking for.”
- [claimed-docs] “Analyze live data any way you like, from line charts and bar graphs to geospatial mapping.”
- [claimed-docs] “Combine visualizations to instantly understand the full story and make better business decisions.”
Twenty provides the building blocks—custom fields for deal value/stage/close date, dashboards with configurable charts, filters, aggregation, and grouping, and docs explicitly mention tracking 'pipeline health, team performance, revenue trends'—but there is no dedicated forecasting feature that models stage-probability-weighted revenue projections; a founder would need to manually configure fields and dashboard aggregations to approximate this. Missing for 10: a native weighted-pipeline forecast report, explicit stage-probability calculation logic, and any hands-on evidence of this being used for revenue forecasting.
- [claimed-docs] “Build custom dashboards with real-time widgets. Track pipeline metrics, team performance, and business KPIs with configurable charts and …”
- [claimed-docs] “You can configure: Chart type... Data source... Filters... Aggregation... Grouping”
- [claimed-docs] “Dashboards give you real-time visibility into your business metrics — pipeline health, team performance, revenue trends”
- [claimed-docs] “Create custom objects, add custom fields with 20+ field types, and build relationships between any objects.”
- [claimed-docs] “Build custom dashboards with real-time widgets.”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to TwentyAttionone0/10No evidence in the pack mentions data residency, region selection, or storage location choices for Attio workspaces; the evidence pack covers API, objects, workflows, AI features, and MCP but nothing on data residency controls.
Twenty doesn't offer an explicit region-selection setting, but self-hosting via Docker Compose lets privacy-conscious users run the entire stack on their own infrastructure, effectively letting them choose where data lives. This is an indirect residency control rather than a built-in region picker for the cloud offering. Missing for 10: explicit cloud data-residency/region selection UI, documented data center regions, compliance certifications (GDPR/SOC2) tied to specific regions.
- [claimed-docs] “Run Twenty on your own infrastructure with a single Docker Compose command.”
- [claimed-docs] “Privacy-conscious organizations — you need to self-host and own your data end to end. Regulatory, contractual, or just principle.”
- [claimed-docs] “**Privacy-conscious organizations** — you need to self-host and own your data end to end.”
- [claimed-docs] “This guide provides step-by-step instructions to install and configure the Twenty application using Docker Compose.”
ai-native userPrevent my data from being used to train AI models
weight 3 · round to TwentyAttionone0/10No evidence in the pack addresses AI-training data usage, opt-out controls, or any privacy policy statement about model training on customer data; this is an applicable privacy-posture axis for an AI-native CRM but no supporting documentation exists in the evidence pack.
Twenty offers self-hosting so an organization can keep full control of its data ('own your data end to end'), which indirectly prevents third-party AI training on it, and permission-scoped AI agent access limits what data agents can see. However, there is no explicit statement, opt-out setting, or policy about excluding user data from AI model training on the cloud/hosted offering. missing for 10: explicit no-training data policy, cloud-hosted opt-out toggle, independent confirmation of data-handling practices for AI features.
- [claimed-docs] “Privacy-conscious organizations — you need to self-host and own your data end to end. Regulatory, contractual, or just principle.”
- [claimed-docs] “**Privacy-conscious organizations** — you need to self-host and own your data end to end.”
- [claimed-docs] “Agents can only access objects and fields that the user (or role) has permission to view. Sensitive data stays protected even when AI is inv…”
- [claimed-docs] “Run Twenty on your own infrastructure with a single Docker Compose command.”
ai-native userControl data retention and deletion
weight 2 · round to TwentyAttionone0/10No evidence pack items address data retention policies, export/deletion controls, or privacy/compliance settings for AI-native data handling; all citations concern API features, CRM data modeling, and workflow automation, not retention/deletion controls.
Twenty offers data export ('Export your data anytime — no lock-in', up to 20,000 records/export) and self-hosting for full data ownership, which gives some control over data, but there is no explicit documentation of retention policies or deletion controls (e.g., record purge, right-to-be-forgotten, TTL settings) tailored to AI-native use. Missing for 10: explicit data retention policy settings, record/field deletion controls, GDPR-style erasure workflow, and any AI-specific retention/deletion controls.
- [claimed-docs] “Export your data anytime — no lock-in.”
- [claimed-docs] “Export your workspace data for backups, reporting, or migration. ... Export limits: Up to 20,000 records per export.”
- [claimed-docs] “Privacy-conscious organizations — you need to self-host and own your data end to end. Regulatory, contractual, or just principle.”
- [claimed-docs] “**Privacy-conscious organizations** — you need to self-host and own your data end to end.”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnAttionone0/10No evidence pack items mention telemetry, usage tracking, opt-out settings, or privacy controls of this kind; this is an applicable axis for a SaaS CRM platform but nothing documents it.
Reporting insights — stories about reporting insights in this arenaReporting insights
Stories about reporting insights in this arena
Ai crm ops
ai-native userHave an agent compile an account brief — open deals, recent emails, and history — from CRM data via the API or MCP server before a meeting
weight 2 · round to AttioAttio has an official MCP server (attio-docs-3, attio-probe-3) and a REST API supporting filtering/sorting, deal/company/history objects (attio-docs-1,2,6,29,30,16) that would let an agent pull open deals, history, and records; the AI platform page explicitly names 'create account briefs' as a capability (attio-docs-22) alongside call transcription/logging that could feed 'recent emails/interactions' context. Missing for 10: independent/hands-on confirmation that the MCP server actually returns email history or that account-brief generation works end-to-end in practice, and explicit documentation of email data access via the API.
- [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
- [probe] “official MCP server documented at https://attio.com/mcp”
- [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
- [claimed-docs] “Get instant visibility into the full history of every interaction.”
- [claimed-docs] “An object to represent deals involving people & companies”
- [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
- [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
Twenty provides the necessary building blocks — GraphQL/REST APIs and a documented MCP server (twenty-docs-32) for programmatic access, automatic linking of emails/calendar events to Company/Person records (twenty-docs-4, twenty-docs-52, twenty-docs-58), and AI agents that can answer questions, enrich records, and execute multi-step tasks within permissions (twenty-docs-5, twenty-docs-18, twenty-docs-56) — which together could let an agent assemble open deals, emails, and history into a brief. However, there is no concrete documentation of an actual 'account brief' workflow, no example of the MCP server's specific tools/resources for querying deals+emails+history in one call, and no hands-on evidence this composite use case has been built or tested. Missing for 10: a documented end-to-end example or MCP tool spec for compiling a pre-meeting brief, and independent/hands-on confirmation of the AI agent successfully synthesizing deals+emails+history.
- [claimed-docs] “MCP server | Yes | Yes | Yes”
- [claimed-docs] “AI agents that work autonomously within your CRM — answering questions, enriching records, and executing multi-step tasks within your permis…”
- [claimed-docs] “Ask questions about your data in natural language. The AI chatbot can query your CRM records, summarize information, and help you find what …”
- [claimed-docs] “AI agents go beyond chat — they can execute multi-step tasks autonomously: Enrich records with data from external sources”
- [claimed-docs] “Connect your Google Workspace or Microsoft 365 account. Emails and calendar events automatically appear on the relevant CRM records.”
- [claimed-docs] “Connect your **Google Workspace** or **Microsoft 365** mailbox. Once connected: Emails are automatically linked to the matching Company and …”
- [claimed-docs] “Emails are automatically linked to the matching Company and People records”
- [claimed-docs] “A developer-first API that adapts to your custom data model. Both GraphQL and REST endpoints, with auto-generated documentation per works…”
Reporting
founderBuild reports and dashboards on pipeline, activity, and conversion without exporting to a spreadsheet
weight 3 · round to TwentyAttio's native reporting platform lets users build live dashboards with multiple chart types (line, bar, geospatial) and combine visualizations for team collaboration, plus SQL query access for deeper analysis—directly enabling in-app reporting instead of spreadsheet exports. Missing for 10: no explicit pipeline/conversion-metric examples, no independent/hands-on corroboration of dashboard-building in practice.
- [claimed-docs] “Attio's powerful engine allows you to find whichever insights you're looking for.”
- [claimed-docs] “Analyze live data any way you like, from line charts and bar graphs to geospatial mapping.”
- [claimed-docs] “Combine visualizations to instantly understand the full story and make better business decisions.”
- [claimed-docs] “Work with your teammates to build th”
- [claimed-docs] “Run SQL queries against your workspace data.”
Twenty provides native custom dashboards with configurable chart types, filters, aggregation, and grouping over pipeline/activity data, with real-time widgets for pipeline health, team performance, and revenue trends — all built in-app without needing spreadsheet exports (twenty-docs-6, twenty-docs-20, twenty-docs-21, twenty-docs-57, twenty-docs-48). Data export is offered only as an optional side capability, not a requirement for reporting. Missing for 10: independent/hands-on validation of dashboard depth and reporting accuracy (only vendor docs cited, and community evidence [twenty-comm-1] notes general 'alpha-version' rough edges without specifically addressing dashboards).
- [claimed-docs] “Build custom dashboards with real-time widgets. Track pipeline metrics, team performance, and business KPIs with configurable charts and …”
- [claimed-docs] “You can configure: Chart type... Data source... Filters... Aggregation... Grouping”
- [claimed-docs] “Dashboards are workspace-level — everyone on your team can see them. Arrange widgets in a grid layout and resize them.”
- [claimed-docs] “Dashboards give you real-time visibility into your business metrics — pipeline health, team performance, revenue trends”
- [claimed-docs] “Arrange widgets in a grid layout and resize them to build the view that works for your team.”
- [claimed-docs] “Build custom dashboards with real-time widgets.”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”
Not comparable on these axes
ai-native userRead the product's source under an open license
weight 2 · not comparableAttion/aAttio is a closed-source SaaS CRM product; there is no evidence of any open-licensed source code release, and this is not a category where source availability is a typical offering. This is a wrong-axis question for a proprietary SaaS platform.
Twenty's source is hosted publicly on GitHub (twentyhq/twenty) and documented as usable with standard React/TypeScript stack ('no proprietary languages, no gatekeeping'), and community discussion explicitly confirms the project is licensed AGPLv3, an OSI-approved open license. This directly satisfies an AI-native user's ability to read the source under an open license, with self-host instructions reinforcing full source availability. Missing for 10: no direct citation of the LICENSE file text itself and no confirmation whether any enterprise-only modules are closed-source, so full completeness of the open-source surface isn't independently verified.
- [github] “Scaffold a new app with the Twenty CLI: npx create-twenty-app my-app ... Define objects, fields, and views as code”
- [github] “npx twenty app:publish --private”
- [community] “Massive difference exist between GPLv2 (Git) vs AGPLv3 (Twenty). You're comparing apples and oranges. Google documents well why they forbid …”
- [claimed-docs] “React, TypeScript. Your team already knows how to extend Twenty. No proprietary languages, no gatekeeping.”
- [claimed-docs] “Run Twenty on your own infrastructure with a single Docker Compose command.”
ai-native userSelf-host the core product
weight 3 · not comparableAttion/aAttio is a SaaS CRM offered only as a hosted cloud product; there is no evidence of any self-hosted or on-premise deployment option, and self-hosting is not a plausible axis for this product category as evidenced.
Twenty provides clear first-party self-hosting docs, a single Docker Compose install command, and even an install script, with docs explicitly framing self-hosting as a use case for privacy-conscious organizations wanting to own their data end to end; community evidence corroborates it as easy to set up. Missing for 10: independent hands-on verification of the full self-hosted core feature set (AI, workflows) at parity with cloud beyond initial setup reports.
- [claimed-docs] “Run Twenty on your own infrastructure with a single Docker Compose command.”
- [claimed-docs] “Install the latest stable version of Twenty with a single command: bash <(curl -sL https://raw.githubusercontent.com/twentyhq/twenty/main/pa…”
- [claimed-docs] “This guide provides step-by-step instructions to install and configure the Twenty application using Docker Compose.”
- [claimed-docs] “Privacy-conscious organizations — you need to self-host and own your data end to end. Regulatory, contractual, or just principle.”
- [claimed-docs] “**Privacy-conscious organizations** — you need to self-host and own your data end to end.”
- [community] “Twenty was almost what we needed. It was extremely easy to set up, the customization is very promising, and the REST API worked ok. The main…”