I like this question. The contrary. IMO, this is one of the best ways to go about it. However, the solution should not give away your secret sauce. Look at exa

I like this question. The contrary. IMO, this is one of the best ways to go about it. However, the solution should not give away your secret sauce. Look at examples, two come to my mind: Ory and Yugabyte. Their solutions are mostly open source and both are examples or healthy businesses operating on an open source foundation. But not all bits are open source. Not all knowledge gathered by the org is shared for free. In both cases, the value is open source, the how isn't. The premise is: "this is what can be done, you, the client, can do it roughly like this and this". There's a lot of space to fill between individual "this". That space is your secret sauce, the "how". For the "how", the client needs to engage. The client must have a way to learn the "how" but it's important that the client knows the price of the "how" and is contractually obliged to keep the "how" knowledge internal.