Услуга · Consulting and audit

System and architecture audit

An outside view of what you have already built or are building right now. It is commissioned in three situations: before buying a company, when changing contractor, and when a project is in its second year with nothing to show.

From outside
we did not build this
What has accumulated
we price the fix
Risks
what collapses first
The report
in plain language

What the work includes

We assess against concrete criteria rather than taste: whether it will take growth, how easy it is to maintain, how well protected it is and whether everything depends on one person.

Discuss the scope

The design of the system

How justified the decisions are, where the bottlenecks are and what happens if the load doubles.

The code

Readability, whether there are tests, duplication, whether documentation exists at all.

The libraries in use

Outdated and abandoned components, and those with known vulnerabilities.

The accumulated debt

What was put off until later and what clearing that backlog would cost.

Dependence on individuals

Whether another team could pick it up or the knowledge lives in one developer's head.

The final document

A list of risks and proposals set out so that more than just a technical specialist can follow them.

How it goes

An average project is reviewed in two or three weeks including the interviews and writing the report.

01

Why we are looking

A transaction, a change of contractor, a risk assessment - the emphasis depends on the purpose.

02

We gather the material

We get the code, the documentation and access to the servers, and talk to the team.

03

We review

We test against the criteria and record the findings and what each of them threatens.

04

We write the conclusion

A report with the risks, the priorities and an estimate of what the fixes cost.

The most dangerous finding is usually not clumsy code but dependence on one person. The solution may be written without brilliance, but when exactly one person understands it and no documentation exists, the organisation is on their hook. We assess that risk separately from technical quality.

Questions and answers

Yes, that is the most common reason people come to us. An outside review gives a sober picture: what has been done, in what state it is and what it costs to take it on. With it in hand you discuss the matter on facts with both the previous contractor and the next one.

We are not looking for someone to blame; we describe the state of things and the risks. Nobody is being appraised. The report often turns out to help the team: arguments the developers have been making to management for years are finally heard from an independent source.

We will say it plainly, with reasoning and costings for both routes: repair or rewrite. The choice is yours, but it is wiser to base it on figures rather than impressions.

We will look at the system from outside

Tell us about the system and the purpose of the review. We will deliver a report with the risks ordered by importance.