How to offer a data introduction during a backup review: a 15-point backup-owner checklist that keeps the retention decision, the CEO's question and SourceX's review in three separate hands

Short answer

Finish the backup review first and write its decisions down, then raise the introduction as a separate item for the company's CEO to decide, not the IT lead who booked the review. Describe only what the review already showed, at the level of descriptions: which systems are protected, how many years they reach back, which old backup sets are due to retire. Say that you may receive a referral reward. Run no restores, exports or catalog reports for it. If the CEO wants the conversation, the company applies and SourceX does the review.

Visual briefFull-size diagram
An annotated backup review sheet listing 9 protected systems, an oldest restore point in 2013 and a legacy set retiring in March, marked as metadata to describe once the CEO approves, leads to three boxes in order: the MSP describes and introduces, the CEO decides, SourceX reviews fit; a warning strip says no restores or exports are run for a referral.
Illustrative review sheet for a fictional 180-person engineering firm; the three roles follow the checklist on this page.

A backup review is one of the few routine meetings where an MSP sees how much operating history a client keeps and how long it plans to keep it. That makes it a fair moment to mention licensing, and an easy one to get wrong, because the same meeting decides what history survives.

What a backup review shows you, and what it leaves out

It shows the shape of the client's history, never its value or its ownership. NIST's contingency planning guide, SP 800-34 Rev. 1, lists what backup policy covers: "Data backup policies should designate the location of stored data, file-naming conventions, media rotation frequency, and method for transporting data offsite." NIST's backup guide written for managed service providers, which notes that "When an MSP is vulnerable its customers are vulnerable as well", has MSPs rank a client's files by business value and set recovery time and recovery point objectives (our paraphrase).

That ranking measures what the client needs back after an outage. Licensing value is a different question. A project archive that rarely changes may rank low for recovery and still hold the company's longest run of operating records. Neither ranking says whether any record can be licensed; that depends on the company's rights and on SourceX's review of operating history, documentation, data rights and relevance to what AI developers currently need.

Review findingWhat it tells youWhat it cannot tell you
List of protected systemsWhich business systems exist and are keptWhether their contents belong to the company or to its clients
Retention period per systemHow long history is heldWhether any of it may be licensed
Oldest restore pointHow far back a system reachesWhether the old records are complete or usable
Legacy backup set due to retireA dated change to what history survivesWhether the CEO wants anything to happen about it
Restore test resultsWhether recovery worksAnything about what the records say

The review also leaves out three facts only the company holds: whether customer contracts restrict reuse, whether the records were licensed for AI training before (a supplier confirms to SourceX that they were not), and whether the CEO wants the conversation at all. The archiving versus backup comparison explains why backups are a poor stand-in for a records archive.

Findings that can open the conversation, and who hears them first

The useful finding is about history, not failure: a long-lived system, a legacy set scheduled for retirement, systems consolidated after an acquisition, a planned change of backup vendor. The person across the table is usually an IT manager, operations lead or CFO. That person can carry the idea upward. The CEO decides.

The introduction never changes a backup recommendation. If the review proposes retiring old backup sets, that decision follows the client's own retention policy and its advisers, on the schedule the backup work needs. You may tell the CEO the retirement is coming so the licensing question can be weighed in time; you never suggest keeping data longer for the sake of a referral. A dated retirement is a reason to raise the subject this month rather than next quarter. It is never a reason to skip the CEO.

Whether any records would ever be licensed, and from which systems, is settled later between the company and SourceX under the company's own signed agreement. If the trigger is a vendor change rather than a review, the backup vendor switch guide covers that moment; if the subject comes up in a quarterly business review, the MSP QBR agenda template has a records block built for it.

The backup-owner conversation checklist

Fifteen checks in three stages. Each names who answers it, so a technician never ends up answering an owner's question or SourceX's.

#CheckAnswered byDone when
1The backup decisions are written up and sentYou, the technical custodianThe action list exists and mentions nothing about SourceX
2Your services agreement and the client's security policy allow you to raise a referralYouYou have read both; whichever is stricter governs
3You have signed the SourceX Channel Partner AgreementYouSigned before any introduction is submitted
4Your note uses only what the review producedYouSystem names, year spans, rough volumes and retirement dates; no new searches, restores or reports
5You know who the CEO is and how to reach themYou, with the review sponsorA named CEO and an agreed route, often through the sponsor
6The CEO hears about it before anyone outside the companyThe CEOThe CEO knows first; SourceX's screening page treats a referral the decision maker never heard about as a poor fit
7You disclose the referral rewardYou, to the CEOSaid in the first conversation, naming SourceX as the payer
8The CEO approves what your note may sayThe CEOApproved wording, or "say nothing yet"
9The records are the company's own, not its clients'The CEO or whoever runs the recordsA plain answer; client-owned material is usually not a fit
10No earlier AI-training license and no earlier contact with SourceXThe CEOBoth answered; earlier contact makes the company a duplicate under section 3 of the terms
11One written introduction goes inYouA dated record naming the company and the CEO
12The company applies itselfThe companyA verified application inside the 90-day attribution window
13SourceX puts its questions to the company directlySourceX and the companyYou answer system questions only as far as the CEO allows
14Nothing leaves your hands for the referralYouNo copies, exports or credentials; a later export runs only on the company's written instruction under its own agreement
15Retention proceeds on its own scheduleThe companyThe backup action list is unchanged by the introduction

Checks 1 to 5 sit with you, 6 to 10 with the customer owner, and 11 to 15 cover what happens once SourceX is involved. Check 4 is the one teams miss: writing "file server, project folders, about 2013 to now" from the review report is a description, while opening the backup console to count folders for a referral is new work.

Custodian, owner and SourceX each keep their own job

You, the technical custodian, work inside the services agreement. Your access exists for backup and recovery. Signing the partner agreement adds no authority on top: under section 4.2 of the sample, a partner gains no standing to pass on a company's inventory, records, raw data or personal details, nor to reach the systems that would extract them, and section 4.4 bars keeping dataset copies through the referral program without separate written authorization. The MSP partner page sets out access, service duty and licensing authority in more depth.

The customer owner, the company acting through its CEO, decides whether to talk, what scope to offer and which terms to accept. It also owns its retention policy, before and after any introduction.

SourceX reviews the company and talks to it directly. Section 2 of the terms lets SourceX communicate with a referred company without affecting valid attribution, and section 2.2 of the agreement sample confirms a partner need not join every call, email or negotiation.

What to say when the review wraps up (Illustrative)

Illustrative. A fictional 180-person engineering firm, founder-run, holds its annual backup review with its MSP. The report covers 9 protected systems; the oldest restore point on the project file server dates from 2013; a legacy backup set is due to retire in March under the firm's retention plan.

To the IT manager who booked the review, once the action list is agreed:

"That's the backup work settled. One separate item, outside our contract: your project records go back to 2013. I'm a referral partner for SourceX, which licenses company records for AI training, and SourceX would pay me a reward if a license ever completed. Would your CEO want to hear about that, and would you prefer to mention it yourself or have me ask?"

To the CEO, once the IT manager agrees:

"Our review found project records back to 2013 on systems you still run, and the old archive set retires in March as planned; none of that changes. Separately, SourceX licenses records like these for AI training. It would pay me a referral reward from its own funds, and nothing would come out of what it pays you. If you want an introduction, your firm applies itself and SourceX asks for a description, never files. Yes, no and later are all fine answers."

The CEO says yes. The MSP, already signed up, submits one written introduction, the firm applies, and SourceX's questions go to the CEO. Illustrative arithmetic: if SourceX later paid the firm USD 200,000 under its signed agreement for a first qualifying transaction, the MSP's reward would be USD 60,000 (the greater of USD 50,000 plus 5%, and 15% of that payout), funded by SourceX rather than taken from the firm's agreed compensation. The March retirement goes ahead on schedule.

A second client of the same MSP, a 70-person document services company, also has deep backups, but most of what it stores is scanned files it holds for its own customers. That material belongs to its clients, so the MSP leaves the subject out of that review. A question about who may license records describing a client's own systems is explored in who can license backup restore validation records.

When the backup review is the wrong place to raise it

  • The company is too small. Its full-time headcount never reached 50 at its peak, leaving contractors out. For a staffing firm, workers placed with clients do not count.
  • The records belong to someone else. Hosted customer files, client document stores and portals the client runs for its own customers.
  • The review follows an incident. After a breach or a failed restore, finish the recovery work first.
  • The sponsor wants to keep it from the CEO. Wait; without the CEO's knowledge it is usually not a fit.
  • Your agreement or the client's policy forbids it. Whichever is stricter governs, and disclosure duties are covered in MSP vendor referral fees.
  • The records were licensed for AI training before, or the company already talks to SourceX. The first rules the data out; the second makes the company a duplicate.
  • The company is outside the covered geography. 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.

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 CEO says yes after your backup review, register for a partner link, check the company once more against who qualifies and read the program terms before you submit the introduction. For the email that follows a vendor change, adapt the backup vendor switch introduction email; more MSP playbooks are in the guides library.

  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

May I run a catalog report to size a client's history before mentioning SourceX?

No. Use only what the backup review already produced. A new report, restore or content search run to size records for a referral is work the client never asked for, and it shows up in logs the client's security reviewer reads.

Should an MSP suggest keeping old backup sets longer in case the records can be licensed?

No. Retention follows the client's own policy and advisers. You can tell the CEO that a retirement is scheduled so the licensing question gets weighed in time, but the backup recommendation stays exactly what it would have been without SourceX.

Is the IT manager who booked the backup review the right person to say yes?

No. The IT manager can tell you whether the CEO would want to hear about it and help you reach the CEO. Under the program the CEO authorizes a licensing discussion, so the CEO answers.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. refer.sourcex.si/how-it-works
  5. sourcex.si/how-it-works
  6. nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800…
  7. csrc.nist.gov/pubs/other/2020/04/24/protecting-data-from-r…

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