The First 100 Days After Close
Why Technology Integration Determines Whether the Investment Thesis Survives. Lessons from post-acquisition technology integration, by Coy Wright, Lumerai Advisors Every acquisition has two closing dates. The one celebrated in the boardroom and the one that begins Monday morning when the systems must work together. Everyone gets excited about the diligence phase. AI-powered underwriting, data rooms parsed in hours instead of weeks, models that flag reserve risk before a human analyst finishes their coffee. It’s useful work, and it deserves the attention it gets. But diligence tells you what you’re buying. It doesn’t tell you what happens the Monday after close, when a field office in the Permian is still running production reports through a spreadsheet macro nobody has touched since 2019, the SCADA historian license responsible for operational production data is about to lapse, and the person who knows both systems just found out she’s “at risk” and is polishing her resume. The handoff, more than the diligence itself, is usually where deals actually lose value. For a PE-backed platform, this isn’t an IT problem sitting off to the side of the deal. It’s deal risk. The underwriting thesis assumed a certain pace of consolidation, a certain cost structure, a certain path to the next add-on. Every week the integration team spends firefighting instead of executing is a week that thesis quietly erodes, and it rarely shows up on a dashboard until it’s already expensive. Research on post-merger integration puts the failure rate at 70 to 90 percent of deals falling short of the value they were underwritten for, and the reasons named most often (incompatible systems, fragmented data, execution slower than planned) are exactly the ones that surface first in a technology stack. Executive Takeaways Technology integration is primarily an operational judgement challenge. Stabilization comes before modernization Institutional knowledge is often more valuable than documentation. AI should be deployed after data integrity is established, not before. The first 100 days determine whether deal value is realized or quietly eroded. Day one is about continuity, not transformation The instinct after close is to start modernizing immediately. New platform, new dashboards, new standards. Resist it for the first few weeks. The only job on day one is making sure nothing that currently works stops working: Production accounting keeps running Field data keeps flowing off the SCADA network Land and lease records stay accessible Payroll and AFE approvals don’t stall This means a real inventory before anything else, not the one sitting in the data room: every system actually touching production, land, HSE, and finance, who administers it, what the license and support terms are, and which of those systems have a single person who understands them well enough to keep them alive. That last category is the one that gets missed, and it’s the one that causes outages. A well-documented ERP is manageable. An undocumented historian configuration that lives in one engineer’s head is a ticking clock, especially if that engineer is uncertain about their future with the new owner. This lines up with what advisory firms like RSM have found studying post-merger integration broadly: the first 100 days is where quick, stabilizing wins need to happen, and where confusing that stabilization work with the long-term transformation plan is one of the more common ways integrations go sideways. Retention of institutional knowledge matters more than retention of headcount Every acquisition has some overlap to rationalize, and the pressure to move fast on org design is real. But the people who know why a particular well pad’s telemetry has been routed through a workaround for three years, or which spreadsheet is actually the source of truth versus which one is decorative, are not replaceable on a 100-day timeline. Identify them early, tell them directly why they matter, and keep them through at least one full reporting cycle before any staffing decisions touch their function. This is cheaper than the alternative, which is rebuilding tribal knowledge from scratch while also trying to close the books. Security comes before optimization A newly acquired asset is, for a window of time, the least defended part of the combined company: Credentials from the prior ownership are still active Vendor remote-access accounts haven’t been audited Nobody has yet mapped which of the acquired company’s systems can reach which of yours Access review and network segmentation belong in the first two weeks, not the first analysis of where AI could add value. This is unglamorous work and it rarely makes the integration deck, but it’s the difference between a clean 100 days and an incident report. Data architecture decisions get made whether you make them deliberately or not By day 60 or so, the temptation shifts from “keep it running” to “make it ours.” This is where the real architecture choice shows up: do you migrate the acquired company’s data into your existing platform, run both in parallel, or build a genuine integration layer between them. Each has a real cost. Migration is clean but risks losing context that lived in the old system’s structure, the tags, the naming conventions, the workarounds that encoded real operational knowledge even if they look messy. Parallel operation is fast but defers the actual integration problem and usually calcifies into permanent duplication if nobody forces the follow-through. An integration layer is the right long-term answer more often than either extreme, but it takes real engineering time that a 100-day plan rarely budgets for honestly. Underneath the plumbing question is a bigger one that most integration plans never name out loud: which system gets to be the source of judgment, not just the source of record, once the two organizations are running on shared data. Whoever’s platform wins that fight inherits the assumptions baked into it, good and bad. Get that decision right early and deliberately, and the rest of the technical integration follows a clear logic. Leave it to default to whichever system happened to be bigger at close, and you’ll spend the next two years discovering, one bad report at a