A second opinion on the technology behind the deal.

For private equity funds and institutional investors. We review how the software was built, who can run it and what it will cost to scale, and write it up for the investment committee.

Request a Due Diligence

Management decks don’t show technical debt.

Code quality, architecture, security, key-person risk and the substance behind the AI claims decide what a software business is worth after closing. We look at all of them with the eyes of the engineers who would have to run it.

What the review covers

Code and architecture

Quality, maintainability and scalability, and what the technical debt we find will cost.

Security and compliance

Vulnerabilities, data protection, open-source licences and IP ownership.

Team and delivery

Key-person risks, the delivery process and what the team can realistically build next.

How a due diligence runs

Scope with the deal team

Code and architecture review

Team interviews

Report and red flags

What we value in working together

Working at eye level

We don't arrive with ready-made answers. You know your domain, we bring product, engineering and AI experience, and we build the solution together, in your language.

Where business, product and tech meet

We work at the intersection of business, product and technology. One interdisciplinary team brings strategy, product, engineering and AI together and translates between them, so nothing gets lost in handovers.

The courage to change

Markets move and change is the new normal. Call it agile, new work or OKRs, ideas alone are not enough. We make the change happen and stay until it works.

Questions you might have

How long does a technical due diligence take?

It depends on the size of the product and the deal timeline. We agree a fixed scope and delivery date before we start.

Do you need access to the source code?

Yes, read-only. Where that is not possible we work from documentation, architecture walkthroughs and interviews, and state clearly what we could not verify.