Transactions
Before you sign, someone should read the system as carefully as the lawyers read the contract. We do both — technical and commercial diligence with legal competence in-house rather than referred out.
You are probably reading this because:
The target's revenue is verifiable and its platform is not.
Technical diligence came back as a list of frameworks rather than a judgement about risk.
The contract allocates risks the technical reality does not match.
You are buying a team, a codebase and a set of liabilities, and only one of the three has been priced.
- 01
Technical due diligence
What has actually been built, what it depends on, what is licensed rather than owned, what the real key-person risk is, and what it costs to run and to change after completion.
- 02
Data and IP position
What data the target holds, on what lawful basis, whether it can be transferred, and whether the intellectual property is where the deal documents assume it is. Contractor-built code is a recurring surprise.
- 03
Commercial and structural review
Revenue quality, customer concentration, the durability of the model, and whether the growth being priced is structural or borrowed from a channel that is about to close.
- 04
Deal documentation review
Reading the transaction documents against the technical findings, so the warranties and indemnities cover the risks that were actually found. Led by an LL.M in International Business Law from the University of London, awarded with Merit.
- 01
A diligence report with findings ranked by effect on value
- 02
A risk register mapped to the deal documents
- 03
Post-completion integration and remediation cost, estimated rather than gestured at
- 04
A direct view on whether the price reflects what is being bought
Invariant
Price the system you are buying, not the one in the data room.
- Do you act as legal counsel?
- We provide legal competence in the review — reading and assessing documents against technical findings — and we work alongside your appointed counsel of record rather than replacing them.
- How fast can diligence run?
- A focused technical and commercial review runs two to four weeks depending on the target's size and how organised the data room is. Where the timetable is shorter, we say what we could not cover instead of implying coverage.
- Do you work on the sell side?
- Yes. Finding what a buyer's diligence would find, before they do, is generally the cheapest value protection available to a seller.