Before you decide on modernization, see what's really in the system
We read the code, logs and database and talk to the people who work with the system. You get a risk map and a modernization plan split into priced phases.
What we check during the audit
The audit takes 2 business days and the system keeps running.
- 1Code and dependenciesFramework and library versions, untested areas, modules everything else depends on. We mark what can be replaced on its own and what's tangled together.
- 2Data and integrationsWhere the system gets data and where it sends it: the ERP, CSV files, old SOAP APIs, queries baked into the code. Every connection is a risk when things change.
- 3People and processesWe talk to the people who use and maintain the system. We find out which screens are critical and what everyone is afraid to touch.
- 4A phased planYou get a list of phases with the scope, order and price of each. You decide where we start, or whether we start at all.
Signs you need an audit before a rewrite
Nobody knows the whole system
Quotes are miles apart
Every change breaks something
The board wants a number
Audit results you can actually decide on
Written for the people who set the budget and for the technical team.
System map
Risk list
Phase plan
Rewrite or modernize
Quick fixes
Walkthrough meeting
How you'll know the audit was worth it
A good audit turns general worries into a concrete list of decisions, each with a cost attached.
- 1Modules with a risk rating
- 2Phases with scope and price
- 3Quick fixes to do now
- 4Board questions answered
You can carry out the plan with us or with any other team.
Common questions
Do we have to hire you for the modernization afterwards?
No. The plan is yours to carry out with any team, or to put on hold.
What do you need from us to start?
Access to the code, a description of the infrastructure and an hour with the people who know the system. Access can be read-only.
Will the audit interrupt the system?
No. We read code and logs, and we run tests on a copy, not in production.
What if the system has no documentation?
That's common. The system map from the audit is often the first documentation the company ever gets.
Describe your system
Tell us what technology it runs on, what it's used for and what causes the most trouble today. We reply within one business day.