|
GTM stack intelligence, enriched.
|
|
The race to embed agents directly into your revenue tools continues as HubSpot put out an Agent CLI, Gong unveiled its Revenue Harness, and Claude is now @-Mentionable in your company’s meme Slack channels.
The same week, a breach at a single market-intelligence vendor drained Salesforce data out of more than ten companies at once through stolen integration tokens. The two stories highlight the revenue cockpit still needs to be secured.
Clay also removed the cap that used to make it a workaround tool and started calling itself a data layer.
|
|
|
HubSpot — Agent CLI Enters Public Beta: A Headless CRM for the Agent to Drive
HubSpot released the public beta of its Agent CLI on June 23rd. Unlike the existing developer CLI, which is meant for human-in-the-loop work, the Agent CLI is built for AI agents like Claude Code and Codex to read and write CRM data without human oversight. It covers contacts, companies, deals, tickets, and custom objects, plus pipeline and stage management, workflow creation, and plenty of others.
HubSpot is shipping the Agent CLI alongside its existing MCP server, but handling different tasks: the MCP server handles conversational, human-in-the-loop work, and the CLI handles non-interactive, scheduled work an agent runs on its own. There’s a subtle implication there. Your CRM workflows are increasingly a datastore accessed via agent, not a seat-holder, and now it has a front door with a welcome mat.
If it sounds scary, that’s because it kind of is. It’s worth a look before someone on your side wires it up unsupervised. The guardrails HubSpot shipped, dry-run and audit logging on deletes, are the ones you’d want to mandate in any internal policy. It’s a good start, but your HubSpot admin and data team will likely want more. If you’re interested in agents writing to your deal records, the question to settle beyond the actions they’re allowed to take is who reviews what they change and how they are notified. Do it while the surface is still in beta and easy to scope.
Source: HubSpot Developer Changelog — Agent CLI, June 23, 2026
|
|
|
Gong — Unveils “Mission Big Dipper,” With Revenue Harness as Their Governed Agent Execution Layer
Gong announced “Mission Big Dipper” on June 24th, and the centerpiece is the Revenue Harness, which Gong describes as an agentic execution layer that governs, orchestrates, and connects AI agents across the full revenue cycle. Alongside it, Custom Agents is now GA, and RevOps sales leaders can build and deploy governed agents in natural language, with scoped data access, a full audit trail, and configurable human oversight, without engineering.
What Gong is selling is governance and guardrails, not a factory for creating endless amounts of agents. The pitch is, essentially, to let a sales manager stand up an agent against your call and pipeline data while maintaining an audit trail and an oversight switch. It’s an argument in favor of decentralizing building while centralizing meaning. Metrics are defined and agent accessibility is configured, but within those sandbox confines your sellers and operations team can build the agents that drive value for their unique needs.
If your RevOps team has Gong in the stack and is interested in Revenue Harness, the near-term move is to read the oversight model carefully before anyone builds on it: what “scoped data access” actually scopes, what the audit trail captures, and whether the human-oversight setting is on or off by default.
Source: PR Newswire / Gong — Mission Big Dipper, June 24, 2026
|
|
A closer look at one smaller stack vendor each issue.
|
Clay — Removing the Cap and Introducing Audiences
The company that coined the GTM Engineer role may no longer fit into the category of “smaller” vendors. Regardless, Clay is our Stack Deep Dive this week.
Clay built its reputation as the enrichment scratchpad for RevOps teams when their CRM and data vendors can’t talk to each other cleanly. The constraint everyone hit, being capped at 50,000 records per table, is no more. On June 23rd, Clay announced Audiences.
With the cap gone, Clay is describing Audiences as GTM infrastructure to build any play that you can imagine. From “always on” enrichment to enrichments that are reusable across campaigns rather than re-run and re-billed each time. The feature that caught my eye: Audiences are dynamic and reusable, updating automatically if the data changes. Clean, updated data syncs back to your warehouse and CRM. No more cold outreach pitching to you based on your previous employer or role.
This pushes and pulls on Enriched’s framework. Data warehouse gravity is on full display. Clay is blending your warehouse and CRM data rather than trapping records in a proprietary store. However, the more your segments, your refresh logic, and your reusable enrichments live inside Clay, the more Clay becomes the place your definitions are authored, and authoring is stickier than storage. A dynamic segment with Clay’s enrichment logic baked into it needs a rebuild if you leave.
Source: Clay — Announcing Audiences, June 23, 2026
|
|
|
|
AI for RevOps · Anthropic
|
Anthropic — Claude Tag Launches in Beta: Your Newest @-Mentionable Teammate Inside Slack
Claude just became your newest teammate in Slack to send funny gifs to. Anthropic announced Claude Tag on June 23rd. It joins a Slack workspace as a team member that any channel participant can @-mention, runs on Claude Opus 4.8, and builds contextual memory from a channel’s history rather than starting cold each time. Per Anthropic, it can schedule and pursue tasks asynchronously, supports DMs with private tool access, and ships with fine-grained admin access controls. It’s available in beta to Claude Enterprise and Team customers with introductory launch credits, and the older Claude-in-Slack app retires in 30 days, on August 3rd.
Source: Anthropic — Introducing Claude Tag, June 23, 2026
|
|
The rest of the week, in brief.
|
|
|
|
Microsoft M365 list prices rise July 1; June 30 is the last day to lock current rates: Microsoft’s list-price increases take effect July 1st. Business Basic goes $6 to $7 per user per month, Business Standard $12.50 to $14, Office 365 E3 $23 to $26, and Microsoft 365 E3 $36 to $39. Existing customers on active subscriptions keep current pricing until renewal, but any new or renewal agreement signed on or after July 1st pays the new rate, which makes June 30th, the day before this issue lands, the last day to lock pre-increase pricing. If you have a renewal in flight, this is a today problem.
Source: Microsoft Licensing News, effective July 1, 2026
|
|
Unify reprices to $20/month self-serve and rebrands as an AI outbound platform: Unify announced its “Next Chapter” on June 24th, calling itself “Claude for outbound sellers” and adding self-service signup with plans starting at $20/month while expanding to more than 40 signal and data sources. The low self-serve entry point in a category that used to start with a sales call is the clearest usage-based-repricing move of the week.
Source: Unify — Changelog, June 24, 2026
|
|
Anthropic’s Mythos 5 cleared for partial US redeployment; Fable 5 still offline at publish: On June 27th Anthropic said the US Commerce Department cleared Mythos 5 to return for roughly 100 US organizations that operate or defend critical infrastructure, along with their foreign-national employees and certain government agencies and national labs. Fable 5 remains offline pending Pentagon and NSA sign-off; Axios reported June 27th that it was “on track to return within days,” but as of June 28th it had not been restored. This is a partial reopening, not a general one, and broad consumer and enterprise access is still suspended.
Source: Euronews / Axios, June 27, 2026
|
|
Rippling launches Data Cloud, an AI BI layer that scores employees against their AI spend: TechCrunch reported on June 25th that Rippling launched Data Cloud, a BI platform that generates dashboards from natural language and connects across systems including Salesforce, GitHub, and Anthropic usage logs, with zero-copy integration into Snowflake. Per Rippling, it ties AI token spend to output and supports compensation and workload analysis. The base SKU runs around $20/month with usage-based charges on top, and Rippling cited 560 companies and $5 to 7 million in new monthly recurring revenue at launch. The line to watch is “scoring employees by their AI spend,” which is the attribution lens pointed inward at your own team.
Source: TechCrunch Enterprise, June 25, 2026
|
|
6sense launches AI-Recommended Leads, surfacing CRM-ready contacts from ad-engaged accounts: Announced June 22nd at the Cannes Lions B2B Summit, the feature identifies contacts from accounts that engaged with 6sense advertising campaigns, drawing on 6sense’s people intelligence and persona logic rather than only the people who clicked. Marketers get the contacts as downloadable lists that route to AI Email, BDR teams, or reps without requiring a form submission. For demand-gen teams the practical effect is a shorter path from ad engagement to a working contact list, with the usual caveat to check how those contacts perform before treating them as marketing-qualified.
Source: MartechSeries, June 22, 2026
|
|
|
👁️ Noticed
Clarify shipped a CRM agent this week under the tagline “The M in CRM shouldn’t be you.” In a week when HubSpot, Gong, and Anthropic all built new ways for an agent to operate your revenue stack without you, it’s hard to argue with the marketing. The M is leaving. Whether you wanted to be the M or not is a separate conversation.
|
|
|
|
|
The agent-control plane is landing. HubSpot shipped a headless Agent CLI built for Claude Code and Codex to pilot the CRM with no human in the loop. Gong unveiled a Revenue Harness whose entire job is to serve as air traffic control to agents across the revenue cycle. Anthropic put a persistent, tool-wielding Claude inside Slack. Inside 48 hours, agents got their own dedicated sandbox within core elements of the GTM stack.
What does the trusty Enriched framework have to say? Agentic integration readiness is clearly satisfied: every one of these tools is now built to be called by an agent rather than only clicked by a person. All three also clearly realize the pesky, but very necessary, governance question is not going away: the audit log, the dry-run, the scoped access, the oversight switch. Whoever owns the layer that governs your agents owns the audit trail and the kill switch for your revenue operations.
Last week’s Klue breach is the proof. One market-intelligence vendor’s stored OAuth tokens, reached through a single abandoned credential, were enough to gain data across a dozen companies at once, without the attacker touching any of those companies’ own defenses. When governance and InfoSec fall short, the blast radius isn’t one tool, it’s every system that tool was trusted to reach. The same property that makes an agent-callable layer powerful, that it holds scoped access into everything, is the property that makes its governance and security a non-negotiable.
So the exercise this week is for the InfoSec minded operators among us: a control-plane audit. First, list every layer that now holds governed, standing access to operate your stack on an agent’s behalf: HubSpot’s Agent CLI, Gong’s Harness, whatever you wire Claude Tag into. Second, list every third party holding a live OAuth token into your CRM, and how fast you could revoke it. The first column is where your leverage is quietly moving. The second is where your risk already is. The list of possible vendors in the GTM stack represented in column one grew this week. Klue spent the week demonstrating the second column.
See you next week. — Andrew
|
|
|
|
|
|
