Service 05 / 05
A senior review of your codebase, and a plan to fix it.
When software someone else wrote has become slow, fragile or impossible to change, we tell you plainly what is wrong and what it takes to fix it.
What you get
A written diagnosis, not a sales pitch.
We read the code, run the software, and talk to the people who use it and the people who maintain it. Then we write down what we found and what we would do, step by step.
- Architecture and code. Where the structure helps, where it fights you, and why changes keep breaking things.
- Security. Keys, encryption, updates, and where data is exposed.
- Data and sync. Lost edits, duplicates, conflicts and what happens offline.
- Build and release. How the software is built, tested, signed and shipped.
- A plan with prices. What to keep, what to correct and what to rewrite, in order, each step with a fixed price.
Sometimes the plan is "keep most of it". We'll say so.
How it works
Read, run, write it down.
- Access. Read access to the code and its documentation, and a person who knows the history.
- Review. We read the code, run the software and interview its users and maintainers.
- Report. A written report and a prioritised plan, which we walk through with you.
- Fix, if you want. We can carry out the plan in milestones at fixed prices, or hand it to your team.
Good fit when
Something has to change.
- The team that built your software has left.
- The app loses data, duplicates records or breaks when the connection drops.
- Every change breaks something else.
- You want a second opinion before paying for a rewrite.
--- Questions
How long does an audit take?
An audit is a Discovery engagement: usually one to three weeks, at a fixed fee agreed in advance.
Do we have to hire you for the fixes?
No. The report and the plan are yours. Your own team, or anyone else, can carry them out.
What do you need from us?
Read access to the code and its documentation, a contact person, and, if possible, access to a running copy of the software.