Skip to content
Arson Tech

Technical audit

Technical audit and code audit

We take the product apart: code, architecture, infrastructure, tech debt. In 10 days you get a roadmap with an estimate, not an opinion. Works as technical due diligence before a deal.

10 days
typical timeline

For a product up to 300k lines and one team.

4
views

Code, architecture, infrastructure, process.

90 days
roadmap

What to do in the first three months, in which order.

1
estimate

The cost of fixes comes with the report, not in the next contract.

Who needs it

When the product works, but nobody knows how long it will last or what growth will cost.

A new CTO or owner

You inherit someone else's code and want to know what is inside before the first incident.

An investor or buyer

Technical due diligence: the real state of the product and hidden liabilities.

Slow delivery

Monthly releases, bugs after each one, a team afraid to touch the code.

Changing vendors

The previous team left; the new one needs a map and priorities.

What we review

Four views of one product

Problems rarely live in one place: bad code is often an architecture symptom, slow releases a process symptom.

Code

Quality, tests and coverage, dependencies and their vulnerabilities, duplication, complexity, stack conventions.

Architecture

Module boundaries, data, integrations, performance bottlenecks, scalability, single points of failure.

Infrastructure

Environments, CI/CD, monitoring, backups, cloud cost, configuration security.

Process

How work is planned, reviewed and released; bus factor; documentation.

What you get

Documents you can decide and negotiate with.

  • Report across four views with severity
  • Tech debt map: what hurts now, what will in a year
  • 90-day roadmap in order of work
  • Estimate for fixes by our team or yours
  • Deal risk assessment
  • Debrief call for technical and business sides

How it works

  1. 130 minutes

    Call

    Goals: growth, deal, team change. Access.

  2. 22–3 days

    Immersion

    Code, infrastructure, docs, developer interviews.

  3. 34–5 days

    Analysis

    Static analysis, architecture sessions, hypothesis checks.

  4. 41–2 days

    Report and roadmap

    Findings, priorities, estimate. Team debrief.

Formats and pricing

Fixed price after a call and a look at the repository.

Express

fixed

One service or site

  • Code and dependencies
  • Infrastructure overview
  • Top 10 issues
  • 3–5 days
Get an estimate in 1 day

Full

quoted

Product and team

  • Four views
  • Tech debt map
  • 90-day roadmap
  • Estimate
  • 10 days
Get an estimate in 1 day

Due diligence

quoted

For an investor or buyer

  • Everything in Full
  • Deal risk assessment
  • Code ownership and licence check
  • Board summary
Get an estimate in 1 day

We work under NDA with read-only access and deploy nothing in our environment without agreement.

FAQ

Let's talk

An estimate within one business day. No spam, no sales calls.