The 100-Day AI Plan: A Private Equity Operating Partner's Playbook for the Value Creation Plan

The standard 100-Day Plan template covers leadership alignment, financial reporting, commercial diagnostic, and operating model review. AI is usually an appendix. That position no longer holds. According to BCG's 2025 AI in the Workplace research, the gap between top-quartile AI deployers and the rest is widening by roughly fifteen points of EBITDA contribution per year. Treating an AI value creation plan as an appendix to the VCP costs you the gap.

This piece lays out the 100-day AI plan we run with operating partners post-close. Five workstreams, named owners, board-ready outputs by day 100. The goal is not to deploy AI for its own sake. The goal is to lock in a scored baseline, identify the top three EBITDA-impacting use cases, and write them into the VCP as named workstreams with defensible targets.

Why the First 100 Days Determine the AI Trajectory

The 100-Day window is the only period in the hold cycle when the operating partner has unambiguous mandate, full leadership attention, and no quarterly results pressure yet. Decisions made in this window compound. Decisions deferred to month four routinely slip to month nine and then to next year's VCP refresh.

For AI specifically, three things have to happen in this window or they tend not to happen at all.

First, an honest AI inventory and governance baseline. Without this, the operating partner cannot answer the LP question, the board AI risk question, or the simple internal question of what AI is actually running today.

Second, identification of the top three EBITDA-impacting use cases, sized in dollar terms. Without this, AI work becomes a series of pilots that never reach production.

Third, a named owner inside the PortCo. Without this, AI becomes a shared responsibility, which means nobody owns it.

The Five Workstreams

Workstream 1: AI Inventory and Risk Register (Days 1 to 14)

Owner: PortCo CIO or VP Engineering. Operating Partner reviews.

The first two weeks produce a single artifact: a written inventory of every AI system in production, including embedded AI inside vendor tools, plus a one-line risk rating per system.

The deliverable is a one-page table with three columns: system, business function, risk tier. Risk tier maps to the EU AI Act tiers if the company sells into the EU and to the NIST AI RMF function categories if it does not.

The point is not perfection. The point is to have a document the board can read in five minutes and that the LP relations team can reference at the next AGM. Most PortCos do not have this. Producing it inside two weeks is a meaningful early win.

Workstream 2: Revenue Architecture Audit and PortCo Review (Days 14 to 35)

Owner: Operating Partner. PortCo executive team participates.

A scored assessment across five dimensions: Data Readiness, Leadership Alignment, Tech Infrastructure, Process Automation Maturity, Governance Readiness. Each dimension scored one to four. The output is a single comparable score per PortCo and a heatmap that tells the operating committee where to invest.

The honest version of this assessment is run by an outside party, not by management. Management consistently over-rates Leadership Alignment and Process Automation Maturity. The outside read is what makes the score defensible across the portfolio.

The Sophizo Revenue Architecture Audit includes an Operating Partner persona track that runs in ten minutes and gives the operating partner a self-scored baseline before the formal assessment.

Workstream 3: Three EBITDA-Impacting Use Cases (Days 21 to 50)

Owner: PortCo CEO with Operating Partner as challenger.

The deliverable is three named use cases, each sized in dollar terms with low, base, and high cases. We screen across four buckets: revenue lift, cost reduction, margin expansion, exit-readiness premium.

The screening discipline that matters: every candidate use case has to pass three filters before it goes on the list.

First filter: can the impact be evidenced in a Quality of Earnings workbook at exit? If the savings cannot survive a QoE review, they do not count for valuation, which means they do not count for the VCP.

Second filter: can the work be substantively delivered inside the remaining hold period? An eighteen-month build inside a year-four PortCo is not viable. The same build inside a year-one PortCo is.

Third filter: does the company have the data and the leadership to execute it? A use case that requires data the company does not yet collect is a year-two use case, not a year-one use case.

Three use cases is the right number. One is fragile. Two is a coin flip. Five is unfocused.

Workstream 4: Governance Baseline and AI Policy (Days 35 to 70)

Owner: PortCo General Counsel with PortCo CIO as co-owner.

The deliverable is a written AI use policy, an AI vendor assessment framework, and a quarterly review cadence on the board calendar.

The AI use policy is short. It defines what AI tools employees may use, what data may not be shared with external AI systems, what review is required for AI-generated customer-facing content, and what escalation path applies to AI incidents. Two pages is the right length. Four pages is too long for adoption.

The AI vendor assessment framework is a one-page checklist any vendor signing a new AI tool has to complete. It covers data residency, training data use, model lineage, security certifications, and termination data return.

The board review cadence is a recurring fifteen-minute slot on the quarterly board agenda. AI inventory delta, governance incidents, top use case progress. Standing item, not ad hoc.

This workstream is what the LPs will ask about next. Doing it inside the 100-Day Plan converts a reactive position into a proactive one.

Workstream 5: First Use Case Into Production (Days 70 to 100)

Owner: PortCo functional leader closest to the use case.

The 100-Day Plan ends with one of the three use cases in production, not in pilot. The discipline matters. Pilots are how AI programs die in PE portfolios. Production is what compounds.

The choice of which use case to deploy first follows a simple rule: pick the one with the highest ratio of EBITDA impact to integration complexity. That is almost never the most exciting use case. It is usually a workflow automation inside a single function where the data is already clean and the change management surface is small.

A representative first deployment in a B2B SaaS PortCo: a stalled-deal recovery agent that monitors the CRM, drafts re-engagement messages for rep review, logs activity, and reports weekly pipeline impact. Four to six weeks to production. Measurable rep time recovered inside thirty days. Defensible pipeline lift inside sixty days.

What the Board Sees at Day 100

By day 100, the operating partner walks into the board meeting with five artifacts.

One: an AI inventory and risk register. Two: a scored Revenue Architecture Audit and a PortCo review with a portfolio heatmap. Three: three sized use cases written into the VCP with named owners and quarterly milestones. Four: a written AI policy and vendor assessment framework on the board calendar. Five: one use case live in production with a defensible early-results read.

That is not an AI strategy. That is an AI operating system, sized to fit inside the 100-Day Plan.

Actionable Takeaways for Next Week

1. Pick one PortCo you closed in the last six months. Score it against the five workstreams. The gaps are the year-two backlog, and they will be twice as expensive to close then as they would have been in the original 100-Day window.

2. Put AI governance on the next board agenda. Fifteen minutes, standing item. The first meeting is uncomfortable. The fourth meeting is routine.

3. Run the Operating Partner audit on yourself. The Sophizo Revenue Architecture Audit takes ten minutes and gives you a baseline you can compare across the portfolio.

4. Name an AI owner inside each PortCo. Not a committee. A person.

5. Decide on a vendor assessment framework template. Any one. Adoption matters more than which one. Stop letting PortCos sign AI vendor contracts without a framework.

Where Sophizo Fits

We embed as the fractional AI capability inside a PortCo for the first 100 days, then continue as a retainer or hand off to an internal hire. Output is the five artifacts above, sized to the PortCo and defensible to the board. The Private Equity page outlines per-PortCo and per-fund engagement shapes.

For the broader value creation context, the BCG Build for the Future research and FTI Consulting's PE practice both publish useful primary data on AI-related EBITDA outcomes in PE-backed companies.