|
GTM stack intelligence, enriched.
|
|
Parker Harris, Salesforce’s co-founder, told customers this quarter to stop logging into Salesforce and use Slack instead. Separately, Anthropic shipped a native HubSpot connector inside Claude. Neither company referenced the other. They both drew the same conclusion.
There’s also a hard HubSpot deadline this Thursday that I’d wager most teams haven’t spotted yet. Let’s start there.
|
|
|
|
⚠ Time-sensitive · May 22 deadline
|
HubSpot — Segments Intro and Legacy AI Suggestions Retiring May 22
The Segments Intro tab and legacy AI Segment Suggestions are disappearing on Thursday, May 22. The Intro page, which gave you the AI-generated overview and aggregate recommendations across your segments, is gone entirely. Individual segments are unaffected, and AI-powered filters are moving into the segment builder itself on all paid tiers, but the aggregated insight view doesn’t survive the migration.
If your team has built QBR decks, reporting templates, or dashboards that pull from that Segments Intro view, those break Thursday. Same goes for any workflow leaning on legacy AI Segment Suggestions for audience recommendations. The fix is straightforward: before Thursday, document what you actually pull from that view, then update any templates to point at segment-level data instead. The underlying AI capability isn’t gone; the surface it lived on is.
HubSpot didn’t lead with this in the Spring announcement. It was in the changelog.
Source: knowledge.hubspot.com/segments/segments-overview
|
|
|
|
GTM Watch · Salesforce Summer ’26
|
Salesforce — Slack Is Now the Default Interface for New Customers
Starting with the Summer ’26 release (GA June 15), Salesforce will provision Slack automatically for all new customers: meaning Slack’s AI functionality is connected directly to your CRM data on Day 1. That’s the product news, but there was a larger signal indicating where the industry is headed. Parker Harris, the co-founder who built the original Salesforce UI, told customers to stop logging in. Combine this with comments made by Marc Benioff last month and it begins to feel less like a bold proclamation of a future headerless CRM and more like a product adoption directive to use Salesforce as it is now intended.
Multi-Agent Orchestration also goes GA in June: Agentforce agents can now coordinate as a network, with a coordinator agent delegating to specialist agents across a full workflow. Slackbot ships as an MCP client with access to 2,600+ apps and Agentforce Exchange tools. Taken together these announcements signal an architectural bet on where the CRM interaction layer is headed (pun intended).
If you’re building on Salesforce, the most pressing operational question is whether your Agentforce implementation should be a coordinator-plus-specialists architecture rather than a single-agent design. That decision compounds: the more workflows you build on top of it, the harder it is to revisit.
Source: salesforce.com/news/stories/summer-2026-product-release-announcement
|
|
The feature news is worth your attention. The pattern connecting it to the next section may be worth more.
|
|
|
|
AI for RevOps · Anthropic
|
Anthropic — Claude for Small Business Ships a Native HubSpot Connector
On May 13, Anthropic launched Claude for Small Business: 15 agentic workflows ready to run, with native connectors to HubSpot, QuickBooks, PayPal, Canva, DocuSign, Google Workspace, Microsoft 365, and Slack. The HubSpot connector handles lead triage, customer pulse, and campaign attribution, running directly from live CRM context. There is minimal custom build required.
The “Small Business” label is doing some heavy lifting in an underselling direction. This is the first time Anthropic has shipped a production-grade, first-party integration into a major CRM. The 15 workflows act as references for Claude, showing exactly how it reasons over live CRM data and structures agentic output. For RevOps teams evaluating Claude API builds, this is the fastest path to understanding what a real deployment looks like and getting a sneak-peak at a reference architecture before scoping custom work.
Want to put it to use? Pull the HubSpot lead triage workflow as a working example even if your org isn’t the target SMB customer. The logic is still transferable to Enterprise Claude deployments and is a faster starting point than building from scratch.
Source: anthropic.com/news/claude-for-small-business
|
|
The rest of the week, in brief:
|
|
|
|
Anthropic / OpenAI: For the first time, Anthropic surpassed OpenAI in business adoption. April survey data puts Anthropic at 34.4% (+3.8%) and OpenAI at 32.3% (-2.9%). Anthropic entered hockeystick territory, quadrupling its business share over the past year; OpenAI gained 0.3%. If you’re evaluating AI vendor strategy for GTM tool integrations, the enterprise preference curve has moved enough to factor into platform decisions. In a signal that OpenAI is feeling the pressure, Sam Altman announced free Codex usage for 2 months to those who make the switch in the next 30 days.
|
|
Apollo / Pocus: Apollo acquired Pocus to add signal-based selling directly into its platform: CRM signals, behavioral data, and buying intent surfaced inside Apollo workflows to prioritize accounts. Apollo serves 600K+ businesses and is approaching $200M ARR. The direction is an AI-native GTM OS handling detection, prioritization, and execution in one place. The Pocus acquisition fills the detection gap.
|
|
Clay: Clay shipped Functions (beta): reusable GTM logic you define once and apply across every table, audience, and workflow in your workspace. They also shipped a native Gong integration, pulling conversation intelligence directly into enrichment workflows. If you’ve been stitching call data into Clay via Zapier, there’s now a native path. These two shipped in the same week, and that’s probably not a coincidence: Clay is building toward a workflow layer, not just a data layer.
|
|
CRM + Claude, both of them: HubSpot now has a Claude-native connector. Salesforce shipped 60+ MCP tools at TDX in April. Both major CRM platforms have standardized agentic interfaces, and now the vendor with no MCP surface and a proprietary data layer is no longer the norm in this stack. It’s the exception.
|
|
|
👁️ Noticed
Salesforce and Anthropic made the same architectural bet this week from opposite ends. Salesforce is pulling CRM interaction into Slack. Anthropic is pushing Claude into HubSpot. Tools are now having to consider “where does someone interact with our data when the browser isn’t where they’re working?” If they haven’t yet asked themselves that, they’re probably already behind.
|
|
|
|
|
My read on the week:
There’s a version of this week’s news where you file the Salesforce announcement and the Anthropic announcement separately and move on. The version I think is more useful: two companies drew the same conclusion from different directions, and they didn’t coordinate to get there.
The browser-based CRM UI is not where GTM work is heading. The data isn’t moving. Salesforce stays in Salesforce, HubSpot stays in HubSpot. What’s shifting is the interaction layer, the place where a rep preps for a call, or an ops person routes a lead, or a manager checks pipeline. That layer is moving into Slack, into Claude, into whatever the practitioner is already looking at. The CRM becomes infrastructure. The surface becomes whatever can connect to it.
This is not a groundbreaking observation, but the question I’d be asking about every tool in your stack right now: does it have an agentic surface? A way for external systems to query it, read it, write to it? Not as a feature checkbox, but as a structural condition for staying relevant when the interaction layer shifts. Salesforce built 60+ MCP tools. Gong shipped MCP. Gainsight made it GA. Tools that are not building with this landscape in mind are accumulating interface risk: technically functional, but increasingly disconnected from where the work is actually happening.
For most operators, the immediate operational question is much simpler, but just as difficult to solve: what would break if your reps stopped opening the CRM tab?
See you next week. — Andrew
|
|
|
|
|
|
