The method
Four readings that establish what a technology asset really is
Each reading looks at a different layer of the asset, and each produces evidence a deal team can act on rather than an engineer’s impression.
The code as it is
We read the repository itself — its structure, its history, its dependency health, its security posture — because the code records what was actually done in a way no presentation can edit. A factual account of code quality and the debt it carries.
The architecture under the diagrams
We trace how the system is actually put together and test it against the growth the deal assumes — more users, more markets, more integrations — to see which assumptions hold. The gap, if any, between the drawn architecture and the running one.
The team and the bus factor
We establish how knowledge is distributed: who can change the critical parts, what leaves with one resignation, and whether the practices that produced the code survive the people who wrote it. The dependency on individuals, named while it can still be priced.
The path to production
We examine how a change becomes a release — testing, deployment, rollback, monitoring — because a team that cannot ship safely will not deliver the roadmap the valuation rests on. A verdict on whether the roadmap is deliverable by this machine.
Why it matters
The two stories every deal room contains
A pitch deck is written to close a deal; a codebase is written under deadlines by people solving that week’s problem. Neither is lying, but they answer to different incentives, and the distance between them is where deal risk lives: the "platform" that is one client’s customised build, the "AI engine" that is a set of rules, the "scalable architecture" that has never carried more than the current load. None of these are unusual, and none are visible from a demo.
The purpose of the review is not to kill deals. Most findings are priced, not fatal: a dependency that needs replacing, a module only one person understands, a test gap that adds a quarter to the integration plan. What changes is that the buyer negotiates knowing these things, instead of discovering them in the first year of ownership, when they cost the most and can no longer move the price.
What it looks like
A vendor platform reviewed before a five-year commitment
Illustrative engagement
An organisation is about to commit to a vendor’s platform for a core operation. The demonstrations are convincing, the references are warm, and the contract is long. Procurement wants an independent view of what is under the surface before signing.
- 01A structured review under NDA: the architecture against the promised roadmap, the release history as evidence of delivery pace, the dependency and security posture, and how much of the product is configurable versus promised custom work.
- 02Findings framed for the negotiation: which gaps are normal for a product of this age, which need contractual commitments with dates, and which should change the exit and escrow terms.
The organisation signs with open eyes: the same vendor, a sharper contract, and a remediation schedule agreed before the dependency exists rather than argued about after it does.
Our role
What our review delivers and what stays with your deal team
- 01
Independence by design
We have no stake in the deal closing or failing, and the review is structured so a finding cannot be softened by the relationship — the evidence is quoted, not paraphrased.
- 02
Findings priced in effort
Every material finding comes with the work needed to remedy it, described by its drivers, so it can enter the negotiation as a cost rather than sit in the report as an adjective.
- 03
A report two audiences can use
The findings are written twice: an engineering appendix your technical people can verify, and a summary the board can read without translation, saying what should change in the deal.
Whether to proceed, at what price and on what terms is your call and your advisers’; we make sure that call is made on what the technology is, not on what the deck says it is.
Common questions
What buyers ask
What does technical due diligence examine that financial due diligence misses?+
The asset itself. Financial diligence verifies the numbers around the business; technical diligence verifies the machine those numbers depend on — whether the code can carry the growth in the model, whether the architecture matches what was presented, whether the team that built it will still be able to change it in a year. A company can have clean accounts and a codebase that makes the roadmap in the valuation undeliverable, and only one of those shows up in a data room spreadsheet.
Can a code review run without disrupting the target’s engineers?+
Yes, and it should. Most of the review is done by reading — the repository, its history, the dependency tree, the deployment configuration — under NDA and with access agreed in advance, which needs little of the team’s time. The interviews that follow are short and specific because the reading has already produced the questions. A review that occupies the target’s engineers for weeks is badly scoped, and it also distorts what it measures: you learn more from how a team ships in a normal fortnight than from how it performs under inspection.
At what point in a deal should the technical review happen?+
After serious intent, before the terms are final. Too early and the target will reasonably refuse deep access; too late and the findings can no longer move the price, only the buyer’s mood. The practical window is alongside the other diligence workstreams, once exclusivity or a letter of intent justifies access — with enough calendar left that a material finding can still translate into a price adjustment, a warranty, or a remediation condition rather than a shrug.
In this cluster
Next step
Scope the review
A scoping call that fixes what the review must answer for this deal, who needs access to what, and the date the deal team gets the findings.
Scope the review
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

