In this first blog of our technical due diligence series, we explain why IT and business process assessments are essential to due diligence and should be part of your standard due diligence protocols in any acquisition.
Part of a blog series.
Today's rapidly changing business environment creates opportunities for mergers and acquisitions. It's no secret that due diligence is a critical part of the merger and acquisition (M&A) process. Used to vet companies for potential investments, the due diligence process allows an organizational buyer to ensure the goals, culture and strategy of a future combined business closely align for their success.
Increasing company valuations and uncertainties to changes in corporate tax rates are driving a rise in mergers and acquisitions. Equipping the people in your organization with the right talent, capabilities and capacity is essential to a successful growth initiative through acquisitions.Why Should Business Process and IT Be Part of Due Diligence?
Due diligence, business process and IT protocols are as important as the review of general company information, company management and employees, financial statements, legal matters, products and services, and competitive analysis. A common misconception is that if a company is operating profitably today, they have the appropriate processes and IT systems in place to sustain the business and support future growth opportunities. Often, this isn't the case, and an early evaluation can help the acquiring company avoid deal-ending pitfalls or high unforeseen expenses. Understanding the relationship between key business practices and IT is crucial in evaluating whether merger discussions should move forward, as some process and system gaps may be too costly to achieve targeted returns. Further, understanding a target company's IT risk posture will uncover potential investments needed to shore up weak security defenses. Buyers should identify, evaluate and confirm business practices and the company's IT infrastructure early in the technical due diligence process to assess potential risk and value, if any, to the proposed business merger. Additionally, executives should think about a high-level integration plan to help lay out the transition to a new, combined company.Due Diligence Business Process and IT Evaluation Activities
Several evaluation activities can help ensure a successful merger. This includes an understanding of:- Business process and IT system compatibility
- Time available to complete the review
- Technology opportunities
- Merger data room availability
- Nature of business relationship (friendly or adversarial)
- Resources available (internal and external).
Compatibility Between Acquiring Company and Target
There are a few questions to ask yourself before merging.- Do manual or automated solutions support their critical business processes?
- Does the company use spreadsheets, or do they manage processes with something more automated?
- Do they manage their databases in-house or through a third party?
- What is the makeup, quality and accessibility of data?
- What are their cybersecurity and other IT risk vulnerabilities?
Conducting an In-Depth IT System Evaluation
By proactively identifying critical issues and risks, an acquiring company is in a better position to strategize and develop a thorough mitigation plan. In addition, an assessment's findings can often prove helpful in negotiations. A comprehensive technical due diligence assessment weighs the following questions:- How effective is the IT infrastructure to business architecture and operational performance?
- What documentation of current IT systems and hardware infrastructure exists?
- What are the licensing requirements?
- What do the IT governance protocols and documentation encompass?
- What cybersecurity protocols exist?
- Is there a regular testing protocol in place?
- Does a Business Continuity Plan exist?
- How comprehensive is it?
- Has it been tested?
- Is there a periodic testing process?
- Is there a dedicated IT capital budgeting process?
- How robust is the budget?
- Does a backlog exist on open capital projects? If so, what are the implications?
- What are data center and cloud environment implications?
- Is the data center located on-site, remotely, or both?
- What is the server structure?
- Is the company using virtual servers?
- How old is the IT hardware and software?
- Are there any defined replacement or upgrade plans?
- What backup, recovery and disaster recovery protocols exist
- When was the last time they were used or tested?
- Are there any propriety IT systems that require a carve-out of value during due diligence?
- Do they require specialized skills to support?
- What is the level of customization to IT systems?
- What is the frequency of IT software updates?
- What testing protocols exist?
- Is there documentation of test results and approvals?