You closed the deal. The board signed off, the press release went out, the price was in the legal pages, and the integration starts on Monday. Nobody ran a structured digital, change and people read before close. You are not unusual; most acquisitions go this way. You are also not stuck. There is a clean way to enter post-merger integration mid-passage, and it does not start with a hundred-page plan.
This piece is for buyers in that position. It covers the honest state of post-merger integration in 2026, what goes wrong in the first 90 days when nobody ran the pre-deal work, the rapid orientation sprint that reconstructs the position you should have had at close, and how to price the work so the fee is tied to value and not to time.
The honest state of PMI in 2026
Mergers and acquisitions are still won and lost on integration. Three things are different now compared to a decade ago. First, the synergy case sits inside technology more than it used to: data platforms, AI capabilities, customer systems, and the IT operating model are usually where the run-rate savings and the cross-sell revenue live. Second, the speed expectation is shorter. Boards want to see synergies in run-rate inside the first year, not the second. Third, the talent question is louder. The capability you bought is often three or four people on the target’s engineering team, and they can leave in a week.
The implication is that integration cannot be left to a generalist PMO. It needs portfolio control, real RAID discipline, an outside view of the honest position, and an explicit value tracker. None of those happen by default.
What goes wrong in the first 90 days without a pre-deal read
When nobody assesses the target’s digital, change and people position before close, the first 90 days post-close usually break in five predictable places.
- The Day-1 cutover slips. Identity, email, licensing and a handful of customer systems need to be live or interoperable on Day-1. Without a pre-deal map of the target’s estate, the cut-over window has to be rebuilt from scratch under time pressure, and something breaks publicly.
- Key engineers and operators exit. The two or three people who actually run the platform you bought receive recruiter calls within days. If no retention conversation happened pre-close, you lose the capability before you have documented it.
- Data migration estimates triple. The volume, quality and lineage of the target’s data is almost always worse than the pitch said. You discover this in the dry-run, not in due diligence, and the migration plan was built on the pitch.
- Vendor change-of-control fees appear. Software licences, cloud contracts and integrator agreements often carry change-of-control clauses that the deal team did not surface. Three figures of unbudgeted fees become six figures.
- Customers ask questions you cannot answer. A regulated client asks where their data will live after the integration. Without a written position, your account managers stall, and a contract you assumed in the value case starts to wobble.
Every one of these is recoverable. None of them are recoverable in the same hour you discover them. The fix is to spend the first ninety days running a different game.
The on-ramp: a one-to-three-week orientation sprint
The right move when there was no pre-deal read is a compressed orientation sprint. It reconstructs the position that a full pre-deal assessment would have established, accepts where it can only achieve a lower confidence level, and explicitly flags what stays unknown.
The sprint runs in three phases. Orient (days one to three) confirms what the acquirer believes they bought, stands up access to systems and key people, and produces a rapid stakeholder map. Read (days four to eight) scores the target against a fixed five-dimension rubric (digital and technology, change, people, readiness, value and outcomes), prioritising the domains most likely to threaten Day-1 and the value case. Frame (days nine to fifteen) produces the integration brief, drafts the initial workstream shape, and agrees the governance to stand up.
The output is a lighter version of what a pre-deal Risk and Readiness Profile would have produced. It is enough to start planning against. It is honest about what it does not know, and it gives the integration a written baseline that everything from there is measured against.
In the Passage method, this on-ramp is called Bearings. It exists because skipping the pre-work is not a gap to apologise for; it is a designed entry point for the standalone PMI engagement.
What “running PMI properly” actually looks like
A managed-portfolio integration runs on five disciplines, all of which can be stood up in the first thirty days regardless of whether you had a pre-deal read.
- An Integration Management Office (IMO). Single point of control with named decision rights, a cadence that steps down deliberately over time (weekly in operational phase, monthly then quarterly through the strategic horizon), and a sponsor that owns the value thesis.
- Workstream charters and owners. Each digital, change and people stream has a written charter, a named owner, and a plan with a Day-1 design plus 30, 60 and 100-day milestones.
- A RAID and interdependency map across workstreams, not within them. Most PMI tools track risks at the workstream level. The interesting risks live between workstreams, which is why they get missed.
- A value tracker tied to the baseline. Every benefit listed in the deal case becomes a measurable line on a tracker with a baseline, a target, a horizon, and a current realised number. The temptation to report activity instead of outcomes is resisted from week one.
- One source of truth, read at four altitudes. The board sees the one-page story. The IMO lead sees the portfolio view. Workstream owners use the playbooks. The doers use the checklists. All four are the same live data.
The five dimensions and the twelve domains
Scoring an integration position needs a fixed rubric. Five dimensions, scored the same way at every stage, hold the portfolio together: Digital and Technology (systems, data, AI, architecture, cybersecurity, technical debt), Change (magnitude, communications, adoption, ways of working), People (key-person risk, capability, culture, retention), Readiness (the ability to operate, absorb, sustain and go live), and Value and Outcomes (what the integration must deliver and how it is measured).
Inside Digital and Technology, twelve domains are assessed individually so the portfolio scales from a small bolt-on to a multi-entity integration without losing shape: Applications and ERP, Data and Analytics, AI and Automation, Infrastructure and Cloud, Cybersecurity, Integration and Middleware, Networks and End-user Compute, Digital Products and Customer, Licensing and Vendor Contracts, the IT Operating Model, Technical Debt, and Compliance and Sovereignty.
AI and Automation is called out deliberately. In the modern deal it is both a value driver and a risk surface, so it is treated as a domain in its own right and threaded through every other.
How to price PMI without a day rate
Day rates align the consultant with hours, not outcomes. In an integration, the outcomes are measurable: hours recovered, costs out, revenue up, run-rate synergies banked. That makes integration one of the cleanest cases for value-share pricing on the consulting market.
The shape that works: the reads are fixed price, the crossing is value share. The orientation sprint or pre-deal assessment ships as a defined output at a fixed fee, quoted inside two business days of a written brief. The execution and value realisation work runs on a modest base plus an agreed percentage of measured synergies against a co-signed baseline. The exact numbers are set per deal. If the synergies do not land, the share does not either.
What this looks like as a Sydney engagement
For a Sydney-based acquirer (or one operating in Australia), the extra threads are sovereignty (where data lives, where AI workloads run), regulatory load (APRA, OAIC, the Privacy Act 1988 obligations), and the talent market. None of those change the shape of the integration method; they change which domains carry the most weight in the read and the recovery sequence.
The Passage method is industry-agnostic and works whether the target is an Australian SMB, an offshore SaaS business being brought onshore, or a multi-entity merger. The artefacts (the orientation guide, the playbooks, the live tracker, the stakeholder register, the board read-out) come as a complete suite.
The honest summary
You can land an integration without a pre-deal read. You cannot land it without portfolio control, a written baseline, and a value tracker. The honest first move post-close is not a hundred-page plan; it is the orientation sprint that gives you a position to plan against. The Bearings on-ramp into the Passage method is built for exactly this case.
If you are looking at a closed deal and trying to figure out who to bring in, the fit check at the bottom of this page is two minutes and is honest in both directions. If a structured engagement makes sense, it will say so and recommend the model. If it does not, it will tell you that too.