# SaaS data referral partner opportunity: a canvas | SourceX

Canonical: https://refer.sourcex.si/guides/the-partner-opportunity-beyond-selling-another-software-seat
Last updated: 2026-11-05

It is a motion that sells nothing your product does. A SaaS company can introduce a customer's CEO to SourceX, which licenses business records directly from that customer, while the vendor keeps its product relationship and never touches the records inside its platform. The idea only works for customers with 50+ full-time employees at peak, years of their own records and a CEO who wants the conversation. Test it on the customer-value canvas below, then run a small opt-in pilot.

Two things it is not. It is not licensing customer data your platform holds; that data is the customer's, and the customer decides. And it is not your company licensing its own engineering, support and operating history, a separate decision covered in the [SaaS data partner guide](/guides/saas-data-partner).

## How this differs from the partner motions you already run

Most SaaS partner programs exist to sell more product. Microsoft's Partner Center, a familiar example, describes co-selling as any collaborative engagement between Microsoft and its partner ecosystem, from joint demand building and sales planning to lead sharing and marketplace-led commerce, including partner-to-partner deals. Every step aims at a product sale. A data-licensing introduction has no product in it at all.

| Question | Co-sell or resale motion | Data-licensing introduction |
|---|---|---|
| What is sold | Your product or a partner's | Nothing of yours; the customer may license its own records to SourceX |
| Who pays whom | The customer pays for software | SourceX pays the customer for licensed records and pays the partner a reward separately |
| Customer data the vendor touches | Whatever the product processes | None for this purpose |
| Decision asked of the customer | Buy, expand or renew | Whether its CEO wants a separate licensing conversation |
| What success looks like for the vendor | A booked deal | A customer who felt helped, whether or not anything is licensed |

The [referral partner versus reseller comparison](/compare/referral-partner-vs-reseller) and [data referrals versus software affiliate programs](/compare/software-affiliate-programs) cover the structural differences in more depth.

## Find a genuine customer benefit and the person who can say yes

Start from the customer, not the partner target. The benefit is real only when a customer holds years of records it created about its own work (work orders, support histories, project files, quality records) and might want a separate revenue line from them, decided by its own CEO. If the honest benefit is "our partner number goes up", the motion fails the first box of the canvas.

The CEO is the person who can authorize a licensing discussion and sign for the customer. Your usual champion, an administrator or an operations lead, can sponsor the idea internally and describe which systems hold records, but cannot say yes. Check who in your company already speaks to customer CEOs: an executive sponsor, a founder, an account executive on strategic accounts. If nobody does, the motion has no path.

## The customer-value partnership thesis canvas

Fill all eight boxes before anyone writes to a customer. Each box has a question, the evidence you may use, and a stop rule. One stop rule triggered ends the idea or sends it back for redesign.

| Box | Question to answer | Evidence you may use | Stop if |
|---|---|---|---|
| 1. Customer benefit | What does the customer gain that it would not get without your introduction? | Customer conversations, advisory board feedback | The only clear benefit is to your partner target |
| 2. Eligible segment | Which customers have 50+ full-time employees at peak, years of history and records of their own? | CRM firmographics and account notes, never tenant data | You cannot name ten without looking inside customer data |
| 3. Authorizer and sponsor | Who at each customer decides, and who on your side can reach them? | Executive sponsor lists, account plans | Your only contact at most fit customers is an administrator |
| 4. Rights boundary | What does your contract say the customer owns, and what may you do with it? | Your MSA, data processing terms, privacy notice | The motion needs you to mine customer data to pick targets |
| 5. Introduction-only role | Who registers, who signs the partner agreement, who makes the handoff? | Partner team charter | Anyone expects your team to export, prepare or carry records |
| 6. Trust controls | How do customers opt in, decline for good and learn about the reward? | Draft message, opt-out process | Sales wants to use it as a renewal or pricing lever |
| 7. Economics, stated honestly | What does the program pay, on what, and when? | The program terms | The business case depends on projected payouts |
| 8. Pilot measures | What will you count after 90 days? | Opt-ins, CEO conversations, complaints, staff hours | You have no way to hear customer sentiment |

**Box 7 in numbers (Illustrative).** The reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months pay 15%, and the USD 50,000 floor applies once per referred company. SourceX pays it separately and never deducts it from what the customer receives. Nothing is paid for a lead, a meeting or a signature.

| Actual Supplier Payout to the customer (Illustrative) | Partner reward on a first qualifying transaction |
|---|---|
| $40,000 | None: below the USD 100,000 Minimum Transaction unless SourceX agrees in writing |
| $250,000 | $62,500 |
| $800,000 | $120,000 |

These pairs explain the arithmetic only: at $250,000 the USD 50,000 plus 5% leg is the larger, at $800,000 the 15% leg is. SourceX has not published typical payouts or conversion rates, so no pilot business case should multiply them by a customer count.

**Method note.** The canvas is built from SourceX's program terms and fit criteria, Microsoft's description of co-selling and Salesforce's contract definition of Customer Data, all read on 2026-10-26. It tests whether a motion is worth piloting. It does not measure customer interest, record quality or demand, and no results from SourceX partner pilots have been published.

## What the partner team may and may not do with each data layer

A SaaS vendor can see a great deal and own very little of it. Major vendors write that into their contracts: Salesforce's Main Services Agreement defines Customer Data as data submitted by or for the customer to its services, and commits Salesforce to safeguards for its security, confidentiality and integrity. Read your own agreement the same way.

| Layer | Whose it typically is | What the partner team may do | What it must not do |
|---|---|---|---|
| Customer content in your product | The customer's | Nothing for this motion | Browse it, count it or export it to find or pitch prospects |
| Your product analytics and telemetry | Yours, within your contract and privacy terms | Treat it as part of your own company's separate licensing question | Present it as the customer's opportunity |
| Firmographics in your CRM | Yours, subject to your privacy notice | Use headcount band, industry and tenure to build the segment | Infer record volumes from tenant usage |
| Customer contact details | Held by you for the relationship | Contact the customer about the program if your terms and privacy notice allow it | Pass names to anyone without the customer's agreement |

An aggregated data clause in your customer contract does not by itself let you license customer-derived data to third parties; the [aggregated data clause guide](/guides/aggregated-data-clause-saas-agreement) and [whether a SaaS company can license customer data for AI training](/questions/saas-customer-data-ai-training-rights) explain why. The customer's records are licensed by the customer, through its CEO, or not at all.

## Three customers through the canvas (Illustrative)

Generic companies and invented facts; no outcome is implied.

**A. An owner-led customer.** A 230-person commercial grounds-maintenance company, run by its founder as CEO, has used your field-service product for six years and keeps 19 years of work orders and crew schedules across two systems. Your executive sponsor knows the founder from the customer advisory board. Boxes 1 to 4 pass; the sponsor sends one opt-in note and the founder replies that he wants the conversation.

**B. An implementation partner in the middle.** A 480-person regional property manager came to you through an implementation partner whose principal advises its CEO. You do not own that relationship. You agree with the implementation partner who makes the ask and who registers, since a company earns credit for just one partner, the one whose valid introduction came first, and only once the company's verified application follows within the 90-day window.

**C. A no-fit counterexample.** A 90-person bookkeeping firm is a loyal customer, but almost everything it holds is its clients' ledgers and payroll files. SourceX's screening guidance treats material that belongs to clients as usually not a fit. Box 2 fails, and the account team is told why so nobody raises it later.

## Pilot opt-in introductions and protect product trust

Run a pilot before any program. Pick 20 to 30 customers from firmographics that pass box 2. Send one neutral note from the person who holds each CEO relationship, explaining what SourceX does, that the customer decides everything, and that your company receives a reward paid by SourceX which never reduces the customer's payout. Make declining one click and permanent. Keep the topic out of renewals and price talks entirely, and do not tie account-team pay to introductions.

Measure four things at 90 days: opt-ins, CEO conversations, customer complaints and staff hours spent. Stop at the first complaint about pressure or the first request that would put your team near customer records. A customer that already has an application, relationship or earlier introduction with SourceX is a duplicate and is not credited, so ask before you send.

Decide who the partner is before launch. In most SaaS companies the company itself should register, sign the SourceX Channel Partner Agreement and receive any reward; individual employees usually need written employer approval for referral income tied to customers, as set out in [employee referral fees and employer consent](/questions/employee-referral-fee-outside-employer-consent). When a single account manager hears an opening mid-conversation, the steps are in [when a customer success manager spots a potential referral](/guides/when-a-customer-success-manager-spots-a-potential-referral).

## Is the customer a fit?

Before any note goes out, each pilot customer needs the published fit facts: a peak full-time headcount of 50 or more, excluding any contractors, an operating history it can document, rights to license its records and an eligible 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. Questions stay at metadata level: which systems, how many years, roughly how much, who administers them. What only SourceX's review settles: relevance to current programs, contract limits on reuse and what a license would cover. The [software and SaaS industry page](/industries/software-and-saas) lists the records SourceX describes as relevant and unsuitable in the sector.

## 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 canvas clears all eight boxes, [register your company for a partner link](/register), screen the pilot list against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the first opt-in note goes out.

## 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://www.salesforce.com/company/msa.jsp
