Grow vs Mode: Which is a better fit?

Thomas: Hi, my name is Thomas and I'm a senior director of information services. I would give Grow a five out of five rating. For more reviews like this, click the link below. Previously we were using more enterprise in Tableau, however it did not fit our business needs. While Tableau is a great tool in its own right, it did not provide the ability to really scale this tool to thousands of users across hundreds of clients to be able to distribute this effectively both internally and externally and everyone to interact in the same BI and data visualization environment in a way that Grow has enabled us to do. The reasons we chose Grow were really around three main components. One was accessibility; being able to not only have a very accessible tool to our team in terms of ease of use and the low-code environment, but accessible to internal stakeholders, lots of different visualizations and lots of different customization options, and also accessible to external stakeholders when it comes to the number of users. Accessibility was a big component, as well as the overall ability of Grow to make BI accessible to the masses. Grow has a very simple interface, both on the front end and the back end, that allows people with very, very little data knowledge to take advantage of the tool and be able to get a lot out of the tool. Those two components along with the general low price point are the three primary reasons that we decided to go with Grow. Overall, it was incredibly easy to get started with Grow. Not only is the internal tools in terms of the user management account management very simple and straightforward compared to some of the more enterprise platforms, but specifically data connections is where Grow makes it really easy. If you have experience using other visualization tools you know it can be a challenge to make sure that the API integrations are effective, but the plethora of native integrations Grow offers makes it incredibly easy. Most of the time it's just like you're logging into the platform or website. So getting started with Grow and being able to produce metrics and produce visualizations was easy to hit the ground running with. If you're considering Grow, I would honestly ask you to consider your use case and how you're going to functionally use this business intelligence and data visualization tool. If it is an internal only use case, and you have incredibly complex use cases around certain scenarios, graphs, data sources, whatever it may be, maybe Grow isn't the right solution for you. However, I would venture that most of the people out there, you actually have a more regular use case than you think. You're trying to get data connections from a number of different sources into a single location that your team can easily access and use. The entire purpose of Grow is bringing business intelligence to the masses, and that's what this is about. So if you are considering that use case and it fits you, I would absolutely encourage you to get ahold of the folks at Grow and give it a try.

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.