|
|
|
|
|
by renewiltord
1923 days ago
|
|
Significantly damages your brand to do this and you'll defacto turn into a consulting company. Plus places incentives on your org to force things to be incidents since that's what pays. You'll get stuck in a local minimum of being a small-time consulting company. Or maybe you won't. But that's the reason I wouldn't want to do it. Besides, there's no way you can only access the no-support users. Google, for instance, offers one of these for their email product and are able to make the product free. In their case, they got brand awareness quite fast. But even though Google has Google One in the US if you want paid response, this forum frequently decries the lack of support. The problem is the users who occupy the no-support space cannot be selected as consumers. When you try to do that, you will get an army of users who want to not pay but who do want support. They think they want no-support but they don't, and they will retroactively rebrand their reasons to be more than money. That isn't bitterness or anything (I've always dealt with B2B software) but it's the reality of the thing as I can see. |
|
Take MS365 as an example. Most small businesses I deal with would be way better off with Exchange than with their current shared hosting email providers, but the value just isn't there for a lot of them. Microsoft thinks they're selling all this awesome stuff like Exchange, OneDrive, Teams, etc. in an ultra valuable bundle, but all small businesses see is Exchange plus a bunch of other bloat they're never going to use but are forced to pay for. They just want Exchange.
Plus, at least for the ones I've dealt with, the partner exclusively interacts with the customer, so bad support gets labelled as having a bad partner, not as Microsoft being bad. That also means Microsoft isn't incurring any cost to be the first point of contact either. In fact, the only time I've ever dealt with MS support for something Exchange related, they sucked. I ended up solving my own problem and closing the support issue by telling them what was wrong. Reputationally, we're the one that recommends it, we're the first point of contact for support, and we're the ones that take the reputation hit if something isn't working. At least that's my experience.
I see lots of small businesses that have 50 mailboxes for $60 / year at a shared hosting provider. That's $.10 per month per user. Guess how they react when you tell them moving to MS365 will be $5 per month per user? Now I'm not saying MS365 isn't worth more, but it's a HARD sell to tell a small business they should pay 50x for something that's currently working fine as far as they're concerned. Then you add in things like backup solutions changing per user per month and all of a sudden you're telling a small business they should pay 75x for the same feature matrix their shared hosting provider is selling them. They don't care about all the stupid value adds. In fact that stuff is negative value because it's unneeded complexity which results in frustration and increased support costs.