# SaaS customer referral outreach permission | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-software-vendor-s-contract-restricts-promotional-outreach
Last updated: 2026-11-04

Read the restriction before you write the email. A note telling customers about SourceX promotes another company's program, and your company may earn a reward from it, so treat it as promotional outreach. If a customer agreement, data processing addendum, privacy notice or a contact's marketing preference limits what you may send or how you may use contact details, that limit governs. Where the documents are silent, send one neutral note through a channel the contact has accepted. Where they restrict, ask counsel first. Where they forbid, send nothing.

None of this limits the customer. A customer that wants to explore licensing its own records can apply to SourceX itself at any time. The check below decides only whether, and how, your company may be the one to mention it. This page is general information, not legal advice; counsel reads your actual clauses.

## Why a note about SourceX counts as promotional outreach

Three features make it promotional rather than a service message: it is about a program your product does not provide, your company may be paid if a customer takes part, and the customer will read it as your suggestion unless told otherwise.

Being business-to-business does not take it out of the rules. The FTC's CAN-SPAM compliance guide says the Act makes no exception for business-to-business email. A commercial message must explain clearly and conspicuously how to opt out, offer a return email address or another easy internet-based way to do it, keep that mechanism working for at least 30 days after sending, and honor each request within 10 business days. Opted-out addresses cannot be sold or transferred, except to a company helping you comply. Customers outside the U.S. may fall under other e-marketing and privacy rules, which the checklist below sends to counsel. The live explainer on [whether CAN-SPAM covers a one-to-one B2B email](/questions/can-spam-b2b-email-rules) goes further on single introductions.

A negotiated customer contract can be stricter than any statute. That is why the documents come first.

## The five documents to pull before anything is drafted

| Document | What to look for | Who usually holds it |
|---|---|---|
| Master agreement and order form | Data use, confidentiality, publicity and communications clauses | Legal or deal desk |
| Data processing addendum | Whether you act as processor, and on whose instructions | Privacy |
| Your privacy notice, as in force when the contact was collected | Marketing use and any promise about sharing contacts with third parties | Privacy or marketing |
| The contact's record in your marketing system | Opted in, product notices only, or opted out | Marketing operations |
| Any reseller or implementation partner agreement | Who holds the customer relationship and any outreach rules | Partnerships |

A customer-specific side letter or security addendum belongs in the pile when one exists. If nobody can find a document, treat the customer as Amber until someone does.

## The contract-and-consent review checklist

Work down the questions in order for each customer, and for each person you would write to. The first Red answer stops the send; an Amber answer changes the route.

| # | Question | Where to look | If yes | If no or silent |
|---|---|---|---|---|
| 1 | Do the documents limit use of contact details to running the service or the account? | Master agreement, order form | Red: no promotional note; counsel decides whether even a one-to-one mention fits | Go to 2 |
| 2 | Is the person a user in the product's directory rather than one of your account contacts? | Data processing addendum, admin records | Red for that person: the directory is customer data, processed on the customer's instructions | Go to 3 |
| 3 | Does confidentiality cover the relationship itself, or its terms? | Confidentiality clause | Amber: tell SourceX nothing about the customer; the customer applies with your link | Go to 4 |
| 4 | Does a publicity clause bar use of the customer's name? | Publicity clause | Amber: keep the customer out of partner reports, stories and lists | Go to 5 |
| 5 | Does your privacy notice promise not to share contacts with third parties? | Privacy notice | Amber: never pass contact details to SourceX; send your link instead | Pass details only with the contact's consent |
| 6 | Has the contact opted out of marketing, or accepted product notices only? | Marketing preferences | Red for that contact | Go to 7 |
| 7 | Must communications go through a named contact or procurement? | Side letter, security addendum | Amber: use that route only | Go to 8 |
| 8 | Did a reseller or implementation partner bring the customer? | Partner agreement | Amber: agree the approach with that partner first | Go to 9 |
| 9 | Would the note use anything learned from the product? | Your draft | Rewrite it: product evidence never selects or personalizes | Go to 10 |
| 10 | Is the recipient the CEO, or someone who will put it to the CEO? | Your account records | Green, if every earlier answer passed | Find the route to the CEO first |

**The three outcomes.**

- **Green.** One neutral, optional note through a channel the contact has accepted, with the reward disclosed and an opt-out. The [optional-resource email](/guides/the-customer-education-email-that-avoids-a-vendor-endorsement-claim) is written for this.
- **Amber.** No bulk send. The person who owns the relationship may raise it with the CEO one-to-one only after counsel confirms the documents allow it, and asks permission before any follow-up or before the customer is named to anyone.
- **Red.** No outreach to that customer or contact. List SourceX on your partner or resources page so any customer can find it, and answer factually if someone asks.

**Method note.** The questions come from the documents a SaaS vendor normally holds, the opt-out duties in the FTC's CAN-SPAM guide, GDPR Article 28(3)(a) and SourceX's program terms, all checked 2026-10-26. The order puts the clauses that most often forbid outreach first, so most customers are sorted in a few questions. The checklist does not interpret any particular contract, does not cover every jurisdiction and does not replace counsel. For what customer contracts usually say about data use, see [customer contract data use restrictions](/guides/customer-contract-data-use-restrictions).

Large partner programs work in the same order. Microsoft's Partner Center documentation, for example, tells co-sell partners to get the customer's consent before giving Microsoft the customer's contact information, because Microsoft can use it to contact the customer directly. The consent comes before the contact leaves your hands, not after.

## Three customers through the checklist (Illustrative)

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

**A. Green: an owner-led customer on standard terms.** A 120-person HVAC services company signed your standard online terms, which are silent on marketing. Its founder-CEO subscribed to your customer newsletter. All ten answers pass. Your partnerships lead sends the neutral note; the CEO applies through the link a week later. Your company told SourceX nothing about the customer beforehand.

**B. Red: a negotiated enterprise agreement.** A 900-person regional insurer negotiated an agreement that limits your use of its contacts to delivering the service and routes all communications through procurement. Question 1 is Red, and question 7 would have been Amber anyway. No email goes out. SourceX appears on your public partner page, and if the insurer's CEO ever asks, the account team answers factually and gives the link. How strong the insurer's records might be makes no difference to this answer.

**C. The counterexample: a willing contact who is not the decision-maker.** An operations director at a 260-person distributor has accepted marketing, the contract is silent, and the director replies that they would like to "test the waters" with SourceX without telling the CEO yet. Questions 1 to 9 pass, but question 10 fails: SourceX's guidance says an introduction kept from the person who decides is usually not a fit. The right reply thanks the director and explains that the CEO authorizes a licensing discussion, so the conversation starts when the CEO wants it.

## Holding a contact is not the customer's consent

Having an email address in your CRM or your product says nothing about permission to promote someone else's program. Three kinds of contact data sit inside a SaaS company, and they are not interchangeable:

| Contact data | Whose record it is | Can it ever receive a SourceX note? |
|---|---|---|
| Account contacts, such as the signer or billing owner | Your own business record, governed by your privacy notice and each person's preferences | Yes, within those preferences and the contract |
| Users in the product directory | Customer data you process for the customer | No |
| People who wrote to support | Collected to resolve their requests | No, unless they are also account contacts who accepted marketing |

The customer's records stay the customer's. Its CEO decides whether to discuss licensing, its counsel reads its own client contracts, SourceX reviews rights and fit, and your company introduces and nothing more. The same line governs how you choose customers in the first place, covered in [keeping a customer referral separate from product usage analytics](/guides/how-to-keep-a-customer-referral-separate-from-product-usage-analytics). Customers already ask what vendors do with their records, as SourceX's main-site guide to [SaaS vendor AI training terms](https://sourcex.si/insights/is-your-software-vendor-training-ai-on-your-business-records) shows; a note that hints at product data invites the same scrutiny of your company.

## Pilot on contacts who already accepted marketing

Start with Green customers only, and keep a dated record for each: documents read, answers, reviewer and outcome. The [consent record guide](/resources/how-to-document-client-consent-for-a-referral) shows a format.

1. Send the note once, to Green contacts, with a working opt-out.
2. Honor every opt-out within 10 business days, and keep those addresses out of every later list.
3. Pause the whole program if any reply cites a contract term or privacy promise, until counsel reviews.
4. After 60 days, count notes sent, opt-outs, complaints, CEO replies and verified applications, and compare Green results with any Amber one-to-one asks.

SourceX has not published response or complaint rates for vendor outreach, so these counts are yours alone, with no benchmark yet.

## What the program needs from your side

The SourceX Channel Partner Agreement is signed before your company submits any introduction; one signed under its earlier title, the Channel Partner Non-Circumvention and Non-Disclosure Agreement, remains in force. Clearing the contract is not enough on its own: the customer must have reached 50 or more full-time employees at peak, with contractors left out of the count, and must also show a documented operating history, hold the rights to license and have an authorized contact, the CEO. 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.

The first valid introduction within the 90-day attribution window is credited when the customer submits a verified application, and only one partner is credited per company, which is why question 8 matters. SourceX may contact a referred company directly without affecting valid attribution. Where a customer wants a warm handoff instead of a link, a [double opt-in introduction](/questions/double-opt-in-introduction) keeps both sides informed.

## 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 a customer comes out Green, or its CEO asks you directly, [register for a partner link](/register), check the customer against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the note goes out.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
- https://eur-lex.europa.eu/eli/reg/2016/679/art_28/oj
- https://learn.microsoft.com/en-us/partner-center/referrals/manage-co-sell-opportunities
