I know its just an example, buy multi user access is something I hate not being on every tier. It's a basic requirement for any business with more than one employee in my opinion.
The alternative is shared password lists that never really go away.
But that's kind of the point, right? If it's an essential for you, then you should pay for the non-basic plan. The one man band doesn't care about it, so they're happy to have the lesser plan without it.
Oh, interesting. We use this to segment between individuals/consultants and businesses. We want to be able to offer individuals an affordable plan while charging businesses an amount commensurate with value they are getting and the addl load they add to customer support and infrastructure. Any thoughts on this model?
As richardwhiuk below says, this approach appears to distinguish between individuals and businesses, but many small businesses will just create an individual account anyway and share the password for a single user account.
They're still going to use customer support and infrastructure as much as other customers, but there's going to be that little bit of extra friction for users as they find out what the password is, and communicate any changes to it.
Personally in the context of Cronitor, I'd drop the user levels, and just segment on monitor counts and features. Maybe bump Slack integration up to the team level, since that's the sort of feature which is genuinely useful to a team, and less so to an individual.
The alternative is shared password lists that never really go away.