# SaaS team data referral training: 8 role-plays | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-train-customer-facing-teams-on-data-referral-boundaries
Last updated: 2026-11-05

Train the boundary, not the pitch. Customer-facing staff need to hold five lines: the customer's records stay the customer's and never pass through the vendor, the CEO decides, any reward is disclosed, nothing is promised about fit, price or timing, and the introduction stays separate from pricing and renewals. Run eight short role-plays in which a realistic customer pushes on one line, score each answer against a written rubric, and let nobody mention SourceX to a customer until they pass.

A one-page policy does not survive a real conversation. The moment that matters is the customer saying "can't you just send it to them?" on a busy Thursday, and a rep wanting to be helpful. Rehearsal is how the right answer becomes the reflex. The FTC's staff guidance on endorsements makes a parallel point for brands that work through networks of endorsers: they need reasonable programs to train and monitor those people, scaled to the risk. A SaaS company whose staff may mention a program it can earn from is in a similar position.

## What a customer-facing team may do

The role is introduction only. Inside it, a rep may:

- mention that the program exists, through an opt-in resource offered to every customer;
- answer factual questions about how it works, and route the rest;
- disclose that the company may receive a referral reward;
- connect the customer's CEO with SourceX when the customer asks.

Outside it, a rep never picks targets from product analytics, opens or describes a customer's data, exports anything, promises an outcome, or links the topic to price or renewal terms. Who owns what inside a SaaS tenant is explained in [who owns data in SaaS](/questions/who-owns-data-in-saas).

The benefit to the customer is real only when the customer fits: 50+ full-time employees at peak (contractors excluded), years of documented operating history, rights to license its own records and a CEO who wants the conversation. The CEO authorizes a licensing discussion; a champion can sponsor it internally. The [Software and SaaS industry page](/industries/software-and-saas) describes the program from the company's side.

## The five lines every scenario tests

1. **Records.** The records are the customer's, and the vendor never moves them; if the customer licenses any, it does so under its own agreement with SourceX. SourceX's screening guidance treats material that belongs to a company's clients as usually not a fit, which is why [whose data sits in a SaaS tenant](/questions/saas-customer-data-ai-training-rights) matters. A rep discusses only what the customer chooses to describe, at metadata level.
2. **Authority.** The CEO decides, and an introduction the CEO has not heard about is, by SourceX's screening guidance, usually not a fit.
3. **Disclosure.** FTC staff guidance counts a financial relationship as a material connection, so the possible reward is disclosed. SourceX pays any reward separately; it never comes out of the customer's payout.
4. **Promises.** None. A lead, meeting or signature alone triggers no reward, estimates are projections, and SourceX decides fit in its own review.
5. **Separation.** The introduction never shares a deck, a thread or a negotiation with price, discounts or renewal terms.

Email follow-ups carry a sixth rule. The FTC's CAN-SPAM guide says the law makes no exception for business-to-business email, that messages to people you already work with are not automatically transactional, and that opt-outs must be honored within 10 business days.

## The eight role-play scenarios

Each scenario gives the customer one line to say and the observer one line to watch.

| # | The customer says | The trap | Line tested | A passing answer includes |
|---|---|---|---|---|
| 1 | "You already host our data. Can't you just send it to SourceX?" | Helping by exporting | 1 Records | The vendor never transfers records; the company licenses directly; an offer to introduce the CEO |
| 2 | Your own manager: "The admin dashboard shows this account has nine years of tickets. Pitch them." | Targeting from product analytics | 1 Records | Declining to use the dashboard as a list; offering the opt-in resource to every customer instead |
| 3 | "If we take the SourceX meeting, can you do better on our renewal price?" | Trading the introduction for price | 5 Separation | A plain no to any link; the renewal and the introduction stay in separate conversations |
| 4 | "I run operations. I'll sign off, just set it up." | Treating a champion as the decider | 2 Authority | Thanks for sponsoring; the CEO authorizes; asking whether the CEO wants an introduction |
| 5 | "What's in it for you?" | Vagueness about the reward | 3 Disclosure | Your company may receive a reward from SourceX, paid by SourceX and never from the customer's payout |
| 6 | "How much would SourceX pay us?" | Quoting a number | 4 Promises | No estimate; SourceX reviews fit and agrees terms directly with the company |
| 7 | "We're 35 people, but we have years of data." | Implying acceptance | 4 Promises | The published baseline of 50+ full-time employees at peak; no introduction now; a note to revisit |
| 8 | "Please stop sending me these emails." | Delaying the opt-out | Email rule | Confirmation, an immediate stop to SourceX mentions for that contact and the opt-out honored and logged within 10 business days |

Three model answers set the standard for the hardest scenarios:

> **Scenario 1.** "We can't do that, and it's deliberate: your records are yours, and if you license any of them you do it under your own agreement with SourceX. What I can do is introduce your CEO, if they'd like the conversation."

> **Scenario 3.** "I'd rather keep those completely separate. Your renewal terms don't depend on this, and nothing about this depends on your renewal. Let's finish the renewal, and if you're still curious afterwards I'll send you the overview."

> **Scenario 5.** "Fair question. If your company ends up licensing records to SourceX, we may receive a referral reward from SourceX. It's paid by them and never comes out of what you'd be paid."

Owner objections that come up later in a conversation, such as confidentiality or staff concerns, belong to the [objection handling script](/resources/objection-handling-script-template). This session trains the boundaries that come before it.

## How to run and score the session

Sixty minutes is enough. Spend ten minutes on the five lines, then run three rounds of twelve minutes in groups of three (customer, rep, observer), rotating roles, and close with a fourteen-minute debrief on the answers that failed.

The observer scores each line from 0 to 2.

| Line | 0 | 1 | 2 |
|---|---|---|---|
| Records | Offered or accepted data, or used analytics | Hesitated before declining | Kept to metadata and the customer's own route |
| Authority | Treated the champion as the decider | Mentioned the CEO vaguely | Named the CEO as the one who authorizes |
| Disclosure | Did not disclose | Disclosed only when pressed | Disclosed when the topic came up |
| Promises | Quoted fit, price or timing | Hedged without a reason | Said SourceX decides in review |
| Separation | Linked the topic to pricing or renewal | Left the link ambiguous | Separated the two explicitly |

**Pass mark:** no zero on any line and at least 8 of 10. A rep who scores a zero repeats that scenario before mentioning SourceX to any customer. Rerun the session whenever the program terms change.

**Method note.** The scenarios and rubric are our design, derived on 2026-10-26 from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its who-qualifies page, the CEO-authorization rule and the FTC guidance cited here. They have not been validated against customer outcomes, and no pass rates or customer reactions have been published.

## Tenant access is never a referral channel

Support engineers and administrators can see inside customer tenants because the customer granted that access to run the service. The training should say in plain words that this access is never a referral channel: nothing seen while supporting a customer is used to select, describe or approach it.

Record permissions the way mature partner programs do. Microsoft's referral records carry separate consent flags for sharing information with other organizations, contacting users and sharing the referral with Microsoft sellers. Mirror that in your CRM with three separate fields: the customer agreed to hear about SourceX, the CEO agreed to an introduction, and the customer agreed that its contact details may go to SourceX. The [client consent guide](/resources/how-to-document-client-consent-for-a-referral) shows how to keep the record.

## Pilot with one team, then monitor

Start with a single customer success team for one quarter, using an opt-in resource rather than outbound lists. One named person submits introductions for the company, after signing the SourceX Channel Partner Agreement, and only one partner can be credited per customer, so reps route interest to that person instead of registering separately.

Monitoring is what keeps the training honest. Each month, review a sample of SourceX mentions in emails and call notes against the five lines, and count role-play pass rates, boundary errors found in review, customer opt-ins and complaints. Publish the counts internally. SourceX has published no benchmark for any of them. The [disclosure examples](/resources/ftc-disclosure-examples-referral) give reps wording to reuse.

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

Once your team passes the scenarios and a customer's CEO wants the conversation, [register for a partner link](/register), confirm fit against [who qualifies](/who-qualifies) and keep the [program terms](/terms) open in the session.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- 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
- https://learn.microsoft.com/en-us/partner-center/developer/referral-resources
