I do think hiding SSO behind "call us" is a pain however.
Fair. But wouldn't the opposite also hold true? The purchasers who say "what..I got pay $10/user/month extra for JUST SSO?"
> To integrate one is less than 100 lines of code.
Ugh not this again...
Let's use a simple example:
AcmeCo makes a widget and sells it for $50
WorldCo buys widget for $50 and uses it create $75 worth of services, thereby profiting $25.
AcmeCo has an opportunity to make up to charge up to $74.99 if they want, because WorldCo still profits. That, in its simplest terms, is what pricing on. value means.
Europe, Asia, or otherwise don't magically say "well that's not fair, you don't deserve higher profits". That's silly, so stop pretending thats the case outside of the US.
I do wonder how much of that money goes into subsidising the free tiers and paying (comparatively) enormous wages of developers to add features I don't really want.
I've seen probably ~10 companies financials that do this. It's ALL OVER THE PLACE. The reality is that the free doesn't two things: tests those new features on guinea pigs and lets you upsell to someone who has given you permission to do so.
There's no free lunch.
If we accept that service providers are going to price discriminate, then we accept that they are going to price discriminate on _some_ imperfect heuristic.
It seems to me that you have to argue
(A) Businesses should not price discriminate
Or
(B) price discrimination based on marginal features is okay but this particular feature (needing SSO) isn't very predictive
Or
(C) This particular feature might be predictive, but security is too important to be part of a willingness-to-pay heuristic, so it's unethical to use this particular feature in this way.
C seems like the argument a lot of people here are obliquely making.