Software-as-a-service: Difference between revisions

Now this would be fine, of course, if the product ''did'' work as billed, intelligently anticipated your particular applications and handled them quickly, quietly and immaculately right out of the box. That would be worth paying for.

But common experience, when you finally get to play with it, is that these applications ''never quite do what you want them to''. Either ''your'' intended use isn’t ''quite'' the one the [[vendor]] had in mind — here the product can’t ''quite'' do what you want, and isn’t flexible enough for you to reconfigure it  so it can— call this a “'''misalignment'''” problem — or it ''can'', but to get the application to be of any use, it will need a good deal of energy, expertise and effort from ''your'' people to configure it; energy [[change adoption|they will be disinclined to provide]] — call this a “'''configuration'''” problem.