|
Assured Velocity
The Velocity Brief
Straight talk on transformation, technology, AI, data and people leadership for mid-market operators. No vendor spin. No consultant waffle. Just what actually works.
|
Issue 06 · September 2026
|
|
|
This Month
The integration you did not finish is now your biggest risk.
|
|
In This Issue
|
01 The Hard Truth
02 The 6 Integration Gaps That Never Close
03 Real World Case Study
|
04 Brian Ford: Programme Recovery Post-Acquisition
05 Richard Danks: Technology Integration
06 Joe Kay: Operational Integration
07 Tom Henry: Process Integration
|
|
|
|
01 The Hard Truth
Most post-acquisition integrations are declared complete at the point the deal closes. The actual integration work has barely started.
The acquisition thesis is always clear at the point of purchase. Strategic fit, revenue synergies, operational leverage, talent acquisition. The business case is well-constructed and the board is aligned. What happens next is where the value either gets realised or quietly destroyed. In most mid-market acquisitions, the integration is treated as an operational task to be completed in the first 90 days. It is neither completed nor operational. It is a complex change programme with a governance gap.
The research on post-acquisition value destruction is consistent across decades of M and A activity. Between 70% and 80% of acquisitions fail to deliver the value anticipated in the business case. The primary cause is not the strategy. It is the integration. Specifically, the parts of the integration that were scoped but never completed - the technology that was never consolidated, the processes that were never aligned, the governance that was never unified, the people whose accountability was never clarified.
|
Why integration gaps persist
Business as usual takes over. The integration workstream loses priority when the operational demands of running two businesses simultaneously consume all available leadership bandwidth.
The gaps become invisible. Teams develop workarounds for unresolved integration issues. The workarounds become the normal way of working. The gap is no longer visible - but it is still there, consuming effort and constraining performance every day.
Nobody owns the completion. The integration lead moved on. The programme was formally closed. The remaining items were captured in a list that lives in a folder that nobody opens. The business is now running a permanent workaround for a problem it believes it solved two years ago.
|
The compounding cost of an unfinished integration grows every quarter. The technology debt accumulates. The process misalignment creates friction in every customer interaction that crosses the legacy boundary. The governance gap produces risk that is not being measured or managed. And the people carrying the unresolved integration in their daily work are quietly burning out or quietly leaving.
|
|
|
02 The Framework
The 6 Integration Gaps That Almost Never Get Closed
Each gap maps to a domain where incomplete integration creates ongoing cost, risk or friction. If you have made an acquisition in the last five years, run this list against your current state.
|
1
|
Technology Consolidation
The acquired business had its own technology estate. The plan was to migrate to the parent platform within 12 months. Three years later both platforms are still running. The migration is on the roadmap. It has been on the roadmap every year. Meanwhile the business is paying for two sets of licences, two sets of support contracts, and the manual effort required to reconcile data across two systems that were never designed to talk to each other.
Cost: Ongoing licence duplication, manual reconciliation effort, data integrity risk, technology team bandwidth consumed by maintenance of a redundant estate.
|
|
2
|
Process Alignment
The acquired business had different processes for everything that matters - order management, client onboarding, billing, compliance reporting. The integration plan included a process harmonisation workstream. It was descoped in month three when the integration lead had to focus on the technology migration. The two businesses now run parallel processes indefinitely. Every cross-entity transaction requires manual translation between two process models that were designed independently.
Cost: Operational friction at every cross-entity touchpoint, client experience inconsistency, staff confusion about which process applies, compliance risk from inconsistent reporting.
|
|
3
|
Governance Unification
The acquired business had its own board, its own reporting cadence, its own risk framework. Post-acquisition the legal entity was absorbed but the governance model was not redesigned. The group board is now receiving reporting from two different governance frameworks with different definitions, different cadences and different risk appetites. Nobody has defined which framework governs which decision at group level. The answer depends on who is in the room.
Cost: Board reporting that cannot be reliably consolidated, governance risk for regulated activities, decision-making ambiguity that slows every cross-entity initiative.
|
|
4
|
Data Model Harmonisation
The two businesses defined their data differently. Customer records, product categories, financial codes, performance metrics - all defined independently, all named differently, all structured differently in their respective systems. The plan was to create a common data model as part of the technology migration. The migration stalled. The common data model was never built. The group CFO cannot produce a consolidated performance view without a manual reconciliation that takes three days and is error-prone every month.
Cost: Management reporting that requires manual reconciliation, finance team effort diverted from analysis to data preparation, strategic decisions made on data that cannot be validated.
|
|
5
|
People and Culture Integration
The acquired business had its own culture, its own values, its own ways of working. The integration plan included a people and culture workstream. It was reduced to a communications plan and two all-hands meetings. Three years later the two teams operate as distinct tribes with distinct identities, distinct informal hierarchies and distinct expectations about how decisions get made. Cross-entity collaboration is harder than it should be and everyone knows why but nobody has been asked to fix it.
Cost: Cross-entity collaboration friction, talent retention risk in the acquired business, inability to deploy talent flexibly across the combined group.
|
|
6
|
Customer Experience Unification
The acquisition was partly justified by the cross-selling opportunity. Three years on, the cross-sell has underperformed against the business case. The reason is straightforward: a customer engaging with both entities experiences two completely different service models, two different account management approaches, two different billing formats and two different quality standards. The customer does not experience a group. They experience two businesses that happen to have the same parent company. The cross-sell requires them to trust the second entity as much as the first. That trust is built on experience. The experience has never been unified.
Cost: Cross-sell underperformance against business case, client relationship risk at the entity boundary, brand coherence gap that limits group market positioning.
|
|
The Integration Audit
For every acquisition made in the last five years, run this list. For each of the six gaps, ask: is this closed, partially closed, or open? If more than two are open or partially closed, you have an unfinished integration that is costing you more than you are measuring. The cost of completing it is almost always lower than the ongoing cost of not completing it. But it requires treating it as a programme - with scope, ownership, governance and a defined completion date - rather than assuming it will resolve itself.
|
|
|
|
03 Real World
The £55M Professional Services Group That Discovered Its 3-Year-Old Acquisition Had Never Actually Been Integrated
Anonymised for client confidentiality
The acquisition had been declared a success at 12 months. Revenue was up. The acquired team was retained. The brand had been unified. The integration programme was formally closed. Three years later the group CFO commissioned a performance review and could not produce a reliable consolidated P and L without two weeks of manual work from the finance team. The CEO described it as "baffling." It was not baffling. It was an unfinished integration.
|
"We closed the integration programme three years ago. We are apparently still running two businesses."
Group CFO, on initial engagement
|
What the integration audit found - three years after programme close:
|
Technology: Two separate CRM instances. Two separate project management tools. Finance data reconciled manually every month end by a senior analyst who had built an Excel model so complex that only she understood it. She was planning to leave.
Data: Client records defined differently in each system. Revenue recognised differently. Project stage definitions used different terminology. The group performance dashboard required manual translation every month before it could be read at board level.
Process: Client onboarding ran as two entirely separate processes. A client engaging both entities completed two separate onboarding journeys with no acknowledgement that they were already a group client.
Cross-sell: The cross-sell target from the acquisition business case had been missed every year. The reason was now clear - there was no mechanism for either entity to identify group clients in the other entity's system and no agreed process for making a warm introduction.
|
20-week integration completion programme. Outcomes:
|
Single CRM instance. Client data consolidated and deduplicated. Group client view available in real time
Common data model implemented. Monthly board report produced in 4 hours rather than 2 weeks
Single client onboarding process across both entities - NPS score up 14 points within 6 months
Cross-sell referral process implemented - 23 cross-entity introductions in the first quarter post-launch
Senior analyst retained - her Excel model retired, her capability redeployed to strategic analysis
|
|
Annual Cost of Unfinished Integration
£180,000
Licence duplication, manual effort, missed cross-sell
|
vs |
Cost of Completion Programme
£68,000
Payback in under 5 months
|
|
|
|
Partner Articles
From the Front Line
All four partners on post-acquisition integration - from programme governance, technology, operational and process perspectives. Because every domain has an integration failure mode of its own.
|
|
Brian Ford
Partner · Programme Recovery and Delivery Assurance · PRINCE2 Practitioner
|
An Integration Is Not a Project. It Is a Programme. And It Does Not End When the Deal Closes.
I have recovered more post-acquisition programmes than any other type of engagement. The pattern is remarkably consistent. The integration is treated as a project with a defined end date - usually the date of legal completion or some arbitrary milestone like "systems access granted." The programme is closed. The governance is dismantled. The integration lead moves to the next acquisition or returns to a business-as-usual role. And the unfinished work is distributed into the organisation with no owner, no timeline and no board visibility.
A meaningful post-acquisition integration is a programme of 18 to 36 months minimum for a mid-market business. It has multiple interdependent workstreams - technology, data, process, governance, people, customer experience. Each workstream requires its own ownership, its own milestone structure and its own reporting cadence. None of them can be declared complete until the outcome they were designed to deliver is measurably achieved.
|
The integration programme should not be closed until you can demonstrate that the combined business operates as a single entity - not until the paperwork is done.
|
The practical implication for any business that has made an acquisition in the last five years is to run an honest audit of what was actually completed versus what was scoped. Not what was delivered by the integration team. What is measurably true in the combined business today. The gap between those two answers is your integration debt. Quantify it. Cost it. Then treat closing it as a programme - with the same governance rigour you would apply to any other investment of that magnitude.
The integration debt does not reduce over time. It compounds. Every quarter you leave it unresolved, the cost of carrying it increases and the cost of completing it increases too.
Brian Ford led the largest banking transformation in Europe at Bank of Ireland and has delivered programmes at EY, Capgemini, Barclays Capital and JPMorgan. Connect on LinkedIn
|
|
|
Richard Danks
Partner · Technology, Governance and CTO Recovery · DBA, MBA
|
The Technology Integration You Deferred Is Now Technical Debt With Compounding Interest.
Technology integration is almost always the first workstream to be deferred and almost always the last to be completed. The reasons are understandable. It is complex, expensive and risky. The business case for completing it is harder to articulate than the business case for the acquisition itself. And in the short term, the workarounds work - well enough for the business to function, not well enough to create the unified capability the acquisition was designed to deliver.
What most boards do not see is the compounding cost of deferred technology integration. Every month of parallel operation adds to the integration complexity. Data diverges. Custom configurations accumulate. The team that understands the legacy system becomes smaller as people move on. The institutional knowledge required to complete the migration safely concentrates in one or two individuals who are increasingly difficult to retain. The window for completing the integration at reasonable cost is closing every quarter it is deferred.
|
The cost of completing a technology integration in year one is a fraction of the cost of completing it in year four. The business case for completing it now is stronger than it has ever been - and weaker than it will ever be again.
|
The practical question for any board with deferred technology integration on the roadmap is: what is the cost of completing this in the next 12 months versus the cost of carrying it for another three years? Include the licence duplication, the manual reconciliation effort, the talent retention risk associated with the legacy system, and the strategic capability you are foregoing by not having a unified data and technology platform. The answer almost always makes completion the more rational choice.
Then treat the completion as a programme with proper governance - not a project to be handed to the IT team alongside everything else they are already doing.
Richard Danks specialises in technology governance, enterprise architecture and CTO recovery across banking, defence and SaaS. Connect on LinkedIn
|
|
|
Joe Kay
Partner · Process and Operational Excellence · Lean Six Sigma Master Black Belt
|
Operational Integration Is Not About Merging Two Teams. It Is About Building One Operation.
In operational terms, a post-acquisition business is running two separate operations under one ownership structure. Each operation has its own efficiency profile, its own waste patterns, its own performance benchmarks and its own institutional knowledge about how things get done. The synergies that were projected in the acquisition business case assumed one operation. What exists is two.
Operational integration means defining the combined operating model - how the unified business will run end to end - and then redesigning the processes to match that model. Not adopting one entity's processes across the other. Not running both in parallel. Building the best version of each process from the combined capability of both organisations, then implementing it consistently across the unified operation.
|
The operational synergies in an acquisition are real. But they do not emerge automatically from shared ownership. They require deliberate process redesign across the combined entity.
|
In practice this means mapping both operations end to end, identifying the waste in each, identifying the best practice in each, and designing a unified process model that captures both. It is not a short exercise. For a mid-market business it typically takes three to six months of structured operational design work. But the alternative is operating at the efficiency level of the less efficient entity indefinitely - which is what most businesses with unfinished integrations are doing.
The operational synergies you projected at acquisition are still available. They are just waiting for the integration work that was supposed to unlock them.
Joe Kay has delivered over £100m in operational savings across 100+ programmes including Network Rail, BCG, Aviva and HSBC. Connect on LinkedIn
|
|
|
Tom Henry
Partner · Process Transformation and Operations Excellence · Lean Black Belt L2A
|
The Customer Does Not Know You Made an Acquisition. They Just Know the Experience Got More Complicated.
Post-acquisition customer experience is one of the most consistently underinvested areas of integration work. The business is focused on the internal integration - the technology, the processes, the governance, the people. The customer is experiencing the consequences of all of those gaps simultaneously, with no context for why the service they were used to has changed and no visibility of when it will improve.
The specific risk in a mid-market acquisition is that the acquired business was often chosen partly because of its client relationships and client experience reputation. Those relationships and that reputation were built on a service model that the integration has disrupted. The clients who valued the acquired entity for its quality of service are now experiencing a service model in transition - with the inconsistencies and friction that come from two processes, two systems and two teams that have not yet been unified.
|
The client relationships you acquired are an asset with a shelf life. If the service experience deteriorates during an extended integration, those relationships will not wait indefinitely for the integration to complete.
|
The practical priority in any integration completion programme is to map the customer journey across the combined entity first. Identify every point where the client experience is degraded by the incomplete integration. Prioritise those points for resolution above the internal efficiency workstreams. The clients will not see the ERP migration. They will see the unified onboarding process, the single point of contact, the consistent service standard. Those are what retain the relationships the acquisition was partly purchased to secure.
Fix the customer-facing integration gaps first. The internal efficiency gains will follow. The client relationships may not.
Tom Henry has delivered 50% lead time reductions and double-digit FTE savings across financial services, legal and energy sectors. Connect on LinkedIn
|
|
|
The One Thing - Do This This Month
Run the 6-gap integration audit against every acquisition made in the last five years.
One session. Six questions per acquisition. For each gap ask: closed, partially closed or open? Then cost the open gaps - licence duplication, manual effort, missed synergies, client experience friction. The number will be larger than expected. It always is.
If the audit surfaces significant open gaps - or if you have an acquisition where the integration was formally closed but the combined business still does not operate as a single entity - an Integration Audit Rapid Triage with Assured Velocity is 30 minutes. We will give you a clear view of your integration debt, the cost of carrying it and what a completion programme would look like. No pitch. No pressure.
|
|
Next Month in The Velocity Brief
"Your board is making strategic decisions with operational data it cannot trust."
How mid-market boards are systematically misled by reporting that looks reliable but is not - and the four changes that produce a board information environment the business can actually navigate by.
|
|
Assured Velocity
Fractional Transformation Office for Mid-Market Businesses (£10M to £100M)
Independent · Vendor-Neutral · Embedded in your execution
Transformation Domains
| Strategy |
Technology |
Data |
AI |
Process |
People |
Delivery |
Governance Domains
| Technology Gov. |
Programme Gov. |
Project Gov. |
Business Gov. |
UK-based · Midlands and Nationwide assured-velocity.co.uk hello@assured-velocity.co.uk
You are receiving The Velocity Brief because you signed up or connected with us on LinkedIn.
Unsubscribe ·
Forward to a colleague ·
View online
|
|