# Software reseller customer referrals: opt-in pilot | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-reseller-wants-to-refer-its-customer-network
Last updated: 2026-11-05

Run an opt-in pilot, not a list upload. A reseller's customer list, the license data in its vendor portals and the admin access it holds can suggest which customers might fit, but none of them lets the reseller license a customer's records or speak for the customer. Tell customers once what SourceX looks for, let each CEO who is interested come forward, and introduce each willing company separately, in that CEO's words. Every customer is its own company, with its own CEO, its own fit test and its own attribution window.

This page is for resellers of software subscriptions, cloud services and hardware who have hundreds of customer relationships and wonder whether those relationships could become introductions at scale. They can, but only in the sense that many single introductions can follow one announcement. A software company piloting the same idea with its own product customers has a separate plan in the [SaaS partner opt-in cohort guide](/guides/the-saas-partner-pilot-with-an-opt-in-customer-cohort). A reseller's position differs: it sits between vendor and customer, holding delegated admin rights and vendor-portal data, and its customers often have other partners who could introduce them first.

## What a reseller holds about its customers, and whose it is

A reseller sits on four kinds of customer information. It is worth naming them, because each one tempts a different shortcut.

1. **The customer list and contacts.** The reseller's commercial relationships, usually shaped by its vendor agreements and its customers' contracts.
2. **License and usage data.** Seat counts, subscription tiers and renewal dates, read from vendor portals. This describes the customer's purchases, not the customer's operating records.
3. **Delegated admin access.** Rights the customer granted so the reseller can provision, support and bill.
4. **The customer's own records.** Tickets, orders, projects and documents the customer created. These are the customer's, and they are what SourceX would actually license.

The large vendors' own channel programs show how customer details are expected to move between partners. Microsoft's Partner Center guidance tells partners to be sure they have the customer's consent before giving Microsoft the customer's contact information for a deal, because Microsoft may contact the customer directly. AWS's Partner Central documentation applies the rule in the other direction: AWS sales staff must secure the customer's consent before passing an opportunity to a partner (paraphrase). If customer contact details need consent to travel inside a vendor's own channel, an introduction to an outside company deserves at least that bar.

SourceX's screening page closes the remaining gap. Material that belongs to a company's clients is usually not a fit, and neither is an introduction made without the decision maker's knowledge. From a reseller's seat, items 1 to 3 identify a possible conversation; only the customer's CEO can start one, about item 4.

## Which renewals and migrations make a good pilot moment

Events in the reseller's normal calendar decide when to send the announcement. They should never be used to pick customers by mining their usage data.

- **Business reviews and renewals.** A quarterly or annual review already has an agenda; one item about SourceX fits there without a separate campaign.
- **End of support for a product.** When a vendor retires a product, customers decide what happens to years of history held in it. The question "who wants to keep it?" leads naturally to "who owns it?"
- **Platform moves.** A customer moving to a new system often leaves an archive behind, and someone inside the customer, usually the IT manager or the operations lead, owns that decision and can carry a question to the CEO.
- **Mergers among customers.** When two customers combine, the acquirer's CEO decides for both from closing onward, and the merged group counts as one referred company, so the USD 50,000 floor applies once, to its first qualifying transaction.

The person a reseller talks to is rarely the CEO. That contact can be a useful internal sponsor, but the pilot always waits for the CEO's own yes.

## The opt-in reseller pilot plan

Six phases over roughly a quarter. The weeks are Illustrative; the gates are not.

| Phase | Weeks | What the reseller does | What it never does | Gate before the next phase |
|---|---|---|---|---|
| 0. Prepare | 0 | Signs the SourceX Channel Partner Agreement, rereads its vendor and customer contracts for limits on contacting customers about third parties, and writes a one-line disclosure that it may receive a reward | Picks customers by reading their usage or storage data | Agreement signed, contracts checked, disclosure written |
| 1. Announce | 1 to 2 | Adds one short item to the pilot group's business reviews or newsletter: what SourceX does, the published fit tests and an invitation for interested CEOs to reply | Attaches forms, estimates or the words "you qualify" | Someone at a customer replies |
| 2. Raise a hand | 2 to 6 | Logs each reply and asks whether the CEO knows; a manager who replied is asked to take it to the CEO | Chases a silent customer more than once, or goes around the person who replied | The CEO wants to talk |
| 3. Fit call | Any | Asks five descriptive questions and writes down the CEO's answers | Opens a console, runs a report or quotes seat counts | No known failed test |
| 4. Introduce | Any | Sends one written introduction per company after the CEO's written yes | Submits a spreadsheet, bundles customers or attaches records | The company applies itself |
| 5. Review | 12 | Counts what happened and decides to widen, hold or stop | Presents the counts to customers as forecasts | A written decision |

**The five fit-call questions**, answered in the CEO's own words:

1. What was the company's highest full-time headcount, leaving out contractors?
2. Which systems hold the company's own records, and from what year?
3. Do any of those records belong to the company's customers?
4. Has the company licensed any of its data for AI training before?
5. Has anyone at the company already been in touch with SourceX?

Question 4 matters because SourceX's suppliers confirm their data has not been licensed for AI training before. Question 5 matters because of duplicates, covered below. SourceX's own first step is a short set of questions with no files, and no records are shared at that stage, so nothing in the pilot requires the reseller to export, count or sample anything.

**What to record.** For the pilot group: customers who received the item, replies, CEO conversations, companies passing every known test, written yeses, introductions submitted, verified applications and hours spent. SourceX has not published conversion rates for any channel, so the pilot measures your own; no figures from other resellers are available here.

## Three hats a reseller wears, and the one it never wears

A reseller doing this work holds three roles at once, each under different paper:

- **Custodian.** It holds admin rights the customer delegated for provisioning and support. Those rights cover service work, and the partner agreement gives a partner no authority to share a company's records or reach its extraction systems.
- **Seller.** It earns margin under its vendor and customer agreements. Nothing about SourceX changes those agreements or adds to that margin.
- **Referral partner.** It introduces a CEO under the SourceX Channel Partner Agreement and may receive a reward paid by SourceX.

The hat it never wears is licensor. The customer licenses its own records directly to SourceX and signs its own deal confirmation, so there is nothing for a reseller to buy, bundle or mark up; the [referral partner versus reseller comparison](/compare/referral-partner-vs-reseller) sets out why. Whether the records can be licensed at all is a question for SourceX's rights review, and whether to try is the customer's CEO's decision. Resellers weighing whether to take on the referral role at all can work through [choosing between referral partner, reseller and service provider](/guides/referral-partner-reseller-or-service-provider-choose-the-actual-role).

## One customer, one introduction

Each willing customer goes through the program on its own. Under section 2 of the terms, SourceX credits a single partner per company: the one whose valid introduction of a company new to SourceX comes first, once that company files a verified application inside 90 days. Section 3 treats a customer that already had any application, relationship, lead, account or email correspondence with SourceX as a duplicate, which is why the fit call asks about it. If a customer's accountant or a SaaS vendor introduced it first, the reseller is second, and [overlaps between a reseller and a SaaS vendor](/guides/when-a-reseller-and-a-saas-vendor-both-know-the-customer) explains how to agree who introduces before anyone writes. When two customers belong to one corporate group, SourceX treats the group as one referred company for the once-per-company floor, and whether one sister company's earlier introduction changes credit for the other is something the terms leave to SourceX's duplicate review.

The introduction itself is short: who the reseller is, that it supplies the company, that the CEO asked to be introduced, and the CEO's own description of the records. It leaves out seat counts, storage figures, usage reports, value estimates and any suggestion that SourceX will buy. The partner agreement bars a partner from telling a company that an estimate, positive interest, a signature or an upload assures a purchase or a reward. After the introduction, SourceX may deal with the company directly without affecting valid attribution.

## Four customers who replied (Illustrative)

Illustrative: a 60-person reseller sends one item to the 45 customers due a business review this quarter. Four replies come back. The companies and facts are invented.

| Customer | What the CEO said on the fit call | Decision | Why |
|---|---|---|---|
| 420-person HVAC service company | Twelve years of service tickets and technician notes in its field-service system; nothing licensed before; never contacted SourceX | Introduce, after a written yes | Every known test passes and the CEO asked |
| Design studio whose full-time staff peaked at 38 | Wants to hear more | Do not introduce; explain the size test | Its full-time peak never reached the published threshold of 50 |
| 260-person payroll bureau | Most of its records are its clients' payroll files | Do not pitch it as a fit; the CEO may ask SourceX directly about the bureau's internal records | Material belonging to clients is usually not a fit |
| 300-person distributor | Its CFO filled in SourceX's form last year | No introduction; the company can continue with SourceX itself | Earlier contact makes it a duplicate, so no partner is credited |

If the HVAC company's first qualifying transaction eventually paid it USD 100,000, the reseller's reward would be USD 55,000 (the greater of USD 50,000 plus 5%, and 15%), paid by SourceX and never subtracted from the compensation in the company's signed agreement. That is an Illustrative figure, not a forecast; most pilots will produce more "not a fit" rows than introductions, and that is the pilot doing its job.

## Where an opt-in pilot falls short

- **Contracts can forbid the announcement.** A vendor agreement or a customer contract may limit what a reseller says to customers about third parties. Read them in phase 0; this page is not legal advice.
- **Dependence feels like pressure.** A customer that relies on you for its systems may hear a suggestion as an expectation. Say plainly that ignoring the item changes nothing about your service, and disclose the possible reward; the [MSP disclosure answer](/questions/msp-vendor-referral-fees-disclosure) covers the wording.
- **Small numbers.** A pilot of 45 customers may produce one introduction or none, which says little about the next quarter.
- **Demand moves.** SourceX matches companies to its current data needs, so a company that passes every known test can still be declined today and fit later.
- **Rights are decided in review.** Customer contracts, privacy duties and earlier licenses are checked by SourceX, not by the reseller.

The fit tests themselves, for the announcement: a full-time workforce that reached 50 or more at its peak, with contractors excluded; documented operating history; rights to license the records; and a CEO 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. For a reseller thinking about its own records rather than its customers', see [how to sell an IT reseller business](/guides/how-to-sell-an-it-reseller-business).

## 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 phase 1 goes out, [open a partner account](/register), copy the fit tests from [who qualifies](/who-qualifies) into the announcement word for word, and read the attribution and duplicate sections of the [program terms](/terms); more partner playbooks sit in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/partner-center/referrals/solution-assessments
- https://docs.aws.amazon.com/partner-central/latest/crm/crm-integration-data-security.html
- https://sourcex.si/how-it-works
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
