AtlanticM&A — Agentic Transformation OS

Built by a practitioner. For practitioners.

An Agentic Transformation OS for M&A integration, divestiture, transformation and cloud migration. Thirty years of integration practice, encoded, so the work runs the way practitioners already run it.

Four things to know

Why it reads like the work, rather than like software about the work.

i.

Built by a practitioner

Thirty years on the practitioner side of M&A integration — sell-side, buy-side, carve-outs, post-merger transformation, restructuring. Cross-border deals across the UK and US. The product reflects the workflow, not the consulting deck.

ii.

For practitioners

Built for the people who run the work, not the people who buy the software. Every screen assumes you already know what a Day 1 readiness gate is, what a TSA exit involves, why a charter has to tie back to a work plan. None of it was translated from a consulting framework, because none of it started as one.

iii.

75 patents filed

Patent-pending across agentic project navigation, voice-driven stakeholder coaching, TSA bootstrap, cross-deal pattern surfacing, data-to-deck generation with chrome-preserving overlay, Wave Plan sequencing, and Cadence Centre.

iv.

For the half of M&A that isn't code

Integration, divestiture, transformation, and cloud migration all share the same gap: a practitioner spends days per week on manual deck-building, status reporting, and stakeholder coordination. That's the half AtlanticM&A automates.

Who built it

Richard Parry, founder of AtlanticM&A

Richard Parry

Founder

Oxford · London Business School · IMI, Deloitte, IBM, mars & co · delivering since 1998

My career has been the work that changes how a business runs: value creation programmes, carve-outs, post-merger integration, and operating-model and technology transformation. I did that at Deloitte, at IBM and at mars & co, and independently since.

My first M&A project was in 1998. I was a young engineer at IMI plc and somebody had to work out which of two overlapping product ranges to keep, so I pulled the sales and cost data out of both companies' systems and wrote the application that answered it. My first M&A project was building software to model a merger. Here we are again.

What followed was a career doing that work without the software. Every programme used the same four artefacts, and I maintained them by hand, engagement after engagement, for over a decade. The method held up. Rebuilding the artefacts by hand did not scale.

The plan was never the problem. Keeping the plan current was the problem.

Published on this, since 2011

The ideas in this product are not new to me and they are not unexamined. Two were published by London Business School.

  • "A better way to merge companies? M&A project teams", Business Strategy Review, Issue 4, 2011. On why handing the messy details to people with no prior involvement fails, and why the missing piece in most M&A programmes is capability rather than process.
  • "A better way to grow?", Business Strategy Review, Issue 3, 2014. A framework for growth programmes across strategy, execution, optimisation, growth capacity and political risk.
  • Sloan Fellowship thesis, London Business School, supervised by Professor Eli Talmor: where the value in a £1.9bn leveraged buyout actually came from, separating financial engineering from operational improvement. It earned a distinction and was contributed as a case study to International Private Equity (Wiley), which is used to teach private equity at LBS.

That last one matters more than it looks: working out which part of a return came from operating improvement and which from leverage is exactly what the value bridge in this product does. I wrote the long-hand version twenty years ago.BETA

Where the methodology was forged

M&A and transformation delivery since 1998, across pharmaceuticals and life sciences, automotive, payments and financial services, industrials and chemicals, technology, energy, retail, healthcare and government. Six continents. Buy-side and sell-side, corporate and private equity, from lower-middle-market acquisitions to multi-billion-dollar separations.

The parts most relevant to what this software does:

Transitional service agreements, end to end

I have designed TSAs pre-signing so a buyer knows what it is taking on, negotiated them into sale agreements as addenda that moved the price, run the exits, and rescued one that was failing: a $2.07bn carve-out from a Fortune 500 seller to a private equity buyer, running at some $12m a month whilst thirty-odd jurisdictions sat deferred on the seller's systems, in the middle of the pandemic. We exited before expiration. The virtual TSA planning method I built there, replacing the walk-the-walls exercise with dependency logic and prioritised swim lanes, is in this product.

Cross-border deals at scale

On a $35bn pharmaceutical asset swap I built the consulting bid for a forty-consultant programme and won the finance workstream. For a different client, on a separate programme, I did the work that laid the ground for a $6.4bn acquisition of a business-process outsourcer. Transformation and M&A are not separate disciplines. The strategy is what tells you what to buy.

Value creation, two years of it, before the exit

At mars & co I spent two years on a value-creation programme at a global water-treatment business, for its French utility parent. That was the operational work that made the business worth selling, ahead of the parent taking it to private equity in one of the largest US deals of that year. Transformation ahead of a sale is the same discipline as transformation after one; only the deadline moves.

Two years as Chief Transformation Officer

Most recently I spent two years as Chief Transformation Officer of a private-equity-backed life sciences platform, running nine acquisitions and the transformation around them across three continents with a team of eighty. Three continents, eighty people, six more deals coming, run on a Smartsheet dashboard I designed and built myself. It worked. The programme delivered. What it cost was people, and that is the reason this software exists.

Diligence that did not confirm the thesis

I have also recommended against acquisitions. One target had attractive financials and a product safety problem serious enough to outweigh them; I told the sponsor not to buy it. Diligence that only ever confirms the thesis is not diligence.

Why it exists

M&A integration has been under-served by specialist software for decades. The Big 4 firms have proprietary tooling; everyone else — independents, in-house corp dev teams, PE operating partners, platform PortCos — make do with spreadsheets and slide decks. We're building the institutional methodology backbone that runs continuously across deals, not the per-engagement consulting product.

How it's built

AtlanticM&A runs on AWS — Aurora PostgreSQL with Row-Level Security for tenant isolation, KMS envelope encryption for data at rest, AWS Bedrock for AI. The platform is multi-tenant SaaS; tenant data never trains shared models. SOC 2 Type II is in progress; ISO 27001 controls implemented; GDPR-compliant by architecture.

What's in the patent portfolio

The portfolio covers agentic project navigation, voice-driven stakeholder coaching, TSA bootstrap, cross-deal pattern surfacing, data-to-deck generation with chrome-preserving overlay, Wave Plan sequencing, and Cadence Centre — the mechanisms that define an Agentic Transformation OS as a category. Patent prosecution is ongoing.

AtlanticM&A — Agentic Transformation OS is operationally separate from the consulting practice at atlanticma.com. The only shared element is the brand. See the trust portal for tenant-isolation and security posture.

See what one practitioner + AI can do.

14-day free trial. SOC 2 Type II observation underway · ISO 27001 controls implemented · 75 patents filed.