This is for fractional CFOs, outsourced accounting firms and practice leaders whose daily counterpart at a client is its in-house controller. "Controller" here means the finance role, not the privacy-law sense of the word.
Why the controller is the natural first conversation and never the last
The controller lives with the company's operating history: the close, approval chains, vendor files, the systems that feed the ledger. That is why controllers are often the first to wonder aloud whether all those years of records might interest an AI developer, and why an adviser who works beside them notices the same thing.
None of that makes the controller the decision-maker. Under the program, the CEO opens a licensing discussion and signs for the company. A controller can raise the idea, prepare the company's own case and champion it internally, and SourceX's screening page treats an introduction its decision maker never heard about as usually not a fit.
The controller also has duties of their own. If they are a member of the Institute of Management Accountants, IMA's Statement of Ethical Professional Practice asks members to keep information confidential unless disclosure is authorized or legally required, and to mitigate conflicts of interest and notify the parties affected by potential ones (our paraphrase). That is one more reason never to ask a controller to describe the company's records to an outsider, you included.
| Person | Role in this conversation | Never asked to |
|---|---|---|
| The controller | Raises the idea, says how the CEO would want to hear it, prepares the company's case if the CEO asks | Authorize a licensing discussion, sign, or send records outside the company at your request |
| You, the adviser | Explain what SourceX publishes, disclose your own interest, introduce the company once the CEO agrees | Review, count, export or forward the company's records, or use engagement knowledge to make a case |
| The CEO | Decides whether the company talks to SourceX at all, and signs | Decide on a timetable set by you or the controller |
| SourceX | Decides fit and credit after its own review | Be spoken for: the sample agreement says a partner may not commit SourceX to prices, licenses or payouts (section 7.1) |
Three checks before SourceX is mentioned
1. Your own pay question. Settle whether this introduction may be paid, and how, with your board, professional body, firm or counsel, before the controller hears a word. The AICPA observes that "The vast majority of state boards of accountancy have adopted the AICPA Code of Professional Conduct within their state accountancy laws or have created their own," and its page lists, among members' duties, disclosing commission or referral fees to the client and disclosing conflicts with the client's consent (our paraphrase). Which rules reach you depends on your services to this client and where you are licensed; the applicable-rules review walks through both. If your firm audits, reviews or compiles for the client, start with the audit separation map.
2. An unpaid route, chosen in advance if you need one. Two exist. The company can apply to SourceX itself with no partner involved; then no partner is credited and no reward exists to pay. Or you can introduce it without a reward, but the published terms do not say how SourceX handles a partner who wants none, so SourceX decides and you ask in writing first, as the unpaid path for finance professionals sets out. Either way the company's money is untouched: section 4 of the terms has SourceX pay any reward separately, so the company receives the same amount with or without you.
3. Earlier contact. Ask the controller whether anyone at the company has already applied, opened an account or exchanged emails with SourceX. Section 3 of the terms treats any of those as an existing relationship, which makes the company a duplicate that no later partner is credited for. If the answer is yes, the company carries on directly and your part ends there.
The controller-to-CEO escalation script
| Move | Who speaks | Purpose | What never enters |
|---|---|---|---|
| 1. The opener | You, to the controller | Name the idea, say who decides, disclose your interest | Figures, record counts, system lists, any estimate of value |
| 2. The controller's questions | The controller, then you | Answer the five questions controllers ask, and stop at each line below | An archive index, a sample, a screenshot |
| 3. The route | Both of you | Agree how and from whom the CEO hears it | A plan to keep the CEO out until "we know more" |
| 4. The decision | The CEO | Yes, no or not now, in the CEO's own words | Follow-up pressure after a no |
Move 1, the opener. "Something outside our usual work. SourceX licenses records that companies created themselves, for AI training and evaluation, directly from the company. Whether your company ever looks at it is [CEO]'s decision, not yours or mine. Would [CEO] want to hear about it, and from whom?" Then the disclosure you settled in check 1, in the same words you would use with the CEO.
Move 2, the controller's questions.
- "Do I need to pull anything together?" No. Nothing leaves the company at this stage. If the CEO wants to explore, the company applies and describes its own records to SourceX.
- "Is this mine to approve?" No. The CEO decides; you can tell the CEO what you think of it.
- "What is in it for you?" The disclosure from check 1, repeated plainly.
- "Can I send you the archive list so you can tell me if it is worth it?" No. You do not review the company's records for SourceX or anyone else, and section 4.2 of the sample agreement gives a partner no authority to share a supplier's records. SourceX judges fit in its own review.
- "Should we hold this back from the CEO until we know more?" No. The CEO hears first, or nothing happens.
Move 3, the route. Three routes, chosen by what the controller says the CEO would prefer:
- A. The controller raises it, forwarding the note below.
- B. You raise it together in a meeting the CEO already attends.
- C. You write to the CEO, with the controller's knowledge.
If the controller would rather not raise it and your engagement gives you no direct line to the CEO, stop and record "no route". If your role already puts you in front of the CEO, as a fractional CFO's often does, tell the controller you intend to mention it there; their view is noted, and the decision still belongs to the CEO.
The note for the CEO.
[First name], [controller's name] and I talked about something outside our usual work. SourceX licenses business records that companies created themselves, for AI training and evaluation, dealing with the company directly. Whether your company explores it is your decision; SourceX decides whether anything fits after its own review, and nothing is promised. [The disclosure line settled in check 1.] Any reward SourceX pays an introducer comes from SourceX separately and is never taken from what a company receives. Nobody needs files, figures or exports to answer a first question. If you want to know more, reply to either of us; if not, that is the end of it.
Move 4, the decision. A yes leads to the route settled in check 1: an introduction, confirmed in writing as the double opt-in pattern describes, or the company applying on its own. A no is recorded with its date and the CEO's words, and nobody raises it again unless the CEO does. A new CFO arriving later does not reopen it either; the conversation after a founder hires a CFO covers that timing.
What the company would need to show, and what nobody knows yet
The company itself, not you, will show SourceX whether it fits: a peak full-time workforce of 50 or more with contractors excluded, operating records it built up over a documented history, legal room to license them, and a CEO keen on the discussion. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
Finance records carry their own rights questions, from customer details to employee information, and SourceX's screening page lists material owned by the company's clients among its usual poor fits. Rights review is SourceX's work with the company, never the adviser's pre-screen. Three things stay unknown until SourceX reviews an application: whether the records match a current program, whether contracts restrict their reuse, and what any license would cover.
Role and jurisdiction checks
| Your position | What it changes in this conversation | Who answers |
|---|---|---|
| Outsourced firm running the close or the books | Your ledger access exists for the engagement; commission and referral-fee rules may reach you | Your firm's ethics partner, your board or counsel |
| Firm that audits, reviews or compiles for the client | Independence and fee rules of their own apply before anything else | Your firm's ethics function, then your board or counsel |
| Fractional CFO with the controller reporting to you | You may owe the company duties as its officer; route C is usually the natural one | Your counsel |
| Licensed in more than one state | Each license is checked on its own; one answer never transfers to another | Each board's published rules |
| Controller is an IMA or AICPA member | Their own confidentiality and conflict duties shape what they can say to you | The controller, with their own adviser |
One escalation from start to finish (Illustrative)
An invented case; no rule's content or outcome is implied.
A 160-person regional engineering firm uses an outsourced accounting practice for its monthly close, and the in-house controller is the practice leader's daily contact. During year-end planning the controller asks whether "fifteen years of project files" could interest AI developers.
- Checks. The practice leader's earlier review with the practice's counsel settled that, for this client, the company would apply on its own with no introduction. The controller confirms nobody at the company has contacted SourceX.
- Move 1. The practice leader gives the opener and says she will not be introducing the company or receiving anything.
- Move 2. The controller offers to send an index of the project archive. The practice leader declines and explains that SourceX reviews applications itself.
- Move 3. The controller prefers to raise it with the CEO at the next leadership meeting, using the note.
- Move 4. The CEO asks for SourceX's public pages and later decides the company will apply. The practice leader files a dated note and has no further part.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If your checks open a paid or unpaid introduction, register and sign the Channel Partner Agreement before Move 4, compare the company's public facts with who qualifies and read the program terms on credit and duplicates; other finance-adviser workflows are in the guides library.