***Solutions (Personal Opinion)
Solutions are based on current problems, and other instances.
**Remove payout business model and change to a new paid assembly subscription.
Developers would be encouraged to work on assembly since they would be receiving a monthly salary based on the number of users on the new paid subscription. Since we are working on providing frequently updated core and assembly, there would be higher chance that ensage user base would increase significantly. Thus, increasing income for both ensage team, and developers.
Users would be encouraged to sub since all paid assemblies made by dedicated assembly team is included. And assemblies and request are frequently considered as top priority, no more hanging user that is waiting for a developer to reply.
**Gather a dedicated assembly team. (I would suggest maximum of 4 developers)
Assemblies are frequently updated by the team, all paid assemblies made by them would be included in the new paid subscription. Ex. beminee/yeeeee/jumpering/idcnoob scripts. (depending on chosen developer)
More paid assemblies would be made available, since there is already a motivation to work (being paid monthly).
Developer are less likely to be inactive since they would be afraid to lose the monthly salary. Thus, creating more frequent updates/fixes.
**Old paid assembly remains in the database, and new recoded scripts are in the new paid assembly sub.
Old users who purchased paid assemblies can still use the old paid assemblies, and old developers can still update their old paid assembly if they wish.
**Rules against trolling new users.
Would help new users be comfortable with ensage, the more they are being helped the more chances that they would recommend and subscribe for a long time.
Remember ensage is not the only hack for dota, if users feel bullied, we lose our customers/users.
*Making these changes would hopefully increase more users thus making more income for both ensage and developers.
*Its is better to have a monthly salary for developers since we are aware that a one-time payout tends to have more problems in the end.
*Developers are given more compensation in time, since we would get more users because of frequently updated assemblies. More users>More income>More better and updated assemblies> more new users to come (cycle).
*User base would most likely increase, since all new paid assemblies, in the new paid subscription are being updated and fixed regularly.
*It is better to have monthly salary, rather than developers don’t get anything when they fix their assemblies. At least with monthly salary coming from new paid subscription, developers are paid as long as they follow rules. (fixing assemblies, making new ones, updating etc.)
New paid assembly subscriptions
What’s included – All paid assemblies that is rewritten, and new paid assemblies.
Ex. 20usd per user/ per month.
Assuming we have gotten 100 subs.
Ex. 20usd x 100 users = 2000usd divided by 4 developers = 500 monthly per developer.
Now we only assume it if we have 100 subscribers for the new paid subscriptions. There is a higher chance to get it to 150-200 users, depending on how development team performs. (This is only my estimate) I believe the more the development team fixes/updates the assemblies, the more users we will have.
If ensage are being kept updated, no trolls, assemblies are perfect, request are considered, no user that is kept hanging and waiting. Our user base would increase.
To increase user base, I would suggest doing a scheme. Get users to spread ensage by making referrals. Each referral grants them 15 days of free ensage etc. Make ensage private, why private you ask? because once we establish a good community with perfect running management of assemblies, there might be an influx of customers, that would make valve notice ensage more, and might have a problem in the end. Also making it private, gives users a good feeling of being accepted in an underground hacking community. The more likely they would stay, because its “private”.
I know user are on the losing end of this proposal, since users need to pay more for a new paid assembly subscription. But look at it this way, users will no longer be burdened with long assembly update, all of the paid assemblies are free when you sub to the new paid assembly subscription. There is a dedicated team to help in your question, suggestions, and fixes. Ask yourself if you like the current model, where you pay for a one time assembly, but when you request or there is an update, the original developers just ignores you, and assemblies are being more broken everyday. I think what my proposal would do is to reverse everything, and ensage would be at its 100% potential.
Thank you if you read it all, and comment if you think this is a bad idea or what. This is only me trying help ensage.
PS. I am a business management professor, and do a lot of consulting, when companies have problems. Since I love dota, for stress relief, I decided to make this thread, so maybe it could open admins/owners/users/devs eyes.
Thank you. - anonymouse since april 2017
It looks like you're new here. If you want to get involved, click one of these buttons!