D://LEAD42M&A, Divestment, & Spinoffs
The technology side
of the deal.
Technology due diligence, separation, and integration for mergers, acquisitions, and divestments, including the day-one plan for identity, email, and data. It is for organisations buying, selling, or splitting a business, where IT sits on the critical path and is rarely planned early enough.
THE PROBLEM
Technology is usually the last thing considered in a transaction and the first thing that delays completion.
The cost of leaving this alone is rarely one visible failure. It is the slow accumulation: the workaround that became the process, the thing only one person knows, the renewal nobody questioned.
Our starting point is always the same: establish what is actually true today, then decide what to change. Work scoped against an assumption tends to solve a problem you do not have.
- 01Nobody owns itIt sits with whoever touched it last, which is not the same as being managed.
- 02No current pictureWhat you have, what it costs, and who has access are all slightly out of date.
- 03Only handled when it breaksAttention arrives after the disruption rather than before it.
WHAT YOU GET
What the engagement covers
Scoped before it starts, so you know what is included and what is not.
- 01
Due diligence
What the target actually runs, what it costs, what is contracted, and what liabilities come with it. Non-transferable licences and undocumented custom systems are the ones that move a price.
- 02
Separation plan
How to untangle shared identity, email, and data without either business stopping trading during the process.
- 03
Day one
What must work the morning after completion, and what can safely wait until month three.
- 04
Integration
Consolidation onto one platform, sequenced so the disruption is planned and finite rather than continuous.
HOW WE WORK
Discover, design, deliver, embed
Four stages with a written output at each one. You always know which stage you are in and what comes next.
- 01Weeks 1 – 2
Discover
We map how the work happens now, including the workarounds people are slightly embarrassed to mention.
- 02Weeks 3 – 4
Design
Options costed against benefit, so the choice is a decision rather than a preference.
- 03Per stage
Deliver
Built in slices that reach production and get used, each with a success measure agreed before it starts.
- 04Post-delivery
Embed
Training, documentation, and a check-in once the novelty has worn off. Adoption is the only measure that counts.
WHAT CHANGES
What you should expect
- Someone other than you owns it, with that written down.
- The current state is documented and stays documented.
- Cost is planned ahead rather than discovered at renewal.
- Decisions are made against evidence rather than assumption.
FAQ
Questions we get asked
01What is IT due diligence for mergers, acquisitions, and divestments?
Technology due diligence, separation, and integration for mergers, acquisitions, and divestments, including the day-one plan for identity, email, and data. It is for organisations buying, selling, or splitting a business, where IT sits on the critical path and is rarely planned early enough.
02When should IT get involved in an acquisition?
During diligence, not after completion. Technology routinely turns up findings that affect the price or the terms: licences that do not transfer with the entity, systems past end of support, a domain registered to a director personally, undocumented custom development maintained by one contractor, or an unresolved security incident. All of those are cheaper to discover before you sign.
03How long does it take to separate IT after a divestment?
Day one needs to work immediately, and full separation typically runs for months afterwards. The usual shape is a transitional services arrangement where the seller keeps providing certain systems for an agreed period while the new entity stands up its own. Getting that period and its exit criteria right in the sale agreement matters considerably more than most parties expect.
04What has to work on day one after a deal completes?
Email and identity, so people can sign in and be reached. Access to the files they need to do today’s work. Phones answering. The finance system able to invoice. Almost everything else can wait a fortnight, and trying to do everything at completion is how day one goes badly.
05What are the most common technology problems found in due diligence?
Licensing that is not transferable or is simply under-purchased. Key person dependency, where one individual holds the knowledge and the credentials. End-of-support systems that need immediate capital. Unresolved security exposure. And documentation that turns out to describe an environment from four years ago. None are unusual, and all are negotiable if found in time.
06How much does IT due diligence for mergers, acquisitions, and divestments cost in New Zealand?
We quote after scoping rather than before. Anyone pricing this work without looking at your environment is guessing, and the guess is rarely in your favour. Scoping itself is quick, and we tell you what it costs before we start it.
07How long does it take to get started with IT due diligence for mergers, acquisitions, and divestments?
A first conversation takes about half an hour and costs nothing. Scoping is usually a week or two of our time depending on the size of the environment, and we agree the delivery dates with you before anything is booked in.
08Can you deliver IT due diligence for mergers, acquisitions, and divestments alongside our existing IT team or provider?
Yes, and it is common. We are happy to work as an extra pair of hands under your internal team, or alongside an incumbent provider on a defined piece of work. We will set out in writing where the responsibilities split, so nothing falls between us.
09Do we have to be an existing Atlas client to start a project?
No. This can be delivered as a standalone piece of work for an organisation we have never worked with before, or folded into a managed agreement if you already have one with us. Plenty of clients use us for one thing and keep everything else where it is.
10Do you deliver projects outside Auckland?
Our team is based in Auckland and we attend sites across the wider region. Most of this work is delivered remotely, so we support organisations throughout New Zealand, and we will say up front where being on site genuinely matters.
11Who from Atlas will be on the engagement?
Named people, not a queue. You get a lead who knows your environment and stays with it, which is the difference between explaining your business once and explaining it every time you make contact.
12What happens when the engagement ends?
You keep the documentation regardless, and anything registered in your name stays in your name. Whether we stay involved is your call. Some clients take it in house from there, others move it onto an ongoing agreement with us. We would rather you left cleanly than stayed because leaving was difficult.
Start with a conversation.
Tell us what you are dealing with and we will tell you whether this is the right service for it, and what it would take.
← All services