Interesting view on user-based pricing. Basecamp, github, and most other sites that I use personally go by project numbers. User count comes in the second level. E.g. 20 projects and up to 50 users.
Interesting view on user-based pricing. Basecamp, github, and most other sites that I use personally go by project numbers. User count comes in the second level. E.g. 20 projects and up to 50 users.
A user will always be a user. One business may need 12 projects while another may only have 1 project everyone is working on. But if both have 30 users they use up the same amount of bandwidth.
And as you suggested, it really comes down to how different businesses work. Some companies work faster than others where 1 project may last 2-3 days. Someone in that company would have to be on top of closing that project and the next one. Or do they create a Generic project for the quick ones and a specific project for the more long term ones?
Properly utilizing Projects (and milestones for that matter) have always been a challenge for me with the project management applications I've used (Basecamp, FogBugz, etc).