Technical
due diligence
An independent read of what sits under a working demo — before an investment, an acquisition, or a decision to take development in-house.
What we assess
Each finding carries a business consequence and a cost to clear, not a severity label alone.
Architecture
Whether the system can carry the growth in the plan, or whether the next ten features each cost more than the last.
Code quality
Readability, duplication, test coverage and the real hours-per-feature cost of changing this codebase.
Security
Access control, secrets handling, dependency exposure and how personal or financial data is stored and deleted.
Team and process
Key-person risk, delivery discipline and whether anyone outside the current team could maintain the product.
How it runs
A fixed scope and a written report, not open-ended consulting.
Access and context
Repository, infrastructure and the thesis behind the deal. We assess the code against where the business intends to go, not an abstract ideal.
Review
Manual reading of the critical paths, backed by static analysis, dependency checks and measurements against the running system.
Report
Findings ranked by business impact with remediation effort and cost — a document an investor or board can act on, not a bug list.
What we can review
If the product runs on something else, ask — we will say honestly whether we can judge it.
AWSSigning a deal
on a demo?
Send us the repository and the timeline. We will scope the review and tell you what it will cost before starting.
