Subscribe to Own Plan
Instead of paying full price for software or just plain subscribing to get it, I suggest a “Subscribe to Own” model instead.
The way it might work is as follows:
There would be a “Super Suite” of applications that consists of everything SCS sells related to pro NLE work as well as a number of other vendors related applications. It would be a whole bowl of wax type of suite.
The total price of all the applications would be divided into monthly payments according to the “Subscribe to Own” plan that one chooses with a nominal amount (according to the plan chosen) added each month for accounting and other costs.
There would be plans ranging from one to six years. The total number of payments and their monthly amounts would depend on how many months there are in the “Subscribe to Own” plan chosen.
The person subscribing would have a subscription license during the payment period and would receive a full license once they have finished their “Subscribe to Own” plan. They would receive updates and upgrades during their plan period.
After they have completed their plan and have a full license, they could then subscribe to a maintenance plan that includes updates and upgrades to all of the applications. They can also opt not to subscribe to the maintenance plan but then they would then be required to pay the full amount for upgrades and not receive any discounts. The maintenance plan would be somewhat less than the “Subscribe to Own” plan. How much less would depend on the “Subscribe to Own” plan that was originally chosen.
If during the “Subscribe to Own” period a person should miss three payments in a row, then they would not only lose their subscription, they would also loose credit for all funds paid. Also, if a person misses a total of three separate payments during the entire “Subscribe to Own” period, they would also lose their subscription and the funds paid. This is to help prevent problems from those who do not make consistent payments but to also allow for those situations where a person might miss a payment because of illness or something else that might come-up. The only exception is if a person contacts SCS and makes special arrangements that SCS in their sole discretion approves of.
There would be a number of other terms applied as well.
The main goal is a subscription model where one can make easy payments to get all of the applications they want and need without breaking their budget and to allow for a steady cash-flow for SCS and support companies. Also allowing one to subscribe and eventually owning the applications and not having the applications shut-off as is the case with other subscription models.
I am open to suggestions as to how this should work.
So please be nice and share what you think.
Thanks in advance to all,
www.dannyfye.com
Instead of paying full price for software or just plain subscribing to get it, I suggest a “Subscribe to Own” model instead.
The way it might work is as follows:
There would be a “Super Suite” of applications that consists of everything SCS sells related to pro NLE work as well as a number of other vendors related applications. It would be a whole bowl of wax type of suite.
The total price of all the applications would be divided into monthly payments according to the “Subscribe to Own” plan that one chooses with a nominal amount (according to the plan chosen) added each month for accounting and other costs.
There would be plans ranging from one to six years. The total number of payments and their monthly amounts would depend on how many months there are in the “Subscribe to Own” plan chosen.
The person subscribing would have a subscription license during the payment period and would receive a full license once they have finished their “Subscribe to Own” plan. They would receive updates and upgrades during their plan period.
After they have completed their plan and have a full license, they could then subscribe to a maintenance plan that includes updates and upgrades to all of the applications. They can also opt not to subscribe to the maintenance plan but then they would then be required to pay the full amount for upgrades and not receive any discounts. The maintenance plan would be somewhat less than the “Subscribe to Own” plan. How much less would depend on the “Subscribe to Own” plan that was originally chosen.
If during the “Subscribe to Own” period a person should miss three payments in a row, then they would not only lose their subscription, they would also loose credit for all funds paid. Also, if a person misses a total of three separate payments during the entire “Subscribe to Own” period, they would also lose their subscription and the funds paid. This is to help prevent problems from those who do not make consistent payments but to also allow for those situations where a person might miss a payment because of illness or something else that might come-up. The only exception is if a person contacts SCS and makes special arrangements that SCS in their sole discretion approves of.
There would be a number of other terms applied as well.
The main goal is a subscription model where one can make easy payments to get all of the applications they want and need without breaking their budget and to allow for a steady cash-flow for SCS and support companies. Also allowing one to subscribe and eventually owning the applications and not having the applications shut-off as is the case with other subscription models.
I am open to suggestions as to how this should work.
So please be nice and share what you think.
Thanks in advance to all,
www.dannyfye.com