Removing the financial aspect for a moment, since I'm not informed enough to comment, I would like to say lots of companies are essentially running on software way older than five years and a lot of their employees don't even realize it because the 'new' development has mostly been repurposing the old software into apis and services that they then consume for their new stuff, but that old thing is still down at the bottom running the stuff, and the team doesn't understand it enough to do more than consume it, and there's always an ugly moment when something goes wrong and someone on an incident call asks "I thought that was retired?"

And then the devs do the "Well uh, it is, but we still uh, consume...uh...apis...endpoints... umm yeah it's not retired. Hank the ancient that now does dev finance built what we're using, we should get his help" And then hank gets on the phone with a sigh and fixes it.

I initially thought this was something exclusive to where I've worked, but after some years it seems to be true more frequently than I'm comfortable. When it's really bad you realize the entire company was built by Hank and maybe one other dude who got laid off and everybody else has just been making bootstrap wrappers of their tool for 15 years between the bare minimum to keep the servers compliant.

When I meet a software engineer that gives me the impression they're an engineer and not their clan's webmaster, it's kind of a cool day.