Why did we Build Count?

We built count because we wanted to build a BI tool which actually helped teams make better decisions. Like, the whole BI market for the last twenty years is basically focused on how to build a dashboard faster. It hasn't really tried to change the way the big data teams make the business drive improvement or actually make decisions. The business is still receiving the same kind of dashboards with cross filters in it. It doesn't actually drive any change. So we were trying to work out actually what does it take to make a decision possible, how do you help the data team and the business work closer together to allow them to problem solve, see the business better, look for opportunities, and then solve those problems in a in a space. And it became obvious that a collaborative canvas interface that we may have used for things like Miro or in Figma to do other types of work could work really well for that kind of, that kind of workflow decision making. So though Count is a full BI tool, it has the ability to build dashboards, it has permissions, it has a data model and semantic layer, like all the best BI tools in the world. It also has all this stuff which enables you to do that improvement cycle of seeing the business differently, mapping on metrics, problem solving, and exploring data really, really deeply, and then getting to a decision point with collaboration all the way through.