# Industry expert data referral advantage, tested | SourceX

Canonical: https://refer.sourcex.si/guides/the-industry-experts-who-can-find-ai-data-opportunities-first
Last updated: 2026-11-04

A specialist's head start is recognition. An ERP implementer or a claims auditor can hear an offhand remark about an old system and know it implies years of company-owned records, before a generalist network notices. The head start counts only if three gates also open: the specialist can reach the CEO, their professional rules allow a referral, and the records belong to the company rather than its clients. SourceX has not published interview results on which specialists do this best; this page gives the test and the interview method.

The reader decision is practical: which experts in your network to brief first, what to ask them to listen for, and when their advantage is real enough to act on.

## Three kinds of claim on this page

| Claim | Status | Basis |
|---|---|---|
| A company a specialist introduces must have reached 50+ full-time employees at its peak, contractors not counted, and needs operating history it can document, rights to license and an authorized contact | Program fact | SourceX terms and who-qualifies page, checked 2026-10-26 |
| Credit is never split: one partner per company, namely whoever made the first valid introduction, confirmed when the company's verified application arrives within the 90-day attribution window | Program fact | SourceX terms |
| Whether a company a specialist spots is accepted, what it licenses and whether any reward follows | Conditional | Decided only in SourceX review and a signed agreement |
| Specialists recognize qualifying records earlier and more precisely than generalist networks | Thesis | Not measured; the interview protocol below is how to test it |

| Term | Meaning here |
|---|---|
| Recognition | Hearing a routine remark and knowing which records it implies, how many years they span and which system holds them |
| Reach | A path to the CEO, who authorizes a licensing discussion and signs for the company |
| Clearance | Freedom under the specialist's professional rules and engagement terms to refer and accept a reward |
| Ownership | The records belong to the company, not to its clients |
| Head start | Recognition that arrives before anyone else in the network notices; worth something only after reach, clearance and ownership |

## The company detail a specialist recognizes immediately

A specialist recognizes the remark that implies records: a system kept read-only after a migration, a habit of writing a narrative on every case, a re-quote after every site visit. A generalist hears the same words as small talk.

| The remark (Illustrative) | A generalist hears | A specialist hears | The metadata question it unlocks |
|---|---|---|---|
| "We kept the old maintenance system read-only after the 2019 switch" | An IT detail | Years of closed work orders, failure codes and technician notes still retrievable | How many years of work orders does the old system hold, and who administers it? |
| "Our adjusters still write a narrative on every claim" | A staffing habit | Free-text reasoning paired with a coded outcome on each file | Do the notes and the final outcome sit in the same system, and since when? |
| "We re-quote every job after the site walk" | A sales process | Estimate, revision and actual cost on one job: a chain of decisions | Are original and revised quotes both kept and linked to job cost? |
| "Every nonconformance goes to a review board" | Quality bureaucracy | A dispositioned record: defect, root cause, decision, sign-off | Where are board decisions recorded, and how far back? |
| "Our dispatchers override the routing software all the time" | A software complaint | Logged human corrections of an automated plan, with reasons | Does the system keep the override and the reason, or only the final route? |

Each specialist reading points at the two screening facts that are hardest for an outsider to see: years of operating history and original documentation the company created itself. That is why recognition matters. It is also why the direction of AI evaluation is relevant: OpenAI's GDPval benchmark builds its tasks from real work products made by industry professionals averaging 14 years of experience, across 44 occupations in the nine sectors contributing most to U.S. GDP. That shows where model evaluation is heading. It says nothing about whether one company's records fit a current SourceX program, which only review decides.

## How sector knowledge becomes a better referral question

It replaces "Do you have data?" with a question the owner can answer from memory, without opening a file.

1. **The generic question.** "Do you have data AI companies might want?" Owners either say "not really" or overclaim, and neither answer helps.
2. **The sector-literate question.** "How many years of work orders survive from before the migration, and who looks after that system?" The answer comes back in years, a system name and an administrator.
3. **The program-literate question.** The sector question plus two more: "Do your service contracts give customers any claim on those records?" and "Would your CEO want to hear about licensing them?" Those map to rights and authorization, the two facts that decide whether recognition is worth anything.

Every answer stays at metadata level: what, how much, how long, which system and who owns it. The column set in the [metadata-only opportunity map](/guides/metadata-only-referral-opportunity-map) holds them. Files, samples, screenshots and logins stay out of bounds.

## Examples from operational, systems and advisory relationships

Each kind of specialist recognizes different records and tends to fail at a different gate.

| Relationship | Typical specialist | What they recognize first | Gate that usually fails |
|---|---|---|---|
| Operational | Former operator now consulting on maintenance, quality, claims or dispatch | What a good record of a decision looks like in that work | Reach: they work with an operations director, not the CEO |
| Systems | ERP, maintenance-system or transport-management implementer | Which tables, archives and audit trails exist, and how far back | Ownership: records in a hosted tenant may belong to the company's clients |
| Advisory | Accountant, industry M&A adviser, fractional CFO | Company size, history and which contracts restrict reuse | Clearance: professional rules on referral fees, disclosure and confidentiality |

Systems specialists are covered in more depth for [ERP consultants](/for/erp-consultants), advisory ones for [accountants](/for/accountants).

**Illustrative case: a fleet-maintenance consultant and a 260-person bus contractor.** Generic company, invented facts, no outcome implied.

- **Discovery.** During a reliability review, the maintenance director mentions that the old maintenance system was kept read-only after the company changed platforms. The consultant asks three metadata questions: how many years it holds (about 11), roughly how many closed work orders (tens of thousands) and who administers it (the IT manager). Nobody opens the archive.
- **Ownership.** The company runs routes under contracts with two public transit agencies. Whether those contracts give the agencies a claim on maintenance records is a question for the company's counsel, so the consultant records it as unknown.
- **Clearance.** Her engagement letter is silent on outside referrals. Before going further, she tells the maintenance director in writing that she could receive a referral reward if the company later licenses records through SourceX.
- **Reach.** The maintenance director is a sponsor, not the authorizer. He raises it with the CEO, who asks for a short note and then agrees to a conversation. The consultant, who has signed the SourceX Channel Partner Agreement, submits the introduction.
- **Conditional outcome.** SourceX reviews relevance, rights and record depth. If the transit contracts claim the records, the scope narrows or the review ends. Illustrative only: if a license were completed and SourceX actually paid the company $250,000, her reward would be $62,500. If nothing is licensed, nothing is owed.

**Illustrative no-fit: perfect recognition, wrong owner.** A clinical-coding auditor reviewing a 400-person medical billing company sees at once that it holds 15 years of coded claims, denials and appeal letters. Every gate except recognition fails. The records describe patients of the physician practices it bills for, so they belong to its clients and contain personal information; SourceX's screening guidance treats client-owned material and personal consumer data as usually not a fit. Her audit engagement also restricts outside commercial referrals. The row closes as "no fit: ownership", with no revisit date.

## Can the specialist reach the person who authorizes?

Often not directly. Specialists usually work one or two levels below the CEO, and the CEO is the person who authorizes a licensing discussion and signs for the company.

| Specialist's usual counterpart | Role in a licensing discussion | Distance to the CEO | How to close the gap |
|---|---|---|---|
| System administrator or IT manager | Custodian: knows what exists and whether it can be exported | Two levels | Ask the business owner of the system to carry the question upward |
| Operations, maintenance or quality director | Sponsor: owns the records day to day and can make the internal case | One level | Ask them to raise it with the CEO, with a note they can forward |
| CFO or controller | Sponsor and adviser: knows contracts and history | One level | The same, with the contract question flagged for counsel |
| Owner-CEO | Authorizer | None | Ask directly whether they want the conversation |

If the only person you reach is a custodian, the head start stalls there. The difference between those roles is set out in [data owner vs custodian](/compare/data-owner-vs-data-custodian), and the choice between going through a sponsor or straight to the CEO in [introduce through a sponsor or directly to the CEO](/compare/introduce-through-sponsor-or-directly-to-ceo). The study design in [which introductions actually reach an authorized data owner](/guides/which-introductions-actually-reach-an-authorized-data-owner) measures how often each path gets there.

Clearance is the gate generalists forget. Accountants who are AICPA members follow its Code of Professional Conduct, which addresses conflict disclosure and client consent, confidentiality, and disclosure of commission or referral fees. Lawyers, financial advisers and other licensed specialists have their own rules, and an engagement letter can add restrictions. Check both before the first conversation, and disclose a possible reward in writing wherever your rules call for it.

## Specialist or generalist: which network discovers better?

Specialists should win on precision and lose on breadth and reach, so the strongest discovery pairs the two. The comparison below is an editorial hypothesis scored on stated criteria, not measured data.

| Criterion | Specialist (sector consultant, implementer, auditor) | Generalist (association lead, peer-group chair, broad connector) |
|---|---|---|
| Recognizes which records exist | Strong: hears the record inside the remark | Weak: hears that a company seems "data-rich" |
| Precision of the first question | Asks in years, systems and administrators | Asks whether the company "has data" |
| Companies in view | Tens, inside one sector | Hundreds, across sectors |
| Reach to the CEO | Often one or two levels short | Often direct: peer groups and associations gather owners |
| Clearance | Professional rules may limit rewards | Fewer professional rules; association policies may apply |
| Typical false positive | Records that turn out to belong to clients | Companies that are large but record-poor |

The pairing that should work best: the specialist recognizes, a generalist with owner access asks. Only one partner is credited per company, so settle in writing who submits before anyone contacts the CEO. For the generalist side, see the page for [industry associations](/for/industry-associations); for how professional roles see owners and systems, see the [AI data introduction economy](/guides/ai-data-introduction-economy).

## What evidence would prove a first-mover advantage?

Dated records showing that specialists noticed qualifying companies before anyone else in the same network and turned more of them into verified applications. No such interviews have been run for this page, and the figures are not yet published.

"First" needs a definition before it can be measured. In this program it means the first valid introduction within the 90-day attribution window, credited when the company submits a verified application. Recognizing first earns nothing; introducing first, validly, does, and that requires reach. Software partner programs have no shared rule for this: in PartnerStack and Wynter's 2026 survey of 100 senior leaders at B2B SaaS companies, 42% used multi-touch attribution for partner revenue, 31% first-touch and 19% last-touch. Here the rule is written down, which makes a head start testable.

### The specialist discovery field interviews

| Element | Protocol |
|---|---|
| Who | Equal numbers of specialists (operational, systems, advisory) and generalist connectors, recruited before any results are seen |
| Unit of analysis | Each company the interviewee considered introducing in the past 12 months, including ones they dropped |
| What each interview records | The remark or event that triggered recognition and its date; the first metadata question; who the interviewee could reach; the clearance check; the outcome |
| Outcome codes | Dropped before asking; owner declined; stalled below the CEO; CEO agreed to talk; verified application; no fit after review |
| Evidence | Dated notes, emails or calendar entries; no company records, samples or names in the dataset |
| Consent and anonymization | Interviewee consent; companies coded by sector and headcount band only; quotes approved before publication |
| Comparison | Share of considered companies reaching a CEO conversation and share reaching a verified application, specialists against generalists, with dropped and stalled cases kept in the denominator |
| What would falsify the thesis | Specialists reach verified applications at no higher a rate than generalists, or the gap disappears once CEO reach is held equal |

Five questions carry each interview:

1. Tell me about the last company where something you heard made you think of its records. What exactly was said, and when?
2. What did you ask next, and what was the answer?
3. Who could you reach at that company, and who decides on new uses of its records?
4. Did your professional rules or engagement terms change what you did?
5. What happened next, including if nothing did?

**Method note.** The recognition table, the gates and the comparison are built from SourceX's published fit criteria and attribution rule (terms and who-qualifies page, checked 2026-10-26) and from editorial judgment about what each role usually sees. They do not measure demand for any company's records, record quality or payout, which only SourceX's review can assess. Where this page says a specialist "should" do better, read it as the hypothesis the interviews would test.

## What must be true before you introduce

- **The records exist and belong to the company.** Record type, rough volume, span of years and system, known at metadata level. Records that describe the company's clients, or that its clients' contracts control, are usually not a fit.
- **Size and history.** 50+ full-time employees at peak, contractors excluded, and documented operating history.
- **Location.** 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.
- **The CEO knows and wants the conversation.** Sponsors can carry the question; the CEO decides.
- **Your clearance is checked**, and any disclosure your rules require has been made.
- **Your agreement is signed.** Whoever submits must first sign the SourceX Channel Partner Agreement (agreements signed under its earlier title, Channel Partner Non-Circumvention and Non-Disclosure Agreement, remain in force).

What stays unknown until SourceX reviews the company: whether its records match current data needs, whether customer contracts limit reuse and what a license would cover. Any reward is paid only after a completed handoff and the payment conditions in the terms; the payment deadline falls 60 calendar days after the later of two dates, the completed handoff and the final written acceptance the Acquisition Partner gives for the complete, validated dataset.

## 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.

When a specialist in your network recognizes a company and the CEO wants the conversation, [get your partner link](/register), run the company past the [fit criteria SourceX publishes](/who-qualifies) and settle any open questions in the [program terms](/terms) before the introduction goes in. More guides are in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://openai.com/index/gdpval/
- https://www.aicpa-cima.com/resources/toolkit/sspfps-toolkit
- https://partnerstack.com/resources/research-lab/charts/multi-touch-is-the-most-common-partner-tribution-method-for-senior-leaders-in-b2b-saas
