Re: 3rd request: What are SMSI's upgrade policies?
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 49419
interpreted = N
texte = >, i.e., Commerce w/ one domain upgrading to Commerce >w/ unlimited domains. So if you applied the policy Doug provided, and they >bought a Commerce license for $995 and a one domain secondary license for >$50, total initial cost is $1,049. If they decided to upgrade the domain >license to unlimited before 30 days, it would cost them $1,000-$50 >additional, or $950 additional. If they made this decision after 30 days, >they then get credited 50% of their initial domain license cost, which would >be $1,000-$25, or $975 additional.Thanks for the clarification! The example clearly illustrates your policy for this particular upgrade scenario, so now I can explain it to clients properly, without leaving them guessing. This only leaves the v5 to v5 upgrade question unanswered ...>The only scenario not yet addressed with a published policy is upgrading >from one 5.0 Edition to a higher level 5.0 Edition, e.g., Commerce 5.0 to >Enterprise 5.0. An upgrade policy for that scenario is being reviewed and >will be published when it's approved.Thanks for this information as well! Even though I would have expected these upgrade policies to have been well thought out and finalized many months ago, at least now I can tell my client that you have no upgrade policy, which (to him) means you might not give him any credit towards a better v5 version if he decides to go in that direction some day.>I find it hard to believe that a business decision hinged on this >one remaining piece and turned on a what if I bought the wrong Edition >scenario pending information from a public talk list.It's not just this one piece of missing information that causes a buyer to spend his money elsewhere, Phil, it's the fact that this is just one *more* missing piece of the puzzle to him -- and buyers simply will not spend their money at SMSI when so many pieces of the puzzle are still missing.The difference in this case is potentially thousands of dollars to a new client who has never even heard of your software or your company before. And he is NOT going to buy until he has the information he expects to receive -- information that other software companies publish on their web sites in an effort to encourage customers to buy and to upgrade.Obviously you're not in the same business as we are, or you would understand these issues a lot better than you seem to ...>I'd either re-focus >the client on clearly identifying their needs so they purchased the right >Edition to begin with ...Sometimes clients -- especially the intelligent and forward-thinking clients -- are considering their potential future needs, and not just their immediate needs. They also consider the money involved, and the possibility of buying an upgrade later vs. buying the better version immediately. It's not as easy as your suggestion seems to indicate, especially in the absence of a published upgrade policy ...>or pick up the phone and get my answer so I could >make it a non-issue with the client ASAP.You can do nothing to make this a non-issue, either on the phone or otherwise, until your v5 to v5 upgrade policies have been properly published. -- Sincerely, Kenneth Grome------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>, i.e., Commerce w/ one domain upgrading to Commerce >w/ unlimited domains. So if you applied the policy Doug provided, and they >bought a Commerce license for $995 and a one domain secondary license for >$50, total initial cost is $1,049. If they decided to upgrade the domain >license to unlimited before 30 days, it would cost them $1,000-$50 >additional, or $950 additional. If they made this decision after 30 days, >they then get credited 50% of their initial domain license cost, which would >be $1,000-$25, or $975 additional.Thanks for the clarification! The example clearly illustrates your policy for this particular upgrade scenario, so now I can explain it to clients properly, without leaving them guessing. This only leaves the v5 to v5 upgrade question unanswered ...>The only scenario not yet addressed with a published policy is upgrading >from one 5.0 Edition to a higher level 5.0 Edition, e.g., Commerce 5.0 to >Enterprise 5.0. An upgrade policy for that scenario is being reviewed and >will be published when it's approved.Thanks for this information as well! Even though I would have expected these upgrade policies to have been well thought out and finalized many months ago, at least now I can tell my client that you have no upgrade policy, which (to him) means you might not give him any credit towards a better v5 version if he decides to go in that direction some day.>I find it hard to believe that a business decision hinged on this >one remaining piece and turned on a what if I bought the wrong Edition >scenario pending information from a public Talk List.It's not just this one piece of missing information that causes a buyer to spend his money elsewhere, Phil, it's the fact that this is just one *more* missing piece of the puzzle to him -- and buyers simply will not spend their money at SMSI when so many pieces of the puzzle are still missing.The difference in this case is potentially thousands of dollars to a new client who has never even heard of your software or your company before. And he is NOT going to buy until he has the information he expects to receive -- information that other software companies publish on their web sites in an effort to encourage customers to buy and to upgrade.Obviously you're not in the same business as we are, or you would understand these issues a lot better than you seem to ...>I'd either re-focus >the client on clearly identifying their needs so they purchased the right >Edition to begin with ...Sometimes clients -- especially the intelligent and forward-thinking clients -- are considering their potential future needs, and not just their immediate needs. They also consider the money involved, and the possibility of buying an upgrade later vs. buying the better version immediately. It's not as easy as your suggestion seems to indicate, especially in the absence of a published upgrade policy ...>or pick up the phone and get my answer so I could >make it a non-issue with the client ASAP.You can do nothing to make this a non-issue, either on the phone or otherwise, until your v5 to v5 upgrade policies have been properly published. -- Sincerely, Kenneth Grome------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Encrypting WebDNA Templates (1999)
multiple credit card merchant accounts/processors (1997)
Error Lob.db records error message not name (1997)
any suggestions for creating a multi-lingual site? (1999)
Shop till you drop dead on the avenue ... (1997)
absolute paths for databases? (1997)
presetting variables ... (2000)
A Global Variable (1997)
[founditems] & radiobuttons (2002)
WebCat2 - storing unformatted date data? (1997)
Reversed words (1997)
WebCat2b12plugin - [search] is broken ... not! (1997)
WebDNA Solutions ... sorry! (1997)
Email template names (1997)
WCS Newbie question (1997)
Errata: WCS Newbie question (1997)
problems with 2 tags (1997)
Using [random] (1999)
The code, one more time. (2003)
WCS Newbie question (1997)