IT due diligence and integration audit, UAE

The technology rarely kills a deal. What it does is arrive three months later as a cost nobody put in the model.

IT due diligence establishes what a target actually runs, what it costs to keep running, what it would cost to integrate and what liabilities come with it. The findings that matter are usually licensing, key person dependency, undocumented systems and security debt that has to be paid immediately.

IT due diligence and integration audit for UAE transactions
  • What existsEstablished rather than described
  • What it costsRun rate, plus what was deferred
  • Integration costModelled, not estimated afterwards
  • Same frameworkSo target and acquirer are comparable
What we assess

Eight areas, and the last three are where the surprises live.

A due diligence review has to work quickly, from limited access, against a management team with other priorities. We assess against the CIS Critical Security Controls at version 8.1 so the target and the acquiring organisation can be compared on the same basis rather than through two different narratives.

What actually exists, rather than what is documented

Systems, platforms, cloud environments, applications, devices and the infrastructure underneath. Established from billing, directory, network and identity evidence rather than from a document pack, because the document pack describes the estate as somebody understood it at the point it was written for a different purpose.

The genuine run rate, including what is not in the IT budget

Cloud consumption across every payment route, software subscriptions procured by business functions, support contracts, and anything charged to a card rather than to a cost centre. Shadow spend is normal rather than exceptional, and in smaller targets it is frequently a material proportion of the true technology cost.

Deferred maintenance, which is a liability rather than a finding

Unsupported operating systems, hardware past end of life, software versions no longer receiving updates, and certificates or contracts expiring shortly after completion. These are not opinions about quality. They are dated obligations that transfer with the business, and they belong in the model rather than in a risk register.

Licensing and entitlement exposure

What the target is entitled to, what it has assigned, and what it has configured. Capabilities in use whose entitlement was assumed rather than verified transfer to the acquirer along with everything else, and they surface at the first true-up rather than during the transaction unless somebody looks for them deliberately.

Key person dependency, which is the most common real finding

How much of the environment only one person understands, whether anything is documented well enough for somebody else to operate, and whether that person is staying. In smaller targets this is frequently the single largest integration risk, and it is invisible in any document pack because the knowledge is precisely what was never written down.

Contracts, terms and what does not transfer

Support agreements, cloud commitments, software terms and managed service arrangements, specifically what happens to each on a change of control. Some transfer, some require consent, some reprice and some terminate. That distinction is a commercial question that IT can identify and that legal and finance then have to decide on.

The integration path, costed rather than assumed

Whether the identity estates can be merged or must coexist, whether devices can be re-enrolled in place, and what each option costs. Microsoft describes multitenant organisation capability for organisations with more than one Entra instance, and cross-tenant synchronisation as a one-way service letting users reach resources without an invitation or consent prompt in each tenant.

Security position, assessed on evidence rather than assertion

Against the same eighteen controls used for the acquiring organisation, so the two can be compared directly. The purpose is not to grade the target but to establish what has to be remediated before the environments are connected, because connecting first and assessing afterwards inherits every weakness immediately.

The finding that changes the plan

Whether devices can be re-enrolled in place, or have to be wiped, is a cost line in the integration model.

It looks like a technical detail during diligence and behaves like a project during integration, and it is entirely knowable in advance.

  • Microsoft publishes the factory reset requirement per enrolment method. Reset required for iOS and iPadOS, macOS, and three of the Android Enterprise corporate modes. Not required for Windows, Linux, Android Enterprise personally owned devices with a work profile, and Android device administrator.
  • So a target with a fleet of Macs and iPhones, moving to the acquirer management platform, is a wipe and rebuild exercise per device with data migration, user communication and a support surge attached. A target running Windows is not.
  • Microsoft also notes that devices enrolled with another management provider must be unenrolled from it first, and that unenrolling typically does not remove the features and settings that were configured. Residual configuration therefore persists on the platforms that are not wiped, which is a different problem in the same area.
  • None of this is difficult to establish during diligence. All of it is expensive to discover during integration, and the difference between the two is a line in a model rather than a surprise in month three.
Ask us to model the integration cost
How we approach it

Four things a technology diligence should produce and often does not.

Diligence reports frequently describe the estate accurately and stop short of the two things a transaction team actually needs, which are what it costs and what has to happen on day one.

We establish the estate from evidence, not from the pack

Billing routes, directory and identity records, network evidence and external discovery. A document pack describes the estate as somebody understood it when writing for a different purpose. Evidence describes it as it is, and the gap between the two is consistently the first substantive finding in a mid-market target.

We produce a number, in the form the model needs

Run rate including spend outside the IT budget, deferred maintenance as dated obligations rather than as observations, and integration cost by option. A diligence report that describes risk without costing it leaves the transaction team to translate, and the translation is where the estimate becomes optimistic.

We assess key person dependency explicitly

How much of the environment exists only in one person head, whether the documentation would let anybody else operate it, and whether that person is staying. In smaller UAE targets this is frequently the largest single integration risk, and it is the one that converts a technical finding into a deal term.

We produce a day one plan, not only a report

What must be true at completion, what can wait, what has to be remediated before the environments are connected, and what the integration options cost. That is the artefact that gets used after signing, and it is the difference between a report that informed the price and one that also informs the first hundred days.

Where this applies

Six transaction situations where technology diligence changes the outcome.

Technology is rarely the reason a deal does not happen. It is frequently the reason the first year costs more than the model said, and that is entirely addressable in advance.

A group acquiring a smaller UAE business

The most common case. The target runs a small estate competently, largely through one or two people, with documentation that describes intentions rather than reality. The findings that matter are key person dependency, technology spend outside the IT budget, and the integration cost of a device fleet that may need rebuilding.

A buyer acquiring a business with client data obligations

Where the target holds client or personal data under contractual or regulatory obligations, those obligations transfer. Establishing what data exists, where, who can reach it and whether any exposure is already present is materially cheaper before completion than as an inherited problem afterwards.

An investor assessing technology as part of a wider review

Where technology is one workstream among several, the useful output is a small number of quantified findings in the form the model uses, rather than a comprehensive technical description. Run rate, deferred obligations, integration cost and the two or three risks that would change the plan.

An acquisition where operational technology is in scope

Plants, facilities and production environments carry technology with longer lifecycles, tighter change constraints and frequently no documentation at all. Assessing it needs a different approach from corporate IT, and its deferred maintenance is usually both more expensive and more consequential.

A carve-out where systems must be separated rather than merged

The harder version of the problem. What the carved-out entity depends on from the parent, what transitional service arrangements are required, how long they run and what standing the entity up independently costs. Diligence here is as much about separation cost as about the estate itself.

A post-completion review where diligence was not done

Entirely recoverable and worth doing quickly. The same assessment run after completion produces the same findings, with the difference that the price is fixed and the findings become an integration budget question rather than a valuation one. Doing it in the first quarter is considerably better than in the first year.

Three positions

How UAE acquirers handle technology in a transaction.

The middle column is common in mid-market deals. Somebody looks at the technology, forms a reasonable view, and the integration cost is discovered rather than modelled.
Estate established from evidence
Assessed on evidenceYes
Reviewed from the document packFrom documents
Technology not assessedNo
True run rate known
Assessed on evidenceYes
Reviewed from the document packThe stated figure
Technology not assessedNo
Deferred maintenance quantified
Assessed on evidenceYes
Reviewed from the document packPartly
Technology not assessedNo
Licensing exposure identified
Assessed on evidenceYes
Reviewed from the document packRarely
Technology not assessedNo
Key person dependency assessed
Assessed on evidenceYes
Reviewed from the document packNo
Technology not assessedNo
Change of control terms flagged
Assessed on evidenceYes
Reviewed from the document packSometimes
Technology not assessedNo
Integration cost modelled
Assessed on evidenceYes
Reviewed from the document packEstimated after
Technology not assessedDiscovered
Security compared on the same framework
Assessed on evidenceYes
Reviewed from the document packNo
Technology not assessedNo
Day one plan exists at completion
Assessed on evidenceYes
Reviewed from the document packNo
Technology not assessedNo
Surprises in month three
Assessed on evidenceFew
Reviewed from the document packSeveral
Technology not assessedMany
What we look for

Ten findings, and what each one means commercially.

These are the findings that recur. The commercial column is what each typically translates into, which is the form the transaction team needs rather than the technical description.
FindingWhat it means commercially
Systems not in the document packThe estate is larger than modelled, and so is the run rate
Technology spend outside the IT budgetTrue cost is higher than the figure provided
Unsupported platforms in productionA dated remediation obligation transferring with the business
Entitlement that cannot be evidencedA cost that appears at the first true-up after completion
Key person dependencyRetention becomes a deal term rather than an HR matter
Contracts affected by change of controlConsent, repricing or termination, each with a value
Apple or Android device estateWipe and rebuild per device during integration
Residual configuration after unenrolmentCleanup effort on the platforms that are not wiped
Security gaps against the same control setRemediation that must precede connecting the environments
Undocumented integrations and interfacesThe most common cause of an integration overrunning
How an engagement runs

Five steps, compressed to whatever the transaction timetable allows.

Typically two to four weeks, and frequently less. Diligence works to the deal timetable rather than the other way round, so the method is designed to produce the material findings early and refine afterwards.
  1. 1

    Agree what the transaction actually needs to know

    A valuation input, an integration plan, a risk view for the board, or all three. That determines depth and emphasis. A review scoped as a general technology assessment produces a comprehensive document, and a review scoped around three specific questions produces answers the deal team can act on.

  2. 2

    Establish the estate from evidence, fast

    Billing routes, directory and identity, network, external discovery and whatever management platforms exist, alongside the document pack rather than through it. The gap between the two is recorded explicitly, because how large that gap is tells you as much about the target as its contents do.

  3. 3

    Quantify cost, obligation and exposure

    Run rate including technology spend outside the IT budget, deferred maintenance expressed as dated obligations, licensing and entitlement exposure, contracts affected by change of control, and any security or data protection exposure that transfers with the business.

  4. 4

    Model the integration options

    Whether identity estates merge, coexist or synchronise, whether devices re-enrol in place or require a rebuild given the published requirements per platform, what residual configuration persists after unenrolment from another management provider, and what each option costs in effort and elapsed time.

  5. 5

    Deliver findings and a day one plan

    A short set of quantified findings in the form the transaction model uses, plus what must be true at completion, what must be remediated before environments are connected, and the sequenced integration plan. Written so it remains useful after signing rather than only before it.

Straight answers

What acquirers ask about IT due diligence.

What we ask for

Fifteen items, and the gaps in the answers are themselves findings.

Diligence works from whatever access is available, and a target that cannot produce these is telling you something useful about how the environment is run.

The estate

  • An asset and application inventory
    Its accuracy is a finding in itself.
  • Cloud environments and who pays for them
    Billing finds what registers miss.
  • Identity platform and directory structure
    It determines the integration path.
  • Device fleet by platform
    It determines the re-enrolment cost.
  • Network and connectivity arrangements
    Including anything site-specific.

Commercial

  • Total technology spend, all routes
    Not only the IT cost centre.
  • Contract list with terms and end dates
    And change of control provisions.
  • Licence agreements and entitlements
    Against what is configured.
  • Managed service arrangements
    And what they actually cover.
  • Committed cloud spend
    Commitments transfer.

People and risk

  • Who runs what, by name
    Key person dependency is the usual finding.
  • What documentation exists
    And when it was last accurate.
  • Recent incidents and their handling
    Both the events and the response.
  • Outstanding audit or regulatory findings
    They transfer.
  • Any known data protection exposure
    It becomes yours on completion.
Next step

Ask what proportion of the target device fleet is Apple. That answer has a number attached.

Tell us about transaction scope, available system records, access constraints and decision deadlines. We will confirm the requirements and proposed scope with you.