I was hoping for a more numeric analysis of purchases and upgrades for IT/SysOps. The article is talking mostly about vague non/difficult to validate benefits

I was hoping for a more numeric analysis of purchases and upgrades for IT/SysOps. The article is talking mostly about vague non/difficult to validate benefits that may or may not exist numerically. Sure, "Pride", "Momentum", "Inspiration" are great benefits from making something 'awesome' but those metrics do not quantify well in a corporate, and even in a startup setting. I think his second example "momentum" actually sums up the viewpoint about hardware purchases, ' IT tells them they can’t push it to production until a new server gets approved, ordered, setup, tested, and then deployed, they will get discouraged. Eventually, they won’t even think about new features. ' Is this a problem with IT's budget? or is it a problem with a dev who gets discouraged too easily? Why not simply the feature? why not nag at the IT? It feels like the author was flippant about this issue, and in reality doesn't do any real cost-benefit analysis.