About
B2B tech brand marketing enthusiast with a strong hands-on generalist mindset. Seen it all - bootstrapped, well-funded, hyper-growth, hybrid, fully distributed, async. Operating best in the early-stage environments - joined Vinted 30something employee, just after Series A; joined Omnisend 20something employee before 1M in ARR. Tried out myself at Oyster's hyper-growth stage during Series C to understand that it's not for me. Now happily landed at Slite with sustainable growth and very much appreciated nimble async culture with often IRL interactions.
Maker History
- SliteYour knowledge base on autopilot
Forums
How do you structure your knowledge base?
There's always a big question when you starting out or outgrowing your current knowledge base - what's the best way to structure it? By teams or by subjects? Which way will make more sense for your team? We see that the majority tends to go by the departments they have within their company, but when they grow this starts limiting them. What's your experience and preference?
How do you set up your FAQs or KnowledgeBase?
We are currently using Notion for the knowledgebase, it is easy to manage, but one big problem is there's no search of the articles. We are using a chat widget, and it offers a knowledge base option but is not so cheap. I think it will be difficult once we like to use a different platform for customer support. How do you manage your knowledge base? Using some dedicated platforms?