Do you? Frankly, it kind of seems that people unscrupulous and cheap enough will always be able to find an unencrypted/cracked/nulled version of any given software, or they simply won't use it. People who would pay for it will do so regardless of how easy it may be to rip off.Trouble with that is I would need to encrypt the source and protect the software.
I don't really know what I think on this subject, or on the subject of pricing. Still weighing up ideas, but I feel I should do something to protect the software to at least discourage piracy and make it clear it's commercial software.Do you? Frankly, it kind of seems that people unscrupulous and cheap enough will always be able to find an unencrypted/cracked/nulled version of any given software, or they simply won't use it. People who would pay for it will do so regardless of how easy it may be to rip off.
I would definitely be interested in asking your contact one main question - why they chose the pricing model they did. I've talked to some 'experts' (a multimillionaire investor + a top PHP developer and creator of a framework), who are recommending SaaS as a method of source and quality control, as well as to lower the barrier to entry. It's not what I had in mind originally but the advice coming from who it's coming from, I'm doing a bit of testing in that area as well.I don't see a problem with you encrypting and/or running licenses for those that pay monthly. Want it unencrypted and open? Pony up! "But what will keep monthly customers from just using the other version?" you ask? Nothing. The exact same thing preventing me from downloading nulled copies of everything else out there. Let honest people pay and don't worry with the rest - a pirate wasn't going to pay so you didn't lose a sale.
I'm friends with the founder of PancakeApp (I did some of the development work as well); if you wanted some insider tips from someone who had been there I could strange an introduction.
Finally, if I forget to PM you mind reminding me (I'm mobile now)? I think you'll be interested in something I'm working on that should hit testing in 6-8 weeks.
If you're doing that, maybe think about monthly fee for using your hosted service, and free or one-time fee for self-hosted variant?I would definitely be interested in asking your contact one main question - why they chose the pricing model they did. I've talked to some 'experts' (a multimillionaire investor + a top PHP developer and creator of a framework), who are recommending SaaS as a method of source and quality control, as well as to lower the barrier to entry. It's not what I had in mind originally but the advice coming from who it's coming from, I'm doing a bit of testing in that area as well.
Also, I didn't get your PM.
Yeah, I do intend to continue work on Billr for the foreseeable future. Obviously there's a lot of work involved to manage the platform and add functionality to the software to allow for lots of separate instances, but I have a team now and I'll probably pay the hosting company to manage everything once it's live.If you're doing that, maybe think about monthly fee for using your hosted service, and free or one-time fee for self-hosted variant?
EDIT: Also, keep in mind that going that route is a lot more work for you, and much of it on-going/constant, so it's not something I'd recommend unless you're really interested in continuing to work on this project for quite some time.
Obviously the server is going to be suitably locked down, but also CC data are stored off-server.Having one server host the billing systems for many companies makes that server a very "interesting" target...
Obviously the server is going to be suitably locked down
What would make you feel secure?Yeah... I don't feel secure with that personally.