Domo Reviews

For a product company, I used Domo. It was my client, and I cannot disclose details, but it was in long storage products. It was purely for marketing.

The most ideal aspect about using Domo is it can accommodate a huge amount of data. Apart from that, we loved the number of sources it provides in a single platform, such as the capability to connect it. These were the two major reasons we stayed with Domo for some time.

Domo helped our team work more effectively. None of the other tools provide the kind of support that enables chatting and working on the same item simultaneously. In other tools such as Tableau or Power BI, you keep sharing the latest version of the dashboard and then someone else keeps updating. Working at the same time on the same dashboard is possible on Domo.

The Domo data visualization feature is situational. The type of dashboard and the type of data that I'm planning to represent to whatever KPI suits the picture. Another thing I appreciated in the dashboards was filtering within the chart itself. You can keep filtering on at two, three levels within the chart without moving out of the dashboard.

I have experience with Domo and Microsoft tools.

Domo is losing out in the pricing area. We tried pitching Domo to many of our clients, and they liked it initially, but the pricing point was something they were not comfortable with. That would be a good boost if you are trying to fetch more clients or a bigger volume of business. I haven't yet seen the AI features, so I cannot comment on those.

Different BI tools have their strengths and weaknesses. If you consider Tableau, it is very adjustable. You can make any kinds of dashboards in Tableau. You can do many things. Power BI has a good background of Microsoft helping it with its Microsoft services. Different tools have different plus points. The strength I found for Domo was collaboration while building dashboards and pipelines, and the volume of data it handled. Domo has its own place in the market, but I suggest the certification costs and the pricing for clients need to be reduced. It's a good tool. There should be a free version of it for people to learn easily so that they get adapted easily and get used to supporting the Domo community. That is very important.

I have one and a half years of experience with Domo.

I did not reach out much to Domo support, but a few seniors of mine who reached out found it satisfactory. Their general experience was good. Domo's support can be rated nine or ten on a scale of one to ten.

Positive

The initial setup with Domo was straightforward.

I did not use Domo's self-service analytics tools because I was serving a client, so the self-service use cases were not enabled. That was not in our use case.

I did not use Domo's AI-driven analytics or insights for uncovering trends or forecasting outcomes. I was using Domo before the latest update, and I no longer use Domo as I'm working with a different client.

I did not use mobile accessibility with Domo.

I rate Domo 8 out of 10.

I primarily use Domo for building reports and dashboards against our Snowflake data warehouse. It is utilized in a university setting with a couple thousand students.

Domo is a local company, and I have found it to be rock solid. I have been using it for four years and have been able to extract the information I need from it.

One of the biggest problems is that end users require a license to run their own reports and dashboards, which are fairly expensive. Domo is also not the easiest product to use and is more expensive to maintain and support. Additionally, data caching issues, limited scheduling options, licensing, and AI feature costs need improvement.

I have used the solution for four years.

Sigma, which is written for Snowflake, scales more easily than Domo. Domo's ability to handle scalability is limited.

Domo's customer service gets back fairly quickly but can be slow at times, especially for smaller clients. While they eventually provide the correct answers, their support for smaller customers could be improved.

Negative

The initial setup of Domo is more complex compared to Sigma. I would rate Domo as a six or a seven in terms of complexity, whereas I might rate Sigma as a nine in terms of ease of use.

Domo is expensive compared to other solutions.

I am considering Sigma and am evaluating its features compared to Domo.

Overall, I would rate Domo as a six. In the early years, I might have rated it an eight, but as I have learned more about it, my assessment has gone down. We are a university, and we did not originally choose Domo; it was selected by a previous CFO. Our current evaluation indicates it might be oversized and costly for our needs, so we're considering alternatives.

For a company that doesn't already have an electronic data warehouse, has disjointed data, and wants to have a repository and analysis all in one unit, that is what Domo's target market is.

The places we use Domo the most have built-in data governance. Being able to define the data as it's coming in and keep those definitions constant, being able to show where the data is stored and how the data is processing in has been valuable. The cloud connections have been really handy. Being able to tap in and pull data from various data sources has been useful. The monitoring of how many credits we've consumed is also a good feature.

Domo's real-time insights and customizable alerts are one of their better features. I really appreciate the alerts and identification of problems. We have to build that in addition when we move over to Sigma and put thought to it.

Domo is the premium option of all the choices. It has fancy features including a built-in chat program with the Buzz feature that no one uses.

When I arrived about a year ago, we had 12 different ways to connect eight different data sources, which was not ideal. I've narrowed that down to using only two, and neither of them were Domo. There were better ways to do it. The capabilities are there, but it ended up being better to go with Fivetran or Azure Data Factory than to leverage Domo's built-in connections.

Domo is capable of doing a write-back, but it isn't smooth. That's one feature that is lacking - the smoothness of the write-back feature.

So that is where we may go back to Domo one day. I don't want to completely cut us off from ever using them because I think they may become the world leader. My concern is that we have to put all the data in their system and then we can use AI. That prevents us from being able to do anything outside of the Domo ecosphere. They limit what we're able to do.

The first time I conducted a review of Domo was probably 2011, 2012 when it was first being developed.

The support with Domo primarily directs users to look up solutions in their giant knowledge base, and they rely on the large number of free conversations. There is an AI solution. There is some support, especially if you're talking about leaving them, suddenly they become much more engaged in solving problems.

In my case, I came in and everything had been set up before. Anything that was convoluted is really difficult to unwind, and there was a lot that was set up convoluted. The other problem is if you have too many admins, everyone can add data, and so the data can be added two or three times and become dependent in the format that it's in with the mechanizations of the data, their solution to ETL, being dependent on the formatting of each person and the way they added the data, and that can be a nightmare to unwind as well.

Neutral

The initial setup is the easiest thing to get into a total tangle-weave, similar to a cat's cradle nightmare. It is really easy to do, but difficult to do well.

The return on investment is there, but if we can do the same thing for $100,000 less, then it's not a good return investment compared to the other alternative.

We have opted to go away from Domo. We selected Sigma because of the price, along with our extensive use of input tables and Excel-focused sort of view.

Currently, my team, which consists of only a handful of people, went to Domopalooza and saw their latest and greatest offerings. We can replicate all of that, so it makes sense for us to own our data and own our AI and to build it so that it functions.

The review rating for this solution is 8 out of 10.

Our primary use case for using Domo is from the consulting point of view.  We use it for unified analytics where they have a lot of batch data and stream data. We want to combine and ensure, particularly that the deliverable side form categories, like real-time dashboard reporting, KPI-driven reports, ad hoc users, ad hoc reporting, as well as advanced analytics and data sets.

The most valuable feature currently is the self-service BI availability in Domo. I would say the data file fabric solutions where the users themselves are responsible for generating their own reports.

One of the improvements that could be made is related to improved storage options. I would also like to see Domo being absolutely one hundred percent compliant with military sets of data.

I have been using Domo for the past two and a half years.

The stability of Domo is excellent.

The scalability is excellent. We have input close to fifty billion rows in Domo, and this is where we saw the cards winded in pretty slowly. So we had a performance issue there, but say maximum up to twenty-five to thirty billion, this product is flawless. But when we talk about big data analytics with too many self-service components, this is where we see some performance depreciation.  We have more than two hundred using the solution.

Technical support is pretty good. However, when a customer claims, that it does not go well with the technical support because of certain items, customer support says, "Yes, it will work," but the technical support says, "We do have a limitation." So there is a gap or contradiction that needs to be addressed between customer support and technical support.

The setup is straightforward and self-explanatory. We do not have to go through a lot of complex steps. The installation was very fast just a couple of minutes.

We are the third party so we did not have to look for other assistance.

The pricing differs from customer to customer, depending on the package.

For mid-size or small customers, this is absolutely fine. However, this product has not been tested on a robust enterprise-scale application where we handle billions and billions of records. So this is where we see the application breathing out a bit. I would rate Domo an eight out of ten.

We use the solution to create a data visualization of all the business processes.

The solution's most valuable feature is the maps tool. It gives a holistic view of geographics. Apart from it, the feature that identifies the sizing of components based on the distribution volume helps us too. In addition, the solution's ability to update the overall visualization each time a new filter is applied is also the best feature.

They should work on making the solution easy to use. Presently, it requires specific knowledge for usage. They should include service-based reporting features similar to Power BI. They should also add more AI features to increase the accuracy rate. In addition, they must consider including a feature for reusable objects as well.

We have been using the solution for three years.

The solution is highly stable, and I rate its stability as a nine.

The solution's scalability is based on the infrastructure. So, the entire configuration changes whenever we add servers to scale up. Also, licensing is very high for scalability. We use the solution for enterprise business. We have thirty-five executives using it to generate global performance reports for our organization.

There needs to be a proper setup trial provided for the solution. The data processing happens daily for around six hours, followed by report generation. Accordingly, the solution gets deployed with the changes every day.

The solution is expensive compared to Tableau. Its license costs around $750 a year for one user. Apart from that, there are additional costs for infrastructure, maintenance support, etc. 

I rate its pricing as a four.

I recommend the solution to others. It provides data security and has good use cases. I rate it as a seven.

Our primary use case for the solution is pandemic data and ensuring that the information is de-identified before it is presented to decision-makers.

The solution has assisted us in de-identifying the data and providing it promptly, so decision-makers can decide whether to keep classrooms open and staff on campus early. This has been instrumental in making sure the university stayed open because other higher education institutions had to close.

We have found securing data valuable because it allows us to provide information without identifying individuals.

The solution can be improved by making the cost more affordable because, with the current price, we're probably not going to be able to continue using it. It is expensive and the pricing structure compared to other computing data visualization options is double.

We have been using Domo for approximately three years.

The solution is very stable.

The solution is highly scalable.

We have a good experience with customer service and support. I rate the solution an eight out of ten.

Positive

The initial setup is straightforward compared to similar solutions we have set up, and we focused on many available data sets. We had one person that led the project that implemented it.

With the original pricing, there is a return on investment.

I rate the solution a nine out of ten. I advise new users to define a few folks on the IT side that are comfortable dealing with implementations in the cloud instead of on-premises.

I was building executive dashboards for project management offices. I would have a portfolio of projects. Mainly, it was for opening new units and new markets. I would have project plans and action item logs, and I would use those in Smartsheet, and then I would ingest those up into Domo and I would be able to run statistics and metrics to track the progress of any given project. I would be able to calculate things like percent complete according to the calendar, percent complete of the budget, percent complete of the scope, number of tasks, percentage of tasks against total tasks, et cetera.

I could, for each project, if I wanted to drill down, go in, and see the detail of the tasks. I could also go see the action items, the risks, the issues, and the action items associated with the project. Therefore, I could see how many of those there were, what were critical, high, medium, or low, and which ones were late in terms of the due dates and things like that. I could run both a general project status meeting for a given project and also, at a high level, show a swift health check of a set of projects. That was very helpful for the executives.

Domo is very strong.

In general, Domo is very powerful and very easy to use, relatively speaking. And so I didn't have a lot of complaints. I'm unsure if I was fully tasking it and stressing the Domo system.

There were very few cases on some of the tables, the data tables, where I wish there was an additional feature or two. However, they were particular. What I wanted to see was the ability to collapse when you group a set of rows, let's say when you group them by status or health, so you have your red projects grouped up top. I wanted to compress or collapse that group of red and then open the yellow projects and then the green projects. There were a bit more features in the tables than I wanted to see.

They have a widget that you can use either in Microsoft PowerPoint to pull over data into your PowerPoints and refresh graphs or charts or metrics or tables. I would love to see that available in Google Slides. I used it successfully in PowerPoint; however, at one company, they were only using Google products, and so that widget didn't help with reporting in slides. Therefore, we had to do a bit more manual work for our quarterly business reviews or monthly business reviews to produce our executive presentations.

Sometimes the fonts were difficult to read if you're trying to put a lot of data in a table and show a lot of rows. Sometimes the fonts got too light, and you had to really play with it to try and figure out how to make it readable.

One thing I had to do, and I don't know if it's necessarily a bad thing, was when I was running a meeting, I would have to go turn off the data jobs. If I was running a meeting and a lot of times people were scrambling in the background to do their updates even as the meeting was occurring, it would cause the page to render very slowly. It would sometimes pause or freeze. I found that if I went and turned off the status, the data update jobs that we're pulling data from Smartsheet, then the meetings would work more smoothly, and there were no interruptions or delays.

I started using the solution since 2019. I just finished a job and used it up until this month.

It is stable. I never had it crash or go out of service.

I’ve never witnessed performance problems like graphs taking a while to render, things like that, only when there were data updates going on in the background.

I never saw any scalability problems. There’s probably not a scalability issue. It’s just if you've got multiple processes hitting the same data source. Sometimes it has to wait for the data to update. Perhaps maybe there's a way in bigger organizations where there's a lot more going on where that could become a problem, and you might have to schedule how that gets done.

I had everything set to real-time, meaning if a database update was made over in Smartsheet, it would immediately notify Domo and start to pull the data over. However, if I had set it to do it every hour or two times a day or something, then that wouldn't have interrupted the project meetings.

It scales pretty well. My data set was not big. I didn't have millions of records or billions of records, so I never really stressed the system. I had 100,000 records or less across all my entities.

At one company, it was being used across all the major teams. There's a data engineering team and a finance team that was using it for the general ledger reporting. Operations were using it, and those operations encompassed a large number of things. That included procurement, construction, hospitality, training teams, and HR teams. So it was fairly broad. However, we were a small division in the company, so it was less than 100 users.

At another organization, I was the only real power user. However, there were 35 people when I left that was given access and were using the reports or had access to the reports. It was not that many in the grand scale of an enterprise or big business.

I don't remember opening a ticket. I did at one company when we had a professional services team helping us set up the instance, and we had a success manager, who were all very skilled. For most of my time there, I was able to work with the implementation team that was able to answer any of my questions, or if there was any logic I was trying to work out, like to take daily snapshots is something that you need to be shown how to do, they could help. That said, once you have the model, you can copy it and replicate it across to other data sets.

I’ve never had a bug and do not remember saying "This system's not working."

We had Tableau. However, the problem with Tableau is it was part of the corporate team, and you had to wait a long time to get at least the way they set it up, where you had to make a request to get your data into the data warehouse. Then, it had to get loaded and cleaned and architected and then approved and pushed out to the production instance. You could start to run your reports after that. They might have to structure it so we just gave up on Tableau since it was such a heavy enterprise system, the way that the one company was using it.

That's the reason why the chief technical officer for our division brought in Domo, as it was a rapid solution that users could get in there, and analysts could start working right away and running reports and analyzing data. That's the only comparison I have. We were a Microsoft shop, and I don't know why we didn't consider Power BI. However, Smartsheet was the tool that was being used, so it didn't really come up as an option. My guess is if I go to my next Microsoft shop, I'll use Power BI instead of Domo since it's probably already in-house and cheaper, and it's pretty flexible and fast.

A company that I used to work for switched over to Power BI.

I was able to have my PMO executive dashboards up and running in a couple of weeks. It's straightforward. If what you want to do, it's swift and easy. Like my data is projects, the tasks, the projects, and the action items. If I have budget data, I pull in budget data as well. Then, I just need to make sure I know how those three link up on the keys. And if that's done correctly, then you can immediately start building the dashboards and linking in all the data. To get it to work out what the executives want to see is just iterative, but you can have something that an executive can see very rapidly, just in a couple of weeks, if not sooner. If that was the only thing I had to do, I could get something up and running very quickly.

I had an enterprise license.

It started out at about $600 a seat. However, then as we started to grow, it scaled that down to about $330 or 3$50 a seat, if I'm not mistaken. Obviously, it's scaled pricing. When I was using it previously, they had the full enterprise license, and they'd negotiated an even lower price.

I don't know if I know the cost when you compare it to all other types of software that are being used across the business. Perhaps it's cheaper than Tableau. However, I don't know all that. However, it was a tricky part of the approval process for me to get that approved due to the price tag. It wasn't tricky at the other organization I worked for, as the CTO knew what he wanted it. He's a very senior member of staff and has a big budget. He was able to get that approved.

I am just an end-user.

I’m not sure which version we’re using. It's a software as a service solution, so it's the latest one. I wasn't using all of the capabilities of the tool.

I’d advise other users that it goes much faster if you really have a sense of what your data. I have an immaculate, apparent picture of my data in my head. It's straightforward. Its projects, tasks, its action items, and budget information are great. As long as you know how you're going to link that up and what you want to be able to analyze. For example, I want to be able to see over time that my issues are coming down. They're shrinking by the day. I want to see a daily snapshot of the total number of issues on my projects. If you have that type of clarity, you can set up your system and data routines reasonably quickly.

After that, it's really just, how do you want to display it? That's just iterative and working with some fairly straightforward widgets. To get your data nice and clean, ensure you understand how it will all hang together. That’s what's nice about Domo. You don't have to formally create a data model behind the scenes, as long as your data from one table to the next has the same column with the same name, then when those. When you put different widgets on the page, you can configure the page to each all of the widgets on that page to respond to that same key.

They'll all filter on the same key even though one data type may be tasks and the other one might be action items. If you have the project ID in both of those data sets, then they'll both filter. Therefore, you don't have to go through a lot of complex data modeling or formalized data modeling. Just knowing your data is probably the key - or at least it was for me. My data set wasn't as complicated as perhaps others.

I’d rate the solution eight out of ten. It was pretty expensive.

The cost didn't justify keeping it around when you look and compare it to other existing tools in the business. That's why I might give it an eight. However, from a feature and functionality perspective, it's just a really straightforward, elegant tool. I like it.

We use Domo to implement our end clients' KPI dashboards and various metrics.

All our client SLAs and daily and weekly dashboards are tracked on Domo. Since all our SLAs are available on Domo, we use it to predict whether we will meet our SLAs. The solution has the flexibility of using multiple connectors. We write our custom code to integrate with Domo and then generate insights. The solution's integration is very easy and friendly, and anybody can learn it.

If Domo had a Copilot feature, you could interact with the graphs and talk to the graphs and tables.

I have been using Domo for two years.

The solution has good stability.

We previously used a different solution called Tableau. We switched to Domo because it was better than Tableau in customization and ease of deployment.

The solution’s initial setup is very easy.

The solution’s deployment took a few weeks.

The solution is deployed on the cloud in our organization. The solution's visualization feature is good and meets whatever most of our customers want. It has all the standard charts and typical drill-downs, and it's quite easy. I would recommend the solution to other people who are considering using it.

Overall, I rate Domo a nine out of ten.