Be open with the customer. Let them know ahead of time that you are only providing the binary for the integrated use. And if they want the documentation, source code, and project files, there will be an additional charge.
For instance, I'm working with a client who owns all works related to the development. But I have a particular library that was open-source. I extended the functionality and sold this to the client. But they do own a copy of the modified open-source library.
Be open with the client and get paid for your efforts.
If they agree to purchase only the binary. Then be clear with them that if they want updates that you will charge for maintenance. Don't try to confuse them or rip them off. Be clear, be transparent.
Hi Clavin,
Be open with the customer. Let them know ahead of time that you are only providing the binary for the integrated use. And if they want the documentation, source code, and project files, there will be an additional charge.
For instance, I'm working with a client who owns all works related to the development. But I have a particular library that was open-source. I extended the functionality and sold this to the client. But they do own a copy of the modified open-source library.
Be open with the client and get paid for your efforts.
even if they agree for taking the binary only, Isn't it hard if they wanna maintain / modify it? If I were in their shoes, I think I wouldn't buy it.
If they agree to purchase only the binary. Then be clear with them that if they want updates that you will charge for maintenance. Don't try to confuse them or rip them off. Be clear, be transparent.
I see, thanks for the insight!