Know What Your Legacy
System Actually Contains
A 2 weeks, fixed-scope engagement ending in a written assessment: what is really inside your .NET application, where the genuine risks are, what modernising it would cost, and the order to do it in. $3,500, and the fee comes back to you if you proceed.
Why this is paid, and why it isn't really a cost: a credible modernisation plan requires reading your code, not listening to a pitch — so it takes real time and it is charged for. The fee is credited in full against the modernisation project if you proceed within 90 days. In practice that makes it a deposit rather than a fee, and the only way you end up out of pocket is if the answer turns out to be “leave this system alone” — in which case you have a written case for not spending a modernisation budget, which is worth considerably more than the assessment cost.Not ready for this yet? Start with the free 45-minute diagnostic →
Everyone Agrees It Needs Doing.
Nobody Can Size It.
Legacy modernisation stalls at the estimate. Without knowing what is actually in there, every number is a guess and everyone knows it.
The Original Authors Have Gone
Business rules live in the code and nowhere else. The people who knew why a particular calculation works that way left years ago, and the documentation (if it exists) describes an earlier version of the system.
Nobody Knows What Will Break
There is a reason nobody touches certain modules. Without a dependency map and a real assessment of test coverage, every change is a gamble with a live business process.
The Estimates Vary By 10x
One vendor says six weeks, another says a year. Both are guessing because neither has read the code. You cannot approve a budget against a range that wide, so nothing gets approved.
Rewrite vs Migrate Is Unresolved
The rewrite promises a clean slate and routinely takes three times as long as forecast. Incremental migration is slower to feel exciting and far more likely to finish. Choosing needs evidence, not preference.
Read the Code First,
Then Give You a Number
We go through the system itself: its structure, its dependencies, its data access patterns, its test coverage, its deployment path and report what we find rather than what would be convenient to find. Some of what we report will be reassuring: legacy systems that have run for fifteen years have survived real-world chaos, and that resilience deserves respect. Some of it will not be. Either way you get a sized, ordered plan instead of a range, and you own the analysis whether or not you use us to execute it.
A system running in production for fifteen years is not a liability by default. Sometimes the correct recommendation is to upgrade the framework, fix the deployment, and leave the business logic exactly where it is.
What You Receive
A written assessment, walked through with your team. Yours to keep, whether or not you work with us afterwards.
System & Dependency Map
What the application is actually composed of: modules, services, third-party and framework dependencies, integration points, and the versions you are pinned to, including any that are out of support.
Risk Register
Specific, named risks rather than general warnings: unsupported components, security exposure, single points of failure, areas with no test coverage, and the parts where change is genuinely dangerous.
Rewrite vs Migrate Recommendation
A reasoned position on incremental migration versus rebuild, per module rather than for the whole system because the answer is rarely the same throughout an estate of any size.
Phased Migration Plan
The order to do things in, with dependencies between phases made explicit, so each step leaves you with a working system and the business keeps running throughout.
Effort & Cost Sizing
Estimated effort per phase with the assumptions shown, so your team can challenge them. Where we genuinely cannot size something without further investigation, we say that rather than pad the number.
Costed Next Step
A scoped proposal for the first phase, or a written explanation of why the system should be left as it is, which is a legitimate and reasonably common outcome.
Two Weeks, Four Stages
Roughly six to eight hours of your team's time. We need read access to the code and a conversation with whoever knows it best.
Kick-off & Access
NDA first. Then a working session on what the system does for the business, what hurts today, and what has already been attempted, plus read access to the repository and a walkthrough from your team.
Code & Architecture Review
We go through the codebase directly: structure, dependencies, framework versions, data access patterns, test coverage, build and deployment path, and the integration surface.
Risk & Options Analysis
Findings turned into a risk register and a per-module position on migrate versus rebuild, with effort sized against each option and the trade-offs stated rather than averaged away.
Report & Walkthrough
The written assessment delivered and talked through with your team, so your engineers can interrogate the reasoning rather than just receive a conclusion.
What This Engagement Covers
Fixed scope means the boundaries are stated up front. Anything beyond them is quoted separately, never absorbed silently.
$3,500 to Stop Guessing
Two weeks, a written assessment of what your legacy system actually contains, and a sized plan for moving it forward — or a clear explanation of why you should not. The fee is credited in full against the modernisation project if you proceed within 90 days.
Ready to Replace Estimates With Evidence?
Tell me roughly what the system is, how old it is, and what is prompting the question. I will confirm whether $3,500 is the right engagement for you, or tell you if it is not — and the free diagnostic exists precisely so you can find that out first.