For a channel partner's business development lead the confusion is built into the job. Your warm contacts are the people you serve every week: an IT director, a controller, an operations manager, a head of support. They are rarely the CEO. That is fine. They are the bridge, not the destination, and the work below is about crossing it without leaning on it too hard.
Warmth belongs to a relationship, authority belongs to a role
Four people can appear in one referral, and each can do something different.
| Person | What they bring | What they can do here | What they cannot do |
|---|---|---|---|
| Warm contact, such as the IT director you have served for years | Trust in you, and inside knowledge of systems | Tell you who decides; carry one question to the CEO | Say yes for the company |
| The CEO | Authority to open a licensing discussion and sign | Agree to an introduction; name a sponsor | Be bypassed |
| A sponsor the CEO names | A mandate from the CEO for this topic | Run the internal work and join calls | Replace the CEO's yes |
| A record owner, such as the controller or a system administrator | Knowledge of where records live | Confirm metadata: systems, years, rough counts | Decide whether any record is licensed |
Titles alone do not settle authority. Delaware's corporation statute, for instance, says every corporation it governs "shall have such officers with such titles and duties as shall be stated in the bylaws or in a resolution of the board of directors which is not inconsistent with the bylaws." A business card shows a title, not what a board assigned to it. The program removes the guesswork for you: the CEO authorizes a licensing discussion and signs for the company, whatever other titles say. Whether the company holds the rights to its records is a different question, and SourceX reviews it.
Clues about warmth, clues about authority, and what neither proves
Sort what you know before you say anything. Each clue speaks to one link in the chain, or to none.
| Clue | Speaks to | What it cannot prove |
|---|---|---|
| You worked together on a project in the last six months | Warmth between you and the contact | That they know the CEO or would raise this |
| They have introduced you to a colleague before | Warmth, and a habit of vouching | Willingness to raise data licensing |
| A LinkedIn connection | Neither, on its own | Any relationship at all |
| "CEO" beside a name on the company's leadership page | Authority | That the CEO knows you or wants a call |
| The contact says "I sign contracts all the time" | Neither, for licensing | That approving vendor renewals covers licensing company records |
| A press interview in which the CEO talks about data | Possible interest | Consent to be approached |
Then draw the path as two links: you to the warm contact, and the warm contact to the CEO. Each link needs its own evidence. A strong first link with no second link is not a path; it is a friendly person who cannot help, and the note on finding the right decision-maker covers where to look next.
The authority verification conversation guide
Five turns with your warm contact. Each has one purpose, a line you can use, what to listen for and a point where you stop. The guide is built so that stopping at any turn costs nothing.
| Turn | Purpose | A line you can use | Listen for | Stop or park when |
|---|---|---|---|---|
| 1. Ask to ask | Separate this from your paid work | "Can I ask you something that has nothing to do with our project?" | A real yes, not politeness | They hesitate, or the timing is bad, such as during an outage or a renewal |
| 2. Who decides | Find the authorizer | "If the company were asked to license some of its own historical records for AI training, whose decision would that be?" | A name, and whether it is the CEO | They say "mine" and are not the CEO: explain that the program needs the CEO's yes |
| 3. Their path | Test the second link | "How well do you know them? Would they take a note from you about something new?" | How often they talk, how recently, whether ideas from them get heard | They rarely speak to the CEO: park the card |
| 4. Permission and stake | Ask them to carry one question, and disclose your interest | "Would you be comfortable asking whether they'd want a short explanation from SourceX? I should say I may be paid if a deal ever closes." | Willingness, and any worry about their own standing | Any reluctance: thank them and close |
| 5. What travels | Agree what may be passed on | "What can I send you to forward, and what should stay out?" | A one-paragraph note; nothing from your engagement work | They offer exports, logins or samples: decline them |
After turn 5, only the CEO's own reply moves the card. A forwarded "sounds interesting" is a sign of interest from the warm contact, not the CEO's consent. If the CEO names a sponsor in that reply, the guide to identifying an internal sponsor covers what the sponsor does next, and introducing through a sponsor or directly to the CEO weighs the two routes.
What you heard, what you were told and what you assume
Your notes will mix three kinds of statement. Tag each one, because only one kind lets you introduce.
| Note | Kind | What it allows |
|---|---|---|
| The CEO, by email from the company's domain: "Happy to have a call with SourceX." | Firsthand, from the authorizer, in writing | Introduce the CEO |
| The IT director: "The CEO would love this." | Secondhand report of the CEO's view | Ask the IT director to put the question to the CEO |
| The IT director: "We have twelve years of tickets." | Firsthand metadata from a record owner | Record it as the company's own estimate |
| Your impression: "They seem likely to say yes." | Inference | Nothing; leave it out of the file |
| LinkedIn shows the CEO joined in 2019 | Public clue, dated | A question about tenure, nothing more |
The written, dated yes matters for a second reason. Section 2 of the terms says "Attribution is decided from dated records, including written introduction evidence, existing applications and preexisting relationships". The CEO's own email is the record you will want if credit is ever questioned; a warm contact's enthusiasm is not.
Three contacts, three outcomes (Illustrative)
Illustrative. Generic companies, invented facts, no outcome implied.
| Fact | 1: warm, not authorized | 2: authorized, not warm | 3: warm and authorized, no fit |
|---|---|---|---|
| The contact | IT director at a 180-person insurance claims administrator you have supported for five years | CEO of a 400-person freight brokerage who spoke at an event you attended | Owner-CEO of a 90-person payroll bureau, your firm's client for a decade |
| Turns reached | All five; the CEO replied in writing twelve days later | None; there is no relationship to use | Turns 1 and 2; the warm contact is the authorizer |
| Fit facts | 180 full-time at peak; its own claims records since 2009 | Unknown | Payroll files processed for client employers |
| Outcome | CEO introduced, with the IT director noted as the path | No outreach; parked until a real path appears | Closed; the records belong to its clients |
Case 2 is the tempting one, because the decision-maker is right there in public. A message from a stranger who may be paid is cold outreach, the weakest way to open this subject; warm introduction versus cold outreach sets out why. Case 3 shows the opposite problem: perfect warmth and authority, but the material belongs to clients, and the screening page treats that as usually not a fit. Case 1 is the ordinary success, and it took two weeks of patience after turn 5.
From the CEO's yes to a submitted introduction
- Sign the SourceX Channel Partner Agreement first; section 1 of the terms requires it before any introduction is submitted.
- Ask the CEO whether the company has ever applied to, or corresponded with, SourceX. An earlier relationship makes it a duplicate under section 3.
- Submit the introduction with the CEO's name and the date of their written yes.
- Send one short email connecting the CEO and SourceX, copying the sponsor if the CEO named one.
- Tell the warm contact it happened, and thank them.
Send nothing else. SourceX's how-it-works page is plain about the partner's role: "You do not need to export, upload, or describe confidential records." The company decides what to share, and when.
When warm and authorized are one person, and when they split again
- Owner-run companies. Your warm contact may be the owner and CEO. Skip turns 2 and 3, but keep turns 1, 4 and 5: the ask-to-ask, the disclosure and the limits on what travels still matter.
- A founder who stepped back. A founder who now chairs the board is not the CEO. Ask who is.
- Equal co-owners or a formal process. With two 50/50 owners, or a company in receivership or bankruptcy, the CEO alone may not be enough because someone else may control the assets.
- A new CEO. A yes from a departed CEO does not carry over. Ask the successor.
- A named sponsor. The sponsor can run everything after the yes, but cannot give it.
Warmth also fades. If your last real conversation with the contact was a year ago, the warm introduction explainer is a good check on whether the first link still holds.
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.
Once your notes hold the CEO's own dated yes, not just a warm contact's enthusiasm, register for a partner link, confirm size and records against who qualifies and read section 2 of the program terms on dated evidence before you submit. Related sourcing methods are in the guides library.