This template is part of the backup vendor switch guide, which explains the link-survival check itself. If the owner conversation has not happened yet, run the backup vendor switch meeting agenda first.
The draft to adapt
Fill the braces from your restore notes and the meeting. It runs to about 180 words; resist adding more.
Subject: {company}: restore test results and the archive before {old_vendor} ends
Hi {first_name},
Thanks for the time on {meeting_date}. While planning the move from {old_vendor} to {new_vendor}, {it_lead} restored a sample of archived cases and checked whether their links came back. {links_survived} of {links_checked} links resolved after the restore, and the history reaches back to {first_year}. The old contract ends on {contract_end}.
You said you would like to know what that history could mean outside the backup project. SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation, delivery and payout. To be open about my position: I am a SourceX referral partner, and SourceX may pay me a reward if a qualifying license completes. It pays that separately, nothing comes out of {company}'s compensation, and none of it changes our backup work.
If useful, I can introduce you. SourceX would begin with a short description: which systems hold the case histories, roughly how many years and cases, and who can approve a conversation. No restored files or exports. A one-word reply works: "yes" or "not now".
{your_name}
Why each line is there
| Line | Its job | Keep out of it |
|---|---|---|
| Subject line | Names the company, the test and the contract end, so it is easy to find and forward internally | "Opportunity", "earn" or any dollar figure |
| "Thanks for the time on {meeting_date}" | Shows the email follows a conversation the owner agreed to | Any suggestion that you are writing cold |
| "{it_lead} restored a sample of archived cases" | Credits the finding to the client's own test, run for the backup project | Case numbers, customer names or screenshots of the restored case |
| "{links_survived} of {links_checked} links resolved" | Gives a count the owner can confirm with the IT lead in one message | A verdict on how valuable or clean the data is |
| "The old contract ends on {contract_end}" | Ties timing to a documented access event | A date you estimated, or pressure phrasing |
| "SourceX licenses approved business data..." | One accurate sentence on what SourceX does | Buyer names, claims about demand or promised prices |
| The disclosure sentences | States the reward relationship before any introduction | Soft wording such as "I may benefit" without naming SourceX |
| "None of it changes our backup work" | Separates the referral from the paid engagement | Discounts, bundles or scope changes tied to the referral |
| "SourceX would begin with a short description" | Writes the metadata-only boundary down | Any request to send, sample or upload |
| "yes or not now" | Makes declining effortless | Follow-up deadlines or reminders about the reward |
Why the restore test is the anchor. The email leans on work the client already does. NIST's contingency planning guide says backup media should be tested regularly so files can be retrieved without errors, and CISA recommends regularly testing the availability and integrity of backups in a disaster recovery scenario. A vendor switch puts that test on the calendar; checking links adds one question. The count matters because restores do not always land where the original sat. Microsoft documents that OneDrive and SharePoint content can be restored to a new URL or new site, while Exchange mailbox items come back into the current mailbox in a new folder. A link that pointed to the old location may or may not still open, so state what the IT lead checked rather than what you assume.
Why the disclosure is spelled out. The FTC's Endorsement Guides call for clear and conspicuous disclosure of a connection between an endorser and a seller that the audience would not expect and that could affect how much weight they give the recommendation. Whether that rule reaches a private email is for your own advisers; writing it plainly costs nothing and reads well if the owner forwards the note to counsel.
Words that never belong in this email
- Restored content. No restored ticket, folder listing or mailbox screenshot, even if the IT lead offers one. Describe; do not attach.
- Backup configuration. Vault names, retention settings, job logs and encryption details belong to the backup project, not to a referral note.
- Names from inside the records. Customers, technicians and approvers stay out. Describe record types and systems.
- A reward figure framed as likely. 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. The reward rate on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the USD 50,000 floor applies once per referred company, and further qualifying transactions first agreed within 12 months pay 15%. Illustrative only, not a promise of earnings: a USD 200,000 payout to the company would mean a USD 60,000 reward. Keep that arithmetic for your own planning.
- A copy to SourceX. Wait for the owner's yes.
- Claims about the new vendor. Do not describe its restore or retention features unless its own documentation says so.
Variants for what the restore test showed
| What the IT lead found | Change to the draft |
|---|---|
| Every checked link resolved | Replace the count sentence with "Every link {it_lead} checked opened correctly after the restore." |
| Links broke because content came back in a new location | Write "Some links still point to the original location after restore; the records came back, and the team knows which links need repair." |
| The test has not been run | Drop the count and write "{it_lead} plans to restore a sample of archived cases before {contract_end}." |
| Historical restore points will move to the new vendor | Remove the contract-end sentence; there is no access event to mention |
| The owner wants the CFO to lead | Address both, name the CFO as the working contact for SourceX, and keep the owner as the one who approves |
| The owner asked about the reward | Link the rewards page instead of quoting a number |
A failed link is not a reason to hold the email. It shows the company knows where context lives and which gaps are fixable, which is a better description than an untested "everything is backed up". The archive versus backup comparison explains why backups bring systems back rather than keep records readable for years, and the ransomware restore integrity question covers what a restore does and does not prove.
Before you press send: fit and authority
Check fit first. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records 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.
Check authority second. The IT lead knows the restore result but cannot approve a licensing discussion; the CEO, usually the owner in an owner-run company, can. What stays unknown until SourceX reviews an application: SourceX's current data needs for those case histories, the rights review outcome, any de-identification work, scope and price.
Sign the Channel Partner Agreement before submitting the introduction. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. After a "yes", submit through your partner account and step back. After "not now", note the date and leave it. The introduction email builder can assemble the placeholders, the archive context checklist confirms the facts before the old vendor stops holding data, and the MSP partner page covers disclosure inside managed-service relationships.
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 restore-test email, register as a partner, confirm the company on who qualifies and read the program terms, so the disclosure in your draft matches what you signed.