Roofing
$450,000
Roofing company
Exclusive · perpetual · full operating record
Your service desk history is how IT agents learn to troubleshoot.
A service desk writes its troubleshooting down as it goes: the ticket, the triage note, the escalation, the change that broke something, the reopen and the fix that held. Companies building agents for IT support and operations need that whole chain, and it's hard to fake. We take an anonymized summary of your record to several buyers at once, and you choose the license.
Small commission on close. Nothing up front.
Usually held in
- ConnectWise PSA
- Autotask PSA (Kaseya)
- HaloPSA
- ServiceNow
- Jira Service Management
- Freshservice
- NinjaOne
- Datto RMM (Kaseya)
- IT Glue
- Confluence
- PagerDuty
- Microsoft Teams
What buyers pay for in IT services and MSPs.
Buyers value records that show a decision and what came of it more than they value finished paperwork. These are the parts of your record they look for.
Tickets with the whole chain
Incidents and requests from first report to resolution: triage notes, escalations, reassignments, reopens and the step that finally fixed it. The detours matter as much as the answer.
Changes, including the failed ones
Change requests, approvals, rollout plans, rollbacks and the incidents a change caused. They show an agent what a risky change looks like before it's made.
Runbooks and knowledge articles
The procedures your technicians wrote and actually follow, with their revision history, linked to the tickets they were used on.
Time entries and SLAs
Time logged per ticket, SLA targets, breaches and response times. Together they show how long real work takes and where it stalls, which matters to anyone building triage and scheduling tools.
Alerts and postmortems
Monitoring and RMM alerts, the noise that was rightly ignored, the alert that mattered and the write-up afterward.
Scripts and automation
Scripts and automation policies your team wrote, with what each one was for. Credentials and client-specific details are stripped first; vendor and community scripts belong to their authors.
Systems that hold it and what to watch for.
This is where the record usually lives. Where we've written a data guide for a system, its card links to it, with steps to find out how much you have.
- ConnectWise PSAIT service management, PSA and RMMRead the data guide
- Autotask PSA (Kaseya)IT service management, PSA and RMM
- HaloPSAIT service management, PSA and RMM
- ServiceNowIT service management, PSA and RMMRead the data guide
- Jira Service ManagementIT service management, PSA and RMM
- FreshserviceIT service management, PSA and RMM
- NinjaOneIT service management, PSA and RMM
- Datto RMM (Kaseya)IT service management, PSA and RMM
- IT GlueDocs and knowledge baseStored passwords and client credentials never go into a deal. Only documentation you wrote is considered.
- ConfluenceDocs and knowledge base
- PagerDutyMonitoring and incidents
- Microsoft TeamsTeam chatMicrosoft Teams meeting recordings and transcripts expire after 120 days by default and then move to the recycle bin, so older recordings may already be gone unless your admin changed the setting.
Who buys it and what they do with it.
We describe buyers by category and don't publish their names. Each one is qualified and under NDA before seeing your summary, and when they bid you see every offer side by side, with exclusivity, term and payment next to the price.
Service-desk and IT support agents
Companies building AI that triages tickets, suggests fixes and closes the routine ones. They need real tickets from many different environments, with the resolution attached.
IT operations and reliability AI
Teams building agents that watch alerts, propose changes and respond to incidents. Change records and postmortems show them what a bad change looks like and how it was undone.
Practice-environment builders
Builders of environments where agents debug realistic systems. Runbooks and resolved tickets give them tasks with known answers.
AI labs testing agents on business work
Labs that evaluate agents on long, multi-step requests, the kind a service desk handles every day across email, chat and a ticket queue.
What a package looks like to a buyer.
Before anyone signs, a buyer sees a summary shaped like this one. It is built from rounded ranges: no name, no website, no people, no addresses.
The numbers in this example are made up. Yours come from your intake and the review call, and you read the summary before any buyer does.
See the full processExample package · IT services
Illustrative- Sector
- Managed service provider, small and mid-size business clients
- Region
- Midwest US
- History
- 8+ years, continuous
- Record
- ~40K tickets, ~120K time entries, ~2K change records, ~250 runbooks
- Mix
- ~80% managed services, ~20% projects
- In scope
- Ticket threads and resolutions, change records, runbooks, SLA history
- Left out
- Credentials, network details, regulated clients' tickets, client documents
What stays out by default.
Some records aren't yours to license, and some shouldn't leave the building. Intake and the review call bring these up early. The main ones for this industry are below.
Credentials and password vaults
Passwords, keys, MFA secrets and anything stored in a credential or documentation vault never go into a deal. Scripts and ticket notes with embedded secrets are cleaned before delivery or left out.
Client network details
Hostnames, IP addresses, network diagrams and anything describing a client's security setup come out, so no ticket can serve as a map of someone's systems.
Client-specific material without consent
Your tickets describe your clients' systems, so their contracts and confidentiality terms apply. Packages start from de-identified process records; anything specific to one client needs that client's written consent, and clients whose agreements bar this use are left out.
Regulated clients' records
If you maintain systems that hold a healthcare client's patient information, you're likely a HIPAA business associate, and your agreement limits what you can do with it (45 CFR 164.504(e)). Tickets for healthcare, government and financial clients stay out unless counsel approves de-identification and the client agrees in writing.
Security findings
Vulnerability scans, pentest results, breach details and anything about an issue that hasn't been fixed stay out.
Client documents and end users
Files clients stored with you belong to them and stay out. End users' names, emails and phone numbers are removed before delivery under the license.
This is not legal advice. Whether a record can be licensed depends on your contracts, your software terms and how it was collected, and your counsel should review any license before you sign. The rules named on this page are linked under Sources.
Licenses in our network closed by buyers, not by us.
Recent licenses of operating records, closed by buyers in our network. They come from trades and services businesses rather than this industry, so read them as a sense of the market and nothing more.
Construction
$300,000
General contractor
Exclusive · 24-month term · full operating record
Solar
$275,000
Solar company
Exclusive · 18-month term · full operating record
Marketing
$110,000
Agency with global clients
Exclusive · 24-month term · full operating record
Licenses closed by buyers in our network, shown to describe the market. They are not deals thedata.broker brokered and not a forecast of what your record will bring. Every record is priced on its own.
IT services and MSPs questions worth settling early.
More in Answers, or ask us on a call after your intake.
The names come out before delivery, along with end users' details, hostnames and IP addresses. The harder question is your client contracts, which may limit what you can do with information about their systems. Intake asks about client agreements, and clients whose terms bar this use are left out. This is not legal advice.
For anything that is really about one client, such as their configuration, documents or a named incident, plan on getting written consent. For de-identified process records, like how tickets were triaged and resolved, it depends on what your agreements say. Your counsel should read the contracts in scope. This is not legal advice.
They're left out by default. An IT provider that maintains systems holding a healthcare client's patient information is usually a HIPAA business associate (45 CFR 160.103), and its business associate agreement limits how that information can be used. This is not legal advice.
It can be. Volume and continuity matter more than age, and several years of resolved tickets, time entries and change records can make a package on their own. If yours isn't enough yet, we say so early.
Code you built for a client usually belongs to that client under your agreement, so it stays out unless the client consents in writing. Your own internal tools and scripts can be considered. This is not legal advice.
We are paid a small commission out of a deal that closes. If nothing closes, you owe nothing. You keep ownership of your records and keep using them.
Sources
Primary sources for the rules this page names. Summaries above are not legal advice.
Not quite your business?
See every industry we take on, the business functions buyers ask for, and which records need special handling.