Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-16 · high
Intercom/Fin, Cognite, and MaintainX all changed hands in the same 30 days, all for the same reason: proprietary data.
Why now: SaaStr grouped Intercom/Fin, Cognite, and MaintainX together in analysis dated July 16, tying all three to the same 30-day acquisition window.
Three B2B acquisitions closed within the same 30 days, Intercom/Fin, Cognite, and MaintainX, and the buyers wanted the same thing: proprietary data, not the product, per SaaStr's analysis.
That reframes how 2026 M&A gets priced. Acquirers are paying software multiples for what functions as a training corpus, and the analysis says a niche vertical SaaS with a decade of customer data is worth more than its ARR implies, whether the owner has priced that in yet or not.
The piece doesn't break out how much of each price tag was data versus software, or list individual dollar figures for the three deals. It treats them as three separate, unrelated-vertical purchases, Intercom/Fin, Cognite, MaintainX, but says the shared asset in each was proprietary data to train on, not the underlying software.
Any vertical SaaS with a decade or more of structured, exclusive operational data is worth more than its ARR multiple suggests, whether the founder knows it or not. Watch which niche B2B categories get bid up next: the ones with the deepest, most exclusive datasets, not the biggest feature sets. The companies that don't know their data is the product yet will find out when someone offers to buy it.
SaaStr's analysis ties all three deals together, dated July 16, the same 30-day stretch the deals happened in.
Each link below shares sources, entities, or timing with this story.
SaaStr benchmarked against Slack / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (SaaStr benchmarked against Slack); both cover ARR, B2B, Intercom, SaaStr; reported by the same outlet (saastr.com).
Jason Lemkin works at SaaStr / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Jason Lemkin works at SaaStr); both cover ARR, Intercom, SaaS, SaaStr; reported by the same outlet (saastr.com).
Linked by a graph relationship (Jason Lemkin works at SaaStr); both cover ARR, Intercom, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Salesforce / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Salesforce); both cover ARR, SaaS, SaaStr; reported by the same outlet (saastr.com).
Zendesk competes with Intercom / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Zendesk competes with Intercom); both cover Intercom, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Salesforce / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Salesforce); both cover ARR, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr benchmarked against Slack / Shared entities / Same source domain / What happened next / Tension
Linked by a graph relationship (SaaStr benchmarked against Slack); both cover Intercom, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Salesforce / Shared entities / Same source domain / What happened next / Tension / Downstream implication
Linked by a graph relationship (SaaStr uses Salesforce); both cover SaaS, SaaStr; reported by the same outlet (saastr.com).