The Bugatti/V.W. is something different, a Bugatti doesn't solve a problem that other brands have, except that it has more status and luxury. The cloud solves actual problems and costs may even be one of them. In one case the solid practical reason was that the on-premises servers were running out of available space. They had everything on-premises, including VM workstations that got less and less memory because the servers couldn't keep up. They were talking about giving everyone a laptop to solve that problem, then bought a new mega server instead. Everyone, including the sys admins, were advocating the cloud for certain solutions. Their issue also wasn't the money, it was security, because somehow the cloud is less secure (according to management and compliance). Another still had a "developer develops, passes code over to system admin who deploys to production" kind of setup, and the practical reason there was that the system admins couldn't keep up with development. That could be solved by going more DevOps and practicing CI/CD and isn't necessarily solved by the cloud, although it does make it somewhat easier. However, they had a lot of servers doing nothing most of the time and peaking once or twice per week, which is another scenario the cloud handles a lot better. And they could get rid of their data centers, which costs lots, including storage of the physical servers. Well, they probably have to write them off first, which could take a while because they just bought a new one... I don't think teams, on average, want to get with "the new thing". Lots of people don't like change, especially if that means learning new things which makes their jobs harder. My experience is that one person wants the latest greatest and alerts the rest of the team. By the time the entire team or even multiple teams want this technology as well it's no longer latest greatest and they're convinced it solves a problem they're having. So, if the people you pay for their technical knowledge tell you to go in a certain technical direction then why would you overrule them because of an uninformed "gut feeling"? That's just bad management... In the end it may even be a matter of keeping up because you can't get new hires otherwise. Last month, I turned down two jobs because they didn't do cloud (which would be a total waste of my two new Azure certificates). No (good) developer wants to work for a company that doesn't use new technologies once in a while. I'm turning into somewhat of a cloud advocate thou