This guide is for whoever runs referrals across a group of introducers: a firm's partners, an association's referral desk, an advisory network.
Three habits that make event-driven outreach opportunistic
Events are good reasons to ask. They turn into bad ones in three predictable ways.
- Borrowed knowledge. Acting on something you learned for another purpose: inside a paid engagement, from a board pack, in a conversation held in confidence. Information that reaches a partner through a board or advisory seat may prompt one question to that company's own CEO, and it travels no further, never to another person and never to a different company. Professionals have their own duties too. The American Bar Association's Model Rule 1.6, for example, bars a lawyer from revealing information relating to a client's representation unless the client gives informed consent, the disclosure is impliedly authorized, or another paragraph of the rule applies (our paraphrase of a search excerpt). SourceX's referral page adds that "Licensed professionals should check their own rules on referral fees." Your own adviser answers how those rules apply to you.
- Bad-moment timing. Layoffs, illness, disputes, investigations and recalls are real events, and they are exactly when a CEO has no room for a licensing question.
- Pile-ons. Public news reaches everyone in a network on the same morning. The program rewards none of the racing that follows. Section 2 of the terms states that "Only one partner is credited per company," credit is decided from dated records, and a link click alone does not decide it; SourceX settles overlapping introductions in duplicate review. And SourceX's screening page counts introductions made without the decision maker's knowledge as usually not a fit.
The relevance-and-consent trigger matrix
Two questions place every event. How close does it come to the company's records and its decision maker? And how did the event reach you?
Relevance, the rows.
- R1. Records or the decision move. A system retirement, an archive move, a new CEO, a closing.
- R2. The CEO is already in the history. An archive review, a records clean-up or a documentation drive the CEO sponsors.
- R3. Money, people or publicity only. A funding round, a hiring spree, an award, a product launch.
Consent, the columns.
- C1. The CEO raised it with you and welcomed a follow-up.
- C2. It is public: announced by the company or visible in a public register.
- C3. It was shared with you for another purpose: an engagement, a board seat, a confidential conversation.
- C4. It is secondhand: a rumor, or another member's story.
| Relevance | C1 CEO raised it | C2 Public | C3 Shared for another purpose | C4 Secondhand |
|---|---|---|---|---|
| R1 Records or the decision move | Book | Hand to the owner | Keep off | Note only |
| R2 CEO already in the history | Book | Hand to the owner | Keep off | Note only |
| R3 Money, people or publicity | Note only | Note only | Keep off | Keep off |
What each verb means.
- Book. A dated entry holding one question for the CEO, owned by the person the CEO spoke to.
- Hand to the owner. The entry goes to whoever holds the CEO relationship as a question for them, "would the CEO welcome this?", never as a question for the CEO.
- Note only. A line in the company's file, with no date and no question attached.
- Keep off. Nothing on the shared calendar. A board or advisory seat allows one question to that company's own CEO, from the person who holds the seat. Knowledge from an engagement is governed by the professional's own rules.
The override. Whatever the cell, an event involving layoffs, illness or a death, a dispute, an investigation or a recall becomes Note only until the company itself says the matter is closed.
One calendar entry, eight fields
Every booked or handed-off event becomes one entry. Nothing in it is a record of the company, only facts about the event and the plan.
| Field | What to write | Why it is there |
|---|---|---|
| 1. Company and entity | The legal entity that holds the records, and its group | A corporate group shares one reward cap, and entries for sister companies should sit together |
| 2. Event and date | The company's own fact, with the date it carries | A dated event, not a news cycle |
| 3. How we know | C1 to C4 | The consent column, written down |
| 4. Relevance | R1 to R3 | The relevance row, written down |
| 5. Owner | One named person | One person asks, and everyone else can see the entry is taken |
| 6. The question | The exact words, one sentence | Keeps the ask from drifting into a pitch |
| 7. Expires | The event date plus a window you set; we use 60 days | Stale triggers turn into pressure |
| 8. Outcome | Asked, declined, introduced or expired, with the date | Closes the loop |
Before anyone creates an entry, they search the calendar for the company and its group. If an entry exists, they add a note to it and leave the owner in place.
A quarter on one network's calendar (Illustrative)
Illustrative. Generic companies, invented events, no outcomes implied.
| Event | Cell | Calendar result | Why |
|---|---|---|---|
| A 180-person freight broker's CEO tells its IT partner the old transport system retires in March and asks what happens to the history | R1, C1 | Booked; owner the IT partner; expires 60 days after the review | The CEO opened the subject and asked |
| Trade press names a new CEO at a 300-person insurance agency | R1, C2 | Handed to the member who knows the new CEO | Public, but nobody knows whether the CEO wants the question |
| An accountant learns during an audit that a client plans to purge ten years of files | R1, C3 | Kept off the shared calendar | Learned inside paid work; the accountant's own rules govern |
| A 70-person software company announces a funding round | R3, C2 | Note only | Money says nothing about records or who decides |
| A 400-person manufacturer whose CEO mentioned an archive project issues layoff notices | R2, C1, override | Note only until the company says the matter is closed | The override outranks the cell |
| Three members flag the same signed acquisition of a 250-person distributor | R1, C2 | One entry, handed to the member who knows the acquirer's CEO, dated after closing; the other two add notes | Before closing the target's CEO decides, after it the acquirer's CEO; only one introduction can be credited |
The last row is the one most calendars get wrong. Three well-meaning messages to one CEO in a week read as a campaign, and they cannot produce more than one credited introduction.
What the owner confirms before a booked entry becomes a question
A booked entry is a prompt to check facts, not permission to send. The owner confirms four things, from the relationship and from public facts, never from the company's files.
- The decider. The CEO is still in the role, and after a sale, which company's CEO decides.
- No earlier contact. Whether the company has ever applied to, written to or held an account with SourceX; section 3 of the terms makes any earlier application, lead, account or email correspondence a duplicate.
- The fit facts already known. Full-time headcount at its peak of 50 or more, contractors excluded; records the company created itself and may license. 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 moment. No override applies, and nothing in the company's week makes the question unwelcome.
If any check fails, the entry drops to Note only, with the reason and the date.
Recording the answer and the next authorized step
The question itself stays short: "You mentioned [the event]. A company called SourceX licenses business records directly from companies for AI training and evaluation; would you like a conversation with them about your company's own history? If it led to a license, SourceX could pay me a referral reward, separately from anything it pays the company." That last clause rests on section 4 of the terms, which says the reward "is never deducted from the supplier's agreed compensation."
The owner then fills field 8 with the date and the CEO's answer in their words. A yes means the owner signs the SourceX Channel Partner Agreement before submitting anything, makes the introduction and lets the company apply itself; nobody in the network collects records for SourceX. A no closes the entry, and an ask built to be easy to decline keeps it that way. Silence is handled in escalating without repeated messages, and the board-seat case is covered in when a board advisor can open the right company door.
This calendar covers a whole network's events. A venture portfolio reviewed on custody and control events has its own transition calendar; a community planning member sessions uses a question-led calendar; and why a funding round belongs in row R3 is argued in why funding announcements should not trigger automatic outreach.
Method note. The matrix, the override, the entry fields and the 60-day expiry are this page's design, built from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening and referral pages and the ABA's Model Rule 1.6 page, all checked on 2026-10-27. They are not SourceX rules or legal advice. SourceX has published no figures on event-driven introductions. To test the calendar, count per quarter the events logged, the share that reached Book, the questions asked, the CEOs who said yes, and how often two members flagged one company.
Where the calendar itself creates pressure
- A date feels like a duty. A booked entry is permission to ask once, not an obligation to.
- Public is not permission. Column C2 tells you the event is real, nothing more.
- Owners hoard entries. If an owner never asks, the entry expires; it does not pass to someone keener.
- Windows get gamed. Re-dating an expired entry to keep it alive defeats the point of expiry.
- Fit is decided elsewhere. Whether any program wants a company's records is settled only in SourceX's review.
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 an entry reaches Book and the CEO says yes, the entry's owner should register for a partner account, hold the company up to the published screening profile and go over the duplicate and credit sections of SourceX's referral terms before writing to anyone.