M&A Due Diligence
What PE Firms Get Wrong About Technology Integration After a Deal
Lauren B. Jones
CEO & Founder, Leap Advisory Partners
Lauren B. Jones
The deal closes. The champagne gets poured. The operating team starts the 100-day plan. And somewhere between the celebration and the execution, technology integration gets pushed to month four because "the team needs to focus on revenue first."
I see this pattern at least six times a year. The technology integration gets deprioritized because it feels like an IT project, not a business priority. Meanwhile, the acquired company is running on systems that do not talk to the platform company's systems, data is siloed, and operational efficiency, the very thing the deal was supposed to create, is stalled because the technology layer is still pre-acquisition.
By the time someone decides technology integration cannot wait any longer, the easy window has closed. People have settled into their existing workflows. Resistance to change has hardened. And the cost of integration has increased because now you are disrupting established post-close routines instead of building new ones.
The first 100 days are the most important window for technology integration because the organization is primed for change, and that openness does not last. The first 100 days after close are the most important for technology integration, and they are also the most crowded. The operating team is focused on financial reporting, leadership transitions, customer retention, and quick revenue wins. Technology feels like a "later" problem because it is complex, expensive, and unglamorous.
But the first 100 days are also when people expect change. The acquired company's employees know things will be different. Clients are prepared for some transition. The culture is primed for new ways of working. That window of openness does not stay open forever. By month six, the status quo has reasserted itself, and every change becomes an uphill battle.
The PE firms that get this right treat technology integration as a day-one workstream, not a phase-two afterthought. They do not need to complete the integration in 100 days, but they need to start it, communicate the plan, and build the timeline that gives the operating team confidence.
There is no single right way to integrate technology after an acquisition. The right approach depends on the relative size and maturity of the two technology stacks, the strategic rationale for the deal, and the pace of value creation the fund requires.
Strategy 1: Absorb
The acquired company migrates fully onto the platform company's technology stack. Their ATS, CRM, payroll, and supporting tools are replaced with the platform's systems.
Use this when: The platform company has a mature, scalable technology stack and the acquired company's systems are inferior. The deal thesis is operational efficiency through standardization. The acquired company is relatively small.
The risk: Absorption is disruptive to the acquired company's team. Their workflows change entirely. Their data has to be migrated. Their learned efficiencies in the old system are lost. If absorption is rushed, you will face adoption problems and productivity dips that can last 3-6 months.
Timeline: 4-8 months for a staffing company with 50-200 employees, depending on data complexity and integration requirements.
Strategy 2: Best-of-Breed
Evaluate both companies' technology stacks and pick the best tools from each. The platform company might keep its ATS but adopt the acquired company's reporting tools. Or both companies might move to a third system that neither was using.
Use this when: Both companies have strong technology in different areas. The deal thesis is creating a combined entity that is better than either standalone. There is time and budget for a thoughtful evaluation.
The risk: Best-of-breed is the most complex strategy. It requires detailed evaluation, custom integration work, and a longer timeline. It also creates political dynamics: nobody likes being told their system lost the evaluation.
Timeline: 6-12 months, often with a phased approach where individual systems migrate on different schedules.
Strategy 3: Greenfield
Both companies move to an entirely new technology stack. This is rare but sometimes the right answer, particularly when both existing stacks have significant technical debt or when the combined entity has fundamentally different needs than either standalone company.
Use this when: Both existing stacks are outdated. The combined entity's scale requires capabilities neither system can provide. The fund is willing to invest in a long-term technology foundation rather than optimize what exists.
The risk: Greenfield is the most expensive and time-consuming approach. It disrupts both organizations simultaneously. It requires strong project management and change leadership.
Timeline: 9-18 months, and it is the approach most likely to exceed both timeline and budget if not managed rigorously.
Technology integration is fundamentally a people project with a technology component, not the other way around. The technical work of migrating data, configuring systems, and building integrations is well understood. The human work of getting two organizations to operate on shared technology is where integration projects succeed or fail.
Shadow IT will emerge. When people do not trust the new system, they build workarounds. Spreadsheets, personal databases, offline trackers. Shadow IT is not malicious. It is a rational response to a system that does not meet someone's needs. But it fragments your data, creates compliance risks, and undermines the integration's value. Address shadow IT by understanding what needs the new system is not meeting, not by issuing mandates.
Key-person risk is amplified during integration. The IT manager who maintained all the integrations at the acquired company is now being asked to support an integration that makes their job different. The top recruiter who built a personal workflow in the old ATS is being told to start over. These people may leave. Plan for it. Document their knowledge before the integration starts, not after they give notice.
Cultural mismatches between tech teams. The platform company's IT team might be centralized and process-driven. The acquired company's "IT team" might be one person who does everything and answers to nobody. Integrating these teams requires more than a new org chart. It requires aligning expectations about process, documentation, response times, and decision-making authority.
Use a 30/60/90/180 framework. Each milestone should have specific, measurable deliverables.
Day 30: Assessment Complete
Map both companies' complete technology stacks. Document all systems, integrations, data flows, contracts, and key personnel. Identify the integration strategy (absorb, best-of-breed, or greenfield). Quantify the integration budget with a 20% contingency.
Deliverables: Technology inventory, integration strategy recommendation, budget estimate, risk register.
Day 60: Architecture Designed
Define the target technology architecture for the combined entity. Map the data migration path. Design the integration architecture (which systems talk to which, through what mechanisms). Identify vendor conversations that need to happen (contract renegotiations, integration support requests, new procurement).
Deliverables: Target architecture diagram, data migration plan, integration design documents, vendor engagement plan.
Day 90: Migration Started
Begin the first phase of data migration (typically the least complex system). Start system configuration for the target state. Launch the change management communication plan. Train the first wave of users.
Deliverables: Phase 1 migration complete, configuration in progress, training materials developed, communication plan active.
Day 180: Core Integration Complete
Primary systems integrated. Data flowing between systems. Core team trained and using the target-state tools. Reporting operational. Remaining phases (secondary systems, optimization, cleanup) scheduled with clear timelines.
Deliverables: Core systems live, adoption metrics tracked, integration punch list for remaining items, optimization roadmap.
This framework is flexible. Some integrations can move faster. Complex ones take longer. But having a structured timeline with milestones prevents the drift that turns a six-month project into an eighteen-month one.
"Systems are live" is not a success metric. Track these metrics instead to understand whether the integration is actually delivering value.
Adoption metrics. What percentage of users are actively using the integrated systems? Not just logging in, but completing core workflows. Set an adoption target (typically 85%+ within 60 days of go-live) and track it weekly. Adoption below target is a signal that training, configuration, or change management needs attention.
Productivity recovery. Every technology migration causes a temporary productivity dip. Recruiters are slower in a new system. Account managers take longer to run reports. Operations teams spend more time on manual tasks during the transition. Measure how long the productivity dip lasts and when key metrics (placements per recruiter, time-to-fill, client response time) return to pre-integration levels. If productivity has not recovered within 90 days, something in the integration needs attention.
Data quality benchmarks. Is the data in the integrated system accurate, complete, and accessible? Run monthly data quality audits. Compare data completeness rates, duplicate rates, and reporting accuracy against pre-integration baselines. If data quality degrades during integration, the reporting and analytics that the combined entity depends on will be unreliable.
User satisfaction. Run a brief survey at 30, 60, and 90 days post-go-live. Ask simple questions: Can you complete your daily work in the new system? What is harder now than before? What is easier? What is missing? User satisfaction data reveals problems that adoption metrics miss, because someone can use a system every day and still hate it.
If your fund acquires staffing companies regularly, every integration teaches you something. Capture those lessons into a reusable playbook.
The playbook should include: standardized assessment templates, decision frameworks for choosing an integration strategy, timeline templates with task-level detail, communication plan templates, training program outlines, risk registers from previous integrations, vendor contact information and negotiation notes, and a lessons-learned database from each completed integration.
The playbook is not a rigid script. Every deal is different. But it is a starting point that prevents your operating team from reinventing the wheel on every acquisition. The fund that has done ten integrations should execute the eleventh faster and cheaper than the first, not because the complexity decreased, but because the team's capability increased.
The best PE firms I work with treat technology integration as a competitive advantage, not a cost center. They invest in it early, measure it rigorously, and learn from every deal. The firms that treat it as an afterthought keep paying the same tuition on every acquisition.
The timeline depends on the strategy. Absorb (migrating to the platform company's stack) takes 4-8 months. Best-of-Breed (selecting the best tools from both entities) takes 6-12 months. Greenfield (moving both to new systems) takes 9-18 months. Use a 30/60/90/180 day framework with specific deliverables at each milestone to prevent drift.
The three strategies are Absorb (acquired company migrates to the platform company's stack, best for standardization), Best-of-Breed (evaluate both stacks and keep the best tools from each, best when both have strengths), and Greenfield (both move to entirely new systems, best when both stacks are outdated). The right choice depends on relative technology maturity, deal thesis, and available timeline.
PE firms deprioritize technology integration because it feels like an IT project rather than a business priority, and the first 100 days are crowded with financial reporting, leadership transitions, and revenue initiatives. This delay is a mistake because the first 100 days are also when the acquired team is most open to change. By month six, the status quo has hardened and every change becomes significantly harder and more expensive.
Track four categories of metrics: adoption (percentage of users completing core workflows, targeting 85%+ within 60 days), productivity recovery (how long until key metrics like placements per recruiter return to pre-integration levels), data quality benchmarks (monthly audits comparing completeness and accuracy against baselines), and user satisfaction (30/60/90 day surveys asking what is harder, easier, and missing in the new system).
Planning a post-close technology integration? Download the M&A Integration Planning Checklist. It covers the 30/60/90/180 framework, assessment templates, and decision criteria for choosing your integration strategy.
Download the M&A Integration Planning Checklist
Lauren B. Jones is the CEO and founder of Leap Advisory Partners, with 28 years of experience in staffing technology. She helps staffing agencies, PE firms, and software companies build technology that actually works.
