esedark
Menu
Back to notes

acquisitions / technical review / buyer

Technical due diligence consulting for an acquisition: what to commission

Before acquiring a business with its own software, distinguish verified findings from unanswered questions. The engagement should explain what you could operate, which dependencies you would inherit and what still needs checking.

Technical due diligence consulting should answer the buyer's questions about a specific product. A technology inventory and a risk traffic light are not enough. I would ask every conclusion to identify its supporting evidence, review date, coverage and implications for keeping the system running.

This is a bounded technical review before an acquisition. The fractional CTO guide covers the role and ongoing leadership. For an internal improvement decision outside an acquisition, the technology consulting guide explains how to commission that broader assessment.

Define what the buyer needs to know

I would start with the technical purpose of the acquisition: keeping the product, adding a capability to your systems or separating an application from the seller's other operations. Each scenario changes the questions. A standalone product needs an operating review; integration adds data compatibility; separation requires identifying services and people that may no longer be available.

The brief should name the products, repositories and environments included, essential workflows, shared dependencies, team members expected to remain available and the deadline for answers. Identify who can authorize access and who on the buyer's side will accept the report.

Agree a cutoff date and the version being examined. If the product changes during the engagement, identify which conclusions need another check. A seller presentation, an interview and an observed test are different sources. Keep that distinction visible in the report.

Choose the review depth and compare alternatives

An initial document review can identify missing information and scope a second phase. Code and operating reviews can investigate specific questions with authorized access. Specialist security or performance assessments need their own tests, boundaries and owners. Ask each proposal to specify which level it includes.

If the question is only whether to refactor an application, a scoped code audit may fit better. If your team already has the capacity and access, you might commission a second review of unresolved points only. I would not buy a broad assessment that can do little beyond repeat a demo because nobody will provide further evidence.

For each material dependency, ask the reviewer to compare keeping the product, configuring existing software, integrating with the buyer's systems or building a missing component. A rewrite should not be the default recommendation. Each option needs requirements, migration work and a maintenance owner. If there is not enough information to choose, leave the question open.

When selecting a consultant, request a sanitized example report, the names or roles of the people doing the work, their treatment of unconfirmed findings and any specialist coverage excluded. If they also propose the later integration, ask for a separate scope and disclosure of any relationship with the seller.

A matrix for comparing coverage and accepting the review

Give each bidder the same matrix. For every row, request included coverage, method, required access, owner and any additional cost. These are proposed commissioning criteria, not a certification or results from testing suppliers.

Evidence the buyer should receive
QuestionEvidence to examineReport acceptance criterion
What product was reviewed?Repositories, versions, environments and the relationship between components and essential workflows.A referenced coverage map that explicitly identifies missing components.
Who controls the dependencies?Accounts, services, libraries and available vendor and license documentation.An owner and third-party dependency for each item; contractual questions referred to legal review.
Can operations continue?Release procedures, incidents, backups and available recovery records.Documents, demonstrations and observed tests distinguished, with the limits of each check.
Which access and data are involved?Roles, privileged accounts, integrations and agreed samples without unnecessary data.Reviewed and unreviewed controls; sourced findings and proposed follow-up checks.
Who is needed to maintain it?Interviews, documentation, maintenance tasks and current responsibilities.People and supplier dependencies, required handover and an owner for each open item.
What work will transition require?Available costs, shared services, interfaces and migration requirements.One-time work separated from recurring spend, with assumptions, uncertainties and exclusions.

Alongside the matrix, request a findings register with an identifier, source, date, potential impact, confidence level, next check and owner. The buyer's summary should point to that detail. Missing access is neither a favorable result nor, by itself, proof of a defect.

Example: a product that depends on the departing supplier

Hypothetical example: a company offers an application that works in a demo. The repository is available, but its document-generation service runs in a supplier's account and only one person knows the deployment process. The demo does not establish how that workflow will continue under a new operator.

I would ask the reviewer to identify the component, its inputs and outputs, hosting account and available documentation. The scope could include an authorized demonstration in a separate environment. If that cannot be observed, the report must identify which conclusions still rely on the seller's explanation.

Technical options might include retaining the service temporarily, integrating an existing tool or replacing the component. Each needs an owner, access, a conditional estimate and a continuity check. A proposed test could process an agreed sample and reconcile the outputs without relying on the previous account. It should not be marked as passed until performed.

The buyer would receive the documented dependency and alternatives. Contractual and acquisition decisions remain with their respective owners; the technical review supplies evidence for those discussions.

Agree scope, exclusions and ownership of the deliverables

Specify the inventory, interviews, samples, methods and a schedule dependent on access. Agree how material findings will be communicated before the final report and how the seller can correct factual errors. Retain the original evidence alongside clarifications so the findings remain traceable.

Deliverables should include a summary, coverage matrix, findings register, open questions and a walkthrough. The buyer should retain editable documents and authorized references. Agree recipients, information handling and access removal. Credentials do not belong in the report.

Unless separately commissioned, I would exclude production changes, migration, code repairs, penetration testing, certifications and ongoing support. Legal review of ownership and licenses, financial valuation and the acquisition decision have separate owners. A technical inventory does not resolve those questions on its own.

Before accepting the work, check that every agreed question has a supported answer or an explicit limitation, contradictions remain visible and open items have owners. Accepting the report does not declare the product risk-free.

Separate review, implementation and maintenance costs

Review effort depends on system count, test depth, documentation quality, team access and shared dependencies. Request separate items for preparation, analysis, specialists, reporting, clarification and checks of subsequent changes. There is no universal fee or timeline, and I do not quote my services without defining that scope.

For transition, request estimates for licenses, configuration or development, integration, data cleanup and migration, testing, training and handover. For operations, account for infrastructure, vendor support, maintenance, incidents and internal team time. Include data export and component retirement if a different solution is chosen.

Compare the same period and distinguish documented amounts, estimates and unresolved costs. Paying for the review does not automatically commission its recommendations. If another dependency emerges, agree who can approve further investigation and when the budget must be revisited.

If the review finds that only the departing supplier can release or recover the product, turn that finding into a separately accepted implementation engagement. The DevOps consulting matrix defines configuration, permissions and a recovery rehearsal. Budget it separately: recommending the work in a report does not establish that it is complete or that the buyer can already operate the system.

What I need to scope your review

Tell me which product you are evaluating, what you expect to retain or integrate, the open technical decision and the transaction deadline. Add the known systems, available documentation, authorized access and buyer and seller contacts responsible for the review. A summary without confidential material is enough to start.

We can assess the scope within my technical consulting and leadership work. Review how to work with me or share the review context. First, we establish which questions I can cover and which specialist work needs another person.

Scope the review on WhatsApp