The GTM Tech Index Brief

The first fortnight in one line

GTM vendors ship weekly and write it down, and the first fortnight of the log reads like a sector that has discovered it can be reached from a chat window. Two CRMs published connectors for AI assistants, one vendor quietly narrowed its own, and the compliance controls that matter most arrived as toggles, each with a default that somebody else will set.

This is the first issue of the Brief. It covers the change log’s opening period, August 10 to August 29: 18 entries across 16 vendors, ten Verified at source and eight Partially Verified. Compared with the sectors this index’s siblings cover, GTM vendors are positively chatty. They publish dated release notes and developer changelogs, which is either admirable discipline or the natural behaviour of an industry whose whole business is sending messages. Funding rounds, valuations, and awards are not logged, here or anywhere on this index.

The CRM became a chat window

Pipedrive published a Model Context Protocol connector on Claude’s official marketplace that can query, create, and update deals, activities, and contacts from the assistant. Clari’s August release added MCP servers for ChatGPT and Claude so Copilot data can be queried from outside the platform, alongside bulk call analysis across up to 1,000 calls. Outreach put MCP connector management into its mobile apps, next to an AI Control Hub for governing AI features and a configuration change log for Revenue Agent. And Reply.io moved 39 AI SDR endpoints into public beta, with approval mode and pending approvals exposed as API objects, so the human in the loop is now scriptable and can also be scripted away.

The entry worth reading twice is the one that took something away. Salesloft’s MCP Server for Claude no longer returns raw call transcripts; summaries and key moments remain. In the same fortnight the sector opened its systems of record to outside assistants, one vendor decided a full transcript was more than an assistant should carry out of the building. A connector that can create and update deals means the assistant has write access to the number the whole company is measured on, so permission scoping belongs in the rollout plan and not in the retrospective.

The compliance controls arrived as toggles

Revenue.io made the meeting recording disclosure configurable, so an administrator now decides how often the announcement replays during a call. QuickProsp version 1.19.0 shipped bring your own model keys for OpenAI, Anthropic, and Gemini, and, in the same release, an option to skip List Unsubscribe headers, which the major mailbox providers require of bulk senders. Saleshandy added Prospect Enrollment, a cap on how many prospects enter the first step of a sequence per day, week, or month, set at the sequence level rather than the mailbox. Revenue.io’s Summer release added automatic SMS and working day aware timing, and the note says nothing about how SMS consent is captured. SalesCaptain gave its agents Actions, including scheduling appointments, updating records, and sending payment requests, with nothing published about an approval step before the agent writes to a connected system.

Every one of these is a setting, and a setting is a policy decision delegated to whoever is in the admin panel at a quarter to five on a Friday. The disclosure replay can be tuned toward safety or away from it. The unsubscribe header can be kept or dropped. The enrollment cap is the rare toggle that only points one way, which is why it is the best deliverability news in the log. This index grades outreach compliance on what the vendor publishes about the default, not on what the toggle allows, and the questions to ask before turning any of them are on the outreach compliance guide.

Read the ones with version numbers

Lusha shipped two API releases a day apart. Version 2.12.0 moved Contact Lookalikes to a v3 path with schemas that are not backwards compatible and made a Signals parameter required; version 2.13.0 tightened validation so an oversized page or a malformed date now returns an error, and folded missing and still processing transcripts into one 404. HubSpot’s August rollup preserves active workflow enrollments when records are merged, which fixes the kind of silent drop nobody notices until the quarter is over. Close released an Event Log recording who changed what and from where, including changes made by integrations rather than people, with an API and webhooks to stream it out. Nobody reads release notes until one of them breaks something, at which point everyone reads that one, twice. Three of the eighteen entries here break something for an integration that was working last month, and the Close entry is the one that lets you find out what they did to your data.

The signals got stranger, in a good way

Autobound added podcast intelligence to its Signal API, more than 58,000 extracted appearances, claims, and sponsorships, and rebuilt its SEO signals around AI search visibility. Somewhere a vice president of sales is about to receive an email about something she said on a podcast in March, and the email will know the episode number. Instantly added Company Sources to SuperSearch, building contact lists from tech stack data, ecommerce stores, and lookalike audiences, without describing where those signals come from, which is the question this index asks first. Meet Drake gave its LinkedIn automation a native CRM and Messenger, which is convenient and also moves more of the conversation record off the platform and into the vendor. And Nooks acquired FullyRamped, so the dialer now trains the roleplay bot on real calls and the roleplay bot trains the rep, and somewhere in that loop a person still has to pick up the phone.

What the fortnight says about the category

The features in this log are what you would expect from a sector that ships every week. The interesting entries are the controls around them: who has write access to the system of record, what the default is on a compliance setting, whether a breaking change was announced before it broke, and whether anyone will say where a signal came from. Those are the things a buyer can check and an index can grade, and in a category where every vendor can generate a personalized email, they are also what is left to compete on.