How much management time does a portfolio data license take?

Who does what at each step of the license?#

Management time on a portfolio data license is split across three company roles and the operating partner, with SourceX carrying the coordination and preparation work between their decisions. The table shows who does what at each step of the SourceX five-step transaction.

The pattern matters more than any single cell. The CEO's time sits at the start and the end, the IT lead's sits in the middle, and counsel's clusters around rights and the contract. Between those points, the work belongs to SourceX.

Process owners join occasionally: a support manager, dispatcher or controller who can explain what a status field or reason code means. Their time is short and specific, spent answering questions about how records were created rather than reviewing documents.

What makes the time go up or down?#

The time a license needs from management depends on the state of the records and the approval chain, not on headcount or revenue. Two portfolio companies of similar size can need very different effort.

Acquired companies deserve a separate note. An add-on that still runs its own help desk or ERP brings its own export route and its own customer contracts, so a platform with several add-ons can need more counsel time than its size suggests, even when the records themselves are strong.

A metadata fit check shows which of these factors apply before anyone commits time, which is why it comes before any export, sample or contract discussion.

What the operating partner carries#

The operating partner carries the portfolio-level work: choosing which companies go first, clearing sponsor, lender and co-investor consents, and shielding each management team from tasks that do not need them.

Reuse is where portfolio time drops. The second company benefits from the first company's checklists, contract positions and consent map, even when its records look nothing alike.

• 1Nominate companies whose records and approvals look simplest, and brief each CEO on the program.
• 2Confirm credit agreement and investor document requirements with fund counsel before term discussions.
• 3Set priority against the value creation plan so the license does not compete with critical projects.
• 4Reuse one rights checklist, consent map and approval template across companies.
• 5Hold a review after the first company finishes, and adjust before widening the program.

What the portfolio company should not have to do#

A portfolio company should not have to build data pipelines, write redaction rules or negotiate directly with buyers to license its records. Those tasks pull engineers and executives away from the operating plan and belong with the party running the transaction.

The company's essential contributions are knowledge and authority: which systems exist, what the contracts say, which records are sensitive and who signs. A request that needs neither probably belongs elsewhere.

Nothing is shared during the initial assessment. The first ask of a company is a short conversation about systems, years of accessible history and known restrictions, not files or exports.

When to say not yet#

Saying not yet is the right call when a license would land on top of work that cannot slip, and timing is the most controllable part of management time. These signals usually justify waiting.

Parking a company is not rejecting it. A finished cutover can even improve its position, because a retired system's archive is easier to scope once nobody is writing to it.

• 1An ERP, CRM or help desk cutover is underway or about to start.
• 2A sale process is live and the exit plan does not yet say how a license would be presented.
• 3Quarter-end or year-end close is running.
• 4A new CEO or CFO is still learning the business.
• 5Key customer contracts are being renegotiated and their data terms may change.

Illustrative: a print software company's time ledger#

Illustrative: a fictional vertical software company, Lindgrove Print Systems, sells production software to commercial printers. Its records sit in Jira, GitHub, Zendesk and Confluence, and a lower-middle-market fund owns it.

The CEO joins a scoping call and later signs the release and contract. The CTO answers metadata questions, then runs Jira and GitHub exports and grants scoped Zendesk access. Outside counsel reviews customer MSAs for confidentiality and data-use language, plus the help desk vendor's terms. The operating partner and fund counsel handle the lender consent.

The fund delays the start until a planned help desk migration is finished, so the CTO is not exporting from a system mid-cutover. The CEO's involvement stays at the decision points, and the fund reuses the same checklists for its next portfolio company.

How SourceX divides the work#

SourceX divides the work so the company decides and SourceX executes. The supplier approves every step of the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, while SourceX runs the inventory, preparation, buyer matching, contract coordination and delivery logistics.

Each approved package is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization, so the CEO signs against a written record rather than a memory of meetings. SourceX's dataset rights are set out in the signed supplier agreement, and large datasets stay in the company's own storage or ship on encrypted drives.