Skip to content

Product engineering

Technical due diligence for founders and investors

Technical due diligence is an independent assessment of a company’s software, infrastructure, security, team and delivery process, produced for an investment round, an acquisition, or a founder who wants to know what an investor will find before they look. Hexploits delivers it as a fixed-price discovery: two to four weeks, a written report with findings ranked by risk, the cost to remediate each, and a recommendation, written in language a board and an investment committee can read.

A named engineer replies within one working day. A written scope and an indicative price within two.

  • Founders preparing for a seed, Series A or Series B round who want the technical narrative to hold.
  • Investors and acquirers who need an independent view of a target’s technology.
  • Boards of scale-ups where the technology is a risk nobody on the board can assess.
  • Founders considering an acquisition of a smaller company.

Deliverables, not slogans. Each one appears in the statement of work.

  • Architecture and codebase review: structure, quality, test coverage, dependencies, technical debt and the ability of a new engineer to change it.
  • Infrastructure and cost review: what it runs on, what it costs per customer, what it will cost at ten times the load, and what is single-point-of-failure.
  • Security review: identity, access, data handling, secrets, vulnerability management and what the first enterprise questionnaire will find.
  • Delivery and team review: how work is planned, shipped and supported, key-person dependencies, and what happens if a named engineer leaves.
  • A findings register ranked by risk, with the cost and time to remediate each, and a recommendation.
  • A board-ready summary and, for founders, a remediation plan to complete before the data room opens.

Our engineers work across the major languages, frameworks and cloud platforms. We build on the stack you already run, with technology choices explained in writing before work begins.

The same four stages as every Hexploits engagement, applied to this capability.

  1. Stage 1

    Scope

    One week. What the round or the deal turns on, what access is available, and who reads the report. Output: a fixed price and a date.

  2. Stage 2

    Assess

    Two to three weeks. Code, infrastructure and security access under a non-disclosure agreement, interviews with the team, and evidence gathered rather than asserted.

  3. Stage 3

    Report

    The written report, a findings register, and a presentation to the founders, the board or the investment committee.

  4. Stage 4

    Remediate

    Optional. The findings that matter fixed by the same team on a fixed price per phase, before or after the round.

Every engagement agrees its measures and the measurement period in writing before work starts.

  • A report the investment committee accepts without a second review.
  • Findings ranked by risk with a remediation cost against each.
  • For founders: technical questions in the data room answered from the report rather than from memory.
  • For acquirers: integration cost and risk known before the price is agreed.

Case studies with numbers, and reviews linked to Google where they were left there.

  • Director, Gradvisor

    Fantastic company and our development partner for Gradvisor, a social mobility careers platform with national ambitions. Extremely responsive and mission-oriented. Cameron owns any shortfalls humbly - rare for IT providers. Thinks like a client too.

    Tushar PrabhuDirector, GradvisorRead the review
  • Director, Lothbury

    Top quality delivery, and reasonable price. Will be using again.

    Peter DentonDirector, LothburyRead the review
What does technical due diligence cost?
It is delivered as discovery and assessment: from £4,000 fixed for a defined scope, two to four weeks. The figure depends on the size of the codebase, the infrastructure and the depth the deal requires, and comes with the written proposal.
Can you do it for the founder’s side?
Yes, and it is often the better use. A founder who commissions the assessment before the round knows what the investor will find, fixes what matters, and writes the technical narrative from evidence.
Do you need full access to the code?
Read access to the repositories, the cloud accounts and the delivery tooling, under NDA, with our engineers working in virtualised environments so nothing is copied to a device. Where access is limited, the report says what could and could not be verified.
How independent is it?
The report says what we found. If we recommend remediation, the findings and their costs are set out so that you can take them to any supplier, including your own team.
What if the findings are bad?
Then you know before the investor does, which is the point. Most findings are fixable at a known cost, and a remediation plan with dates is a stronger data-room document than a clean report nobody believes.

Sectors where this is most often needed

Request a proposal.

Tell us about the system and the sector. A named engineer replies within one working day. A written scope and an indicative price within two working days of a short scoping call.