---
title: "Before you keep it or rebuild it, you need to know what is actually there."
description: "An audit of the code, the deployment and the data: risks, maintenance costs, a plan for putting things right, and a costed comparison between keeping and rebuilding."
url: "https://francaisedulogiciel.fr/en/audit"
language: "en-GB"
---

# Before you keep it or rebuild it, you need to know what is actually there.

We examine your application and the technical environment around it without assuming the answer. The point is not to find fault, it is to give you the technical and financial grounds to decide what happens next.

## What we look at

### The code

Architecture, readability, dependencies, tests, security, and whether a new team could take it on without starting over.

### The technical environment

Deployments, backups, monitoring, environments and the access that keeps the application running. Above all, whatever could take the service down.

### The data

Structure, quality, duplicates, access rights, flows and the migrations to plan for. A rebuild that works usually starts by working out what has to survive.

### The hidden costs

Licences, infrastructure bills, manual work, and the hours people spend working around the tool. The real cost is not all in the code.

## A clear scope before we start

We audit the application and what keeps it running: its code, its architecture, its deployment, its database and its data flows. We do not dress that up as a full audit of your information systems.

If the diagnosis needs to cover offensive security, networks, complex infrastructure or regulatory compliance, we bring in the specialists first and propose a scope and a price after that.

## What you take away

Not a document for developers only. Something management, the business teams and the technical team can read together and decide from.

### A report you can read

Findings in plain language, backed by evidence and sorted by how much risk they carry.

### A plan of action

What to secure now, what to put right next, and what can reasonably wait.

### A costed estimate

What putting things right would cost and how long it would take, with the assumptions stated and anything left out of scope.

### A reasoned choice

Keeping it or rebuilding it, compared on cost, time, risk and how long each would last.

## How an audit runs

### Scoping

We talk to the people who use the tool, the people who maintain it and the people who pay for it, so we understand the context as well as the symptoms.

### Analysis

We work through the code, the data, the documentation and production with the right access. Every finding that matters gets verified.

### Findings

We present the conclusions, answer questions and hand over the documents. You can use them with us or with anyone else.

## An audit is not an excuse to rebuild everything

An imperfect codebase can still be sound, worth keeping and possible to take on. We separate the flaws that are merely irritating from the risks that threaten the business.

If what you have can be steadied, we set out a path to take it on in stages. If starting again costs less or carries less risk over the medium term, we say so, using the same figures.

> The conclusion has to hold even if you hand the work to someone else.

## See also

- [This page in Français](https://francaisedulogiciel.fr/audit)
- [Home](https://francaisedulogiciel.fr/en)
- [Every page](https://francaisedulogiciel.fr/sitemap.xml)