What is a metadata-only PSA ticket history inventory template for MSPs?

When to use this PSA ticket history inventory

Use this template when an MSP owner or service director is curious whether years of PSA tickets could be licensed, but nobody wants to export a single ticket to find out. Every field below is metadata: counts, years, categories and yes/no flags. The MSP fills it from the PSA's own reports, and the sheet can be shared in an introduction without exposing a client name or ticket text.

The template is vendor-neutral. ConnectWise, Autotask, HaloPSA and similar tools each have their own report builders, so adapt the report names to your tool and check its documentation for how to produce the counts.

The template

Copy the block below into a spreadsheet. One row per year, plus the summary rows at the end.

How should an MSP fill each section?

Round counts rather than exact totals. A range such as "40,000 to 60,000" is enough, and nothing in the sheet should let a reader identify a customer.

What do the results mean?

Many MSPs have dozens of tickets for one client problem. What matters is the pattern: a problem report, triage, an escalation and a closing note that explains the fix. Compare with the way engineering firms pair commits with reviews in git history vs a code snapshot, or how dispatch decisions are kept in dispatcher decision records.

What should never go in the sheet?

• Client names, contact names, email addresses, hostnames or IP addresses.
• Ticket text, attachments, screenshots or passwords.
• Any reward figure or promise of payment.
• Estimates of what the data is worth.

Partners make introductions and give basic fit information only. Partners never export, upload or describe confidential records.

Illustrative example

Illustrative: a fictional 90-person MSP fills the sheet and finds nine years of history, resolution notes on most tickets in the last six years, three clients with restrictive terms and two older PSAs archived. The service director flags the restricted clients as out of scope and the owner agrees to an introduction. The partner never saw a ticket; the sheet held only counts and flags.

Follow-up timing

1. Send the filled sheet only after the sponsor agrees to an introduction.
2. If no reply in a week, send one short follow-up to the sponsor.
3. After that, leave the lead; the MSP can also apply directly from the referral link.

How rewards work

Rewards are 25% of the eligible platform fees SourceX actually collects, capped at $100,000 cumulative per referred company, and become payable only after the buyer pays and SourceX receives its fee; no reward is guaranteed. Because the reward is a share of SourceX's fee, it is never deducted from what the company receives.

Related reading

The service-business screening style used here is explained in the MSP referral guide. Companies also holding safety paperwork can read about near-miss and incident reports. Acquirers of finance-side businesses can compare screening approaches in equipment finance company acquisitions, and the specialty contractor roll-up guide describes how sponsors run a screen across a portfolio.

Next step

Once the sheet is complete, check the MSP with who qualifies or the data inventory builder, then register as a partner to make the introduction.