Skip to content
KYE Ventures

Technical due diligence, inside and out

One report, read from the inside and the outside.

A signed review of the code, the architecture, the infrastructure and the team, joined with an outside-in review of the attack surface and dark web exposure. Written for the person who has to decide, not for the engineer.

Who it is for

  • Investors with a term sheet or letter of intent and a clock running.
  • Firms reviewing a company they already hold, before a new round or an exit.
  • Founders about to raise or sell who would rather find the problems before the buyer does.

The two halves

From the inside: Nathan Biles

Read-only repository access under a mutual NDA. Five axes, each rated, each finding backed by evidence down to file and line, with the business impact in plain language:

  • Architecture
  • Security in the code and the pipeline
  • Code quality and tests
  • Infrastructure and operations
  • Team and key-person risk

Plus a dependency and license inventory with end-of-life and advisory checks.

From the outside: our security partner

  • The external attack surface: domains, exposed services, email security.
  • Dark web and breach exposure for the company and its key people.
  • A score and a prioritized list of fixes.

What you receive

  • The three findings that most affect value, and a go, caution or stop recommendation with the conditions attached.
  • A 30, 60 and 90 day remediation plan with engineer-day estimates you can use in the negotiation.
  • A readout call with the people who signed it.
  • Two signers. Each signs the part they reviewed.

Fixed-price, scoped to the company and the work, and agreed in writing before work starts.

How it works

  1. 1.Scope.A short call on the company, the timeline and the access. A fixed price in writing.
  2. 2.Access.Read-only repository access and a mutual NDA. The outside review needs only the company name, its domains and its key people, with consent.
  3. 3.Review.AI coding agents do the volume of reading. Nathan reviews every finding, decides every rating and signs his part by name. The security partner does the same for its part.
  4. 4.Readout.One report, one call.

Also: advisory

Already have a CTO, or about to hire one? A senior second opinion on architecture, AI, build or buy, and team decisions, scoped as a short engagement.

Book a strategy call

What the report is and is not

The report is an expert opinion on the code, the infrastructure, the security and the team as observed during the engagement. It is not a warranty and it does not replace legal, financial or commercial diligence. Where a finding is inferred rather than verified, the report says so. It is not a recommendation to invest or not to invest.

See the depth before you buy

A sample report on an anonymized software company, with the full 40-item checklist.

Questions

How long does it take?
Usually five business days from access to report for one product. Larger scopes are quoted in writing.
What does it cost?
It is fixed-price, scoped to the size of the codebase and the work, and agreed in writing before work starts.
Who signs the report?
Nathan signs the inside review; the security partner signs the outside review.
Can I get only one half?
Yes. Either half can run alone.