GTM Tech Index
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.

Most recently tracked

Airspeed 2026-09-03, Chili Piper 2026-09-03, Qwilr 2026-09-03, Clari 2026-09-02, HeyReach 2026-09-02, Membrain 2026-09-02, Rox 2026-09-02, Autobound 2026-09-01, Fireflies.ai 2026-08-31, HubSpot Sales Hub 2026-08-27, Nooks 2026-08-25, Saleshandy 2026-08-24

29 tracked changes across 23 of the 315 indexed vendors, spanning 2026-08-10 to 2026-09-03. 100 percent carry a live retrieved source, 14 are confirmed at the vendor's own materials and 15 are reported by a credible third party but not confirmed at source. 15 are graded High impact. Entries span 4 change types and touch 9 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 Lusha only.Show the full log
2 entries
Weekly Brief →Browse vendors →Methodology →
L
Lusha2026-08-19
Impact
High
Verification
Partially Verified
Product / capability

Lusha released API version 2.13.0, introducing a dedicated Conversations tag for conversational intelligence. The update adds stricter validation, where a pageSize above 100 or an invalid date format now returns a 400 error, and it unifies the response for missing or still processing transcripts under a single 404.

Teams integrating Lusha's conversational intelligence need to update pagination and error handling, since requests that previously succeeded will now fail validation. The unified 404 also removes the ability to distinguish a transcript that does not exist from one that is still processing, so retry logic has to assume both.
Related: Ecosystem and Integration DepthView source
L
Lusha2026-08-18
Impact
High
Verification
Partially Verified
Product / capability

Lusha released API version 2.12.0, adding a maxContactsPerCompany parameter to the Prospecting Contacts endpoint and a required maxResultsPerSignal parameter to the Signals API. The Contact Lookalikes endpoint moved to a v3 path with fully replaced request and response schemas that are not backwards compatible.

This is a breaking change. Any integration calling Contact Lookalikes has to be rewritten against the v3 schema, and calls to the Signals API now fail without the new required parameter. The per company cap is the useful addition, giving operations teams direct control over credit consumption during prospecting.
Related: Ecosystem and Integration DepthView 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 14 and 15 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: 29 tracked changes across 23 vendors so far, each carrying the source link back to the vendor's own release note, announcement or documentation. Recent entries cover Airspeed, Chili Piper, Qwilr, Clari, HeyReach, Membrain 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. 29 entries have cleared that bar so far, across 4 change types, and 15 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.