Updated October 2026
License your software company's data to AI buyers
Cielo24 sold 13 years of Slack, Jira and email for "hundreds of thousands of dollars", Forbes reported.1

A software company writes down almost everything it does. Product managers write PRDs, engineers argue in pull requests, the on-call engineer writes up the incident, support answers the same bug report twenty times before it is fixed, sales logs every objection in Salesforce or HubSpot, and customer success notes why an account churned. Unlike most industries, these records are already linked: a support ticket points to a Jira issue, which points to a commit, which points to a release note.
That linkage is why software companies are central to the data market. Cielo24 sold 13 years of Slack, Jira and email; MIT Technology Review counts more than 150 data deals for wound-down startups through SimpleClosure; Troveo names code with commits, reviews and bug history. micro1 lists technology companies first. Brokers have started advertising to SaaS teams of 30 to 200 people with the line "Your wiki might be worth something".
This hub is for founders and operators of SaaS and software companies with ten or more employees that are still operating. It covers what buyers ask for, what customer data and contracts mean for a license, which buyers fit, and how a running company's package differs from a shut-down startup's. Companies winding down should also read the startups page.
Worth
What a company's data may be worth
Set for a typical company, 60 staff and 8 years of records. Move the sliders to match yours. Our estimate, not an offer.
Buyers
Which buyers want this data
Buyers whose own published rules fit SaaS and software companies. We can introduce you to the ones we work with.
Featured partners
micro1
Lists "Technology companies" first among its industries and asks for knowledge bases, project management workflows and task histories.9,10
- $100K to $2M+, micro1 says6
Watch out for: Says it removes personal details only "when relevant", so ask exactly how.11
Polyshares
Names software first among its industries and buys Slack, tickets, CRM and design files.12,13
- $100K to $2M+, Polyshares says7
- None, Polyshares says14
- An offer in 1 to 2 weeks, then paid in 30 to 60 days15
Watch out for: Exclusive by default, and every deal it lists is exclusive with no end date.16,17
Everyone else we reviewed
By score, with full reviews. We have no referral agreement with these companies, so we do not link out to them.
Mercor
Connects to GitHub, Slack, Confluence, Notion and Salesforce, and takes repositories, commits, PRs and issues.18,19
Watch out for: It confirmed a cyberattack in 2026, and class actions followed.23,24
Nyne AI
Buys Jira, Salesforce and HubSpot data, and support tickets, the engineering and go-to-market systems of most SaaS companies.25,26
- $100K or more, Nyne says27
Watch out for: Pays only after the dataset is accepted, and publishes no timeline.28
Troveo
Names production code with commits, reviews and bug history, and a support escalation across tickets and chat.29,30
- Six figures and up for a whole company, Troveo says31
- A share of the revenue; the percentage is not published32
Watch out for: You are paid from a revenue share, so ask what percentage you keep.32
Who wants this
Do buyers want SaaS and software companies?
No buyer publishes prices by industry, but their own intake forms show which industries they rate higher.
- Troveo puts developer tools, data and AI infrastructure, and cybersecurity in its top demand tier, and business and consumer apps in its third.33,34
- Polyshares takes software and saas, without marking it premium.35
- VMS, a broker, gives software or tech extra weight when it estimates value.36
Which buyers take a company your size
Shown for 60 staff, a typical company. Ask whether contractors and part-time staff count.
micro1
Polyshares
No headcount rule; the length and texture of the record matter more38
Mode
20+ full-time US office staff (accounting firms 10+, law firms 6+)39
Pewter
20+ staff and 3+ years; by industry, from 10+ (healthcare) to 50+ (manufacturing, finance)40,41,42
Grepped
No headcount minimum stated43
Ventra
30+ US employees and 3+ years of records44
Mercor
None stated45
Troveo
No minimum stated; its estimator starts at 2046
Nyne
20+ US W-2 employees and 3+ years47
Endless
Roughly 30+ employees48
Supersoniq
50+ employees and 5+ years49
What buyers value
What in a company's records buyers value
What buyers look for in your records, and what to talk through with your buyer before anything leaves your systems.
| Data | Where it lives | Why a buyer values it | Raise with the buyer |
|---|---|---|---|
| Repositories with review and incident history | GitHub, GitLab | Code with its commits, reviews and bug history, the exact phrase Troveo uses. | Open-source components and any customer data in fixtures. |
| Jira or Linear issues linked to commits | Jira, Linear | Bug reports and feature requests traced through to the code change that closed them. | Nothing specific |
| PRDs, RFCs and the internal wiki | Confluence, Notion, Google Docs | Product reasoning before code is written, and the trade-offs considered. | Nothing specific |
| Support tickets and escalations | Zendesk, Intercom | Customer problems diagnosed and escalated to engineering, linked to the fix. | Customer names and data quoted in tickets. |
| Sales and customer success records | Salesforce, HubSpot, Gong notes | Objections, renewals and churn reasons written up by the people who heard them. | Customer contacts and contract values. |
| Incident postmortems | Confluence, Slack, incident tools | What broke, how it was found and what changed, written for engineers who were not there. | Nothing specific |
Process
How it works with each buyer
In each buyer's own words. Where a buyer publishes nothing, we say so.
micro1
- Internal docs, SOPs and playbooks, knowledge bases, project management workflows, internal comms, templates, CRM and workflow metadata, task histories10
- 30 to 200 employees37
- $100K-$2M+ per data package; over $1M for unique data6
- PII removed "when relevant"11
- The company keeps ownership of its data and reviews samples before release50
- Not published
Polyshares
Mercor
Nyne AI
Selling or closing
Selling or closing your company? License its data first
Buyers already approach software companies at the moment of a deal: Mercor approached Warmly about its archives after HubSpot acquired it. If an acquisition or wind-down is in view, ask each licensing company what an acquirer would need to know about a license signed beforehand, and read the startups page for the wind-down route.2
FAQ
SaaS and software companies: questions, answered
It could reach one through a model; that is the purpose of the data. Ask which AI labs receive it and whether you can exclude named competitors. Offering retired products or internal tools instead of the current codebase is one way to limit that.29
AI Input, an intermediary, ran ads from 2026-10-12 headed "Your wiki might be worth something", aimed at SaaS companies of 30-200 people using Confluence and Jira. It is a broker's ad, not an AI lab's offer.60
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Before you sign
Questions to talk through with your buyer
Every business is different, so these are best talked through with the buyer you're working with. Their team goes over them with you before anything is signed.
Questions for this kind of business
- Which customer contracts and DPAs cover data in tickets, logs and fixtures?
- How is open-source code in our repositories treated?
- Would a license affect a later acquisition: reps, warranties or exclusivity?
- How do CCPA, GDPR, UK GDPR and state privacy laws apply, and is de-identified data still personal information?
- Do customer, vendor or platform contracts, NDAs or API terms restrict this?
- How does a license affect a sale of the business: reps and warranties, change of control, earnouts, exclusivity?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?
Proof
Deals in this kind of business
- Cielo24, a transcription software company, sold 13 years of Slack, Jira and email for "hundreds of thousands of dollars" (Forbes reporting, via AI Weekly).1