A fractional CFO's playbook for MSPs: separating the MSP's records from client data

Why a fractional CFO sees what MSP records are worth

A fractional CFO for a managed service provider or IT services firm spends much of the month inside the systems where the business actually runs: the PSA for tickets, time entries and agreements, the project board, the quoting tool, the documentation platform and the finance stack. You reconcile agreement revenue to billing, chase unbilled time, measure technician utilization and build the numbers for quarterly business reviews. That gives you a clear view of how much operating history the company has built up and how well it is organized.

That view matters because AI developers training agents for IT operations need records of real service work: the ticket as the user reported it, triage, escalation, the fix, the time spent and whether the problem came back. An MSP with years of well-categorized tickets, documented runbooks and project histories holds that kind of record. The catch, and the reason this playbook exists, is that much of what sits in an MSP's tools belongs to its clients.

Which records belong to the MSP and which belong to clients

Draw the line before anyone mentions licensing.

Recorded help desk calls need their own check. Federal law generally permits recording when one party to the call consents (18 U.S.C. 2511), but California requires the consent of all parties to a confidential communication (Penal Code section 632), and other states set their own rules. Nor can an MSP close a rights gap by quietly rewriting its master services agreement. In a February 2024 post about consumer data (staff guidance, not a rule), FTC staff warned that adopting more permissive data practices, such as using data for AI training, through a surreptitious, retroactive change to terms of service may be unfair or deceptive. The business lesson is the same: ask clients openly where consent is needed. This is general information, not legal, tax or financial advice.

Which MSPs in your book fit

Smaller MSPs that never reached the headcount baseline are not a fit, however good their records. The who qualifies page covers the remaining tests: a documented history of several years, the right to license the records, and someone with authority to sponsor the deal.

The PSA test: five questions before you raise it

• Ownership: can the owner separate the MSP's own records from client-environment data, and do the MSAs allow that separation?
• Depth: does the PSA hold several years of tickets and time entries, with older history preserved if the platform changed?
• Structure: are tickets categorized consistently enough that outcomes can be read without guesswork?
• Sponsor: would the owner, CEO or another authorized person consider an exclusive AI-training license for an agreed term?
• Export: can someone at the MSP actually run exports from the PSA, documentation platform and communication tools?

A clear no on ownership or export ends the conversation for now. Two or more no answers on the other questions means park it and revisit after the next platform or ownership change.

When to raise it in the MSP's year

How the introduction works without touching client data

1. Confirm the owner is interested; share nothing about the MSP before that.
2. Register as a partner and send the owner your referral link, or enter the company in the referral form with a few lines of fit information.
3. SourceX reviews size, history, data breadth and rights with the owner.
4. The MSP completes its own data inventory, listing systems and years of history at a high level.
5. Redaction and de-identification rules, including how client identifiers are handled, are agreed with the MSP before any work begins.
6. The MSP agrees price and terms, AI labs and data buyers review the opportunity, and records are delivered only after the MSP signs and authorizes delivery.

What to say to the MSP owner

Stop there. Do not estimate value, name buyers or promise outcomes. If the owner's first question is about client contracts, that is the right instinct, and SourceX's qualification covers rights.

How rewards work for a fractional CFO

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It comes out of SourceX's fee and never reduces the MSP's proceeds.

If you hold a CPA license or work inside an accounting firm, review the referral-fee and disclosure rules of your profession and state first, and tell the owner in writing that you may receive a reward. The fractional CFO partner page summarizes how the program works for CFOs.

When not to bother

• The MSP's most valuable records are client files, mailboxes or backups, and clients will not consent.
• It runs a white-label help desk or NOC for other MSPs, so the tickets belong to those partners and their clients.
• The PSA was replaced and the old history was never exported.
• The owner will not consider an exclusive license for AI training.
• The company has never reached 50+ full-time employees at peak (contractors excluded).

The same separation logic applies across services businesses; see the records playbooks for professional services firms and staffing firms. MSPs with a software product line also hold engineering records, covered in the B2B SaaS playbook.

Next step

Run your largest MSP client through the PSA test. If it passes, try the company fit checker for a preliminary screen, then register as a partner and send the owner your referral link, or have them apply at sourcex.si/apply.