Find the hidden AI data connections in your business network: a one-sitting worksheet that turns 40 names into three permission requests and a dated yes, no or later log

Short answer

The hidden connections are owners and operators you already know in another capacity: a supplier you buy from, a client's owner, a fellow board member, a former colleague who now runs a company. Write down 40 of them, keep only people who run or own a company, describe each company's history in a sentence, and separate what you know from what you assume. Check the published fit facts, then ask no more than three for permission to introduce, and log every answer as yes, no or later without collecting a single file.

Visual briefFull-size diagram
A narrowing funnel from one Illustrative sitting: 40 names written down, 18 who run or own a company, 7 that look plausible on the fit facts, 3 permission requests, ending in a log of one yes, one no and one later, with no files collected.
Illustrative counts from one sitting described on this page; they are not program results.

SourceX's network opportunity finder asks for your role and the sectors your clients work in, then suggests what to look for. This worksheet is the step after it: from sectors to the named people you already know, and from those people to a handful of permissioned conversations.

Six capacities where owners hide in plain sight

Most people search their network by job title and miss the owners they know in some other role. Go through six capacities in turn and write down every owner, CEO or senior operator that comes to mind, without judging fit yet.

CapacityWho you might know there (Illustrative)What you usually knowThe pressure to manage
Your own suppliers and service providersThe owner of the firm that prints your packagingSize, years in business, how orders runYou are their customer, so a yes can feel owed; make no the easy answer
Your clients' ownersThe CEO of a client you adviseSystems, history and headcount, from your workWhat you learned while serving them is theirs; ask in person, never from their files
Boards, committees and associationsA fellow nonprofit board member who owns a companyThe company in outlineA social setting; raise it privately or not at all
Former colleagues now running companiesA former manager who is now CEO elsewhereLittle that is currentTheir new company may look nothing like the old one
Lenders, co-investors and landlords you deal withA co-investor in a local deal who owns a distributorOwnership, rarely operationsThe relationship has money in it; keep the subjects separate
Community and family tiesA neighbor who owns a building services contractorVery littleThe relationship matters more than any introduction

Stop at 40 names. A longer list stops being a memory exercise and turns into a prospecting list, which this is not.

The permissioned network mapping worksheet

One row per person. The worksheet holds only what you need to decide whether to ask, and it never holds anything from inside a company.

ColumnWhat goes in itWhat never goes in it
Person and capacityInitials and how you know themContact details you do not already have
Their roleOwner, CEO or another executivePersonal background
Company in one sentenceThe kind of work, roughly how long, the kind of system if you know itCustomer names or financial figures
KnownWhat they told you directly, with the monthHearsay presented as fact
AssumedYour inference, marked as yoursAnything you have not labeled as a guess
Fit factsPeak full-time headcount, years of its own records, a rights clue and location, each marked pass, unknown or failGuesses written as passes
Who can authorizeThe CEO, and whether you know the CEO directlyA manager's enthusiasm standing in for a yes
DecisionAsk now, find who can ask, park, or no fitMore than three "ask now" rows at a time
LogYes, no or later, the date, and their reason in a few wordsFiles, samples or forwarded documents

The worksheet is itself a record about people you know, so keep it lean. The UK Information Commissioner's Office explains the data minimisation principle as personal data that is adequate for your purpose, relevant to it and limited to what is necessary, and suggests periodically reviewing what you hold and deleting what you no longer need. That habit is sensible for any partner and expected of anyone working under the UK GDPR: initials instead of full profiles, and no-fit rows deleted at each review once the log entry is made.

The fit facts come from SourceX's published screen: 50 or more full-time employees at peak, contractors excluded; several years of records the company created itself; rights to license them; an authorized contact; and 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.

Known or assumed: four rows from one sitting (Illustrative)

Illustrative. In one sitting a partner wrote down 40 names. 18 of them run or own a company, 7 look plausible on the fit facts, and 3 became permission requests, which came back as one yes, one no and one later. Four of the rows, with invented facts and no licensing outcome implied:

RowCapacityKnownAssumedFit factsDecision
1. Packaging printer ownerYour supplierTwo plants, "about 300 people" (said in March), same order system since 2009Its order and job records are its ownHeadcount pass, years pass, rights unknown, U.S.Ask now, phrased so a no costs nothing
2. Former colleague, COO of a 120-person claims administratorFormer colleagueHandles claims for insurer clientsMost claim files belong to those clientsHeadcount pass, years pass, rights clue weakAsk her whether the CEO would want to hear about the company's own procedures and quality records
3. Board colleague who owns a landscaping firmNonprofit board45 full-time staff at peakNone neededHeadcount below the 50 thresholdNo fit; log the trigger "passes 50 full-time"
4. Client CEO, 600-person distributor, 22 years oldYour clientOwner-CEO; two system changes in that timeLong order and returns history survivesAll pass except rights unknownAsk now, first

Row 2 shows the most common correction. A warm relationship with a senior operator is not access to the person who decides; the CEO authorizes any licensing discussion. And a company whose deepest records belong to its clients can still have records of its own, which is the only part worth raising. Row 3 shows that a no-fit row is still a useful row: it is dated, it names what would change it, and nobody is pestered in the meantime.

Choosing a small number of permission requests

Pick the three rows that best meet four tests, in this order:

  1. You know the CEO directly, or you know exactly who can ask the CEO.
  2. The fit facts are known and passing, with rights the only unknown.
  3. The relationship can absorb a no without either of you feeling awkward next time.
  4. A dated event exists, such as a planned system retirement or sale, that makes now a sensible time.

Three is a deliberate limit. Each request deserves a proper answer and a follow-up, and a short list keeps the exercise about conversations, not volume. When one row closes, the next one moves up.

A permission request can be five sentences, in your own words: what SourceX does (it licenses business records directly from companies for AI training and evaluation); why you thought of this company, in one plain sentence about the kind of work it records; that SourceX would pay you a referral reward only if a license is completed, paid separately and never taken from the company's payment; that the CEO decides everything and nothing is shared unless the company chooses; and a direct question with an easy exit, such as "Would a conversation help, or shall I drop it?" The guide on asking a business owner for permission to make an introduction covers the conversation in more detail.

Record a yes, no or later without collecting company files

The log is the last column, and it is the only output of the exercise that matters.

AnswerWhat you recordWhat happens next
YesThe date, the CEO's words, and whether the company has spoken with SourceX beforeRegister, introduce with the CEO's approval, and let the company apply itself
NoThe date and the word noClose the row; do not re-ask unless they raise it
LaterThe date and the trigger they namedAsk again when their trigger happens, not on your schedule

Ask about earlier contact on every yes. Under the program terms, a company that already had an application, lead, account or email correspondence with SourceX is a duplicate and is not credited to a later partner; it can still talk to SourceX, but the introduction will not earn a reward. For a company new to SourceX, credit goes to one partner: whoever made the first valid introduction inside the 90-day attribution window, confirmed when the company submits a verified application. Your own signature on the SourceX Channel Partner Agreement has to come before any submission.

Nothing else is collected. If an owner offers to send a sample, a spreadsheet or a login, decline: SourceX deals with records directly and under an agreement with the company.

What one sitting cannot tell you

  • Known is still self-reported. "About 300 people" is the owner's figure; SourceX's review checks it.
  • Assumptions fail quietly. The column exists so a guess never travels as a fact.
  • Demand is decided elsewhere. SourceX checks whether records match its current data needs during review, and a company that fits no program today may fit one later.
  • Relationship cost goes unmeasured. Nobody has published how owners react to these requests. Note it in the log.
  • Results are not yet published. SourceX has not published how often network permission requests lead to applications, so this page offers no rates. To measure your own, count per sitting the names listed, the requests made, the yeses and the applications that followed.

Method note. The worksheet and its columns were built from the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's who-qualifies page and network opportunity finder, and the ICO's guidance on data minimisation, all checked on 2026-10-27. The counts above are invented to show the method. For a broader inventory of your contacts, the network opportunity discovery worksheet is the companion resource; for why the permission-first route matters, see warm introduction versus cold outreach, and the rest of the walkthroughs are in 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 a row on your worksheet ends in a dated yes from the CEO, sign up for your partner link at registration, measure the company against who qualifies, and go over the program terms before you make the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, 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.

Common questions

Why stop at three permission requests?

Three is a number you can follow through properly, with a dated answer for each, and it keeps the exercise a set of conversations rather than a prospecting campaign. When one closes with a yes, no or later, the next row on your worksheet can take its place.

Should I tell the owner I could earn a referral reward?

Yes, in the first message. Say that SourceX would pay you a reward only if a license is completed, that it is paid separately and never comes out of the company's payment, and that the owner decides everything.

What do I keep when someone says no?

The date and the word no, and nothing else. Do not re-ask unless they raise it, and remove the row at your next review of the worksheet so you are not holding personal information you no longer need.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/tools/network-opportunity-finder
  4. ico.org.uk/for-organisations/uk-gdpr-guidance-and-resou…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment