Hi Product Hunters 👋
Andy from Tettra here, co-founder & CEO. I'm very proud of the team for building this version of Tettra and am really excited to share it with you all today.
When we launched Tettra on Product Hunt almost two years ago as the first wiki for Slack teams, the product was admittedly pretty barebones. Today marks a big step forward with this new version. We've added the ability to get started without having to use Slack, you can now integrate Tettra with your other collaboration tools, and oh - did we mention the product's now free?
Some other new features:
- Inline Mentions for Github Issues, Google Docs, and more that dynamically update with what's happening in your other systems right in Tettra so you don't have to write documentation twice (let us know what other systems you'd like to see)
- A new bot that helps keep your team's knowledge organized and updated
- More robust permissions to work with guest users and make your content private or public
- Templates to make writing documentation a snap
- Combine Templates and our new Zapier integration to automate your documentation
There's a ton of other good stuff in this new version, which I could go on-and-on about, but I'll let y'all ask questions on here instead. We'll be on Product Hunt all day to answer them.
Thanks for checking us out and for all the support over the years, Product Hunt 🙌
If you're curious how we're thinking about the future of Tettra and the structure of companies in general, please check out our latest blog post: https://tettra.co/blog/reintroducing-tettra-a-better-way-to-share-scattered-knowledge/
@andygcook Congrats on the launch. I'm particularly intrigued by the inline mentions of third-party systems (and self-updating that data). That's useful.
@dharmesh Thanks, Dharmesh! We're admittedly very excited about Inline Mentions. Makes writing pages so much faster by eliminating the dozens of screen loads and clicks you need to make to share a simple hyperlink. The dynamic updating is also very useful too because it lets you document your process in a single place to share with your team instead of having to do it in a wiki and a collaboration tool like Github, HubSpot, etc. Speaking of which, hoping to add an integration for the latter soon :)
The best companies do a great job of sharing internal updates and documentation of projects and goals, and messaging products fall way short on this because they are disorganized and there is poor signal to noise ratio.
Using an internal wiki is how the best run companies work, and Tettra is the easiest and most agile company wiki I have seen.
@mvolpe Huge thanks, Mike! We really appreciate the kind words, your support, and your advice!
Love Tettra! It is solving a core problem in company wikis. Most wikis are bare-bones and end up being not well maintained, with stale content. They are automating a lot of these manual work pieces.
How new is 2.0? I tried Tettra out 2-3 weeks ago and ultimately went with a different solution. Should I look again?
@ideasasylum Hi Jamie, there are a few things we've rolled out since you last tried Tettra, so I'd definitely encourage you to take another look. And we have a number of additional things coming in the next few weeks too...hope you like what you see!
True story: At Google, we used to have this internal wiki we built ourselves. I learned the hard way that, with few exceptions, internal tools do NOT get prioritized by internal employees. Then I went to HubSpot and saw how the internal wiki can be both a huge boost and a huge barrier to information sharing. Big fan of Tettra -- simpler than the stuff I've used before. More integrated with tools we already use. Feels built by actual, high quality product designers not people hoping to move elsewhere in their careers. Plus the human beings behind the company are just as high quality ;)
@jayacunzo Having also been at HubSpot we agree with you, Jay. In fact, our experience there was the biggest reason we built Tettra in the first place. Saw the power of sharing knowledge on a high performing, fast-growing team and wanted to make that more accessible to other people.
Pop quiz: Do you remember what Google's internal wiki was called?
@andygcook MoMA. I have NO idea what it stood for...
@jayacunzo Apparently no one knows the origin.
I'm a sucker for a clean UI. 👏
@dave_poly Big thanks, Dave! I can't even tell you how many people flee other knowledge sharing tools and come to Tettra, eager for a less overwhelming UI. We appreciate your kind words!
Useful for sharing information among a team of co-workers and you do not have to search long minutes or even giving up on finding it, which I did, most of the time.
Congrats on the launch.
Pros: Simple and intuitive— by far the best organization for an internal knowledge base tool I've come across. And a great group of folks to work with to boot, with top notch support.
Cons: Not a reflection of the tool itself, but make sure your team is very clearly aligned on what goes where. At my company we tend to have some moments of, "is that in Tettra or Quip?" So not a Tettra downside specifically, but a byproduct of how easy it can be for everyone to build documentation.
Overall Tettra has brought us out of the stone age with internal docs (although to be fair, RIP custom internal wiki, you served us well). Give it a go!
@jonah_silberg We're working on a fix for the "what is where?" issue. Stay tuned 🤫
Great job!! Super useful for high end teams!!
Looks cool but how is it different/better from Slite or Coda? We've tried out most of these kinds of 'Wiki 2.0' tools and they seem to nearly all be the same. Would love to hear your thoughts 🙂
@matthew_morley Hi Matthew - Thanks for checking us out and great question.
We differ in a couple of ways. Slite's very much focused on getting your team to write and share their notes in their product as a replacement for your other document editors. Coda seems to be set on being an all-in-one solution to replace GSuite.
At Tettra, we're taking a different approach. We think it's better to reference your existing content than recreate it in yet another tool. Changing people's habits to use a new tool is hard, if not impossible. We think of Tettra as the missing cooperation system that connects all your team's disparate knowledge in one place. Tettra allows you to pull in content from all your other collaboration tools - Github, Google Docs, Dropbox, etc - then makes it easy to share and access all that knowledge in your communication systems like chat. The main differentiator is that we offer more integrations with the systems you're already using than some of our competitors. Also, we're funded pretty much by our actual customers and have raised considerably less money than most of the other tools you could use. That means we aren't going to go out of business or disappear on you with an "our amazing journey post" where we win, but you don't. Since we don't have the pressure to hit a $1B valuation by VCs, we can do things differently like not forcing you to talk with sales people and not making decisions that optimize for investors over our customers. We're a team of makers focused on solving our customers problems above all else.
Finally, will say that's Slite's a great product and they seem to be a great team. From what I can tell, Coda seems solid too. I'd recommend checking out all the products in this space and choosing your favorite that works best for your team. Like I mentioned above, our definition of success here at Tettra isn't to dominate a winner-take-all market and crush the competition on our way to being a billion-or-bust unicorn company. There's plenty of room in the sea for everyone to succeed.
@matthew_morley @andygcook Love your attitude here Andy. Kudos on the product and recent features!
Congrats on the update guys! 🌊 Inline updates looks neat!
Would love to see Tettra support for empowering other developers to get support for their app via mentions. I.e a way for anyone to make supported "mentions" that Tettra can understand. Is that even possible / in the works?
@pseudovirtual Great feedback, Vinayak. It's not quite possible at the moment, but it's something we're exploring and plan to do in the future. Will most likely be our first step to building out a proper platform.
@andygcook can't wait 🙌
Knowledge sharing is so important to a company's success, and I can think of no other team so focused on the problem and creating a product people love using.
I haven’t had a chance to dig in yet, but I’m super excited about this. Love the Zapier idea :)