Keep usage analytics out of your customer referrals: a 12-signal evidence map for SaaS partnership teams

Short answer

Choose which customers hear about SourceX from evidence the customer gives you or the public record shows, never from what your product observes. Usage events, record counts in a tenant, feature adoption and support-ticket content were collected to run the service. Using them to rank customers for another company's program can step outside the purposes your contracts and privacy commitments set, and it tells customers you watch their accounts. Send one neutral invitation to a whole segment, let interested CEOs opt in, and confirm fit with them directly.

Visual briefFull-size diagram
A split diagram: usage, tenant records, ticket content and health scores stay on the product side behind a no-crossing wall, while public facts, a customer raising the topic and a customer opting in may select a customer, leading to the CEO opting in, the customer applying and SourceX reviewing.
The selection boundary described on this page. Verdicts follow the evidence map; no real customers.

Your company's role is introduction only. If a customer's CEO wants the conversation, the customer applies itself and SourceX reviews whether the customer's own operating records qualify. Product data, tenant exports and account lists never travel with the introduction, and nothing about the customer's subscription changes, whatever it decides.

Why product analytics is the wrong tool for choosing whom to invite

Product analytics answers how a customer uses your software. A referral needs to know something else: whether the customer owns years of its own records, reached 50 or more full-time employees at peak and has a CEO who wants to talk. The first cannot answer the second, and trying creates three problems.

Purpose. Telemetry and tenant content were gathered to deliver and support the service. Where they contain personal data and you act as a processor under the GDPR, Article 28(3)(a) allows you to process that data only on the customer's documented instructions, and ranking customers for a referral is not an instruction any customer gave. Outside the GDPR, the customer agreement and your published privacy commitments draw the same kind of line. FTC staff wrote in January 2024 that model-as-a-service companies must keep their privacy and confidentiality commitments to customers wherever those commitments were made, including terms of service and marketing materials, and that a material omission can draw the same enforcement as a misrepresentation. That post addressed AI model providers; the lesson for any SaaS vendor is to read its own commitments before reusing customer data for something new.

Trust. A customer who receives "we noticed you store 60,000 project records with us" learns that its vendor mines its account for commercial leads. That cost lands on the product relationship, not on SourceX.

Validity. Seats are not full-time employees: they often include contractors and temporary staff, and the program counts only full-time employees at peak. Heavy use of your product says nothing about whether the customer has the rights to license what it holds. The fit facts can only come from the customer.

Where the real customer benefit sits, and who should sponsor it

The benefit belongs to the customer: the chance to license its own operating records, such as SOPs, project histories, QA records and support workflows, directly to SourceX and be paid for them. Your benefit is a referral reward, and the customer should hear about it from you.

A useful test before any outreach: would you still tell this customer if you earned nothing? If the honest answer depends on the reward, the selection is about you, not the customer.

Two sponsors matter. Inside your company, a partnerships or customer marketing lead owns the program, with privacy or legal review of the selection rules and the message; customer success managers can pass on interest a customer volunteers but do not choose targets. Inside the customer, the CEO authorizes a licensing discussion and signs for the company. An operations lead may know the records best, but the conversation goes ahead only when the CEO wants it. SourceX's own screening guidance adds that a customer introduced without the decision maker knowing is usually not a fit.

The customer-selection evidence map

Each signal gets one of three verdicts. Select: the signal may decide that a specific customer is introduced. Segment: the signal may decide who receives a general, identical notice, never who is singled out. Never: the signal stays on the product side.

#SignalWhere it comes fromVerdictWhyUse instead
1Logins, active users, session lengthProduct telemetryNeverCollected to run and improve the service; predicts no fit factNothing; leave it out of selection
2Record or object counts in the customer's tenantCustomer data you hostNeverThe customer's data, held for the customerAsk the customer which records it keeps across all its systems
3Content of tickets, files or messages in the tenantCustomer data you hostNeverReading it for leads defeats the reason you hold itNothing; never open it for this purpose
4Feature or module adoptionProduct telemetryNeverShows how the tool is used, not what the company ownsThe customer's own description of its operations
5Health score or churn riskDerived analyticsNeverMixes retention with an outside offer and invites pressureKeep retention and referral conversations apart
6Support tickets the customer filed with youYour support systemNeverFiled for help, not offers, and often holds customer dataResolve the ticket; raise nothing
7Plan tier, seat count or contract valueYour billing recordsSegmentYour own commercial record, but seats include contractors and value measures your revenueDecide only which segment receives the general notice
8Billing country and data languageYour billing recordsSegmentAvoids sending a notice where the program cannot applyConfirm location and language with the customer
9Advisory board or community membershipThe customer's choice to engageSegmentThe customer joined a forum for broader discussionInvite the whole group to an education session
10Public headcount range and founding yearCompany website, filings, public profilesSelect, as a hintPublic, and close to two fit factsConfirm full-time headcount at peak with the CEO
11The customer raised data licensing itselfA conversation the customer startedSelectVolunteered for this purposeAsk permission before passing anything on
12The customer replied to the general noticeThe customer's own actionSelectThe strongest signal: an opt-inSend the SourceX link so the customer applies itself

How the verdicts were set. Each signal went through three questions, in order. Was it collected to deliver the service to this customer? If yes, the verdict is Never. Did the customer give it for this purpose, or is it public, and does it bear on a published fit fact? If yes, Select. Is it your own commercial record that bears on no fit fact? Then Segment. The questions apply the purpose line above and the fit facts in SourceX's program terms and who-qualifies page (checked 2026-10-26). They do not settle what your own contracts say: counsel reads those, and the contract-and-consent checklist covers outreach permissions.

Three customers through the map (Illustrative)

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

A. An owner-led customer that raised it. At a quarterly review, the founder-CEO of a 180-person engineering consultancy asks your account executive whether anyone pays for old project files. That is signal 11. The account executive says your company does not handle licensing, discloses that it may receive a referral reward from SourceX, and asks whether the CEO wants the link. The CEO says yes and applies. Nothing from your product enters the conversation.

B. The account the analytics would have picked. A 600-seat logistics customer has the largest tenant you host and the heaviest usage, and a customer success manager wants to pitch it. The map says no: record volume is signal 2 and seat count is signal 7, and many of those seats belong to drivers on contract. The customer sits in the segment that receives the same general notice as everyone else. If its CEO replies, the conversation starts there; if not, nobody follows up.

C. The enthusiastic no-fit. A 30-person design agency replies to the general notice within an hour. Two facts stop it: the program terms require 50 or more full-time employees at peak for an introduced company, and much of an agency's work product belongs to its clients, which SourceX's guidance lists as usually not a fit. Your reply says so plainly, points the CEO to who qualifies, and changes nothing about the account.

Hosting the records does not give you rights to them

Your access exists because the customer bought a service. It does not make you an owner of the customer's records, a party to its licensing decision or a channel for its data. In most business SaaS agreements the customer keeps ownership of what it puts into the tool, though the contract decides; who owns data in SaaS walks through the clauses.

QuestionThe vendorThe customer
Who decides whether to discuss licensingNobody at the vendorThe CEO
Whose records could be licensedNone of the vendor's, through this programThe customer's own operating records, subject to its contracts
Who exports or delivers anythingThe vendor does not act for SourceXThe customer, from its own systems, if a license is agreed
Who reviews rights and fitSourceX, in its reviewThe customer and its counsel, with SourceX
What the vendor may tell SourceX about the customerNothing without the customer's permissionWhatever the customer chooses to share

Owning records is still not the same as being free to license them. The customer's client contracts, employee privacy obligations and confidentiality terms decide that, and the guide on telling company data from customer-owned data helps a customer sort its material. If your team is really asking whether your own aggregated product telemetry could be licensed, that is a different decision in which your company would be the supplier; SourceX's main site covers it in is product analytics valuable for AI training.

Start with one segment and a 60-day review

Run one segment first, with the rules written down before the first send.

  1. Pick the segment with Segment signals only, such as plan tier and billing country.
  2. Send one identical notice to everyone in it. The neutral optional-resource email is built for this.
  3. Introduce only customers who select themselves through signals 11 or 12, and record that signal against each introduction.
  4. Wall off the data. The people running the program get no new access to analytics or tenant data.
  5. Review after 60 days. Count notices sent, opt-outs, complaints, replies, CEO conversations and verified applications. Any introduction whose first evidence was a Never signal is a process failure, whatever its outcome.

SourceX has not published response or conversion figures for SaaS customer cohorts, so there is no benchmark yet; the pilot measures your own rates.

What stays open until SourceX reviews

Before review, you and the customer can settle the fit facts together: whether it had 50+ full-time employees at peak, not counting contractors; whether its operating history is documented; whether it holds rights to license; and that its authorized contact is the CEO. Location matters as well. 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 is whether the customer's records match SourceX's current data needs, which SourceX checks in review, and what any license would cover.

Your company signs the SourceX Channel Partner Agreement before submitting introductions; if the copy on file still carries the agreement's old heading, Channel Partner Non-Circumvention and Non-Disclosure Agreement, it remains in force. Whichever valid introduction came first in the 90-day attribution window is the one credited, once the customer submits a verified application, and only a single partner per company receives that credit. For the wider program, see the SaaS data partner guide and the software and SaaS industry page.

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 through a general notice or raised licensing itself, register for a partner link, check the customer against who qualifies and read the program terms before you send it anything.

  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 we use usage data only to exclude customers who would not fit?

Exclusion is still selection. Use only segment signals, such as plan tier or billing country, to decide who receives the general notice, and confirm fit with the customer itself. Telemetry stays out of both inclusion and exclusion.

What if a customer success manager hears interest during a support call?

That is a volunteered signal. The manager can say the company takes part in a partner program, ask whether the customer wants the link and pass on nothing else. The call notes and any ticket content stay on the product side.

Should we tell customers that we may earn a reward?

Yes, in the notice and in any one-to-one conversation. SourceX pays the reward separately; by default it is the greater of $50,000 plus 5% and 15% of what SourceX actually pays the customer, with no cap, and it never reduces the customer's payout.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. eur-lex.europa.eu/eli/reg/2016/679/art_28/oj
  4. ftc.gov/policy/advocacy-research/tech-at-ftc/2024/01…

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