# Custom vs standard referral terms: a plan | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-keep-custom-terms-from-confusing-standard-partners
Last updated: 2026-11-04

Publish one default and keep every custom term inside the signed documents of the partner it belongs to. Segment partners by the document that governs them, not by status or size: not yet signed, standard, earlier-title agreement, signed exception, and departed. Each segment hears only its own terms. Shared decks, group chats and leaderboards carry the published default and the line that a signed Schedule A or addendum can differ, and never another partner's numbers.

The plan is for heads of channel partnerships whose benches mix partners on standard terms with a few on signed variations. Program facts were read on 4 November 2026 in SourceX's terms (Version 2026-11-04), the sample Channel Partner Agreement and the rewards page. The segments, message rules and situations are this page's own, and every example is Illustrative.

## How one partner's exception becomes everyone's rumor

Confusion rarely starts with a lie. It starts with a document meant for one reader reaching many.

| Failure | What partners come to believe | What the documents say |
|---|---|---|
| A deck written for one partner is reused for all | That a custom figure is the program's rate | A signed Schedule A sets one partner's reward formula, floor and base; the website terms govern everyone else |
| A network leader paraphrases a deal | "Everyone gets the better rate" | A partner is not SourceX's agent and cannot commit SourceX to payouts |
| A dashboard or calculator changes | That the terms changed with it | Calculator changes and dashboard edits amend nothing; changes need a writing signed by both parties |
| An earlier-title agreement is forgotten | That the old document lapsed | A document signed under the old title (Channel Partner Non-Circumvention and Non-Disclosure Agreement) still binds exactly as signed, and SourceX offers its signers an addendum adopting the current text |
| A partner hears a new agreement "resets" things | That the USD 50,000 floor applies again | The USD 50,000 element applies once per referred company, to its first qualifying transaction, and not again on a repeat, renewal or amendment |
| Someone circulates earnings estimates | That projections are part of the offer | SourceX's rewards page says it does not provide income projections |

The floor rumor shows how much one wrong sentence costs. A partner told the USD 50,000 floor applies to every agreement, watching a company sign two licenses within 12 months that each pay the supplier $320,000, expects $132,000 in rewards. The default gives $66,000 on the first transaction (USD 50,000 plus 5%) and $48,000 on the second (15% in the Repeat Window), $114,000 in all, because the floor applies once per referred company. That arithmetic is Illustrative, not a forecast for any company.

## Activation and referral quality when terms differ

Two partners can be equally active while one of them is working from the wrong terms. The plan counts both:

- **Activated partner:** has signed the document that governs them and has made at least one proposal. A partner who cannot say which document governs them is not yet activated, however keen.
- **Referral quality:** unique companies proposed that pass the fit facts, counted once, plus a terms measure: the share of a partner's term questions that already cite the right governing document.
- **Misquote incidents:** each time a non-default figure appears in shared material, logged with the date and the channel.

None of the segments changes which companies fit. Every message to every segment uses the same published facts: 50 or more full-time employees at peak with contractors excluded, years of the company's own records, rights to license them and a CEO who authorizes the discussion. 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 terms segmentation communication plan

| Segment | Governing document | What they receive | Channel | Never send them | Refresh when |
|---|---|---|---|---|---|
| 0. Not yet signed | None yet; public terms and the unsigned sample apply for reading | Link to /terms, the unsigned sample, a note that introductions wait for signature | Onboarding email | Any custom figure, any "you will get" | They sign |
| 1. Standard | Signed Channel Partner Agreement with the standard Schedule A | A one-page default summary and their signed copy | Shared partner channel | Another partner's Schedule A or addendum | SourceX publishes a new terms version |
| 2. Earlier-title agreement | Their agreement as signed, until any addendum is signed | Their signed copy and SourceX's offer of an addendum adopting the current text | Private email | "Your terms changed automatically" | They sign the addendum, or not |
| 3. Signed exception | A varied Schedule A or an addendum naming the provisions it changes | A private sheet listing only the provisions that differ, by clause; everything else is default | Private email | A broadcast, a badge, a leaderboard mention | Its review date or renewal |
| 4. Departed | Their agreement, ended | What survives: earned rewards stay payable when conditions are met, and contacts introduced during the term stay protected for six months | Private email | New program material | Six months after the end |

Departed partners raise one question the published terms leave open: how credit is treated for an introduction still in review on the day a partner exits. Do not answer it from the network's side. Ask SourceX, and file its answer with that partner's documents.

Five message rules hold the segments apart:

1. **One public source.** Every shared item links to [the terms](/terms) instead of restating them.
2. **One standard line.** Every shared item that mentions a reward says a signed Schedule A or addendum can differ, and nothing more about who has one.
3. **Default figures only.** Shared material shows the default reward, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and no other number.
4. **Answer from the asker's own document.** A term question is answered by naming the clause in the asker's signed agreement.
5. **Correct where the error appeared.** A wrong figure is retracted in the same channel, within two working days.

## Three situations (Illustrative)

Illustrative: invented networks, partners and companies.

**An underperforming cohort.** An advisory network has 70 partners on standard terms. A rumor spreads that "founding members get a higher rate", and the cohort's proposals fall from 12 in one quarter to 3 in the next, as partners wait to be offered something better. The fix is the standard summary, a plain statement that terms are set individually in signed agreements and never compared across partners, and an invitation to ask about their own document. The test is the next quarter's proposal count from the same 70.

**A duplicate risk.** A partner whose addendum covers publicity only and a standard partner both claim the same 260-person claims administrator. The addendum does not mention attribution, so the default decides: the first valid introduction within the 90-day window, judged from dated records, with one partner credited. The other partner hears that plainly and early. If the two had named a parent and its subsidiary, SourceX would settle credit for the second entity in duplicate review, and no published rule says how; the USD 50,000 floor applies once per referred company, so that review would also decide whether the two count as one. [Explaining attribution without promising exceptions](/guides/how-to-explain-attribution-without-promising-manual-exceptions) has wording for that conversation.

**A capacity limit.** A channel team of one fields about 6 term questions a week. After a deck with a custom figure goes to the whole bench, 40 arrive in one week. The team sends one correction to everyone who got the deck, publishes a short note on the five segments, holds two open office hours and replies individually only to segment 2 and 3 partners, whose answers depend on private documents.

## Who carries the load when terms differ

| Load | Where it sits | What to watch |
|---|---|---|
| Term questions | Your channel team | Weekly count, and the share answered by pointing to a clause |
| Private sheets for segment 3 | Whoever owns partner documents | One owner, one copy per partner, a review date on each |
| Concentration | Partners on custom terms | If they produce most fit-passing companies, standard partners may feel second tier; keep support equal |
| Overlap | Partners in two networks, or signed both personally and through a firm | Record which agreement each introduction was submitted under |

The overlap row matters more as networks grow. One person can hold a personal agreement and also introduce through a firm's agreement, and the record should show which one each introduction travels under, because one partner is credited per company.

## Correction path when a wrong figure circulates

1. **Retract** in the channel where it appeared, with the corrected default and a link to the terms.
2. **Name the governing documents**, not the partner: "Terms are set in each partner's signed agreement."
3. **Log the incident** with the date, the channel and the terms version in force; [saving the applicable terms version](/guides/why-a-partner-should-save-the-applicable-terms-version) explains why the version matters.
4. **Check proposals made during the confusion.** Partners who introduced companies expecting a different figure deserve a direct note.
5. **Promise nothing to make up for it.** A network cannot commit SourceX to any payout, so it cannot honor a wrong figure on SourceX's behalf.

## Where segmentation fails

- **Partners talk.** Private sheets reduce leaks; they do not end them. Openness that individual terms exist does more than secrecy about whether they do.
- **Too many segments.** Five is the most a small team can run. If segment 3 grows past a handful of partners, the exceptions have become a second program and need their own review.
- **The plan is not legal advice.** Whether a member may share in a reward, or must disclose one to a client, depends on their profession's rules; the [referral arrangement compliance review checklist](/resources/referral-arrangement-compliance-review-checklist) lists what to check.
- **The measures are new.** SourceX publishes no benchmark for misquote incidents or terms accuracy. Count them for two quarters before setting targets; those figures are not yet published.

For a plain-language walk through the default itself, see [SourceX referral terms explained](/guides/sourcex-referral-terms-explained); for how a signed exception overrides the default line by line, [when a signed addendum changes default referral terms](/guides/when-a-signed-addendum-changes-default-referral-terms).

## 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.

Send new partners to the default first: [register for a partner link](/register), screen companies against [who qualifies](/who-qualifies) and keep [the terms](/terms) as the one shared reference, with any signed exception held only by the partner it belongs to.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/rewards
- https://refer.sourcex.si/who-qualifies
