An MSP's ticket history is a decade of problems solved end to end.
Tickets, runbooks, escalations, the change that fixed it. This is the vertical buyers ask about most, and it is also the one where the records belong to the customer more often than the firm expects.
Example engagement
ExampleAn illustration of a firm of this kind, not a client and not a transaction. No figure here is a price; the published figures on this page are the buyers' own, and each one links to the page it came from.
- Headcount
- 30 to 80 people
- Years of records
- 9 years of records
- Tools it runs on
- A PSA, an RMM, a ticketing system, a documentation tool, a monitoring stack and a CRM.
- What is in them
- Tickets from first report to resolution; runbooks and standard operating procedures; change and incident records; escalation threads; the configuration history behind each fix.
- Route options
- 1License a defined sliceOne buyer licenses records you choose, from a set period, for a set term or use. You keep the records and the right to license them again.
- 2License on a scheduleThe history first, then new records each year or quarter, paid as they arrive. It works while the business keeps producing the same work.
- 3Sell the company to a buyer that prices the records inAI-enabled roll-ups and strategic buyers now pay for companies whose records and workflows they can put to work. The records are part of what they buy.
- 4Build a data productA valuation and build partner measures what the records support, builds a product buyers ask for, and sells it on license or as a service. You pay fees up front; revenue follows if it sells.
What buyers publish
Checked Nov 5, 2026
Published per-company figures
$10K to $4M+
The span of what 7 programs publish for a company like yours.
These are the programs' own advertised figures. None of them is an offer, and no buyer has seen your records.
Where these come from
- Handshake AI data licensing $100K to $4M+ payouts
- micro1 Company Data Partnerships $200k-2M+ headline; $100K-500K, $500K-2M and $2M+ by tier; payments typically $150K to over $2M
- Polyshares data licensing Typically $100K to $2M, paid by us to the company
- Replay data licensing $10K - $100K for 20-50 employees; $100K - $1M for 50-250; $1,000,000+ for 250+
- Scale AI Data Partnerships $10K-$1M+ illustrative value per data partnership, scaling with cadence
- SourceX data licensing Estimated licensing payout based on company size (for example $30K–$180K for 50–99 employees); exact payout fixed in a signed Dataset Deal Confirmation
- Turing, Project Lazarus up to $1M
Every program, with its terms and its source
Fifteen to twenty minutes on what these figures mean for your records, your rights and the rest of your plans.
What changes in this line of work
A managed-services agreement usually says who owns the documentation and the ticket record, and the answer is often the customer. Customer environments and configurations are frequently theirs too. What is reliably the firm's own is its method: how it triages, what it standardised, what it stopped doing. A recurring licence works here when the firm keeps producing the same work.
What decides whether you may license at all
Read the MSAs before anything else, especially the data-ownership and confidentiality clauses, and check any upstream vendor terms on the tools the records were exported from.
Where to go next
- Work through your own records
The same questions, answered for your firm: whether the records are ready, which route fits your plans, and the range the published figures support.
- Already hold an offer?
Paste it. You get a note on the figure against what buyers publish, the payment trigger, exclusivity, export and retention.
- Every buyer, with its terms
One row per program: what it buys, what it publishes, a quote from its own page and the day we read it.