Every company of a certain size ends up with at least one piece of software that nobody outside it will ever see: a scheduling tool bolted onto a spreadsheet, an approval system three people maintain part-time, a dashboard that somehow became load-bearing.
These tools rarely get a proper name, a design pass, or a real budget. They get built fast, by whoever was free that quarter, to solve a problem that seemed temporary at the time. Years later, entire departments depend on them without anyone quite remembering how.
Software nobody planned to keep
Engineers who inherit these tools describe a familiar dread: the codebase has no tests, the original author left years ago, and touching the wrong line risks breaking a process that finance, HR, or logistics now silently depends on every single day.
A few companies have started formalizing these tools retroactively — giving them real ownership, real documentation, sometimes even a rewrite. Most don't bother. The tool works, technically, and that's usually enough to keep it running exactly as it is.