Make long-term pricing clear, simple, predictable (no hidden or unpredictable costs)
Our experience with "pay as you go" services -- not only from Microsoft -- is that managers are very reluctant to bet the farm on someone potentially volatile pricing policy. What is required is a simple, easy to find and use, fixed or "flat rate" scenario that is comparable to an owned-machine scenario: no hidden or unpredictable costs ... and the variable costs are clearly denoted and covered by a ceiling threshold. The first question is: is it real and dependable. The second question is: what are the real and dependable costs...
anonymous
shared this idea
1 comment
-
Mike
commented
Yes, I agree.
Spending Limit or Spending CAP is very important, so that I donot have to worry of my Credit Card being suddenly charge too much money.
And it can prevent some evil attack to my Azure site causing charge a large billing.
