Hi, guys. I do not know where to ask a question. We have been building a in-house platform solution for our company for a very long time. It's time to switch on COTS and provide it for external customers. Imagine, all our processes, infrastructure habits, release management - everything is built like in-house. And now there are many customers with different requirements, limitations and scales. New customers want special bundles, version control of individual components, they want individual features. I'm trying to find literature, articles with the experience of other teams, about the features of the COTS industry, organizational structures and processes. Please help me if you have expertise.

Based on your description I think I have a lot of experience in this area. I work for a company Seeq that has a product (also called Seeq) which we provide as kind of a managed service to our customers. Each customer may be on a slightly different version of the product, though this is mostly because of our on-premise history and we’re trying to move away from that. Can you share more detail about your product and give some examples of the challenges you’re facing?

Great! Sure. Our system consists of dozens of services. It is a complex observability platform. Different customers put forward different functional and non-functional requirements. This brings non-standard bundles, compatibility issues with rollbacks and updates. We are currently concerned about the following: • How to assemble and deliver customized packaging according to the customer's needs? • Who should lead the process of such releases? • How are the organizational structures of such projects usually organized? • What is important to consider when switching from in-house to COTS?