Complete dependency map
Every screen, module, data access path and dependency in the system, mapped automatically from the source code. Not a sample, and not an interview-based estimate.
Free legacy system assessment
Find out exactly what your legacy system contains, and what it will cost to modernize.
Most modernization decisions stall in the same place. Nobody can say with confidence what is in the system, how far a change reaches, or what replacing it would actually cost. We run our Code Analyzer across your source and answer those questions from the code itself. It costs you nothing, and the plan is yours whatever you decide to do next.
What you get
Four deliverables, from your own code.
Fixed scope, 3 to 5 weeks, no charge. No discovery workshops, and no estimate built from a questionnaire. Free for a single application. Multi-application portfolios are scoped separately.
Risk scoring by component
Which parts of the system are most entangled, most fragile, and most exposed to the loss of the people who understand them.
Effort model
What can be transformed automatically, what needs custom work, and where the real cost sits, read out of the actual code.
Costed migration plan
A sequenced plan with effort and cost attached, in a form you can take to a budget holder.
No strings
The plan is yours to keep.
The assessment stands on its own. If you take the plan and modernize the system with your own team, or with somebody else entirely, it has still done its job. We think you will want us to do the work. Nothing about the assessment requires it.
Scope
What it covers, and what it needs from you.
The offer is real and the plan is genuinely yours. It is not unlimited, so here is the shape of it before you ask.
Which systems qualify
PowerBuilder, Visual Basic 6, COBOL, Oracle Forms and PL/SQL, RPG on IBM i, Classic ASP and .NET WebForms, Nexaweb, Biz/Browser and most aging web stacks. If yours is not on that list, ask us. The approach reaches further than the list does.
One application
Free covers a single application. If you are looking at a portfolio, we will still talk, and we will scope that separately rather than pretend it is the same piece of work.
We need the real source
The analysis reads source code. Documentation, screenshots and interviews are not a substitute, and partial source produces partial answers. Where that happens we will tell you what is missing instead of filling the gap with an assumption.
When the clock starts
The 3 to 5 weeks runs from the handover of the source, not from the first call. Scope and timing are confirmed in writing before anything moves.
How your code is handled
An NDA is in place before any code moves. Transfer is by a secure handoff we agree with you, the source is used only for your assessment, and it is deleted when you ask.
Why it is free
Our own software does the reading, so an assessment costs us machine time rather than weeks of consultants. The costed plan is also the most persuasive argument we have. If it tells you not to modernize this system yet, we would rather you found that out from us.
Assessment or POC
Two ways in, and they answer different questions.
The assessment tells you what is in the system and what moving it costs. The proof of concept shows you the modernized code itself, generated from a slice of your real application.
Assessment
Analysis only. Nothing is modernized. You get the dependency map, risk scoring, effort model and costed plan, and you keep them.
Start here when the question is “what have we got, and what will this cost?”
Proof of concept
We model a representative slice of your application and run the transformation on it, so you can read the code you would own. The full fee is credited against the modernization if you go ahead.
Start here when the question is “is the output actually good enough?”
Plenty of clients do both, in that order. The assessment is the cheaper way to find out whether a POC is even worth running.
Proof
Millions of lines of VB6, mapped in two months.
A financial services firm had a VB6 codebase that had grown to millions of lines. Nobody could tell how far the impact of a change would reach, so updates and new features had stalled entirely.
Code Analyzer mapped every dependency in the codebase. With that visibility, the team completed a concrete migration plan in two months. The analysis was the entire engagement, and it unblocked a programme that had been stuck.
Start with a free assessment of your own system.
Tell us what the system runs on and roughly how large it is. We will confirm the scope and the timing in writing before anything begins.