The 100-day plan is where the LBO model meets the operating reality of the business. By Day 100, the sponsor has typically committed 15-25% of the Year 1 value creation budget, the new CEO or CFO has been onboarded (or replaced), and the lender covenant package is in monthly reporting cadence. Technology decisions made in this window — what data platform, which ERP, what identity provider, which KPIs get instrumented — compound for the entire hold period. Get them wrong, and the Year 3 add-on roll-up strategy collides with brittle integrations and Excel-bound finance teams. Get them right, and you fund 60-80% of the Year 1 EBITDA bridge from automation and visibility alone, before any commercial initiatives land.
This article walks through the tech-enabled 100-day plan used in mid-market and upper-middle-market deals (enterprise values typically $200M-$2B), where the sponsor has neither the bandwidth of a mega-fund operating group nor the simplicity of a small bolt-on. I'll cover the integration command center, the data and identity foundation, ERP and finance system decisions, KPI instrumentation, cybersecurity baseline, and the carve-out-specific issues that derail roughly a third of corporate divestitures.
Why 100 Days, and Why Technology Sits at the Center
The 100-day convention isn't arbitrary. It maps to one full month-end close cycle plus two more, which is the minimum needed to validate the diligence-era financial picture against actual post-close performance. It also aligns with the typical Transition Service Agreement (TSA) clock on carve-outs, where the seller provides IT, payroll, and back-office services for 6-18 months at cost-plus 5-10%, with step-up penalties of 15-25% after month six. Every day the buyer remains on seller infrastructure burns TSA fees and exposes the business to forced cutover risk.
Technology is the spine of the plan because nearly every value lever — pricing optimization, procurement consolidation, working capital release, sales productivity, shared services standup covered in Article 6 — depends on data that's clean, current, and accessible. A portfolio company running 14 disconnected QuickBooks instances and a homegrown CRM cannot execute a price increase by SKU-customer cohort. The first job of the 100-day plan is to make the business legible.
Day 0-30: Command Center, Data Foundation, and Identity
The first 30 days are about establishing control and visibility. Three workstreams run in parallel: an integration management office (IMO), a data foundation buildout, and identity and access consolidation. Each has hard deliverables tied to Day 30.
The IMO is typically run by an interim COO or a deployed operating partner, supported by a PMO platform — Smartsheet, Asana, or for larger deals, a dedicated instance of MA Software (Midaxo, DealRoom, or Devensoft). The IMO tracks 200-400 discrete tasks across functions, with a weekly steering committee chaired by the sponsor's operating partner. Status is reported on a five-color RAG scale tied to the value creation plan line items, so a delayed ERP cutover shows up directly as a $1.2M EBITDA risk to the lender model, not as an abstract IT issue.
The data foundation workstream stands up a lakehouse — typically Snowflake or Databricks — with Fivetran or Airbyte connectors pulling from the source systems within 10 business days. dbt models build the first version of a standardized chart of accounts, customer master, product master, and employee master. By Day 30, the sponsor should have automated daily refresh of revenue, gross margin, AR aging, cash position, headcount, and pipeline. This single source of truth replaces the Tuesday-morning Excel scramble that characterized the seller's reporting. The architecture choices here echo those discussed in the lakehouse approach for asset managers, scaled down to portfolio company needs.
Identity consolidation is the most underestimated Day 0-30 task. On a carve-out, the seller revokes corporate SSO access on Day 1 or within 30-90 days, and every SaaS application — Salesforce, NetSuite, Slack, Zendesk, GitHub — needs a new tenant or a re-pointed identity provider. The standard play is to stand up Okta or Microsoft Entra ID, federate it to a new domain, and migrate users in waves. On a non-carve-out, the equivalent task is consolidating 3-7 inherited identity stores into one, which typically reduces SaaS license spend 12-18% within 90 days by killing orphaned accounts.
Stand up IMO with weekly RAG-tracked workstreams. Deploy lakehouse (Snowflake/Databricks) with 8-12 source connectors. Consolidate identity into Okta or Entra ID. Baseline cybersecurity posture with Wiz or CrowdStrike. Lock TSA exit dates by service line.
Finalize ERP decision (NetSuite for sub-$500M revenue; SAP S/4HANA or Oracle Fusion above). Migrate first finance module (typically AP or GL). Launch FP&A platform (Mosaic, Pigment, or Planful). Instrument 15-25 operating KPIs with daily refresh. Begin contract repository build in Ironclad or Sirion.
First automated month-end close on new stack (target 5-business-day close from prior 10-15). CEO/CFO dashboard live with drill-through to transaction level. Two to four automation quick wins delivered (RPA for AR collections, AP three-way match, sales commission calc). 100-day report to LP advisory committee with EBITDA bridge actualized.
Day 31-60: ERP, FP&A, and the First Real Decisions
The second month forces commitments that are expensive to reverse. The ERP decision is the largest. For portfolio companies with revenue under $500M and reasonable process complexity, NetSuite is the default — implementation runs 4-7 months at $400K-$1.2M with partners like RSM, BDO Digital, or Terillium. Between $500M and $2B, the choice opens up to Microsoft Dynamics 365 F&O, Oracle Fusion Cloud, or SAP S/4HANA Cloud, with implementations of 9-18 months and budgets of $3M-$15M. Above $2B revenue or with heavy manufacturing complexity, SAP S/4HANA with a tier-one SI (Deloitte, Accenture, Capgemini) becomes typical.
FP&A platform selection runs in parallel and matters more for the lender and the LPs than the ERP. By Day 60, the CFO needs to produce a monthly forecast variance pack, a 13-week cash flow, and a covenant compliance certificate without spreadsheet heroics. Mosaic and Pigment dominate the mid-market for speed of deployment (6-10 weeks), with Planful, Vena, and OneStream picking up the more complex multi-entity situations. Anaplan remains the choice for sales planning and operational modeling at the larger end. A well-deployed FP&A platform cuts the monthly close-to-report cycle from 12-18 business days to 5-7.
Contract intelligence is a Day 31-60 task that punches above its weight. Deploying Ironclad, Sirion, Icertis, or for smaller portcos, LinkSquares or Evisort, against the inherited contract estate surfaces auto-renewal clauses, MFN provisions, change-of-control triggers, and indemnity caps that the diligence team almost certainly missed. In a typical mid-market deal, this exercise identifies $300K-$2M in annual procurement savings from rationalized vendor contracts and 3-8 customer contracts with change-of-control risk that need active management before Day 90.
| Dimension | Carve-Out from Corporate | Bolt-On to Platform | Platform Buyout (Sponsor-to-Sponsor or Founder) |
|---|---|---|---|
| TSA dependency | 6-18 months, $2M-$25M cost | None (absorbed into platform) | None or short founder transition |
| Identity migration scope | Full rebuild — every SaaS tenant | Merge into platform IdP | Re-federate to new sponsor IT |
| ERP decision urgency | High — TSA clock drives it | Migrate to platform ERP within 6-12 months | Evaluate vs. retain, decide by Day 60 |
| Data foundation lift | Heavy — extract from corporate DW | Moderate — extend platform lakehouse | Moderate — modernize existing stack |
| Cybersecurity baseline | Build from zero (seller controls leave with parent) | Inherit platform posture | Assess and uplift in 90 days |
| Typical IT integration cost (% of EV) | 3-7% | 0.5-1.5% | 1-3% |
Day 61-100: KPI Activation and Automation Quick Wins
By Day 60 the plumbing exists; by Day 100 it has to produce visible results. The CEO and CFO dashboards go live with 15-25 operating KPIs refreshed daily — for a B2B SaaS portco, that means NDR, gross retention, ARR by cohort, CAC payback, pipeline coverage, and sales cycle by segment; for an industrial business, OEE by line, on-time-in-full, scrap rate, days inventory, and quote-to-order velocity. The dashboards are built in Tableau, Power BI, Looker, or Sigma against the lakehouse, with row-level drill-through to source transactions so the CFO can defend every number to the audit committee.
Automation quick wins delivered by Day 100 typically fall into four buckets. AR collections automation using HighRadius, Versapay, or Billtrust cuts DSO by 6-12 days and recovers 0.5-1.5% of revenue in working capital. AP automation through Tipalti, Stampli, or Bill.com eliminates 60-75% of manual three-way match effort and captures 1-2% in early payment discounts the prior team was missing. Sales commission automation via CaptivateIQ or Spiff resolves the dispute backlog and frees 10-20% of finance team capacity. RPA bots in UiPath or Power Automate handle the long tail of report generation and data reconciliation between systems that won't be retired until Year 2.
Cybersecurity: The Non-Negotiable Day-1 Baseline
Cyber posture during integration is uniquely exposed because identity controls are in flux, contractor counts spike, and TSA-period network connections create lateral movement paths. The 100-day cyber baseline has six non-negotiables: MFA enforced on 100% of admin accounts by Day 14 and all users by Day 45; EDR (CrowdStrike, SentinelOne, or Microsoft Defender for Endpoint) deployed on every endpoint by Day 30; cloud posture management (Wiz, Orca, or Prisma Cloud) scanning every AWS/Azure/GCP account by Day 30; email security (Abnormal, Proofpoint) live by Day 21; backup immutability validated by Day 60; and a tabletop ransomware exercise completed by Day 90.
Cyber insurance is the forcing function. Renewal underwriting questionnaires from Beazley, Chubb, AIG, and the Lloyd's syndicates now require evidence of all six controls, with premium step-ups of 40-150% or outright declination for portcos that can't demonstrate them. Sponsors who skip the Day-1 baseline get hit at the next renewal — and the cross-portfolio approach to this problem is the subject of Article 11.
Carve-Out Specifics: The TSA Exit Plan
Roughly 30% of mid-market PE deals are corporate divestitures, and these carry an integration burden 3-5x heavier than founder-led platform buyouts. The TSA defines what services the seller provides post-close — typically IT infrastructure, email, payroll, benefits, finance system access, procurement systems, and sometimes manufacturing execution systems. Each service line has its own exit date, exit cost, and dependency chain.
The carve-out 100-day plan adds a TSA exit workstream that maps each service to a target replacement (build, buy, or absorb into an existing platform portco system), assigns an exit owner, and tracks burn rate against the TSA fee schedule. Smart sponsors negotiate TSA fee step-ups at 6, 9, and 12 months specifically to create exit urgency for their own teams. A typical mid-market carve-out TSA carries $300K-$2M per month in fees; every month of delay past Day 180 is a direct EBITDA hit.
Talent, Org Design, and the Fractional CTO Question
Most mid-market portfolio companies don't have a CIO or CTO worth the title at acquisition. The Day-1 IT director typically reports to the CFO, manages a help desk and a couple of SaaS admins, and has never run a transformation. The 100-day plan must answer whether to upgrade this role to a full-time CIO ($350K-$600K loaded for mid-market), deploy a fractional CTO from a firm like Bridgepoint Consulting, Pillar IT, or a sponsor-affiliated operating partner network (typically $40K-$80K/month for 2-3 days/week), or borrow capability from a shared services center across the portfolio.
The default for sub-$500M revenue portcos is the fractional model for the first 6-9 months, transitioning to a full-time hire once the architecture is set and the role is about execution and team-building rather than design. This pattern, and the broader talent operating model, is covered in Article 12.
By Day 100, you're not measured on what you've built. You're measured on whether the next 1,200 days have a credible plan and the data to steer it.
— Senior partner, upper-middle-market buyout fund
What the 100-Day Report to the LP Advisory Committee Should Contain
The 100-day report is increasingly a formal deliverable, especially for funds that committed to operational value creation in their PPM. It should include: the actualized EBITDA bridge against the underwriting model, with variance explanations by line; the integration status report (RAG by workstream); a refreshed value creation plan with quarterly milestones through year 3; a technology roadmap showing the architecture target state and phased investment plan ($X spend, $Y EBITDA impact, by quarter); a cyber posture attestation; and a talent plan with critical role status.
LPs increasingly probe these reports. The 2024-2025 ILPA reporting template updates and the SEC's private fund adviser rules (parts of which survived the Fifth Circuit vacatur and were re-proposed in modified form in late 2025) push sponsors toward more granular disclosure on value creation execution. A 100-day plan that produces a defensible, data-backed report isn't just an operating asset — it's a fundraising asset for Fund N+1.
Common Failure Modes
Five patterns recur across deals that miss Year 1. First, ERP-first thinking: sponsors who decide to replace the ERP in Month 2 burn the entire 100-day window on requirements gathering and have nothing else to show. The lakehouse-first sequence — get visibility before changing systems of record — outperforms in every benchmark I've seen. Second, identity deferral: leaving SSO consolidation until Month 6 means every other integration is harder, slower, and less secure. Third, TSA optimism: assuming the seller will be flexible on exit dates is a billing-clock mistake measured in seven figures. Fourth, dashboard theater: building executive dashboards on top of dirty data produces precisely calibrated wrong numbers that erode CFO credibility. Fifth, cyber as a Year 2 problem: this assumption survives until the first incident or insurance renewal, whichever comes first.
The discipline of the 100-day plan is sequencing: foundation before systems, visibility before automation, identity before applications, baseline before optimization. Sponsors who hold that sequence — and resist the operating partner's natural urge to start with the most visible value lever — consistently produce the EBITDA bridges they underwrote, and set up the add-on roll-up strategy described in Article 7 to compound on a platform that can actually absorb acquisitions.