3 Things To Consider In Your Software Referral Agreement

Short answer: a software referral agreement lives or dies on three things: exactly which referrals you pay on, how and when you pay, and whether both your partner and your own sales team can understand it. Get those right and most referral disputes never happen.

While there are many different issues to include in a software or SaaS referral agreement, here are a few practical things to consider:

1) What is In and Out. What types of referrals will you pay on, and what types will you not? Do not forget to exclude transactions already in flight or that do not close within X amount of time. What about extensions of the transaction? Be super clear on all of this, because this is the key part of the agreement and where most disputes arise.

2) Payment and Reporting. Do you want to pay after each transaction, or on a monthly or quarterly basis under a report? Do not forget to address credits and returns, and the fact that you have to be paid first (before you pay them).

3) Simplicity and Plain English. Keep this agreement simple and short. You want both (a) your partner and (b) your internal sales and channel teams to understand it. Any confusion between these two groups on referrals creates a lot of disagreements.

The Clause That Prevents the Fights.

Almost every referral dispute traces back to a fuzzy “qualifying referral” definition. Spell out how a lead is registered, how long the registration lasts, what happens if two partners claim the same lead, and when the fee is actually earned (on signature, on payment, on each renewal). Tie the fee to collected revenue, not booked revenue, so a deal that never pays does not cost you a commission. Write that section as if a partner and your channel manager will both read it under pressure, because they will.

A Few More Traps to Close.

Once the qualifying-referral definition is tight, these are the ones I see bite vendors next:

• The tail. Decide whether the referrer earns on year-one only or on renewals too, and put an end date on it. An open-ended “as long as the customer pays” commission becomes a liability that sits on your books forever.
• Independent contractor status. State clearly that the referrer is not your agent and cannot bind you, quote prices, or make product promises. That keeps a referral from quietly becoming a reseller relationship (and keeps their statements from becoming your warranties).
• Termination and survival. Say what happens to in-flight referrals when the agreement ends. Usually you honor leads already registered for a set window, and nothing after.
• Compliance. A short anti-bribery and no-kickback rep matters when the “referrer” is influencing a buyer, especially in regulated or government-adjacent deals.

A Quick Example.

Here is how the fuzzy-definition problem plays out. A partner introduces you to a prospect in March. The prospect goes quiet, then signs on its own through your website in November. The partner sees the logo as a customer and invoices you for a commission. Who is right? If your agreement defined a registration window (say, a lead is “yours” for 90 days after registration) and tied the fee to a deal closed in that window, the answer is clear and nobody argues. Without that line, you are now in a relationship-damaging fight with a partner you wanted to keep. The whole point of the paperwork is to make that answer obvious before anyone is annoyed.

For the broader frame on how referral, reseller, and OEM channel models differ, and when to use each, see SaaS Reseller and OEM Agreement Models.

I hope this helps.

Disclaimer:

This post is for informational and educational purposes only, and is not legal advice. You should hire an attorney if you need legal advice, which should be provided only after review of all relevant facts and applicable law.