This checklist is for the operations lead at a consultancy, accounting firm, managed service provider or agency whose people introduce companies to SourceX. It starts at the CEO's yes. The conversation before it is covered in what to send before a founder accepts, and the email that takes you out of the thread in the introduction handoff email template.
Three acceptances that are easy to confuse
"Accepted" means three different things in SourceX's documents, and a handoff that blurs them makes promises nobody made.
| Acceptance | Who gives it | What it starts | What it does not mean |
|---|---|---|---|
| The CEO accepts the introduction | The company's CEO, in writing | This handoff, and the company's own application if it chooses to apply | That the company fits, will sign or will be paid |
| SourceX accepts the delivered data | SourceX, in writing, once every condition in the company's deal records is met | Closing, after which the company invoices SourceX | That any partner reward is payable yet |
| The Acquisition Partner's final written acceptance | SourceX's licensing counterparty, by unconditionally selecting the complete, validated dataset under its data license | Together with completed handoff of that dataset, the 60-day clock for paying a partner reward | That every other payment condition has been met |
This page is about the first row. Write "CEO agreed to be introduced" in your own records rather than "accepted," and the other two rows stay where they belong, in SourceX's process and the program terms.
The accepted-introduction handoff packet
Assemble the packet on the day of the CEO's yes. Each parcel has one destination, and each item comes from a named place: the CEO's own words, your records or a SourceX page.
Parcel A: to SourceX, the introduction record. Under SourceX's partner agreement, each introduction record has to name six things: which company, at what web address, put forward by whom, for what opportunity, by what method and at what times. Parcel A carries those six, plus the CEO's contact, and nothing more.
- ☐The company's legal name and web domain, and its parent, if any (one reward cap covers a whole corporate group)
- ☐The CEO's name and the contact route the CEO chose
- ☐Your name and partner account, under the Channel Partner Agreement you signed before submitting anything
- ☐The opportunity in one line, in the CEO's words
- ☐How the introduction was made, by portal submission or email, and its timestamp
- ☐The CEO's answer to whether anyone at the company has dealt with SourceX before
The last item matters because SourceX's terms treat a company it already knew, through an earlier application, a lead, an account, an email thread or any other relationship, as a duplicate that no later partner is credited for. SourceX checks its own records as well, so the CEO's answer is a courtesy to everyone, not a ruling.
Parcel B: to the CEO, what happens next.
- ☐A link to SourceX's own description of its process, not your summary of it
- ☐How the company moves: SourceX's process starts with a short application from the company, a few questions and no files
- ☐What you will not do: handle or forward records, speak for the company on terms, or carry messages between the company and SourceX
- ☐Your interest in one sentence: who could be paid, and that SourceX pays it separately, never out of the company's compensation (wording ideas in disclosing a reward naturally)
- ☐That SourceX may deal with the company directly, without you on calls or emails
- ☐That the CEO can stop at any point and owes you no updates
Parcel C: kept in your own file.
- ☐The CEO's written yes, or a pointer to the message that holds it
- ☐The submission reference and timestamp
- ☐The version of the Channel Partner Agreement you signed, and the terms version in force that day
- ☐The date 90 days after the recorded introduction; the agreement's Schedule A credits an introduction only if the company submits a verified application within that time
- ☐The parent group, if there is one
Never packed, in any parcel.
- Files, exports, screenshots or samples of the company's records. The agreement bars partners from collecting or keeping dataset copies through the program without separate written authorization.
- Logins, credentials or access notes. The agreement gives a partner no authority to reach extraction systems or to share a company's records.
- System names, volumes or record descriptions picked up in other work. The company describes its own systems in its application.
- Any estimate of what the records or the reward might be worth.
- Another advisor's claim to the company. Overlapping claims are SourceX's to settle in duplicate review, as the duplicate-claims guide explains.
Health care has a name for a handoff made in front of the person it concerns. The Agency for Healthcare Research and Quality describes a warm handoff as a transfer between two members of a care team made in front of the patient and family, so the patient hears what is said and can correct or clarify it (our paraphrase). Borrow the idea: send the CEO the exact text of parcel A before you submit it, or copy the CEO on the email that carries it. The person whose company is being described gets to fix the record before SourceX relies on it.
Who moves next, step by step
SourceX publishes its process from application to payment. Set your part against it and your column is nearly empty, by design.
| SourceX's published step | Who acts | Your part |
|---|---|---|
| Apply and qualify | The company answers a few questions, with no files; SourceX checks fit, completes the inventory with the company and runs the rights check | Answer SourceX if it asks about the introduction itself |
| Indicative offer, Master agreement, alignment, Dataset Deal Confirmation | SourceX and the company, with the company's CEO signing | None |
| Commercial commitment, then preparation and delivery | SourceX, with the company, through approved processing routes once SourceX gives the go-ahead | None, and no timing relayed to the CEO |
| Acceptance review, Closing and invoice | SourceX accepts in writing; the company invoices SourceX after Closing | Read your dashboard |
SourceX's own wording on timing is careful, and yours should be more so. Of the commercial step it says: "Commercial feedback usually takes 7–14 days; that is a target, not a promise, and positive interest is not yet a purchase." Quote it with attribution or leave it out; never restate it as your own estimate. On your side, SourceX's referral page says the dashboard shows each referral's stage and reward status, and marks a reward Paid only once an actual payout has been recorded; the agreement adds that partners follow their own referral through generic stages or reference codes, and that SourceX need not reveal buyer names or prices. How much a partner should stay involved at all is weighed in referral involvement after an introduction, and what SourceX itself handles is listed in what SourceX manages after an introduction.
When the handoff meets something unexpected
| Situation | Who decides | Your move |
|---|---|---|
| The CEO forwards a file or sample to you "to help" | The CEO, about the company's own records | Do not open or pass it on; say that material goes to SourceX only through SourceX's process, and delete your copy |
| SourceX asks you about the company's records or systems | The company | Point SourceX to the CEO; you hold no authority to share company records |
| The CEO asks what the data is worth or how fast a deal could happen | SourceX, in its review and offer | Send the link to SourceX's process and give no estimate |
| The company agrees to be acquired before it applies | The target's CEO until closing, the acquirer's CEO after it | Leave the record as submitted; if closing comes first, the acquirer's CEO decides whether the company goes on |
| Another advisor says they introduced the company too | SourceX, in duplicate review | Keep your dated record and never ask the company to choose |
| The company belongs to a group with its own history with SourceX | SourceX settles any credit question involving related companies in duplicate review; no published rule covers it, and the group shares one reward cap | Note the parent in parcel C and claim nothing beyond that |
| The CEO changes their mind | The CEO | Close your file with a one-line thank-you |
For a company in the middle of a sale, the business-sale handoff checklist adds the deal-specific steps.
One packet, filled in (Illustrative)
Illustrative. A generic company and firm, invented details, no outcome implied.
| Parcel | Item | Entry (Illustrative) |
|---|---|---|
| A | Company and domain | A 180-person regional engineering consultancy and its web domain; no parent |
| A | CEO and contact route | The founder-CEO, who asked that scheduling go through her assistant |
| A | Partner | A partner at the company's outside accounting firm, whose Channel Partner Agreement is signed |
| A | Opportunity, in the CEO's words | "Licensing our own project histories for AI training, if it makes sense for us" |
| A | Method, timestamp and earlier contact | Portal submission on the day of her email; she knows of no earlier contact with SourceX |
| B | What went to the CEO | The process link, three sentences on what the firm will not do, the interest sentence and a note that SourceX may contact her directly |
| C | Kept on file | A pointer to her email, the portal reference, the agreement and terms versions and the day-90 date |
| Never packed | Left out | The project counts the firm saw while preparing the company's accounts, which stay in the engagement file |
Closing the packet under your own policy
When the introduction ends, whether by the CEO's decision, a lapsed window, SourceX's decision or a paid reward, keep parcel C and the reason it closed, and delete drafts and any personal details you no longer need. How long parcel C stays is your firm's retention policy to set. The agreement's return-or-delete clause makes an exception for records needed for reward accounting and dispute evidence, which is what parcel C is. If the company licenses again later, the cap does not reset, so the parent line can matter years afterwards.
Where the packet can still fail
- A packet cannot repair a missing yes. If the CEO's agreement is spoken or second-hand, stop and get it in writing first.
- Speed against accuracy. Submitting before the CEO has seen parcel A risks a record the CEO would not recognize.
- The window keeps running. Nothing in the packet stretches the 90 days; the terms say the window does not extend because contact protection under the agreement continues.
- Silence is normal. After the handoff, SourceX and the company work directly, and you see generic stages only.
- No outcome evidence yet. Whether a packet shortens the time from a CEO's yes to a verified application has not been measured. Log both dates for every introduction over two quarters to find out; no figures are published.
More operations guides are in the guides library, and the partner-side stages are on how it works.
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 CEO's written yes arrives, make sure your firm has registered as a partner and signed the agreement, recheck the company against who qualifies, and file the version of the program terms you relied on inside parcel C.