In the IT space, the time between acquisitions is actually when a lot of the groundwork for future integrations gets done. I use that time to stay connected to what IT is implementing. That could be infrastructure upgrades, new systems, cloud migrations, or application rollouts. These changes are often tied directly to business goals like improving customer experience, reducing operational costs, or enabling growth.
Between deals, I focus on understanding how these initiatives are expected to support the business. That context is critical when it comes time to plan post-merger integration. Knowing what systems are being modernized, what architectures are being standardized, and what the current support models look like helps me build realistic integration plans when the next acquisition happens.
I also treat internal IT projects as a way to refine the M&A playbook. I’m documenting lessons learned, improving templates, and testing out approaches we might apply in an integration. So even when deal activity slows, I’m learning and updating my approach based on what IT is doing day-to-day.