Renewal feels like the obvious moment. The account team finally has senior people from the customer in the room, the relationship is under review anyway, and a new idea looks like added value. That is precisely the problem. At renewal the vendor holds a deadline and a price, and anything it raises arrives with both attached.
Why renewal timing is a pressure question, not a scheduling one
A customer hearing about SourceX from its software vendor at renewal will ask itself, silently, whether its answer affects its price, its service or its standing with the vendor. Nothing the account manager says fully removes that doubt while the contract is unsigned.
European consumer law has a precise name for this risk. The Unfair Commercial Practices Directive defines undue influence as exploiting a position of power to apply pressure, even without force, in a way that significantly limits someone's ability to make an informed decision, and Article 9 puts the timing of a practice first among the factors for judging whether it is aggressive. The Directive protects consumers and does not govern a business-to-business SaaS contract; it is used here as a yardstick, not a legal test. Its logic still fits: whether an ask is pressure depends on when it is made and from what position.
Two program facts remove any reason to hurry:
- Nothing pays early. A lead, meeting or signed agreement alone does not earn a payable reward. The payment deadline counts from the later of two milestones for the complete, validated dataset, the Acquisition Partner's final written acceptance and completed handoff, and neither milestone can occur until the company has signed, prepared and delivered its data.
- Credit does not reward speed into a renewal. The first valid introduction within the 90-day attribution window is credited when the company submits a verified application. Squeezing the topic into the renewal call wins nothing the rules recognize.
And one disclosure rule applies at any moment: FTC staff guidance counts a financial relationship as a material connection, so if your company may receive a referral reward, the customer should hear that from you. The disclosure examples show plain phrasing.
Who benefits, and who can say yes?
The introduction helps a customer only if the customer fits: 50+ full-time employees at peak (contractors excluded), years of documented operating history, the rights to license its own records and a CEO who wants the conversation. For a customer that fits, the benefit is the chance to be paid for licensing records it already owns, under its own agreement with SourceX.
The CEO authorizes a licensing discussion. At renewal, your counterpart is usually procurement, the functional buyer of your product or, in an owner-run company, the CEO who also signs your renewal. That last case is where pressure peaks: the one person who can say yes to SourceX is the same person deciding whether to renew you.
The commercial-pressure timing test
Before anyone mentions SourceX to a customer in a renewal quarter, the account owner answers six questions and writes the answers in the account record.
| Signal | Ask before raising it | Counts as pressure when | Note in the account record |
|---|---|---|---|
| 1. Open commercial terms | Is a quote, discount, redline or budget approval outstanding? | Any of them is unsigned | What is open and its expected close date |
| 2. Same signer | Would the person you would ask also sign or approve your renewal? | Yes | Name and role |
| 3. Vendor-held deadline | Are you within 60 days of the renewal date or notice deadline? | Yes | The date |
| 4. Unresolved service issue | Is an escalation, service-credit claim or churn-risk flag open? | Yes | Ticket or flag reference |
| 5. Shared channel | Would the topic appear in the same deck, thread or meeting as price? | Yes | The planned channel |
| 6. Undisclosed interest | Has the customer been told your company may receive a referral reward? | Not yet | Date of disclosure |
Scoring. Zero signals: raise it as a separate agenda item, with the disclosure. One signal: wait until it clears, then raise it in a short written note the customer can ignore. Two or more: not this cycle; log the earliest clean window. If the customer asks first, answer factually whatever the score, disclose and offer to continue after the renewal closes.
Method note. The six signals come from three sources: the pressure factors in the Directive's definition (position of power, timing), the FTC's material-connection rule, and SourceX's program terms. The 60-day threshold in signal 3 is our design choice, not a measured figure; set it to match your own sales cycle. The test has not been validated against outcomes, and no data on customer reactions to referral timing has been published.
Calmer windows than the renewal call
Each of these windows runs on the customer's clock rather than the vendor's:
- After signature and first value. Thirty to ninety days after the renewal closes, in a check-in with no commercial agenda.
- When the customer asks. A question the customer raises is the cleanest opening there is.
- On the customer's own documented event. A planned system migration, an archive being retired or a retention policy changing. Real urgency belongs to a dated event like this, and the archive retention guide and the migration context guide show what to look for.
- A planning review held apart from pricing. Advisors use the same rule; the client renewal questions keep data questions in planning, not pricing.
Your renewal file is not the customer's permission
A renewal file shows seats, usage and storage growth. It does not show whose records sit in the tenant, whether the customer's own client contracts allow reuse, or whether its CEO is interested. SourceX's screening guidance treats material that belongs to a company's clients as usually not a fit, and an introduction made without the decision maker's knowledge as usually not a fit either.
So the renewal report is not a target list. If a customer wants the conversation, the customer describes its records at metadata level (what kind, roughly how many, how many years, which system) and licenses them directly with SourceX. The vendor never exports, samples or describes the contents of a tenant. When the customer is a portfolio company reviewing its own subscriptions, the view from its side is in the guide to SaaS renewals as data checkpoints.
Four accounts, scored (Illustrative)
Illustrative. Generic accounts and invented facts; no outcomes implied.
| Account | Signals present | Score | Decision |
|---|---|---|---|
| 300-person logistics customer; renewal signed last month; its COO asked about AI data | None; disclosure made in reply to the COO | 0 | Offer an introduction to the CEO through the COO, in a separate meeting |
| 180-person insurance agency group; 45 days to renewal; discount request open | Open terms, same signer, vendor deadline | 3 | Not this cycle; log a window 60 days after signature |
| 520-person manufacturer; renewal eight months away; open priority-one escalation | Unresolved service issue | 1 | Wait until the escalation closes, then send a short written note |
| 35-person design studio; no renewal pending | None | 0 | Do not raise: below 50 full-time employees at peak, so timing is irrelevant |
The last row matters as much as the others. A clean score never overrides fit.
Pilot opt-in timing and protect product trust
For one quarter, take SourceX out of renewal decks and pricing emails entirely, and offer it only in post-renewal check-ins as an opt-in. Track four counts: introductions raised in clean windows, introductions raised with one or more signals present, customer comments that link the topic to price or service, and unsubscribes or complaints. Report them as counts. SourceX has published no benchmark for these numbers. One named person submits for your company, after signing the SourceX Channel Partner Agreement, so introductions never come from several account managers at once.
The stakes explain why the test exists. Illustrative: at a $400,000 Actual Supplier Payout the default reward on a company's first qualifying transaction is USD 70,000, while a $40,000 payout is below the USD 100,000 Minimum Transaction and earns nothing unless SourceX agrees in writing. SourceX pays the reward separately and never takes it from the customer's payout, but a figure that size should never sit beside a renewal price, even in someone's head.
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.
When an account scores zero and the customer wants the conversation, register for a partner link, confirm fit against who qualifies and read the program terms before the introduction goes out. The SaaS data partner overview covers the company's side.