Private equity and portfolios
AI readiness in PE-backed companies: what operating partners check in 2026
By SourceX Editorial · Updated
Short answer
Operating partners checking AI readiness across a private equity portfolio in 2026 look at four areas: data foundations, rights, governance and quick wins. The deciding question is whether each company's records and permissions can support AI work at all. Quick wins often come from preserving and licensing legacy archives before systems retire, not from new tools.
Key takeaways
- AI readiness is checked company by company across data foundations, rights, governance and quick wins.
- The first quick win is usually preventing history loss in planned system migrations.
- An AI use policy and an inventory of AI vendor data terms belong in every governance check.
- Legacy archives with clear rights can become a licensing line while the wider AI program is still being planned.
What do operating partners check for AI readiness in 2026?#
Operating partners checking AI readiness in 2026 look past pilots and tool subscriptions to four areas at each company: data foundations, rights, governance and quick wins. The change from earlier reviews is that the records and permissions behind AI work now get as much attention as the projects themselves.
The reason is practical. AI pilots at portfolio companies tend to stall on the same few problems: history lost in a migration, records that cannot be exported, customer terms nobody reviewed and no one with authority to approve data use. Checking those early saves a program from repeated false starts and makes later board reporting more credible.
Outside research points the same way. Analysys Mason has predicted that fewer than 25% of portfolio companies' AI tools will fully succeed in 2026, citing inflated vendor promises, insufficient data readiness and weak operational integration. That is a forecast, not a measurement, but it matches what operating partners report: the data foundations decide whether the tools pay off.
The portfolio screen table#
The portfolio screen table gives every company the same four areas, the same evidence requests and a known common gap to look for. Use it as the agenda for a readiness conversation with each CEO rather than as a form to send out, since the follow-up questions matter more than the first answers.
| Area | What to check | Evidence to ask for | Common gap |
|---|---|---|---|
| Data foundations | Which systems hold core records, how far back, and whether they connect | System list with date coverage and one test export | History lost in a past migration |
| Rights | Whether customer, vendor and employee terms allow the planned uses | Contract templates, terms versions, vendor export rights | Customer terms never reviewed for data use |
| Governance | Who approves data use, how staff use AI tools, how vendors treat inputs | AI use policy, named approver, AI vendor list with data terms | Staff using AI tools with no policy |
| Quick wins | Moves that create value or prevent loss with current systems | Migration calendar, archive list, candidate record families | Legacy archives shut off without export |
Data foundations: what to look at first#
Data foundations come first because every AI use, internal or external, depends on records that exist, connect and can be exported. Ask each company for a list of its core systems, how many years of history each still holds and one example of a full export with free-text fields and attachments intact.
Be wary of companies that describe their data in terms of dashboards. Reporting layers can hide the fact that the underlying notes, threads and attachments were never kept or were lost in a move between systems. The records that matter for AI are usually unglamorous: ticket threads, job notes, order exception emails, NCR dispositions and project review comments.
Rights: the check most readiness reviews skip#
Rights are the check most readiness reviews skip, and they decide whether any AI use of customer-related records can go ahead. The question is not whether the company owns its systems but whether its customer contracts, terms of service, employee notices and vendor agreements allow the specific use in mind.
Ask for the documents rather than a summary. A company that has never reviewed its terms for data use should score that as a gap, not a pass, and the review should separate records that are clearly the company's own work, such as internal engineering issues or dispatcher notes, from customer content that needs permission.
Rights also differ by use. Training an internal assistant on support history, adding AI features to a product and licensing prepared records to an AI developer are three different questions, each with its own permission path. Record the answer for each use separately so a yes for one is not read as a yes for all.
Quick wins that do not need a data platform#
Quick wins in AI readiness are moves a company can make with its current systems and people. They rarely involve new software, and several protect value that would otherwise disappear quietly at the end of a vendor contract.
- Freeze the shutdown of any legacy help desk, CRM, ERP or TMS until its full history is exported.
- Inventory the AI tools staff already use and the data terms each vendor applies to inputs.
- Name one executive owner for data decisions and confirm who signs for the legal entity.
- Collect every version of the customer terms and the largest negotiated customer agreements.
- Run a metadata-only licensing fit check on legacy archives where the rights look clear.
Governance questions for the quarterly review#
Governance questions belong in the quarterly portfolio review because the answers change as companies adopt tools, sign contracts and retire systems. Ask the same five questions each time so movement is visible across quarters and across companies.
| Question | Why it matters | Who answers |
|---|---|---|
| Which AI tools have access to company records, and on what terms? | Vendor terms may allow retention of inputs or training on them | CIO or IT lead |
| Who approves new uses of customer or employee data? | Unclear authority stalls projects and invites mistakes | CEO with counsel |
| Which systems retire in the next planning cycle? | Retirements are the main cause of lost history | COO or IT lead |
| Have customer terms been reviewed for AI and data use? | Rights gaps block both product features and licensing | General counsel or outside counsel |
| Which record families could support licensing? | Identifies a revenue option that does not change operations | CEO and value creation lead |
Illustrative: a lower-middle-market fund reviews four companies#
Illustrative: a fictional lower-middle-market fund reviews four portfolio companies: a commercial landscaping company on a field service platform, a construction bid management software vendor, an industrial distributor preparing to replace its ERP, and an environmental engineering firm on Deltek.
The distributor's ERP replacement drives the first action: the operating partner requires a full export of order exceptions and customer service history before cutover. The software vendor scores well on data foundations and rights, so it moves to a licensing fit check for its engineering and support records.
The engineering firm needs a rights review first, because many project files are client deliverables. The landscaping company's priority is governance, since crews and office staff use several AI tools with no policy and no record of what has been uploaded.
Where SourceX fits in the readiness review#
SourceX fits the rights and quick-wins parts of the review. A fit check guided by the SourceX Enterprise Data Value Framework shows whether a company's archives could support a license, using metadata only, so no records leave the company during the assessment.
Companies that proceed follow the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, one supplier entity at a time. Each approved package is documented in a SourceX Evidence Packet that the board can review alongside the rest of the readiness work.
Frequently asked questions
Should every portfolio company get the same AI readiness review?
Use the same four areas and questions so results compare, but expect the depth to differ. A software company needs a closer look at code ownership and customer terms, while a contractor or distributor needs more attention on job or order history and on planned system retirements.
How is a readiness review different from an AI strategy review?
A strategy review asks where AI could help. A readiness review asks whether the records, rights and governance exist to act on those ideas. Running readiness first keeps strategy work grounded in what each company can actually do with its own records.
Where do legacy archives fit if the company no longer uses the system?
They are often the quickest licensing candidate, because they are complete, no longer changing and frequently tied to a subscription about to lapse. Preserve the export first, then check rights and whether the records link decisions to outcomes.
Who should own AI readiness at the portfolio company?
One executive, usually the COO, CFO or CTO depending on where the records sit, with the CEO as sponsor. The operating partner sets the review format and follows up, but the company owns its records and its decisions.
Does a readiness review require sharing records with the fund?
No. The review runs on descriptions: system names, date coverage, contract templates and policies. Customer and employee records stay at the company, which also limits the fund's exposure to sensitive material it has no reason to hold.
What should an operating partner report to the investment committee?
A one-page view per company: the four areas rated, the top gap, the next action and its owner. Add any quick wins completed, such as an archive preserved before a system retirement, and any licensing fit checks under way. Avoid forecasting value from data until a buyer has engaged.
Sources
- Analysys Mason predicts that fewer than 25% of portfolio companies' AI tools will fully succeed in 2026, citing inflated vendor promises, insufficient data readiness and weak operational integration. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.