A proactive, deliberate approach to technology is valuable for investors and portfolio companies of all sizes, but especially important for lower-middle- and middle-market enterprises with limited corporate-level resources. In scenarios where a lean back-office is an inevitable reality, a thoughtful technology integration gameplan can make the difference between achieving both leverage and scale rather than getting routinely taxed by tactical data and system issues. Your technology and IT integration planning should begin early, ideally during diligence.
Without an early, intentional approach to post-close IT integration, investors risk an administrative tax — the costs of manual work to get the management team the data it needs to operate efficiently and identify improvement initiatives. When IT isn’t addressed thoughtfully upfront, management teams face persistent pain points and constraints on their ability to lead and to meet investor mandates. Examples include manual, error-prone financial close processes involving extensive Excel-based reconciliations or quarterly board reporting that rely on a “workbook data warehouse,” bogging sales teams with data requests for information that should otherwise be readily available.
Additionally, when companies with loosely coupled platforms are taken to market to sell, investors are finding they’re not getting anticipated returns. Often, feedback from prospective buyers reveals that they assumed the target’s technology integration was complete.
Other sell-side risks include challenges pulling required data together for reporting, normalizing critical data, and creating a sell-side data cube to aggregate data for analysis on multiple dimensions. Sellers may have missed opportunities to realize synergies. And technical debt — the cost to bring an acquisition’s technology in line with expected performance and maintain it there — impacts the capital expenditure needs for buyers, which in turn can impact price.
Technology integration planning starts during due diligence
Avoiding these risks requires a digital blueprint, and developing the technology integration blueprint for your acquisition should start well before your transaction closes, ideally during the diligence phase.
Integration planning won’t look the same for all transactions, and diligence should be tailored based on the technology-related specifics of your target and the deal. Is there custom or homegrown software in the mix? Then you’ll want to include a code review to scan for licensing risks, vulnerabilities in the code, and gaps to best practice.
Is there personal health information in play or other regulatory requirements? In these cases, you’ll want a deeper dive to assess data controls and ensure clear data privacy measures are in place.
IT integration planning blueprint considerations
Some of the critical IT aspects to address in your tech integration planning blueprint include:
- How IT is managed — outsourced (fully or project-based) vs. in-house.
- Primary ERP and accounting systems.
- Email and other communications and calendar applications.
- Consolidated file storage and shared access, including cloud usage and access.
- Consistent configuration of cybersecurity, IT, and data security tools and controls.
- Standardization of IT infrastructure.
- Management and control capabilities.
- How IT supports your operating model, performance improvement initiatives, and value creation plans.
Additionally, you’ll want to consider the relationship between technology and other strategic initiatives, such as increasing the timeliness and quality of financial reporting, improving pipeline visibility, or missed opportunities to realize synergies. Often, the success of seemingly business-oriented goals is predicated on a corresponding IT system project like a CRM implementation or accounting system upgrade. Always consider how your strategic efforts can be advanced more effectively when technology initiatives are well aligned.