Re: $50 per additional simultaneous Administrative User
I don't have an issue with raising the price but the method used to determine usage and percent increase seems flawed, at least for us, for how we actually use the admin. In the past we had the admin timeout set too high so even though someone may only need to do something for 5 minutes they wouldn't be logged out for hours so the simultaneous seat usage is artificially high. I know you say upgrade to Miva 9 to have control over the seats but until you build if the better ability to control the individual users it just becomes a big headache seeing who is logged into which site. I don't really care about a user getting booted but I really don't want StoneEdge to get booted. Like I said we would be able to get by with 2 seats per site (one being an API) and would be fine with that increase in price if we had better control over the users (which cant get booted). It feels like you are rushing to get the $ before the seat system is where it needs to be. I guess this might only be true for 10% of the people but that is still a pretty good # of customers.
I think you are missing how inconvenient the seat method is for some people. I realized you did the math on a bunch of different methods of increase and this method gave you the $ you wanted but from a business prospective on our end and what we really use the admin for it makes more sense to have a lower seat total and deal with headaches. We have 4 users for 4 sites with maybe 3 of the users spending 15 minutes a day in the admin (if I did the $ per day cost calculation based on 15 minutes a day of usage it would be much higher than $2/day) but for these 4 users we would need 16 seats even though a single user could only be doing something on one site at a time. Looking at max simultaneous log ins over a month period isn't a good way to determine overall admin usage for some people. I get that you don't have a better way to do it but that still doesn't make this a good way.
So say for a site that has only 1 user and that is all they need they still get all the improvements made since 1997 with no price increase but for us to have 3 users be able to work at the same time if need be for a few minutes a day we should pay $600 ($150 x 4) per month more than them for nothing different they they have. This is the part that seems unfair. If we did order management in the admin I could totally see the reason for us paying $50 per seat per site but we don't.
On a side note what needs to be done to be a certified developer. We have one person that does 5 sites (one site not associated with 4 mentioned above) do we really need to have 5 more seats for this one person ($10 per day for one user) to develop or does he just have to switch to working nights?
I don't have an issue with raising the price but the method used to determine usage and percent increase seems flawed, at least for us, for how we actually use the admin. In the past we had the admin timeout set too high so even though someone may only need to do something for 5 minutes they wouldn't be logged out for hours so the simultaneous seat usage is artificially high. I know you say upgrade to Miva 9 to have control over the seats but until you build if the better ability to control the individual users it just becomes a big headache seeing who is logged into which site. I don't really care about a user getting booted but I really don't want StoneEdge to get booted. Like I said we would be able to get by with 2 seats per site (one being an API) and would be fine with that increase in price if we had better control over the users (which cant get booted). It feels like you are rushing to get the $ before the seat system is where it needs to be. I guess this might only be true for 10% of the people but that is still a pretty good # of customers.
I think you are missing how inconvenient the seat method is for some people. I realized you did the math on a bunch of different methods of increase and this method gave you the $ you wanted but from a business prospective on our end and what we really use the admin for it makes more sense to have a lower seat total and deal with headaches. We have 4 users for 4 sites with maybe 3 of the users spending 15 minutes a day in the admin (if I did the $ per day cost calculation based on 15 minutes a day of usage it would be much higher than $2/day) but for these 4 users we would need 16 seats even though a single user could only be doing something on one site at a time. Looking at max simultaneous log ins over a month period isn't a good way to determine overall admin usage for some people. I get that you don't have a better way to do it but that still doesn't make this a good way.
So say for a site that has only 1 user and that is all they need they still get all the improvements made since 1997 with no price increase but for us to have 3 users be able to work at the same time if need be for a few minutes a day we should pay $600 ($150 x 4) per month more than them for nothing different they they have. This is the part that seems unfair. If we did order management in the admin I could totally see the reason for us paying $50 per seat per site but we don't.
On a side note what needs to be done to be a certified developer. We have one person that does 5 sites (one site not associated with 4 mentioned above) do we really need to have 5 more seats for this one person ($10 per day for one user) to develop or does he just have to switch to working nights?
Comment