A fractional CFO's playbook for spotting licensable records at B2B SaaS clients

Why a SaaS-focused fractional CFO is well placed

You already hold a map of every system a SaaS client runs, because each one is a vendor line in your opex review. The AP history shows when the company started paying for Atlassian, GitHub, Zendesk or Gong, which tells you roughly how many years of engineering, support and sales records exist before anyone opens a single tool.

Your calendar also puts you in the right rooms: the monthly close with its deferred revenue rollforward, the ARR bridge for the board deck, the runway model, the annual operating plan and the data room before a raise. Few outside advisers see the cash pressure and the system history at the same time.

The demand side is specific. AI developers training agents for software and support work need connected records of real work: a ticket, the pull request that fixed it, the code review, the deploy, the incident and the postmortem. Records like that sit inside software companies, not on the public web.

Which SaaS clients in your book fit?

CFOs serving adjacent sectors will recognize the pattern from fractional CFOs for MSPs and IT services firms and the professional services records playbook.

The tenant test: what the company owns versus what it hosts

The most important rule for SaaS clients: records of how the company does its own work can be candidates, while data its customers put into the product generally cannot. Customers' documents, transactions and end-user records sit in their tenants under the company's terms of service and privacy commitments. FTC staff have stated that companies' promises not to use customer data for undisclosed purposes, such as training models, are enforceable wherever they were made.

The contractor point comes from copyright law. The Copyright Office's circular on works made for hire explains that work an employee prepares within the scope of employment belongs to the employer, while commissioned work qualifies as made for hire only in listed categories and with a signed written agreement. A SaaS company that relied on outside dev shops should locate its assignment agreements before the conversation goes further.

The six-question SaaS records screen

A clear no on any line means wait, not push.

• Did the company reach 50+ full-time employees at peak, not counting contractors?
• Can someone still export several years of Jira, Git and help desk history, including archived projects?
• Are internal work records clearly separate from customer tenant data?
• Are employee and contractor IP assignments on file?
• Has the company never licensed these records for AI training before?
• Would the CEO or founder consider an exclusive AI-training license for an agreed term?

The company fit checker runs a preliminary, non-binding version with no contact details required, and who qualifies lists the full baseline.

When to raise it in a SaaS client's calendar

On the accounting question, how a license is structured can affect when revenue is recognized. Deloitte's ASC 606 licensing roadmap describes the distinction between a right to access intellectual property over the license period and a right to use it as it exists at a point in time. Bring the client's auditors in early rather than predicting the answer.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

How the introduction runs

1. You get the CEO's agreement to an introduction; no records change hands.
2. You share your referral link so the company applies at sourcex.si/apply, or you submit the referral form.
3. SourceX qualifies the company on size, history, breadth of records and rights.
4. The company builds a data inventory: each system, its years of history and what can be exported.
5. SourceX and the company agree one all-in price and the terms; nothing binds until the company signs.
6. AI labs and data buyers review, the agreement is executed, data is delivered under the agreed redaction rules, and the company receives a one-time payment.

What to say to a SaaS CEO

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 are paid only after the buyer pays and SourceX receives its fee, and no reward is guaranteed.

The reward is a share of SourceX's fee and is never deducted from what your client receives. Before registering, read your engagement letter for conflict and outside-compensation terms, tell the CEO about the reward, and if you hold a CPA license, check your state board's rules on referral fees.

When not to bother

• The product is consumer-facing and the valuable records are mostly end-user data.
• Engineering was outsourced and nobody can find the IP assignments.
• The company never reached 50+ full-time employees at peak, contractors excluded.
• Older Jira or help desk instances were deleted without an export.
• The same records were already licensed for AI training.
• The CEO will not consider an exclusive license.

Next step

Run your SaaS clients through the six-question screen this month. If one passes and the CEO is open, register as a partner and send the referral link; the hub for fractional CFO referral opportunities covers the program in full.