I mentioned this before, but Slack is particularly interesting as a social graph. Tettra is one of the few (non-bot / integrations) I've seen using this in a unique way.
@rrhoover Thanks for the comment, Ryan. Building on top of Slack has been really great for us so far. The APIs are the best I've ever worked with and the platform team is super helpful. They even opened up an endpoint when were we building our MVP about a year ago so we could create comments via the API. Here's the Twitter DM conversation http://imgur.com/a/J5iF9
I think you're right in that most companies aren't utilizing the Slack Platform as a social graph. Our theory at Tettra is that Slack is going to keep becoming the backbone of most organizations, or as I like to call it, the Slackbone 😁 We sort of think of Slack as a command center that all other systems hook into. Unifying the login under your team's Slack account saves a ton of administrative headache too.
@andygcook Andy... any plans to integrate with Ryver.com? I am not a fan of how they marketed themselves by going after Slack... but I can assure you, their product is quite potent and user-friendly. @rrhoover
@jimcanto Hey Jim. Great to meet you and great question. We're pretty focused on our Slack integration right now and because we have such limited engineering resources being a team of six people total, realistically I don't think we'll get to any other messaging platforms for the next few months. We do have plans to build more integrations into Tettra including GitHub, Google Apps and other messaging platforms like HipChat/Ryver. I'll make a note to ping you if we build out a Ryver integration. Thanks again for the comment and interest in Tettra.
@andygcook My pleasure. One more question; Are the Tettra pages visible only within Slack, as in logged in members only? (Forgive me if this question is naive.)
@jimcanto Not a naive question at all. All Tettra pages are only visible by members of your Slack team who sign into Tettra with their Slack account. The one note bene is that the Slack API doesn't allow single-channel or multi-channel guests to add integrations, so those people wouldn't be able to sign in to see Tettra pages.
Tettra is a modern take on the age old wiki which works nicely with Slack. Neat idea that I'm looking forward to watching evolve. One of the missing pieces of company collaboration is the ability to create and find internal company content without the headache of logging into multiple tools. Tettra has the potential to solve that and many other problems that document and wiki tools haven't yet.
Really dig the simplicity and opinions baked into this product. Every other wiki out there tries to bolt on features or make it highly configurable, and I love that Tettra has strong beliefs about how wikis should be used.
Hi ProductHunt - Andy from Tettra here 👋🏾 Happy to answer any questions from anyone.
For some backstory, my cofounder Nelson and I came up with the idea for Tettra while working on an internal startup inside of HubSpot Labs. As our team grew, we needed a way to help us onboard new team members and keep everyone moving in the same direction. We started looking for an internal wiki but couldn’t find anything that integrated into our existing workflows or was super easy to use, so we set out to scratch our own itch by building Tettra.
After talking to a lot of other teams, we realized we aren't the only ones who needed a better way to organize internal knowledge and share updates. Most people entering the workforce now grew up with Google and want the same level of access to information in their professional lives as their personal lives. Tettra makes it easy for teams to share, access and update their internal knowledge. We believe that transparent access to information empowers people to make better decisions and understand the impact of their work, which helps teams stay ahead.
Thanks for checking Tettra out. We’ve been working on the product for a little over a year and are excited to share it with you all. We’d love for you to take it for a test drive and leave your comments, feedback and questions here.
You can get started on our site for free in just one click by signing up with your Slack account.
@andygcook Congrats! As someone who uses a wiki every day (that's the HubSpot way), I think this area is in much need of innovation. Wish you the best -- success couldn't come to a nicer group of folks. Cheers.
@tart2000 Thanks for the kind words. Would love to have you check out the product for your projects. You can chat with us right in app, or my email is andy@tettra.co if you need to get a hold of me directly. We love candid product feedback, so please let us know what you think.
@andygcook I'm tired of this member based pricing! It does not apply to every online business. I rather pay 6$ to Slack where everybody can engage than you were usually 5% of the members generate content and 95% just occasionally observe. Also, I doubt that you have smart pricing model like Slack does when somebody isn't using the product in 14 days, they don't charge you.
Excited to watch this team grow, and see how their product(s) evolve. It starts with a lot of heart, and these people put it all out there in there open... Very wiki :)
@andygcook This looks awesome. I wish the pricing wasn't based on per-user though. The agency I work at has about 8 full-time employees, and a variable number of contractors who all need access to the tool. Currently we store everything in Google Docs. When contractors come onboard, I would want to share this with them, but the amount of information they need out of a wiki is much less than a regular employee. The ease of use of something like Tettra doesn't really justify the $5 cost for a user who might barely use it. I'd rather just keep everything in Google Docs. My point is, if you charged a reasonable flat rate (~$30-40/mo), I would be MUCH more likely to sign my company up immediately.
@paulgambill Hey Paul. Thanks for the candid feedback. You rock 🤘🏽 I totally understand where you're coming from that it's hard to justify paying monthly for someone who isn't using the tool daily. We do have a way for you to remove a user from your Tettra account, so you could have contractors in there while you're working with them and then remove them once your contract is over. Do you think that would work?.
Also, just curious: would you share your entire Tettra wiki with a contractor, or only select categories?
@horsthuis Hey Nick - Thanks for the question and sorry for the delayed response here. I admittedly missed your comment. We really like Notion here at Tettra and have huge respect for what their team has built. It's really impressive and a refreshing take on writing documents.
The way we differ from them is that we're 100% focused on the wiki use case to help your team organize, share and access your collective knowledge. Tettra's slightly more opinionated than Notion about how a wiki should work and we've left out the task management features. Instead, we'd suggest you use something like Trello or Asana for that, both which we plan to integrate with eventually instead of trying to recreate those tools inside of Tettra.
We're also working on features that help you keep your team's knowledge updated over time. One of the issues we've seen with most company wiki's from talking to hundreds of teams is that people write stuff down then never update it. We have some ideas on how we can help your team keep your knowledge base organized and updated over time. Stay tuned.
At PI we use Tettra for documenting key processes and workflows. As a growing startup, we want to ensure that we have the right training and documentation as we scale. It's too big a risk to leave things to tribal knowledge. Tettra makes it simple to quickly take notes, it's clean to reach and easy to find notes created by others. While there's always ways to improve, Tettra is off to a good start.
@lindsaybayuk Thanks for the positive vibes, Lindsay. We're working hard to improve the product based on our customer's feedback. Keep it coming, please :)
I LAHV Tettra. Had researched a lot of different platforms that took too much team time to get off the ground, and found Tettra earlier this year. Implemented it myself (non-dev)... and by implement I used Slack to log in. It's as easy as that. It took a month or two to make it robust enough for the team to rely on it, but launched it internally in May. I truly believe it's made the company (we're global!) more transparent + betterfasterstronger. Slack integration is awesome (if you know how to use Giphy... it's basically "/tettra find" and then it'll pull up your wiki pages w/the best results)... but I still open up the site every morning next to my Gmail, calendar, and other must-have apps. Oh yah, and the team behind the product is pretty awesome too. ;)
@_jacksmith I saw Notion, but wasn't crazy about the tasks being included. That's cool and all, but we already have a task system that people can pop into. Tettra / our wiki, at least for us, does cover everything else that Notion lists on their site though - specs, internal KB, handbook, etc. There's some process detail in our wiki, and I actually link to our task manager if necessary, but it lists who's accountable for what / who contributed without getting into the nitty gritty step by step stuff. I also like that you can search Tettra within Slack and publish articles to a channel. Not sure if Notion has that yet. I will say that at the moment, Tettra doesn't have the nesting that Notion does. I think it all comes down to preferences / needs. :)
Guys, I love what you're doing here. So so so much easier to get answers you need or have a voice in your personal life than at work. I've managed a couple teams in my career and honestly was not a fan of confluence or other solutions -- too confusing, clunky integrations, etc. Good stuff!
@jayacunzo Thanks Jay. A lot of what informed the product's design is our extensive use of Confluence at previous jobs. A company wiki can do wonders for internal communication and empowerment, but if all that value is trapped in a unfriendly interface, it can be really hard for a team to extract it.
That's how I see Tettra helping, we're taking that immense value and setting it free. 😁
15 days seems pretty short for a trial giving the type of service this is. wouldn't it be better to limit the number of contributors, so then once they're invested, have them invite more people? I don't imagine setting up my team's wiki in that amount of time, especially with the amount of work we all do in a startup environment. So if it were people based instead of a time-based trial, I'd give this a shot right away. Hope this helps you in someway :)
@skyeselbiger Hey Skye, thanks for the feedback. I agree that the 15 day trial isn't long enough to actually start using the system fully. When we first launched we wanted to test if anyone would be interested in the promise of the product and commit to paying before fully adopting it. Since lots of folks have, we feel like we've validated that what we have built is super valuable.
Now that we're past that initial launch phase, we're going to start experimenting with a freemium model to see if we can ramp up acquisition and usage.
@nelsonjoyce Of course, and thanks for taking the time to reply. I know working on pricing models is extremely tough, just wanted to give you my two cents from working on them myself with Noun Project & Lingo.
How long have you found it takes for teams to adopt or become 'activated' (hate jargo but w/e)?
Anyways, seems like a great & simple tool :) best of luck to you guys!
@skyeselbiger I don't know if we have a single team 'activation' yet. Each team adopts at a difference pace depending on who in the company is championing it, how fast their hiring, other project priorities, and a variety of other factors.
We track multiple different actions such as creating pages, inviting users, ect. to get an idea of how 'activated' a team is.
It's definitely one of the most challenging problems that b2b collaboration products need to solve. :)
@pseudovirtual Great question. Right now we natively support importing Slack Posts into Tettra as pages. We haven't built more integrations beyond Slack to import from other sources yet like Github and Google Drive, but it's in the works Stay tuned.
We do know that it's a pain to format content again that you've already formatted once in markdown or in Google Docs. So we made sure that content you copy and paste into Tettra carries over the formatting from the original source. Does that work for you for now as a temporary solution until we build out more robust integrations?
@andygcook that makes sense, was just curious about the roadmap for absorbing more information sources. Overall the new design looks polished, congrats!
We use Tettra over at Wistia for our community Slack team, and our company Slack. It's been super helpful to consolidate info that we get from our community, as well as onboard new employees from the company end. Love Tettra and excited to see it grow!
At unmortgage.com we've been using tetra with great success, lightweight enough (think medium.com usability) with nice slack integration. We had a good look at the alternatives: atlassian, media wiki, even rolling our own. But in terms of price / ux it's a great win.
The real magic is that we "live in slack" as a team, Dropbox/Tettra/Busybot means you never have to worry too much where something is due to really well thought through integrations. Like the Tettra feature request new page, or slack driven search.
Product Hunt