The problem is that adding some open source code to a project when it's free is simple, easy, and can be done without oversight (it shouldn't, but it can). If the code couldn't be added without paying the owner a sum of money and receiving a licence in return (i.e. something that would have to be archived and looked after), then it all gets more difficult. Budgets have to be allocated, spending authorised, receipts processed, etc. This would require approval from authority, and they would want assurances frrom the supplier that the code is well-maintained, does what it says it does, etc. Someone would have to review the code, and that costs time and more money. They might even have to review multiple alternatives to ensure that the project selected is the right project. At this point commercial suppliers get invited into the room, who send professional salesfolk to a meeting with management, and the whole ball game changes.

This isn't "management bullshit". It's what should happen in a well-run organisation with a good procurement process.

If you want to sell your software, that's the game you play, and you better hite professional salesfolk to get your cash. If you don't want to play that game, then give it away for free. But don't whine later that it created "millions in value" and you didn't get any of that.