Technology Due Diligence
See what you are buying before you sign, in code, contracts and cost.
Why It Matters
A deal moves faster than the technology review. The buyer sees demonstrations, a data room and a summary, but not the code, the contracts or the real running cost. The gaps appear after completion, when the price is fixed.
Deals go wrong when the technology is checked too lightly. The review stays at the level of slides. Hidden licence and platform costs are left out of the price. No one plans for separating the systems on day one. Each surprise lands on the buyer.
What We Do
Due Diligence for Investors and Acquisitions
A clear view of the technology risk and value in a deal, with the evidence behind each finding.
Architecture and Code Quality Review
We read the estate and report what it will cost to own, change and scale.
Security and Scalability Risks
The weaknesses that could stop growth or expose the business, ranked for the deal.
Integration and Separation Planning
How to join the systems, or split them cleanly after a sale, with dependencies and owners.
What Changes for You
A Costed View
The licence, platform, maintenance and people costs the business will carry after completion, with the evidence behind each figure.
Risks Ranked for the Deal
The technical, security and contract risks that should change the price, the conditions or the decision.
A Plan for Day One
What must be separated, transferred or kept running in the first weeks, with owners and dependencies.
What We Assess
We look at the parts a deal summary leaves out.
Code and Architecture
We read the code, the tests, the architecture and the deployment. We look for key-person knowledge, undocumented workarounds and parts that cannot scale.
Platforms and Contracts
We review licences, cloud commitments, support terms and exit routes. We compare the contracted cost with what the business actually uses.
Security and Data
We review access, encryption, backups, incidents and data flows. We check whether the controls operate, not only whether a policy exists.
People and Delivery
We review the team, the suppliers, the delivery record and the open work. We name the knowledge that would leave with a person and what can be taught before completion.
Method
The review is fixed in scope and evidence, so the report can support a price or a condition.
Agree Scope and Access
We agree the questions the deal needs answered, the systems in scope and the timetable. You provide the data room, code access, contracts and interviews. You confirm what is out of scope.
Inspect the Evidence
We read the code and contracts, run the tests you allow, review the cloud bills and interview the team. We share interim findings early so the deal team can act. We keep a list of what we could not see.
Cost and Rank
We model the costs after completion and rank each finding by its effect on the deal. You decide the risk you can accept and which findings need a price or a condition. Every finding cites its evidence.
Report and Brief
We write the report and brief the deal team in person. You decide the next steps. The report is yours, and another adviser can rely on its evidence.
The Report You Receive
The report separates what we verified from what we could not see.
Findings and Evidence
Each finding states what we saw, why it matters and the evidence behind it. We separate what we verified from what we could not.
Price and Conditions
Findings that should change the price or the contract terms, with a suggested condition for each. You decide how to use them.
The First Weeks
What must happen on day one, who owns it and what depends on it. The plan covers separation, access, contracts and the team.
What Happens Next
You decide what happens after the report.
The report can support a price, a condition or a decision to walk away. Our engineering teams can plan the separation or integration after completion as a separate engagement. Another supplier can also use the report, because every finding cites its evidence. We brief the people who will own the systems after completion.
Industries
Healthcare
Patient apps, scheduling and billing, and clinical data integrations, engineered for health-data protection.
Retail and Omnichannel Commerce
POS integration, stock and price sync, card payments, loyalty and e-commerce for retailers with many sites.
Software and Technology Companies
Software companies and technology teams: multi-tenant products, platforms and the AI features and billing that keep them growing.
Questions
The questions deal teams ask before they commission a review.
What drives the cost?
The number of systems, the depth of the code review and how many contracts and platforms are in scope. A focused review of one business costs less than a group-wide one. We agree the questions and the timetable first.
How long does it take?
A focused review can run in a few weeks, and a larger one takes longer. The deal timetable sets the limit. We agree the date and what can be covered by then.
How do we start, and what access do you need?
The data room, read access to the code and contracts, the cloud bills and interviews with the team. We work under your confidentiality terms. If something is missing, we record it as not seen.
What will the report contain?
The findings, the evidence, the costs after completion, the risks ranked for the deal and a plan for the first weeks. It separates what we verified from what we could not. You own it.
What is not covered?
We do not provide legal, tax or financial advice. We also do not integrate or separate the systems in this service; that is a separate engagement after the deal. We can plan it with you.
Tell Us What You Need to Run, Build or Secure.
Describe the service, the systems and the pressure you are under. The right team takes it from there.