Save it, rewrite it, or replace it?
A short engagement that answers the question with evidence and a costed roadmap, so the largest decision in your technology budget stops being an argument between confident people.
- 30 to 50 story points
- Two to three weeks
- A costed roadmap you own
The problem
Everyone in the building already has an opinion about the old system. The engineers who maintain it want it gone. The people who depend on it want it untouched. Whoever signs the cheque has to choose between two groups of confident colleagues and no numbers.
That decision is usually worth seven figures over three years. It gets made on instinct anyway, because the analysis feels like a delay. It is not a delay. It is the cheapest part of the whole program.
We measure what it costs you to change the system now. Then we cost each alternative. Then we say which one we would pick, and why.
- A recommendation, not three options and a shrug
- Costed in story points, so it converts directly into a budget
- Written to be read by the person approving it, not only by engineers
What this Pod ships
Cost of change, measured
What a typical change costs today in time and risk, established from the repository and the ticket history rather than from anecdote.
Architecture and dependency map
What the system is made of, what it talks to, and which parts can move independently of the rest.
Risk register
Unsupported runtimes, absent tests, single points of failure, and the compliance exposure each one carries.
A costed recommendation
Save, rewrite or replace, with the story point cost of each path and the sequence we would run.
What an assessment hands you
Why we rarely recommend a rewrite
A rewrite replaces a system you understand with one you do not. It also asks the business to stop receiving value while it happens. Sometimes that is the right call. Far more often the economics favor carving the system up and moving it one piece at a time.
We tell you which case you are in. Sometimes the system is fine and the real problem is the deployment process. If so, that is what the document says, and it cost you 30 points to find out.
What it costs
30 to 50 story points depending on how many systems are in scope and how much of the history is documented. Quoted before work starts.
If you go on to run the recommended work with us, the assessment credits in full against the first phase, provided the work starts within 90 days. The window matches the one on banked points.
- Points: 30 to 50, agreed before work begins
- Timeline: two to three weeks
- Credits in full against the modernization work if you start within 90 days
- The roadmap is yours, whoever ends up delivering it
Bring us the backlog.
In 30 minutes, we will show you what a Pod would ship first and how we would price it.