The birth of consumption- & outcomes-based IT pricing

The birth of consumption- & outcomes-based IT pricing

It's hard to keep a technology evangelist quiet on the subject of cloud computing. The world of complex multi-cloud is reaching critical mass where we can now start to build an intelligent ‘data fabric' composed of componentized automated efficiency etc… you know the sort of thing.

But ask those same evangelists to follow through on the ultimate promise of the Software-as-a-Service (SaaS) model, and the response is somewhat more tight-lipped.

If we can use the subscription-based pricing model of cloud to buy just the required amount of processing, storage and analytics, then why shouldn't we be able to follow that through and pay for just the portion of IT that was useful?


From consumption, to outcomes

This is the shift from consumption-based pricing to outcomes-based pricing and not everybody wants to talk about it. If technology is supposed to deliver the precisely defined functionalities that industry vendors promise it will, then why shouldn't we be able to map those functionalities against our business model and pay for just those functions that deliver?

To continue reading...

Your token has expired.Try again.


« How to (really) evaluate a developer's skillset


Workload automation: Buyer's guide and reviews »