Legacy check
What your frontend can still carry and what it cannot.
Every new feature takes longer than the last, and the question of a rebuild is on the table. In the legacy check I assess the code, dependencies and release process of your frontend. You learn where the risks are and how to modernize step by step while your product keeps running.
What the legacy check examines
Code and architecture
I check structure, coupling and test coverage: which parts can be changed safely, and which ones are tied to everything?
Dependencies
I check frameworks and libraries: what is still maintained, where are security vulnerabilities open and what blocks an update?
Build and release
I check how a change gets to production: duration, manual steps and the places where errors slip through unnoticed.
What you have in hand after the legacy check
Risk assessment
The areas of your frontend, ranked by how urgently you need to act.
Prioritized findings
Every finding with its location in the code, impact and estimated effort.
Modernization roadmap
The steps in a sensible order, with a clear recommendation: convert step by step or rewrite individual parts.
Closing call
We go through the results together and answer your team's questions.
Example finding from a legacy check
This is how every finding in the report is structured. The example is made up and shows how specific the results are.
Finding
The application runs on AngularJS 1.6. The framework has not received security updates since early 2022.
Impact
New security vulnerabilities stay open, and 38 of the 54 views depend on one shared state. Switching in a single step would halt development for months.
Recommendation
Build new views in the target framework from now on and embed them in the existing application, replace old ones by usage. First step: cover the twelve most used views with tests.
How the audit works
Request the audit
You pick your audit and briefly describe your application.
Fixed price and analysis
You get the fixed price for your application, then I review it.
Findings and action plan
You receive prioritized findings and a plan for the next steps.
Frequently asked questions about the legacy check
Do you need access to our source code?
Yes, read access to the repository of the frontend. If you like, I sign a non-disclosure agreement beforehand.
Will you recommend a rebuild in the end?
Only if it pays off. In most cases a frontend can be modernized step by step while the product keeps running. The roadmap states the reasons for the recommendation so you can make the case internally.
What does the legacy check cost?
The legacy check comes at a fixed price from €1,500. I tell you the exact price before I start, it depends on the size of your application. If a follow-up project comes out of it, the audit price is credited towards it.
Do you also review the backend?
The legacy check covers the frontend and its interfaces. If it turns out that a cause lies in the backend, the report says so.
Request the audit or talk first
Request your audit directly and you get the fixed price and time frame, with no obligation. Not sure which audit fits? Then we sort that out in a free initial call.
Problem
Your frontend slows down every new feature
Code that grew over years, outdated frameworks and nobody dares to touch it anymore. I modernize step by step while your product keeps running.