It's not as much of a direct competitor because Count's approach seems more like "Miro for Data" while ours is more like "Notion for Data".
Still, I do think people could end up comparing both our tool and theirs when evaluating a few types use cases.
For some replace LoB use cases just storing the data directly and letting users query it would be an advantage.
It's not as much of a direct competitor because Count's approach seems more like "Miro for Data" while ours is more like "Notion for Data".
Still, I do think people could end up comparing both our tool and theirs when evaluating a few types use cases.