Data licensing guide
By industry

Licensing an IT services firm's or MSP's data for AI

By Ade Molajo · Updated · How we check figures

Quick answer

Often, yes. Ticket histories, runbooks, scripts and resolution notes show how IT problems get solved, which is valuable training data. micro1 and Mode take firms with 30+ staff. Mercor has no MSP listing, though its cybersecurity listing ($20K–$750K, from 20 staff) fits security-led firms. Most MSP data sits inside client environments, so client contracts and security decide the scope.

30+
staff for micro1 and Mode
No listing
for MSPs at Mercor (cybersecurity is closest)
Tickets
and runbooks are the core asset
Clients'
environments need their agreement

01What the programmes publish for IT services firms

Published ranges that apply to IT services firms and MSPs: micro1 tiers from $100K to $2M and up; Mode $100K to $5M; Mercor publishes no listing for this business type.$0$1M$2M$3M$4M$5Mmicro1$100K–500K · $500K–2M · $2M+micro1.ai/data-partnerships · 30 Oct 2026Mode$100K–$5M per companydata.mode.inc · 30 Oct 2026
Each programme’s own published range, checked 30 October 2026. Ranges, not offers.
micro1ModeMercor
RangeTiers $100K–500K to $2M+$100K–$5MNo MSP listing; cybersecurity listing $20K–$750K
Minimum size30+ full-time staff30+Cybersecurity: 20–2,000
What it wantsSOPs, knowledge bases, project histories, internal processesJira, Zendesk, Slack and other systemsCybersecurity: "security alerts, investigations and case write-ups, or security software"

Each programme's own pages, checked 30–31 October 2026. Ranges, not offers.

Where these records usually live

PSA and RMM

  • ConnectWise
  • Autotask
  • HaloPSA
  • NinjaOne

Service desk

  • Jira
  • Zendesk
  • ServiceNow

Documentation

  • IT Glue
  • Confluence

Examples of common tools, to help you find your records. Product names and logos belong to their owners; no affiliation or endorsement.

02Why MSP data is useful

An MSP's ticket history is a record of thousands of real problems and how they were fixed: the symptom, the diagnosis, the steps and the outcome. Runbooks, scripts and post-incident reviews add the method. That's the "how work gets done" record AI companies are paying for.

03Yours versus your clients'

  • Usually yours: runbooks, internal procedures, scripts and tools you wrote, training material, your own PSA and service-desk workflows.
  • Usually your clients': data from inside their environments, their configurations and network details, their users' information.
  • In between: ticket history. Your notes on how you fixed something may be yours; the client details in the ticket aren't. Strip them, and check each contract.

04Security comes first

Leave out anything that would help someone attack a client: credentials, network diagrams, firewall rules, vulnerability details, and unpatched findings. Scan ticket text and attachments for secrets before anything is shared. See Jira and ticketing data for scoping a ticket system.

IT services and MSPs: usually licensable (Runbooks and internal procedures; Scripts and tools you wrote; Resolved tickets, clients removed; Post-incident reviews) versus check first or leave out (Client environment data; Credentials and network details; Vulnerability findings; Client users’ personal data).Usually licensableRunbooks and internal proceduresScripts and tools you wroteResolved tickets, clients removedPost-incident reviewsCheck first, or leave outClient environment dataCredentials and network detailsVulnerability findingsClient users’ personal data
A starting point for scoping, not a legal test.

05Before you apply

  1. Read your MSA and client contracts for data-use clauses.
  2. Separate your own IP from client-environment data.
  3. Scrub tickets of client names, users and secrets.
  4. Have a lawyer read the licence. This isn't legal advice.

06Check which programmes you're likely to match

Our free fit check asks about your size, location, records and tools. The programme decides.

07Questions people ask

Can an MSP sell its ticket data?

It can license ticket history it's entitled to use, with client and personal details removed. Check your client contracts first: many restrict use of information from their environments.

Does Mercor take MSPs?

It publishes no MSP listing. Security-led firms may fit its cybersecurity listing, which asks for alerts, investigations and case write-ups.

What should never go in?

Credentials, network diagrams, vulnerability details and anything that would help someone attack a client.

Sources

Check which programmes you’re likely to matchA few short questions, about a minute. Free, no sign-up. The programme decides who qualifies.trackimpact.io/data →