Building ButterDocs, the Google Docs replacement for serious writers and teams.

Write better →
Joined February 2009
Google Docs was supposed to be the future of writing, but it led us to a dead end. Here is why it is fundamentally broken, and how we’re fixing it at @ButterDocsHQ
12
5
3
48
13,105
Michi Huber retweeted
11
8
4
72
9,151
Sol LeWitt as a service
it's not a prompt chain I built in 5 minutes on Glif dot app it's a LARGE WOJAK MODEL sparks of AGI
2
3
460
One app that sticks out for becoming very good across these dimensions is @linear. their capture, triage, and handoff are all great. What’s missing for me is a global shortcut to quickly capture an issue (though Raycast integrates and kinda does this).
1
165
It’s great that we’re seeing apps move away from trying to capture as much attention as possible, and actually work to reduce their users’ cognitive load.
1
151
😡
google docs is actually an incredible product
1
2
384
Y'all if you aren't using @ButterDocsHQ for your long-form writing, you're missing out. Notes, outlines, and draft all in one place. Every writer's paradise
2
2
308
If you’re using Google Docs to collaborate on your shopping list — sure, that works. But if your words matter, it might pay to not go with “free”.
1
95
Google Docs’ greatest strength is also its biggest weakness: ​ Everything happens in one document. This sounds ideal until you realize having only one document means: – Once published, you can’t work in private (anyone can pop in at anytime). – You can’t ask for edits without worrying about losing work (if someone forgets to track edits, you need to dig through a terrible version history UI to find the original). – You can't take the draft in a different direction (if you realize you need to make significant changes, but don't want to lose the original work, you need to create a new document). ​ The premise is fundamentally broken. ​ Not to mention, some people (like lawyers) can't even use Docs because of these privacy issues. They're stuck in Word. ​ To solve all these issues, we have to fundamentally rethink what a document could be: – We shouldn’t think of it as a piece of text. – We should think of it as a process. A collaboration. A series of moving parts that come together to form a result. ​ This process involves multiple drafts, to experiment, to write in private, to work in parallel, that can easily be merged into the final version. ​ git’s workflow enabled this kind of collaboration for engineers, and changed the way programmers work forever. It’s time this workflow was made available for writers. ​ At Butterdocs, we're building a complete writing environment so you can: – Be more productive – Collaborate seamlessly – Enjoy privacy – Keep all your notes, ideas, research, and playbooks in one place – And so much more ​ Welcome to the future.
2
1
2
12
5,188
• You can't "stash" ideas for later. If something doesn't quite fit, you've got nowhere to put it. Need to open yet another doc, which is...not productive.
1
6
207
• There's no big picture view. The best they've got is a table of contents. Sometimes you want to think about the ideas, not the words you use to communicate them. Why can’t I focus on high-level ideas only?
1
5
185
Writing = thinking, and this is not a good environment to think in.
1
5
298