Why full rewrites fail, and what we do instead
Of nine full-rewrite projects we were called into as reinforcements, seven had already overrun budget by more than 60%. Here is the pattern that repeats, and the alternative that works.
Articles written by our technical team about real decisions and their consequences.
Of nine full-rewrite projects we were called into as reinforcements, seven had already overrun budget by more than 60%. Here is the pattern that repeats, and the alternative that works.
A single-number estimate hides everything we do not know yet. Here is how we report uncertainty so clients can make decisions rather than just wait.
We analysed the cloud bills of eleven clients. The same five problems appeared in at least eight of them, and fixing them cut costs by 20–40%.
We stopped four machine learning projects at the assessment stage, because the input data supported no conclusion at all. Here is what a proper foundation looks like.
A security audit in the final month finds problems you can no longer fix without rewriting. Here is what we move to the start of the project.
We measured the additional accessibility effort across eight projects. The difference between starting in week one and starting at the end is tenfold.
Book a 30-minute call with an architect, not a salesperson. We will tell you honestly whether we can help, how long it would take and what it would cost.