September 2026 · Note
Some vendors will not let you, or anyone acting for you, look at the code they built and you paid for. People do not generally hide work they are proud of. And a sloppy kitchen, like neglected code, does not present the bill on the evening you eat there.
Read more →
August 2026 · Case study
When two long-standing rivals combined into one Global Fortune 500 group, leadership had to decide, division by division, which systems to keep, replace or retire. Claroview measured both portfolios and put every system on a single comparable chart.
Read more →
June 2026 · Note
Every architecture diagram was accurate on the day someone drew it. The code kept moving and the drawing did not, and nobody in the room can say how far apart they have drifted. That is the question worth asking before any transformation plan is signed.
Read more →
September 2025 · Case study
Robert Bor, CTO at 42.nl, on what happened when his team benchmarked their products against open-source systems from much larger organisations. They expected a reality check and got a confirmation, along with a clear read on where they had traded quality for speed on purpose.
Read more →