Service
Technical due diligence
An honest read on a codebase, a team and a platform before capital moves — findings ranked by consequence, with a costed plan.
What we do
We assess software the way we assess our own: what it would take to operate it, what it would take to change it, and what it will cost to fix the parts that will not survive growth.
That includes the things a code scan cannot tell you — whether the team can ship without one particular person, whether the deployment process is a ritual, and whether the numbers in the data room reconcile to the systems that produced them.
Scope
- Architecture, data model and code quality, with evidence
- Delivery practice: testing, review, release cadence, incident history
- Security posture and compliance exposure
- Infrastructure, scalability and run cost
- Team capability, concentration risk and hiring dependency
What you get
A written report with findings ranked by consequence rather than a score out of ten, a costed remediation plan sequenced by risk, and a call with your team to argue it through. Turnaround is typically two to three weeks, faster where the deal timetable demands it.
Who it is for
Investors and acquirers who need a technical read before committing. Boards inheriting a platform they did not commission. Founders who want the findings before a buyer produces their own version.