10 replies to this topic

[Michael]

So this question has come up a few times lately now that IP.Board 3.2 is out, and I wanted to take the time to put this question out there for everyone, existing customers and potential customers alike.

I write several commercial products for IP.Board, and charge for the initial sale of those products, and then also charge a reduced cost for 'upgrades' whenever I have to drastically rewrite the product for a new IP.Board version. I've always used this method, long before there was any such thing as the IPS Marketplace and its concept of annual renewals of purchased products. I did this because the act of upgrading a product is often very intensive, sometimes it takes as long as writing the product initially. So I felt that made it a logical choice for a time when a new payment for that work was justified.

Most people have been happy with this setup, but with 3.2 now coming out I've seen several people who recently purchased the older version of Tutorials, and thus are now being asked to pay another $10 to upgrade. Obviously I can understand the frustration there, but I couldn't change everything about the renewal process for them without changing it for everyone. So I wanted to put this out for public discussion, and voting on which method everyone thinks is best. Bear in mind, there's nothing I can do to make everyone happy; I can't go with a mixed method on this, as the software won't allow it. If I'm going to charge an annual renewal, then it will always have to be that way.

With the current method, you pay for a product once, then you continuously get updates to that product as I produce them, but only for that single IP.Board version's life cycle. You also are not bound to a single site for your products; I've always allowed you to install what you buy from me on as many sites as you actually own. When I have to invest the time in producing a major rewrite for a new IP.Board version, then I ask that you pay the reduced cost upgrade fee to get that new version.

The alternative method is to charge for renewal annually. You buy the product once, then you get any updates I produce for that product for a year. After the year has expired, you can continue to keep using what you downloaded last, but you don't get any updates. You can still install the product on unlimited sites that you own, I don't plan on changing that. I would, like IPS, freely release security patches if necessary, but you wouldn't get access to new versions if your license is expired.

If I did decide to go with the annual renewal method, the renewal prices would mirror what they are currently at: $5 for mods up to $20, $10 for more expensive ones. And I'd also need to set expiration dates on all existing sales. I would set them to a year in the future from when the change was made, though, so if I do decide to change then all existing customers would have a year from that date before their product would expire.

So please, feel free to voice your opinions on this, I'd like to know definitely what folks prefer on this.

[AndyF]

Personally I prefer the current setup, however I do feel that changing to the annual renew would avoid problems down the line so to speak as there'd be no doubt as to what was required and when, would also stop the "I have to pay for an update" questions too, even though I know you only charge for the major updates not the small point releases.

[Loren]

I have no problem with the current method.
It would seem to me that the annual renewal would be more work for you - even if mostly automated.

[Michael]

I have no problem with the current method.
It would seem to me that the annual renewal would be more work for you - even if mostly automated.

It would be a lot of work initially. I'd need to combine the commercial files into a single submission, and make sure all of the various old versions are intact for those who need to get the old versions. And then I'd need to straighten out all of the sales data so that if you bought any version, you should be marked as having bought the new version. And then I'd need to update all of those sales to have an expiration date.

But then after I get all that done, going forward it wouldn't be too bad.

[planetby]

Well Michael, personally no matter which method you choose to use i'd still very happily pay the fee for upgrades on two simple grounds :

1: Your mods work well
2: Your always quick to help IF there is a problem (even if its of my own doing )

That to me is worth its weight in gold alone so a small upgrade fee is nothing for the amount of work involved

[Pintac]

I agree with John. Which ever way you choose, I'll still stand behind you 100%.

[Dave MacLeod]

I have no skin in this game (yet) but I have never been a fan of annual renewals.
I think you have a fair setup as it is.

[Woodsman]

Mike,
The way I see it at present if you change to annual I can see you working your butt off and getting little in return. Not that you are making big bucks now.
What I mean by this is IPS is starting to make some pretty drastic changes with 3.2 and for a while they are going to keep on coming
just like they did throughout 3.1.X. I would rather pay the small amount extra as we are right now keeping you excited with your projects.
rather than having it turn into some hum drum project where you feel like "Damn I got another update to produce".
Sure Annual would be nice but in the long run you will be the one getting screwed in the end.
A good example is How many rewrites did you have to make through out 3.0.x to the end of 3.1.4?
Don't bother counting it was more than the board changes were worth.
Keep it the way you have it and make the money you deserve. Its not fair to you to charge annual if IPS makes 15 changes through out the year.

Well built products are hard to come by and you already sold me a PeterBuilt at a Pinto price.
You deserve to make what you can and have always been more than fair.

And thats my opinion and I'm sticking to it!

[Michael]

I've updated the poll a little bit, added a third option to the initial question and added a second question. If anyone didn't vote before because they had no strong opinion either way, it'd be great if you could indicate that with the new choice.

[planetby]

Mike,
The way I see it at present if you change to annual I can see you working your butt off and getting little in return. Not that you are making big bucks now.
What I mean by this is IPS is starting to make some pretty drastic changes with 3.2 and for a while they are going to keep on coming
just like they did throughout 3.1.X. I would rather pay the small amount extra as we are right now keeping you excited with your projects.
rather than having it turn into some hum drum project where you feel like "Damn I got another update to produce".
Sure Annual would be nice but in the long run you will be the one getting screwed in the end.
A good example is How many rewrites did you have to make through out 3.0.x to the end of 3.1.4?
Don't bother counting it was more than the board changes were worth.
Keep it the way you have it and make the money you deserve. Its not fair to you to charge annual if IPS makes 15 changes through out the year.

Well built products are hard to come by and you already sold me a PeterBuilt at a Pinto price.
You deserve to make what you can and have always been more than fair.

And thats my opinion and I'm sticking to it!

Well said Woodsman, +1

[najaru]

I have no problem with the current method, but probably i prefer recurrent annual method.....