Tracked Changes

Change Log

Consolidated release notes for go to market software. GTM Tech Index tracks material product and capability changes across indexed vendors: releases, AI and agent capabilities, integrations, breaking API changes, pricing and packaging changes, and compliance and governance changes. Funding rounds, valuations and awards are excluded by policy. Every entry cites a live source, and each is linked to the capability axis it bears on.

Follow this change log by RSS

Free for your reader, newsletter or automation tool. One feed covers the whole index, and every category has its own.

All feeds and terms
Most recently tracked

SalesBlink 2026-10-18, Evergrowth 2026-10-17, Tuco AI 2026-10-16, ChurnZero 2026-10-16, Demandbase 2026-10-15, Generect 2026-10-15, GetAccept 2026-10-15, Read AI 2026-10-15, Salestools 2026-10-15, Airspeed 2026-10-15, AiSDR 2026-10-15, Avoma 2026-10-15

206 tracked changes across 137 of the 406 indexed vendors, spanning 2025-12-02 to 2026-10-18. 100 percent carry a live retrieved source, 145 are confirmed at the vendor's own materials and 61 are reported by a credible third party but not confirmed at source. 76 are graded High impact. Entries span 10 change types and touch 17 of the seventeen capability axes.

Public source research. Entries are sourced from vendor changelogs, documentation, announcements and press materials. Entries marked Partially Verified are reported by a credible source but not confirmed at the vendor's own materials, and should be independently verified before relying on them for procurement decisions.

Showing changes for Airspeed only.Show the full log
A
Airspeed2026-10-15
Impact
Medium
Verification
Verified
Integration / interoperability

The Airspeed MCP server is now listed in the Claude connector directory and the ChatGPT plugin directory, with Gemini Enterprise set up through Airspeed support. It exposes 61 tools across search, company 360, calls, deals, scorecards, forecasts, playbooks, agents, tasks, comments and call shares. Users sign in with their own Airspeed account with no API key to manage, and Airspeed says the assistant sees only what the user can see and acts only where their Airspeed and CRM permissions allow.

Call and deal data now reaches Claude and ChatGPT under each rep's own sign in, so what the assistant can see and change follows that person's Airspeed and CRM permissions.
Related: Ecosystem and Integration DepthView source
A
Airspeed2026-09-22
Impact
High
Verification
Verified
Pricing / packaging

Airspeed switched on Mach 1, which its 24 Sep newsletter describes as deep analysis, for every workspace by default, with no request or admin toggle needed. Each user gets a published allowance of 16 Mach 1 runs per month.

A stated per user monthly run limit tells buyers what the deep analysis feature includes before they sign, and it is a usage cap to plan around for heavy users.
Related: Commercial TransparencyView source
A
Airspeed2026-09-11
Impact
Medium
Verification
Partially Verified
Integration / interoperability

Airspeed rebuilt its MCP server so that AI assistants such as Claude can read calls and deals from the browser rather than through a desktop installation. The release also fixes installation problems Windows users had reported and reduces the latency between a question and its answer.

Moving the MCP server out of a desktop install and into the browser removes the step that stalls most MCP rollouts, which is getting an installer past IT on a fleet of Windows laptops. The Windows fix and the latency work say the earlier build was rough in production, so the rebuild is the version to evaluate.
Related: Ecosystem and Integration DepthView source
A
Airspeed2026-09-03
Impact
Medium
Verification
Partially Verified
Product / capability

Airspeed expanded what its agents can produce, adding chart generation, presentation decks and code. The Deal Board now displays CRM fields inside the view rather than requiring a jump to the CRM.

Moving from summarizing a conversation to producing the artifact that follows it is a real widening of scope, and it is also where output quality becomes harder to check. A deck an agent builds from call data is easy to accept without reading, which is a different risk from a transcript nobody reads.
Related: AI CentralityView source

Common questions

How do I keep up with changes to go to market software?

Vendor release notes are the primary source and they are scattered, inconsistent and written to announce rather than to inform a buyer. The GTM Tech Index change log consolidates them into one feed with a fixed editorial policy. It tracks material product and capability changes at indexed go to market vendors: releases, AI and agent capabilities, integrations and interoperability, breaking API changes, pricing and packaging changes, and compliance and governance changes. It excludes funding rounds, valuations, stock listings, partnerships and awards, because none of those change what the product does. Every entry cites a live retrieved source, 100 percent of them today, and each is linked to the capability axis it bears on so a change can be read against the vendor's graded profile rather than in isolation. Entries confirmed at the vendor's own materials are marked Verified and the rest are marked Partially Verified, currently 145 and 61 respectively. The practical routine is to read the log for what changed and the weekly Brief for what it means.

Where do I find release notes for go to market software vendors?

Each vendor publishes its own, in its own format, on its own schedule, and many put them behind a login or retire them after a quarter. This page is the consolidated alternative: 206 tracked changes across 137 vendors so far, each carrying the source link back to the vendor's own release note, announcement or documentation. Recent entries cover SalesBlink, Evergrowth, Tuco AI, ChurnZero, Demandbase, Generect and others. The feed is filterable by vendor, change type, impact level and verification status, so a buyer tracking a shortlist can watch three vendors rather than reading everything. Where a vendor's own release notes exist publicly, the entry links straight to them.

What counts as a change worth tracking?

A change earns an entry if it would move a buyer's evaluation. That is a deliberately narrow test and it excludes most of what a vendor announces. Funding rounds, valuations, stock listings, partnerships and awards are out by policy: they tell you about the company rather than the product. Acquisitions qualify only where there is direct product impact. What is in: shipped capability, model and architecture changes, performance evidence, regulatory and licensure changes, security and compliance changes, integrations, pricing and packaging changes, safety and governance changes, and product sunsets. 206 entries have cleared that bar so far, across 10 change types, and 76 are graded High impact.

How is each entry verified?

Every entry requires a live retrieved source URL before it is written, and no entry exists without one. An entry marked Verified is confirmed in the vendor's own materials or a regulatory filing. An entry marked Partially Verified is reported by a credible third party but not confirmed at source, and should be independently checked before it is relied on in procurement. Vendor claims inside a summary are attributed to the vendor rather than restated as fact. Each entry also names the capability axis it bears on, which is what connects a change to the graded assessment on that vendor's profile rather than leaving it as news.

Contact us

Found a vendor we missed? Have feedback on the index? We’d love to hear from you.