I'd guess that if your dispute has reached the level of kicking each other collaboration tools, then I would not be the target market either, in the sense that

I'd guess that if your dispute has reached the level of kicking each other collaboration tools, then I would not be the target market either, in the sense that this isn't a common enough use case for me, that it would warrant optimizing for it. A workplace like that is just not very healthy. Sure, conflicts happen all the time, and I guess it is good to be able to handle that, too. But it feels a bit odd to include this in the marketing material as a common case. If I was marketing I would try to find a way to draw attention to this feature in a more subtle way. The thing that you are trying to sell is that "all parties have access to verified decisions at all times", right? Maybe there is a way to word it that does not end up associating "loqbooq" with "disputes and projects falling apart". While I am at it: I think I understand the technical background of Points 1,2,3,4,5 of "In Case of Dispute", but it's worded very technically. Maybe there is a way of describing the benefits of a (semi-)distributed verified log more high-level and then add an additional section "How it works under the hood". And of course congratulations on the launch!