A lot of knowledge tools promise organization, but what they often deliver is one more place your information can get trapped. That tradeoff starts to feel worse over time, especially when teams realize they are paying to re-find their own material inside someone else's interface.
The better path here was local-first. That meant structuring documents, notes, and captured web material in a way that stayed portable from the start. The system needed to be searchable, reusable, and ready for AI assistance without forcing the team into a permanent subscription dependency.
From there, the work was about building useful retrieval patterns, clarifying naming and storage conventions, and making sure the information remained understandable outside the tool itself. A knowledge base should still make sense even if the app changes later.
That is the real point of local-first thinking. It is not nostalgia. It is leverage. When your information stays in your hands, your future options stay open too.