Anyway, just so you know: the pricing model will be similar to github: free for open source / public projects, small monthly fee for private projects ($5+ a month depending on number of projects).
Anyway, just so you know: the pricing model will be similar to github: free for open source / public projects, small monthly fee for private projects ($5+ a month depending on number of projects).
I'd try to structure your business model more along the lines of behavior that people already have. Some ideas off the top of my head:
1. Notebooks. All writers are intimately familiar with the concept, and having separate notebooks is a useful organizational tool. First notebook's free, and you can pay for the rest.
2. Blogging. You can have one private working document at a time, and unlimited number of public blog posts. The private document is important — no one wants to publish half-finished. Want more working documents? Pay up.
3. Collaborators. You can collaborate with one person for free; if you want multiple collaborators, you have to pay.
I'm sure you can come up with others. My point just is: structure your company around your customers.
On your first two points, this is not too far off from what GitHub does (and what I plan on doing) - the main difference is the nomenclature. You call them notebooks/blogs/documents, I call them projects, GitHub calls them repositories. The model is the same, though. FWIW, I'm calling them 'projects' because it's confusing to have multiple names for essentially the same thing.
The "first one's free" concept is interesting, and something I'm considering. However, I'm not entirely sure I agree with 'no one wants to publish half-finished' - Leanpub (http://www.leanpub.com) is built on this concept, and seems to be successful. Another argument is for open source and community-driven projects [1], which could be considered to be always in an unfinished state.