A company that I use to work for would give clients a break on the hourly rate if the customization was going to be part of the next release of the software. Clients would submit WIBNIFS (Wouldn't It Be Nice IF) all the time. We used the WIBNIFS as our feature enhancement list.

I never heard of any o the clients having a problem with this policy. Those who needed the features right a way, paid for it.



>We have an application that will be sold to businesses. After a year a given amount will have to be paid by the customers so that they always get the newest version. Up to that point no problem.
>
>Here's what I'm wondering about. Some clients are already asking for additions/modifications. How do we manage that?
>
>Do we charge them for what we just added? Because there are possibilities that these improvements will be included in a newer version. But to be fair we don't want to charge that customer for things that could be used by others at probably no cost other than the premium they'll have to pay each year. If we charge them do we offer them free services after a new version is released because they're responsible in part for a better version of our software?
>
>We also have to keep in consideration that some improvements could become major things added to the software. In the end improvements worth more than the annual amount paid by only one client.
>
>What should be the fair way to manage this for everybody (us and the clients)?