Slite (@slitehq) header
Slite (@slitehq) profile picture

The self-maintaining knowledge base for teams. Find out more about us at https://nitter.cf/t.co/eqkskI9Cvt

21 cities across 3 continents
Joined May 2017
Photo by Slite (@slitehq)Photo by Slite (@slitehq)Photo by Slite (@slitehq)Photo by Slite (@slitehq)Photo by Slite (@slitehq)Photo by Slite (@slitehq)Photo by Slite (@slitehq)Photo by Slite (@slitehq)Photo by Slite (@slitehq)
Pinned Tweet
We asked 149 teams if they had a company brain. 17% have one that works. the rest have a wiki with a chat box on top. So we took ten of them apart, open source and commercial, bought and DIY. GBrain, Zep, mem0, Letta, Sylph, Gorgias Cortex, Slite Agent, Pletor, and the DIY Claude Code and git setup most eng teams run. Every one that works does the same four things: ingest, remember, prune, speak. We've collected all the user and builder insights, architecture and research notes into one free ebook. Get it here: slite.com/ebooks/company-bra…
8
12
2
90
40,654
The scariest thing in your team's stack this Halloween? An AI that answers from a two-year-old document, and sounds completely sure about it 👻 Slite Agent dressed our team up based on how we keep our knowledge. Open Slite Agent to find yours (dark mode has an extra treat 🌙)
1
2
6
316
How much of your company's documentation would you trust an AI agent to act on? That's one of the questions in our survey for our next playbook: how teams keep company knowledge accurate enough for people and AI to trust. If you own documentation on your team, or you're rolling out AI on top of it, we'd like to hear how you do it. It takes about 10 minutes, and you'll see the findings before anyone else. Take the survey: forms.gle/tTHkj8aGNNTfMTxT9 Prefer to talk it through? There's a link to book a 30-min call at the end, and everyone we interview gets a gift card. 🎁
1
3
223
Amazon’s site went down after an AI agent read an old wiki document. But how many of those documents do we all have? 👀 In March, Amazon’s retail site had four high-severity incidents in one week. One traced back to an engineer following AI advice that came from an outdated internal wiki. AI agents now read our documentation and act on it, but a lot of teams can’t say which pages are still up to date. You’d expect AI to make this easier. In practice it makes it trickier: agents answer from an old page just as confidently as from a current one, and they write new pages faster than anyone can check them. Usually someone on the team keeps updating the documentation, often without it being their actual job. That’s what our next research piece at @slitehq is about: how teams keep their knowledge accurate enough to trust, for people and for AI. The survey for our last ebook, on company brains, got so many great responses and interviews. If this topic speaks to you, I’d love your experience and opinions in this one too. Here’s the 10-min survey: forms.gle/tTHkj8aGNNTfMTxT9 If you’d rather talk it through, there’s a link to book a call at the end, and everyone who does an interview gets a gift card 🎁 💸
3
4
1
18
975
We hosted a company brain webinar to talk architecture. But the questions that kept coming back were about maintenance: 1. Who reviews a change before it lands? 2. Which edit wins when two people disagree? 3. How do you know a gap the agent flagged is real? Building a company brain is the part everyone plans for. Keeping it accurate is what they wanted to know about. Five of their questions are in the image, and answered by Yochan Khoi from Gorgias, who built their brain in-house, and Christophe Pasquier (@Christophepas) who built Slite. Missed the webinar? Watch the full session: slite.com/webinars/company-b… What's the maintenance question your team hasn't answered yet?
1
2
4
261
Your dev team is shipping faster than ever with AI. Your help center hasn't kept up. In this demo, a maintenance routine finds a merged PR that changes product behavior and suggests an update to the help center. How it works: 1. Set which documents to check, how often to run the check, and who's responsible for reviewing them. 2. Choose the sources the routine should check against. 3. Review the suggested changes before accepting an update. This clip comes from Company Brains in Action: Build vs. Buy, our 22 September webinar with Christophe Pasquier from Slite and Yochan Khoi from Gorgias. It shows the maintenance workflow being developed in Slite at the time. Full session: slite.com/webinars/company-b…
2
9
278
We're bringing Beelieve 2026 to Paris on October 14! 🇫🇷 Join us at Maison de la Recherche alongside top tech executives, finance, product, and RevOps leaders, and founders from across France. You’ll leave with actionable frameworks, pricing templates, and operational blueprints designed specifically for the AI era. While flexible pricing and packaging—whether based on outcomes, usage, credits, or hybrid subscriptions—is now table stakes, the true frontier in 2026 is building the underlying operational infrastructure that allows those models to scale smoothly without breaking quote-to-cash or destabilizing ARR. Here’s a sneak peek at what’s in store for the day:🗓️ ⟡ Scaling AI-Era Business Models | Keynote with @cbkrish (Co-Founder & CEO, @chargebee) ⟡ AI Monetization: The Era of Credits | Keynote with Baptiste Drianno (Senior Director, Simon-Kucher & Partners) ⟡ Decide, Then Run: Product & RevOps Leaders on Monetizing AI | Panel with Ramy Atassi (@gopigment), Théo Vanneufville (@DustHQ), and Natalia Williams (Product Executive & Fractional CPO) ⟡ Seats, Credits, Outcomes: How AI-Native Teams Are Betting on Tomorrow's Models | Panel with Julien Frèche (@FolkHQ) and Christophe Pasquier (@slitehq) ⟡ Chargebee Product Spotlights & Partner Showcases featuring @GoCardless, @goInvopop, and Fincome ⟡ Networking Happy Hour 🍹 Secure your spot before registration closes—only a few tickets remain: bit.ly/47RLeUk
3
8
426
You can now see where your team’s AI credits go in Slite. The AI usage page shows a breakdown for each person, so admins can see which features consumed their credits. If usage spikes, there’s somewhere to start looking. For a closer look, export every credit consumption event as a CSV and run your own analysis. Find it under Settings → AI usage.
1
148
Your dev team is shipping faster than ever with AI. Your help center hasn't kept up. In this demo, a maintenance routine spots the mismatch and proposes an update for a person to review. A look at how company knowledge gets maintained.
1
1
4
251
A company brain can be a git repo, an agent memory layer or a managed knowledge base. We mapped 10 architectures across the same four parts. Explore the research in our free ebook: slite.com/ebooks/company-bra…
2
3
1
8
383
Offslite #22 is a wrap. Five days together near Paris: builds, a trip to Versailles, pétanque and pickleball. Even the dog joined the game. A few photos from the week.
1
140
Who uses a company brain most? Not developers. At Slite, most questions come from support, CX, sales and CS. At Gorgias, engineering uses it the least of any department. Engineers have the code. Everyone else has knowledge that isn't written down anywhere. Earlier this week, @Christophepas sat down with Yochan from Gorgias to talk through whether to build or buy a company brain. Watch the full session: slite.com/webinars/company-b…
1
1
143
(Tonight) we're opening up two company brains, live. 🧠 Yochan Khoi shows how Gorgias built Cortex in-house. @Christophepas shows what Slite looks like. You'll see the same four components in both, solved two different ways. Half the hour is live demo, and we're keeping real time for Q&A at the end, so bring your questions. Join us, at your local time: 7PM CEST / 1PM ET / 10AM PT Last chance to save your spot: app.livestorm.co/slite/compa…
3
3
299
Everyone is talking about company brains. We're opening two up, live. 🎥 After surveying 149 teams, interviewing 10+ people building and using these brains, and taking apart 10 real company brains, we wrote the playbook. Now, we're showing you how it works in practice. Join us on Tuesday, 22 September as @Christophepas demos Slite alongside Yochan Khoi, whose team at @gorgiasio built theirs in-house. They'll break down the 4 core components both systems share: → Getting signals → Remembering → Dreaming and pruning → Speaking and searching And finally, we’ll tackle the question you’re actually asking: Should you build or buy yours? One hour, half of it live demo, plus a real Q&A at the end (so bring your questions!) Secure your spot: app.livestorm.co/slite/compa…
2
2
10
4,258
Finallyyyy @slitehq is in the official @claudeai connector store 🥳
2
5
330
Slite is now in the Anthropic Claude Directory. • 1-click install via OAuth • No API keys to paste • Direct access to verified company docs Try it out on Claude: claude.ai/directory/slite
1
1
5
576
One week ago we launched the interactive Company Brain 101 ebook. Not another 60-page PDF sitting unopened in your downloads folder. Just the research, in your browser, so you can jump straight to the part you care about. In case you haven't seen it, it's free, here you go → slite.com/ebooks/company-bra…
4
2
1
9
501
Ok fine, we defined one. 😌 After asking 149 builders and users, opening up 10 brains. Find it in this free Company Brain 101 guide: slite.com/ebooks/company-bra…
5
3
31
2,025