# Large network referral agreement review | SourceX

Canonical: https://refer.sourcex.si/guides/when-to-offer-a-bespoke-large-network-arrangement
Last updated: 2026-11-05

Offer or request a bespoke arrangement only after a network's own dated records pass five gates: enough active introducers, unique companies that pass the fit facts, duplicates caught before submission, screening capacity to spare, and a named problem the default terms leave unsolved. Member counts and logos prove none of these. Most large networks belong on the default Channel Partner Agreement; the few that pass usually need one narrow change, written into an addendum that both parties sign.

This page is for heads of channel partnerships who run a large bench of introducers: an association's members, an alliance of firms, a reseller ecosystem. The terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the sample Channel Partner Agreement and the who-qualifies page were each read on 26 October 2026 for this review. SourceX has not published when it offers or accepts bespoke terms, so the gates and thresholds below are this page's own planning method, and every network in the examples is Illustrative.

## What the default agreement already does for a big network

Many requests for "something bespoke" turn out to be answered by the standard documents. Check this table before drafting anything.

| Large-network worry | What the default already says | Bespoke needed? |
|---|---|---|
| Several members know the same company | The first valid introduction within the 90-day window is credited once the company submits a verified application; one partner per company, decided from dated records | No |
| A member proposes a company SourceX already knows | Any earlier application, relationship, lead, account or email correspondence makes it a duplicate, not credited | No |
| Members introduce several companies in one corporate group | No cap applies; the USD 50,000 floor on a first qualifying transaction applies once per referred company, and not again on its repeats, renewals or amendments | No |
| Members want to follow their own referrals | Each partner gets what it reasonably needs about its own referral, through generic stages or reference codes | No |
| The network wants to announce the program and name SourceX | Neither party may publicly identify the other as a partner without written authorization | Yes, a short written authorization |
| A member leaves the network | Rewards already earned stay payable once their conditions are met; how credit works for an introduction still in review when the member exits is not set out publicly | Ask SourceX and write the answer down |
| The arrangement's length | One year, 30 days' notice, renewal only with fresh signatures | No |

Two rows in seven need any writing at all, and one of them is a question rather than an exception. That ratio is the first finding of most reviews. For the finance view of the same decision, see [the financial questions before a large-network partnership](/guides/the-financial-questions-to-ask-before-a-large-network-partnership); for which document overrides which, [when a signed addendum changes default referral terms](/guides/when-a-signed-addendum-changes-default-referral-terms).

## Activation and referral quality, as this review counts them

A registered member is a name on a list. PartnerStack's glossary, in paraphrase, defines an inactive partner as one who has joined a program but has not contributed to its success or produced meaningful value, and a large network is usually mostly inactive by that test. The review therefore counts three things, each from dated records:

- **Enabled member:** has signed the Channel Partner Agreement and holds a partner link.
- **Active introducer:** an enabled member with at least one proposal that reached the network's screen in the last 90 days.
- **Referral quality:** the share of unique proposed companies, each counted once however many members named it, that pass the fit facts at the network's screen and are not already known to SourceX.

The fit facts are SourceX's published ones: at least 50 full-time employees at the company's peak (contractors are excluded from the count), a documented operating history, the right to license its records, and the CEO as the authorized contact who wants the conversation. 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. Screening answers come from conversations at metadata level, never from files, samples or logins. Whether a company's records match current demand is decided only in SourceX's review.

## The five-gate commercial review

Run the gates in order on two full quarters of records, with the criteria version noted beside every screen result. A gate that fails stops the review; it does not get averaged away by a strong gate later.

| Gate | Question | Dated evidence | Passes when (planning line) | If it fails |
|---|---|---|---|---|
| 1. Activation | Are enough members actually proposing? | Proposal log by member | At least 15 active introducers and at least 20% of enabled members active | Stay on default terms; work on activation |
| 2. Unique fit | Do proposals become fit-passing companies? | Screen result per unique company | At least 12 unique fit-passing companies, and at least 40% of unique proposals passing | Stay on default terms; tighten the screen |
| 3. Duplicates | Does the network catch collisions before SourceX does? | Internal claim log and duplicate outcomes | Member collisions resolved before submission, and under 1 in 5 submissions found to be duplicates | Build the claim log first |
| 4. Capacity | Can the network screen what arrives? | Arrivals and screening hours by month | Arrivals below 80% of screening capacity for three months | Pause recruiting or add hours |
| 5. Named gap | Is there a problem the default leaves open? | The clause, the cases it affected, their dates | At least two dated cases where the default gave an unworkable result | No addendum; the default works |

The thresholds are planning lines chosen for a bench of a few hundred members. Change them for your network, write the version you used beside the result, and never present them as SourceX criteria.

## Three networks at review (Illustrative)

Illustrative: invented networks, counts and dates. None describes a real partner or a signed arrangement.

**Network A, the underperforming cohort.** A 420-member professional association enabled 300 members after a sign-up drive at its annual conference. Over two quarters, 9 members proposed 14 companies, 11 of them unique, and 4 passed the fit facts. Gate 1 fails at 3% of enabled members active, and gate 2 fails as well. The association's request for a custom rate is premature; the work is activation, starting with the members who already proposed.

**Network B, the duplicate risk.** A 60-firm consulting alliance has 31 active introducers, but its firms share clients. Their 58 proposals named only 37 unique companies, and of the 30 it submitted, 9 turned out to be companies SourceX already knew through earlier email correspondence. Gate 3 fails. Two firms had also proposed a parent and its subsidiary separately; there is no cap to share, but the USD 50,000 floor applies once per referred company, and SourceX decides whether the second entity counts as its own company during duplicate review, under no published rule. The alliance needs a claim log that checks every name against members' earlier proposals before anyone contacts a CEO; [counting the same company across networks](/guides/how-to-avoid-counting-the-same-company-across-three-networks) shows one way to build it.

**Network C, the capacity limit.** A group of 25 managed-service providers has 18 active introducers, 40 unique proposals and 22 fit-passing companies, a 55% pass rate, with few duplicates. Its one screener has 24 hours a month at 1.5 hours per screen, so capacity is 16 screens against 20 arrivals: gate 4 fails with arrivals at 1.25 times capacity. After the group adds a second screener and holds arrivals under 80% for three months, it reaches gate 5 with two dated cases. Its newsletter could not name SourceX without written authorization, and its members kept asking for a single status view. Both are narrow, and neither touches money.

## The written-exception guide

When all five gates pass, write the request as narrowly as the problem. The sample agreement says a signed addendum overrides a provision only if it expressly identifies the change, and that amendments need a writing signed by both parties. A dashboard edit, an unanswered message or a one-time exception amends nothing.

1. **Name the clause** the change touches, by section.
2. **Attach the dated cases** from gate 5.
3. **Propose the smallest wording** that fixes those cases and nothing else.
4. **List what stays default**: the fit facts, the CEO's authority to decide for a company, the duplicate rule and the payment conditions.
5. **Set a review date** inside the agreement's one-year term.
6. **Get both signatures.** On SourceX's side the sample agreement names its Founder & CEO as signatory.
7. **Keep it private.** Members on default terms see the default, not another partner's addendum.

| Request | Default today | Documented written path | This review's view |
|---|---|---|---|
| Name SourceX in member newsletters | No public identification without written authorization | A written authorization | Common, narrow and worth asking for |
| Count a partial delivery as its own handoff for payment timing | Separate only by express written agreement | Written agreement per deal | Case by case, never network-wide |
| Reward a transaction first agreed after the protection period | None unless agreed in writing | Written agreement | Case by case |
| A different rate or base | Schedule A sets them; a signed Schedule A prevails | A signed Schedule A | SourceX has not published when it agrees; never promise members |
| A central desk that submits for members | Each partner signs, and one partner is credited per company | Settle the structure in writing before launch | Decide before anyone introduces; check [fee-sharing rules](/questions/fee-sharing-arrangement-meaning) |
| Relaxed fit facts or duplicate rule | They protect companies and review time | None | Do not ask |

If the network will pass part of any reward to members, that is the network's own arrangement, and professional rules may restrict it; the [referral arrangement compliance review checklist](/resources/referral-arrangement-compliance-review-checklist) lists what to check.

## Capacity, support, concentration and overlap, before and after

| Load | On default terms | Under a bespoke arrangement |
|---|---|---|
| Screening | Your screener checks fit facts and the claim log | Unchanged; an addendum adds no screening capacity |
| Support | Members ask you, and you point to the terms | Members also ask about the exception; brief your team first |
| Concentration | One prolific member is a risk you can see | The exception may rest on that one member's output; record the share |
| Overlap | Collisions settle by dated records | Unchanged; no exception should promise priority in a collision |

Concentration deserves a number. If one member produced half of gate 2's fit-passing companies, the case for an exception is really a case about that member, and it ends when they leave.

## Gates for keeping the arrangement, and paths to correct it

Review the exception at its date with the same five gates. Return to the default if activation falls below gate 1 for two quarters, if duplicates climb back over 1 in 5, or if the screener the capacity case relied on leaves. Members may correct their own rows in the proposal log, with the reason noted beside the change. Attribution disagreements go to SourceX with the referral details and evidence, as the terms' dispute section sets out. The terms also say signed agreements are never silently replaced and their rates and exceptions are preserved, so an exception stays in force until both parties sign a change, even if it no longer fits.

## Where this review misleads

- **Small benches with one superb introducer** fail gate 1 and may still deserve attention; the review is built for volume.
- **The thresholds are judgment calls,** written for a bench of a few hundred members; a network of 40 needs its own.
- **Demand moves.** SourceX applies the criteria of a specific program, and a company that fits today may not fit later, or the reverse.
- **The review counts companies, not value.** A network that passes every gate can still see no completed deals.

To test the method, record for two quarters the share of "bespoke" requests the first table answered without any writing; SourceX has not published that share, so your count is the evidence. The [three-rung partner ladder](/questions/how-to-qualify-referral-partners) helps with gate 1.

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

If your network has not yet passed the five gates, start members on the default: [register for a partner link](/register), screen each company against [who qualifies](/who-qualifies) and read the [program terms](/terms) that apply until something else is signed.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://partnerstack.com/glossary/inactive-partner
