When a customer success manager spots a potential referral: a three-gate permission and handoff checklist, from the remark you heard to the CEO who decides

Short answer

Pause, then clear three gates before saying anything. First, the signal must come from what the customer told you, never from looking through its data in your product. Second, only the customer's CEO can decide on a licensing conversation, so ask your contact whether the CEO would want information, and get permission before passing on any name. Third, hand the lead to your partnerships owner with a metadata-only note, step out, and keep the topic away from renewals.

Visual briefFull-size diagram
A left-to-right timeline from a remark heard on a customer call through three gates (source of the signal, permission from the customer, metadata-only handoff) to the CSM stepping out, with a stop exit below each gate.
The three gates of the CSM permission-and-handoff checklist. Any stop exit ends the referral and leaves the account untouched.

The customer's records stay the customer's throughout. Your company introduces the people who can decide; SourceX does its own review; the customer licenses or does not. Nothing in your product, your admin console or your usage dashboards plays any part.

Which remarks count as a signal, and which do not?

A good signal is something the customer chose to say. The test is simple: could you repeat where you learned it without mentioning your product's data?

What you noticedWhere it came fromAct on it?Why
"We are retiring our old ticketing system after 14 years"The customer, on a callYes, through the gatesThe customer volunteered a dated event and the span of its records
"Our CEO asked what our data might be worth"The customer, in a business reviewYes, through the gatesThe decision-maker is already curious
A tenant with millions of records in your productYour admin console or usage reportsNoIt is customer data processed for the service, not a lead source
A customer planning to cancel seatsYour billing systemNo, unless the customer raises its archiveBilling data was not given to you for prospecting
"Some AI company emailed us asking to buy data"The customerYes, through the gatesThe customer opened the topic itself

The reason for the third row is legal as well as ethical. Most SaaS vendors process customer data on the customer's behalf. Under the EU's General Data Protection Regulation, a processor handles personal data only on the controller's documented instructions (Article 28(3)(a)), and a processor that decides the purposes of processing itself is treated as a controller for that processing (Article 28(10)). Outside the EU the rules differ, but the point holds: combing tenant data for referral prospects is a purpose no customer gave you. If the customer mentions a migration or a lapsing subscription, the pages on workflow context lost in a SaaS migration and archive retention after canceled seats explain why the date matters.

A real benefit for the customer, and the person who can say yes

The customer's benefit is a separate decision about records it created, with no effect on its product or its contract with you. If raising it would feel like a favor asked of the customer, or a pitch, do not raise it.

Your day-to-day contact, often an operations lead or a system administrator, can carry the idea and describe which systems hold records. Only the customer's CEO can authorize a licensing discussion and sign for the company. So the question to your contact is not "do you want to do this?" but "would your CEO want information about it?", and your contact decides whether to ask.

The CSM permission-and-handoff checklist

Twelve checks in three gates. Every check needs a yes before the next; any stop ends the referral and leaves the account as it was.

Gate 1: the source of the signal

#CheckA pass looks likeStop if
1The signal came from the customer's own wordsYou can quote the call or emailYou learned it from tenant data, usage or billing
2Your company runs an approved introduction motionA named partnerships owner; the company registered and signed the partner agreementNobody owns it; log the remark and tell your manager
3The account is calmNo renewal negotiation, escalation or price dispute openAny of those is live
4Your own position is clearThe company, not you personally, is the partner, or you have written employer approvalYou would take a personal reward without approval

Gate 2: permission

#CheckA pass looks likeStop if
5You asked one neutral question"Would your CEO want information about this?", with no follow-up pressureThe contact hesitates and you push
6You know who the CEO is, and the contact will raise itThe contact chooses to ask, on their own timingThe contact cannot or will not reach the CEO
7You have explicit permission to pass on namesA dated yes to sharing name and email with your partnerships owner and SourceXPermission is assumed or second-hand
8The customer knows how the reward worksTold that SourceX pays any reward separately and never deducts it from the customer's payoutYou would rather the customer did not know

Gate 3: handoff

#CheckA pass looks likeStop if
9A metadata-only noteCompany, headcount band, years in business, systems the customer named, its own words, consent dateThe note contains anything from inside your product
10Nothing else movesNo exports, screenshots, record counts, samples or loginsAnyone asks you to "pull some numbers"
11The right people take overThe partnerships owner submits; the customer applies itself; you step outYou stay in the licensing conversation
12The outcome is logged without promisesOne line in the CRM; no mention in business reviews unless the customer raises itAnyone links it to renewal or pricing

Check 7 follows a pattern large partner programs already use. Microsoft, for example, tells partners creating co-sell referrals that Microsoft can use the customer's contact details to reach the customer directly, so the partner should have the customer's consent before sharing them. Check 4 matters because many employers require written approval for referral income tied to customers; see employee referral fees and employer consent.

Method note. The checklist applies SourceX's program terms and fit guidance, GDPR Article 28 and Microsoft's consent step for co-sell referrals, all read on 2026-10-26, to the moment a CSM hears a signal. It is a process aid, not legal advice; your own contracts and privacy notice decide what your team may do. No figures on how customers respond to these questions have been published.

Three calls, three outcomes (Illustrative)

Generic companies and invented facts; no outcome is implied.

A. An owner-led customer clears all three gates. The operations director of a 210-person plumbing-supply distributor mentions retiring a 14-year-old ticketing system. The founder is CEO. The CSM asks one question; the director raises it with the founder, who wants information. With a dated permission, the CSM sends the partnerships owner a five-line note and steps out.

B. A network intermediary changes the route. The CFO of a 900-person logistics customer says the board has asked about AI and data. The company is owned by a buyout fund whose operating partner, it turns out, already works with a referral partner. The partnerships owner checks before doing anything: only one partner can be credited for this logistics company, credit follows whichever valid introduction came first in the 90-day window and is confirmed when the company submits a verified application, and a company SourceX already knows is a duplicate. The CSM's note is logged, and the vendor steps back.

C. A no-fit counterexample stops at once. A 120-person medical billing customer says it holds "years of claims for hundreds of practices." Those records are its clients' and contain patients' personal data. SourceX's screening guidance treats client material and personal consumer data as usually not a fit. The CSM says nothing further and logs no lead.

Keep vendor access and customer rights apart

A CSM sees three kinds of information, and only one of them can start a referral.

  • The conversation. What the customer chose to tell you. This is the only source for gate 1.
  • Your product's data about the customer. Tenant content, record counts, usage and admin views. It is the customer's data processed for the service; it never starts, sizes or supports a referral.
  • Your company's account records. Headcount band, industry and tenure in your CRM. Partnerships may use these to decide which customers to approach in a planned program, as set out in the partner opportunity beyond selling another software seat.

A customer that wants to license is screened on the published fit facts: 50+ full-time employees at peak with contractors excluded, documented operating history, rights to license and location. 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. What stays unknown until SourceX reviews the customer: relevance to a current program, contract limits on reuse and what a license would cover. If your own company is weighing whether to license its own support or engineering history, that is a different question, covered in the SaaS data partner guide.

Pilot it with the CS team, and protect the relationship

Do not roll this out by memo. Run one quarter with a small group of CSMs who have the checklist and a named partnerships owner. Count five things: signals logged, consents given, CEO conversations, customer complaints and CSM hours. Read every "no" for signs of pressure, and stop the pilot at the first complaint. Keep introductions out of CSM targets and out of business review agendas. The aim is a customer who would say the question was fair and easy to decline.

What CSMs hear can be valuable in its own right: commitments made at handover and how they played out are themselves a kind of record, described in customer success handover records. That page is about the vendor's own records; this checklist is about the customer's.

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 clears all three gates and its CEO wants the conversation, your partnerships owner can register the company for a partner link, confirm the details against who qualifies and check the program terms before submitting.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can a CSM look up how many tickets or records a customer has before raising it?

No. Counts from your product are the customer's data processed for the service, not a prospecting source. Ask the customer to describe its records in its own words, at metadata level, if it wants the conversation.

What if my contact says yes but cannot reach the CEO?

Then the referral waits. Only the CEO can authorize a licensing discussion, and SourceX's screening generally treats an introduction the decision maker has not heard about as a poor fit. Your contact decides whether and when to raise it.

Can I keep working with the customer while SourceX talks to them?

Yes, and nothing about the account should change. Step out of the licensing conversation, keep it out of renewals and business reviews, and leave status questions to the customer and SourceX.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. learn.microsoft.com/en-us/partner-center/referrals/manage-co-sel…
  4. eur-lex.europa.eu/legal-content/EN/TXT

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment