How a fractional CFO evaluates a data licensing proposal for a client

Why is the fractional CFO the right person to evaluate a data licensing proposal?

A fractional CFO sees the client's contracts, lender terms, close calendar and tax position in one place, which is exactly the set of facts a data licensing proposal touches. The owner usually asks "is this price fair?" The CFO's better question is "what does this do to cash, covenants, revenue presentation, customer obligations and risk?"

This playbook gives a one-page evaluation framework you can run in an afternoon. It covers how to review a proposal, not how to find opportunities; for that, start with the fractional CFO overview.

What is the 5-lens CFO review?

Use five lenses, in this order, and write one line per lens.

How do you assess the cash lens?

Ask for the price in one all-in number. With SourceX, the company gets one all-in price with SourceX's fee included and no separate charges, paid as a one-time payment typically within about 60 days of invoicing once the buyer selects the data. Anything else in an offer, such as staged payments, usage fees or a revenue share, needs a model of its own.

An unsolicited offer needs the same discipline; see how to evaluate an unsolicited offer to buy your company's data for the extra checks on who the buyer is and what the offer actually permits.

What should the accounting lens cover?

The central issue is how the license is structured. Under ASC 606, a license of intellectual property is assessed as either a right to access over time or a right to use at a point in time, and the answer can change when revenue is recognized; the Deloitte ASC 606 licensing roadmap walks through the distinction. The Journal of Accountancy reported on FASB's licensing clarifications in ASU 2016-10, which is a good orientation. This is general information, not legal, tax or financial advice. Confirm treatment with the client's auditor, because the draft agreement's terms drive the conclusion.

Practical prompts for the auditor conversation:

• Is the license of a delivered snapshot or of something that continues to change?
• Are there any post-delivery obligations from the company, such as support or refreshes?
• Should the amount be shown outside core recurring revenue?

How do you check covenants and contracts?

Start with documents, not data. Pull the credit agreement and test whether a one-time inflow is excluded from covenant definitions or triggers a mandatory prepayment. Then screen the client's top customer agreements for confidentiality terms that touch the records in scope; the page on whether a client NDA stops you from licensing records about them covers how the company's own team screens archives. Customer data inside emails and shared drives is the usual blocker, and exclusion or redaction is the usual fix.

Which one-page template do I use?

Copy this structure into the client file:

1. Proposal summary. Stage, parties, scope in one sentence, term, exclusivity.
2. Cash. Amount, trigger, expected date, risks.
3. Accounting. Draft treatment, auditor contacted (yes/no), open questions.
4. Tax. Entity, owners, estimated-tax impact, adviser engaged.
5. Covenants and contracts. Lender check, customer check, outcome.
6. Risk and cost. Counsel fees, internal hours, redaction plan.
7. Recommendation. Proceed, proceed with conditions, or decline, plus a decision date.

When should the CFO raise it with the owner?

What does the risk and cost lens look like in practice?

Put numbers on effort before the owner gets excited. List counsel review hours, the internal staff time needed to build the data inventory, any redaction support the company will fund, and the length of the exclusive term. A deal typically exclusive for AI training for an agreed term means the same records cannot be licensed to others for AI training during that period, so check the term against any other plan for the archive, such as a sale process or a second license.

Then name the downside cases. Ask what happens if a buyer declines, if counsel finds a customer restriction midway, or if the owner changes their mind. Because nothing is binding until signature, the cost of stopping early is limited to your hours and counsel's, which is worth saying plainly to the owner.

What to say

What does the referral process look like?

You make the introduction and give basic fit information only. You never export, upload or describe confidential records. SourceX qualifies the company, the company completes a data inventory, price and terms are agreed, buyers review, and the deal closes, data is delivered and the company is paid. The partner reward is paid after SourceX receives payment. For deal mechanics see how to negotiate an AI data licensing deal, and for the buyer-side route question see data marketplace listing vs managed data licensing. A ready-made email is in the introduction templates for fractional CFOs.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. Check your own professional rules on referral fees, disclosure and independence first, particularly if your firm provides attest services.

When not to bother

Do not run the review for a client with fewer than 50 full-time employees at peak (contractors excluded), no clear rights to license, or no authorized sponsor. Also stop if the records are mainly someone else's data held without consent.

Next step

If a client passes your review, register as a partner and introduce them. Use the data inventory builder for the metadata-level list of systems, and read the pros and cons of licensing company data with the owner.