Why we don't start without an audit
We don't know software we did not build ourselves yet. The code contains choices by earlier developers that were never written down. Without an audit, a quotation for management or further development is a guess, for you and for us.
The audit is a fixed assignment at a fixed price. You are not tied to anything afterwards. If you choose another party, the report is still yours.
What we do in those two weeks
We set up the code on a test environment with us and run the software. Then we go through the code. We look at how it is structured, which versions of PHP, the framework and the packages it contains and where the integrations with other systems are. We also cover the servers, the backups and the access.

Halfway through, we plan a meeting with the people who use the software every day. They know where it falters. We then look up those points in the code.
What the report contains
- A description of how the software is put together, in plain language.
- The risks, sorted by how soon you need to act on them.
- The outdated parts and what it costs to update them.
- A plan for the first three months, with a budget per phase.
What happens next
We discuss the report with you in a one-hour meeting. Often the conclusion is that the software is good enough to build on, with a few parts that need attention first. Sometimes we advise rebuilding a part. The report then explains why.
If you continue with us, the takeover starts with the first item in the plan.

Serge Huijsen
Founder and developer
Serge started CodeIQ and still builds along. He leads most first conversations and sketches out the set-up of new platforms.
More about Serge





