This playbook belongs to the 100-day plan template for PE portfolio companies, which sets out the roles. Here the job is the play: when to notice the moment, what is at risk, and how the conversation runs. The introduction email for this moment is the companion tool.
The trigger: day one of the hold period
Close starts a clock. Within days, the operating partner and the management team agree workstreams: finance reporting to the fund's standard, IT consolidation, a new CRM or ERP, cost actions that retire tools and roles. Each of these is sensible. Together they create a short period in which records accumulated over a decade or more are moved, frozen or dropped, often by people who joined last month.
The play is to add one question to the plan while its workstreams are still being drafted: which operating teams can identify the records each retiring system holds, and who can authorize a review of them? Asked early, it costs nothing and changes no timeline. Asked after cancellation notices go out, it may already be too late, because vendor windows are short. Salesforce, for example, documents that customers may request return of their data within 30 days after contract termination (Salesforce); other vendors' windows differ and must be read from their own terms.
Signals inside the plan
The plan document usually shows the moment before anyone names it. Read its workstream lines with these signals in mind.
| Line in the plan | What it signals | Who to ask first |
|---|---|---|
| "Consolidate onto group CRM by month four" | A legacy CRM with years of account history will be retired | Sales operations lead |
| "Rationalize software spend" | Tools with small user counts but long histories get cut first | IT lead |
| "Transition finance to fund reporting pack" | Old close files and reconciliations stop being maintained | Controller |
| "Restructure support into a shared center" | Helpdesk history may be migrated partially or archived | Support manager |
| "Founder moves to advisory role" | The person who knows why records exist is leaving daily operations | CEO |
| "Renegotiate top customer contracts" | Data clauses will be read anyway; a natural moment to flag use limits | General counsel |
The records the plan puts at risk
Illustrative. A fictional 520-person insurance claims administrator is acquired in the spring. Its plan schedules three systems for retirement and two teams for restructuring.
| Record type | Team that can identify it | Plan action that threatens it | What to record |
|---|---|---|---|
| Claims files with adjuster notes, from 2012 | Claims operations lead | Migration to the platform's claims system, open claims only | First year, volume, export route |
| Customer service tickets | Support manager | Shared service center, new helpdesk | Retention setting, admin access |
| Billing and fee history by client | Controller | Fund reporting pack replaces legacy reports | Years held, system name |
| Client contracts with data clauses | General counsel | Contract renegotiation | Which contracts restrict use |
| Process documentation and audit responses | Compliance lead | Role consolidation | Where kept, who maintains it |
Notice the pattern: every row has an identifier, and none of those people can authorize a licensing review. The column you fill is metadata only. Nothing is exported, copied or shown to the operating partner.
The conversation, from question to decision
- In the plan workshop. Add a line to each retiring system: "records owner named; export confirmed before retirement." Frame it as preservation, which it is.
- With each identifier. Ask what the system holds, from what year, how it exports and who has admin access. Write the answers in the plan, not in your own notes.
- With the general counsel. Ask which client contracts mention data use, and whether any prohibit it outright. Flags, not conclusions.
- With the CEO. Present the list and ask the qualifying question directly: of these teams and systems, is there anything you want reviewed for licensing, and who signs for it? The CEO can say "not now" and the preservation lines still stand.
- Disclose before any introduction. If you have a SourceX referral relationship, say so first. CFA Institute's Standard VI(C) is one benchmark: the nature and estimated value of a referral benefit are disclosed before any formal agreement (CFA Institute). State that any reward is paid by SourceX separately and does not reduce the company's payout.
For where this work goes after day 100, see value creation plan vs 100-day plan and the operating partner 90-day plan.
Where the operating partner stops
The operating partner identifies the moment, convenes the teams and, if the CEO asks, makes the introduction. The partner does not decide for the company, negotiate on its behalf or handle its records. Check your firm's policy on fees connected to portfolio companies before accepting any reward.
Before introducing, confirm the baseline: 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. Sign the Channel Partner Agreement first; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Whether any records are selected, the rights review and any price remain unknown until SourceX reviews the company. The portfolio data opportunity scanner screens several holdings at once, the acquisition integration handoff checklist covers add-ons, and more plays 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.
When the CEO names what should be reviewed and who signs, register as a partner, check the company against who qualifies and read the terms with your firm's fee policy in mind.