# Customer base referrals: a targeted opt-in pilot | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-strategic-partner-wants-to-refer-an-entire-customer-base
Last updated: 2026-11-05

Say no to the base and yes to a pilot. A customer base cannot be referred as a block: every SourceX introduction records one identified company and one opportunity, the program credits companies one at a time, and an introduction its CEO did not know about is usually not a fit. What a strategic partner can run is a targeted opt-in pilot: a few account owners who know a customer's CEO personally ask that CEO, one company at a time, at a capped weekly pace, and only a written yes becomes an introduction.

The request usually arrives with good intentions. A corporate with thousands of customers sees a way to give them something valuable, and someone senior asks why the venture team is talking about five companies when it could talk about five thousand. This page is the answer a platform manager can give, and the design that replaces the blast.

## Three requests hiding inside "refer our whole base"

Ask what the proposal would actually involve, and it usually splits into three different requests. Only one of them can work, and it is the slowest-sounding one.

The partner agreement is explicit about scale. Section 1.4 says a protected opportunity "does not include every business activity of that contact, unrelated dealings or an entire market," and section 3.3 says each introduction record identifies "the company, domain, Partner, opportunity, introduction method and timestamps." A record that names one company cannot hold a customer base. Even a referral system built for volume keeps consent at the level of the single customer: in our paraphrase of Microsoft's Partner Center documentation on managing co-sell opportunities, a partner should have each customer's agreement before passing that customer's contact details to Microsoft, since Microsoft may then contact the customer itself.

| The request | What it would take | Verdict |
|---|---|---|
| Send SourceX our customer list | Passing thousands of companies' names and contacts without any CEO's agreement; the partner agreement gives a partner no authority to share a company's records or personal information | Never |
| Tell every customer at once | One message from a supplier to its whole base, read by CEOs who never asked and some who depend on the supplier | Not part of this design |
| Let account owners ask the CEOs they know | A handful of personal asks, each approved, each answered by one CEO | The pilot |

## Three seats: the strategic partner, its account teams and each customer

A strategic partner holds its customers in more than one way, and each way carries a different limit. Keep them in separate columns before anyone drafts an ask.

If the partner hosts or processes its customers' data, the hosted data is never used to pick or describe a customer. That boundary is drawn tenant by tenant in [the IT vendor hosting page](/guides/when-an-it-vendor-hosts-data-for-many-clients).

| Seat | What it holds | What it may do in the pilot | What it never does |
|---|---|---|---|
| The strategic partner as a corporate | Customer contracts, privacy notices, its brand, its compliance rules | Approve the pilot, the wording and who may ask; decide who registers as partner | Share a list, imply that SourceX endorses it or that its customers will qualify |
| Its account teams, the vendor relationship | Personal relationships with some CEOs, renewal dates, open disputes | Nominate a customer whose CEO they know, and make one ask | Ask during a renewal, tender or dispute, or hint that saying yes helps the account |
| Each customer, an operating company | Its own records and its own decision | Say yes, no or nothing; apply to SourceX itself | Nothing passes through the partner: no records, samples or logins |

## The targeted opt-in pilot design

The design trades reach for evidence. Its job is to find out, on a small scale, whether customers welcome the question and whether any of them fit, before anyone argues about the rest of the base. "Targeted" means the account owners choose a few customers they know; it never means mining the customer database for candidates.

Public facts are enough to decide whether an ask makes sense: SourceX's screening profile looks for roughly 50 or more full-time employees at peak, contractors excluded, and several years in operation, along with records the company created itself and holds the rights to license. A fact nobody knows stays marked unknown; the company answers it in its own application.

| Design element | Rule | Why |
|---|---|---|
| Who nominates | Up to five account owners, each nominating up to two customers whose CEO they know personally | The relationship, not the database, picks the company |
| What may be used | Public facts and what the CEO has said openly; no CRM export, segment query or hosted data | The partner's data about a customer is not the customer's permission |
| Who is left out | Any customer in a tender, renewal or dispute; any whose records mostly belong to its own clients; any the CEO says has already been in touch with SourceX | Leverage, rights and duplicates all end an ask before it starts |
| Who asks | The nominating account owner, in a personal note | Sales leadership approves; it does not send |
| What the note says | What SourceX does, that the CEO alone decides, that nobody can promise a fit, who could be paid, and that the account is unaffected either way | Every line answers a worry before the CEO has to raise it |
| Follow-ups | None; a CEO who does not reply is not asked again | Silence is an answer |
| Consent record | The CEO's dated written yes, and how the CEO wants to be contacted next | Nothing is recorded with SourceX before this exists |
| Unit | One introduction per company, each its own record | The agreement's record names one company |
| Pace | At most three asks a week across the whole pilot | A queue keeps reviews possible and mistakes small |
| Tripwires | A complaint, a CEO raising the commercial relationship, any request to share records, or an ask outside the approved note | Any one pauses the pilot until reviewed |
| Readout | At week 4 and week 8 | Two looks catch a problem while it is still small |

## Approvals inside the partner, and the one each customer gives

The partner's own approvals come first, so a customer never hears about a program its supplier later withdraws. The substance of the compliance review is set out in [what compliance teams review](/guides/what-corporate-compliance-teams-need-to-review-in-a-referral-program). For a customer base, four internal answers come before the one that concerns the company:

1. **Counsel.** Do customer agreements or privacy notices limit using a customer relationship to raise an outside company's program? This is a question for the partner's lawyers, not a conclusion this page can draw.
2. **Compliance.** Who registers as partner, whether anyone may accept the reward, and how each CEO is told who could be paid.
3. **Communications.** The note carries no co-branding and no suggestion that SourceX endorses the partner or that customers get special access; the [co-branding audit](/guides/how-to-avoid-suggesting-a-corporate-partner-endorses-sourcex) covers the details.
4. **Sales leadership.** Renewals stay off limits, and no account owner is measured on asks.
5. **Each customer's CEO.** The only approval that concerns the company itself, given in writing, one company at a time. If a customer is being acquired, its own CEO decides until closing and the acquirer's CEO after it.

## An eight-week pilot log (Illustrative)

Illustrative: a software distributor with 2,400 customer accounts runs the design above. All figures are invented.

Five account owners nominate ten customers. The week-3 tripwire is the useful moment: a CEO asks whether saying no would affect the account's renewal. The pilot pauses. The review finds that this customer's renewal had opened a week earlier, so the ask should never have gone out; the note gains a sentence stating that the account is unaffected whatever the answer, and renewal dates are now checked on the day of each ask rather than at nomination. By week 8: ten asks, three written yeses, five noes, two with no reply, and three introductions, each recorded for its own company.

If one of those three companies later licensed data and SourceX's actual payout to it came to USD 100,000, the reward on that first qualifying transaction would be USD 55,000 (USD 50,000 plus 5%, which beats 15%). SourceX would pay it from its own funds once the conditions in the terms were met, and nothing would come off the compensation in that company's signed agreement.

| Week | Asks made | Written yes | What happened |
|---|---|---|---|
| 1 | 2 | 1 | Both CEOs answered within days |
| 2 | 3 | 1 | One no came with thanks for asking |
| 3 | 2 | 0 | A CEO asked about the renewal: tripwire |
| 4 | 0 | 0 | Review: note reworded; renewals checked on the day of each ask |
| 5 | 2 | 1 | Asks resumed with the new note |
| 6 | 1 | 0 | Last nomination asked |
| 7 | 0 | 0 | No follow-ups sent |
| 8 | 0 | 0 | Readout: 10 asks, 3 yes, 3 introductions |

## Reading trust instead of volume

Three yeses from ten asks is not the result to report first. Report how the noes went: whether any CEO raised the commercial relationship, whether any account owner felt pushed to nominate, whether any complaint reached the account team. Then report the yeses, and whether each company applied on its own. A pilot that produced five introductions and one CEO who felt cornered has failed; one that produced two introductions and ten comfortable conversations has earned a second round.

Expand only if no tripwire fired after the week-4 fix and the CEOs who answered say the ask felt optional. Expansion means more account owners and the same rules, never a broadcast. SourceX has not published how often CEOs agree or how often introduced companies are accepted, and no such figures appear here. A software company running the same idea with its product customers has a separate plan in the [opt-in customer cohort guide](/guides/the-saas-partner-pilot-with-an-opt-in-customer-cohort), and a reseller's version is in [the reseller customer network page](/guides/when-a-reseller-wants-to-refer-its-customer-network).

## Where the pilot design breaks down

- **Dependence.** Customers who rely on the partner for a critical product may find any question from it hard to refuse. The tripwire catches what a CEO says, not what a CEO feels.
- **Account owners' incentives.** If nominating is noticed by managers, nominations will follow attention rather than relationships. Keep asks out of performance reviews.
- **The base may not fit.** If most customers never reached 50 full-time employees, or hold records that belong to their own clients, the pilot will show that quickly, which is worth knowing before anyone promises leadership a number.
- **Demand and review.** A CEO's yes leads to SourceX's review, not to a license; programs differ, and a company that misses one may suit another later.
- **Duplicates and overlap.** A customer may already know SourceX, or another partner may know it too. Only one introduction can be credited, and SourceX settles overlapping cases in duplicate review.

**Method note.** The design applies SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the sample Channel Partner Agreement (version 2026-10-19) and the screening page, read on 2026-10-27, to a strategic partner with a large customer base. Microsoft's guidance is an outside comparison only. The five-owner, ten-company size, the three-a-week cap and the week-4 review are our design choices, not SourceX rules. The pilot log is invented; demand, acceptance and payouts are not measured.

## 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 the partner's approvals are in and the first CEO has said yes in writing, [register the partner of record](/register), check that company against [who qualifies](/who-qualifies) and keep the [program terms](/terms) with the pilot log.

A strategic partner weighing a referral pilot and an investor weighing SourceX itself are making different decisions; the second starts with a request for materials on the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://learn.microsoft.com/en-us/partner-center/referrals/manage-co-sell-opportunities
- https://sourcex.si/investors
