Good software might begat the need for more good and useful software.
Where's the proof for that? And what do you define "good SW"? For the management, "good SW' is whatever makes money fast. It's business.
SW isn't like building chruches or bridges, something to last 100+ years, but something with an incredibly limited lifespan, that will have to be rewritten anyway, so why bother investing too much in "good SW" if "OK SW" will do the same job anyway?
>but something with an incredibly limited lifespan,
Oh hell, I found a js developer with their package du jour. Meanwhile in a lot of enterprise you work with software that is positively ancient.
For that matter, how do you know good software really doesn't last centuries? The practice of software's creation has yet to see its hundredth birthday. We have quite literally not had time to tell, and early results seem suggestive in really either direction.