User Power
Value/Post Ratio
175%
- Nov 13, 2018
- 12
- 21
I have not sold software as a private person to organizations, but have long experience in working as a software developer and related roles, also participating in licensing decisions both as seller as a buyer. My advice is to prepare a few packages consisting of following components:
1) The software itself (with or without source)
2) Documentation (for internal support and/or end users)
3) Support (think about reaction times, pricing, how many hours per month/year etc.)
4) Training (e.g. 4-hour training for support staff, 4-hour training for end users)
5) Updates
You could, for example offer these three packages. The client has maybe something else in mind, but they serve as a nice conversation starter.
1) Software without right to modify, documentation, 4 hours of support per month, no training, 12 months updates for n $
2) Software without right to modify, documentation, 8 hours of support per month, one day of initial training, 12 months updates for 1.2 x n $
3) Software with right to modify, documentation, 16 hours of support per month, two days of initial training, 12 months updates for 2 x n $
When drafting a license agreement, you should make clauses for
a) where the software may be used (e.g. restrict the use for the particular company)
b) prohibition of reverse engineering if you don't want the client to modify your software
c) warranty, restriction of your liabilities
d) redistribution rights (you probably want none)
e) intellectual property rights
Disclaimer: this is no legal advice.
According to my experience, corporate clients often conveniently forget to renew licenses (often if someone notices the license expired, he doesn't care enough to tell somebody in charge of that) so I suggest using some mechanism to prevent that (without irritating the client).
1) The software itself (with or without source)
2) Documentation (for internal support and/or end users)
3) Support (think about reaction times, pricing, how many hours per month/year etc.)
4) Training (e.g. 4-hour training for support staff, 4-hour training for end users)
5) Updates
You could, for example offer these three packages. The client has maybe something else in mind, but they serve as a nice conversation starter.
1) Software without right to modify, documentation, 4 hours of support per month, no training, 12 months updates for n $
2) Software without right to modify, documentation, 8 hours of support per month, one day of initial training, 12 months updates for 1.2 x n $
3) Software with right to modify, documentation, 16 hours of support per month, two days of initial training, 12 months updates for 2 x n $
When drafting a license agreement, you should make clauses for
a) where the software may be used (e.g. restrict the use for the particular company)
b) prohibition of reverse engineering if you don't want the client to modify your software
c) warranty, restriction of your liabilities
d) redistribution rights (you probably want none)
e) intellectual property rights
Disclaimer: this is no legal advice.
According to my experience, corporate clients often conveniently forget to renew licenses (often if someone notices the license expired, he doesn't care enough to tell somebody in charge of that) so I suggest using some mechanism to prevent that (without irritating the client).