That only makes sense to me in the context of a business being an IT shop to begin with. Most businesses aren't, and their new product offerings require factories and dies and labor and materials. Besides which, the problem of provisioning is entirely overblown for this scale of business. I can spin up new servers all day on our on-prem vSphere cluster.
Lots of businesses outside of 'IT shops' use computers. I currently work in Civil Engineering and more and more of our product and service offerings have an IT/Online/Web based component which involves setting up some sort server.
I can spin up new servers all day on our on-prem vSphere cluster.
I what price? At my old job an on-perm vSphere 'machine' cost my department a lot more than what AWS was charging.
And since it's my 'private' cluster I don't have to worry about queuing my jobs and waiting for the machines to be free. There is no way my department would have bought me those machines as physical hardware.
At that scale in a single company the ability to provision verticals weighs heavily in architecture and design choices.
"Should we spin this new feature out as a microservice or fold it into an existing app so we don't have to wait weeks and do crazy cost accounting for new environments?" And the answer has follow-on effects because now it has to be accounted for in a specific teams' backlog and we encounter yet more waiting.
Do you really? In my experience, admittedly outside of SV, pretty much nobody needs that.