About CodeOptimo

Expensive decisions about complicated software deserve better evidence.

CodeOptimo helps organisations understand complex existing software well enough to decide what to do with it: what should change, what can be left alone, what order the work should happen in and whether the investment is justified. Its core service is the Codebase Assessment, and where it makes sense, CodeOptimo can also help implement the resulting roadmap.

The business was founded by Peter, a software developer who has spent his career building and maintaining business-critical .NET systems. The pattern he kept seeing was the same one many technical leaders will recognise: a system that still runs the business but has grown to the point where apparently simple changes take weeks, estimates stop holding and certain areas are quietly avoided. The organisation knows the software is difficult. What it usually lacks is a clear enough picture to decide what to do about it.

Without that picture, decisions tend to go wrong at one of two extremes. Some organisations carry on indefinitely, absorbing the cost and risk because the alternative feels too uncertain to start. Others commit to a full rewrite or replacement before establishing whether most of the system actually needs it. Both are expensive ways of avoiding the real question. CodeOptimo exists to answer that question properly, before the money is spent.

The thinking behind the work is deliberately proportionate. Old does not mean bad; parts of a long-serving system are often perfectly adequate and should stay as they are. Untidy code is not automatically the first thing worth fixing; technical debt matters commercially only when it creates real cost, risk or constraint. Adding developers does not resolve a problem whose real constraint is understanding the system. And a rewrite is one legitimate option among several, to be chosen on evidence rather than fashion or frustration.

That evidence comes from what can actually be observed about the system, drawn from the code, existing documentation and the knowledge of the people who work on it, with inference clearly labelled as such. Deterministic analysis and AI-assisted reasoning help analyse large codebases more systematically and consistently, but they are the tools, not the product. The product is understanding and judgement. Recommendations are subject to human technical review, with the findings weighed against what the business is trying to achieve.

Understand the system. Decide on evidence. Change what is worth changing, in the right order, and leave the rest alone. The aim is not the biggest project. It is the right intervention.