Annual license true-up data introduction email: an annotated draft for SaaS spend consultants

Short answer

Send one short email to the executive who owns the records in the app being canceled: a subject line naming the app and the true-up, one paragraph on the decision history it holds and the vendor's retention rule, one paragraph on what SourceX does with your referral interest disclosed, and a yes-or-no offer to introduce. Attach nothing, quote no records and leave the license savings out. The draft and a note on every line follow.

Visual briefFull-size diagram
An email to a chief operating officer builds from top to bottom in the center (subject, the decision history with no other copy, the vendor's retention rule, the disclosure and a yes-or-no ask) with notes appearing alternately on the left and right of each line.
The draft and its notes. Placeholders in braces come from the owner's answers and the vendor's own documentation.

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

LineWhy it is thereWhat never goes in it
Subject lineNames 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 levelRecord 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 goesJudgments about what the history is worth
"No other system has a copy"This is the test that made the app worth raisingAssumptions; 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 urgencyA 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 theirsAny claim that the owner already agreed to a licensing review
"One option, alongside a straightforward export"Makes clear an export is a perfectly good outcomeWording that frames licensing as the only sensible path
"SourceX licenses approved business data..."One accurate description of what SourceX doesBuyer names, AI labs or claims of demand
Disclosure sentencesPuts your interest in plain view before any introductionHedged 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 engagementLicense savings, your fee or any link between them
"A description only"Sets the metadata-only boundary in writingRequests for exports, samples or admin access
"A one-word reply is fine"Makes declining as easy as acceptingReminders, "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 youChange to the draft
Not sure whether a copy existsReplace "no other system has a copy" with "it is not yet clear whether another system has a copy"
The retention rule is undocumentedDelete the retention sentence and add: "{system_owner} is confirming what happens to the data after the end date."
Several apps, one ownerList each app with its decision type and years on its own line in paragraph one
The owner wants counsel involvedAdd: "Happy to include {counsel_name} on the introduction."
The order has already been placedChange 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should the email mention the license savings from canceling the app?

No. The savings belong in your true-up report. Mixing them into the introduction makes the referral look like part of your fee case, which it should never be.

What if the vendor's retention rule is not documented?

Leave the retention sentence out and write that the owner is confirming what happens to the data after the end date. Do not guess a period.

Can I send the same email for several apps?

Yes, if one executive owns all of them. Name each app and its decision history in one line each, and keep the rest of the draft unchanged.

Sources

  1. support.atlassian.com/subscriptions-and-billing/docs/reactivate-a-…
  2. microsoft.com/licensing/guidance/Enterprise-Agreement
  3. ecfr.gov/current/title-16/chapter-I/subchapter-B/part…
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment