> We were constantly faced with product leaders (VPs of Product, CPOs, PMs, etc.) who were very excited about adding Cord to their existing product. They saw th

> We were constantly faced with product leaders (VPs of Product, CPOs, PMs, etc.) who were very excited about adding Cord to their existing product. They saw the value unambiguously. And then we’d get to the dev team and face a stonewall of NIH syndrome alongside a clear preference for building it all themselves, even when that meant shipping a vastly less-useful product to their end users. You are painting the adoption problem as the software team having a different opinion on the build-or-buy decision. It could be they were OK with "buy" but didn't like your product for other reasons. You've said that management teams liked the idea of your product, not that engineering teams liked working with your product. All software these days is built on stacks of OTS software. Of all the external dependencies they took on, why was yours different? I've been on a bit of a tear recently, throwing away internal tech from 5-15 years ago that was inventive at the time, but where high quality off the shelf solutions now exist. I've still skipped on number of things I've wanted to pull into our stack. But they're too opinionated when they should be stupid libraries or flexible external services. I can't reshape our existing software to fit their idea of how our product can make life easier for them.