How EOS implementers can refer clients for data licensing without losing neutrality
EOS implementers can refer clients to SourceX when a leadership team runs a US company with 50+ full-time employees at peak (contractors excluded), several years of system history and records it owns. Disclose any referral reward first, offer it as an Issues List question the team can IDS, and let the Visionary and Integrator decide whether to explore.
Where an EOS implementer fits
EOS implementers can refer clients to SourceX when a leadership team runs a company that holds years of its own operational records, and the referral works best as a question the team decides rather than a recommendation. You disclose your interest, the Visionary and Integrator choose whether it belongs on the Issues List, and if they want to explore, SourceX works with them directly.
Few outside advisors see a company the way you do. Every quarter you sit with the full leadership team, you know the Accountability Chart seat by seat, you see which systems feed the Scorecard and you know which core processes are documented and followed by all. That is enough to judge whether a client might interest AI labs and data buyers, without ever looking at a record.
Narrowing your client book with EOS tools
Not every client will fit. Use what you already see in sessions to narrow the list.
| EOS tool | What it tells you | Fit signal |
|---|---|---|
| Accountability Chart | Seats and headcount by function | 50+ full-time employees at peak, contractors excluded |
| Scorecard | Which systems produce the weekly numbers | CRM, help desk, ERP or project tools with years of history |
| Documented core processes | Whether the way work gets done is written down | SOPs, checklists and handoffs that show real workflows |
| Issues List and IDS habits | Whether problems, decisions and outcomes are recorded | Decision records with outcomes attached |
| V/TO 10-year target and 3-year picture | The owner's horizon: growth, succession or exit | A reason to weigh a one-time payment |
| Rocks | Planned migrations or tool retirements | A moment to preserve exports before history is lost |
The 50-5-10 strength filter
Run a three-number filter before you raise anything. Only the first number is a hard line; the other two tell you how strong a candidate is. Then check rights and sponsorship.
- 50: the company reached 50+ full-time employees at peak (contractors excluded).
- 5: it has five or more years of records. SourceX asks for several years of documented operations, and histories of 5-10+ years make a company stronger.
- 10: its records sit across ten or more systems. Strong companies tend to keep records in 10-15+ systems: email, Slack or Teams, shared drives, CRM, finance, support, engineering and operations tools.
- Rights: the records describe the company's own work, not mainly clients' material or consumers' personal data.
- Sponsor: the owner, CEO, CFO or an authorized representative would consider an exclusive license for an agreed term.
The who qualifies page has the full baseline. Clients whose output belongs to their customers, such as many agencies, need extra care; the agency owner playbook explains why.
Issue, not pitch: bringing it into a session
The leadership team owns its Issues List, so the idea should reach it the same way any other issue does.
- Disclose first, in writing, to the Visionary and Integrator, outside a session.
- Offer it as a question: do our records have value outside the business, and do we want to find out?
- If they want it on the list, they add it. You facilitate IDS as usual: identify which records and rights are involved, discuss, then solve.
- A typical solve is a Rock owned by the Integrator or CFO, such as completing a fit check and a data inventory this quarter.
- Step back from the solve if your interest could look like steering, and let the team own every decision.
The IDS example on deciding whether to license company records shows how that discussion can run.
When to raise it in the EOS calendar
| Session | Fit | How to handle it |
|---|---|---|
| Focus Day | Poor | The team is still learning the tools; leave it |
| Vision Building days | Possible | Only if the owner raises growth, succession or exit |
| Quarterly session | Good | After disclosure, if leaders have added it to the Issues List |
| Annual planning | Best | As a candidate Rock for the coming quarter |
| A Rock to replace a core system | Urgent | Suggest a full export before the old system is retired |
| Check-in calls between sessions | Good | Use them for the private disclosure conversation |
The guide to putting data assets on the Issues List at annual planning covers that session in detail.
Keeping your facilitator role clean
Your value to a leadership team rests on neutrality. A referral reward is a financial interest in one possible outcome, so handle it in the open.
- Tell the Visionary and Integrator in writing before the topic reaches a session.
- Explain who pays: SourceX, from its own fee, never deducted from what the company receives.
- Make it easy to say no, and do not raise it again if they pass.
- Do not take ownership of a Rock connected to the license.
- If you work under an agreement with a franchisor or coaching organization, check whether it addresses outside referral compensation.
Why owners are open to the conversation
Implementers work with owner-led teams that set 10-year targets, and succession is often part of that picture. McKinsey's report on the great ownership transfer estimates that about six million US small and medium-size businesses will face ownership transitions by 2035, and that more than half of US small-business owners are over 55.
An owner working on succession has good reason to know what the company owns besides its revenue. Records of real work are one such asset: AI developers training agents to carry out multi-step tasks need examples of workflows, decisions and outcomes that exist only inside companies.
How the introduction works
- The leadership team decides to explore after an IDS or a private conversation.
- You register as a partner and either share your referral link, which sends the company to sourcex.si/apply with your credit attached, or submit the company through the referral form.
- SourceX qualifies the company with its sponsor on size, history, data breadth and rights.
- The Rock owner completes a data inventory listing each system and its years of history.
- Price and terms are agreed: one all-in price with SourceX's fee included, and nothing binding until the company signs.
- Buyers review, the deal closes and the data is delivered under redaction rules agreed before work began; the company receives a one-time payment.
- SourceX pays your reward after it receives its fee.
You never export, upload or describe client records at any point.
What to say to the Visionary and Integrator
There are written versions in the introduction email templates for EOS implementers.
How rewards work for implementers
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 meeting, a qualification call or a signed agreement alone does not trigger payment, and no reward is guaranteed.
A few well-qualified clients matter more than a long list. Each referred company is assessed on its own, and the reward is a share of SourceX's fee rather than anything taken from the client.
When not to bring it up
- The company never reached 50+ full-time employees at peak (contractors excluded).
- Its records mostly belong to its clients, and those clients have not agreed.
- Most of its data is consumer personal information or patient records.
- The leadership team is still working through Right People, Right Seats and has no one to own an inventory.
- The owner wants to generate records with AI to sell them, or nobody can export the data.
Implementers who also take consulting work can compare notes with the management consultant playbook.
Next step
Run the 50-5-10 filter across your current clients this week; the network opportunity finder helps structure the list. When a leadership team wants to explore, register as a partner and share your link, or have the Integrator apply directly at sourcex.si/apply.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Does referring a client conflict with an EOS implementer's role?
It can if handled badly. Your value rests on facilitating without steering, so disclose the referral relationship in writing before the topic reaches a session, let the leadership team decide whether it belongs on the Issues List, and step back from the solve if needed. If the team passes, drop it. The reward comes from SourceX's fee, never from the client's proceeds.
How many of my clients are likely to qualify?
It depends entirely on your book. The hard requirements are a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license its records and an authorized sponsor. Clients with long histories across many systems and documented core processes are the strongest candidates; smaller or younger clients will not qualify yet.
Can exploring a data license become a Rock?
Yes, if the leadership team chooses it. A sensible Rock is narrow and measurable, such as completing a fit check and a data inventory by the end of the quarter, owned by the Integrator or CFO. The licensing decision itself stays with the owner, and nothing is binding until the company agrees price and terms and signs.
Which records from an EOS company tend to interest AI buyers?
Records of real work with outcomes: support tickets and how they were resolved, CRM history with won and lost deals, project files, engineering work, approvals and the SOPs behind core processes. Developers training AI agents to carry out multi-step tasks value these because they show how work actually gets done, and they are scarce on the public web.
When exactly is the implementer's reward paid?
Only after the buyer pays and SourceX receives its fee. An Issues List discussion, a qualification call or even a signed license does not trigger payment on its own. The reward is 25% of the eligible platform fees SourceX collects from that company's deals, capped at $100,000 per referred company, and no reward is guaranteed.
Related pages
- Which US businesses are a fit for a SourceX data licensing introduction
- Referral opportunities for agency owners
- An EOS IDS example: should we license our operating records?
- EOS annual planning: how implementers can put data assets on the Issues List
- Introduction email templates for EOS implementers and business coaches
- Referral opportunities for management consultants
Free resources
- Operational data inventory builder — List systems, record types, years held and owners.
- AI readiness assessment — Ten questions, five dimensions, a score out of 100.
- EBITDA calculator — Reported and adjusted EBITDA from net income.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment