Post-Merger Integration Advisory in India

The pattern

The deal closes and within a fortnight an integration PMO exists. Workstreams are named, milestones are set, reporting starts. The technical work is usually competent and the first hundred days land close to plan. Eighteen months on, the value case is behind, much of the acquired leadership team has gone, and two organisations are still running two ways of working under one logo.

The review that follows examines execution, because execution is what was tracked. The factors that decided the outcome were never on a workstream list. Leadership alignment, cultural integration and behavioural adoption sit between functions with no natural owner, so they wait until the friction is visible. By then the people you most needed to keep have made their decisions.

01A day-one plan that is complete on systems and reporting lines and silent on how decisions will get made in week three.
02Two executive teams publicly aligned on the rationale and privately holding different views on which operating model wins.
03A value case whose benefits depend on thousands of people behaving differently, and a plan that names none of them.
04Every Artificial Intelligence (AI) pilot reported as a success, and nothing in the profit and loss has moved.

THE GLOBAL PICTURE

67%

of senior leaders reported at least one underperforming transformation in the previous five years, in research covering 935 senior leaders and direct reports and 1,127 workforce members across 23 countries and 16 sectors.

EY with University of Oxford Saïd Business School, transformation research, 2022 fieldwork

2.6x

the association between scoring above average on six leadership and human factors and reported transformation success, moving the success rate from 28 percent to 73 percent in the model. It is produced by regression on that same sample and is not a measured causal effect.

EY with University of Oxford Saïd Business School, transformation research, 2022 fieldwork

96%

of transformation programmes hit a turning point at which the programme is at risk, in a later wave of the same collaboration covering 846 senior leaders and 840 workforce members in 23 countries and 16 sectors, all at companies above US$1bn revenue, surveyed in June and July 2023. Leaders who met those turning points with a human-centred approach were reported as up to twelve times more likely to succeed.

EY and University of Oxford Saïd Business School, transformation study announcement, 2024

All three figures come from one research programme, run by EY with the University of Oxford's Saïd Business School, and all three are self-reported by the leaders and employees who lived through these programmes rather than audited against the value cases. The move from 28 percent to 73 percent is an association drawn by regression on that sample, not a measured causal effect; programmes that score well on leadership and human factors also tend to be better run in ways the survey cannot separate out. The samples are global and skew to companies above US$1bn in revenue, with no India-specific breakdown published, so they describe the shape of the problem rather than a base rate for your own deal. None of them establishes what proportion of lost value sits outside an integration PMO's remit. POLIP does not have that number and has not found one from a publisher it is prepared to cite.

What the PMO owns, and what decides whether value lands

The left column is trackable, ownable and reported weekly, which is why it absorbs the governance. The right column decides whether the projected value is realised, and in most programmes it sits in no one's charter.

Why it persists

Large transformations are governed as programme management problems, and for most of the work that is correct. A PMO tracks what can be defined, sequenced and reported, and does it well. The difficulty is structural: much of what decides whether projected value arrives sits outside its remit, and no governance body owns what its charter does not contain.

The first reason is remit, and the second is sequencing. The decisions that settle leadership and cultural outcomes have to be made before the announcement, during diligence and in the first few weeks. That is when attention is consumed by closing mechanics.

Third, these factors do not take the form the programme measures. A milestone has a date and a completion test. Whether a regional leader has stopped routing decisions through the old structure has neither. Without a definition of adoption in observable behaviour, it is reported in a steering meeting as a judgement rather than as evidence.

Every milestone can land on its date while the value case comes in short. A milestone records that defined work was completed; the benefits were priced on people in both businesses working differently.

What the work examines

POLIP works that territory and does not run the integration PMO. A PMO's charter begins where work can be defined; these questions sit upstream.

Four questions carry the work. Who holds authority in the target, and which of its decision mechanics are incompatible with yours? Where did the two executive teams leave the operating model ambiguous in order to close? Who is load-bearing enough in the acquired business that their exit resets the plan? Which behaviour changes does the value case depend on, in which populations, and by when?

AI adoption lands in that gap twice on most digital transformation programmes. A pilot is approved on condition that it disturbs nothing beside it, which contains the risk, and confines the pilot to work the process can absorb unchanged. So the process that would have to be redesigned if the pilot worked, and the person who owns that redesign, are never named before it runs. Usage is the easiest AI measure to count, so it reaches a benefits realisation report first. The question that decides whether the benefit arrives is which population will decide what differently, and what they stop doing to make room.

The same questions are put to the acquirer and the target, by the same people, which is rarely how diligence is run and is what makes the answers comparable. The work reports to one sponsor, so integration risk reaches the board as one view rather than a second opinion beside the PMO's. Whether the entry point is diligence, pre-announcement alignment or a mid-integration reset is settled with you in scoping, against your deal thesis.

Cultural and organisational due diligence

Decision mechanics, authority and management practice in the target, assessed while price and timetable can still change.

Leadership alignment before the announcement

Operating model, decision rights and senior role questions put to both executive teams and settled in writing before day one.

Retention and capability risk

Who is load-bearing in the acquired business, what they are likely to do, and what holds them beyond a payment.

Adoption architecture

Named behaviour changes by population and date, with observable measures reported beside the value case rather than behind it. The same applies to AI adoption, which is a change management question long before it is a deployment.

Where this shows up in the business

Day to day
Decisions stop routing through the old structure
Where the combined entity's decision rights are written down and the forum that can commit is named, requests stop looping back through the pre-deal structure. Escalation volume becomes countable instead of anecdotal.
Over a year
The numbers already on the integration report
Regrettable attrition among senior leaders in the acquired business over the first eighteen months. Internal fill rate on the roles the value case depends on. Decision elapsed time against the pre-deal baseline. Alongside them, the value case's behavioural assumptions, each with a named owner and a measure.
Over several years
The next transaction costs less to integrate
An organisation that has documented how its own decision rights, forums and management practices work can assess a target against something concrete. It integrates against a model it has already written down, and stops paying for the same discovery at every deal. That accrues whether or not the current deal performs.

None of those numbers is a promised result, and POLIP publishes no client figures. The work establishes which of the value case's behavioural assumptions are load-bearing, and what it would cost to hold the rest. Where the integration thesis will not hold as constructed, you will be told while price, structure and timetable are still variables.

Common questions

We already have an integration PMO and a large firm advising on the deal. Where do you fit?

Beside them, on the territory neither is chartered for. Transaction advisers work the financial and commercial case; the PMO tracks defined work to a plan. Both are correctly scoped; neither charter covers whether the two leadership teams agree on how the combined business will be run, or whether the behaviour the value case assumes actually occurs.

POLIP does not duplicate programme management or take the PMO's reporting line. It reports to the same sponsor, so integration risk reaches the board as one view rather than two.

Can cultural due diligence realistically change a deal decision?

It can change price, structure, earn-out design, retention terms, the integration timetable, and autonomy after close. Those are the levers it is built to inform. Occasionally it changes the decision itself, when the capability being bought turns out to be held by a small number of people whose reasons for staying end at completion.

Timing decides what it can change. Findings delivered while price and structure are open are commercial inputs. The same findings delivered after signing are a description of what you now own.

We are already mid-integration. Is it too late?

No, though the available moves are narrower and some cost is already sunk. Mid-integration work starts with two questions: which of the value case's behavioural assumptions are actually holding, and where decision-making has returned to the pre-deal pattern. Both are answerable in weeks, and both point at specific interventions rather than a reset.

The common finding at this stage is ambiguity. People operate the old way because the new decision rights were agreed in principle and not yet written down case by case. That is normal at close, correctable, and far cheaper in month nine than in month thirty.

How do you measure cultural integration and AI adoption without a survey score?

By defining adoption as observable behaviour in specific populations, then tracking it in the record. Whether decisions of a given type are being taken at the level now authorised to take them. Whether the new forums are making commitments or referring upward. Whether escalation volume and cycle time are moving in the combined entity. Whether the target's managers are using the new process or the workaround. Whether a recommendation produced by a tool reaches a forum with a named owner.

Sentiment scores and usage counts corroborate; neither is built to be the primary instrument. Sentiment reports how people feel about a change, and a usage count records that a tool was opened.

Transformation and Post-Merger Integration Advisory