# Cost reduction introduction email, annotated | SourceX

Canonical: https://refer.sourcex.si/resources/system-cost-reduction-introduction-email
Last updated: 2026-11-04

Write the introduction only after the owner has agreed to it, and only about a tool whose end of access is fixed by a document: a notice already sent, a court order or the vendor's written post-cancellation policy. Keep it to a subject line and three short paragraphs: the archive and its binding date, what SourceX does, and your referral interest stated plainly. Ask for a metadata-only call. Never attach records, quote figures from the cost plan or imply a deadline the company has not set.

The draft is part of the [software rationalization and cost reduction guide](/guides/software-rationalization-cost-reduction). Sort tools into real dates and watch-list items first with the [archive context checklist](/resources/system-cost-reduction-archive-context-checklist), and get the owner's yes in the [30-minute meeting](/resources/system-cost-reduction-meeting-agenda). This page covers the writing.

## The draft, ready to adapt

> **Subject:** Before [tool] access ends on [date in the notice]: a short call about its history
>
> Hi [approver's first name],
>
> Following our review on [meeting date], [Company] has given notice on [tool], which holds about [years] years of [tickets, cases or jobs]. Under that notice, access ends on [date]. You mentioned you would be open to hearing about options for that history before then.
>
> SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. A first call covers only metadata: which systems, how many years, how the records are organized and who owns them. No records, exports or logins are shared at this stage, and [general counsel's name] should confirm whether any discussion needs court or lender sign-off.
>
> In full transparency: I am a SourceX referral partner. If a license completes and SourceX pays [Company], SourceX may pay me a referral reward separately; it is never deducted from what [Company] receives. If you would like to go ahead, reply and I will connect you, or tell me it is not a fit and I will drop it.
>
> [Your name]

About 170 words. If yours runs past 220, cut from the second paragraph, never from the disclosure.

## Line-by-line annotation

| Line | Why it is there | Never put in it |
|---|---|---|
| Subject line | Names the tool and the binding date, so the approver sees at once that the timing is the company's own | "Urgent", "last chance" or any date the company has not fixed |
| "Following our review..." | Anchors the email to a conversation the approver remembers, which shows consent already exists | The names of other tools in the cost plan, headcount cuts or savings targets |
| "...has given notice on [tool]" | States the document that fixes the date, so nobody has to take the advisor's word for it | A vendor policy as if it were the contract; quote the notice, or say the policy still needs checking |
| "...holds about [years] years..." | Gives scale in metadata terms, enough for a first conversation | Record counts from systems you did not run, customer names or sample content |
| "You mentioned you would be open..." | Repeats the owner's own opt-in | Any suggestion that the owner has agreed to a license |
| SourceX sentence | Uses the program's own description of what SourceX does, so the role is clear | Buyer names, claims about demand, price expectations or promises about acceptance |
| "A first call covers only metadata..." | Sets the boundary for what will be shared, which lowers the legal stakes | Requests for exports, screenshots, logins or a "quick sample" |
| Counsel and court sign-off | In a court case, rejection of an executory contract needs the court's approval under 11 U.S.C. 365, and a data license may need approval too | Your own legal view of whether approval is needed |
| Disclosure paragraph | States your interest plainly and that the company keeps its payout | Reward amounts, percentages applied to the company's deal or "small finder's fee" |
| "...tell me it is not a fit..." | Makes declining easy, which is what an honest introduction looks like | Follow-up threats such as "I will check back daily" |

## Why the disclosure paragraph is not optional

The Federal Trade Commission's endorsement guides were written for advertising, but their test is a useful benchmark here: when a connection could affect how much weight someone gives a recommendation and they would not reasonably expect it, it should be disclosed clearly, and the disclosure must convey the nature of the connection, not every detail. An approver reading an introduction from their restructuring advisor would not expect the advisor to have a financial interest. So the email says so in plain words. The [introduction without endorsement guide](/guides/introduction-without-endorsement) explains how to connect two parties without vouching for either.

Keep the disclosure accurate to the terms. The default reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, paid only after the payment conditions in the [terms](/terms) are met. You do not need those figures in the email; if the approver asks, point to the terms rather than estimating.

## Variants by date status

| Date status | What changes in the draft | Example opening line |
|---|---|---|
| Notice already sent | Use the draft as written | "Under that notice, access ends on [date]." |
| Court-approved rejection | Name the order instead of the notice, and keep the counsel sentence | "Under the court's order approving rejection, the contract ends on [date]." |
| Vendor policy is the only date | Say the policy still needs confirming for this account | "Zendesk's published policy starts deletion 90 days after cancellation; [IT lead] is confirming how it applies to your account." |
| No binding date yet | Do not send this email; mention timing only when a date exists | Not applicable: keep the tool on the watch list |

The vendor example is a published policy as checked on 2026-10-18; policies change and contracts can override them.

## Before you press send

- The owner said yes to an introduction, and you know who the approver is.
- The date in the subject line comes from a document the company holds.
- The company appears to meet the baseline: 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.
- You signed the Channel Partner Agreement. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application.
- Unknown until SourceX reviews it, and not to be implied in the email: buyer interest, the rights result, de-identification and any offer.

To adapt the wording quickly, the [introduction email builder](/tools/introduction-email-builder) and the [email preparation worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation) take the same fields. [Warm introduction etiquette](/guides/warm-introduction-etiquette) covers tone and follow-up.

## 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.

If the approver replies yes to this email, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies) and keep the [program terms](/terms) to hand for their questions.

## Sources

- https://refer.sourcex.si/terms
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
- https://support.zendesk.com/hc/en-us/articles/4408883628954-Zendesk-Service-Data-Deletion-Policy
- https://www.law.cornell.edu/uscode/text/11/365
