The slack model of only paying for active users is so much better than paying for users that may not actually be using the product:<p>How users are counted towards billing?<p>"Once users are created they are automatically counted towards billing even if they don't accept the invite or ever login. A user must be explicitly deactivated, deleted, or removed from a synced user directory (if you have Google sync) to not count towards billing. Learn how to add or remove users."<p>With slack, they are strongly incentivized to keep the product engaging enough to hold onto users.
> "Monthly pricing is progressive<p>Our monthly pricing is progressive, meaning that we offer volume discounts as you add more users"<p>Just to nitpick: It's actually regressive pricing. The larger your corporation, the less you'll pay per user.
Its not huge price jump for everyone.
Its just different pricing model. Companies pay per user instead of ranges like; 1-100 user, 100-500 user, 500-1000 user.<p>So with the old model if you had 101 user, you would pay the same price as someone with 499 users. Thats unfair.
I really wish they would extend per user licensing to their on premise version as well.<p>It's completely stupid that if you are one user over the limit, you have to pay for the next block of licenses. It's a huge cost increase for one more user.
It actually looks like the way that they should have done the pricing originally. Not that i'm a fan of Atlassian as i'd rather use open-source alternatives, but this seems fairer.<p>Am I wrong?
Comparing, Microsoft Team Services pricing is based on team size, but the brackets are more granular. <a href="https://www.visualstudio.com/team-services/" rel="nofollow">https://www.visualstudio.com/team-services/</a>