Domo Reviews

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.

Domo is a cloud intelligence software, so it's used in data analytics or analysis. It's a one-stop shop BI tool that handles the entire business intelligence process. Multiple components are involved when giving end-to-end BI solutions, for example, integration, ETL, data warehousing, data analytics, data visualization, data science, and machine learning, which Domo is capable of handling end-to-end. It's a tool that can do everything, and you can pull data from anywhere, from visualizations using advanced AIML concepts through it.

The best feature of Domo is that it's completely on the cloud. I also like that you can handle data end-to-end without having to depend on multiple tools. Another specific feature I like the most about Domo is Magic ETL because, through it, you can do all your expression, transformation, and loading activities very smoothly. The tool also follows the lineage concept, so you can understand what kind of transformations took place on a particular data set. You can find end-to-end data from the source until it has become the final output or the final data set. Whatever happened to a particular data set, you can understand it through the Domo lineage, and that isn't possible in most of the tools available in the market, but in Domo, that's available.

The tool is also solid and because it's on the cloud, it uses multiple data engineering in the backend and multiple algorithms in the back, behind the scenes, resulting in a great performance. For example, if an end user such as the CEO or COO opens a report or the dashboard and it takes more than ten seconds, the end user won't be interested in looking at that report or dashboard, but Domo enables better performance and there's usually no performance issues from that tool.

Domo or any other BI tool has room for improvement, in particular, in the calculations. User-guided material isn't available for calculations. The tool, though user-friendly, could also be more customizable, especially when you're building a dashboard. Data integration could also be improved in Domo because even if the tool connects to multiple data sources, some hiccups still arise and need to be addressed.

Additional features I'd like to see in the next release of Domo include automatic data loading and understanding through machine loading algorithms and ready-made dashboards that end users would find easy to understand. For example, if I'm going to customize the dashboard and start using it, the tool should understand my data immediately through machine learning algorithms and data science models which would be a great addition to Domo.

I've been using Domo for almost two years now.

Domo is a stable tool. I never had any bug issue or breakdown from it. The tool runs smoothly because it always has a backup engine running, so if something goes down, the backup engine immediately kickstarts. Domo runs flawlessly and doesn't have any problem, delay, or outage because of the backup engine.

In terms of scalability, we can add more users to Domo remotely. If today we have fifty users and tomorrow we want a total of five hundred users, we can just set up a call with the Domo team and they'd support us. Scaling up Domo won't be a problem.

As we are implementation partners with Domo, we closely work with their support team, particularly when building custom visualizations. We also support the Domo team in terms of building their solutions. For example, if customers have specific requirements, we get in touch with the Domo team and build the solutions. They're supportive, and in fact, we're planning for an event in the coming days. My company, GWC, in collaboration with Domo, we're going to have a conference in India, so very often we get into discussions with them in terms of Domo improvement areas, and whenever we need some support, we can contact their support team. 

On a scale of one to five, with one being bad and five being excellent, Domo technical support would be four out of five.

The initial setup for Domo is very simple because it's a serverless approach where you don't have to maintain a server. You don't have to have the hardware. You don't need a support team or admin team for its setup. It's just a subscription model. When you want to buy this tool, you can directly contact Domo. I run an analytics company, so I'm a partner of Domo, and it's very easy to implement the tool in the initial stage. Setting the tool up is a very simple process.

The implementation of Domo is done in-house.

Domo has more than one licensing model. You can choose between the yearly subscription and the per-user licensing model. The tool is flexible in terms of licensing. As for the cost, Domo is an end-to-end BI tool so its pricing is a little higher than other players in the market, for example, non end-to-end BI tools such as OBIEE and Tableau specific only for business intelligence and presenting data to the end users, unlike Domo which handles everything. You want to get Domo as an integration tool, an ETL tool, etc. As the tool is end-to-end, its cost is always going to be a little higher than other BI tools, but it's worth paying because you won't have to spend extra for other activities. After all, Domo can do those activities.

Domo doesn't have a version because it's completely on the cloud, even if there's a change in the backend. It doesn't have any software that you need to install as Domo itself is a cloud tool.

My company is a Domo implementer with eight to ten projects executed, and with every project, there's a minimum of twenty-five to thirty end users of Domo, but the company has forty certified Domo developers. Every developer supports, on average, ten different users, so overall, the tool has three hundred to four hundred users.

The main reason my company decided to use Domo is that it's a one-stop shop BI tool, so it solves requirements for all customers. It can also integrate with any data source, and it's the only tool so far that can integrate with more than one thousand five hundred different data characters.

Another reason why my company chose Domo is because of the look and feel of the dashboard which is easy for the end-users to understand. Domo made it very simple. The tool is what people need as it has more algorithms and gives effective results.

My advice to anyone planning to use Domo for the first time is to just get on a call with the Domo team and explain your requirement in detail. The Domo team will give you a demo, and after understanding the demo, you have to explain any problems and your requirements, so the Domo team will understand, and depending on your requirements and data sources, the team will suggest the particular approach you can take. This is what you have to keep in mind before you approach the Domo team for implementation.

My rating for Domo is eight out of ten because it's a cloud-based tool that's good for data security and it's user-friendly. Any other BI tool expert can easily learn the tool and start working on it. Domo has a drag-and-drop approach, so you don't have to be technically skilled to learn it.

My company is a partner of Domo.

The solution was an aggregation of accounting information across the entire organization. Most of the controllers and accountants were using Excel or Access on their desktops in order to create the reports that they were generating. First of all, we parsed and imported all of the Oracle ERP and the other, JD Edwards ERP information into one, into Domo. And then we even imported some of the access database information from the other accountants into Domo and we generated the dashboard and KPI reports out of Domo.

The dashboarding itself was pretty easy. So both the front and the back end were positive in this case. Domo focuses very heavily on being able to get data out of the Microsoft domain which is helpful as it was automated.

I would like to see improved data intake. You have to work into being the tool that helps you do a really good job of data ingestion. So having a good data lineage, having the semantic layer and ontological model development in there, making the ingestion part of the tool really, really robust. Because in the end, data science is almost always held up by poor data tagging and unclean data. So the ability to really do good data ingestion is important.

I have been working with Domo for the past five years.

I think that it is a fairly elastic and extensible application that I would scale to as big as you needed it to be based on how much computing you put behind it. I do not think it has a problem there.

Technical support was very good, especially during deployment.

It was fast. I would say it only took four weeks. And two of the weeks were because of the customer, not because of the Domo implementation. So if you really had your act together and you were doing just what I was doing, which is linking data sets and generating standard monthly financial reports, which were already part of a template in there, it goes real quick. I imagine if you were not using templated reports it would not go as fast.

I think the ROI was a month and a half. It was really fast. Not only did I get seven people in the day-to-day aggregation of financial data, but they went from quarterly reports to real-time data. So that is something we could not measure.

I think it is reasonable. I will say that all of the competitors right now I think are a little pricey, but I am cheap.

Pay very close attention to your data catalog development. Do your best to drive towards a common data catalog across the entire enterprise. So you do not have data that is tagged similarly from different data sets. I would rate Domo a seven out of ten.

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.

Domo is a data platform that helps us collect different kinds of data. It also allows us to put all the data together, assess it and use it to help work through business processes or workflows.

The dashboard is the most valuable feature and allows for customization to create and share reports. It is also a collaborative tool.

There's some complexity with the charts in the solution, and there's a learning curve before you can get used to the solution. The solution currently has many great features, but enhancements to the visualizations or cards would be great.

We have been using Domo for a couple of years. It is deployed on the cloud.

We have not experienced any issues from a stability perspective. There have been no crashes or downtime, or any loss of information.

This solution is designed for scalability and depends on how much data you want to collect.

I don't know the exact number of users using this solution, but it is probably at least 100. In terms of the roles of users, it ranges from engineers to developers and managers. In terms of maintenance, there is a primary contact, and another person acts as a backup if the primary contact isn't available.

We've used technical support once and have not experienced issues with Domo. We've only leveraged general support.

We used a solution called Qlik in the past, and I believe the pricing was the deciding factor in switching to Domo.

The initial setup was straightforward.

I can't speak specifically to pricing, but we do not plan to increase our number of licenses. We are satisfied with what we currently have working for us.

I rate this solution an eight out of ten. Regarding advice, I would recommend going with the cloud version and something seamless. Also, leverage the dashboard, and explore it. There might be an initial learning curve, so ensure you have enough buffer time to learn.

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.

Our primary use case for the solution is creating operational reporting to help us make decisions that go live executive dashboard. We deploy the solution on cloud.

We find the ease of using the solution valuable.

The price of the solution can be improved.

We have been using the solution for three years.

The solution is stable.

The solution is scalable, and 40 users are currently utilizing the solution in our organization.

The customer service and support team is responsive. They answer our questions once we submit tickets. I rate them an eight out of ten.

Positive

I was not involved in the initial setup.

The solution has a standard license with some embedding. It is expensive so I rate it as three out of ten.

I rate the solution a seven out of ten. The solution is good, but the price can be improved.