Many years ago, I designed and ran a developer relations program. Companies would license our tech for a quarter million dollars and up, sometimes multiple tim

Many years ago, I designed and ran a developer relations program. Companies would license our tech for a quarter million dollars and up, sometimes multiple times for multiple products. We used to hand it over with basically no knowledge transfer or support at all, and I came in and changed all of that. 1. Do you want to provide technical support? Often (but not always) there's knowledge transfer: you spend hours or days or weeks helping them get it building correctly and showing them your structure and explaining why you made certain technical choices. Sometimes (but not always) there's a period after that where you're available to answer questions (by some defined method and for some defined amount of effort and possibly [but not always] for a defined fee). Occasionally they won't have a staff at all, and want to buy it, rebrand it, and have you do all the work; it's like a regular consulting job at that point. But, what do you want to do? 2. Talk to a lawyer. That's what they're for.