For IT services firms and MSPs
Get paid for what your service desk already knows.
Years of tickets, runbooks and incident reports record how your technicians diagnose and fix real problems. AI labs pay for that kind of record. We license selected records on your behalf, keep client data and credentials out and negotiate the best available price.
Systems we often see
- ConnectWise PSA
- Autotask
- HaloPSA
- NinjaOne
- Datto RMM
- Kaseya
- ServiceNow
- Jira Service Management
- Microsoft Teams
- Slack
Partner estimate for qualifying records: $100K to $1M+. Buyer interest and value are not guaranteed.
- No files or logins to start
- You pay nothing unless a license is signed
01 Why AI labs care
What your records show that AI can’t do yet.
AI can explain how DNS works. It still struggles with real troubleshooting: narrowing a vague complaint to a cause, knowing which fix is safe on a client's network, escalating at the right moment and writing it up so the next tech can follow. Your ticket history shows that process thousands of times, with the outcome attached.
What makes IT services firms and MSPs’ records valuable
- Large volumes of problems paired with resolutions, time spent and outcomes
- Escalations that show how tier-one questions turned into tier-three fixes
- Runbooks and documentation refined over years of real incidents
- Incident reports and post-mortems that capture root causes and lessons learned
02 Workflows
The work with the most value.
Buyers look for complete pieces of work, start to finish. In your industry, these are the strongest.
Service desk tickets
User-reported problems, troubleshooting steps, internal notes and the fix that closed each ticket.
Escalations and incidents
Outages and security events from first alert through resolution, including who was pulled in and why.
Projects and migrations
Scoping, cutover plans, issues found mid-migration and how they were handled.
Runbooks and procedures
Standard procedures written and revised as your team learned what works.
Client reviews and recommendations
Quarterly business reviews, lifecycle plans and the reasoning behind each recommendation.
03 Connected records
One piece of work, followed end to end.
This is what connected history looks like, and why it’s worth more than any single file.
Illustrative exampleInvented details. Not client data.
A slow-network complaint, traced to the cause
- TicketTicket 48213: staff at a client office say file transfers crawl every afternoon.
- Internal notesTier one rules out the workstations. Monitoring shows the firewall's CPU spiking around 2 p.m.
- Team chatA senior tech spots a cloud backup job that moved into business hours after an update.
- Change recordThe job is moved to 11 p.m. and bandwidth limits are added, approved by the client's office manager.
- TicketTransfers are back to normal the next day, and the fix is added to the client's runbook.
Each note is routine. Together they show real diagnosis, from a vague symptom to a lasting fix. Client names, IP addresses, hostnames and user details are replaced or removed before anything is shared.
04 Privacy and rights
What stays out, and what’s reviewed first.
Every industry has its own sensitive material and its own rules. For IT services firms and MSPs, these come first.
Always excluded or removed
Before anything is shared, these stay out entirely or are replaced.
- Passwords, API keys, MFA secrets and anything from documentation platforms or password vaults
- Network diagrams, IP addresses, vulnerability details and other security-sensitive information
- Protected health information from healthcare clients
- Client end users' personal information inside tickets (removed or replaced)
- Client names and contact details (replaced with consistent stand-ins)
- Records from clients whose contracts prohibit reuse
Rights reviewed before buyers are approached
Client agreements
Master services agreements and NDAs usually include confidentiality terms covering the client information you handle. They're reviewed client by client to decide what can be included, and some clients' records may stay out.
HIPAA business associate agreements
Providers that support systems holding electronic protected health information are usually business associates under HIPAA. Records from those clients get extra care, and protected health information stays out entirely.
Security exposure
Tickets and documentation can reveal how a client's network is built and defended. Anything that could weaken a client's security is removed or excluded, not just personal information.
This isn’t legal advice. We flag what we find and encourage you to have your own counsel review. How records are protected
05 How it works
From first conversation to signed license.
We negotiate on your behalf and manage the process. You approve every term, and you pay nothing unless a license is signed.
- 01
Start with a conversation
Tell us about your business, the systems you use and how far back your records go.
No files or logins needed - 02
Agree on what’s in scope
Together we decide what’s included and what stays out. Rights and privacy are reviewed before anything is shared.
You set the boundaries - 03
Bring offers to the table
We present your opportunity to AI labs, compare the offers and negotiate price and terms.
We negotiate for you - 04
Approve and get paid
Nothing moves until you sign. Records are prepared and delivered under the terms you agreed.
Your signature, your call
06 Questions
Questions from IT services firms and MSPs.
New to this? Start with our plain-English guide to licensing business data.
Can an MSP license ticket data about its clients' systems?
It depends on your client agreements and the data involved. Many tickets are about your team's work rather than the client's information, but client details, end-user information and security specifics are removed, and agreements are reviewed before any buyer is approached. This isn't legal advice, so your counsel should confirm.
Which IT records are most valuable?
Tickets with the full trail: the original complaint, the troubleshooting notes, the escalation and the fix. Several years across many clients and environments is what buyers look for.
Do you need admin access to our PSA or documentation platform?
Not to start. A conversation is all it takes, and nothing from a password vault is ever in scope. If you go ahead, the scope you approve decides exactly what's prepared, and nothing is shared until you sign.