Technical due diligence and stack inventory for an acquisition
Before the deal closes, build one inventory of what the target runs, who owns it, what it costs and what it is tied to. Every later decision, keep, merge, bridge or retire, starts from that list.
Technical due diligence is a structured look at the target's systems, data, security and people so the buyer prices risk and plans integration before signing. The core output is a stack inventory: every system, its owner, its contract and renewal terms, the data it holds, what it connects to and whether anything about it blocks or complicates a merge.
Google Workspace
Microsoft 365Salesforce
HubSpot
NetSuite
QuickBooksShopify
Snowflake
How to read this chart
The scores are our planning judgement for a typical small or mid-size deal: they show where effort tends to concentrate, not measured data. Replace them with your own once the inventory is done.
What does a stack inventory need to include?
For each system: what it does, who owns it, who uses it, what it costs, when the contract renews, what data it holds and what it connects to. A spreadsheet is enough if it is complete and has one owner.
- System name, vendor, plan and number of paid and active users.
- Business owner and technical owner by name, plus who holds admin rights.
- Contract term, renewal and notice dates, and any assignment or change-of-control wording.
- Data held, including personal and payment data, and where it is hosted.
- Inbound and outbound connections: other systems, automations and manual exports.
Which findings should change the deal, not just the plan?
Findings about data you may not lawfully hold or move, security incidents the seller has not disclosed, and contracts that cannot transfer are for deal counsel and price negotiation, not for the integration team to absorb.
- Customer or employee data collected without a clear basis to transfer it.
- Core systems that sit on a personal account or an unlicensed plan.
- A key platform whose contract needs the vendor's consent to assign.
- Security gaps that need money and time before you can connect the networks.
- Revenue that depends on a system you plan to retire.
Contract and privacy questions need your own lawyers. This guide is planning guidance, not legal advice.
How do you run diligence without slowing the deal?
Send one request list early, ask for read-only access or screen shares instead of exports where you can, and agree who on each side answers technical questions.
- Agree a short request list covering the eight areas in the table above.
- Hold a single working session per area with the target's system owner.
- Record every system in the inventory with an owner and a first guess: keep, merge, bridge or retire.
- Mark open questions and assign each to a person with a date.
- Hand the inventory to the integration lead as the starting point for the Day-1 plan.
Questions on this topic
Who should run technical due diligence?
A technical lead on the buyer's side, with the target's system owners answering. Smaller deals often use an outside advisor because there is no in-house IT team to spare.
How much of the inventory can the seller see?
That is a deal question. Before close, share only what the agreement and any clean-team rules allow, and keep customer and employee personal data out of the data room unless counsel agrees.
What if the target has no documentation at all?
Treat that as a finding. Build the inventory from admin consoles, invoices, the card statements that pay for software and interviews, then verify each entry with an owner.
Vendor documentation to check against
Microsoft 365 for enterprise documentation (Microsoft Learn)
Import your organization's data to Google Workspace (Google Workspace Admin Help)
Product details change. Confirm current options in each vendor's own documentation. Consultants in a Box is an independent consultancy; this page is not published or endorsed by any vendor named. Names and logos are trademarks of their owners.
Related guides
Day 1, 30 and 100 plan
Integration goes wrong when everything is urgent. Split the work into three checkpoints: keep the business running on Day 1, make the decisions by Day 30, and complete the moves by Day 100.
Read the guideRisk register
Most integration failures are predictable. A risk register makes them visible early, with an owner and a mitigation each.
Read the guideKeep, merge, bridge or retire
Every system in the inventory ends up in one of four places. Three questions decide which: is it still used, does the other company have an equivalent, and can you switch safely now?
Read the guideAll M&A tech stack guides
The full playbook, from diligence to synergy capture.
See the hubMerging two stacks?
Start with the free business analysis, or book a call and we will talk through both companies' systems and where to begin.
