You’ve just completed a lengthy requirements gathering phase with business users and are evaluating 3 software solutions. The solutions vary in price, but all 3 meet your “must-have” requirements.
The highest-priced solution offers extensive capabilities which were identified as “nice-to-haves” that would ease multiple pain points. You appreciate the importance of these features and the positive impact they could have on the business.
You present the potential solutions, heavily stressing the benefits of the nice-to-have features: ease of use, visual data reporting, compatibility with third party solutions, and more.
At the end of day, it’s the team’s decision, and the bottom line is all too influential. They select the cheapest option.
Now what?Read More