[Wilder7977]

And if it's so cheap and bespoke, why buying it and not making it in house? What about access to people with know-how of that product? You use a product that only 4 other companies use, you can be sure you won't find any new hire that knows how to use it.

To me it seems the reality works in the opposite way. Among the many products built, some will be successful and will swallow the whole market, like now with basically any software or SaaS product.

[csa]

> And if it's so cheap and bespoke, why buying it and not making it in house?

0. Sure, some products will be made in house. That said, being able to spec a product well is a skill that is not as common as some folks seem to think. It also assumes that an org is large enough to have a good internal dev team, which is both rare and relatively expensive.

1. It sloughs responsibility, which many folks want to do.

2. It allows for creation to be done not by committee and/or with less impact from internal politics.

3. It facilitates JIT product/tool development while minimizing costs.

That’s off the top of my head.

The realities of business often point to internal development not being ideal.