Beegit

The easiest way for teams to write together.

get it
There are no images or videos added to the gallery.
Add to gallery

Reviews

Discussion

You need to become a Contributor to join the discussion - Find out how.
Matt GartlandHunter@mattgartland · Founder, Winning Edits
As an editor and writer—for my own projects, my teams internal projects, and especially with clients—collaborative writing/editing is paramount. I've really struggled to find good collaborative writing tools. Editorially was good for a while. Alas, they're gone. Google Docs has improved but still has a long way to go for serious editorial work. Beegit is the best tool I'm aware of right now that delivers the caliber user experience and feature-rich capabilities my team and I need to be efficient, effective, and (ultimately) successful with our editorial work. I've had a chance to get to know the Beegit team. They care deeply about serving the evolving needs of the writer/editor community, especially those with a strong product-orientation. They get it. And they're smart enough to be leveraging ideas from adjacent niches (e.g. the Github community). Beegit is still early in its evolution, but I'm wildly optimistic about it. If you're a writer, editor, on a team of writers and editors, a product manager or product leader, or—heck—anyone that recognizes writing as an instrumental business skill and advantage, you should give Beegit a serious look.
Mike CottrillMaker@mrcottrill · CEO, Beegit
@MattGartland, Thanks for the kind words and thanks for the listing! We're excited to talk with the Product Hunt community. We're building the best tool for people to write together. That means all the web-first tools required of a collaborative editor (Markdown, easy export, real-time visibility), but it also means easy-to-use team tools like @mentions and version control. My partners and I would love to hear any questions from the Hunt community!
Matt GartlandHunter@mattgartland · Founder, Winning Edits
@mrcottrill You're welcome, Mike. I'm totally sincere in my comments. Could you share more about your vision for Beegit, especially in context of the other writing/editing tools spring up on the web? As I mentioned, I've experimented with and struggled with a number of other collaborative writing/editing tools. What lies ahead for Beegit that's going to keep it on a compelling growth trajectory?
Mike CottrillMaker@mrcottrill · CEO, Beegit
@MattGartland Well, this is a topic I could talk about for hours, but I'll try to be brief. In our mind, the collaborative editor is important. But what's really important is moving the workflow along. We put a high value on our Markdown editor, but we hang our hat on our workflow help. It's not enough to have a shared place to write (there are plenty of fine tools out there for that, including another Hunt here today). But what makes a team write better together is an easier way to collaborate and make sure the whole team has visibility into who is doing what. We often say our product is like Google Docs meets Trello. It gives everyone a centralized place to write, communicate and stay on track. The teams that are using it love to manage everything in one tab, and our current focus is making iterations that help them get more content done on time.
Vinish Garg@vingar · Co-founder @mystippi @ContentHug
Nice app for internal content workflow though not sure if can serve the purpose of a product knowledgebase. Two two positives are (a) the little track-changes interface for common and shared content, (b) the @mentions for easy targeting. Looking forward to dive deeper!
Mike CottrillMaker@mrcottrill · CEO, Beegit
Hey @vingar - Thanks for the comment! We're very glad you like the version control/change tracking process and the @mentions. So far we've seen that the @mentions are tied with Markdown as the user favorite for improving workflow. We're ready for your deeper dive! Let me know if you have any other thoughts as you use the product more.
Vinish Garg@vingar · Co-founder @mystippi @ContentHug
Nice app for internal content workflow though not sure if can serve the purpose of a product knowledgebase. Two positives are (a) the little track-changes interface for common and shared content, (b) the @mentions for easy targeting. Looking forward to dive deeper!