GitBook combines powerful docs with AI-powered search and insights to give technical teams a single source of truth for their knowledge. Effortlessly create, surface and improve documentation in the tools you use every day β such as Slack, GitHub and VS Code.
So I really like Gitbook. I've been using it for about 2 years now and I've made it my source of truth for a number of things. I have two primary issues I'd love to see improved as an individual user.
1. Pricing is unrealistic for individuals & small Teams (1-3 people). I'm not sure if this is by design to price us out, but if so, it's working.
$15 Base fee + $99 monthly platform fee? The only features I'm looking to "unlock" is export to PDF and shareable link so one or two other people can view or edit those shared items.
I've tried to get more people on board with Gitbook, but as soon as they see the pricing they laugh it off, and I can't share anything with them to show how good it is because that's behind a paywall, essentially. Kind of a bummer.
I find that pricing to be absurd for the ability to export to PDF and share some links as an individual. I would like to see something in the $15-20/month range.
Hello Sara and the GitBook Team!
Congratulations on your major launch! GitBook's journey towards becoming a leading knowledge-sharing platform for technical teams is commendable. The introduction of features like turning Slack conversations into documentation and creating docs directly in VS Code shows a deep understanding of the needs of engineering teams. The new UI design and brand overhaul add an exciting touch to the user experience.
However, there are some potential concerns and questions to consider. Firstly, with the integration of AI to extract and structure information, how does GitBook ensure the accuracy and relevance of the content generated? AI's interpretation of technical discussions can be challenging, and inaccuracies could lead to misunderstandings. Secondly, as GitBook becomes more feature-rich, how do you maintain simplicity and ease of use, ensuring that the platform does not become overwhelming for new users or smaller teams?
A question for you as the CEO: In an environment where technology and software development practices are rapidly evolving, how does GitBook plan to continually adapt and innovate to meet the ever-changing demands of technical teams? Are there any specific areas or technologies that you're particularly excited about exploring to enhance GitBook's capabilities?
I'm looking forward to seeing how GitBook evolves and contributes to the efficiency and effectiveness of knowledge sharing in the tech community.
Wishing you the best with your continued growth and development at GitBook!
Replies
Mojo rizz
Unrevealed
GitBook
SprintsQ