# SaaS customer introductions to SourceX, by consent | SourceX

Canonical: https://refer.sourcex.si/guides/how-a-software-company-can-introduce-customers-to-sourcex
Last updated: 2026-11-05

A software company introduces customers to SourceX the way it would recommend any outside service: it tells customers the option exists and introduces only those whose CEO opts in. It never scans, exports or describes the records it hosts for them, because those records are the customer's and the vendor handles them on the customer's instructions. The customer decides, applies, licenses and is paid by SourceX; the vendor's part ends at the introduction.

The decision for a partnerships director is whether an opt-in program suits your customer relationships, and how to run one so that nobody on your product or support teams ever looks at customer data to make it work.

## What a vendor may use, and what it may not

Three things sit close together inside a software company and have to stay apart: what customers store in your product, what your product analytics record about their usage, and the introduction itself.

| Layer | Whose it is | Its role in an introduction | Off limits |
|---|---|---|---|
| Customer records stored in your product | The customer's, under your contract | None. They are why a customer may be interested, not something you assess | Querying, sampling or summarizing them to pick candidates |
| Product analytics about usage | Governed by your contract and privacy notice | None for choosing whom to approach | Using usage telemetry to judge whose records run deep |
| Commercial account facts in your CRM | Yours, as the seller | Enough for a fit pre-check: company size, region, years as a customer | Sharing them with anyone without the customer's consent |
| The introduction | A courtesy to the customer's CEO | The vendor's whole role | Any involvement once the CEO is talking to SourceX |

The legal anchor is plain in the EU and usually mirrored in contracts elsewhere. Under Article 28 of the GDPR, a processor's contract must require it to process personal data only on the controller's documented instructions, and a processor that decides the purposes and means of processing for itself is treated as a controller for that processing. Combing hosted customer data for licensing candidates is a purpose no customer instructed. The guide to [who owns data in SaaS](/questions/who-owns-data-in-saas) explains the usual contract clauses.

Your own records are a separate matter. A software company's own engineering, support and operating history may itself be worth a licensing conversation, through its own CEO; see [whether a SaaS company can license data](/questions/saas-customer-data-ai-training-rights) and the [SaaS data partner page](/guides/saas-data-partner). Keep that conversation out of the customer program.

## Which customers, and who can say yes

The benefit to the customer is concrete: a way to license records it already owns, with SourceX as counterparty, paid under its own agreement. The customers most likely to fit share traits you can see in commercial facts alone.

- **The fit facts.** A customer whose full-time headcount peaked at 50+ (contractors don't count), whose operating history is documented, which holds the rights to license its records and which operates from a location the geography rule accepts. 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.
- **Records the customer created.** A field-service contractor's work orders, written by its own technicians, are its own. An agency's creative files often belong to its clients, and client-owned material is usually not a fit; [company data versus data owned by its customers](/guides/how-to-distinguish-company-data-from-data-owned-by-its-customers) shows how to tell them apart.
- **A CEO who can say yes.** Your customer success manager probably knows an operations director or a system administrator. That person can pass a message along. The CEO authorizes a licensing discussion.

## The customer-consented introduction flow

Seven steps, each with a gate that must be passed before the next one starts.

| Step | Who acts | Gate | What stays on file |
|---|---|---|---|
| 1. Prepare | Partnerships and legal | Partner registration, the signed SourceX Channel Partner Agreement, and a check that customer contracts allow the message | The signed agreement and legal's note |
| 2. Announce | Partnerships | One neutral, opt-in message to every eligible account, saying that you may earn a referral reward | The message and the criteria for the send list |
| 3. Opt in | The customer | The reply comes from the CEO, or with the CEO's knowledge | The reply |
| 4. Pre-check | Partnerships | Commercial facts pass the fit facts; the records are the customer's own | A one-line note with no customer data in it |
| 5. Introduce | Partnerships and the CEO | A short CEO-to-SourceX email with your partner link; the company applies itself | The introduction email |
| 6. Step back | Everyone at the vendor | No data work for the referral | Nothing new |
| 7. Reward | SourceX | The payment conditions in the terms | SourceX's statement |

**Step 2, disclosure.** The FTC's Endorsement Guides FAQ says a connection that could change how much weight people give a recommendation, such as payment, should be disclosed clearly, and that people who earn commissions should say so. A vendor recommending SourceX while able to earn a reward says that in the message itself.

**Step 3, consent.** An introduction the customer's CEO has not heard about is, under SourceX's screening guidance, usually not a fit. Large partner programs build the same gate into their tooling: Microsoft's Partner Center requires a partner who wants to run an engagement with a customer to ask for that customer's consent, its agreement to participate, within a set number of days. Consent comes before the engagement, not after.

**Step 6, exports.** If the customer later asks to export its own records from your product, handle the request exactly as you would for any customer archiving or leaving: under your contract, through your normal process, at the customer's instruction. It is not part of the referral, and nobody at the vendor reviews what is exported.

**Step 7, the reward.** SourceX pays the vendor separately, and the reward is never deducted from the customer's compensation. Before it is payable, the customer's dataset must be fully handed off and the Acquisition Partner must give final written acceptance of the complete, validated dataset; the Acquisition Partner must pay SourceX in cleared funds; the customer's compensation must be paid; SourceX finance must approve; and your tax and payment details must be on file. The deadline is 60 calendar days after the later of that acceptance and the handoff. Illustrative figures for a company's first qualifying transaction, not forecasts:

| Illustrative Actual Supplier Payout to the customer | Reward SourceX pays the vendor |
|---|---|
| $40,000 | None: below the USD 100,000 Minimum Transaction, unless SourceX agrees in writing |
| $250,000 | $62,500 |
| $800,000 | $120,000 (15% exceeds USD 50,000 plus 5%) |

## What hosting a customer's records does and does not tell you

Hosting a customer's records gives you technical reach, and technical reach answers none of the questions that matter.

| What you can see as the vendor | What it tells you | What it does not tell you |
|---|---|---|
| Admin access to the customer's tenant | That you could technically read the records | That you may, or that the customer can license them |
| Years the account has been active | Roughly how far back records could go | Whether they were kept, purged or migrated in |
| Seat count | A rough floor on users | Full-time headcount at peak, contractors excluded |
| Your aggregated-data clause | What you may do with aggregated data | Anything about the customer licensing its own records |

The trap is how easy the forbidden question is. An engineer could answer "how many tickets does this customer have?" in a minute. Do not ask it. The number comes from the customer, if the customer chooses to share it, and SourceX's review does the rest. The guide to [aggregated data clauses](/guides/aggregated-data-clause-saas-agreement) explains why that clause is a separate question entirely.

## Three customers through the flow (Illustrative)

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

**A. An owner-led company.** A 260-person founder-owned property maintenance contractor has used the vendor's field-service software for nine years. Its founder-CEO replies to the opt-in announcement. The commercial facts pass the pre-check, and its work orders are written by its own technicians. The partnerships director sends a short introduction to SourceX with the partner link, copies the CEO, and steps out.

**B. A network intermediary.** A 400-person logistics customer came in through an implementation partner, who still runs its quarterly reviews and owns the CEO relationship. Before anyone raises it, the vendor and the implementer agree in writing which of them submits the introduction, because SourceX credits one partner per company. The implementer asks; the vendor stays out of the conversation. [Software implementation partners](/for/software-implementation-partners) have their own guide.

**C. A no-fit counterexample.** An operations manager at a 35-person customer replies with enthusiasm and offers to "send over an export." Two problems: full-time headcount has never reached 50, and the CEO has not heard of the idea. The director thanks him, declines the export and closes the row. At a larger company the reply would still wait until the CEO knew.

## Pilot it before announcing it widely

Run one small, opt-in pilot before any broad announcement, and decide in advance what would make you stop.

- **Scope.** One segment, such as accounts in one region that have been customers for five years or more.
- **Message.** One version, reviewed by legal and customer success, with the reward disclosure.
- **Length.** 60 days.
- **Measures.** Opt-ins; opt-ins confirmed by the CEO; opt-ins passing the fit facts; introductions submitted; unsubscribes; support tickets or complaints that mention the message.
- **Stop rules.** Pause and rewrite if any customer suggests you looked at its data. Stop and retrain if anyone on staff used tenant data to choose a target.

SourceX has not published opt-in or conversion figures for vendor programs; the pilot is how you get your own. If a product retirement is on your roadmap, keep the retirement notice and any licensing mention in separate messages; the main site's guide on [notice before a product is retired](https://sourcex.si/insights/how-much-notice-should-customers-get-before-a-software-product-is-retired) covers the notice itself.

| Write this | Not this |
|---|---|
| "Your records stay yours. We have not looked at them and will not." | "We noticed your data could be valuable." |
| "Reply only if your CEO would want a conversation." | "Reply to claim your payout." |
| "We may earn a referral reward from SourceX. It does not reduce what you would be paid." | Silence about the reward |
| "SourceX decides fit in its own review." | "You qualify." |

How this differs from reselling software is set out in [company data referrals versus software affiliate programs](/compare/software-affiliate-programs), and the wording for asking an owner directly is in [asking for permission to make an introduction](/guides/how-to-ask-a-business-owner-for-permission-to-make-an-introduction).

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

If your customer base includes established companies whose CEOs would welcome the option, [register for a partner link](/register), check the segment against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the first announcement goes out. More playbooks sit in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32016R0679
- https://learn.microsoft.com/en-us/partner-center/incentives/mci-engagements-customers
- https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking
