It keeps breaking and you have stopped reporting it
There is a workaround for the workaround. Somebody has learned not to click that button on a Friday. New faults stopped being reported a while ago, because reporting them did not achieve anything.
The tell is the resignation, not the faults
Plenty of systems have bugs. What marks this state is that the people using it have stopped expecting them to be fixed and have built their working day around the failures instead. That is expensive in ways that never appear on an invoice, and it is nearly invisible from above, because nobody is complaining any more.
Why every change breaks something else
Almost always the same cause: there are no tests, so nothing tells anyone when a change has broken something unrelated. Add a data model that has been extended sideways a dozen times and logic that lives in three places, and every fix becomes a gamble. Developers working in that environment are not careless. They are working without instruments.
Stabilise before improving
The first job is not new features and it is not a rewrite. It is stopping the bleeding: get it building reliably, get the errors visible rather than silent, put tests around the parts that break most, and fix the faults that are costing real time. That usually takes a few weeks and it changes the mood of the whole thing, because for the first time in a while something got better instead of worse.
When we say replace instead
Sometimes the honest answer is that the foundations will not carry another five years and the money is better spent starting again. We will say so, with the reasoning, and we would rather say it before you have paid us to stabilise something we then recommend replacing.
What it takes
A stabilisation engagement is typically four to six weeks and produces a system that can be changed without fear. Whether it is worth doing is the first thing we assess, and that assessment takes days, not weeks.
Tell us what you need.
Broken, half-finished, or not built yet. Whatever state it is in, and whatever you do or do not know about it. Within two working days you will have an answer on whether we can help and roughly what it would cost, from someone who has read it, not a form.
Or email richardking@sixteenpillars.com