To me the best sales pitches is around the overall health of the framework, suitability to a set of problems, and the level of support you, the seller, will pro

To me the best sales pitches is around the overall health of the framework, suitability to a set of problems, and the level of support you, the seller, will provide to me, the customer. This means: - dev mindshare: hiring for the skills and getting help. You can quantify these trends via job listings and stackoverflow question volume. - supply chain risk: with open source, what’s the risk of the project going dormant leaving no maintainers behind. How open are they to contributions? How well maintained is the code? Does a major company (or Google) back if? When was the last commit date? - problem suitability: what class of problems is the project suitable for. Improve your pitch by saying what it’s NOT for. Finally, if you want adoption you need to engage these other groups as customers. Up to the level of it being the main measure of your teams success. You need to setup support, training, documentation, and evangelism. You also need to work hand in hand ON the customer projects in a short-term, consummating capacity to increase adoption and understand the gaps in the tech. Otherwise you risk being seen as too “ivory tower” divorced from real problems. Most of these are not technical problems, they are, like you say about “human ops” etc