Bring CIOs Into the Deal Before Signing, Not After

Bring CIOs Into the Deal Before Signing, Not After

Sometimes a deal adds up, but a business ends up with incompatible systems, hidden costs and features it can’t tap. As technology leaders, CIOs confront the humongous challenge of post-merger in not just tying together two technology stacks, but also it’s working with the business to turn the deal into value.

Top CIOs deliberated on this subject at a panel discussion themed ‘Architecting the Modern Enterprise: Boardroom Strategies for M&A, Ecosystem Alliances, and Accelerated Growth.’ The session was a part of the CIO Retreat event organized by ObserveNow in Gurgaon.

Start with Business Outcomes

Speaking at the session, Rajiv Mishra, CIO, Hindustan Times, recalled being called into a board discussion during the pandemic, only to discover that an acquisition was already being considered without a technology assessment.

“I was not even aware that we were acquiring that company,” he said. Expectedly, before proceeding, he sought time to examine its technology stack, infrastructure, spending and team capabilities.

The experience illustrated the limitations of bringing technology leaders into a transaction late. By then, assumptions about cost, compatibility and execution may already have shaped the business case.

Priya Dar, Head-IT, Valvoline Cummins, described an earlier merger in which IT received a fixed-asset register containing approximately 80 lakh lines and instructions to combine the entities.

Today, she said, the opening questions should be different. “What are the KPIs? What is it that we want to accomplish? What are the timelines, and how much are we going to spend?”

Platform choices matter, but they should follow clarity on the outcomes the transaction is intended to achieve.

Look Beyond the Balance Sheet

Some of the most consequential technology dependencies are barely visible in formal asset records.

Annapurna Kuchibhatla, CTO, Bajaj Electronics, pointed to spreadsheets, cloud subscriptions, open-source tools and internally developed applications that may operate outside central IT’s knowledge. Acquiring these environments without examining how they work can create unexpected dependence on particular teams or individuals.

She recalled an acquisition that included a substantial software platform without first establishing whether it matched the buyer’s requirements. It subsequently became a “white elephant.”

Atul Govil, Chief Transformation Officer & Head (SAP & IT) – Corporate at India Glycols, highlighted another hidden exposure: “tribal knowledge”, where only two or three people understand an application critical to the business.

Sustaining that group for 12-18 months and even possibly having their knowledge documented, or starting the re-build of the application, must be included in the cost of the transaction and not an operational problem to overcome downstream.

Translate the Risks of Integration into the Bottom Line

The board needs more than a description of ageing technology stacks or moribund applications. The board needs to understand the impact on capital deployment, risks and returns.

Govil urged CIOs to explain the cost of securing legacy systems, retaining essential employees and delaying integration.

“You have to speak in the language which they want to understand,” he said.

This is particularly important when an acquisition’s financial rationale depends on synergies. Shared platforms and consolidated processes cannot generate immediate savings if the underlying systems cannot be integrated.

In cases where those benefits will take a year or two longer to materialize, CIOs should be up-front about this delay and its associated costs before those benefits turn into commitments.

Make Controls Non-Negotiable

Gyan Pandey, CDIO, Polycab, listed cybersecurity deficiencies, data ownership issues, residencies, compliance and complexity of integration as reasons to challenge a suggested technology configuration. Similar to entry, exit considerations: how hard is it to leave a platform or partnership?

But to protect the business, not all corporate systems need to be installed all at once.

“When you start forcing everything to be implemented at the same time, it is a sheer disaster,” he said. His methodology isolates critical controls –financial validation, audit trail, cyber security and role-based access –from the incremental processes.

The sales office might require the customer interface to be implemented first; the manufacturing process could require that operational processes are available first. Training, local champions and reviews at regular intervals can help that transition to be practical.

Preserve Continuity and Local Relevance

Mishra advocated phased modernization in publishing, where daily operations cannot pause for a technology transition. Legacy systems must remain secure and functional while newer capabilities are introduced and tested.

Dar offered a parallel lesson from a joint venture involving Cummins and Valvoline: collaboration should enable learning without forcing uniformity.

“We take the good bits from Cummins. We take the good bits from Valvoline, but we make our decisions that work for India,” she said.

That requires transparency, regular engagement and recognition that global practices may need adaptation to local commercial realities.

Integrate Selectively

The panel’s closing message was that integration should serve the business, not become an end in itself.

Govil cautioned against compromising the acquiring company’s core systems while focusing on the new enterprise while Annapurna suggested that some acquired capabilities may suit only selected divisions.

Dar captured the leadership imperative: remain open to learning, but be prepared to challenge unnecessary consolidation. “Not everything has to be merged in a merger and acquisition,” she said.

For CIOs, the mandate is to help enterprises integrate deliberately—preserving valuable differences while making the costs, risks and benefits of change clear.

Author

Yashvendra Singh

Yashvendra is Editor at CIONow.in, with over two decades of experience covering enterprise technology, business, and the CIO community.

Chat with CIONow.in