Attio vs Salesforce Sales Cloud

Agent access

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

   weight 2 · round to Attio
   Attio✓fullprobed9/10

   Attio directly hosts a working llms.txt at docs.attio.com/llms.txt (verified via probe returning HTTP 200 with structured doc links), confirming agents can be pointed at agent-oriented documentation, and this is corroborated by an official MCP endpoint for AI tool integration. missing for 10: independent third-party confirmation beyond the direct probe.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”
   • [probe] “official MCP server documented at https://attio.com/mcp”
   • [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”

   proof ↗⚑ flag

   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

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

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

   Attio exposes a REST API, OAuth, webhooks, and SQL query access that let developers script and automate workspace actions headlessly outside the UI, and probes confirm a real API/docs surface (llms.txt, MCP server) rather than pure marketing. However, there is no mention of a CLI, SDK for CI pipelines, or any CI-specific tooling/guide, so the 'run in CI' half of the story is unevidenced. Missing for 10: CLI or CI-pipeline integration guide, examples of scheduled/headless jobs, official SDK usable in build pipelines.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “Building an OAuth flow for your app”
   • [claimed-docs] “Run SQL queries against your workspace data.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”

   proof ↗⚑ flag

   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

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

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

   Evidence shows Attio ships its own MCP server so external AI tools (Claude, ChatGPT) can connect to and control Attio (attio-docs-3, attio-probe-3), but this is the reverse of the story — there is no evidence Attio itself can plug in and consume external MCP servers' tools.

   • [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
   • [probe] “official MCP server documented at https://attio.com/mcp”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Attio
   Attio✓fullprobed8/10

   Attio documents an official MCP server (attio.com/mcp) explicitly enabling connection of Claude, ChatGPT, or other AI tools to search, update, and manage the workspace, and a probe confirms this page exists. Missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice and more detail on setup/auth specifics.

   • [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
   • [probe] “official MCP server documented at https://attio.com/mcp”

   proof ↗⚑ flag

   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

5. ai-native userUse an official CLI

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

   Attio is a CRM SaaS platform whose ecosystem could plausibly ship an official CLI, but the evidence pack contains no mention of a CLI tool anywhere—only REST API, webhooks, SQL query access, and an MCP server for AI assistants. Absence of evidence for this applicable capability yields none.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Run SQL queries against your workspace data.”
   • [probe] “official MCP server documented at https://attio.com/mcp”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Attio✓fullprobed8/10

   Attio documents a REST API for reading/writing workspace data, OAuth flows, filtering/sorting, rate limiting, and webhooks, giving AI-native users a fully documented public API to drive the product; llms.txt and docs.attio.com confirm developer-facing documentation. missing for 10: no discoverable OpenAPI/Swagger spec (probe found 404s) and no independent/third-party corroboration beyond vendor docs.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
   • [claimed-docs] “Building an OAuth flow for your app”
   • [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”

   proof ↗⚑ flag

   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

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

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

   Attio documents a general OAuth flow for third-party apps (attio-docs-7) and an MCP server for AI tools (attio-probe-3), but there is no evidence of granular, least-privilege scopes or agent-specific API credential issuance — no mention of scope lists, permission levels, or restricting an API key/token to specific objects/actions for an AI agent.

   • [claimed-docs] “Building an OAuth flow for your app”
   • [probe] “official MCP server documented at https://attio.com/mcp”

   proof ↗⚑ flag

   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

8. ai-native userBuild against official SDKs

   weight 2 · round to Salesforce Sales Cloud
   Attio~partialprobed4/10

   Attio documents a REST API, OAuth flow, webhooks, and a TypeScript-based 'Apps' framework for building on the platform, which functions as a developer toolkit, but there is no explicit mention of dedicated official client SDKs (e.g., named Node.js/Python/Go libraries), and the OpenAPI spec probe returned 404s, suggesting no auto-generated or downloadable SDK artifacts. Missing for 10: named official language SDK packages/libraries, published SDK versioning/changelog, and independent developer corroboration of SDK usage.

   • [claimed-docs] “This allows developers to embed Typescript React applications within the Attio interface and run server functions with access to our REST AP…”
   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Building an OAuth flow for your app”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”

   proof ↗⚑ flag

   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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Attio
   Attio✓fullclaimed8/10

   Attio's REST API docs explicitly describe webhook subscriptions for real-time change events, including signed payloads for verification, which directly satisfies subscribing to events via webhooks. Missing for 10: independent/hands-on corroboration beyond vendor docs, and details on event-type granularity/filtering for webhook subscriptions.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “We cryptographically sign every webhook request using your webhook secret, and include it as HTTP header called `Attio-Signature`”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Salesforce Sales Cloud
   Attio✓fullclaimed7/10

   Attio's AI platform docs describe in-product AI features like buying-signal detection, call transcription and analysis, account briefs, AI-driven workflow agents (scoring, routing, web research), and 'search, update, create with AI' surfaced directly in the CRM, which match the story of AI-generated insights/suggestions from workspace data. Missing for 10: independent/hands-on verification of these AI insight features in real use (all evidence is vendor marketing copy) and detail on underlying model/accuracy.

   • [claimed-docs] “Search, update, and create with AI.”
   • [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
   • [claimed-docs] “AI records, transcribes, and logs every call as you speak.”
   • [claimed-docs] “AI picks up buying signals, blockers, or requests during the call, not days later.”
   • [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
   • [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
   • [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
   • [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”

   proof ↗⚑ flag

   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

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

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

   Attio documents workflow automations with triggers (e.g., new deal created) and AI-driven 'agents' (Web Agent, Routing Agent, Scoring Agent) that run automatically in the background, plus webhooks for real-time event handling. However, there's no independent/hands-on evidence of true autonomous multi-step agentic execution or scheduling reliability beyond first-party marketing copy. Missing for 10: independent verification of autonomous background execution, details on failure handling/monitoring of these automations, and evidence beyond vendor marketing pages.

   • [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
   • [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
   • [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
   • [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
   • [claimed-docs] “When a new deal is created / Trigger when a new deal record is created.”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”

   proof ↗⚑ flag

   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

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

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

   Attio has built-in AI features that act as an assistant: search/update/create with AI, drafting follow-ups, updating records, scheduling next steps, building account briefs, and even building workflows by describing a goal, plus AI call transcription and signal detection. This shows delegable AI assistant tasks embedded in the product, but evidence lacks detail on a dedicated chat-style assistant UI, task delegation scope, or independent hands-on confirmation of reliability. missing for 10: independent/hands-on validation of assistant behavior, clarity on assistant UI/interaction model, and limits/scope of delegable tasks.

   • [claimed-docs] “Search, update, and create with AI.”
   • [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
   • [claimed-docs] “AI records, transcribes, and logs every call as you speak.”
   • [claimed-docs] “AI picks up buying signals, blockers, or requests during the call, not days later.”
   • [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Attio
   Attio✓fullprobed8/10

   Attio explicitly documents natural-language control via AI: connecting Claude/ChatGPT to search, update and manage the workspace, an official MCP server, and AI features to search/update/create records and build workflows just by describing goals. This directly matches the story of operating the product via natural-language commands, though evidence is vendor-documented without independent hands-on verification. missing for 10: independent/third-party confirmation of natural-language command reliability, and depth on limits/edge cases of NL command coverage.

   • [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
   • [claimed-docs] “Search, update, and create with AI.”
   • [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
   • [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
   • [probe] “official MCP server documented at https://attio.com/mcp”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Attio—none0/10

   The docs describe REST API concepts (filtering, webhooks, rate limits, OAuth) but there is no mention of an interactive API reference or runnable/try-it examples, and a probe found no discoverable OpenAPI spec at any standard path, suggesting no such interactive console exists.

   • [claimed-docs] “Building an OAuth flow for your app”
   • [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Attio—none0/10

   Direct probes for OpenAPI/Swagger spec files at Attio's docs domain all returned 404, and no evidence pack item references a downloadable machine-readable API spec despite extensive REST API documentation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Salesforce Sales Cloud
   Attio—none0/10

   No evidence of a sandbox/test workspace or staging environment separate from production; docs cover API, objects, workflows, and MCP but nothing about sandbox testing without touching live data.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Attio—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the docs cover REST API features (filtering, webhooks, rate limits, OAuth) but nothing about version numbers, changelogs, or deprecation timelines. OpenAPI spec probes also 404'd, further suggesting no clear versioned contract is published.

   • [claimed-docs] “Building an OAuth flow for your app”
   • [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Attio
   Attio~partialprobed5/10

   Attio's REST API supports filtering/sorting to narrow record sets and has SQL query access, and its API/MCP integration could enable scripted bulk updates, but there is no explicit documentation of a bulk-update/bulk-create/bulk-delete endpoint or batch operation limits for AI-driven mass edits. missing for 10: explicit bulk write/update API endpoints, documented batch size limits, and evidence of AI agents performing bulk operations across many records at once.

   • [claimed-docs] “Run SQL queries against your workspace data.”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
   • [claimed-docs] “Filtering and sorting > Searching for just the records you need”
   • [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request.”
   • [probe] “official MCP server documented at https://attio.com/mcp”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Attio
   Attio✓fullclaimed7/10

   Attio's Workflows platform explicitly supports event-based triggers (e.g. 'trigger when a new deal record is created') that fire automated actions/agents (routing, scoring, web research agents), and webhooks/REST API allow custom event-driven automation. Missing for 10: detailed documentation of the full trigger/condition/action rule-builder UI, and independent/hands-on verification of complex multi-step automation reliability.

   • [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”
   • [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
   • [claimed-docs] “When a new deal is created / Trigger when a new deal record is created.”
   • [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
   • [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
   • [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Attio
   Attio~partialclaimed5/10

   Attio's workflows platform supports event-triggered automations (e.g., 'when a new deal is created') and AI agents that run continuously (routing, scoring, web research), implying ongoing/ongoing-scheduled automation, but there is no explicit documentation of cron-like recurring/time-based scheduling of jobs. Missing for 10: explicit recurring/scheduled job trigger (e.g., 'run every day/week'), documentation of interval-based automation, and independent confirmation of scheduling reliability.

   • [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”
   • [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
   • [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
   • [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
   • [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
   • [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Attio—none0/10

   No evidence of version history, review workflows, or rollback for Attio's automations/workflows; docs describe building and triggering workflows but nothing about versioning or reverting them. missing for 10: version history for automations, change review/approval process, rollback mechanism, audit trail of automation edits.

   ⚑ flag

   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

Workflows

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

   weight 2 · round to Attio
   Attio~partialclaimed6/10

   Attio's Workflows platform explicitly includes a 'Routing Agent' that 'routes every lead to the right rep or channel' and a 'Scoring Agent' that assigns fit based on ICP criteria, directly supporting automated lead assignment; workflows can also trigger on new record creation. However, evidence is all vendor marketing copy with no configuration detail on round-robin logic, tie-breaking, or capacity balancing, and no independent/hands-on confirmation. Missing for 10: detailed documentation of round-robin/assignment rule configuration options, independent or hands-on validation of the Routing Agent in practice, and evidence of load-balancing or fairness logic.

   • [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
   • [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
   • [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
   • [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Attio
   Attio~partialclaimed6/10

   Attio documents workflows platform with triggers (e.g., 'when a new deal is created') and automated agents that route leads, score leads, and update records, plus webhooks for real-time notifications and REST API for record updates — covering the core story elements. However, evidence is mostly marketing-page descriptions rather than detailed workflow-builder documentation showing task creation or multi-step conditional logic, and no independent/hands-on confirmation of reliability. Missing for 10: detailed docs on workflow builder UI/logic, explicit task-creation trigger actions, and independent verification of automation reliability.

   • [claimed-docs] “When a new deal is created Trigger when a new deal record is created.”
   • [claimed-docs] “Routing Agent Routes every lead to the right rep or channel.”
   • [claimed-docs] “Web Agent Researches accounts for the latest on the web.”
   • [claimed-docs] “Web Agent / Researches accounts for the latest on the web. ... Scoring Agent / Assigns fit to leads based on your ICP criteria. ... Routing …”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “We cryptographically sign every webhook request using your webhook secret, and include it as HTTP header called `Attio-Signature`”
   • [claimed-docs] “Orchestrate your best plays, on every account, over the deepest context layer in AI CRM.”

   proof ↗⚑ flag

   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

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

   Attio has a documented REST API for creating/updating records (attio-docs-2, attio-docs-8/9/14) and an official MCP server (attio-probe-3, attio-docs-3, attio-docs-12) letting AI tools search, update and create records, and separately advertises 'automatic data enrichment' (attio-docs-26/45/47). However, there is no explicit documentation showing an end-to-end workflow of creating a lead, auto-filling company data, and assigning an owner in one API/MCP call chain — owner-assignment and enrichment-via-API/MCP specifics are unevidenced. Missing for 10: explicit API/MCP example of owner assignment, documented enrichment endpoint/field mapping, and a hands-on end-to-end example combining all three steps.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
   • [claimed-docs] “Search, update, and create with AI.”
   • [claimed-docs] “Real-time contact syncing Automatic data enrichment”
   • [claimed-docs] “Real-time contact syncing Automatic data enrichment Up to 3 seats”
   • [claimed-docs] “Automatic data enrichment”
   • [probe] “official MCP server documented at https://attio.com/mcp”
   • [claimed-docs] “Create the exact data model your business needs with custom objects.”
   • [claimed-docs] “Link objects to make your data actionable and insightful with our powerful graph model.”
   • [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”

   proof ↗⚑ flag

   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

Data quality

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

   weight 2 · round to Attio
   Attio~partialclaimed5/10

   Attio's pricing page explicitly lists 'Automatic data enrichment' and 'Real-time contact syncing' as features, and the platform data page mentions prospect context 'automatically drawn from 100' (sources, cut off), suggesting some enrichment capability. However there's no detail on what firmographic/contact data sources are used, how enrichment is triggered/configured, or coverage/accuracy — missing for 10: documentation of enrichment data providers, configuration/setup details, coverage scope, and independent/hands-on verification of enrichment quality.

   • [claimed-docs] “Real-time contact syncing Automatic data enrichment”
   • [claimed-docs] “Real-time contact syncing Automatic data enrichment Up to 3 seats”
   • [claimed-docs] “Automatic data enrichment”
   • [claimed-docs] “Real-time contact syncing”
   • [claimed-docs] “Get the context you need for every prospect, automatically drawn from 100”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Attio—none0/10

   No evidence pack item mentions duplicate detection or record merging for contacts/companies; docs cover objects, lists, filtering, webhooks, and AI features but nothing about dedupe/merge workflows.

   ⚑ flag

   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

Record management

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

   weight 3 · round to Attio
   Attio✓fullclaimed8/10

   Attio's data model natively supports People and Companies as linked objects connected via a graph model, with custom fields, list/table views, and full interaction history surfaced per record (e.g., 'Link objects to make your data actionable' and 'Get instant visibility into the full history of every interaction'). This directly matches the ops story of managing linked contact/company records with activity timelines. missing for 10: independent/hands-on corroboration of the timeline UI itself (only first-party marketing/docs cited), and no explicit screenshot or detailed description of the timeline feed contents.

   • [claimed-docs] “Link objects to make your data actionable and insightful with our powerful graph model.”
   • [claimed-docs] “Get instant visibility into the full history of every interaction.”
   • [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
   • [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
   • [claimed-docs] “Customize fields to capture exactly what you need to track.”
   • [claimed-docs] “From kanbans to tables, visualize your data the way that works for you.”

   proof ↗⚑ flag

   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

Data model

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

   weight 2 · round to Attio
   Attio~partialclaimed6/10

   Attio's docs confirm custom fields ('Customize fields to capture exactly what you need to track'), filtering/sorting capabilities, and object/list data modeling that ops users could use to build views without engineering, but evidence is API/docs-centric rather than showing the actual no-admin UI workflow for creating and sharing saved views. missing for 10: explicit documentation of the UI-level 'shared views' feature and permission model confirming non-admin ops users can create/share views without admin involvement.

   • [claimed-docs] “Customize fields to capture exactly what you need to track.”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
   • [claimed-docs] “Filtering and sorting > Searching for just the records you need”
   • [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”
   • [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
   • [claimed-docs] “From kanbans to tables, visualize your data the way that works for you.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Attio
   Attio✓fullclaimed8/10

   Attio's docs explicitly support creating custom objects with custom fields, and linking objects via a graph model to build relationships beyond the standard people/company/deal objects (attio-docs-8, attio-docs-9, attio-docs-46, attio-docs-29). This is corroborated by API-level guidance for objects and lists as domain modeling primitives. missing for 10: independent/hands-on third-party confirmation of custom object creation limits or relationship types, and deeper API reference detail on relationship/field-type configuration.

   • [claimed-docs] “Create the exact data model your business needs with custom objects.”
   • [claimed-docs] “Link objects to make your data actionable and insightful with our powerful graph model.”
   • [claimed-docs] “Customize fields to capture exactly what you need to track.”
   • [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
   • [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”

   proof ↗⚑ flag

   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

Email

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

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

   No evidence describes a calendar sync feature that surfaces meetings on contact/deal timelines; mentions of 'real-time contact syncing' and call logging/transcription do not address calendar/meeting sync specifically.

   ⚑ flag

   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

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

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

   Evidence pack shows general contact syncing/enrichment claims and API/webhook infrastructure, but no mention of Gmail or Outlook two-way email sync or automatic email logging to records anywhere in the docs or probes.

   ⚑ flag

   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

Outreach

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

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

   Attio is a CRM with data model, workflows, AI agents, and API/webhook capabilities, but the evidence pack contains no mention of templated email sending or multi-step outbound sequence/cadence functionality for prospects; only 'draft follow-ups' via AI assistant is mentioned, not automated sequences.

   ⚑ flag

   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

Api depth

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

   weight 3 · round to Attio
   Attio~partialclaimed6/10

   Attio's docs confirm a read/write REST API, documented rate limits (429 + Retry-After) and webhooks for real-time change detection, which together support much of the story. However, there is no explicit documentation in the evidence pack of upsert/assert-style endpoints or guidance on syncing at scale (batching, pagination limits, throughput), so the story is only partially covered. missing for 10: explicit upsert endpoint docs, scale/batch sync guidance, independent corroboration of reliability at scale.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “We cryptographically sign every webhook request using your webhook secret, and include it as HTTP header called `Attio-Signature`”
   • [claimed-docs] “Rate limit responses always have the HTTP status code `429`. They also always include a `Retry-After` header”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
   • [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”

   proof ↗⚑ flag

   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

Ecosystem

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

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

   Evidence shows Attio has a developer platform for building custom apps, REST API, webhooks, and OAuth, plus an AI/MCP connector, but there is no mention of a prebuilt app marketplace with ready-made Slack, support desk, marketing, or data warehouse integrations that ops users can simply install.

   • [claimed-docs] “This allows developers to embed Typescript React applications within the Attio interface and run server functions with access to our REST AP…”
   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Building an OAuth flow for your app”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.attio.com/llms.txt # Attio Docs - [Overview](https://docs.attio.com/docs/overview.md): Start build…”

   proof ↗⚑ flag

   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

Imports

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

   weight 2 · round to Attio
   Attio~partialclaimed4/10

   Attio references migration mostly via marketing-chat snippets promising deal history mapping and an onboarding migration checklist, but there is no documented import tool, CSV/CRM connector, owner-mapping mechanism, or independent verification that records/owners/history transfer intact. missing for 10: a documented migration tool or CRM-specific importer, evidence of owner/user mapping during migration, independent case studies or hands-on confirmation of successful full-history migration, and details on handling of activity/history data beyond a marketing anecdote.

   • [claimed-docs] “we'll map it during onboarding, and I'll include a migration checklist.”
   • [claimed-docs] “Can we bring our existing deal history across too? ... Yep — we'll map it during onboarding, and I'll include a migration checklist.”
   • [claimed-docs] “Yep — we'll map it during onboarding, and I'll include a migration checklist.”
   • [claimed-docs] “Get instant visibility into the full history of every interaction.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Attio
   Attio~partialclaimed3/10

   Marketing chat snippets mention that Attio will 'map it during onboarding' and provide a 'migration checklist' for bringing over existing spreadsheet/deal data, implying some import support, but there is no actual product documentation describing a CSV/spreadsheet import tool, field-mapping UI, validation rules, or safeguards against silently dropped rows. missing for 10: dedicated import/CSV mapping feature docs, validation/error-reporting behavior, evidence of row-loss prevention, independent user confirmation of successful large imports.

   • [claimed-docs] “we'll map it during onboarding, and I'll include a migration checklist.”
   • [claimed-docs] “Can we bring our existing deal history across too? ... Yep — we'll map it during onboarding, and I'll include a migration checklist.”
   • [claimed-docs] “Yep — we'll map it during onboarding, and I'll include a migration checklist.”
   • [claimed-docs] “Everything's in spreadsheets right now and it's getting unmanageable. I'd like the whole team moved over by Monday if we can.”

   proof ↗⚑ flag

   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

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

   Attio ships default People/Companies objects and optional Deals that can be enabled instantly (attio-docs-14, attio-docs-13), and marketing copy references a migration checklist and same-week team migration (attio-docs-38, attio-docs-39, attio-docs-44), suggesting some self-serve speed. However, these quotes describe 'we'll map it during onboarding' which implies vendor/human-assisted setup rather than a pure self-serve under-an-hour flow, and there is no evidence of a guided import wizard, templates, or time-to-value benchmarks. Missing for 10: concrete self-serve CSV/import tooling, onboarding time benchmarks, evidence that no implementation partner or vendor assistance is needed.

   • [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
   • [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
   • [claimed-docs] “Can we bring our existing deal history across too? ... Yep — we'll map it during onboarding, and I'll include a migration checklist.”
   • [claimed-docs] “Everything's in spreadsheets right now and it's getting unmanageable. I'd like the whole team moved over by Monday if we can.”
   • [claimed-docs] “Yep — we'll map it during onboarding, and I'll include a migration checklist.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Attio
   Attio~partialprobed6/10

   Attio's REST API covers core CRUD on objects/lists, filtering/sorting, webhooks, and OAuth, and there's an official MCP server for AI agent access, suggesting broad parity with UI operations for data management. However, evidence doesn't confirm API parity for newer AI-native workflow builder features (natural-language workflow creation, AI call recording/insights, routing/scoring agents) or reporting/visualization capabilities, and no OpenAPI spec was found to verify full endpoint coverage. Missing for 10: explicit confirmation that all UI-exposed features (AI agents, workflow builder, reporting/dashboards) are API-accessible, and a published OpenAPI spec proving endpoint completeness.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”
   • [claimed-docs] “Building an OAuth flow for your app”
   • [claimed-docs] “Filtering and sorting > Searching for just the records you need”
   • [claimed-docs] “Attio supports two distinct formats for filtering. There is the verbose format, which supports a wider variety of operators and conditions, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.attio.com/openapi.json, https://docs.attio.com/swagger.json, https://docs.attio.com/api…”
   • [probe] “official MCP server documented at https://attio.com/mcp”
   • [claimed-docs] “Ask Attio to build workflows for you just by describing the goal.”
   • [claimed-docs] “Analyze live data any way you like, from line charts and bar graphs to geospatial mapping.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Attio
   Attio~partialclaimed3/10

   Attio's REST API (attio-docs-2, attio-docs-4, attio-docs-6) lets a developer read/write and query workspace data, which could technically be used to script a full data export, but there is no documented native 'export all data' feature, no mention of open export formats (CSV/JSON dump), and no explicit portability/exit guarantee. Missing for 10: a documented bulk export/backup feature, explicit open-format export (CSV/JSON), and any statement about data portability upon leaving the platform.

   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Run SQL queries against your workspace data.”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”

   proof ↗⚑ flag

   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

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

   Attio has a documented MCP server that lets AI tools search, update and manage workspace data (attio-probe-3, attio-docs-3, attio-docs-12), plus REST API with read/write access and webhooks for real-time signals (attio-docs-2, attio-docs-5), and deals/next-steps fields exist as standard objects (attio-docs-13, attio-docs-30). AI features mention drafting follow-ups and updating records, and call AI picks up buying signals (attio-docs-22, attio-docs-24), suggesting the pieces exist, but there's no concrete documentation of an agent workflow specifically ingesting email/meeting signals to update deal stage/next-steps fields end-to-end. Missing for 10: explicit documented workflow/recipe connecting email or meeting transcript signals to automated deal-stage/next-steps updates via API or MCP, and independent/hands-on confirmation of this specific automation working.

   • [probe] “official MCP server documented at https://attio.com/mcp”
   • [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
   • [claimed-docs] “Search, update, and create with AI.”
   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Webhooks allow you to subscribe to changes that happen in Attio and then receive real-time HTTP requests to a chosen target URL to notify yo…”
   • [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
   • [claimed-docs] “An object to represent deals involving people & companies”
   • [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
   • [claimed-docs] “AI picks up buying signals, blockers, or requests during the call, not days later.”

   proof ↗⚑ flag

   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

Deals

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

   weight 2 · round to Attio
   Attio~partialclaimed5/10

   Attio's docs describe lists as a mechanism to 'aggregate records and model business processes' distinct from objects, implying that multiple lists (each potentially with its own stage/status field) can serve as separate pipelines for different products or motions, and deals is an optional, configurable object. However, there is no explicit documentation confirming per-list custom stage sets or multiple concurrent pipelines with distinct stages for different motions. Missing for 10: explicit docs on creating multiple pipelines with independent stage sets, UI screenshots or guides showing per-list stage configuration, and any customer/hands-on evidence of running distinct pipelines for different products.

   • [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
   • [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
   • [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
   • [claimed-docs] “Create the exact data model your business needs with custom objects.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Attio
   Attio✓fullclaimed7/10

   Attio ships a native Deal object for pipeline tracking (attio-docs-13,30,33), supports kanban board views alongside tables (attio-docs-34), and lets users customize fields/stages via custom objects and lists that model business processes (attio-docs-8,29,46). This directly matches the pipeline-with-customizable-stages story, though evidence never explicitly names 'drag-and-drop' interaction or shows independent hands-on confirmation. Missing for 10: explicit drag-and-drop UI documentation, independent/third-party hands-on review confirming the kanban interaction works as described.

   • [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
   • [claimed-docs] “An object to represent deals involving people & companies”
   • [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin”
   • [claimed-docs] “From kanbans to tables, visualize your data the way that works for you.”
   • [claimed-docs] “Objects can be used to model your domain entities, while lists can be used to aggregate them together and model business processes.”
   • [claimed-docs] “Customize fields to capture exactly what you need to track.”
   • [claimed-docs] “Create the exact data model your business needs with custom objects.”

   proof ↗⚑ flag

   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

Forecasting

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

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

   Attio's Deal object provides pipeline data (stage, value, close date) and its reporting engine supports custom visualizations/analytics, which could underpin revenue forecasting, but no evidence explicitly documents a forecasting feature, stage-probability weighting, or a forecast report type. Missing for 10: explicit probability-weighted forecast feature, documented forecast reports/dashboards, and any customer/independent evidence of forecasting use.

   • [claimed-docs] “The Deal object is available in every Attio workspace, but disabled by default. It can only be activated by a workspace admin, in the object…”
   • [claimed-docs] “Attio comes with two objects enabled by default, people and companies, and three optional objects: deal, user and workspace.”
   • [claimed-docs] “An object to represent deals involving people & companies”
   • [claimed-docs] “Attio's powerful engine allows you to find whichever insights you're looking for.”
   • [claimed-docs] “Analyze live data any way you like, from line charts and bar graphs to geospatial mapping.”
   • [claimed-docs] “Combine visualizations to instantly understand the full story and make better business decisions.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Attio—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location choices for Attio workspaces; the evidence pack covers API, objects, workflows, AI features, and MCP but nothing on data residency controls.

   ⚑ flag

   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

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

   weight 3 · round drawn
   Attio—none0/10

   No evidence in the pack addresses AI-training data usage, opt-out controls, or any privacy policy statement about model training on customer data; this is an applicable privacy-posture axis for an AI-native CRM but no supporting documentation exists in the evidence pack.

   ⚑ flag

   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

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Attio—none0/10

   No evidence pack items address data retention policies, export/deletion controls, or privacy/compliance settings for AI-native data handling; all citations concern API features, CRM data modeling, and workflow automation, not retention/deletion controls.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Attio—none0/10

   No evidence pack items mention telemetry, usage tracking, opt-out settings, or privacy controls of this kind; this is an applicable axis for a SaaS CRM platform but nothing documents it.

   ⚑ flag

   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

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

   Attio has an official MCP server (attio-docs-3, attio-probe-3) and a REST API supporting filtering/sorting, deal/company/history objects (attio-docs-1,2,6,29,30,16) that would let an agent pull open deals, history, and records; the AI platform page explicitly names 'create account briefs' as a capability (attio-docs-22) alongside call transcription/logging that could feed 'recent emails/interactions' context. Missing for 10: independent/hands-on confirmation that the MCP server actually returns email history or that account-brief generation works end-to-end in practice, and explicit documentation of email data access via the API.

   • [claimed-docs] “Manage Attio via AI. Connect Claude, ChatGPT or your AI tool of choice to search, update and manage your Attio workspace.”
   • [probe] “official MCP server documented at https://attio.com/mcp”
   • [claimed-docs] “Draft follow-ups, update records, schedule next steps, create account briefs. Instantly, not eventually.”
   • [claimed-docs] “Get instant visibility into the full history of every interaction.”
   • [claimed-docs] “An object to represent deals involving people & companies”
   • [claimed-docs] “This allows developers to build apps that read and write information to and from Attio workspaces. You can also subscribe to events in realt…”
   • [claimed-docs] “Some of our endpoints allow specifying `filter` or `sorts` objects as part of the request. These properties can help reduce the size of the …”

   proof ↗⚑ flag

   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

Reporting

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

   weight 3 · round to Attio
   Attio✓fullclaimed7/10

   Attio's native reporting platform lets users build live dashboards with multiple chart types (line, bar, geospatial) and combine visualizations for team collaboration, plus SQL query access for deeper analysis—directly enabling in-app reporting instead of spreadsheet exports. Missing for 10: no explicit pipeline/conversion-metric examples, no independent/hands-on corroboration of dashboard-building in practice.

   • [claimed-docs] “Attio's powerful engine allows you to find whichever insights you're looking for.”
   • [claimed-docs] “Analyze live data any way you like, from line charts and bar graphs to geospatial mapping.”
   • [claimed-docs] “Combine visualizations to instantly understand the full story and make better business decisions.”
   • [claimed-docs] “Work with your teammates to build th”
   • [claimed-docs] “Run SQL queries against your workspace data.”

   proof ↗⚑ flag

   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