The reader here is the growth manager of a large network about to brief hundreds of members at once: an association with chapters, a firm with many offices, an operating-partner bench across funds. Whether members register as partners themselves or the network submits for them, whoever submits signs the SourceX Channel Partner Agreement first, and each introduction names one company whose CEO agreed to it.
A rollout pilot asks whether it can be done safely, not how much it will yield
The temptation is to pilot in a few chapters, count introductions and multiply by the number of chapters. Clinical researchers learned to distrust that move. NCCIH's guidance on pilot studies describes a pilot as a check on whether the approach planned for a larger study is feasible and acceptable, a question of whether it can be done rather than whether it works, and it lists estimating an effect size from a pilot among the common misuses (paraphrase).
Translated to a network, the pilot's job is to show that members can use the kit as written: they describe SourceX accurately, they get the CEO's yes before anything is submitted, nobody handles a company's records and CEOs do not feel pushed. Introduction counts are reported, but no rollout decision rests on them.
Two truthful kits and the lines both must carry
| Element | Full kit | Link-only kit |
|---|---|---|
| Fit facts | A one-page brief that links who qualifies and summarizes it in plain words | The who-qualifies link |
| Briefing | A 30-minute call per chapter | None |
| Message template | A draft note to a CEO the member adapts | None |
| Must-say lines | All five below | All five below |
| Terms | Linked, never retold | Linked, never retold |
Both kits carry the same five lines, word for word:
- The CEO decides whether the company talks to SourceX, and signs for it; neither the network nor the member can decide for a company.
- SourceX decides fit and credit in its own review, from dated records; a link click alone does not settle credit.
- The member or the network may earn a reward from SourceX, paid separately and never deducted from what the company receives; say so to every CEO.
- Nobody collects records, samples, exports or logins for SourceX, and nobody gets preferential access to a company's data.
- SourceX does not endorse the network or its members, and no one can promise a company a result.
Three clauses of the sample Channel Partner Agreement explain why. Section 4.2 gives the partner no authority to share a supplier's records, raw data or personal information; section 4.5 bars publicly identifying the other party as a partner without written authorization, so the rollout announcement cannot call the network a SourceX partner unless SourceX has agreed in writing; section 7.1 says the partner is not SourceX's agent and cannot commit it to prices, licenses or payouts. For what a one-page brief can look like, see the advisor enablement one-pager.
Chapters, not members, as the unit of allocation
Members of one chapter talk to each other, forward each other's emails and sit on the same calls. If you split a chapter between kits, the full kit leaks into the light half within a week. So the chapter is the unit:
- Pick six chapters that agreed to pilot, then pair them by size and type (two large, two mid-size, two small).
- Within each pair, a logged coin flip sends one chapter to the full kit and the other to the link-only kit.
- Every member of a chapter counts in that chapter's results, whether or not they read the kit.
- Outside the six, nothing changes until the rollout decision.
Six chapters in three pairs cannot prove one kit better than the other. They can show whether either kit fails the gates, which is the decision you actually face.
The knowledge-and-fit pilot evaluation
Knowledge is read from what members did, not from a quiz. Understanding before anyone writes to a CEO can be tested separately with the onboarding scenario cards; this evaluation looks at real notes and real outcomes.
Part A, the message audit. With each member's agreement, the member shares the first note they send to each CEO, with company and personal names removed before it reaches the pilot lead. The lead codes every note against eight misstatements:
| Code | Misstatement in the note |
|---|---|
| M1 | Says or implies the company qualifies |
| M2 | Says or implies SourceX endorses the network or the member |
| M3 | Promises preferential access, priority or a faster review |
| M4 | Suggests someone other than the CEO can decide for the company |
| M5 | Asks the CEO to send records, samples, exports or screenshots |
| M6 | Leaves out that the sender may be rewarded |
| M7 | States an amount the company or the sender will receive |
| M8 | Says the link or the email itself secures credit |
Part B, fit. For each chapter, per 10 members: introductions submitted with the CEO's written yes; introductions SourceX verified and credited and has not closed at the read date; introductions closed; duplicates. Copy the stage and status words exactly as the dashboard shows them, as how it works describes. These counts are descriptive.
Part C, side effects. CEO complaints about pressure or promises; any record offered to or requested by a member; any introduction that reached SourceX before its CEO agreed; any public post describing the network as SourceX's partner.
| Measure | When read | Role |
|---|---|---|
| Notes audited, and the share with any misstatement, by kit | Day 120 | Gate |
| M1, M4 and M5 counts | Day 120 | Gate (target zero) |
| Introductions with a written yes before submission | Day 120 | Gate |
| Members who say they could use the kit as written | Day 120, one-question survey | Gate |
| Verified, open, closed and duplicate counts per 10 members | Day 180 | Descriptive |
| Side effects in Part C | Throughout | Stop rules |
Four gates set before the first chapter is briefed
Write each threshold down before the first briefing, sign and date it, and do not move it afterwards.
- Records. No member received, requested or forwarded a company record because of the kit.
- Claims. Zero notes with M1, M4 or M5, and no more than an agreed share of audited notes with any other misstatement, for example one in ten.
- Consent. Every submitted introduction had the CEO's written yes before submission.
- Usability. At least an agreed share of surveyed members, for example half, say they could use the kit as written, and no CEO complaint is unresolved.
Either kit can pass or fail on its own. The rollout uses the lightest kit that passes all four.
Duration, sample floor and stop rules
Duration. Briefing in week 0, notes and introductions collected to day 120, outcome stages read on day 180 so a late introduction has a full 90-day attribution window. The rollout decision is taken on day 120 from the gates; the day-180 table is appended when it is ready.
Floor. Gate 2 is judged only once each kit has at least 10 audited notes. If either kit falls short, extend the pilot rather than judging on a handful.
Stop rules.
- A record reaches a member: stop that chapter's outreach until the kit is fixed.
- An introduction reaches SourceX before its CEO agreed: stop and rebrief that chapter.
- A CEO complains about pressure or a promise: pause that chapter and review the note.
- Anyone announces the network as SourceX's partner without written authorization: take it down and pause the pilot.
- SourceX changes its terms or who-qualifies: reissue both kits, note the date and restart the clock for notes written afterwards.
- Never stop early because a chapter's introduction count looks strong.
Roll out, revise or stay small: reading the pilot
| Gate result on day 120 | Decision |
|---|---|
| Both kits pass all four | Roll out the link-only kit, with the full kit offered on request |
| Only the full kit passes | Roll out the full kit, and budget the briefing calls before announcing |
| Neither passes on claims or consent | Revise the must-say lines and run a second pilot in two new chapter pairs |
| Either fails on records | Stay small; rewrite the kit's records section and pilot again |
| Gates pass but members say the kit is unusable | Simplify, then re-survey the same chapters before rollout |
A strong introduction count in one chapter never overrides a failed gate. After rollout, the now-or-later workshop design can test whether extra training changes what members do.
Where a rollout pilot can mislead
- Volunteer chapters. Chapters that agree to pilot are usually the most engaged. Passing in them is necessary, not sufficient, so watch the first month of rollout with the same audit.
- Being watched. Members who know their notes are read may write more carefully than they will later. Keep a lighter audit, a sample of notes each quarter, after rollout.
- Shared notes only. The audit sees what members chose to share. Report how many members shared nothing.
- Few clusters. Three pairs leave wide uncertainty about any difference between the kits; state it plainly.
- Review is SourceX's. A verified, open introduction is not an accepted company, and a lead, meeting or signed agreement alone earns nothing payable.
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.
Before the first chapter is briefed, make sure whoever submits has registered as a partner and signed the Channel Partner Agreement, link both kits to the current who qualifies page and date them against the program terms version in force. Other test designs are in the guides hub.