A generic "just checking in" email fails because it asks the partner to do the remembering. PartnerStack's activation guide passes on advice to treat an inactive partner base as "a pipeline for reactivation" and suggests reactivation email campaigns. PartnerStack's glossary lists common causes of inactivity: not understanding the program's benefits, too little support, competing priorities, or no interest. A brief can fix the first two. It cannot fix the last two, which is why every brief carries an exit.
Which quiet partners are dormant, and what would count as reactivated?
Write the definitions down before anyone gets a brief, or the result will be counted three different ways.
- Dormant: a partner with no dated introduction and no named CEO relationship in your chosen window. 120 days is this page's suggestion, not a SourceX rule.
- Reactivated: the partner names at least one CEO relationship whose company passes the published fit facts at metadata level, within 30 days of the brief.
- Referral quality: of the unique companies a partner introduces, the share that pass SourceX's fit review, read alongside the recorded reasons for the rest.
Dormant partners are not one group. What the brief must cover depends on the last dated record each one left.
| Partner state | Last dated record | What the brief must cover | The one ask |
|---|---|---|---|
| Registered, never signed | Registration date | The agreement must be signed before any introduction | Sign, or tell us to close the account |
| Signed, never introduced | Agreement date | The fit facts and how to describe one relationship at metadata level | Name one CEO you could ask |
| Once active, then quiet | Date of last introduction | Every change since that date, and the status of their earlier companies | One new relationship, or "pause" |
| Quiet, with introductions still open | Date of last introduction | What is still with SourceX and what the partner cannot see | Nothing new; stay reachable |
For the rungs between sign-up and a working channel, see qualifying referral partners and registration versus activation.
The changed-criteria reactivation brief
One page, six parts, in this order. The order matters: facts that changed come before the ask, so the partner reads the context first.
| Part | What it says | Where the facts come from |
|---|---|---|
| 1. Header | The partner, their last dated activity, the terms version described and the date sent | Your partner records and the terms page |
| 2. Changed since your last activity | Only the version entries dated after that activity | Section 11 of the terms |
| 3. Not changed | the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; one partner per company; the 90-day window; 50+ full-time employees at peak; partners never handle records | The terms and the qualification page |
| 4. Your agreement | The title it was signed under, its date, the one-year term and renewal by fresh signature | The partner's signed copy and section 9 |
| 5. Your earlier companies | Each company they named, with your claim-log date and a plain status | Your own claim log, never SourceX's records |
| 6. One ask, one exit | A single request that fits today's criteria, and a one-word way to pause | You |
Part 2 is built by filtering SourceX's published version log against the partner's last activity date. A partner last active in June gets every line; one last active on 20 October gets the final three.
| Terms version | What changed | Relevant to a partner last active before |
|---|---|---|
| 2026-10-12 | The the greater of $50,000 plus 5% and 15% of Actual Supplier Payout calculation applies to all referrals, including those submitted earlier | 12 October 2026 |
| 2026-10-19 | Partners sign the SourceX Channel Partner Agreement; partners who signed before the rename (Channel Partner Non-Circumvention and Non-Disclosure Agreement) stay bound by that signed version | 19 October 2026 |
| 2026-10-21 | An existing relationship now explicitly includes any earlier lead, account or email correspondence with SourceX | 21 October 2026 |
| 2026-10-22 | The payment deadline and conditions follow the agreement's Schedule A, and an unsigned sample agreement is linked | 22 October 2026 |
| 2026-10-22.2 | Actual Supplier Payout is defined in the words of Schedule A | The second 22 October release |
For a partner who left before the payment line changed, part 2 should state the deadline in full: a 60-calendar-day clock running from the later of two dates, the day the handoff is completed or the day the Acquisition Partner's final acceptance of the complete, validated dataset arrives in writing, with any condition still open then paid promptly once met and no new 60-day period. Founder-facing wording that has gone stale is a separate problem, covered in old criteria in founder outreach.
One brief, written for one partner (Illustrative)
Illustrative. A generic partner and invented activity dates; the version entries are the published ones.
For: an advisor at a regional accounting firm. Last dated activity: an introduction submitted 2 June 2026. Describes: terms version 2026-10-22.2, since replaced by version 2026-11-04. Sent: 26 October 2026.
Changed since June: all five October versions apply to you. The three that matter most: the reward calculation now applies to every referral, including yours from June; the terms now spell out that any earlier email between SourceX and a company makes it an existing relationship; payment timing is tied to the Acquisition Partner's final written acceptance and completed handoff.
Not changed: one partner per company, the 90-day window, 50+ full-time employees at peak, and you never handle client records.
Your agreement: signed in May under the earlier title and still in force as signed. SourceX offers partners on that title an addendum adopting the current text; reply if you want it.
Your earlier companies: the 400-person freight company you introduced in June never applied, so that 90-day window has closed. Whether a new introduction would be credited is for SourceX's duplicate review, so please make no promises to its CEO.
One ask: is there one CEO you could ask this quarter whose company you already know passes the fit facts? If not, reply "pause" and we will stop writing until you say otherwise.
The brief is about 250 words. It does not recap the program, attach a deck or mention what anyone might earn.
Size the waves to capacity, and check overlap before anyone asks
Capacity. SourceX has not published its review throughput, so the limit you control is your own follow-up time. A brief is meant to open a call, not replace it. Illustrative arithmetic: a partner manager with five hours a week for reactivation, spending 30 minutes per call and 15 on notes, can hold about six calls a week, which makes a wave of twelve briefs over two weeks, not forty in a day.
Support. Note what each partner needs to act: a criteria refresher, the addendum, or help phrasing a first ask to a CEO.
Concentration. If most of a returning partner's relationships sit in one sector, or behind one person, record it. A wave that reactivates one well-connected partner and nobody else is a dependency, not a recovery.
Overlap. Check every company a returning partner names against your claim log before they contact the CEO. Partners never receive access to other partners' records or applicant documents, so the log is your best defense against two people asking the same CEO. First valid referrer versus last touch explains how credit is decided.
An underperforming cohort (Illustrative). A firm recruited 26 advisors after a spring offsite. Today 9 never signed the agreement, 11 signed but never introduced anyone and 6 made at least one introduction before going quiet. Wave 1 is the six once-active advisors, because they know the steps and have dated history to brief against. Wave 2 is the eleven signed-but-silent, with a shorter brief and one question. The nine unsigned get a single message asking whether they want their registration kept.
A duplicate-risk case (Illustrative). A returning advisor proposes a 350-person facilities company she mentioned informally in April. The claim log shows a colleague logged the same CEO relationship in September and introduced it within the week. One partner is credited per company and the colleague's introduction is dated first, so the brief tells her before she calls, and she does not ask that CEO a second time. Whether anything she did in April affects credit is for SourceX to decide from dated records.
Evidence gates for the next wave, and how to correct a brief
Treat each wave as a test with gates set in advance. These thresholds are this page's proposal; adjust them, but write them down before the wave goes out.
| Gate before wave 2 | Measured how | Proposed bar |
|---|---|---|
| Replies | Partners who answered, including "pause" | Half of wave 1 |
| Named relationships | CEO relationships that pass the fit facts at metadata level | At least one per three briefs |
| Duplicates caught late | Overlaps found only after a CEO was contacted | Zero |
| Follow-up kept | Calls held within two weeks of the brief | Every partner who replied |
Corrections. Keep a send log: partner, date, terms version. If SourceX publishes a new version, the next brief carries the new stamp. If a sent brief misstated a fact, every partner who received it gets a correction within a week, before any new ask. Partners who replied "pause" are not written to again until they say so.
Email form. If you send briefs from the U.S., the FTC's CAN-SPAM guide treats a message whose primary purpose is a change in the terms of an ongoing relationship as a transactional or relationship message, but a mixed message is judged by its subject line and by whether the transactional part comes mainly at the beginning. Lead with the changes, keep the subject line factual and put the ask last. Rules elsewhere differ; check with counsel.
When reactivation is the wrong goal
- Some partners should leave. A partner who never had a CEO relationship to offer is better closed than coaxed.
- You cannot see review. A partner with introductions still open may be quiet because SourceX is still reviewing them; the brief should say what you can and cannot see.
- Partial exits are unsettled. The terms say rewards already earned stay payable when their conditions are met. They do not say what happens to an introduction still in review when a partner steps away, so promise a pausing partner neither outcome.
- Criteria differ by program. SourceX applies the criteria of each program, and a company that did not fit one may fit another later, which is a reason to mention an old declined company only as "worth asking SourceX about", never as "now eligible".
Methods note. The brief and its version filter come from SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04) and qualification page, checked on 2026-10-26; the email point from the FTC's CAN-SPAM guide; the reactivation framing from PartnerStack's guide and glossary. No partner reactivation data has been published by SourceX, so the gates above are untested proposals and reactivation rates are not yet published. For the related question of when to stop chasing a single introduction, see inactive referral follow-up.
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 your first reactivation wave, have each returning partner confirm their account through registration, check their named companies against who qualifies and read the current program terms the brief describes.