What is included

We assess against criteria rather than taste: scalability, maintainability, security and dependence on specific people.

Discuss the scope

Architecture

Whether the decisions are justified, where the bottlenecks are and whether it can take growth.

Code quality

Readability, test coverage, duplication and whether documentation exists.

Dependencies

Outdated and abandoned libraries, and components with known vulnerabilities.

Technical debt

What has accumulated and what it will cost to fix.

Dependence on people

Whether another team could continue the project or the knowledge sits in one developer head.

Report

A risk assessment and recommendations in language that non-technical readers can follow.

How the work runs

An audit of an average project takes two to three weeks including interviews and preparing the report.

01

Framing

Why the audit is needed: a deal, a change of contractor, a risk assessment. The emphasis follows from that.

02

Gathering material

Access to the code, documentation and infrastructure, plus interviews with the team.

03

Analysis

A check against the criteria, recording the findings and their consequences.

04

Report

A document with risks, priorities and an estimate of what fixing them costs.

The most serious risk we find is not bad code but dependence on one person. A system may be written unremarkably, but if only one developer understands it and there is no documentation, the company is held hostage. We assess that separately from technical quality.

Frequently asked questions

Yes, that is one of the main reasons for commissioning one. The audit gives an independent picture: what has been done, what condition it is in and what it costs to pick up. With that document, negotiations with both the outgoing and the new contractor become concrete.

An audit is not about finding someone to blame. We describe the state and the risks, not the people. The conclusions often help the team: what developers have been saying for a long time finally gets independent confirmation.

We will say so plainly, with reasoning and an assessment of both alternatives: continue or rewrite. The decision stays with you, but it is better made with figures than with feelings.

We will run an independent audit

Tell us what the system is and why you need an assessment. We will prepare a report with risks and priorities.