I recently launched the enterprise version of Graphite (https://graphitedocs.com) after so many fits and starts while trying to get it shipped. So happy to finally have it out there, but now I'm running right into the natural pricing struggle.
Graphite is currently targeted at businesses and other organizations that want/need privacy and security. Google's G-Suite can't be the tool for them. Graphite fills a void and because of that, I want to price it accordingly. So, my initially price point starts at $99/month.
I wonder, though, if I should focus more on initial adoption with a lower price and then raise the price if there is traction, demand, and the market sustains it...
I would consider charging per user, per month, since that way your price will be more tied to how much value you are creating. Most SaaS apps do this, with Basecamp being a notable exception.
You need a way to get people in the door. I would consider making it free for under 10 users, 5Mb, or something like that so companies can try it without paying. Then they will be more likely to upgrade as more and more people within the company use it.
I would also consider doing direct sales, it may not be scalable but it will give you an invaluable chance to try all sorts of different pricing models and product positioning to see what is most effective.
Love it! User seat pricing has crossed my mind a few times. My only concern there is support. As a solo founder (for now), all support runs through me. So I want to mitigate that as much as possible and had considered offering unlimited seats but only one person could reach out for support.
BUT, I could still do a similar thing while charging per user seat. And I like the free plan option. I actually hadn't considered that since Graphite has a free offering for individuals. But that makes a lot of sense.