Salesforce Sales Cloud vs Twenty

Agent access

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud✓fullprobed8/10

   Direct probe evidence confirms an llms.txt file exists at https://www.salesforce.com/llms.txt returning HTTP 200 with structured agent-oriented content links, and this is corroborated by an official MCP server and CLI ecosystem that agents can also use. Missing for 10: independent third-party confirmation that agents actively consume this llms.txt successfully, and more comprehensive agent-oriented documentation beyond the single probed file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.salesforce.com/llms.txt - [AI Agent Course: Free Online Training](https://www.salesforce.com/agentfo…”
   • [probe] “official MCP server documented at https://github.com/salesforcecli/mcp”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”

   proof ↗⚑ flag

   Twenty✓fullprobed9/10

   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:/…”

   proof ↗⚑ flag

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

   weight 2 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud~partialprobed7/10

   Salesforce ships an official CLI (sf/@salesforce/cli) with headless-friendly commands like `sf data query`, `sf apex run test`, `sf org create scratch`, and even `sf agent create/activate`, which are the standard mechanism developers use to script and automate Salesforce orgs in CI pipelines. However, the evidence is CLI/platform-level rather than Sales Cloud-specific, and there's no explicit CI/CD pipeline example, GitHub Actions integration doc, or independent hands-on CI report cited. Missing for 10: explicit CI/CD pipeline integration guide or example, independent verification of headless automation in a real CI environment, Sales-Cloud-specific (not just generic platform) automation documentation.

   • [github] “sf org create scratch”
   • [github] “npm install -g @salesforce/cli”
   • [github] “[`sf data query`](#sf-data-query)”
   • [github] “sf apex run test”
   • [github] “sf agent create”
   • [github] “sf agent activate”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”

   proof ↗⚑ flag

   Twenty~partialclaimed4/10

   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…”

   proof ↗⚑ flag

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

   weight 3 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud✓fullclaimed7/10

   Salesforce's Agentforce Builder explicitly lets users find, evaluate, and plug in trusted third-party agents, sub-agents, and MCP servers via AgentExchange, directly enabling agents to use external MCP tools, and Agent Builder also connects to Flows, Apex, MuleSoft APIs, etc. This is first-party documentation without independent hands-on corroboration of the MCP plug-in flow. Missing for 10: independent/community verification of actually connecting an MCP server in Agentforce Builder, and more detail on configuration/setup steps.

   • [claimed-docs] “you can find, evaluate, and plug in trusted third-party agents, sub-agents, and MCP servers directly within Agentforce Builder”
   • [claimed-docs] “Connect to your data, channels, and existing Salesforce assets like Flows, Apex, MuleSoft APIs, and prompt templates.”
   • [claimed-docs] “Access to AgentExchange”

   proof ↗⚑ flag

   Twenty—none0/10

   The 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”

   proof ↗⚑ flag

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

   weight 3 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud✓fullprobed7/10

   Salesforce publishes an official MCP server (salesforce-probe-3: github.com/salesforcecli/mcp) alongside its CLI, and Agentforce Builder documentation explicitly supports plugging in third-party and platform MCP servers (salesforce-docs-28), confirming the platform embraces the MCP standard for agent connectivity. Missing for 10: detailed first-party setup/usage docs for the MCP server itself, and independent/hands-on validation of its functionality beyond the repo's existence.

   • [probe] “official MCP server documented at https://github.com/salesforcecli/mcp”
   • [claimed-docs] “you can find, evaluate, and plug in trusted third-party agents, sub-agents, and MCP servers directly within Agentforce Builder”
   • [github] “Read the sf Plugin Developer Guide to learn how to develop a sf plugin.”

   proof ↗⚑ flag

   Twenty✓fullclaimed5/10

   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”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud✓fullprobed8/10

   Salesforce ships an official, actively documented CLI (@salesforce/cli / sf) with commands for org management, data queries, Apex tests, and even agent creation/activation, corroborated by GitHub docs and independent community praise for its command-line tooling. Missing for 10: deeper AI-native agent workflow examples in the CLI itself and more independent hands-on reviews specifically of newer 'sf agent' subcommands.

   • [github] “sf org create scratch”
   • [github] “npm install -g @salesforce/cli”
   • [github] “[`sf data query`](#sf-data-query)”
   • [github] “[`sf org create scratch`](#sf-org-create-scratch)”
   • [github] “Read the sf Plugin Developer Guide to learn how to develop a sf plugin.”
   • [github] “sf apex run test”
   • [github] “sf agent create”
   • [github] “sf agent activate”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”
   • [community] “"With SFDC I get a passable command line tool, multiple VS Code extensions, an easy deployment path, local development with Lightning Web Co…”

   proof ↗⚑ flag

   Twenty✓fullclaimed7/10

   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”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Salesforce Sales Cloud✓fullprobed8/10

   Salesforce documents extensive public APIs (REST/SOAP/Apex/Bulk via Platform APIs), a robust official CLI (sf commands for data query, org management, agent creation, apex tests) and even an official MCP server, all confirmed via GitHub tooling and probes, giving AI-native users multiple documented ways to drive the product programmatically. Missing for 10: a discoverable OpenAPI/swagger spec (probe found only 404s) and independent hands-on validation of the public REST API itself beyond CLI tooling.

   • [claimed-docs] “Discover Salesforce APIs & put them to work.”
   • [github] “sf org create scratch”
   • [github] “npm install -g @salesforce/cli”
   • [github] “[`sf data query`](#sf-data-query)”
   • [github] “[`sf org create scratch`](#sf-org-create-scratch)”
   • [github] “sf apex run test”
   • [github] “sf agent create”
   • [probe] “official MCP server documented at https://github.com/salesforcecli/mcp”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”
   • [community] “"With SFDC I get a passable command line tool, multiple VS Code extensions, an easy deployment path, local development with Lightning Web Co…”

   proof ↗⚑ flag

   Twenty✓fullprobed8/10

   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/…”

   proof ↗⚑ flag

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud~partialclaimed4/10

   Salesforce documents attribute-based access control (ABAC) policies that admins can enforce to control what data agents (not just humans) can see, which speaks to least-privilege access for agents, but there is no explicit mention of scoped/least-privilege API credentials, tokens, or connected-app OAuth scopes issued specifically to an agent. Missing for 10: explicit API credential/token scoping mechanism for agents, OAuth scope documentation, and any independent/hands-on confirmation of least-privilege enforcement in practice.

   • [claimed-docs] “Admins can control who sees what data and when, from humans to AI agents, by enforcing custom attribute-based (ABAC) access policies.”

   proof ↗⚑ flag

   Twenty✓fullclaimed7/10

   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…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud✓fullprobed8/10

   Salesforce offers robust official SDK/CLI tooling (salesforcecli/cli with sf commands for org, data, apex, agent management), a dedicated plugin developer guide, and platform APIs for building apps/agents, corroborated by independent developer testimony praising the CLI, VS Code extensions, and local dev tools. missing for 10: no direct evidence of a language-specific SDK (e.g., Node/Java/Python client libraries) beyond the CLI, and no independent hands-on review of SDK completeness for AI-native workflows specifically.

   • [github] “sf org create scratch”
   • [github] “npm install -g @salesforce/cli”
   • [github] “[`sf data query`](#sf-data-query)”
   • [github] “Read the sf Plugin Developer Guide to learn how to develop a sf plugin.”
   • [github] “sf apex run test”
   • [github] “sf agent create”
   • [claimed-docs] “Discover Salesforce APIs & put them to work.”
   • [community] “"With SFDC I get a passable command line tool, multiple VS Code extensions, an easy deployment path, local development with Lightning Web Co…”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”

   proof ↗⚑ flag

   Twenty~partialprobed6/10

   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/…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   The evidence pack contains no mention of webhooks, Platform Events, Streaming API, or any push-notification subscription mechanism for Salesforce Sales Cloud; only CLI, MCP server, and marketing content are documented. missing for 10: webhook subscription API/docs, event notification setup guide, any first-party or community confirmation of webhook support.

   ⚑ flag

   Twenty~partialclaimed5/10

   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).”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Salesforce Sales Cloud✓fullclaimed8/10

   Sales Cloud ships built-in AI features like lead scoring, predictive forecasting, and AI-powered pipeline insights directly in the CRM UI, backed by named customer results (e.g., Crexi saving 5 hours/day with Sales AI). Missing for 10: independent hands-on review specifically validating insight quality/accuracy, and more detail on how insights surface in-product beyond marketing copy.

   • [claimed-docs] “Equip reps with real-time data and AI-powered insights so they can cut through the noise, deliver better buying experiences, and close more …”
   • [claimed-docs] “Get complete visibility into your pipeline. Surface insights to speed up prospecting and opportunity management.”
   • [claimed-docs] “Dashboard view of Sales Cloud with an overlay to zoom in on AI-generated lead scoring within a CRM view.”
   • [claimed-docs] “Predictive Forecasting”
   • [claimed-docs] “Lead Scoring”
   • [claimed-docs] “Crexi saves its sales reps 5 hours a day with Sales AI.”

   proof ↗⚑ flag

   Twenty✓fullclaimed8/10

   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”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Salesforce Sales Cloud✓fullclaimed7/10

   Salesforce documents Agentforce agents that run 24/7 autonomously across the sales cycle (prospecting to close), with CLI tooling (sf agent create, sf agent activate) and Agent Builder for configuring automated logic, access controls, and integrations with Flows/Apex/MuleSoft. This directly matches background autonomous automation for an AI-native user. missing for 10: independent/hands-on verification that agents genuinely run unattended in production, and more detail on monitoring/error-handling for autonomous runs

   • [claimed-docs] “Deploy AI agents 24/7 to autonomously handle repetitive tasks, expand your pipeline, and boost revenue without adding headcount.”
   • [claimed-docs] “Turn on agents across every stage of the deal cycle — from prospecting to close.”
   • [claimed-docs] “Qualifying inbound lead | Updating opportunity | Closing renewal deal”
   • [github] “sf agent create”
   • [github] “sf agent activate”
   • [claimed-docs] “Connect to your data, channels, and existing Salesforce assets like Flows, Apex, MuleSoft APIs, and prompt templates.”
   • [claimed-docs] “Use natural language and Agent Optimizer to get started quickly, then apply advanced logic and controls to deliver agents you can trust in p…”
   • [claimed-docs] “Admins can control who sees what data and when, from humans to AI agents, by enforcing custom attribute-based (ABAC) access policies.”

   proof ↗⚑ flag

   Twenty✓fullclaimed7/10

   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).”

   proof ↗⚑ flag

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

   weight 3 · round to Twenty
   Salesforce Sales Cloud✓fullclaimed7/10

   Sales Cloud embeds Agentforce agents directly in the CRM to autonomously handle tasks like qualifying leads, updating opportunities, and closing renewals, with natural-language agent building and 24/7 deployment described in first-party docs. Missing for 10: independent/hands-on verification of the assistant's task delegation working reliably in practice, and more detail on the interactive 'delegate a task' UX rather than marketing case studies.

   • [claimed-docs] “Deploy AI agents 24/7 to autonomously handle repetitive tasks, expand your pipeline, and boost revenue without adding headcount.”
   • [claimed-docs] “Turn on agents across every stage of the deal cycle — from prospecting to close.”
   • [claimed-docs] “Qualifying inbound lead | Updating opportunity | Closing renewal deal”
   • [claimed-docs] “Connect to your data, channels, and existing Salesforce assets like Flows, Apex, MuleSoft APIs, and prompt templates.”
   • [claimed-docs] “Use natural language and Agent Optimizer to get started quickly, then apply advanced logic and controls to deliver agents you can trust in p…”

   proof ↗⚑ flag

   Twenty✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud~partialclaimed6/10

   Salesforce documents natural-language agent building ("Use natural language and Agent Optimizer to get started quickly" — salesforce-docs-30) and Agentforce agents executing sales tasks like qualifying leads and closing deals via natural-language-driven automation (salesforce-docs-21, salesforce-docs-31), which supports agentic natural-language operation within Sales Cloud's Agentforce layer. However, this is mostly about configuring/building agents rather than a general natural-language command interface for day-to-day CRM operation by end users, and there's no hands-on/independent confirmation of reliability. Missing for 10: independent verification of natural-language command execution in daily use, clear evidence of a conversational interface for core CRM tasks beyond agent-builder configuration.

   • [claimed-docs] “Use natural language and Agent Optimizer to get started quickly, then apply advanced logic and controls to deliver agents you can trust in p…”
   • [claimed-docs] “Turn on agents across every stage of the deal cycle — from prospecting to close.”
   • [claimed-docs] “Qualifying inbound lead | Updating opportunity | Closing renewal deal”
   • [claimed-docs] “Deploy AI agents 24/7 to autonomously handle repetitive tasks, expand your pipeline, and boost revenue without adding headcount.”
   • [claimed-docs] “Connect to your data, channels, and existing Salesforce assets like Flows, Apex, MuleSoft APIs, and prompt templates.”

   proof ↗⚑ flag

   Twenty✓fullclaimed7/10

   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…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   There is no evidence of an interactive API reference with runnable examples; the openapi probe returned 404s and no docs mention a try-it-console or embedded runnable examples for the API. Only marketing mentions of 'Discover Salesforce APIs' and CLI tooling exist, which is not an interactive reference experience.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.salesforce.com/openapi.json, https://www.salesforce.com/swagger.json, https://www.salesf…”
   • [claimed-docs] “Discover Salesforce APIs & put them to work.”

   proof ↗⚑ flag

   Twenty~partialprobed3/10

   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/…”

   proof ↗⚑ flag

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   The evidence pack includes an explicit probe showing all standard OpenAPI spec paths (openapi.json, swagger.json, etc.) return 404, and no docs item describes a downloadable machine-readable API spec — only vague marketing copy about 'Discover Salesforce APIs.' No concrete OpenAPI/Swagger artifact is shown to exist.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.salesforce.com/openapi.json, https://www.salesforce.com/swagger.json, https://www.salesf…”
   • [claimed-docs] “Discover Salesforce APIs & put them to work.”

   proof ↗⚑ flag

   Twenty~partialprobed5/10

   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/…”

   proof ↗⚑ flag

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

   weight 1 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud~partialclaimed6/10

   The Salesforce CLI supports scratch org creation (`sf org create scratch`) which spins up isolated dev/test environments separate from production, and includes test/query tooling (`sf apex run test`, `sf data query`) that could be run against such sandboxes. However, no evidence explicitly ties this to an AI-native/agentic workflow or documents a dedicated 'sandbox for AI testing' story beyond generic dev tooling. Missing for 10: explicit documentation of AI-agent-specific sandbox testing workflows, integration between scratch orgs and Agentforce/AI agent testing, and independent corroboration of this specific use case.

   • [github] “sf org create scratch”
   • [github] “[`sf org create scratch`](#sf-org-create-scratch)”
   • [github] “`sf org create scratch`”
   • [github] “sf apex run test”
   • [github] “[`sf data query`](#sf-data-query)”

   proof ↗⚑ flag

   Twenty—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Salesforce Sales Cloud—none0/10

   No evidence in the pack references API versioning, version deprecation timelines, or a documented deprecation policy for Salesforce APIs; the pack only shows CLI/MCP tooling and marketing content. missing for 10: documentation of API version numbering, deprecation schedule/policy, and any changelog or support-lifecycle references.

   ⚑ flag

   Twenty—none0/10

   Evidence 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/…”

   proof ↗⚑ flag

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   The evidence pack shows CLI/query commands (sf data query, sf org create scratch) and general AI/automation marketing claims, but nothing documents bulk create/update/delete operations across many records for an AI-native workflow. Missing for 10: explicit bulk API or bulk data manipulation documentation, evidence of batch processing at scale, or AI-agent-triggered bulk operations.

   • [github] “[`sf data query`](#sf-data-query)”
   • [github] “sf org create scratch”
   • [claimed-docs] “Discover Salesforce APIs & put them to work.”

   proof ↗⚑ flag

   Twenty✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

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

   weight 3 · round to Twenty
   Salesforce Sales Cloud~partialclaimed6/10

   Salesforce documents rule-based automation constructs (Built-in Sales Flows and Lead Routing, Agentforce agents triggered across deal-cycle stages, Agent Script Recipes) and CLI/agent tooling (sf agent create/activate) that support event-driven automation, but the evidence is largely marketing copy rather than technical documentation of a rules engine or trigger/condition/action framework a developer could inspect. Missing for 10: concrete docs on defining trigger conditions (e.g., Flow Builder trigger types, Apex triggers) with independent/hands-on verification that automations reliably fire on events, and no community corroboration of automation reliability.

   • [claimed-docs] “Built-in Sales Flows and Lead Routing”
   • [claimed-docs] “Turn on agents across every stage of the deal cycle — from prospecting to close.”
   • [claimed-docs] “Deploy AI agents 24/7 to autonomously handle repetitive tasks, expand your pipeline, and boost revenue without adding headcount.”
   • [claimed-docs] “Build enterprise agents with Agentforce using Agent Script Recipes”
   • [github] “sf agent create”
   • [github] “sf agent activate”
   • [claimed-docs] “Qualifying inbound lead | Updating opportunity | Closing renewal deal”

   proof ↗⚑ flag

   Twenty✓fullclaimed8/10

   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”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Twenty
   Salesforce Sales Cloud~partialclaimed4/10

   Sales Cloud advertises built-in Sales Flows, automation of the sales cycle, and 24/7 autonomous agents (salesforce-docs-27, salesforce-docs-11, salesforce-docs-18), implying some workflow/automation scheduling capability, but there is no explicit documentation of an AI-native interface (API/CLI) for creating or managing recurring scheduled jobs — the CLI evidence only shows org/test/agent commands, not job scheduling. missing for 10: explicit docs on scheduled/recurring Flow or batch job creation via API/CLI, AI-native scheduling interface, and independent confirmation of recurring automation working as claimed.

   • [claimed-docs] “Built-in Sales Flows and Lead Routing”
   • [claimed-docs] “Automate, optimize, and unify your sales cycle from pipeline to paycheck—improving visibility and reducing operational costs.”
   • [claimed-docs] “Deploy AI agents 24/7 to autonomously handle repetitive tasks, expand your pipeline, and boost revenue without adding headcount.”
   • [github] “`sf org create scratch`”
   • [github] “sf apex run test”

   proof ↗⚑ flag

   Twenty✓fullclaimed7/10

   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).”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Salesforce Sales Cloud—none0/10

   No evidence describes versioning, review workflows, or rollback specifically for automations/agents (e.g., Flow version history, agent build rollback); only DevOps Center is mentioned generically without detail on versioning/rollback mechanics.

   ⚑ flag

   Twenty—none0/10

   The 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”

   proof ↗⚑ flag

Workflows

1. ops userRoute new leads to the right owner automatically with assignment rules or round-robin

   weight 2 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud~partialclaimed5/10

   Pricing page explicitly lists 'Built-in Sales Flows and Lead Routing' and lead scoring/management features, indicating assignment/routing capability exists, but no evidence details round-robin logic, configuration specifics, or independent confirmation it works as expected. Missing for 10: documentation of round-robin assignment mechanics, admin setup guide, and hands-on/independent verification of lead routing behavior.

   • [claimed-docs] “Built-in Sales Flows and Lead Routing”
   • [claimed-docs] “Lead, Account, Contact, and Opportunity Management”
   • [claimed-docs] “Lead Scoring”

   proof ↗⚑ flag

   Twenty—none0/10

   Twenty'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”

   proof ↗⚑ flag

2. ops userBuild trigger-based workflows that update records, create tasks, and send notifications automatically

   weight 3 · round to Twenty
   Salesforce Sales Cloud~partialcommunity5/10

   Salesforce Sales Cloud includes Flow/automation ('Built-in Sales Flows and Lead Routing') and community evidence confirms trigger-based automation like timed emails is easy to build, supporting record updates, tasks, and notifications. However, the evidence pack lacks first-party documentation specifically detailing trigger-based workflow builders (e.g., Flow Builder, Process Builder) with concrete examples of update/create/notify actions chained together. missing for 10: detailed first-party docs on Flow Builder/trigger automation mechanics, independent hands-on verification of multi-action workflows (update+task+notification) working end-to-end.

   • [claimed-docs] “Built-in Sales Flows and Lead Routing”
   • [community] “"D365 documentation is utter garbage when compared to the SFDC Trailhead... I spent many hours trying to figure out how to send timed emails…”
   • [claimed-docs] “Automate, optimize, and unify your sales cycle from pipeline to paycheck—improving visibility and reducing operational costs.”

   proof ↗⚑ flag

   Twenty✓fullcommunity8/10

   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…”

   proof ↗⚑ flag

Ai crm ops

1. 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 to Twenty
   Salesforce Sales Cloud~partialprobed4/10

   Salesforce exposes a documented Data API/CLI (sf data query, sf agent create) and an official MCP server (salesforce-probe-3), and the CRM data model explicitly includes Lead/Account/Contact/Opportunity objects (salesforce-docs-22), which together make an end-to-end lead-enrichment workflow plausible. However, there is no concrete documentation or example showing an agent actually creating a lead, filling company data, and assigning an owner via the API or MCP server in one flow. Missing for 10: a worked example or docs of the specific lead-create+enrich+assign-owner workflow via API/MCP, and any hands-on/independent confirmation it works end-to-end.

   • [probe] “official MCP server documented at https://github.com/salesforcecli/mcp”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”
   • [claimed-docs] “Lead, Account, Contact, and Opportunity Management”
   • [github] “[`sf data query`](#sf-data-query)”
   • [github] “sf agent create”

   proof ↗⚑ flag

   Twenty~partialclaimed6/10

   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…”

   proof ↗⚑ flag

Data quality

1. ops userHave contact and company records auto-enriched with firmographic and contact data

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   Evidence covers lead scoring, forecasting, pipeline management, and CRM sync, but no citation mentions auto-enrichment of contact/company records with third-party firmographic or contact data. Missing for 10: any documented data-enrichment feature/integration, evidence of firmographic data append, or contact/company auto-fill from external sources.

   ⚑ flag

   Twenty~partialclaimed5/10

   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…”

   proof ↗⚑ flag

2. ops userDetect duplicate contacts or companies and merge them without losing data

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   The evidence pack contains no mention of duplicate detection, deduplication rules, or merge tools for contacts/accounts (e.g., no reference to Salesforce's native 'Merge Duplicates' or matching/duplicate rule features). Only generic lead/contact/account management mentions (salesforce-docs-22) appear, with no specifics on dedup or merge workflows.

   • [claimed-docs] “Lead, Account, Contact, and Opportunity Management”

   proof ↗⚑ flag

   Twenty~partialclaimed4/10

   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”

   proof ↗⚑ flag

Record management

1. ops userManage contacts and companies as linked records with a full activity timeline on each

   weight 3 · round to Twenty
   Salesforce Sales Cloud~partialclaimed5/10

   Salesforce Sales Cloud explicitly lists 'Lead, Account, Contact, and Opportunity Management' as a core capability, implying linked contact/company records, but the evidence pack contains no direct documentation of an activity timeline feature on records or details on how records are linked. missing for 10: explicit documentation/screenshots of activity timeline on contact/account records, independent hands-on confirmation of the linked-record UI.

   • [claimed-docs] “Lead, Account, Contact, and Opportunity Management”
   • [claimed-docs] “Accelerate sales, connect with buyers, and take action with engagement built directly into your CRM.”
   • [claimed-docs] “Sales Cloud gives every seller the context they need to move deals forward — and handles the work in between.”

   proof ↗⚑ flag

   Twenty~partialcommunity6/10

   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…”

   proof ↗⚑ flag

Data model

1. ops userAdd custom fields and build filtered, sorted, and shared views without an admin project

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   The evidence pack contains no documentation or citation that ops users can add custom fields, build filtered/sorted views, or share views without going through an admin/dev project — all cited material is generic marketing (AI, pipeline, forecasting) or CLI/developer tooling, not self-service customization UI. Community comment [salesforce-comm-4] even suggests customization in practice requires paid consultants rather than being self-serve, but this is general skepticism rather than a concrete hands-on contradiction, so it doesn't elevate to 'disputed' — it simply reinforces the lack of supporting evidence.

   • [community] “"That's the theory, in practice companies end up paying through the nose for an army of salesforce consultants" in response to the idea that…”
   • [community] “"We chose Salesforce, and haven't regretted it. The thing you need to keep in mind... is that you will need to do some customizations, and S…”

   proof ↗⚑ flag

   Twenty✓fullcommunity8/10

   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…”

   proof ↗⚑ flag

2. developerModel custom objects with fields and relationships beyond the built-in contacts, companies, and deals

   weight 3 · round to Twenty
   Salesforce Sales Cloud~partialcommunity5/10

   Evidence confirms Salesforce is broadly known for deep customization and has developer tooling (CLI, APIs, VS Code extensions, LWC local dev) that would support building custom objects/fields/relationships, and community input (salesforce-comm-6) explicitly notes Salesforce is 'a king of' customization. However, none of the evidence explicitly documents the Custom Objects/Fields/Schema Builder relationship-modeling feature itself. Missing for 10: explicit docs/screenshots of custom object creation, field types, and relationship (lookup/master-detail) modeling, plus independent hands-on confirmation of this specific capability.

   • [community] “"We chose Salesforce, and haven't regretted it. The thing you need to keep in mind... is that you will need to do some customizations, and S…”
   • [community] “"With SFDC I get a passable command line tool, multiple VS Code extensions, an easy deployment path, local development with Lightning Web Co…”
   • [claimed-docs] “Discover Salesforce APIs & put them to work.”
   • [github] “sf org create scratch”
   • [github] “[`sf org create scratch`](#sf-org-create-scratch)”

   proof ↗⚑ flag

   Twenty✓fullcommunity9/10

   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…”

   proof ↗⚑ flag

Email

1. ops userSync my calendar so meetings appear on contact and deal timelines

   weight 2 · round to Twenty
   Salesforce Sales Cloud~partialclaimed4/10

   There's a claimed-docs mention of 'AI Automatically Syncs Emails, Events, and Contacts' implying calendar/event sync into the CRM, but no evidence detailing calendar integration setup, how synced meetings appear specifically on contact/deal (opportunity) timelines, or any hands-on/independent confirmation. Missing for 10: detailed calendar-sync documentation, evidence of meetings appearing on timelines, independent/hands-on corroboration.

   • [claimed-docs] “AI Automatically Syncs Emails, Events, and Contacts”

   proof ↗⚑ flag

   Twenty✓fullclaimed8/10

   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”

   proof ↗⚑ flag

2. ops userConnect Gmail or Outlook so emails sync two-way and log automatically to the right records

   weight 3 · round to Twenty
   Salesforce Sales Cloud~partialclaimed5/10

   Salesforce Sales Cloud pricing docs list "AI Automatically Syncs Emails, Events, and Contacts" as a feature, implying Gmail/Outlook two-way sync and activity logging, but there is no detail on setup, reliability, or which records emails log to, nor any independent/hands-on confirmation. missing for 10: detailed docs on Einstein Activity Capture/Gmail-Outlook integration setup, confirmation of two-way sync behavior, independent user validation that emails log to correct records.

   • [claimed-docs] “AI Automatically Syncs Emails, Events, and Contacts”

   proof ↗⚑ flag

   Twenty✓fullclaimed8/10

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

   proof ↗⚑ flag

Outreach

1. ops userSend templated emails or multi-step sequences to prospects from inside the CRM

   weight 2 · round drawn
   Salesforce Sales Cloud~partialcommunity4/10

   Marketing copy mentions 'engagement built directly into your CRM' and automatic email syncing, and a community anecdote praises how quickly a timed email could be set up in Salesforce, but there is no explicit documentation of templated email or multi-step sequence/cadence tooling. Missing for 10: explicit feature docs for email templates, cadence/sequence builder, or multi-step engagement workflows, and independent verification beyond a single anecdotal comment.

   • [claimed-docs] “Accelerate sales, connect with buyers, and take action with engagement built directly into your CRM.”
   • [claimed-docs] “AI Automatically Syncs Emails, Events, and Contacts”
   • [claimed-docs] “Built-in Sales Flows and Lead Routing”
   • [community] “"D365 documentation is utter garbage when compared to the SFDC Trailhead... I spent many hours trying to figure out how to send timed emails…”

   proof ↗⚑ flag

   Twenty~partialclaimed4/10

   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”

   proof ↗⚑ flag

Api depth

1. developerSync records bidirectionally through the API at scale, with documented rate limits, upserts, and change detection

   weight 3 · round to Twenty
   Salesforce Sales Cloud—none0/10

   While Salesforce is known for REST/Bulk APIs, the evidence pack only offers generic marketing lines about 'APIs' and a CLI for org/data querying (salesforce-docs-7, salesforce-gh-3) with no documentation of upsert operations, rate limits, or change-data-capture/streaming for bidirectional sync at scale. Missing for 10: documented rate limits, upsert API details, change detection (CDC/PushTopic/Platform Events) evidence.

   • [claimed-docs] “Discover Salesforce APIs & put them to work.”
   • [github] “[`sf data query`](#sf-data-query)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.salesforce.com/openapi.json, https://www.salesforce.com/swagger.json, https://www.salesf…”

   proof ↗⚑ flag

   Twenty~partialcommunity5/10

   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…”

   proof ↗⚑ flag

Ecosystem

1. ops userInstall prebuilt integrations (Slack, support desk, marketing, data warehouse) from an app marketplace

   weight 2 · round to Twenty
   Salesforce Sales Cloud~partialclaimed3/10

   Evidence shows Salesforce has a marketplace concept (AgentExchange) where admins can 'find, evaluate, and plug in trusted third-party agents, sub-agents, and MCP servers' (salesforce-docs-28) and pricing tiers reference 'Access to AgentExchange' (salesforce-docs-23), suggesting some app-marketplace capability exists. However, none of the evidence specifically confirms prebuilt Slack, support-desk, marketing, or data-warehouse integrations being installable from this or the classic AppExchange marketplace. Missing for 10: explicit mention of AppExchange, named integrations (Slack, ServiceNow/Zendesk, marketing tools, Snowflake/data warehouses), and any independent confirmation of installation workflow.

   • [claimed-docs] “you can find, evaluate, and plug in trusted third-party agents, sub-agents, and MCP servers directly within Agentforce Builder”
   • [claimed-docs] “Access to AgentExchange”

   proof ↗⚑ flag

   Twenty~partialclaimed4/10

   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”

   proof ↗⚑ flag

Imports

1. ops userMigrate from another CRM with my records, owners, and history intact

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   No evidence pack items address CRM migration tooling, data import from competing CRMs, preservation of record ownership, or historical activity data; all evidence covers AI/sales features, CLI/dev tooling, and general community sentiment unrelated to migration.

   ⚑ flag

   Twenty~partialclaimed5/10

   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…”

   proof ↗⚑ flag

2. founderImport my spreadsheet of contacts and deals with field mapping and validation, without losing rows silently

   weight 3 · round to Twenty
   Salesforce Sales Cloud—none0/10

   No evidence in the pack addresses spreadsheet/CSV import, field mapping, validation, or handling of failed/skipped rows during data import — the pack only covers AI sales features, CLI tooling, and general community sentiment. This is a fair onboarding-migration axis for a CRM, but nothing here demonstrates it.

   ⚑ flag

   Twenty✓fullclaimed8/10

   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”

   proof ↗⚑ flag

Time to value

1. founderGo from signup to a working pipeline with my real data in under an hour, without an implementation partner

   weight 2 · round to Twenty
   Salesforce Sales Cloud!disputedcontradicted4/10

   Salesforce offers a self-serve free trial signup (salesforce-docs-15), but hands-on community evidence directly contradicts the claim of quick, partner-free setup: users note Salesforce customization is heavy and 'companies end up paying through the nose for an army of salesforce consultants,' and that it 'will need customizations' and is compared to 'the Jira of CRMs' for being cumbersome. No evidence of a guided, sub-hour data-import-to-pipeline flow exists in the pack. missing for 10: documented quick-start data import wizard, evidence of founders/small teams completing setup without consultants, time-to-value benchmarks.

   • [claimed-docs] “Try our all-in-one CRM - free for 30 days”
   • [community] “"That's the theory, in practice companies end up paying through the nose for an army of salesforce consultants" in response to the idea that…”
   • [community] “"We chose Salesforce, and haven't regretted it. The thing you need to keep in mind... is that you will need to do some customizations, and S…”
   • [community] “"Salesforce is the Jira of CRMs.." — a comparison suggesting Salesforce is powerful but cumbersome/bloated like Jira.”

   proof ↗⚑ flag

   Twenty~partialcommunity6/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud~partialprobed5/10

   Evidence shows Salesforce has a broad API/CLI ecosystem (sf CLI, data query, org management, agent creation) and community praise for developer tooling, plus an MCP server, suggesting programmatic access is extensive. However, there's no explicit documentation or claim of full UI/API feature parity, and the openapi probe returned 404s, leaving the actual scope of API coverage unverified. Missing for 10: explicit API-vs-UI parity documentation, enumeration of UI-only features (if any), and independent confirmation that all sales-cycle actions (forecasting, quoting, agent config) are fully API-accessible.

   • [claimed-docs] “Discover Salesforce APIs & put them to work.”
   • [github] “sf org create scratch”
   • [github] “[`sf data query`](#sf-data-query)”
   • [github] “sf agent create”
   • [probe] “official MCP server documented at https://github.com/salesforcecli/mcp”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.salesforce.com/openapi.json, https://www.salesforce.com/swagger.json, https://www.salesf…”
   • [community] “"With SFDC I get a passable command line tool, multiple VS Code extensions, an easy deployment path, local development with Lightning Web Co…”

   proof ↗⚑ flag

   Twenty~partialcommunity7/10

   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…”

   proof ↗⚑ flag

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

   weight 3 · round to Twenty
   Salesforce Sales Cloud—none0/10

   No evidence of bulk data export in open/standard formats or a documented data-portability/exit path; CLI (sf data query) supports querying but not evidenced as a full open-format export mechanism. Missing for 10: documented bulk export tools (e.g., Data Loader/Bulk API) producing open formats like CSV/JSON, data portability/exit guarantees, and any independent confirmation of a clean 'leave with your data' workflow.

   • [github] “[`sf data query`](#sf-data-query)”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”

   proof ↗⚑ flag

   Twenty✓fullclaimed8/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   Salesforce Sales Cloud is closed-source proprietary SaaS; while a CLI is open-source, the core product source is not available under any open license, and no evidence indicates otherwise.

   ⚑ flag

   Twenty✓fullcommunity8/10

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

   proof ↗⚑ flag

Ai crm ops

1. 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 Salesforce Sales Cloud
   Salesforce Sales Cloud~partialprobed6/10

   Salesforce documents an official API/CLI (salesforce-probe-4, salesforce-docs-7) and an official MCP server (salesforce-probe-3, salesforce-docs-28) that can plug into Agentforce, plus Agentforce agents explicitly listed as 'Updating opportunity' (salesforce-docs-31) and automatic email/event syncing (salesforce-docs-8). However, no concrete documentation ties these together into the specific workflow of an agent parsing email/meeting signals to update deal stage and next-step fields end-to-end. Missing for 10: explicit docs/demo of email-or-meeting-signal-driven stage/next-step updates via API or MCP, and independent/hands-on confirmation this works as described.

   • [probe] “official MCP server documented at https://github.com/salesforcecli/mcp”
   • [claimed-docs] “you can find, evaluate, and plug in trusted third-party agents, sub-agents, and MCP servers directly within Agentforce Builder”
   • [claimed-docs] “Qualifying inbound lead | Updating opportunity | Closing renewal deal”
   • [claimed-docs] “AI Automatically Syncs Emails, Events, and Contacts”
   • [claimed-docs] “Discover Salesforce APIs & put them to work.”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”

   proof ↗⚑ flag

   Twenty~partialclaimed5/10

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

   proof ↗⚑ flag

Deals

1. ops userRun multiple pipelines with different stage sets for different products or motions

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   Salesforce Sales Cloud supports customizable sales processes and multiple record types with different stage sets in principle, but the evidence pack contains no mention of multiple pipelines, record-type-based sales processes, or configurable stage sets for different products/motions — only generic AI/forecasting/pipeline-visibility marketing copy and CLI/dev tooling references.

   ⚑ flag

   Twenty~partialclaimed5/10

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

   proof ↗⚑ flag

2. founderTrack deals on a visual pipeline with customizable stages and drag-and-drop updates

   weight 3 · round to Twenty
   Salesforce Sales Cloud~partialclaimed5/10

   Docs confirm pipeline/opportunity management, forecasting, and stage-based sales cycle tracking (salesforce-docs-3, -20, -22, -24), which implies a Kanban-style pipeline view exists in Sales Cloud, but no evidence specifically describes drag-and-drop stage updates or customizable stage configuration UI. Missing for 10: explicit documentation or screenshot/hands-on confirmation of drag-and-drop pipeline board interactions and customizable stage setup, independent corroboration of this specific UX feature.

   • [claimed-docs] “Get complete visibility into your pipeline. Surface insights to speed up prospecting and opportunity management.”
   • [claimed-docs] “Advanced Forecast & Pipeline Management”
   • [claimed-docs] “Lead, Account, Contact, and Opportunity Management”
   • [claimed-docs] “Transform every stage of the sales cycle — from prospecting and pipeline management to account growth and partner success.”

   proof ↗⚑ flag

   Twenty~partialcommunity7/10

   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…”

   proof ↗⚑ flag

Forecasting

1. founderForecast revenue from pipeline value, stage probabilities, and close dates

   weight 2 · round to Salesforce Sales Cloud
   Salesforce Sales Cloud✓fullclaimed8/10

   Salesforce Sales Cloud explicitly offers Predictive Forecasting, Advanced Forecast & Pipeline Management, and Opportunity Management features that combine pipeline value, stage probabilities, and close dates for revenue forecasting, backed by named product features in pricing docs. Missing for 10: independent hands-on validation of forecasting accuracy and no detailed walkthrough of how stage probability/close date roll up into forecast numbers.

   • [claimed-docs] “Predictive Forecasting”
   • [claimed-docs] “Advanced Forecast & Pipeline Management”
   • [claimed-docs] “Sales Quoting and Forecasting”
   • [claimed-docs] “Lead, Account, Contact, and Opportunity Management”
   • [claimed-docs] “Get complete visibility into your pipeline. Surface insights to speed up prospecting and opportunity management.”

   proof ↗⚑ flag

   Twenty~partialclaimed5/10

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

   proof ↗⚑ flag

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

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   No evidence pack items mention data residency, regional hosting options, or org data location controls for Sales Cloud; only ABAC access control and general AI feature marketing are covered. Salesforce is known to offer data residency options in reality, but this evidence pack contains no documentation of that capability, so verdict must be none. Missing for 10: any documentation of region/data-residency selection, hyperforce or org shard location controls, or data storage compliance options.

   • [claimed-docs] “Admins can control who sees what data and when, from humans to AI agents, by enforcing custom attribute-based (ABAC) access policies.”

   proof ↗⚑ flag

   Twenty~partialclaimed5/10

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

   proof ↗⚑ flag

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

   weight 3 · round to Twenty
   Salesforce Sales Cloud—none0/10

   The evidence pack contains no documentation or policy statement addressing whether customer data is used to train AI models or how users can opt out of such training; only ABAC access control policies and generic AI feature marketing are mentioned. Missing for 10: explicit data-usage/training opt-out policy, documentation of a no-training guarantee or toggle, any independent confirmation of such controls.

   • [claimed-docs] “Admins can control who sees what data and when, from humans to AI agents, by enforcing custom attribute-based (ABAC) access policies.”

   proof ↗⚑ flag

   Twenty~partialclaimed4/10

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

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Twenty
   Salesforce Sales Cloud—none0/10

   The evidence pack covers AI sales features, CLI/DevOps tooling, and access-control (ABAC) mentions, but nothing addresses data retention policies, deletion workflows, or how AI-processed data is purged or retained. missing for 10: documentation on data retention schedules, right-to-erasure/deletion tooling, AI-specific data handling/retention policy statements.

   ⚑ flag

   Twenty~partialclaimed3/10

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Salesforce Sales Cloud—none0/10

   No evidence pack items mention telemetry opt-out, usage tracking controls, or any privacy toggle for AI-native usage data collection; ABAC data access controls (salesforce-docs-32) address data visibility, not telemetry opt-out. Missing for 10: any documentation of a telemetry/usage-tracking opt-out mechanism, settings or admin controls for disabling analytics/telemetry collection.

   • [claimed-docs] “Admins can control who sees what data and when, from humans to AI agents, by enforcing custom attribute-based (ABAC) access policies.”

   proof ↗⚑ flag

   Twenty—none0/10

   No evidence in the pack mentions telemetry, usage tracking, analytics collection, or an opt-out setting; self-hosting is mentioned but does not itself confirm control over telemetry data collection.

   ⚑ flag

Ai crm ops

1. 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 Twenty
   Salesforce Sales Cloud~partialprobed5/10

   Salesforce exposes CRM data (accounts, opportunities, emails, activity history) via APIs and has an official MCP server (salesforcecli/mcp) plus a general-purpose CLI capable of data queries, giving an agent plumbing to assemble an account brief. However, there's no documented example, template, or first-party workflow specifically compiling 'open deals + recent emails + history' into a pre-meeting brief — this is inferred capability rather than demonstrated. Missing for 10: a concrete first-party or independent example of an agent generating a pre-meeting account brief combining deals/emails/history, and documentation of the specific API/MCP calls needed to pull email history alongside opportunity and activity data.

   • [probe] “official MCP server documented at https://github.com/salesforcecli/mcp”
   • [probe] “official CLI documented at https://github.com/salesforcecli/cli”
   • [github] “[`sf data query`](#sf-data-query)”
   • [claimed-docs] “AI Automatically Syncs Emails, Events, and Contacts”
   • [claimed-docs] “Lead, Account, Contact, and Opportunity Management”
   • [claimed-docs] “Discover Salesforce APIs & put them to work.”

   proof ↗⚑ flag

   Twenty~partialclaimed6/10

   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…”

   proof ↗⚑ flag

Reporting

1. founderBuild reports and dashboards on pipeline, activity, and conversion without exporting to a spreadsheet

   weight 3 · round to Twenty
   Salesforce Sales Cloud~partialclaimed5/10

   Evidence shows Sales Cloud provides built-in pipeline visibility, forecasting, and a dashboard view (salesforce-docs-3, salesforce-docs-9, salesforce-docs-10, salesforce-docs-20) rather than requiring spreadsheet export, supporting the core of the story. However, there is no explicit documentation of a report/dashboard builder tool, activity reporting, or conversion-rate analytics specifically, so the coverage of the full story is only partial. missing for 10: dedicated report-builder documentation, activity-metrics reporting evidence, conversion funnel analytics, and independent/hands-on corroboration of dashboard customization.

   • [claimed-docs] “Get complete visibility into your pipeline. Surface insights to speed up prospecting and opportunity management.”
   • [claimed-docs] “Sales Quoting and Forecasting”
   • [claimed-docs] “Dashboard view of Sales Cloud with an overlay to zoom in on AI-generated lead scoring within a CRM view.”
   • [claimed-docs] “Advanced Forecast & Pipeline Management”

   proof ↗⚑ flag

   Twenty✓fullcommunity8/10

   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…”

   proof ↗⚑ flag