First 100-day plan meeting agenda: a timed 30-minute records meeting in five blocks

Short answer

The teams that can identify records and authorize a review fit in one 30-minute meeting: the integration lead names the systems being retired, the IT lead and controller say what those systems hold and how to export it, the general counsel flags contract limits, and the CEO decides. The operating partner chairs and keeps time. Run it once, after the systems inventory exists and before the first cancellation notice. The agenda below times each block, names who answers and describes a good answer.

Visual briefFull-size diagram
A meeting clock split into five timed segments that fill in turn, labelled retiring systems, records held, contract limits, CEO decision and disclosure, ending in a recorded decision.
Illustrative 30-minute agenda. The CEO's decision in the fourth block is the meeting's output.

This agenda belongs with the comparison of a value creation plan and a 100-day plan, which explains why the protective step sits in the 100-day plan and any licensing review later. The companion archive context checklist covers what to confirm before switch-off.

Before the clock starts: who to invite and what to send

Send the invitation with a one-page pre-read: the integration plan's list of systems to retire and their contract end dates. Nothing else. No records are opened in or before the meeting.

InviteeWhy they are in the roomBring
Integration or PMO leadOwns the retirement list and datesThe system shortlist with contract end dates
IT leadKnows export routes and admin accessAdmin access holder for each system
ControllerKnows which systems hold financial and operating historyFirst year of data per system
General counselKnows which contracts limit use of recordsAny customer or vendor terms that mention data
CEOOnly person who can authorize anything beyond preservationA decision
Operating partnerChairs; discloses any referral relationshipThe timer

Keep the list to these six. Each extra person adds opinions, not authority.

The 30-minute agenda at a glance

Illustrative. A fictional 450-person facilities services company, acquired in the spring, holds this meeting in week five, right after the integration review.

BlockMinutesQuestionWho answersOutput
1. Trigger0-5Which systems will the integration retire, and on what contract dates?Integration leadShortlist with dates
2. Records5-13What does each system hold, from which year, and who can export it?IT lead and controllerOne inventory row per system
3. Limits13-19Does any contract restrict how these records may be used?General counselFlags, not conclusions
4. Decision19-26For each system: export before retirement, and review in the value creation plan, park or close?CEORecorded decision per system
5. Disclosure26-30Does the CEO want an introduction to explore licensing?Operating partner, then CEOOpt-in, or item closed

Block by block: what a good answer sounds like

Block 1, trigger (5 minutes). Weak: "We're consolidating onto the parent's CRM sometime this year." Good: "Three systems retire. The legacy CRM's contract ends on the date in its order form, the field service tool a month later, and the old ticketing system at year end." Dates come from contracts, not renewal emails.

Block 2, records (8 minutes). Weak: "Everything's in there." Good: "The CRM holds accounts and service contracts from 2014, about twelve years. Export is a full CSV with attachments, and two people have admin rights." The IT lead should also know the vendor's post-termination window. Salesforce, for example, documents that customers may request return of their data within 30 days after contract termination, as CSV files with attachments in native format; a good answer names the window for each system from the vendor's own documentation.

Block 3, limits (6 minutes). Weak: "Legal will need to look at that." Good: "Two large customer contracts have confidentiality clauses that mention service data. I'll flag them; I'm not concluding anything today." Flags are enough. Rights questions are settled later, by the company and, if it proceeds, in SourceX's rights review.

Block 4, decision (7 minutes). Weak: "Let's revisit next month." Good: "Export all three, verified before the end dates. Put a licensing review for the CRM and ticketing history in the value creation plan for the second half; park field service." The decision belongs to the CEO alone, and silence is not a decision.

Block 5, disclosure (4 minutes). If the operating partner has a referral relationship with SourceX, say so before offering any introduction. CFA Institute's Standard VI(C) is one example of the norm: compensation for a recommendation is disclosed to the client before any formal agreement. A good answer from the CEO is either "Yes, introduce me" or "Not now", both of which end the item.

The decision record the meeting must produce

The meeting succeeds if, and only if, it ends with this record filed in the 100-day plan close-out. The 100-day plan template has room for it.

SystemRecords and first yearExport owner and verify-by dateContract flagsCEO decisionIntroduction
Legacy CRMAccounts, service contracts, 2014IT lead, two weeks before contract endTwo customer clausesExport; review in value creation planCEO opted in
TicketingService tickets, 2016IT lead, one month before year endNone knownExport; review in value creation planCovered by the same opt-in
Field serviceWork orders, 2019Controller, before contract endNone knownExport; parkNot applicable

Whether a review happens is then tracked in later meetings; the portfolio review agenda shows where. For governance timing more broadly, see the first board meeting after investment.

If the CEO opts in, confirm the baseline before introducing: 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. Share metadata only. What stays unknown until SourceX reviews the company: buyer interest, the rights review result and any offer. More on the role is on the operating partner page.

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 your meeting ends with a CEO opt-in, register as a partner and sign the partner agreement before you introduce anyone, check the company against who qualifies, and keep the program terms at hand for the disclosure in block 5.

  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

Why 30 minutes rather than a longer workshop?

The meeting decides one thing: what happens to the records in systems the integration will retire. A short, timed agenda keeps it to that decision and stops it turning into a data strategy session.

What if the CEO cannot attend?

Move the meeting. Everyone else can describe the records, but only the CEO, or someone the CEO has expressly delegated, can decide on export and a later licensing review.

Is the referral disclosure always on the agenda?

Only if the operating partner has a referral relationship with SourceX. If so, it comes before any introduction is offered, and the CEO can close the item in one sentence.

Sources

  1. salesforce.com/en-us/wp-content/uploads/sites/4/documents/l…
  2. cfainstitute.org/standards/professionals/code-ethics-standard…
  3. refer.sourcex.si/terms

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