From an AI-data need to a kind of operating company
Start from how AI developers describe what they test, then translate that into records and finally into a kind of company. Anthropic's engineering guide to agent evaluations treats a task as one test whose inputs and success criteria are defined, and separates the outcome, the actual end state of the environment, from what the agent claims; in its example, a flight-booking agent is judged by whether a reservation exists, not by what it says it did. Records that keep the request, the steps and the checked end state together have that shape, and some companies produce them every day.
| Shape of the need | A record that has it | Kind of company that keeps it (Illustrative) |
|---|---|---|
| A request with a checked end state | A service call closed with the customer's sign-off | Commercial field-service contractor |
| Judgment under written rules | Invoice exceptions with the approver and the reason | Wholesale distributor's finance team |
| A long exchange that ends in a resolution | Support threads with resolution codes | Business software company's own support desk |
| Plans revised under constraints | Dispatch changes and delivery exceptions | Freight brokerage or regional carrier |
| Decisions with money attached | Claim files with reserves and payments | Regional insurer's own claims department |
The translation stops short of a promise. None of these rows says what SourceX's programs want today; SourceX checks relevance to its current data needs during review, criteria vary by program, and a company that fits none now may fit one later.
Three things a connector needs: access, context and permission
An introduction needs three things, and they are easy to confuse because one warm relationship can look like all three.
- Access. You can ask the CEO for a conversation and be heard. The CEO is the person who authorizes a licensing discussion and signs for the company.
- Context. You know how the company records its work, in which systems and for roughly how long, so the first conversation starts from facts.
- Permission. You are free to raise the client's situation with anyone outside the relationship. For some professions that requires the client's consent before a word is said.
Two professions have written rules on the third point. The ABA's Model Rule 1.6(a) begins: "A lawyer shall not reveal information relating to the representation of a client unless the client gives informed consent," alongside disclosures impliedly authorized to carry out the representation and a list of exceptions, and each state adopts its own version. The AICPA Code treats any information obtained from a client that is not available to the public as confidential client information; SourceX's guide to the AICPA confidential client information rule walks through what that means for a referral, and can a lawyer share client information for a referral covers the lawyer's side. In practice, both professions raise the idea with the client and let the client decide whether anyone else hears the company's name. Other professions are bound by engagement letters, statements of work, master services agreements and bank policies rather than a code; read your own.
The industry relationship coverage map
The map has two parts: a profile of each profession, then the same three needs applied to the kinds of company in your own network.
How the ratings work. Access is high when the profession routinely speaks with the owner or CEO about the business, medium when it works mainly with a CFO or COO, and low when it works with managers. Context is high when the profession works inside the systems that record the work, medium when it sees outputs such as financials or loss history, and low when it sees neither. The permission column states what has to happen before the client's name or situation goes to anyone else. These are judgments built from how each relationship usually works, not measured data.
| Profession | CEO access | Work context | Before naming the client | Best role |
|---|---|---|---|---|
| Outside accountant or CPA firm partner | High in owner-run companies | Medium: finance systems, rarely operations | The client's agreement; nonpublic client information is confidential under the AICPA Code | Asker |
| Business lawyer | High | Low | The client's informed consent under Rule 1.6 or the state's version | Asker |
| Commercial insurance broker | Medium to high | Medium: loss history and operating risks | The client's agreement under the broker's own terms | Asker |
| Commercial banker or lender | Medium | Low | The bank's confidentiality policy | Asker for owner-run borrowers |
| M&A advisor or business broker | High during an engagement | Medium: what reached the data room | Engagement terms and any NDA | Asker, with care over timing |
| ERP or vertical software implementer | Low to medium | High: configured the systems | Statement-of-work confidentiality | Spotter |
| Managed IT provider | Medium | High: tenants, retention, archives | The master services agreement; admin access is not a right to license | Spotter |
| Industry association executive | Medium, across many CEOs | Medium: sector practice | Member privacy; member lists never shared | Educator |
Read the pattern before the rows. The professions with the deepest context, implementers and IT providers, rarely hold the CEO relationship. The professions with the strongest access, accountants and lawyers, carry the strictest confidentiality. Nobody scores high on all three, which is why a single "best partner type" does not exist.
The second part applies the three needs to one network. Illustrative: a 40-person regional advisory firm with a tax and advisory practice and an IT services arm.
| Kind of company | Who in the firm serves them | Access holder | Context holder | Gap | Next move |
|---|---|---|---|---|---|
| Field-service contractors | IT arm (6 clients), tax partners (4 clients), 2 shared | Tax partner | IT arm | None inside the 2 shared clients | Tax partner raises it with those two CEOs |
| Wholesale distributors | Advisory partners (3 clients) | Advisory partner | Nobody on operations | Context | The CEO asks their own operations lead, if interested |
| Software companies with their own support desks | Nobody | Nobody | Nobody | Both | Research note, no outreach |
| Freight brokers | One former client | Retired partner | Nobody | Context, and access may be stale | Confirm the relationship is live first |
| Regional insurers | Association membership only | Association executive | Nobody | Context | The association informs members; CEOs come forward themselves |
Pairing a spotter with an asker inside one client
When context and access sit with different people, pair them, but only inside a client both already serve. The spotter, often the IT provider or implementer, notices that a client keeps years of its own records. The spotter does not pass that observation across to a colleague or another firm; it goes to the spotter's own client contact, and from there to the CEO if the contact thinks it is worth raising. The asker, usually the partner who holds the CEO relationship, raises the program with the CEO once the client is comfortable. Agree in writing, before anyone speaks to the CEO, which of you will submit the introduction, because only one partner is credited per company. If a firm's rules require client consent for any disclosure, collect it first. Accountants weighing a reward should also read SourceX's note on AICPA conflicts, disclosure and consent.
The introduction handoff to SourceX
Once the CEO wants the conversation, the handoff is short.
- The submitter signs first. Whoever submits signs the SourceX Channel Partner Agreement before submitting introductions.
- The CEO's answer on prior contact is recorded. A company with any earlier application, lead, account or email correspondence with SourceX is a duplicate and is not credited to a later partner.
- The company applies itself. Credit is assigned when the company submits a verified application, and it goes to the valid introduction made earliest in the 90-day attribution window.
- No records change hands. The partner passes on the CEO's interest and a few lines of metadata, never files, samples or logins.
Every company on the map faces the same entry test: its full-time workforce must have peaked at 50 or more, with contractors left out, and it needs documented operating history, the rights to license it 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. Material that belongs to clients is usually not a fit, which matters most for the outsourced operators an IT provider or implementer is likely to know.
When a network gap calls for research rather than outreach
A row with no access holder is a finding, not a prospecting list. Do not email the CEOs of companies nobody knows to pitch the program: SourceX's guidance counts an introduction the decision maker knows nothing about as usually not a fit, and a cold pitch is not a relationship. Write a short research note instead: which companies of that kind exist from public sources, which associations and software ecosystems serve them, and which profession would need to join your network to reach them. Keep the row marked "research" until a named person with access appears, then start again from the three needs. The network opportunity finder is a quick way to see which sectors your own role tends to reach.
Method note. The profession ratings and the coverage table were built from the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's who-qualifies page, ABA Model Rule 1.6, the AICPA Code's definition of confidential client information and Anthropic's guide to agent evaluations, all checked on 2026-10-27. They were not tested with partner or company interviews, and SourceX has not published introduction or acceptance rates by profession; those figures are not yet published. To measure it, tag each introduction with the profession of the asker and of the spotter, if any, and record whether the company applied.
Limits of the coverage map
- Ratings are generalizations. A particular accountant may know a client's operations better than its IT provider does. Rate the people you actually have, not the profession.
- Rules vary. Professional conduct rules differ by state and country, and engagement terms differ by firm. The permission column is a prompt to check, not legal advice.
- Evaluation research is not demand. Anthropic's guide describes how developers test agents. It does not show that any company's records are wanted, which only SourceX's review can establish.
- Two connectors, one company. Pairing invites disputes over credit. Settle who submits before the CEO hears anything.
- The map omits cost. Raising a new subject with a client spends goodwill, and nobody has published how clients react. Record it.
For profession-specific detail, see the program pages for accountants, managed service providers and industry associations, or browse the guides library.
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 your coverage map shows a company with an access holder, enough context to describe its records and the client's permission to raise the idea, get a tracked link by registering as a partner, screen the company with the who-qualifies criteria and read the terms in full; only then is the CEO asked.