Hi everyone! 👋 I'm Brian, the founder of OINKBase. Over the years I've worked with businesses, churches, schools and event teams, and I kept seeing the same problem: Important knowledge was all over the place. Policies lived in Google Drive. Processes were buried in WhatsApp chats. Content plans in Dropboxes. FAQs were answered over and over again. And too much knowledge only existed in someone's head. When that person left, the knowledge often left with them. We built OINKBase to solve that problem. OINKBase is an Organisational and Institutional Knowledge Base that helps teams capture, organise, maintain and publish their knowledge in one structured system. Instead of asking: "Where did we save that?" Your team can simply open one place and find it. We're starting with a simple foundation: Teams, Topics, Articles (Knowledge Assets) From there, teams can build everything from policy libraries and SOPs to content systems, learning resources and event FAQs. This is just the beginning of the journey, and we'd genuinely love your feedback. A few questions for you: 1. Where does your team currently store important knowledge? 2. What's the hardest thing to keep documented? 3. If you could add one feature to OINKBase, what would it be? Thanks for taking the time to check us out. Looking forward to hearing your thoughts!

OINKBase

Your Knowledge In Your Team's Hands.

Your Knowledge In Your Team's Hands.