Charging to renew lapsed support
This is not a programming question, but a business practices question. I have an application that we sell commercially. The first 90 days of support are included with the purchase. We then charge the client 15% of the original list price for a yearly support contract, which includes both phone support and updates to the software (we're putting out at least one update per year so the clients can see value received for their money). I know Oracle charges 22% yearly, but they're pricey in everything; I'm not trying to gouge.
Of course, not all clients buy the support. The application has been out for about 18 months, and we're about to release a new version with a number of new features that could potentially interest some users who aren't under support. I'm trying to decide how to price a renewal of support. I don't really want to make it the standard price for the update and a full year of support, as that might tend to encourage people not to automatically renew, but to wait for updates to come out. At the same time, I don't want to price it so high that people are discouraged from coming back.
Any thoughts? Any examples of what other companies are doing? How would you respond if you were the purchaser?
Of course, not all clients buy the support. The application has been out for about 18 months, and we're about to release a new version with a number of new features that could potentially interest some users who aren't under support. I'm trying to decide how to price a renewal of support. I don't really want to make it the standard price for the update and a full year of support, as that might tend to encourage people not to automatically renew, but to wait for updates to come out. At the same time, I don't want to price it so high that people are discouraged from coming back.
Any thoughts? Any examples of what other companies are doing? How would you respond if you were the purchaser?
ASKER
So you're suggesting paying for two years' worth of support, one as the price of getting back in the system and the second to actually get 12 more months of support? If the regular support price was $500, then, they would pay $1000 today to get the update plus support through April 2010. That seems a reasonable way to handle it.
Anyone with other ideas?
Anyone with other ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I would say, No support, is no new release. If that kind of customers like to have the new features, they have to buy the application. Because if you give them any other arrangement, it's unfair for the customers that DID take a support contract. and they will ask you why they have to pay the contract is it is not necessary for new releases and they will complain that they payed to much.
Of course I know that it is not realistic or accaptable to handle a customer in that way. But the customer has to pay something for his new release, so I think it's normal that he pay the support contract over the last year to get the update and a oblige him a contract for the next period(s).
Regards,
Murph