Choosing a Vendor With Outcome-Based Sourcing

Choose a vendor with outcome-based sourcing by judging each option against the real outcomes your services need, not against licence price or demonstration polish. A sound decision weighs capability, fit, implementation risk, total lifecycle cost, partnership behaviour and evidence, and selects technology against designed services, use cases and lifecycle outcomes, because a polished tool cannot repair unclear ownership or a broken process.

• Set weighted outcome criteria first. Make the criteria, the decision rights and the resulting decision visible to everyone who depends on it.
• Run scripted scenarios and check references and delivery capability, so vendors are tested against real service situations rather than polished demonstrations, which the article warns are easily overweighted.
• Evaluate total lifecycle cost, not licence price. In the article's example, a lower-priced product loses because integration effort, weak support and migration risk make its lifecycle cost and outcome fit worse.
• Plan for exit and data portability from the start; ignoring them is one of three named pitfalls, alongside choosing on licence price and overweighting demonstrations.
• Track evaluation evidence, implementation risk and total cost variance as a set, each with an agreed baseline and owner. Start with one priority service, record assumptions and the date they will be checked, and review results with delivery teams and consumers.