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
A Survival Guide for Today’s Tech Leader
“The most dangerous place to be as a technology leader is surrounded by people who only agree with you.” The Clock Is Already Ticking If you are a CIO, the data on your tenure is sobering. The average CIO tenure now sits between 3 and 5 years, significantly shorter than CEOs and CFOs. The tenure is not just short, it is getting worse. According to the Nash Squared Digital Leadership Report, over 70% of CIOs have been in their positions for less than five years, with nearly 40% serving for two years or less. The Failure Rates Are Not Getting Better If tenure trends are troubling, the correlated project failure data is even more alarming. A Bain 2024 study puts failed business transformations at a staggering 88%. An MIT Project NANDA’s study found that after investing $30–40 billion in GenAI, 95% of businesses see little or no ROI. ERP implementations, often the centerpiece of a technology transformation, are especially brutal. Gartner estimates 70% of ERP projects fail to meet their objectives and 25% will fail catastrophically. The Echo Chamber Nobody Admits Exists Most major technology investment plans are built, reviewed, and approved by the same people who created them. Vendors have their own agenda. Consultancies have preferred platforms. Board members rarely have the technical depth to meaningfully challenge. No one in the room is truly incentivized to say “this will not work.” The Second Opinion Your Strategy Deserves Very few patients skip a second opinion before major surgery. The stakes are too high, and the consequences of a wrong call are too significant. When using a Generative AI Model to review content, which feedback personality do you really use? Do you want friendly or candid feedback? Why, then, do so many technology leaders approve $10M, $20M, or $50M transformation programs without a single independent voice in the room? An independent advisor does not replace your team or your consultants. They pressure-test the strategy, approach and plan. They identify the gaps your internal team is too close to see. They can benchmark your approach against what has actually worked at comparable organizations. Those independent advisors will provide you an unbiased read on feasibility before you stand up in front of your CEO or Board and stake your credibility on it. Most importantly, they are free to be honest with you. That isn’t something you can attain internally. The Conflict-of-Interest Problem with Traditional Advisors Not all advisors operate with equal independence. Large consultancies often have preferred vendor relationships that quietly shape their recommendations. Others avoid hard conversations simply to protect long-standing relationships. They know that delivering uncomfortable news risks the engagement and potentially vendor relationships. So the feedback gets softened, the risks get minimized, and the client believes they are receiving objective consultation when they are actually receiving managed guidance. A small boutique advisory firm is structurally better positioned to give you the truth. Fewer vendor entanglements, more accountability, and a business model built on your success rather than on hitting a vendor quota or preserving a relationship. Their reputation is the product, getting your recommendation right is the only incentive that matters. What Good Independent Advice Actually Looks Like You will know you have found the right advisor when they do several things most advisors do not: Give you a candid assessment of your current state versus where you think you are, including the uncomfortable parts. Red-team your strategy, arguing the case against your plan before your someone else does. Identify specific, actionable gaps, not a glossy report full of frameworks and 2×2 matrices. Benchmark your approach against real organizations, not vendor-sponsored research. Tell you when the timing is wrong, the data is not clean, the team is not ready, or the vendor is not the right fit, even when that is not what you want to hear. The relationship should be built on your success — not on the next engagement. The Cost of Not Getting a Second Opinion Once CIO credibility is lost, it is almost impossible to recover. Boards do not forgive a “we followed our vendor’s advice” excuse. Tenure data suggests you may only get one shot at this and if it goes sideways, the clock does not restart, it stops. The cost of an independent advisor is a rounding error against the risk of a failed implementation. The real question is not whether you can afford an independent voice, it is whether you will survive without one. The critical inquiry is not about the cost of securing an impartial perspective, but rather the risk of your continued viability without one. The Best Tech Leaders Do Not Go It Alone The best CIOs and CTOs are not the ones with all the answers. They are the ones who build the right conditions to find the right answers, which means surrounding themselves with people who are paid to be honest, not to be agreeable. Before you go into that board room, before you sign that software or implementation contract, before you stake your career on a plan you built inside a room full of people who need you to succeed, get an independent perspective. Echo chambers feel like alignment. Until the project fails, and they feel like something else entirely.
Cloud Repatriation: Why Companies Are Moving Workloads Back from the Cloud
From Cloud-First to Cloud-Smart For more than a decade, enterprise technology strategy was dominated by a simple directive: move to the cloud. Today, many organizations are discovering that cloud adoption and cloud optimization are not the same thing. As a result, a growing number are reevaluating where workloads should reside, leading to a trend commonly called cloud repatriation or cloud exit. Here are some of the most-cited recent statistics: That does not mean companies are abandoning the cloud entirely. Most are moving toward hybrid architectures, keeping some workloads in public cloud while bringing others back to private infrastructure or colocation facilities. Executive Takeaways Why are cloud migration rollbacks happening? Cost Overruns Many organizations discovered that: Several surveys cite cost optimization as the #1 driver. Well-known examples: In our experience, organizations often underestimate cloud operating costs because they evaluate migration costs but fail to model long term consumption patterns, storage growth, and data egress charges. Data Sovereignty and Compliance Regulated industries increasingly want tighter control over: This is particularly strong in Europe, finance, healthcare, and government sectors. Security and Operational Control Some organizations feel they lost visibility or governance in highly distributed cloud environments. Vendor Lock-in Concerns Companies worry about dependence on a single hyperscaler, with proprietary services, and the potential of escalating pricing. Hybrid and multicloud strategies are often attempts to reduce this dependency. Despite this, cloud spending is still growing. Public cloud spending continues to rise, SaaS adoption remains extremely high, and most enterprises are becoming “cloud-smart,” not anti-cloud. The current enterprise pattern is usually: In other words, the market has shifted from “move everything to the cloud”, to “place each workload where it economically and operationally fits best.” Cloud adoption for many workloads is still the right answer, but companies need to conduct detailed diligence on what gets moved and more importantly, how the variable spend model gets managed. At Lumerai Advisors, we use the Lumerai Cloud Placement Framework to help executives evaluate hybrid architecture and workload placement decisions. For private equity-backed organizations, workload placement decisions increasingly affect EBITDA performance, making cloud economics a business strategy issue rather than simply a technology decision. The Lumerai Cloud Placement Framework When evaluating cloud placement decisions, we assess workloads across four dimensions: Dimension Key Question Cost Predictability Can workload consumption be forecast accurately enough to benefit from cloud economics? Performance Requirements Does latency, throughput, or workload intensity justify dedicated infrastructure? Data Sensitivity Do regulatory, security, or data sovereignty requirements necessitate greater control? Business Agility Does the workload require speed, scalability, and flexibility to support growth and innovation? The goal is not to determine whether cloud is good or bad, but to determine which environment delivers the best economic and operational outcome for each workload. Cloud repatriation should not be viewed as a reversal of cloud strategy, but as the natural maturation of enterprise workload placement decisions. The future is not cloud-first or cloud-exit. The future is cloud-smart. The organizations that create the most value will be those that place every workload in the environment that delivers the best combination of performance, economics, security, and agility. Sources and References
The Machine That Changed Everything and What We Can Learn From It
The Difference Between Job Displacement and Job Elimination As artificial intelligence reshapes the modern workplace, leaders should remember an important lesson from technology history: automation often changes jobs more than it eliminates them. Executive Takeaways A Machine Arrives It was 1967, and a London bank called Barclays quietly installed a strange new device in its Enfield branch. Customers could insert a coded paper voucher, and the machine would dispense cash no teller required. The Automated Teller Machine had arrived. The reaction was predictable: The story was persuasive and easy to grasp, yet as time would reveal entirely wrong. The Numbers Tell a Different Story Between 1970 and 2010, the number of ATMs in the United States grew from essentially zero to well over 400,000. Over that same period, the number of bank tellers in America did not shrink. It grew from approximately 300,000 to over 550,000. How is that possible? The answer lies in a dynamic that technology critics routinely underestimate. When automation reduces the cost of a service, demand for that service expands, and that expanded demand requires more human labor. ATMs made it dramatically cheaper for banks to operate a branch. With lower overhead costs, banks opened more branches in more locations — particularly in smaller communities and suburbs that had never had convenient banking access before. Each branch still needed human staff. Not just tellers, but loan officers, financial advisors, relationship managers, and customer service representatives handling the complex transactions that machines couldn’t resolve. The ATM didn’t eliminate the teller. It changed what the teller did. “The ATM didn’t eliminate the teller. It changed what the teller did freeing humans to focus on judgment, relationships, and complexity.” Displacement vs. Elimination This is not to say automation is painless, individual tellers who lost their jobs to ATMs faced real hardship. Communities where bank branches consolidated experienced genuine disruption. The macro outcome, more jobs overall, offered little comfort to the person who lost a specific job in a specific town in a specific year. But the ATM story illustrates a distinction that is critical to understanding technological change, the difference between displacement and elimination. Jobs are displaced constantly by technology. Roles shift, skills become obsolete, industries restructure. What history consistently shows is that elimination the permanent net reduction in human employment is far rarer than the headlines suggest. The pattern repeats across sectors: Enter Artificial Intelligence Which brings us to the present moment. Artificial intelligence, particularly the large language models and generative tools that have captured global attention since 2022 is being greeted with the same mix of wonder and dread that met the ATM in 1967. The scale, however, feels different. While the ATM automated a narrow physical task (dispensing cash), AI can automate cognition itself: writing, analysis, coding, legal reasoning, medical diagnosis, creative work. If machines can think, the concern goes, what is left for humans to do? It is a serious question that deserves a serious answer and the ATM offers the beginning of one. What AI is demonstrably doing right now is automating the routine, predictable, high-volume cognitive tasks. These are the intellectual equivalents of dispensing cash. “What AI automates today are the routine cognitive tasks the intellectual equivalent of dispensing cash. What remains is judgment, creativity, and human connection.” What it is not doing, at least not yet, is replacing the judgment-intensive, relationship-dependent, contextually complex work that defines the most valuable human contributions in virtually every field. The Lumerai Expansion Effect Step Outcome Automation reduces cost Services become more affordable Lower cost increases demand More customers can access the service Increased demand expands human work New roles and opportunities emerge Human work shifts upward People focus on judgment, relationships, and complexity The ATM lesson also points to something AI optimists cite but skeptics tend to dismiss, the expansion effect. When a capability becomes cheaper and more accessible, demand for it and for everything adjacent to it tends to grow dramatically. Legal advice has historically been expensive enough that most individuals and small businesses simply go without it. If AI makes quality legal guidance affordable at scale, the number of people seeking legal counsel may multiply many times over. Lawyers may find their practices transformed, but the total demand for legal expertise could increase substantially rather than contract. The same logic applies to medicine, financial planning, software development, education, and virtually any knowledge-intensive field. AI acts as a force multiplier, enabling practitioners to serve more clients, take on more complex cases, and focus their energy where human insight genuinely differentiates outcomes. For executives, the implication is clear. The primary question is not which jobs AI will eliminate. It is how AI will reshape the economics of work within your industry. Organizations that focus solely on headcount reduction may capture short term savings. Organizations that redesign work around AI may create entirely new sources of growth. Warning Signs You’re Viewing AI Through the Wrong Lens Your AI business case is built entirely on labor reduction. You measure AI success only through cost savings. Workforce planning discussions focus on positions rather than capabilities. No one has defined how roles will evolve after AI deployment. Training budgets decrease while AI spending increases. What History Doesn’t Guarantee History is instructive, but it isn’t deterministic. There are meaningful differences between the ATM era and the AI era that warrant genuine concern. The Human Dividend The ATM story offers valuable insight into what AI displacement might look like. The bank teller who survived the ATM era was not the one who competed with the machine at its own game. It was the one who leaned into what machines could not replicate, customer service, trust, judgment, and the capacity to understand a customer’s full financial picture and respond with genuine, personalized guidance. The workers who will thrive in an AI-integrated economy are likely those who make a similar pivot. Not competing with AI on speed or information retrieval, but leveraging AI as a tool to free up time and cognitive bandwidth