and your costs track a certain number (e.g. number of checks/hosts)
why would you bill per user?
if you did all that and you have the right LTV and CAC numbers, at certain point you could basically run it on auto pilot
billing per user, but maybe you have 1 power user in a team, and a few extra accounts for non tech/backup/etc, which login once a month to check something
It isn't and the cost of developing something... is too much for a side gig with the intended purpose for the VPS to pay for itself.
> why would you bill per user?
In my situation I don't need to bill per user (and it would be counterproductive for me to do so in the long run), my point here is what my price calculation per resources spent doesn't correlate with my resources cost in any meaningful way, at least with anything with the word 'income' in it.
> and your costs track a certain number (e.g. number of checks/hosts)
In the end I just drew some arbitrary numbers for a checks/hosts numbers, slapped the price tag of a couple bottles of beer and called it a day. One person was happy with it and he uses only a couple of basic HTTP checks (so maybe around 0.002% of VPS? Who knows). Other one said it was too much for him. *shrug_emoji*
and your costs track a certain number (e.g. number of checks/hosts)
why would you bill per user?
if you did all that and you have the right LTV and CAC numbers, at certain point you could basically run it on auto pilot
billing per user, but maybe you have 1 power user in a team, and a few extra accounts for non tech/backup/etc, which login once a month to check something