in a broad sense, any area where people struggle with having too much information can benefit (if that sounds like it could apply to everything, its because it can). the reason for our focus on developers is because the concepts we introduce (eg. schemas, type systems, refactoring, etc) are already familiar and so there's an easier onramp to a tool like dendorn. the goal is to make these fundamentals intuitive enough that everyone can use
an analogy I use here is excel - no one was born knowing how to use a spreadsheet but the structure and functionality it provides make it a pre-requisite for anyone working with numbers today. dendron's end goal is to be like excel, but for general knowledge
in terms of current non-software use cases, we actually have as many non-technical users using dendron as technical. some popular examples include authors (dendron is popular for world building), gamers (we have a professional street fighter user who uses dendron to keep track of different character movesets), and students (they use dendron for our ability to support math notation and diagrams)