Which professional relationships can surface company-owned operational records?
The ones that see the owner and the systems in the same month. Operational records, such as tickets, approvals, exceptions, project histories and the email around them, are not published anywhere. They sit inside a company's ERP, CRM, helpdesk and mailboxes, and the only people outside the company who know they exist are the professionals hired to work on them or on the business that owns them.
Most roles see only half the picture. An IT partner may know the helpdesk holds a decade of tickets and never meet the owner. A business lawyer meets the owner every quarter but has no idea what the ERP holds. The strongest introductions come from roles that see both, or from two professionals who compare notes, each staying at metadata level.
The relationship map
Editorial assessment, not survey data. "Typically" means the usual scope of the engagement, not any individual's knowledge.
| Relationship | Reaches the owner | Sees the systems | Record types typically in view (metadata only) | Moment it tends to come up |
|---|---|---|---|---|
| Outside accountant or CPA firm | Yes, at year end and in planning | Partly: finance systems | General ledger history, close and reconciliation workflows | Annual planning, audit or tax review |
| Fractional CFO | Yes, as part of the leadership team | Yes: finance and reporting | Approvals, forecasts against actuals, vendor and pricing decisions | Budgeting, board reporting, exit planning |
| ERP consultant | Sometimes, through the sponsor | Yes, in depth | Orders, purchase exceptions, change history | Implementation, upgrade or replacement |
| Managed service provider | Rarely; usually the office or IT lead | Yes: tenant, tickets, backups | Ticket history, mailboxes, document stores | AI readiness, migrations, renewals |
| Business attorney | Yes, on contracts and disputes | No | Knows which contracts restrict reuse, not what records exist | Contract reviews, restructuring |
| M&A advisor | Yes, during a process | Through the data room | Diligence lists of systems and record sets | Sell-side preparation, carve-outs |
| Private equity operating partner | Yes, at board level | Through portfolio reviews | System inventories across several companies | Value creation plans, portfolio reviews |
| Commercial banker | Yes, on financing | No | Knows company size and history, not records | Refinancing, covenant reviews |
Two patterns stand out. Roles with system access but weak owner access, like ERP consultants and MSPs, usually need the project sponsor to carry the question upstairs. Roles with owner access but no system view, like lawyers and bankers, can open the door but should not describe the records beyond what the owner tells them. The MSP AI services guide and the Copilot readiness assessment show how system-side work produces the inventory; data catalog vs data inventory explains what that inventory does and does not prove.
Why AI data companies now pay for introductions
Because the records are private, buyers cannot find them by searching. They need someone who already has the relationship. Public evidence of this, checked on 2026-10-18:
- micro1's company-referral page, checked 2026-10-26, pays $50K for enterprise data partnerships up to $700,000 and 7.5% of the deal value above that, and $75K for defunct-company partnerships up to $1 million and 7.5% above, with no published cap above those thresholds.
- micro1 announced on 2026-10-09 a commitment to spend $1 billion on enterprise operational data acquisition over 12 months. That is a company announcement, not evidence that the money has been spent or that any given company's data will be bought.
- Mercor's data page says it licenses business workflow data and pays the business, that participation is opt-in, and that a referral to a company that becomes a paid partner earns a bonus. It does not publish a numeric company-referral reward. Mercor has also advertised for contractors to identify companies with valuable operational data.
SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Its default referral reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months pay 15%. A higher advertised figure does not establish higher expected earnings; compare the calculation base, any floor or cap, the minimum deal size, eligibility, the payment trigger and the written terms. The Mercor comparison and micro1 comparison do that side by side.
How to map your own network
SourceX has not published interview or cohort data on which relationships produce qualifying introductions, so treat the map above as a starting hypothesis. A partner can test it on their own client list in about an hour:
- List active clients with 50+ full-time employees at peak (contractors excluded).
- For each, mark whether you personally reach the person who could authorize a licensing discussion.
- Mark whether you know, at metadata level, which systems hold the company's operating history and for how many years.
- Note any documented event in the next year: a migration, a retention deadline, a sale process.
- Clients with all three marks are where a short conversation makes sense. Clients with only one mark need a colleague who holds the other.
If SourceX publishes interview data on this, the useful measures would be which role made the introduction, whether the owner opted in, and how many introductions reached a verified application. Until then, no conversion figures are available. The network opportunity finder runs a similar screen, and warm introductions vs cold outreach explains why the relationship matters more than the list.
Which companies qualify, and who decides?
The company decides whether to proceed, and SourceX's review decides whether its records fit. Before introducing, a partner should know four things at metadata level: which records exist, roughly how much and over how long, which systems hold them, and who owns them and can authorize a discussion. Contract restrictions on reuse are for the company's counsel. Dataset selection, price and timing stay unknown until SourceX reviews the opportunity. Partners never ask for or handle raw client records.
Eligibility is on who qualifies: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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. Attribution goes to the first valid introduction within the 90-day window once the company submits a verified application, and partners sign the Channel Partner Agreement before submitting.
The company's compensation and the partner's reward are separate. SourceX pays the company for its data and funds the reward on top. Illustrative only: if SourceX actually paid a company $250,000 on its first qualifying transaction, the reward would be $62,500; at an $800,000 payout it would be $120,000, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards) explains. Role-specific guides cover accountants, fractional CFOs, ERP consultants, business attorneys, M&A advisors, operating partners and commercial bankers. More guides are in the guides hub.
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 map shows a client where you reach the owner and know where the records live, register as a partner, check the company against who qualifies, and read the program terms before raising it.
What should an adviser know about AI data economy opportunities?
For an adviser, the AI data economy offers a choice of role before it offers any income. If you already see a client's owner and its systems, you can introduce the company to a licensing counterparty, advise the company through a licensing process for a fee it pays you, or, less often, license your own firm's records. Each role tests a different duty: disclosure, independent advice or client confidentiality. Choose one per client, and only after the client asks.
The statements below carry different weight. Program facts come from SourceX's published terms and screening page, checked 2026-10-26: the referral reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, repeats within the 12-month Repeat Window pay 15%, and a lead, meeting or signed agreement alone earns nothing payable. Whether a client is accepted, what it licenses and what it is paid are conditional, settled only in SourceX's review and signed agreements. Our thesis, which nobody has measured, is that an adviser's most durable gain here is client value: being the person who explained an option the owner had not heard of, whether or not a deal follows.
| Term | Meaning on this page |
|---|---|
| Introducer | The adviser who, with the owner's permission, connects the company's CEO with SourceX and is credited as its referral partner |
| Paid adviser | An adviser the company engages and pays to help it decide on, and work through, a licensing process |
| Direct participant | An advisory firm that applies as a supplier with records about its own operations |
| Context | What an adviser knows about why records exist, which systems hold them and who runs those systems, passed on only at metadata level |
What an adviser knows that an application form cannot capture
An application tells SourceX what a company says it holds. An adviser who has worked inside the business often knows why those records exist and whether they hang together, which is the part a form cannot ask.
| Context an adviser often holds | Why it matters in a licensing review | Pass it on only when |
|---|---|---|
| The process behind the records, such as how a claim, order or project actually moves | Records with a visible decision path are easier to scope than an export with no story | The owner agrees, and only as a description, never as samples |
| Which years are complete, and where a system change broke the history | Depth of operating history is part of fit | It can be stated as a span of years and a system name |
| Who administers each system | Export and preparation later run through that person | The administrator knows the question may come |
| Events already scheduled, such as a migration, an archive deletion or a sale | A dated event is real timing; a quarter-end is not | The event is already known inside the company |
| The owner's own view of the idea | Nothing proceeds unless the CEO wants the conversation | Always, because it comes first |
That context turns a cold application into a permissioned introduction. The CEO hears the idea from someone they trust, the adviser passes on only what the owner has agreed to share, and SourceX starts its review with a described company rather than a name. It is also where advisers overstep. A description of a process is context; a screenshot of a ticket queue is a record. A partner never needs to export, upload or describe confidential records, and partners never ask for or handle raw client records.
Introducer, paid adviser or participant: how the three roles compare
The three roles are not steps on one ladder. They are alternatives, and for most clients only one of them is open.
| Question | Introducer | Paid adviser to the company | Direct participant |
|---|---|---|---|
| What you do | Ask the CEO, then connect the company with SourceX | Help the company decide and prepare: a record inventory, coordination with its own counsel, a read of proposed terms | Your own firm applies as a supplier |
| Who pays you, and for what | SourceX, a reward on the company's first qualifying transaction of the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, only once the program's payment conditions are met | The client, under your engagement letter, for your time | SourceX pays your firm for its own licensed records under the firm's own agreement |
| The duty it tests | Disclosure of the reward, and your profession's rules on referral payments | Advice the client can rely on, uncolored by any payment from the other side | Client confidentiality, because most of a firm's files describe clients |
| What rules it out | Your rules bar a referral payment for this client, or you cannot disclose it | You also hold an undisclosed reward interest in the same company | The records worth licensing belong to clients, or the firm never reached 50 full-time employees |
| Fits best when | You reach the owner and the licensing work sits outside your service line | The client asks for hands-on help you are qualified to give | The firm has years of its own methods, QA and internal operating records |
An adviser paid by the client who also stands to receive a reward from the counterparty holds a conflict that must be disclosed and, in some professions and client relationships, cannot be cured at all. AICPA guidance on members' professional responsibilities lists disclosing any commission or referral fees to the client, and maintaining client confidentiality, among a member's duties. A workable default is one role per company, unless your professional rules allow both and the client agrees in writing. The referral fee rules by profession table collects the primary rules; if your firm performs attest work for the company, start with the attest-client independence check.
The client-trust boundaries that decide which role is open
Five lines hold whichever role you take.
- Consent before names. SourceX hears a client's name, size or systems only after the owner agrees, and the owner's agreement is to a conversation, not to licensing anything.
- Engagement access stays in the engagement. Admin rights in an ERP or audit fieldwork are not a way to size records for licensing. Describe what the owner or the system administrator tells you. The consultant's guide to raising it mid-engagement sets out the walls in detail.
- The CEO decides. Authority to open licensing talks, and to sign, sits with the CEO. A CFO or controller can sponsor the idea and prepare the case, but does not replace that decision.
- No numbers you cannot stand behind. Do not quote a price, a timeline or a likely payout. A Dataset Deal Confirmation fixes the exact dataset, net payout and terms; anything said earlier is indicative at best. The permission guide has wording for the first ask.
- Client property ends the question. If the most interesting material belongs to the company's clients, it is usually not a fit, and no role changes that.
Three ways an advisory practice could respond (scenarios, not forecasts)
These scenarios describe how a practice might look over the next two years. They are built from the program terms and the duties above. None is a forecast, and SourceX has not published data on how often advisers' introductions lead to licensed datasets.
| Scenario | What changes in the practice | Who pays the adviser | Assumption that must hold | What would change the recommendation |
|---|---|---|---|---|
| A. Occasional introducer | Nothing in the service line; the question comes up in planning meetings with clients that pass the size test | SourceX, under the terms, if a client is paid | A few clients pass size, history and rights checks, and the adviser's rules allow a disclosed referral payment | Several clients ask for hands-on help, which points to scenario B |
| B. Data-readiness adviser | A client-paid service helps owners inventory their records and frame rights questions for any licensing counterparty | The client, by engagement | Clients will pay for the help; no published data shows that they will | Clients want only the introduction, or the conflict with a referral payment cannot be cleared |
| C. Network convener | The firm teaches peer professionals to recognize context, and each relationship owner makes their own ask | Each relationship owner separately; the convener only where it is the credited partner | Members' rules allow it and credit is agreed before anyone contacts a CEO | Two members claim the same company, or clients start to feel marketed to |
Scenario A leaves the business model alone. The value to the client is the option itself, and any reward is incidental. Illustrative arithmetic: if SourceX actually paid an introduced client $40,000, below the USD 100,000 Minimum Transaction, no reward would be due unless SourceX agreed in writing; at $400,000 the first qualifying transaction would pay $70,000, and a further qualifying transaction first agreed within 12 months would pay 15% of its payout, with no cap. SourceX funds the reward separately, so it never comes out of the client's payout.
Scenario B is the one that changes the business, and the one most exposed to conflict. A firm advising a client through licensing is usually better off not being that client's introducer as well; the client advisory services examples show how such work is usually scoped. The free data inventory builder gives a client a no-upload list of what it holds, which is often enough to tell whether paid help is warranted.
Scenario C rests on the attribution rule, under which a network of conveners still yields one credited partner per company: the convener whose valid introduction came first in the 90-day window, credited as of the company's verified application, with duplicates sent to review. A convener who has not settled credit inside the network before the first call has built a dispute, not a channel.
A ten-client trial before you pick a role
Run this before any public change to the practice. It takes one quarter of meetings you already hold.
- Choose ten clients you will see in the next quarter that you believe reached 50 or more full-time employees at peak, contractors excluded, and have operated for several years.
- Clear your own rules first: engagement letters, your profession's referral payment rules and any attest relationship. Mark each client where the introducer role is closed.
- In a meeting already on the calendar, ask one neutral question rather than a pitch: "Some companies now license their own operating records for AI training. Is that something you would want to hear about?"
- Log five fields per client: the answer (yes, later or no); whether you reach the CEO; whether the records are the company's own; which help the client asks for (an introduction, hands-on help or nothing); and minutes spent.
- Read the log, not your hopes. Mostly requests for an introduction: stay an introducer. Two or more requests for hands-on help you can give without a referral conflict: test the paid adviser role with one client. A conflicts column that fills before the answers do: fix engagement terms before any introduction. Mostly no: the option is now on record, so revisit when a client mentions a migration, a sale or an archive deletion.
The threshold of two is a working rule for a small trial, not a benchmark. Fractional finance leads and IT providers can adapt the question to their own meetings; see the pages for fractional CFOs and managed service providers.
The case where the answer is none (Illustrative). A 14-person CPA firm's strongest candidate is a 260-person distributor whose financial statements it audits. The introducer role waits on the firm's ethics review of an attest client. The paid adviser role would need an independence check of its own. The firm itself, at 14 people, fails the size test for direct participation. The right role for this client today is none, and the trial log records why. The trial still worked: it stopped a conflict before it started.
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 trial turns up a client that wants the introduction, whose CEO you reach and whose records are its own, sign the SourceX Channel Partner Agreement when you register as a partner, measure the client against who qualifies and review the program terms before you make the ask. More role guides sit in the guides hub.