HubSpot vs Salesforce Sales Cloud

Agent access

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

   weight 2 · round to Salesforce Sales Cloud
   HubSpot~partialprobed6/10

   HubSpot's docs explicitly state that agents can 'Fetch the complete documentation index at: https://developers.hubspot.com/docs/llms.txt' and that any doc page can be turned into markdown by appending .md (corroborated by real evidence sources that are themselves .md URLs, e.g. hubspot-docs-47, hubspot-docs-57). However, independent probes found the top-level https://developers.hubspot.com/llms.txt and https://developers.hubspot.com/docs.md both return 404, raising doubt about the accessibility/discoverability of the claimed agent-oriented entry points at the paths most agents would guess. Missing for 10: a probe confirming the specific /docs/llms.txt path actually resolves, and clearer top-level discoverability (root llms.txt) rather than only nested doc-page .md conversion.

   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.hubspot.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://developers.hubspot.com/docs.md”
   • [claimed-docs] “Retrieve detailed information about the account associated with the HubSpot portal.”

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

   HubSpot exposes a CLI (`npm install -g @hubspot/cli && hs init`) and a full REST API (contacts, custom objects, webhooks) plus a machine-readable OpenAPI spec, all of which can be scripted and run non-interactively in CI/automation pipelines. However, there is no explicit documentation or example showing CI/CD integration, headless CLI usage in pipelines, or automated testing workflows tailored to AI-native/agentic CI use. missing for 10: explicit CI/CD pipeline examples, documented headless/non-interactive CLI flags, and independent evidence of running HubSpot automation in a build pipeline.

   • [claimed-docs] “Install the HubSpot CLI globally / Authorize your HubSpot account / Start building”
   • [claimed-docs] “npm install -g @hubspot/cli && hs init”
   • [claimed-docs] “the contacts endpoints allow you to create and manage contact records in your HubSpot account, as well as sync contact data between HubSpot …”
   • [claimed-docs] “the webhooks journal API enables third-party integrators to subscribe to real-time events, retrieve historical event data, and manage snapsh…”
   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [probe] “official MCP server documented at https://developers.hubspot.com/ai-tools/mcp”

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

   Evidence only shows HubSpot exposing its own MCP servers (CRM MCP server, Developer MCP server) so external AI tools/agents can call HubSpot — this is HubSpot acting as the MCP server, not as a client that lets a user plug third-party MCP servers into HubSpot's own AI features (e.g., Breeze agents) to gain new tools. No evidence describes HubSpot's agents consuming or connecting to external MCP servers.

   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — conta…”
   • [claimed-docs] “The Developer MCP server enables your agentic development tools to interact with the HubSpot Developer Platform via the CLI.”
   • [claimed-docs] “This server is CLI-based and enables your agentic development software to interact with the HubSpot Developer Platform, helping you to quick…”
   • [probe] “official MCP server documented at https://developers.hubspot.com/ai-tools/mcp”
   • [claimed-docs] “Build demand, win deals, and serve your customers with a team of AI agents for marketing, sales, and customer service. Built on your CRM dat…”

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

   HubSpot documents two official MCP servers: a CRM MCP server giving MCP-compatible agents secure read/write access to CRM data (contacts, deals, engagements), and a Developer MCP server for agentic dev tools to interact with the HubSpot Developer Platform via CLI. This directly matches the story of connecting an agent via an official MCP server. Missing for 10: independent/hands-on third-party corroboration of the MCP server's real-world reliability and setup experience beyond first-party docs.

   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — conta…”
   • [claimed-docs] “The Developer MCP server enables your agentic development tools to interact with the HubSpot Developer Platform via the CLI.”
   • [claimed-docs] “This server is CLI-based and enables your agentic development software to interact with the HubSpot Developer Platform, helping you to quick…”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data”
   • [claimed-docs] “enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements…”
   • [claimed-docs] “The **HubSpot MCP server** enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — c…”
   • [claimed-docs] “The **Developer MCP server** enables your agentic development tools to interact with the HubSpot Developer Platform via the CLI.”
   • [probe] “official MCP server documented at https://developers.hubspot.com/ai-tools/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 drawn
   HubSpot✓fullclaimed8/10

   HubSpot documents an official CLI (`npm install -g @hubspot/cli && hs init`) for installing, authorizing, and building on the platform, and this CLI is further tied into an official Developer MCP server enabling agentic tools to interact with the HubSpot Developer Platform via the CLI — directly supporting AI-native/agentic workflows. Missing for 10: independent/hands-on developer corroboration of the CLI's robustness and no evidence of deeper agent-specific CLI features beyond scaffolding.

   • [claimed-docs] “Install the HubSpot CLI globally / Authorize your HubSpot account / Start building”
   • [claimed-docs] “npm install -g @hubspot/cli && hs init”
   • [claimed-docs] “Install the HubSpot CLI globally... Authorize your HubSpot account... Start building”
   • [claimed-docs] “The Developer MCP server enables your agentic development tools to interact with the HubSpot Developer Platform via the CLI.”
   • [claimed-docs] “This server is CLI-based and enables your agentic development software to interact with the HubSpot Developer Platform, helping you to quick…”
   • [claimed-docs] “The **Developer MCP server** enables your agentic development tools to interact with the HubSpot Developer Platform via the CLI.”

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

   HubSpot publishes an extensive, versioned public REST API (CRM objects, contacts, custom objects, webhooks, account info) with CLI tooling, OpenAPI specs inline per endpoint, and a documented deprecation/versioning policy, all clearly aimed at programmatic/agentic access (hubspot-docs-2,3,4,31,57,63, hubspot-supp-api-versioning, hubspot-supp-deprecation-policy, hubspot-supp-openapi-spec). Probes hitting guessed root-level paths (llms.txt, openapi.json) 404'd, but the actual docs confirm an agent-readable llms.txt under /docs and inline OpenAPI specs, so this is a minor path-discovery issue rather than a real gap. Missing for 10: independent/third-party corroboration of API robustness and no confirmation the root-level llms.txt/openapi.json discovery paths work as some agents might expect.

   • [claimed-docs] “the contacts endpoints allow you to create and manage contact records in your HubSpot account, as well as sync contact data between HubSpot …”
   • [claimed-docs] “You can retrieve custom object records individually or in batches.”
   • [claimed-docs] “the webhooks journal API enables third-party integrators to subscribe to real-time events, retrieve historical event data, and manage snapsh…”
   • [claimed-docs] “To create one contact, make a `POST` request to `/crm/v3/objects/contacts`.”
   • [claimed-docs] “Retrieve detailed information about the account associated with the HubSpot portal.”
   • [claimed-docs] “Retrieve detailed information about the account associated with the HubSpot portal. This endpoint provides insights into the account type, t…”
   • [claimed-docs] “Docs, "2026-09 API reference": "The 2026-09 APIs use a date-based versioning scheme (e.g., /crm/2026-09/)... This versioning model gives Hub…”
   • [claimed-docs] “Docs, "Sunsetted and deprecated APIs": a maintained table of sunsetted APIs with dates and migration targets, plus "Deprecated APIs... HubSp…”
   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.hubspot.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://developers.hubspot.com/docs.md”

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

   The evidence pack documents HubSpot's general API, CLI, and MCP server (with 'secure read and write access') but contains no mention of scoped/least-privilege API keys, OAuth scopes, or granular permission tokens specifically issuable to an AI agent. 'Granular reporting permissions' (hubspot-docs-51/65) refers to dashboard viewing, not API credential scoping.

   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data”
   • [claimed-docs] “Control who sees what with granular reporting permissions”
   • [claimed-docs] “Build custom reporting dashboards for every team... Control who sees what with granular reporting permissions”

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

   The evidence pack documents HubSpot's REST APIs, an OpenAPI-spec-per-endpoint, a CLI (@hubspot/cli), and MCP servers, but nowhere mentions official client SDKs/libraries (e.g., Node.js, Python, PHP, Ruby SDKs) that an AI-native developer would build against. Missing for 10: any documentation of official SDK packages, language coverage, or SDK release/versioning cadence.

   • [claimed-docs] “Install the HubSpot CLI globally / Authorize your HubSpot account / Start building”
   • [claimed-docs] “npm install -g @hubspot/cli && hs init”
   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [claimed-docs] “Docs, "2026-09 API reference": "The 2026-09 APIs use a date-based versioning scheme (e.g., /crm/2026-09/)... This versioning model gives Hub…”

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

   HubSpot documents a dedicated webhooks journal API allowing third-party integrators to subscribe to real-time events, retrieve historical event data, and manage CRM object snapshots, directly matching the story. Missing for 10: independent/hands-on corroboration of webhook subscription reliability and no explicit mention of AI-agent-specific webhook consumption patterns.

   • [claimed-docs] “the webhooks journal API enables third-party integrators to subscribe to real-time events, retrieve historical event data, and manage snapsh…”

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

   HubSpot's Breeze AI features (docs-35/50: describe a report in plain language and it builds it from your data; docs-14/22/23: prospecting agent watches accounts for buying signals and drafts follow-ups; docs-56: AI agents built on CRM data giving contextual insights) directly deliver AI-generated insights/suggestions surfaced inside the product. Missing for 10: independent/hands-on validation of insight quality (only vendor docs, no user reports confirming these AI features work well), and detail on breadth/accuracy of the suggestions across all data types.

   • [claimed-docs] “describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “with Breeze Assistant, describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Approve automatic CRM updates and follow-up drafts after every meeting”
   • [claimed-docs] “Build demand, win deals, and serve your customers with a team of AI agents for marketing, sales, and customer service. Built on your CRM dat…”

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

   HubSpot ships native Workflows automation that runs processes autonomously on CRM triggers, plus AI agents (e.g., the Prospecting agent) explicitly described as watching accounts for signals and reaching out automatically, and smart deal progression handling next steps without user action — all clearly background/autonomous behaviors. Webhooks and the CRM API further support event-driven automation an AI-native user could wire up. Missing for 10: independent/hands-on verification that these agents run reliably unattended over time, and deeper docs on scheduling/trigger configuration for developer-built autonomous flows.

   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “Create workflows”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Approve automatic CRM updates and follow-up drafts after every meeting”
   • [claimed-docs] “the webhooks journal API enables third-party integrators to subscribe to real-time events, retrieve historical event data, and manage snapsh…”
   • [claimed-docs] “Build demand, win deals, and serve your customers with a team of AI agents for marketing, sales, and customer service. Built on your CRM dat…”

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

   HubSpot documents built-in AI agents (Breeze Assistant, Prospecting agent, campaign-planning agent) that can autonomously watch accounts, draft follow-ups, build reports from plain-language requests, and generate content — a clear built-in delegate-to-AI-assistant capability (hubspot-docs-14, 22, 23, 35, 50, 56). However, all evidence is vendor-authored marketing/docs pages with no independent or hands-on corroboration of these agents actually performing delegated tasks reliably. Missing for 10: independent/hands-on verification of the AI assistant executing delegated tasks, and detail on scope/limits of autonomy.

   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Approve automatic CRM updates and follow-up drafts after every meeting”
   • [claimed-docs] “describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “with Breeze Assistant, describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “Build demand, win deals, and serve your customers with a team of AI agents for marketing, sales, and customer service. Built on your CRM dat…”
   • [claimed-docs] “Create blog posts, social content, and landing pages in your brand voice”

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

   HubSpot documents natural-language interaction in specific areas — Breeze Assistant lets users 'describe the report you need in plain language' to build dashboards, and Breeze AI agents handle prospecting/deal-progression tasks with natural-language-driven automation. The official MCP server additionally lets any MCP-compatible AI agent read/write CRM data, enabling natural-language-driven operation via external agents. However, this is scattered across specific features (reporting, prospecting) rather than a unified natural-language command layer for the whole CRM, and there's no first-party chat/command interface spanning all core CRM operations. Missing for 10: a comprehensive in-product NL command interface covering most CRM actions (not just reporting/prospecting), and independent/hands-on evidence validating these NL features work as claimed.

   • [claimed-docs] “describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “with Breeze Assistant, describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “Build demand, win deals, and serve your customers with a team of AI agents for marketing, sales, and customer service. Built on your CRM dat…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Approve automatic CRM updates and follow-up drafts after every meeting”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data”
   • [claimed-docs] “enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements…”
   • [claimed-docs] “The **HubSpot MCP server** enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — c…”

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

   HubSpot publishes machine-readable API reference pages (OpenAPI specs, curl/code examples like the contacts POST endpoint, and agent-readable .md/llms.txt paths per hubspot-supp-openapi-spec, hubspot-docs-31, hubspot-docs-57), showing a structured API reference exists. However, there's no evidence of an interactive 'try it' console or runnable execution within the docs, and probes for llms.txt/openapi.json at expected root paths returned 404s, suggesting the interactive/agent-discoverable surface is inconsistent or non-standard. Missing for 10: explicit interactive 'run this call' sandbox UI, confirmation that root-level llms.txt/openapi.json resolve, and independent corroboration of hands-on interactivity.

   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [claimed-docs] “Retrieve detailed information about the account associated with the HubSpot portal.”
   • [claimed-docs] “To create one contact, make a `POST` request to `/crm/v3/objects/contacts`.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.hubspot.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.hubspot.com/openapi.json, https://developers.hubspot.com/swagger.json, https://de…”

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

   First-party docs show each API reference page embeds a machine-readable OpenAPI 3.0.1 spec (e.g., specs/2026-09/account-account-info-v2026-09.json) and an agent-readable index at /docs/llms.txt, confirming a real OpenAPI-based spec exists per endpoint. However, independent probes for a single top-level downloadable spec (openapi.json, swagger.json, llms.txt at root) all returned 404, suggesting there is no one-shot full-API spec download — only per-endpoint fragments discoverable via docs navigation. Missing for 10: a consolidated single-file OpenAPI document confirmed downloadable, and independent/community verification of successfully fetching it.

   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.hubspot.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://developers.hubspot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.hubspot.com/openapi.json, https://developers.hubspot.com/swagger.json, https://de…”

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

   HubSpot explicitly documents the ability to create up to 10 free test/sandbox accounts to test apps and integrations without affecting real production data, directly matching the story. Missing for 10: no independent/hands-on confirmation of sandbox fidelity or limitations, and no detail on how closely sandbox mirrors production data/schema.

   • [claimed-docs] “You can create up to 10 test accounts to test apps and integrations without affecting any real HubSpot data.”

   proof ↗⚑ 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 to HubSpot
   HubSpot✓fullprobed8/10

   HubSpot documents a date-based API versioning scheme (e.g. /crm/2026-09/) with predictable release cadence and continued support of prior versions until end-of-life, plus a maintained sunsetted/deprecated APIs table with migration targets and changelog-based advance notice, and machine-readable OpenAPI specs per endpoint. Some probes (llms.txt, docs.md, generic openapi.json) 404'd, suggesting the agent-readable surface isn't as universally exposed as claimed. Missing for 10: independent/community corroboration of the deprecation policy actually being honored in practice, and confirmation that the llms.txt/agent-friendly endpoints work as documented rather than 404ing.

   • [claimed-docs] “Docs, "2026-09 API reference": "The 2026-09 APIs use a date-based versioning scheme (e.g., /crm/2026-09/)... This versioning model gives Hub…”
   • [claimed-docs] “Docs, "Sunsetted and deprecated APIs": a maintained table of sunsetted APIs with dates and migration targets, plus "Deprecated APIs... HubSp…”
   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.hubspot.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://developers.hubspot.com/docs.md”

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

   HubSpot documents bulk-oriented capabilities: batch retrieval of custom object records, bulk import of multiple objects (companies, deals, activities) with associations, and automatic/manual deduplication across large record sets, plus workflows to automate processes at scale. However, the evidence pack doesn't show explicit batch create/update/delete endpoints for core objects like contacts or deals (only single-record POST is shown), nor any AI-native bulk operation via MCP/agent tooling beyond single-item CRUD examples. Missing for 10: explicit batch API documentation for contacts/deals/tickets, evidence of MCP or AI agent performing multi-item bulk actions, and independent confirmation of bulk operation reliability at scale.

   • [claimed-docs] “You can retrieve custom object records individually or in batches.”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects.”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
   • [claimed-docs] “Record IDs can also be used to manually deduplicate contacts, companies, deals, tickets, products, admin-activated objects (e.g., appointmen…”
   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements…”

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

   HubSpot's Workflows feature explicitly lets users create automated rules that trigger actions on events (contact property changes, form submissions, deal stage changes, etc.), and this is compounded by webhook subscriptions for real-time event-driven automation via API, plus AI agents (prospecting agent, deal progression) that act automatically on signals. missing for 10: no explicit documentation tying natural-language/AI-native rule authoring directly to workflow triggers, and no independent/hands-on verification of workflow automation depth beyond vendor docs.

   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “Create workflows”
   • [claimed-docs] “the webhooks journal API enables third-party integrators to subscribe to real-time events, retrieve historical event data, and manage snapsh…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Approve automatic CRM updates and follow-up drafts after every meeting”

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

   HubSpot's native Workflows feature ('Create workflows in HubSpot to automate your processes') supports building automated, recurring business processes, which is the closest evidence to scheduled/recurring jobs, but the evidence pack gives no detail on cron-like scheduling, re-enrollment intervals, or how an AI-native/agentic user would programmatically create or manage such recurring workflows via API/MCP. Missing for 10: documentation on recurring/scheduled triggers within Workflows, API or MCP-server support for creating/managing workflows programmatically, and independent confirmation of AI-driven workflow automation.

   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “Create workflows”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — conta…”

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

   Evidence shows workflow creation (hubspot-docs-12/45) and API-level date-based versioning (hubspot-supp-api-versioning) but nothing about version history, review, or rollback of built automations/workflows themselves.

   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “Create workflows”
   • [claimed-docs] “Docs, "2026-09 API reference": "The 2026-09 APIs use a date-based versioning scheme (e.g., /crm/2026-09/)... This versioning model gives Hub…”

   proof ↗⚑ 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 Salesforce Sales Cloud
   HubSpot~partialclaimed3/10

   HubSpot's documentation confirms a general-purpose workflow automation engine ('Create workflows in HubSpot to automate your processes') that is the underlying mechanism used for lead routing, but the evidence pack contains no explicit mention of assignment rules, lead routing, or round-robin distribution features. Missing for 10: explicit documentation of assignment rules, round-robin lead distribution, or lead-routing-specific workflow actions, and any independent/hands-on confirmation these work as described.

   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “Create workflows”

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

   HubSpot's Workflows product (hubspot-docs-12/45) is explicitly documented as a trigger-based automation builder, and complementary docs confirm the CRM record model (contacts, custom objects, deals) that workflows act on, task creation, and notification/email capabilities (sequences, connected inbox) that workflows commonly trigger. Missing for 10: no deep documentation excerpt showing the specific workflow trigger/action UI (task creation, internal notifications) beyond the generic 'create workflows' page, and no independent hands-on review confirming reliability at scale.

   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “Create workflows”
   • [claimed-docs] “the contacts endpoints allow you to create and manage contact records in your HubSpot account, as well as sync contact data between HubSpot …”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”
   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails, and…”
   • [claimed-docs] “With the sequences tool, you can send a series of targeted, timed”

   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 HubSpot
   HubSpot~partialprobed5/10

   HubSpot's REST API supports creating contact records (POST /crm/v3/objects/contacts) and companies/custom objects can be created and updated via the same object APIs, and the official MCP server explicitly grants 'read and write access to your HubSpot CRM data — contacts, deals, engagements, and more' to any MCP-compatible agent, so the create+enrich portions of the story are documented. However, there is no evidence of an owner-assignment field/endpoint being called out, nor any end-to-end example showing an agent orchestrating create→enrich→assign-owner in one flow. Missing for 10: explicit owner-assignment API/MCP action, a documented end-to-end lead-enrichment workflow example, and independent/hands-on confirmation of the MCP server performing writes successfully.

   • [claimed-docs] “To create one contact, make a `POST` request to `/crm/v3/objects/contacts`.”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — conta…”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data”
   • [claimed-docs] “enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements…”
   • [claimed-docs] “The contacts endpoints allow you to create and manage contact records in your HubSpot account, as well as sync contact data between HubSpot …”
   • [claimed-docs] “HubSpot custom objects allow organizations to represent and organize data based on unique business requirements. Create and update custom ob…”
   • [claimed-docs] “use the objects API to create and manage the custom object’s records”
   • [probe] “official MCP server documented at https://developers.hubspot.com/ai-tools/mcp”

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

   The evidence pack covers CRM data storage, deduplication, import/export, workflows, and AI agents for prospecting/reporting, but contains no mention of automatic enrichment of contact/company records with third-party firmographic or contact data. Absence of evidence for this applicable CRM capability yields 'none'.

   ⚑ 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 to HubSpot
   HubSpot✓fullclaimed7/10

   HubSpot docs confirm automatic deduplication (by email for contacts, domain for companies) plus manual merge via record IDs across contacts, companies, deals, tickets and other objects, directly addressing duplicate detection and merging. Missing for 10: explicit documentation confirming no data loss during merge (e.g., how conflicting field values are preserved) and independent/hands-on confirmation of merge behavior beyond vendor docs.

   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
   • [claimed-docs] “Record IDs can also be used to manually deduplicate contacts, companies, deals, tickets, products, admin-activated objects (e.g., appointmen…”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names. Record IDs can also be used to manually…”
   • [claimed-docs] “Deduplicate records in HubSpot”

   proof ↗⚑ 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 HubSpot
   HubSpot~partialclaimed6/10

   HubSpot's docs confirm contacts and companies exist as CRM records with dedup by domain (companies) and email (contacts), the ability to import and associate records across objects (contacts, companies, deals), and email/replies being logged to the CRM — indicating activity capture on records. However, no direct evidence describes a company-record API or a rendered 'activity timeline' UI feature explicitly, only inferred from email-logging and engagement mentions in MCP docs. Missing for 10: explicit documentation of the company object API/endpoints, and explicit description of a unified activity timeline UI on contact/company records.

   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails, and…”
   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails”
   • [claimed-docs] “To create one contact, make a `POST` request to `/crm/v3/objects/contacts`.”
   • [claimed-docs] “enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements…”

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

   The evidence pack lacks any documentation of ops-user self-service custom property/field creation on CRM records or of building filtered, sorted, shared list/table views without going through a developer or admin project — coverage is limited to custom objects via the developer API, reporting dashboards, and permissions, none of which address this specific ops workflow.

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

   HubSpot's docs explicitly cover custom objects: creating/updating records via the custom objects API and retrieving them individually or in batch, letting developers extend beyond contacts/companies/deals. Evidence also shows import/dedup/association support extending to custom objects. Missing for 10: explicit documentation of defining custom fields/properties and relationship/association types on custom objects, and independent hands-on developer corroboration beyond HubSpot's own docs.

   • [claimed-docs] “HubSpot custom objects allow organizations to represent and organize data based on unique business requirements. Create and update custom ob…”
   • [claimed-docs] “You can retrieve custom object records individually or in batches.”
   • [claimed-docs] “use the objects API to create and manage the custom object’s records”
   • [claimed-docs] “Create and update custom object records with the custom objects API.”
   • [claimed-docs] “Record IDs can also be used to manually deduplicate contacts, companies, deals, tickets, products, admin-activated objects (e.g., appointmen…”

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

   The evidence pack covers email inbox connection, contacts/deals APIs, imports, and reporting, but contains no mention of calendar sync or meetings appearing on contact/deal timelines. This is a plausible and common CRM capability, but no supporting evidence exists in the pack.

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

   HubSpot docs confirm connecting an individual work email (Gmail/Outlook) to log replies and send emails from the CRM, and automatic deduplication by email address helps route logged emails to the right contact records. However, evidence doesn't explicitly confirm true two-way sync behavior details (e.g., sync settings, filtering, conflict handling) or explicitly name Gmail/Outlook as the connected providers. missing for 10: explicit mention of Gmail/Outlook as supported providers, details on two-way sync configuration/filters, and independent/hands-on verification of reliable auto-logging to correct records.

   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails, and…”
   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails”
   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM”
   • [claimed-docs] “Connect an individual work email”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names. Record IDs can also be used to manually…”

   proof ↗⚑ 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 HubSpot
   HubSpot✓fullclaimed8/10

   HubSpot documents connecting an inbox to send one-to-one emails and sequence emails directly from the CRM (hubspot-docs-13/21/46/54), plus a dedicated sequences tool for sending targeted, timed multi-step outreach (hubspot-docs-37/44/52) and workflow automation for broader processes (hubspot-docs-12/45), all native to the CRM ops experience. missing for 10: no hands-on/independent verification of the sequences UX or deliverability, and no detail on template management specifics.

   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails, and…”
   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails”
   • [claimed-docs] “With the sequences tool, you can send a series of targeted, timed”
   • [claimed-docs] “With the sequences tool, you can send a series of targeted, timed [email temp”
   • [claimed-docs] “Create and edit sequences”
   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”

   proof ↗⚑ 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 HubSpot
   HubSpot~partialclaimed5/10

   Evidence shows CRUD and batch operations for contacts/custom objects, plus a webhooks journal API for real-time and historical event subscription (a change-detection mechanism), supporting bidirectional sync at scale. However, no evidence cites documented rate limits, and there's no explicit mention of 'upsert' semantics (e.g., idProperty-based upsert) in the API docs provided. Missing for 10: documented rate-limit numbers/headers, explicit upsert endpoint documentation, and independent/hands-on confirmation of scale performance.

   • [claimed-docs] “You can retrieve custom object records individually or in batches.”
   • [claimed-docs] “the webhooks journal API enables third-party integrators to subscribe to real-time events, retrieve historical event data, and manage snapsh…”
   • [claimed-docs] “The contacts endpoints allow you to create and manage contact records in your HubSpot account, as well as sync contact data between HubSpot …”
   • [claimed-docs] “HubSpot custom objects allow organizations to represent and organize data based on unique business requirements. Create and update custom ob…”
   • [claimed-docs] “use the objects API to create and manage the custom object’s records”

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

   The evidence pack covers HubSpot's CRM APIs, CLI, MCP servers, import tools, and reporting, but contains no mention of an app marketplace or prebuilt one-click integrations for Slack, support desks, marketing tools, or data warehouses — the specific capability this story asks about. Since this is a plausible and expected capability for a CRM platform, absence of evidence yields 'none' rather than 'na'.

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

   HubSpot documents import tools for multiple objects (companies, deals, activities, associations), self-service transfer/audit-and-sync for new customers, and automatic/manual deduplication using email/domain or record IDs, which together support migrating records and relationships from another CRM. However, evidence does not confirm preservation of 'owners' (rep/user assignment mapping) during migration, nor explicit historical activity/timeline preservation beyond basic activities import, and there's no independent/hands-on account confirming migration fidelity. missing for 10: evidence of owner/user mapping during import, confirmation of full historical timeline/audit trail preservation, and independent verification of migration outcomes.

   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”
   • [claimed-docs] “If you're new to HubSpot and want to transfer your existing CRM data to HubSpot's CRM, you can use self-service transfer to audit and sync y…”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
   • [claimed-docs] “Record IDs can also be used to manually deduplicate contacts, companies, deals, tickets, products, admin-activated objects (e.g., appointmen…”
   • [claimed-docs] “you can use self-service transfer to audit and sync your data”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects.”

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

   HubSpot's docs confirm a bulk import tool for contacts/deals/companies with multi-object support and association mapping, plus automatic and manual deduplication to prevent duplicate rows, which addresses the core of the story. However, there is no documented evidence of explicit field-mapping validation UI details, error/row-level reporting on failed imports, or guarantees against silently dropped rows during import. Missing for 10: explicit field-mapping/validation UI documentation, error-handling/row-rejection reporting during import, and independent/hands-on evidence confirming no silent row loss.

   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”
   • [claimed-docs] “If you're new to HubSpot and want to transfer your existing CRM data to HubSpot's CRM, you can use self-service transfer to audit and sync y…”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
   • [claimed-docs] “Record IDs can also be used to manually deduplicate contacts, companies, deals, tickets, products, admin-activated objects (e.g., appointmen…”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects.”
   • [claimed-docs] “Import records for multiple objects”

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

   HubSpot documents a self-service path — free CRM signup with no expiration, self-service data transfer/import for multiple objects, automatic deduplication, and workflow creation — all achievable without a partner (hubspot-docs-7,9,25,27,29,8,10,12). However, no evidence quantifies time-to-value or confirms a real founder can reach a 'working pipeline with real data' inside one hour; community commentary only addresses marketing/product perception, not onboarding speed. Missing for 10: a documented or independent time-to-pipeline benchmark, and hands-on confirmation that import+dedup+workflow setup is fast enough for non-technical founders without support.

   • [claimed-docs] “HubSpot's free CRM unifies all your customer data on one platform, with AI that makes it easy to understand. And unlike a free trial, it's 1…”
   • [claimed-docs] “If you're new to HubSpot and want to transfer your existing CRM data to HubSpot's CRM, you can use self-service transfer to audit and sync y…”
   • [claimed-docs] “Your data deserves better than spreadsheets. HubSpot's free CRM unifies all your customer data on one platform, with AI that makes it easy t…”
   • [claimed-docs] “you can use self-service transfer to audit and sync your data”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”
   • [claimed-docs] “HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “When you’re ready for more, upgrade to get premium CRM functionality that builds on what you already have. No starting over, no data migrati…”

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

   HubSpot exposes extensive CRUD APIs (contacts, custom objects, workflows, imports, dedup) with OpenAPI specs and versioning, and even an MCP server for CRM read/write, suggesting broad API parity with UI actions. However, many UI-surfaced features (AI-generated reports via Breeze Assistant, prospecting agent, sequences UI, plain-language report builder) are not shown to have direct API equivalents, and probes show no llms.txt/docs.md/openapi.json at the root, indicating some agent-discovery gaps. missing for 10: API coverage confirmation for AI/reporting/sequence features shown only as UI capabilities, independent verification of full UI-API parity, working llms.txt/root OpenAPI discovery endpoints.

   • [claimed-docs] “the contacts endpoints allow you to create and manage contact records in your HubSpot account, as well as sync contact data between HubSpot …”
   • [claimed-docs] “You can retrieve custom object records individually or in batches.”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”
   • [claimed-docs] “Create workflows in HubSpot to automate your processes.”
   • [claimed-docs] “To create one contact, make a `POST` request to `/crm/v3/objects/contacts`.”
   • [claimed-docs] “use the objects API to create and manage the custom object’s records”
   • [claimed-docs] “Every endpoint reference page publishes its machine-readable spec inline ("## OpenAPI ... specs/2026-09/account-account-info-v2026-09.json G…”
   • [claimed-docs] “Docs, "2026-09 API reference": "The 2026-09 APIs use a date-based versioning scheme (e.g., /crm/2026-09/)... This versioning model gives Hub…”
   • [claimed-docs] “describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “with Breeze Assistant, describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.hubspot.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://developers.hubspot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.hubspot.com/openapi.json, https://developers.hubspot.com/swagger.json, https://de…”
   • [claimed-docs] “enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements…”

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

   HubSpot's docs mention APIs to retrieve contacts and custom object records (e.g., GET requests) which could be used to pull data out, but there is no explicit documentation of a full data-export feature, bulk export tool, or guarantee of open/portable formats (e.g., CSV/JSON export for all objects) — the cited import/export docs focus almost entirely on importing, not exporting. Missing for 10: dedicated 'export all data' feature docs, explicit open-format (CSV/JSON) export guarantees, and evidence of exporting non-CRM objects (workflows, sequences, reports) for a full data migration/exit.

   • [claimed-docs] “To create one contact, make a `POST` request to `/crm/v3/objects/contacts`.”
   • [claimed-docs] “You can retrieve custom object records individually or in batches.”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects.”
   • [claimed-docs] “Import records for multiple objects to add or update data across different objects. You can import records such as companies or deals, as we…”

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

   HubSpot ships both a native AI capability ('smart deal progression keeps deals moving after every call, with next steps handled for them' and 'Approve automatic CRM updates and follow-up drafts after every meeting') and an official MCP server giving 'any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements, and more,' directly matching the story of an agent updating deal stages/next steps from email and meeting signals via API or MCP. Missing for 10: explicit deals-object API endpoint documentation (evidence only details contacts/custom-object endpoints), and independent hands-on confirmation that MCP-driven deal-stage updates work as advertised in practice.

   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — conta…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Prospecting agent watches accounts for signals that they're ready to buy and reaches out automatically, while smart deal progression keeps d…”
   • [claimed-docs] “Approve automatic CRM updates and follow-up drafts after every meeting”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data”
   • [probe] “official MCP server documented at https://developers.hubspot.com/ai-tools/mcp”

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

   The evidence pack contains nothing about HubSpot's deal/ticket pipeline configuration, multiple pipelines, or custom stage sets — it covers CRM objects, MCP servers, imports, dedup, workflows, and reporting but never pipeline-management features. Since this axis clearly applies to a CRM/ops product, absence of evidence yields 'none'.

   ⚑ 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 Salesforce Sales Cloud
   HubSpot—none0/10

   The evidence pack contains no mention of a visual deal pipeline, customizable stages, or drag-and-drop functionality anywhere in the docs, community, or probe items; only generic CRM/AI deal-progression references (e.g., hubspot-docs-14, hubspot-docs-22) exist without describing the pipeline UI itself. Missing for 10: explicit documentation of the visual pipeline board, stage customization, and drag-and-drop deal movement.

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

   The evidence pack shows generic sales reporting/dashboards (pre-built reports, custom dashboards, deal-related analytics) but nothing documents a dedicated pipeline forecasting feature that combines deal value, stage probability, and close dates into a revenue forecast. Without that specific capability being evidenced, this applicable CRM axis is unsupported.

   • [claimed-docs] “dozens of free pre-built sales reports that come standard with HubSpot’s sales reporting software”
   • [claimed-docs] “Choose from dozens of pre-built reports or customize your own”
   • [claimed-docs] “Build marketing, sales, revenue, and service analytics reports with filters and chart types to see exactly what's happening across your busi…”
   • [claimed-docs] “Monitor your team’s sales activities and unlock additional rep performance with deep coaching insights”

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

   The only relevant evidence is that HubSpot's account API can report a data hosting location, but there is no evidence a user can choose or select their storage region for compliance/residency purposes.

   • [claimed-docs] “Retrieve detailed information about the account associated with the HubSpot portal. This endpoint provides insights into the account type, t…”

   proof ↗⚑ 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
   HubSpot—none0/10

   No evidence in the pack addresses AI-training data opt-out or any privacy control preventing customer data from being used to train AI models; the evidence covers CRM features, APIs, MCP servers, and reporting but nothing about AI-training consent/data usage controls.

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

   No evidence pack items address data retention policies, deletion controls, GDPR/CCPA data deletion tools, or configurable retention settings for AI-native usage; nothing describes how a user can delete or control retention of data used by HubSpot's AI features or CRM data generally.

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

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings for HubSpot or its AI/CLI/MCP tools; nothing about privacy controls, data collection disclosures, or opt-out mechanisms is documented. missing for 10: any mention of telemetry collection, opt-out settings, or privacy controls for AI features/CLI/MCP usage.

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

   HubSpot's official MCP server explicitly grants read access to contacts, deals, and engagements, and its CRM APIs (contacts, custom objects, account info) plus connected-email logging supply the underlying data (open deals, emails, history) needed for such a brief; this directly supports an AI-native agent pulling account context via MCP or API before a meeting. However, there's no documented end-to-end 'account brief' workflow or example, no explicit deals/engagements API doc cited, and no independent/hands-on evidence the MCP server actually performs this compilation reliably. Missing for 10: a demonstrated brief-generation example, explicit deals/engagements endpoint docs, and third-party corroboration of MCP data-pull quality.

   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — conta…”
   • [claimed-docs] “The HubSpot MCP server enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data”
   • [claimed-docs] “enables you to give any MCP-compatible AI tool or agent secure read and write access to your HubSpot CRM data — contacts, deals, engagements…”
   • [claimed-docs] “the contacts endpoints allow you to create and manage contact records in your HubSpot account, as well as sync contact data between HubSpot …”
   • [claimed-docs] “Connect an individual work email to HubSpot to send one-to-one emails from the CRM, log email replies to the CRM, send sequences emails, and…”
   • [claimed-docs] “Retrieve detailed information about the account associated with the HubSpot portal.”
   • [probe] “official MCP server documented at https://developers.hubspot.com/ai-tools/mcp”

   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 HubSpot
   HubSpot✓fullclaimed9/10

   HubSpot's reporting-dashboards product page directly supports this story: custom dashboards, pre-built and customizable reports across marketing/sales/revenue/service, AI-assisted report building from plain language, and role-based views/permissions, all built natively on CRM pipeline/activity/conversion data without spreadsheet export. missing for 10: independent hands-on corroboration or case study demonstrating actual dashboard-building workflow beyond vendor docs.

   • [claimed-docs] “combine multiple reports to help every team member view the data most relevant to their role”
   • [claimed-docs] “describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “Build custom reporting dashboards for every team”
   • [claimed-docs] “Build marketing, sales, revenue, and service analytics reports with filters and chart types to see exactly what's happening across your busi…”
   • [claimed-docs] “with Breeze Assistant, describe the report you need in plain language, and HubSpot will build it from your actual data.”
   • [claimed-docs] “Control who sees what with granular reporting permissions”
   • [claimed-docs] “Build custom reporting dashboards for every team... Control who sees what with granular reporting permissions”
   • [claimed-docs] “View marketing, sales, revenue, and service data in one place”
   • [claimed-docs] “dozens of free pre-built sales reports that come standard with HubSpot’s sales reporting software”
   • [claimed-docs] “Choose from dozens of pre-built reports or customize your own”
   • [claimed-docs] “Monitor your team’s sales activities and unlock additional rep performance with deep coaching insights”

   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