# SaaS referral program and SourceX overlap | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-saas-company-s-referral-program-and-sourcex-overlap
Last updated: 2026-11-05

The two programs meet at one point only: the same customer can sit in both. Your referral program decides who brings you new buyers and what you pay them. SourceX's program covers an introduction of your customer's CEO to license the customer's own business records, with a reward SourceX pays. Keep them apart on seven lines: who is referred, whose records, who decides, what consent covers, who pays, what the vendor touches and who gets credit. The customer's records never pass through you.

That separation is not a legal nicety. A SaaS company holds two assets that look similar and are not: its relationship with the customer, which it owns, and access to the customer's records, which it does not. The overlap goes wrong when the second is treated as if it were the first.

## Where the two programs meet in practice

A partnerships director usually meets the overlap in one of four ways:

1. **Your partners know your customers.** Resellers, implementation consultants and co-sell partners all hold customer relationships, and any of them could introduce one of your customers to SourceX.
2. **You want to introduce customers yourself.** The vendor registers as a SourceX partner and invites customers to consider licensing their own records.
3. **Your customers refer each other.** Your existing customer referral program pays for new subscriptions; nothing in it covers data licensing.
4. **Your product team sees a feature.** Someone proposes an export button "for SourceX". That is outside an introduction-only role altogether.

Mature partner programs already separate these motions. Microsoft describes co-selling as any collaborative engagement with its partner ecosystem, from joint demand building and sales planning to lead sharing and marketplace-led commerce, and it sorts opportunities into categories that include co-sell, partner-to-partner and private deals. Its referral records go further: each carries a consent object with separate flags for sharing information with other organizations, contacting users and sharing the referral with Microsoft sellers. One permission never stands in for another. Copy that habit before you copy anything else.

## Is there a real benefit for the customer, and who can say yes?

The benefit exists only for customers that fit. A company introduced to SourceX needs 50+ full-time employees at peak (contractors excluded), years of documented operating history, the rights to license its records and a CEO who wants the conversation. If most of your customers are small teams, the overlap is narrow, and saying so internally before you build anything saves a quarter of wasted enablement. The [Software and SaaS industry page](/industries/software-and-saas) describes what fit looks like on the customer side.

For a customer that does fit, the benefit is concrete: it may be paid for licensing records it already owns, under an agreement it negotiates directly with SourceX. Your champion, usually a functional buyer of your product, can sponsor the idea internally. Authorizing a licensing discussion and signing for the company remain the CEO's call. Under SourceX's own screening guidance, an introduction made behind the CEO's back is usually not a fit, so a champion's enthusiasm is a reason to ask the CEO, not a substitute for asking.

## The program boundary comparison

Fill the middle column from your own partner terms. The SourceX column comes from the published program terms (Version 2026-11-04) and the who-qualifies page, checked 2026-11-05. The right-hand column is the rule that keeps the two from blending.

| Line | Your SaaS referral or partner program | SourceX referral program | Boundary rule |
|---|---|---|---|
| 1. Who is referred | A prospect who may buy your product | A company, possibly your customer, whose CEO may license its own business records | Never present the introduction as part of your product or roadmap |
| 2. Whose records | Yours: pipeline, deal registration and opportunity data | The customer's own records; material that belongs to the customer's clients is usually not a fit | Admin access to a tenant is not a right to describe or license what is in it |
| 3. Who decides | The prospect's buyer for your product | The customer's CEO, who authorizes a licensing discussion | A champion or administrator can sponsor internally, not authorize |
| 4. What consent covers | Sharing a prospect's contact details with your partner | A separate yes to be introduced, after which the customer applies itself | Log each permission on its own; one never implies another |
| 5. Who pays what | You pay your referrer, usually from your own revenue | SourceX pays the partner the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, separately and never from the customer's payout; the USD 50,000 floor applies once per company | No credit, discount or renewal term tied to an introduction |
| 6. What the vendor touches | Opportunity records in your CRM | Metadata only: record type, rough volume, years of history, system name | No exports, samples or credentials, even where your platform could produce them |
| 7. Who gets credit | Your own rules, such as deal registration | First valid introduction within the 90-day window, credited on a verified application; one partner per company; companies SourceX already knows are duplicates | Agree internally who registers before anyone contacts the customer |

**Method note.** The comparison has stated criteria: each line is a question a customer, a partner or your counsel would ask, answered from the cited terms for SourceX and left blank for your program so you fill it from documents rather than memory. It does not measure customer reactions, opt-in rates or outcomes. No such figures have been published by SourceX, and none are implied here.

## Product analytics cannot choose referral targets

Product analytics are the strongest temptation in the overlap and the weakest basis for it. A dashboard that ranks tenants by record count and account age looks like a ready-made target list. It answers none of the questions that matter.

- **It does not show ownership.** Records in a tenant may be the customer's own, or its clients' records that it processes. The [SaaS customer data rights question](/questions/saas-customer-data-ai-training-rights) walks through why that line decides fit.
- **It does not show permission.** Whether your customer agreement lets you use usage data to choose targets for a third party's program is a question for your counsel and your contract, not for the partnerships team.
- **It does not show interest.** Only the customer's CEO can say whether the company wants the conversation.

So selection should come from the customer, not the telemetry. Publish an opt-in resource, such as a short explainer in your customer community or newsletter, and let customers raise their hand. Then ask what the company holds at metadata level and whether the CEO wants an introduction.

Two disclosure rules travel with any outreach. FTC staff guidance counts a financial relationship as a material connection that should be disclosed, so tell customers plainly that your company may receive a referral reward from SourceX; the [disclosure examples](/resources/ftc-disclosure-examples-referral) show phrasing. And an email promoting SourceX to customers is commercial email: the FTC's CAN-SPAM guide says the law makes no exception for business-to-business messages, reads the relationship-message exemption narrowly and requires opt-outs to be honored within 10 business days.

## Three overlaps, resolved (Illustrative)

Illustrative. Generic companies, invented facts, no outcomes implied.

**A customer's COO raises it.** A 400-person field-services customer's COO asks your account manager whether "the AI data thing" is real. The account manager explains the program in two sentences, discloses the possible reward and asks whether the CEO would want an introduction. The CEO says yes a week later. The vendor submits the introduction; the customer applies and deals with SourceX directly from then on.

**A reseller wants the same customer.** Your largest reseller manages that account and also registers with SourceX. Before anyone contacts the CEO, the two of you agree in writing who will introduce. Only one partner can be credited, and a second introduction adds noise for the customer without adding value. The [referral partner versus reseller comparison](/compare/referral-partner-vs-reseller) explains why a data licensing introduction can only ever be a referral, never a resale, whoever makes it.

**A product manager proposes an export connector.** The request is declined. A vendor-built pipeline would put the vendor between the customer and its own records, which is precisely the role the introduction-only model avoids. If the customer later licenses records, it does so under its own agreement with SourceX.

## Pilot opt-in introductions before you scale

Run one quarter with a small, opt-in cohort before any wider launch.

- **Owner:** one named person registers for the vendor and signs the SourceX Channel Partner Agreement before any introduction is submitted.
- **Scope:** customers who answer an opt-in invitation, not a list built from analytics.
- **Script:** the seven-line comparison, condensed to one paragraph, plus the disclosure sentence.
- **Stop rules:** pause if a customer says the topic felt tied to pricing, or if support tickets mention it as pressure.
- **Measures:** invitations sent, opt-ins, CEO conversations agreed, complaints and unsubscribes. Record them as counts; this page publishes no benchmark because none exists yet.

Customer referral programs and professional partner programs serve different jobs, as the [customer referral versus partner program note](/questions/customer-referral-program-vs-partner-program) explains. The overlap works when it stays an invitation the customer controls. The [SaaS data partner overview](/guides/saas-data-partner) covers the company side.

## 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 a customer has opted in and its CEO wants the conversation, [register for a partner link](/register), work through [who qualifies](/who-qualifies) for that customer and read the [program terms](/terms) so the seven lines hold from the first email.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://learn.microsoft.com/en-us/partner-center/referrals/co-sell-overview
- https://learn.microsoft.com/en-us/partner-center/developer/referral-resources
- https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking
- https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
