I personally force stakeholders to define sunset dates on the system / code ill be writing.
If its sunset date is never, cost of development proportional to roi approaches zero.
If the sunset date is near, cost of development gets very, very expensive.
Having that information both informs my priorities and the understanding of how long development will take / cost.
I am not sure that is good economics, because the discount rate for the future revenue approaches 100% over extended time.
Not everything is monetarily cost based.
Cant recreate a space probe 30 years ago to replace the one malfunctioning now.
Cant recreate makret share gained against compeitors with stability problems.
Interesting point though, definitely ignored it til now.
Iguess the point is, everything is a trade off, and we shouldnt be acting like its either high quality or high throughput or high cost. Its somehwere in between and you get to choose depending on your contlstraints and needs.
And lots of organizations would be willing to borrow money at a usurious interest rate-- why not borrow technology for the same? ;)
[edit] hell, communicating that in a way the weaker end of technical managers will care about can be hard, for that matter. If they came up “doing it wrong” and are of a certain mindset, good friggin’ luck.