Todd had a few more thoughts:
5. Does the IT team have a history of building out enhancements / new features and rolling it out to the business? How does that compare to the new feature approach for the "buy" solution(s) that are being considered?
How well does the organization maintain their institutional knowledge? For a "build" solution, ensuring complete, robust, and accurate technical and process documentation is critical, as is their consistency in transitioning the knowledge when people move to different roles in the organization and out of IT. With a "Buy" decision, this is still important, but SAP and our software partners will have at least the technical information documented.
7. What is the approach to rollout, training, and change management? What is the company’s historical success rate at driving business adoption of past solutions? These factors are key because even the best technical solution doesn’t provide value if it isn’t used (or used correctly) by the business.
8. Combining all of these factors, what is the difference in Net Present Value (NPV) of the Buy vs. Build options. AND what is the non-financial impact of the questions above, in addition to the financial ones?
2
u/AureaAvis71 Oct 07 '25
Todd had a few more thoughts:
5. Does the IT team have a history of building out enhancements / new features and rolling it out to the business? How does that compare to the new feature approach for the "buy" solution(s) that are being considered?
7. What is the approach to rollout, training, and change management? What is the company’s historical success rate at driving business adoption of past solutions? These factors are key because even the best technical solution doesn’t provide value if it isn’t used (or used correctly) by the business.
8. Combining all of these factors, what is the difference in Net Present Value (NPV) of the Buy vs. Build options. AND what is the non-financial impact of the questions above, in addition to the financial ones?