First 100-day plan introduction email: an annotated draft that separates who identifies records from who authorizes

Short answer

Send one short email to the portfolio CEO, not to the people who found the records. Credit the system owners who described each system (IT lead, controller, support manager), state plainly that the decision to explore a licensing review is the CEO's, with the board where the approvals matrix requires it, disclose your referral interest, and ask only for a description. Below is a draft to adapt and a note on every line: what it does and what never belongs in it.

Visual briefFull-size diagram
An email to a portfolio CEO writes itself line by line, from the subject to the systems the teams described, the decision that rests with the CEO, the referral disclosure and a description-only ask, while margin notes on the left explain each line.
Illustrative draft. Placeholders in braces come from the Days 1-30 inventory, never from records you have opened.

This email belongs to the 100-day plan template for PE portfolio companies. It comes after the 30-minute records meeting and before anything in the archive context checklist is switched off; the partner playbook covers how the opportunity surfaces in the first place.

The draft, ready to adapt

Illustrative. Fill each brace from the Days 1-30 inventory and your meeting notes. Keep it under 220 words and send it from your own address.

Subject: {company} legacy systems: what the teams found, and a decision that is yours

Hi {ceo_first_name},

In the Days 1-30 inventory, {it_lead} described the helpdesk back to {year_1}, {controller} confirmed billing and contract history back to {year_2}, and {support_manager} said resolutions are written into the tickets. They can describe these systems; they cannot decide what happens to them, and nobody has asked them to.

Whether to explore licensing any of this history is your call, with the board if our approvals matrix requires it. SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation, delivery and payout. Counsel would confirm first whether client contracts restrict anything.

Disclosure: I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes. SourceX pays it separately; it does not reduce what {company} would receive and it has no bearing on the plan or on retirement dates.

If you want to look at it, SourceX would start from a description only: which systems, how many years, rough volumes, who owns them. No exports and no records. A one-word reply is fine either way.

{operating_partner_name}

Line-by-line annotation

LineWhy it is thereWhat never goes in it
Subject lineSays the email reports findings and asks for a decision, so the CEO can file or forward itThe word "opportunity", any figure, or the program's name as a headline
"{it_lead} described... {controller} confirmed..."Credits each fact to the system owner who supplied it, at the level of system and yearCounts you pulled yourself, client names, screenshots or ticket text
"They can describe these systems; they cannot decide"Separates identification from authority in one sentence, which is the whole point of the emailAny suggestion the records owner has already agreed to anything
"Your call, with the board if our approvals matrix requires it"Puts authority where corporate governance puts itA deadline, a recommendation to proceed, or a forecast of value
"SourceX licenses approved business data..."One accurate description of what SourceX doesBuyer names, demand claims, or AI labs
"Counsel would confirm first"Shows legal assesses rights before any decisionA legal conclusion you are not qualified to give
The disclosure paragraphStates the connection and who pays it, in plain words, before any introduction"I may benefit" with no payer named, or a reward estimate
"No bearing on the plan or on retirement dates"Keeps the 100-day plan and the referral apartAny link between the referral and value-creation targets
"A description only... no exports"Writes the metadata-only boundary into the recordA request for samples, files or admin access
"A one-word reply is fine either way"Gives the CEO an easy noFollow-ups framed as last chances

The disclosure sits in the body, not a footer: the FTC's Endorsement Guides call for clear and conspicuous disclosure of an unexpected connection, including the chance of payment, and FTC guidance says vague labels and disclosures behind links fall short. Whether they reach a private email is for your firm's counsel; a plain paragraph removes the doubt.

Addressing it: who goes on the To line, who is named, who is left off

The email goes to the officer who can authorize; everyone else appears only as the source of a fact. Getting this wrong is the usual way a well-meant email turns into a governance problem.

PersonWhere they appearWhy
CEO or other authorized officerTo lineHolds authority to start a licensing review on the company's behalf
IT lead, controller, support managerNamed in the first paragraph onlySupplied the metadata; credited so the CEO can check with them
General counselNamed as the first step if the CEO says yesAssesses whether contracts restrict use, not whether to proceed
Board or investment committeeMentioned, not addressedUnder Delaware law the board manages or directs the corporation's affairs; the approvals matrix says when a review reaches it
Deal team and other portfolio CEOsLeft offThe email concerns one company's records and one decision
SourceXLeft off until the CEO replies yesCopying SourceX first turns an offer into an assumption

Words that never go in a portfolio-company email

  • Records or extracts. No tickets, invoices, contract pages or report files, even when a system owner offers to attach one.
  • People's names from the records. Describe record types; name only the colleagues who described them.
  • Reward figures as a promise. If the CEO asks, the default is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, payable only after the conditions in the terms are met. Illustrative only: a $250,000 Actual Supplier Payout would mean a $62,500 reward. Point to the rewards page rather than quoting a number in the first email.
  • Pressure. The only real dates are the company's own contract ends and retirement plans.

Adapting the draft to what the inventory found

What the first 30 days showedChange to the draft
A system owner has already leftReplace their name with "the integration lead, who now holds access" and keep the system and year
The approvals matrix sends reviews to the boardChange the second paragraph to "your call to take to the board"
Counsel has already found restrictive client contractsSay so in one line and narrow the ask to the systems without restrictions

The introduction email builder produces variants, the operating partner 90-day plan shows where this email sits in your calendar, and the value creation plan comparison explains why the referral stays out of plan documents.

After the CEO replies

On yes, sign the Channel Partner Agreement if you have not, submit the authorized contact through your partner account, and step back; SourceX works with the company directly. 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. On "not now", record the date and do not chase.

SourceX checks fit, but screen first: 50+ full-time employees at peak (contractors excluded), a 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. The rights review, de-identification needs, buyer interest and any offer stay unknown until SourceX reviews the application. More plays for your role are 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.

Before the email goes to the CEO, register as a partner, screen the company against who qualifies and read the program terms, so the disclosure paragraph matches what you signed.

  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

Should the records owner be copied on the email to the CEO?

Only if the CEO would expect it. Naming the records owner as the source of the facts is enough; copying them can make it look as though the decision has been delegated to the person who gathered the metadata.

Can the operating partner send this to the board instead of the CEO?

Send it to the officer who runs the company first. If the approvals matrix sends a licensing review to the board, the CEO raises it there; the email should say the board may be involved, not go around the CEO.

What if the firm's policy does not allow partners to accept fees connected to portfolio companies?

Then do not send the email. Check the firm's conflicts policy before the Day 60 screen; if it rules out a referral reward, the inventory still helps the company, and no introduction is made through this program.

Sources

  1. delcode.delaware.gov/title8/title8.pdf
  2. ecfr.gov/current/title-16/chapter-I/subchapter-B/part…
  3. ftc.gov/business-guidance/resources/ftcs-endorsement…
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

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