Sisense vs Mode: Which is a better fit?

Ahuva S.: Hey, my name is Ahuva. I'm a project manager and I give Sisense a four out of five. Click below for more reviews like this. Before using Sisense, we didn't have much of a BI solution. We did try Click. Click did not work out well because they didn't have open source capabilities to code additional features into the product. Sisense's open source was really our selling point. It's also super user-friendly, which we really appreciated. Sisense seemed like they would work with us in the most partner or partnership experience then all the other companies. They were extremely flexible. They had a lot of solutions for a lot of different concerns that we had and really it was customer service. When we first got started, our biggest challenge was to connect the software to our business model. We had a dedicated business analyst project manager, which actually was myself, and once we figured out exactly what we needed, we put together a plan and we implemented it with the help of Sisense support. They were great. Really on target, really on time, really fantastic at helping us launch by filling in little details that we needed to get it up and running. I recommend that you, first of all, really make a really strong list of what your needs are. Very critical. And once you really know what you need out of a BI solution, make sure you're choosing the one that will accommodate your needs. They're all slightly different. They all have different features, a little bit. But I think most importantly, once you decide on a platform to use, invest the time in setting it up because it's worth it. It's a little bit more of a focus that you need to put on just getting things up and running, but once they are up and running, people will love it and it will save you so much time and money and your businesses will just work so much better. The benefits are endless.

Rohan V.: My name is Rohan. I'm a software engineer at Lyft. And I use Mode Report just for general analytics to understand our data better. And I would give it a rating of a five. I use Mode report at Lyft for different data purposes. It might be for visualizations to better understand our data sets and to be able to get better visibility into the data that we have to understand it. At a higher level, it may be to be able to generate reports, to be able to share with other stakeholders in order for us to be able to better inform them on the data that we do have. Or it may be to even just do playground reporting. Just like being able to investigate data on an ad hoc basis to be able to figure out something on the fly. For all these different purposes, Mode report has been very helpful. I would say that the biggest thing that I like about Mode is just how easy it is to use and how nice it looks. I think the combination of both makes it a very accessible platform to be able to do anything of the use cases that I mentioned before. The fact that visually it has a lot of customization aspects to it, to be able to make it feel how you want it to. And then the fact that all the features are very self-evident, very well documented, and usually pretty intuitive to be able to look at and understand how to interact with it makes it a very engaging solver to use. The two things that I suppose has the most room for growth with regards to Mode that I dislike at the moment is the use of the collections feature and the UI for being able to navigate different data sources. For a collections, being able to organize by maybe teams or purposes is an important feature that I think should definitely be there. But I think the way that I'm navigating it feels not as fluid and not as smooth as the other aspect of Mode. It feels very ad hoc, search driven. Instead of being able to view the collections as a whole, I have to explicitly find it, which only comes from having the pre-knowledge that it exists. And for the data sources, having different engines or different data sources to be able to query data on when I'm using the Python notebooks, or being able to use the data to actually get the sets from, it tends to not have much information about its availability, about if it's actually able to be used with the table in reference. And that tends to mean that you have to have, again, a lot of pre-knowledge on the actual data that you're using to be able to know if the query engine would work for it.