What is Tettra?

Tettra is an AI-powered internal knowledge base built for teams that live in Slack. Rather than asking employees to context-switch into a separate wiki, Tettra brings documentation to where conversations already happen — its AI assistant Kai answers questions right in Slack channels and DMs, pulling answers from the knowledge base in real time. The platform covers the full documentation lifecycle: creating pages, assigning subject matter experts as owners, scheduling re-verification to catch stale content, and measuring what employees actually search for. Tettra targets small-to-mid-sized companies (roughly 10–500 employees), particularly in SaaS, agencies, and customer-facing roles where onboarding documentation and process guides are constantly needed and frequently outdated.

Key Takeaways

• Kai AI answers questions directly in Slack without employees leaving the conversation to search a wiki.
• A built-in verification workflow assigns page owners and schedules review cycles, catching stale content before it causes problems.
• All paid plans require a 10-user minimum, so a 5-person team still pays for 10 seats.
• The free plan was eliminated in mid-2024; a 30-day trial is now the only no-cost option.
• Tettra is easier to deploy than Confluence but has a narrower integration footprint — Slack, Google Workspace, GitHub, and Zapier cover most of it.

How Kai Changes the Documentation Habit

The fundamental reason knowledge management fails in most organizations isn't that employees don't value documentation — it's that writing docs requires switching gears after a conversation is already over. Tettra's Kai AI addresses this with a "Summarize & Save" action that converts any Slack thread into a new knowledge base page with a single click. The AI drafts the page from the thread's content; a human reviews and publishes it. This pattern mirrors how modern teams actually work: decisions happen in Slack, then knowledge capture follows immediately rather than weeks later. For hiring managers, this workflow distinction matters — an ops hire who understands proactive knowledge capture versus reactive wiki-building is doing fundamentally different work.

Kai also handles the retrieval side: @mention it in any Slack channel with a question and it searches the knowledge base instantly. If it can't find an answer, it routes the question to the designated expert, then saves that response as a new entry for future use. Over time, the knowledge base grows from actual questions asked, not just what admins guessed employees would need.

Tettra vs. Guru vs. Notion

These three tools occupy different positions in the same neighborhood. Tettra is the most opinionated — it's built specifically for internal Q&A and documentation, with verification workflows and Slack-first retrieval baked in. It doesn't try to be a project manager or a database. Guru is the better fit for customer-facing teams where answer accuracy is critical mid-conversation — its browser extension surfaces knowledge cards during live support or sales calls, and its verification model is similarly rigorous. Pick Guru over Tettra when your team needs knowledge during external interactions, not just internal ones. Notion does far more than either — databases, project tracking, personal notes, wikis — but that breadth creates organizational drift. There's no verification workflow in Notion, no page ownership enforcement, and no AI answer bot with Slack escalation. Teams that choose Notion for knowledge management typically find content quietly rotting after six months. Tettra's intentional scope constraint is a feature, not a limitation, for teams that just need reliable internal documentation.

Who Uses Tettra

Tettra's strongest adoption is in three team types: HR and People teams managing onboarding, policy, and benefits documentation; Customer Success teams standardizing support responses and escalation procedures; and Operations teams at remote-first companies where tribal knowledge otherwise lives in someone's head or a chaotic Notion workspace. It's not a freelancer or consultant tool — the platform is organizational by design, requiring an admin to structure the knowledge base and manage permissions. Where fractional and contract professionals enter the picture is during rapid growth phases: a part-time Chief of Staff or fractional Ops hire is often brought in specifically to build out a company's documentation infrastructure, and Tettra is a common choice at the 50–200 employee stage. The integration stack reflects the target customer — Slack, Google Workspace, GitHub, and Zapier cover the typical early-stage SaaS toolkit.

Pricing

Tettra's free plan was discontinued in mid-2024. The current lineup has three tiers. The Basic plan runs approximately $4–5 per user per month billed annually, covering core pages, Slack integration, and limited AI features. The Scaling plan is approximately $8–10 per user per month billed annually and unlocks the full AI suite: AI answers, AI page tagging, AI FAQ generation, advanced permissions, usage analytics, and API access. The Professional plan is custom-quoted — a 50-user annual contract runs roughly $7,200 per year as a public reference point. All plans carry a 10-user billing minimum regardless of actual team size. Monthly billing is available at roughly a 20% premium over annual rates. A 30-day trial covers Basic and Scaling plans. For small teams under 10, the minimum-seat requirement is the most important cost factor to model before committing.

Limitations Worth Knowing

Tettra's narrow integration footprint is its most cited constraint — there are no native connections to Salesforce, Zendesk, HubSpot, Jira, or Asana. Teams that need knowledge surfaced in support or CRM contexts will hit a wall quickly. The editor is intentionally minimal: multi-column layouts, complex tables, and rich embeds available in Notion or Confluence aren't here. Real-time collaborative editing of the same page by multiple users simultaneously isn't supported, which creates friction during collaborative documentation sprints. The 10-user billing floor means small teams overpay from day one. And while Tettra handles the 10–200 employee range well, organizations that scale past that threshold typically find the organizational structure (folders and sub-pages only, no databases or relational content) too flat for the volume and complexity of knowledge they accumulate. The migration path to Confluence or Notion at that point is manual and painful.

The Bottom Line

Tettra earns its place by solving a specific, painful problem: companies that rely on Slack for communication but have no reliable way to capture and retrieve the knowledge that lives in those conversations. Its AI verification workflows and Kai bot address documentation failure modes that broader tools like Notion quietly ignore. The tradeoff is real — limited integrations, a minimal editor, and a 10-user billing floor make it a poor fit outside the 10–300 employee Slack-centric sweet spot. For companies hiring through Pangea, Tettra proficiency signals an ops or people professional who treats knowledge management as a system, not a folder of Google Docs.