This agenda is part of the backup vendor switch guide for backup service providers. If the owner wants a written record of what must happen before the old vendor stops holding data, pair it with the backup vendor switch archive context checklist.
Before the meeting
Send a two-line invitation that names the purpose: "Fifteen minutes after the migration plan, on how much of your history comes back intact, and one optional question about it." Invite the IT lead and the person who can authorize a licensing discussion: the CEO, who in an owner-run company is usually the owner. Bring nothing from the client's systems. You need the migration plan's dates and a blank page for answers.
The 15-minute agenda at a glance
| Minutes | Block | The question | Who answers |
|---|---|---|---|
| 0 to 2 | The switch | When does the old vendor contract end, and do historical restore points move? | IT lead |
| 2 to 5 | Restore with links | Has the company verified that archived records can be restored with their links? | IT lead |
| 5 to 9 | Four metadata questions | What, how long, which copy is authoritative, who owns it? | IT lead, then owner |
| 9 to 12 | Disclosure and permission | Would you like an introduction, now that you know my interest? | Owner |
| 12 to 15 | Decision | Introduce now, test first, or no? | Owner |
Block by block: what a good answer sounds like
Minutes 0 to 2: the switch. Ask for the old contract's end date and whether historical restore points will move to the new vendor. A good answer is specific: "The old contract ends on [date]; restore points older than a year stay with the old vendor." That sentence tells you whether there is a documented access event. If everything moves, say so and keep the pace relaxed.
Minutes 2 to 5: restore with links. Ask the question exactly: "Has the company verified that archived records can be restored with their links?" Explain in one sentence what you mean: a restored support ticket still opens its customer email thread, its approval and its invoice, not just its own file. A recovery drill that only checks files come back may never open the links inside a recovered case, so this can be news to the room.
A good answer names systems and results: "We restored one case last quarter; the ticket and email linked, the shared folder link broke because SharePoint restored to a new site." That matches how some restores work: Microsoft documents that OneDrive and SharePoint content can be restored to a new URL or new site, while Exchange mailbox items restore to the current mailbox in a new folder. A weak answer, "the backups are fine", is not a no; it means block five will likely be "test first".
Minutes 5 to 9: four metadata questions. Ask them in order and write down only the answers.
- What: which systems hold the longest case or project histories?
- How long: from which year, and roughly how many cases?
- Which copy is authoritative: after the old contract ends, will any system exist only in the old backups?
- Who owns it: which executive owns those records, and do client contracts limit reuse?
A good answer to question four comes from the owner, not the IT lead: "I do, and two key accounts have contract terms we would need to check." "Contracts unknown" is acceptable.
Minutes 9 to 12: disclosure and permission. Say plainly that SourceX licenses approved business data directly from companies for AI training and evaluation; that you are a SourceX referral partner and may receive a reward if a qualifying license completes; that SourceX pays it separately and it never reduces what the company receives; and that the backup project continues exactly the same whatever they decide. Then ask: "Would you like an introduction?" A good answer is a clear one, in either direction.
Minutes 12 to 15: the decision. Read back the answers and agree one outcome.
The decision the meeting produces
| Outcome | When it fits | What you do next |
|---|---|---|
| Introduce now | Links survive for at least some case histories, the owner is identified and says yes | Submit the introduction to the owner, with the IT lead copied if they want |
| Test first | The restore-with-links question has no answer yet | IT lead adds a link check to the planned restore test; book ten minutes after it |
| No | The owner declines, or the history is thin | Note the date and continue the backup project unchanged |
Illustrative. At a 260-person property management firm, the IT lead reports that ticket-to-email links survived a test restore but approval records point to deleted accounts, history runs from 2015, and older restore points stay with the old vendor when its contract ends. The chief financial officer owns the records and says yes. Outcome: introduce now, with the two broken link types noted as known gaps.
If the IT lead asks why the link check belongs in this meeting at all: 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. The agenda only adds links to a drill the company should already run.
Never ask for exports, screenshots or a sample case during the meeting. The archive versus backup comparison helps if the owner asks why backups alone may not keep records readable for years, and the MSP QBR agenda template shows where this 15 minutes can sit in a regular review. The portfolio review agenda covers the same idea for investor-backed groups.
Qualification before you submit
The company needs 50+ full-time employees at peak (contractors excluded), 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.
What stays unknown until SourceX reviews it: whether the histories fit a dataset need, the rights review result, scope, preparation needs and any offer. 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. The MSP partner page covers disclosure in long client 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.
If the meeting ends on "introduce now", register as a partner, confirm the company on who qualifies, and read the program terms before you submit the introduction.