This email is part of the annual license true-up guide for SaaS spend consultants. Send it only after the owner has answered the question "Will the proposed cancellation delete unique decision histories?" and said they want to hear about a licensing review. The true-up archive context checklist records those answers.
The draft email
Fill the braces from the owner's answers and the vendor's own documentation. Keep it under 200 words.
Subject: {app} history before the {month} true-up order
Hi {first_name},
When we reviewed the cancel list, {system_owner} confirmed that {app} holds {decision_type} from {first_year} to {last_year}, and that no other system has a copy. Under {vendor}'s published policy, data is deleted {retention_period} after the subscription ends. You said you want to decide what happens to that history before the order goes in.
One option, alongside a straightforward export: SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation, delivery and payout. Nothing is shared unless {company} agrees terms. I should be clear: I am a SourceX referral partner, and SourceX may pay me a reward if a qualifying license completes. It is funded separately, does not reduce what {company} would receive, and has nothing to do with my true-up work or fees.
Would you like an introduction? SourceX would start with a description only: the app, the years, rough volumes and who can approve a discussion. A one-word reply is fine.
{your_name}
Line-by-line annotation
| Line | Why it is there | What never goes in it |
|---|---|---|
| Subject line | Names the app and the order, the two facts the owner will search for | "Opportunity", "revenue", a figure or the word "urgent" |
| "{system_owner} confirmed that {app} holds..." | Credits the facts to the person who gave them, at metadata level | Record counts you pulled yourself, client names or screenshots |
| "{decision_type} from {first_year} to {last_year}" | States what kind of history is at stake and how deep it goes | Judgments about what the history is worth |
| "No other system has a copy" | This is the test that made the app worth raising | Assumptions; if the owner was not sure, write "may not have a copy" |
| "Under {vendor}'s published policy..." | Ties the timing to a documented retention rule, which is real urgency | A period you have not read in the vendor's documentation |
| "You said you want to decide..." | Restates the owner's own words, so the choice stays theirs | Any claim that the owner already agreed to a licensing review |
| "One option, alongside a straightforward export" | Makes clear an export is a perfectly good outcome | Wording that frames licensing as the only sensible path |
| "SourceX licenses approved business data..." | One accurate description of what SourceX does | Buyer names, AI labs or claims of demand |
| Disclosure sentences | Puts your interest in plain view before any introduction | Hedged wording such as "there may be a finder's fee" |
| "Nothing to do with my true-up work or fees" | Separates the referral from the paid engagement | License savings, your fee or any link between them |
| "A description only" | Sets the metadata-only boundary in writing | Requests for exports, samples or admin access |
| "A one-word reply is fine" | Makes declining as easy as accepting | Reminders, "last chance" lines or follow-up pressure |
The retention sentence must come from the vendor. Atlassian, for example, documents that data for deactivated cloud apps is kept for 60 days after the end of the subscription period on Free, Standard or Premium plans, 15 days for trials, and then permanently deleted (Atlassian). The order date also comes from the agreement: under a Microsoft Enterprise Agreement, the true-up order must reach Microsoft between 60 and 30 days before the anniversary (Microsoft). Quote neither unless it applies to this app.
The disclosure sits in the body because the FTC's Endorsement Guides call for clear and conspicuous disclosure of a connection, including the chance of payment, that the audience would not expect and that could affect how much weight they give the recommendation (eCFR). Whether the guides cover a private email is for your own advisers; plain wording removes doubt.
What to leave out of a true-up introduction
- The savings case. Seat counts, license costs and your fee stay in the true-up report.
- Records. No exports, sample tickets, change requests or screenshots, even if the system owner offers them.
- People. Describe record types, not the employees or clients who appear in them.
- Reward figures as a promise. If the owner asks, the terms are the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, payable only after the conditions in the program terms are met. Linking the rewards page is usually better than quoting.
- SourceX on copy. Wait for a yes.
Variations by answer
| What the owner told you | Change to the draft |
|---|---|
| Not sure whether a copy exists | Replace "no other system has a copy" with "it is not yet clear whether another system has a copy" |
| The retention rule is undocumented | Delete the retention sentence and add: "{system_owner} is confirming what happens to the data after the end date." |
| Several apps, one owner | List each app with its decision type and years on its own line in paragraph one |
| The owner wants counsel involved | Add: "Happy to include {counsel_name} on the introduction." |
| The order has already been placed | Change the subject to "{app} history before the subscription ends" and keep the retention sentence |
The introduction email builder produces variants, and the wealth advisor introduction email shows the same structure for a different relationship. If you are unsure whether to raise licensing at all, read when to raise data licensing with a client; if the true-up falls inside a yearly planning meeting, the annual client review guide shows where it fits.
After the reply
On "yes", submit the introduction through your partner account with the authorized contact's details and your checklist notes, then step back. On "no", record the date in the true-up file and do not follow up on the referral. Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, one partner per company.
Fit still matters: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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. What stays unknown until SourceX reviews it: whether the history fits a dataset need, the rights review, preparation needs and any offer. The SaaS spend audit guide helps find the next app worth the same question.
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.
Before you send the draft ahead of the true-up order, register as a partner, confirm the company on who qualifies and read the program terms, so your disclosure matches the terms you signed.