Earlier quoted context omitted.
> Whether they are better off depends on whether they end up getting a bill they are unhappy with later at some unspecified future date, or not. How is that a function of the overly-simplified and often-wrong calculator? If the user is never there to be happy/unhappy about it in the first place, then how would you test this anyway? By closing the loop and increasing engagement, you are increasing the chance that you…
> often-wrong The author was very careful with their words: they didn't say the calculator was wrong. They said it was confusing and sensitive to small adjustments. It's likely that the same confusion and variable sensitivity exists during usage. IMHO they should have bit the bullet and revised the pricing model.
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 :)