

Measurement Manufacturing Company Tuned for Precision Service at Scale
Global Manufacturer
Programme Delivery
The deal's done. Now you've got two organisations that need to become one. Two sets of processes, two cultures, two technology estates... and a board that wants to see synergies yesterday.
We run the end-to-end post-merger integration (PMI) programme. Assessment, process harmonisation, platform consolidation, change management, adoption. People, process, and technology together. Not just a systems migration with a change plan bolted on afterwards.
20+
Countries rolled out across
50+
People managed across workstreams
£1.3m
Technology simplification savings delivered
5
Vendors coordinated on a single programme
Delivered for
The deal's closed. But two companies don't just become one because the paperwork says so. Here's what M&A integration actually looks like on the ground:
Two cultures, unclear roles. Nobody knows what's changing or when. Adoption fails before it starts.
Lead-to-cash, billing, service... everything works differently. No one owns the target operating model.
Separate CRMs, ERPs, operational tools. Conflicting data, duplicated costs. Nobody trusts the numbers.
One combined organisation that works. Not just merged systems, but harmonised processes, aligned teams, and technology that supports how the business actually needs to operate.
Change management, role clarity, training, and hypercare. So people actually adopt new ways of working instead of resisting them.
A clear, agreed model for how the combined business works. Who does what, how work flows, how decisions get made.
Standardised lead-to-cash, service operations, billing, reporting. With governed local variation only where it genuinely matters.
One data model, one version of the truth. Clean data, trustworthy reporting, cross-sell that's actually possible.
CRM, ERP, finance, and operations joined up properly. End-to-end revenue lifecycle without manual re-keying or duplicate systems.
A playbook, target architecture, and governance model. So the next acquisition doesn't start from scratch.
Right after an acquisition, everyone expects change. People are open to it. They're waiting for direction. That window doesn't stay open long. Within a few months, people settle into new comfort zones and the organisation "refreezes."
That's why we front-load the hard stuff. Get the integration framework established, set synergy targets, launch communications, get teams mobilised. All in the first few weeks, while momentum is on your side.
Three phases with clear entry and exit criteria, built on proven merger integration frameworks. Parallel workstreams for programme management, people, and value tracking run throughout.
Running in parallel across all phases
Steering Committee, PMO, governance, risk, reporting, decision cadence
Retention, communications, culture transition, training, change champions
Financial baseline, targets by team, actual vs planned, benefits realisation
Exit criteria
PMO established, integration team structure defined, guiding principles agreed, communications plan live, roadmap confirmed, synergy targets set.
Exit criteria
Target operating model agreed, synergies assigned by team, integration plans with milestones, customer and employee programmes running, updated roadmap.
Exit criteria
Plans deployed, KPI reporting live, synergies tracked and realised, integration resources redeployed, BAU handover complete.
“Without a Design Authority, every team can hold the programme hostage with their own dependency. ‘We can't move to the new CRM until we know what ERP we're on.’ That's a legitimate concern. But someone needs the mandate to say: that's a Phase 2 decision, it doesn't block Day 1, here's the interim approach.”
Anna Bromley
Director, Agile Delivery
Sample deliverable
How we sequence integration workstreams so the business keeps running while the integration gets done.
The frameworks, tools, and deliverables we use at each stage.
Global
Core
80%+
Design principle
We design 80%+ of the combined business to run on a single, governed core. Standardised processes, common data model, shared definitions, and a Centre of Excellence to keep it clean.
The remaining 20% is for genuine variation. Regional legal requirements, fiscal differences, or real business model differences (e.g. B2B vs B2C divisions that have legitimately different sales processes). Every variation is documented, governed, and reviewed. Not silently customised.
The CoE is a small permanent team that governs the platform after the integration programme ends. They maintain standards, manage change requests, own the enhancement roadmap, and onboard future acquisitions using the established playbook.
Structure, roles, staffing
Segments, journeys, retention
CRM, ERP, MDM, integrations
Synergies, costs, benefits
Lead-to-cash, service, billing
Channels, brands, pricing
Sample deliverable
Before any technology decision, we define how the combined business will actually work. Org design, process maps, customer model, tech blueprint, governance, financials. It's not one document, it's a collection of design decisions that every integration team works from.
This is what stops the "best of breed" trap. Where companies try to pick the best bits from each side and merge them. It sounds sensible but it creates a Frankenstein that nobody recognises. We pick one company's process as the foundation and only adapt where there's a genuine business reason to.
“Keep departments whole. Select one company's entire suite of processes rather than mixing and matching. The mixing and matching is where it falls apart.”
Anna Bromley
Director, Agile Delivery
Sample deliverable
A four-stage toolkit that takes each acquired business unit from initial assessment through to a funded implementation roadmap.
Questionnaire
Pre-filled where existing materials are available. Owner assigned for each section.
Technology & Business Workshops
Workshops with key tech and business contacts across both entities.
Capability Mapping
Capabilities across business units and maturity levels. Common vocabulary for current and future states.
Business Unit Profiling
Key business needs and dependencies across units. Recommendations presented to leadership.
Scoring & Prioritisation
Weighted scoring across dimensions to assess and prioritise readiness to onboard.
Architecture & Design
Target architecture, reference designs, and integration patterns for the combined platform.
Funding Strategy
Business case with investment needed, resource levels, and expected benefits.
Implementation Roadmap
Phased plan with milestones, dependencies, and go/no-go gates.
Sample deliverable
Before any cutover or go-live, we check whether each business unit is actually ready. Not "does it work in test?" but genuinely ready across customer impact, process, testing, system interfaces, and people.
Red means stop. Green means go. This gets published weekly to the Steering Committee so there are no surprises on cutover day.
| Business Unit | Customer | Process | Testing | Interfaces | People |
|---|---|---|---|---|---|
| Sales | |||||
| Service Ops | |||||
| Finance | |||||
| IT | |||||
| HR |
Sample deliverable
Synergies don't materialise on their own. We set a financial baseline, assign targets to each integration team, and track actual vs planned monthly. The numbers feed directly into the combined budget so value doesn't leak.
This is what your board and CFO will ask for. We build it in from Phase I so it's not an afterthought.
| Team | Status | Target | Planned | Realised |
|---|---|---|---|---|
| Sales | £2.0m | £1.2m | £0.9m | |
| Finance | £1.5m | £0.8m | £0.6m | |
| IT | £0.8m | £0.4m | £0.2m | |
| Customer Service | £0.5m | £0.3m | £0.3m | |
| HR | £0.3m | £0.1m | £0.0m | |
| Total | £5.1m | £2.8m | £2.0m |
Built from doing this work, not from reading about it.
The goal isn't to merge systems. It's to create something better than either company had before.
Customer and employee experience workstreams run in parallel with everything else. Not bolted on at the end.
Agree how the combined business works first. Then configure the tools to support it.
Organisations have limited capacity for change. Get the critical stuff right first, go live, then iterate on the rest.
Mergers are messy. Tight governance and rapid decision-making stop things drifting.
Customers, employees, partners, regulators. Silence causes more damage than bad news.
Governance from day one. So the next acquisition plugs into a proven playbook, not another firefight.
Programme leadership for Salesforce integration following a major acquisition (600 staff). Ran the assessment and onboarding approach for the acquired entity, defining scope, governance, and delivery plan. Programme was paused to recalculate strategy after the initial approach proved too narrow.
Led a €4m programme consolidating multiple Salesforce orgs into one global instance integrated with ERP. Eight workstreams, ~50 people, five vendors, 20 countries. Included carve-out work as a department moved into a new entity.
Programme leadership redesigning the revenue operating model across Salesforce, NetSuite, and a new data platform. Delivered £1.3m in technology simplification, CPQ re-implementation business case, and governed BI/reporting blueprint.
Windows 10 estate refresh across 100+ sites as part of a business integration drive ahead of Kantar Media's sale to Bain Capital. Plus application rationalisation to determine which apps should be re-engineered, retired, or re-aligned ahead of the separation.
It depends on scope. A focused single-entity integration might be £150k. Multi-country, multi-system consolidations go to £2m+. We scope in phases so you can commit incrementally. Phase I (Assessment) is typically £25-50k and gives you the full business case before committing to build.
We lead the programme and bring delivery governance, business analysis, and change management. For platform build we work with implementation partners or coordinate your existing vendors. You get independent programme leadership that isn't conflicted by build revenue.
Phase I can begin within 2 weeks. We mobilise a small team for the assessment, then scale up based on the roadmap we build together.
That's something we've dealt with before. Sometimes integrations stall because the initial approach was too narrow, or governance wasn't right, or scope wasn't properly defined. We can start with a Delivery Control Snapshot to assess where things are before committing to a full programme.
Our deepest expertise is Salesforce and CRM/ERP integration. But the programme methodology is platform-agnostic. We've delivered across Salesforce, NetSuite, SAP, ServiceMax, MuleSoft, and Microsoft Dynamics.