System cost reduction introduction email: an annotated draft for restructuring technology advisors

Short answer

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.

Visual briefFull-size diagram
An email draft composing itself line by line, subject, binding date, what SourceX does, reward disclosure and a metadata-only ask, with a margin note appearing beside each line.
The draft's five parts and the rule attached to each. Bracketed fields are filled from the company's own documents.

The draft is part of the software rationalization and cost reduction guide. Sort tools into real dates and watch-list items first with the archive context checklist, and get the owner's yes in the 30-minute meeting. 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

LineWhy it is thereNever put in it
Subject lineNames 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 existsThe 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 itA 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 conversationRecord counts from systems you did not run, customer names or sample content
"You mentioned you would be open..."Repeats the owner's own opt-inAny suggestion that the owner has agreed to a license
SourceX sentenceUses the program's own description of what SourceX does, so the role is clearBuyer 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 stakesRequests for exports, screenshots, logins or a "quick sample"
Counsel and court sign-offIn 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 tooYour own legal view of whether approval is needed
Disclosure paragraphStates your interest plainly and that the company keeps its payoutReward 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 likeFollow-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 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 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 statusWhat changes in the draftExample opening line
Notice already sentUse the draft as written"Under that notice, access ends on [date]."
Court-approved rejectionName 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 dateSay 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 yetDo not send this email; mention timing only when a date existsNot 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 and the email preparation worksheet take the same fields. 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, confirm the company against who qualifies and keep the program terms to hand for their questions.

  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

Can I send this before the owner agrees to an introduction?

No. The email assumes the owner already said yes in a meeting or call. Without that, it becomes cold outreach about a client's confidential cost plan, which damages the advisory relationship.

Should I copy SourceX on the first email?

Only if the approver asked to be connected directly. Otherwise send it to the approver alone and connect SourceX once they reply, so they keep control of who learns about the cost program.

What if the date in the notice changes after I send it?

Send a one-line correction to the same thread. The email's credibility rests on the date being the company's own, so an outdated date should be fixed, not left to stand.

Sources

  1. refer.sourcex.si/terms
  2. ecfr.gov/current/title-16/chapter-I/subchapter-B/part…
  3. support.zendesk.com/hc/en-us/articles/4408883628954-Zendesk-Serv…
  4. law.cornell.edu/uscode/text/11/365

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