Every organization has the same problem. The knowledge is there — scattered across drive folders, buried in an LMS, half-documented in a wiki, living in the heads of people who've been around long enough to know where the bodies are buried. The tools exist. The content exists. And yet people still can't find what they need, don't know what they don't know, and learn most of what actually matters from whoever happens to sit next to them.
Knowledge bases store documents. Learning management systems track completions. Wikis collect pages. SOP tools hold procedures. Each one does its job. But none of them understand the organization — the way a product update connects to a training gap, the way a policy change affects three teams differently, the way one person's expertise is the answer to another person's question they haven't thought to ask yet.
The connections between things are where organizational knowledge actually lives. Not in any single document or course, but in the relationships between them — and between the people who create, use, and need them.
That's the problem we set out to solve. And it's why we needed a new name.
Why not EquipBot
EquipBot was a good name when we started. It said what it needed to say. But as the product grew, the name stopped fitting.
We're not a bot. We're not a single-purpose tool that answers questions from a knowledge base. What we're building is a system that understands an organization's knowledge at a deep level — the content, the people, the skills, the gaps — and uses that understanding to connect the right knowledge to the right person at the right moment. That's a fundamentally different ambition than what "EquipBot" suggests.
The name needed to catch up to the product.
Why Mereon
Mereology is the branch of philosophy that concerns itself with the relationships between parts and wholes. How individual pieces connect to form something larger. How the structure of those connections determines what the whole thing actually is.
That's not a bad description of what we do.
An organization's knowledge isn't a pile of files. It's a structure — videos connect to lessons, lessons connect to roles, roles connect to teams, teams connect to goals. A single piece of content means one thing to a new hire and something entirely different to a senior engineer. The value isn't in the parts. It's in how the parts relate to each other, and how those relationships surface the right knowledge for the right person.
Mereon comes from mereology. It's the study of connections made into a name. We think it fits.
What's next
We're launching the new name alongside a wave of new capabilities that we'll be writing about here over the coming days. This isn't a rebrand for the sake of a rebrand — it's a marker for where the product is headed.
Stay tuned.
LinkedIn
Facebook