> they didn't say the calculator was wrong Fair point. The author commented elsewhere here and stated that it's not the usage but the understanding of the vari

> they didn't say the calculator was wrong Fair point. The author commented elsewhere here and stated that it's not the usage but the understanding of the variables in the calculator which are often wrong by more than 10x. From the response, it seems like the only way to know how much something will cost is to actually run a workload. Edit: if the customer is getting a wrong-answer because of wrong-inputs, IMO, it's still a wrong-answer. > IMHO they should have bit the bullet and revised the pricing model I don't know enough to agree/disagree because they may be offering close to at-cost which might give better overall pricing than competitors. It's a complex-game :)