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
| Line | Why it is there | What never goes in it |
|---|---|---|
| Subject line | Says the email reports findings and asks for a decision, so the CEO can file or forward it | The 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 year | Counts 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 email | Any 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 it | A deadline, a recommendation to proceed, or a forecast of value |
| "SourceX licenses approved business data..." | One accurate description of what SourceX does | Buyer names, demand claims, or AI labs |
| "Counsel would confirm first" | Shows legal assesses rights before any decision | A legal conclusion you are not qualified to give |
| The disclosure paragraph | States 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 apart | Any link between the referral and value-creation targets |
| "A description only... no exports" | Writes the metadata-only boundary into the record | A request for samples, files or admin access |
| "A one-word reply is fine either way" | Gives the CEO an easy no | Follow-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.
| Person | Where they appear | Why |
|---|---|---|
| CEO or other authorized officer | To line | Holds authority to start a licensing review on the company's behalf |
| IT lead, controller, support manager | Named in the first paragraph only | Supplied the metadata; credited so the CEO can check with them |
| General counsel | Named as the first step if the CEO says yes | Assesses whether contracts restrict use, not whether to proceed |
| Board or investment committee | Mentioned, not addressed | Under 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 CEOs | Left off | The email concerns one company's records and one decision |
| SourceX | Left off until the CEO replies yes | Copying 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 showed | Change to the draft |
|---|---|
| A system owner has already left | Replace their name with "the integration lead, who now holds access" and keep the system and year |
| The approvals matrix sends reviews to the board | Change the second paragraph to "your call to take to the board" |
| Counsel has already found restrictive client contracts | Say 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.