A health check for your application
In two weeks, you know what your tool costs you, what will break first, and what you can save.
What you will know
Five questions almost nobody can put a figure on. The health check answers them, with your own numbers.
-
Your current maintenance cost
What does the tool really cost you each year, in invoices and in hours your team loses?
-
What will break first
Which part will give way first, and what stops on that day?
-
The savings to be made
How many hours of re-keying and workarounds could you win back, and at what price?
-
Your security exposure
What has not been updated, and who still has access to what?
And the question that decides what comes next: what does the tool cost if you keep it alive for another 12 months, compared with the price of a rebuild?
How we work
Management and the people who use the tool do not see the same thing. Sometimes management believes the tool is in use, while the team works around it with spreadsheets of its own. We listen to each separately, then we read the code.
-
One hour with management
What the tool must do for the business, what it costs, what worries you.
-
One hour with your users
Three to five people who use it every day, and who know where it gets stuck.
-
A reading of the code and the hosting
What the tool really does, where it runs, and in what state.
No individual is named in our findings. We describe the tool, not the people.
What you receive
A written report, which ends with three priced proposals.
The report describes the situation, the problem, what it means for the business, and what happens if nothing changes in the next 12 months. Before the proposals, we check with you that we have understood correctly.
-
The urgent fix
The fix we would not want to leave you without.
-
The pay-back module
The fix that pays for itself fastest, priced against the time you lose today.
-
The rebuild, estimated
Its cost, for comparison. Estimated, not proposed: it only comes if the figures justify it.
How much does a health check cost?
A health check costs under €3,000 excl. VAT. That fixed price covers the two weeks of work: one hour with management, one hour with your users, a reading of the code and the hosting, and the written report with its three priced proposals.
Why two weeks? Because it is work for senior developers, and we do it ourselves.
Frequently asked questions
What state is my application in?
That is the question the health check answers, in two weeks. We listen to management, then to your users, and we read the code and the hosting. You then know what the tool costs you, what will break first, what you can save and what has not been updated.
Is it an audit?
Not quite. An audit reports what it finds. The health check puts a figure on what the tool costs you, and ends with three proposals you are free not to follow. If you were looking for a "technical audit" of your application, the health check also covers a review of the code and the hosting, and adds the figures.
What if we do not have the source code?
That is where we start: recovering it is part of the health check.
And afterwards?
Nothing compulsory. The report is yours, and it is useful even if you never work with us again.
We already have developers. Is a health check any use to us?
Yes, if they are busy with new projects. The health check gives your team an outside view of the existing tools, with figures. Then, if it has no time to look after them, we take them over alongside your team, document them and hand them back. See when your team no longer has time.
The three-step takeover
The health check is the first step: scope. Then you decide.
What does your tool really cost you?
In two weeks, you will know.
Not ready yet? Take the free self‑assessment: ten questions, your score straight away.