![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Folks Hows that for an attention grabbing subject? |
#2
| |||
| |||
|
|
On Thu, 21 Oct 2010 03:41:29 -0700 (PDT), Wayne cqdigital (AT) volcanomail (DOT) com> wrote: Hows that for an attention grabbing subject? Hi Tony. What licence fee will be applicable to a developer who distributes the Updater to lots of clients? I'm thinking a price would be $100 per client. But maybe that's a bit high. I'm not quite sure on this. Maybe a graduated pricing policy. |
#3
| |||
| |||
|
|
Well, for what it's worth, I won't use it in that case, and won't have my clients purchase it, either. |
|
I worry that you won't make any more than you're making now, Tony, |
|
and all you've done is deprived yourself of a bunch of free quality assurance testers. |
#4
| |||
| |||
|
|
You were musing on pricing. Perhaps 2 types; professional (developer) and single site (user). A professional for someone that can distribute to unlimited companies, user for one company's use. |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Can AutoFE be expanded to other programs? i don't know. Yes. That's one reason why I added the Start Method = Display File Count Message. This way it doesn't actually start a program such as Access, Excel, Word, whatever. It just states "All files are up to date" or "x files copied". I also own the www.autofileupdater.com domain. <smile Does FileMaker or other database programs require easy distrubution as well? Apparently FileMaker has the capabliity built ni. Maybe other developers here know of other programs that require easy distribution. Would an IT department that distributes apps to new end-users need something like this? Awaiting suggestions. <smile |
#7
| |||
| |||
|
|
Tony, your work is brilliant, and I see no reason you can't charge for it. Careful of your stats. Some large percentage of downloads probably never get implemented, so their payment of a fee would not be appropriate. |
|
Having said that, I haven't paid you, but I had planned when moving to the next version to license your Professional version. I'll bill it to my client "under the covers". Take a look at VBAGlobalErrorHandler for an example of a pretty well- thought-out licensing structure. Its still relies on some trust, but I think it's worked out for me and my client. |
#8
| |||
| |||
|
|
Tony, I used it several years ago (when it was very simple) with a couple of clients (now out of business due to the economy), and it did all I needed. I would have no problem paying a reasonable, one-time fee for distribution rights. As a matter of fact I will soon be rolling out a major upgrade at a client and have been considering using the FE Updater. My only hesitation is that there has been so much added to it, and I am only interested in simple distribution, like the old one did. |
#9
| |||
| |||
|
|
I used it several years ago (when it was very simple) with a couple of clients (now out of business due to the economy), and it did all I needed. I would have no problem paying a reasonable, one-time fee for distribution rights. As a matter of fact I will soon be rolling out a major upgrade at a client and have been considering using the FE Updater. My only hesitation is that there has been so much added to it, and I am only interested in simple distribution, like the old one did. |
#10
| |||
| |||
|
|
but setting up a new users seems to me like something peripheral, and oughtn't be in the updater proper. |
|
I think a shareware model might be better for yours, or the pay version having features that the free one lacks. But then, how much time does it take to re-architect to work that way? Is it worth the time to get your utility more widely distributed for basic functionality? |
![]() |
| Thread Tools | |
| Display Modes | |
| |