# Customer success referral incentives: a trust review

Canonical: https://refer.sourcex.si/guides/how-to-avoid-reward-driven-pressure-on-customer-success-teams
Last updated: 2026-11-05

Do not pay customer success managers per introduction, set quotas or run time-limited contests for SourceX referrals. When the SaaS company is the registered partner, any reward reaches it well after the introduction, only once the customer's own licensing deal has closed and been paid, so a bonus at introduction time pays for something the program never rewards. Recognize good judgment instead, disclose the reward to every customer, and run any proposed incentive through a six-question customer trust review before launch.

A customer success manager is the worst-placed person in a software company to carry a sales incentive for a third party's program. The CSM sits in the renewal path, answers the escalations and is the face of the product. A customer who feels nudged by that person cannot easily separate the nudge from the service it depends on.

## Where incentive pressure comes from in a customer success seat

The pressure does not need bad intent. It comes from three facts about the seat: the customer depends on the CSM, the CSM controls attention and goodwill the customer values, and an incentive gives the CSM a personal stake in the customer's answer. Put those together and even a careful person starts timing the question to moments when the customer is least able to say no.

Regulators have seen what product-specific incentives do to customer-facing staff, in industries far stricter than software. In September 2016 the Consumer Financial Protection Bureau fined Wells Fargo $100 million, saying sales targets and compensation incentives had led employees to open deposit and credit card accounts without customers' knowledge or consent. When the SEC wrote Regulation Best Interest for broker-dealers, it required firms to identify and eliminate sales contests, sales quotas, bonuses and non-cash compensation based on the sales of specific securities or specific types of securities within a limited period of time.

Neither the rule nor the enforcement action applies to a SaaS company introducing customers to SourceX. Both describe the same mechanism, and the design lesson is portable: product-specific, volume-based, time-boxed incentives for people who serve customers are where pressure starts.

## Is the partner the company or the person?

Settle this before any incentive discussion. Under the program terms, a partner holds an approved partner account and signs the SourceX Channel Partner Agreement before submitting introductions, and the reward goes to that partner. If the SaaS company registers, the company receives any reward, and paying any of it to staff is an internal compensation decision.

If an individual CSM registers personally to introduce the employer's customers, the employer's customer relationships are being turned into a personal side income. That needs the employer's written agreement at the very least; the live note on [employee referral fees and employer consent](/questions/employee-referral-fee-outside-employer-consent) covers how to raise it. For most SaaS companies the clean answer is that the company is the partner and no individual registers.

The customer side does not change with that choice. The introduction has to offer the customer something real: a conversation about licensing its own records directly to SourceX, which pays the customer under its own agreement. The fit baseline is roughly 50 or more full-time employees at peak, several years in operation, records the customer created and rights to license them. The customer's CEO is the person who can authorize a licensing discussion, and an introduction made behind that decision maker's back is, by SourceX's own screening, usually not a fit. No incentive should ever reward reaching anyone else.

## The customer trust incentive review

Six questions. Any proposed incentive for customer-facing staff must pass all six before launch, and the answers go to whoever owns customer trust in the company, not only the partnerships team.

| Question | Passing answer | Why it matters |
|---|---|---|
| 1. Does anyone's pay depend on how many introductions they make? | No | Volume is the one thing the program never pays for |
| 2. Is there a quota, target, leaderboard or deadline? | No | Targets and deadlines are the pattern Regulation Best Interest removes |
| 3. Could a customer who says no be treated differently in support, pricing or renewal? | No, and the policy says so in writing | A no has to cost the customer nothing |
| 4. Is the customer told in the first message that the company may be rewarded? | Yes | The customer would not expect it, so it is a connection to disclose |
| 5. Does any payment to staff happen before SourceX pays the reward? | No | Before supplier payment, any reward shown is only an estimate |
| 6. Can anyone earn without the partnerships owner checking the customer contract and the CEO's consent? | No | Outreach limits and the CEO's knowledge come before any introduction |

Question 4 rests on a general rule rather than a SourceX one. The FTC's Endorsement Guides require a connection that might materially affect the weight of an endorsement, including the possibility of being paid, to be disclosed clearly and conspicuously when the audience would not expect it. A customer hearing about SourceX from its software vendor would not expect a reward. The [guide to discussing rewards transparently](/guides/how-to-discuss-referral-rewards-transparently-with-a-business-contact) has wording.

Six common designs, scored against the review:

| Design | Pays for | Fails questions | Verdict |
|---|---|---|---|
| No individual incentive; the partnerships owner runs the program | Nothing individual | None | Default |
| Recognition for well-documented handoffs, including ones that ended in a no | Judgment and process | None | Recommended |
| A team-level share of rewards SourceX has actually paid, unrelated to who introduced whom | Paid outcomes, spread across the team | None, if disclosed and paid only after SourceX pays | Acceptable |
| A flat bonus per introduction | Volume | 1, 5 | Rejected |
| A quarterly quota or target | Volume against a deadline | 1, 2 | Rejected |
| A time-limited contest or leaderboard | Volume against a deadline, publicly ranked | 1, 2, 5 | Rejected |

**Method note.** The review and the scoring were built on 2026-10-26 from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and screening page, Regulation Best Interest, the CFPB's 2016 Wells Fargo action and the FTC Endorsement Guides. The six questions and verdicts are our design. They have not been tested on customer success teams, and SourceX has not published data on how incentives affect introduction quality or customer trust; the trial below is how a company would collect its own.

## Product dashboards and bonuses do not mix

A CSM can see usage data, admin settings and support history that the customer never offered for this purpose. An incentive, however small, turns that view into a prospecting tool: which accounts have the most history, which have the most users, which just renewed. The records in that product belong to the customer, and the customer decides whether anyone discusses licensing them.

So the review has an unwritten seventh rule that the incentive must never touch: introductions start from something a customer said to a person, never from what the product shows. A customer's COO mentioning fourteen years of dispatch records on a call is a signal. A usage report showing fourteen years of dispatch records is not. The live guide on [customer success handover records](/guides/customer-success-handover-ai-data) shows how rich those records can be, which is exactly why the customer, not the vendor, decides what happens to them.

## Following one reward through the SaaS company's books (Illustrative)

Illustrative. A generic customer, invented figures, no outcome implied; not a forecast or a quote.

| Event | What the SaaS company actually knows | What a bonus paid at this point would rest on |
|---|---|---|
| A CSM hears the customer's COO mention years of dispatch records | Nothing about fit or interest | A remark |
| The customer's CEO agrees, and the customer applies through the company's partner link | An application exists; credit is decided by SourceX from dated records | An application, which earns nothing by itself under the terms |
| The customer's licensing terms propose a supplier payout of $400,000 | An estimate of USD 70,000 under the default rule | An estimate that can still change |
| The Acquisition Partner gives final written acceptance and the dataset handoff completes | The payment deadline starts: 60 calendar days after the later of the two | Conditions still open: cleared payment to SourceX, the customer's own payment, finance approval |
| SourceX pays the customer and the payment conditions are met | The reward becomes payable | The first point at which any staff payment makes sense |
| The supplier payout is later reduced to $320,000, so the reward is recalculated to USD 66,000 | The reward follows the reduced total down, so the USD 4,000 already paid above it is adjusted | A staff bonus already paid on the larger figure |

The arithmetic follows the default rule for a company's first qualifying transaction, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. At $400,000 that is USD 50,000 plus 5%, USD 70,000, which is more than 15% of the payout. If that payout later falls to $320,000, the reward becomes USD 66,000 and the USD 4,000 already paid above it is adjusted. A buyer refund alone, without a reduction in what the customer was paid, would change nothing. An incentive designed around the last two rows cannot pay anyone for a deal that never closed.

## A two-quarter trial with customer feedback built in

Run the program first as an opt-in for staff as well as customers. No CSM is required to raise SourceX, and a CSM who never does is not marked down.

1. **Choose a small group.** Three to five CSMs who volunteer, each with accounts that look like a plausible fit on the published baseline.
2. **Route everything through one owner.** The CSM passes a metadata-only note to the partnerships owner, who checks the customer contract for outreach limits and confirms the CEO wants the conversation before anything is sent.
3. **Disclose every time.** The first message to the CEO says the company may receive a reward, paid by SourceX and never deducted from the customer's payment.
4. **Ask the customer one question.** After the conversation, the partnerships owner asks the CEO whether raising it felt like an option or like a request from a supplier they rely on.
5. **Count the right things.** CEOs who said yes, CEOs who said no, complaints, support tickets or renewal notes that mention the topic, and hours spent. Leave rewards out of the count until any are actually paid.
6. **Stop on the first complaint about pressure,** fix the step that caused it, and resume only after the review is rerun.

At the end of two quarters, compare customer feedback from accounts that were asked with those that were not. If asked customers report more friction in support or renewal conversations, the program design, not the CSM, needs to change. The [SaaS data partner overview](/guides/saas-data-partner) and the [guides library](/guides) cover the rest of the program; MSPs facing the same question can read the [vendor referral fee disclosure note](/questions/msp-vendor-referral-fees-disclosure).

## 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 the incentive review passes and one owner holds the program, the company should [register for a partner link](/register) in its own name, check each opt-in customer against [who qualifies](/who-qualifies) and read the [program terms](/terms) with the customer success leadership before the first message goes out.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.ecfr.gov/current/title-17/chapter-II/part-240/subject-group-ECFR64f52d737aea1ed/section-240.15l-1
- https://www.consumerfinance.gov/archive/newsroom/consumer-financial-protection-bureau-fines-wells-fargo-100-million-widespread-illegal-practice-secretly-opening-unauthorized-accounts/
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
