Will you be able to keep changing it?
We identify today the areas that will cause pain tomorrow.
- Hard-to-maintain code
- Risky dependencies
- Duplicated code
- Areas where any change is a gamble
Software audit
Do you know what is underneath your software?
It works, yes. But if nobody knows how it is built, every change is a gamble. We audit it before you invest more in it.
Audit from €1,000 · 5–7 days of analysis depending on the size of the system · The report is yours even if you decide not to continue with us
Signs
It works. But something is not right.
If two or more of these sound familiar, your software needs an audit before it grows further.
- It works today, but every change breaks something else.
- Nobody on your team really knows how it is built.
- The original developer has gone, and so has the documentation.
- You are afraid to add more features because something will break.
- It has already failed once. And you worry it will happen again.
A specific case
Did you build it with ChatGPT, Claude, Cursor or Copilot?
That does not mean it is bad. Generating software quickly can also generate technical debt quickly: code that is difficult to maintain, inconsistent decisions and dependencies nobody reviewed.
An audit lets you know where you stand before you keep building.
- Dedicated audit of AI-generated code
- Detection of data hallucinations
- Cost per call to external APIs
- Supplier dependency
What could end up costing you money.
We review what really matters to your business, not what sounds technical.
Will it cope as you grow?
Performance, database and infrastructure under real load.
Does it comply with the GDPR?
Data, access and intellectual property.
The aim is not to tell you that your software is bad. It is to tell you exactly what you have and the risks of carrying on.
Not just theory
We audit the kind of systems we also build.
This is software in production. We design, develop, deploy and maintain real systems. That is why our audit goes beyond reviewing code: we analyse how the software actually works within a business.
This is not the first time something has been built too quickly.
Every technology wave has promised speed, and the same bill has always followed: systems that grew faster than anyone could understand them. We have spent over 25 years in the market watching it happen.
- 2000
HTML and dedicated servers
Websites were written by hand and each project lived on its own machine.
- 2005
Web 2.0 and CMS
Content becomes separate from code and no longer depends on the developer.
- 2008
Virtualisation and LXC/LXD
Several machines within one. Hardware is no longer the limit.
- 2014
Cloud, Docker and Kubernetes
Infrastructure is defined in a file instead of being bought.
- 2022
Generative AI today
Writing software gets faster. Understanding it does not.
That is why we do not audit whether the chosen technology is fashionable, but whether it will stand up to what your business needs over the coming years. It is the same question as always, with today's tools.
What is written quickly is maintained slowly by someone else.
Before you contact us
Who this audit is for, and who it is not for.
A good fit if…
- You have business-critical software and no in-house technical team to review it.
- A freelancer or external company built it and no longer responds, or did not hand it over properly.
- You built it, or had it built, with ChatGPT, Claude, Cursor or Copilot, and it has grown faster than your control over it.
- You inherited it from a previous partner and nobody on your team knows how it is put together.
- It has grown without an architecture and every change feels like walking on broken glass.
- You are considering migrating, modernising or rewriting it and need to know whether it is worthwhile.
Not a good fit if…
- You only need to add a small feature. A freelancer can handle that.
- You are looking for the cheapest possible quote. This is a professional diagnosis, not a rubber stamp.
- You do not have access to the source code. Without access, an audit is not possible.
- The software is not important to your operations. If it fails, nothing happens.
This audit makes sense when you need to know whether it is worth continuing to build on what you have.
How an audit unfolds
A technical decision should not feel like an act of faith.
Starting point
The problem rarely starts in the code.
An initial meeting establishes the context, the objective and what must not fail. Only then does it make sense to request access and start looking.
Your contribution Context, key people and available access.
Reading the system
We get into the product to find its real limits.
We review the repository, deployment, integrations and tests in an isolated environment. Architecture is understood by following its dependencies, not by reading a summary.
Our focus Structure, tests and points of failure.
Technical judgement
A list of errors does not help you prioritise.
We turn scattered findings into risks with context. We distinguish what is inconvenient today from what could block operations, costs or growth tomorrow.
Outcome Clear priorities and the cost of not acting.
Delivery
The technical work must make the business decision clear.
We deliver the diagnosis and walk through it with you. The aim is not to impress with jargon, but to help you understand what is worth doing and why.
You receive Report, priorities and a roadmap.
Next move
You finish with your own judgement, not another dependency.
You decide whether to fix, rebuild, prioritise one part or continue with your team. If you need help implementing it, we discuss that separately, with the report already on the table.
No lock-in Implement the plan with whoever you choose.
Investment
From €1,000
The price depends on the size and complexity of the system. Fixed quote before work begins.
- Initial meeting with no obligation
- Technical report in PDF
- Prioritised list of issues
- Action plan with timings
- One-hour handover meeting
- The report is always yours
Tell us what you have.
Unsure whether your software is well built? Request an initial assessment. No obligation. We reply within 24 working hours.
Would you rather talk directly?
Frequently asked questions.
The most common questions before getting started.
Do you audit software generated with ChatGPT, Claude, Cursor or Copilot?
Yes. This is precisely the kind of software that most needs an audit: it was generated quickly, with little visibility of what was generated or how, and it often has hidden technical debt.
How much does the audit cost?
From €1,000, depending on size and complexity. We confirm the quote after the first meeting, with no obligation.
How long does the report take?
Between 5 and 7 working days, depending on the size of the system. The first meeting lasts 30 minutes and is scheduled within 48 hours.
Do I need to give you access to the source code?
Yes. Without access to the code, we cannot audit it. If a supplier built it and did not hand it over, we explain how to request it and, where possible, may still be able to audit the binary or its behaviour.
Does the audit commit me to hiring you for development?
No. The report is yours. You can implement it with us, your in-house team or whoever you prefer. If you continue with us, the audit fee is deducted from the remediation quote.
Can you audit the backend and frontend separately?
Yes. We can audit just one layer if you wish. But the problem is usually in how they connect, so we generally recommend looking at both.
Do you also carry out remediation?
Yes, under a separate quote based on the report itself: issues are already prioritised and costed, so you can start with the most urgent ones without repeating the analysis. Your team or another supplier can also carry it out; the plan is equally useful.
The report is yours, whatever you decide.
Start with a 30-minute meeting. If you then prefer to implement it with your team or another supplier, you still take the diagnosis with you.