Domo Reviews

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 is to use it to show all of the analytics for our retail stores and allow the managers to see their store numbers and compare them to the other stores.

And for employee performance, employees can compare themselves to the rest of the country. That was probably my biggest application of it and it's an interesting use case because we manage all of the data in the backend. We are able to get the users to see a very static view of how they are doing compared to the top ten percent of their region, their state, and the top ten in the country. It creates a pretty cool way for employees and store managers to compete, in a healthy way, with the rest of the stores.

The best improvement is the data availability. For an organization that has over 12,000 users, having data on the cloud for anyone, anytime, to see their live stats is really different. We didn't have that before. That completely changed the way we look at how a store performs and how employees perform.

We had limited visibility into the data previously so I can't tell you that we have seen huge improvements from the data standpoint. But the company really started to focus on performance metrics and, over time, we saw people improve their performance from the time that we got Domo and onward for the next two years. When people started to adopt it, we started to see performance increases, especially in the stores that were more focused on it.

The best thing is that the data storage is pretty much free. I can store as much data as I want, from different sources.

The ETL tools they have in Redshift are pretty awesome. They also have them in MySQL, but I find it really easy to gather data from AWS and work with Redshift all the way through the process. I can work in Redshift to get the data from AWS and work in Redshift, in Domo, to create Transforms and the data structure we need for the remainder of the users.

They could use more charts. They have had a very limited number of charts we can use. I believe, now, there are somewhere around 30 of them, but they could definitely use some more options.

I would also like to see improvements to their drag and drop Magic ETL tool. You can drag and drop your ETL tool, but it doesn't really work for a large amount of data. It struggles with that. In a real-world application, where you're working with 30 million rows or 100 million rows, it takes a bit longer to process the data. If you do it in the Redshift ETL tool, using your own code, it's much faster.

The stability is great. We have been down for maybe a few hours, once or twice, over the four years I've worked with them.

Most of the issues we had were on our side, with our data, rather than with them. That's why I was actually surprised to read other reviews that said that they were having trouble with loading the data or updating the data. I think that may be because of the way they implemented it because I've never had any issues with that.

I have worked with such large businesses with Domo that I think it could scale to any size. We have 12,000 users across the country, 600 stores, and hundreds of gigs of data.

The majority of the users are just looking at their numbers. They're not really doing much analysis or creating their own charts. But about 600 to 1,000 of the users are corporate users who make tables or their own charts or create their own metrics. But most of that runs through me, if they needed data changes.

I'm not sure there's much need for us to grow into it. We have adopted it close to 100 percent of the time. All of our company employees are on it.

I have to give tech support a really good score. They've been great with me. If I have a question, I call them and they answer the phone. They are able to walk me through from the most minimal thing. If I need help with something really complex, something I developed which is customized, they still give me a hand. But ultimately, whatever you build is on you.

I have had to escalate a few things, mostly because I wanted to get them done faster or there was a problem I didn't understand. I just go to my sales rep and he gets it taken care of. He gets someone to call me right away.

We had a custom tool. It was proprietary and it wasn't that great. It was mostly scraping the data and pasting into an Excel-style sheet in the website. I wouldn't say it was a business intelligence tool at all. Rather, it just showed you flat numbers for reports.

The CEO brought Domo in. He saw that we were growing and he thought it was an interesting tool. He showed it to us, we sampled it. We used it for a few demos and we decided to go with it because there wasn't anything else that gave you the cloud space without charging you for it. They're really good about that. You can take up as much space as you want for data and they don't charge you for it.

We needed something more versatile than what we had and something that was managed on the cloud that we didn't have to touch too much. They were able to provide that for us.

The initial setup really depends on your native structure and what you have built previously. If you already have a really good understanding of your data setup, and you have flattened your data a bit for it to be absorbed by any other tool, it's going to be really straightforward, really easy. Users are going to be able to take advantage of it really quickly. 

If you have to go through the process of flattening out all the data and getting everything correct, the prep work could take a couple of months. They do provide a lot of help from their side, if you have questions or for getting the data in. They provide a lot of hands-on from their team. That was good.

For our deployment, to get it out to the 12,000 users, it took about three to four months.

We didn't have an implementation strategy at first. About a month into it, we got a new CIO and he implemented a strategy for us to get it done. A lot of it was guided, before that, by our CEO. He wasn't necessarily great in that area; he was more of a finance guy. Domo also helped a lot, getting us onboard and running as soon as possible.

It was hands-on for me. I had to do a lot of collecting of ideas and what they actually needed. I had to do a little bit of the project management myself, as well. I had to do some pulling of strings everywhere to collect everything that they really needed so we could translate it to what the user needed to see. Half the time I was developing, the other half I was chasing down what exactly was needed.

I was the main developer. We used Big Squid Consulting as extra resources, but I guided most of the actual developmental work.

The Big Squid guys are really good. They provided two consultants and I was able to offload a lot of the work, where I needed help. They took care of a lot of code that, otherwise, I wouldn't have been able to put my hands on as fast.

The deployment was done by the three of us. I worked on it 40 hours a week for three months, and we had each of the other two guys for about five to ten hours a week.

We have seen ROI on the retail side. It brought an openness to the associates who are trying to sell at the storefront. It made them compete a bit harder, being able to see what their commissions were on the fly, live. That really returned most of the investment. I would say within six months of having it implemented it returned its full value.

Domo is expensive compared to some of its competitors but it is well worth it, mostly because the competitors either want you to store the data yourself, or they have similar pricing that isn't really worth it when you compare some of the features that Domo gives you.

We looked at Power BI, but there really weren't any others that gave us the deal that we got on the amount of data we could store and the support that we needed at the time. When we made the decision, Domo was fresh into the market, and there weren't really many competitors. Looker wasn't around. QlikView was around, but they came in a little late to try to get our business. We had already made our decision.

Don't complicate it. At first we thought it was going to be a lot more complicated. It just wasn't. Knowing that, next time, would help me a lot, instead of trying to plan so much for every detail. It was a lot easier than I expected and we spent a lot of time testing stuff and figuring out if the tool was updating. If we had trusted what they were saying, we would have finished a lot faster.

If you don't have a lot of data changing, if your structures are not changing - some companies keep changing the way they structure their data and that will take a lot of time - maintenance isn't that bad. I spend about ten hours a week on maintenance of the solution, and we are running a really big implementation. It's mostly answering user questions. There haven't really been any problems. I am able to work on that and on other projects at the same time. I am able to maintain it with very minimal work.

Overall, I'd give it an eight out ten. From easy usability to documentation to pricing, it's pretty much all there.

We use it to work on many business problems using the data visualization. Currently, I'm working for a company which deals with title insurance. We use Domo to visualize the data: How many open orders are created, which agent performed better, which region got the most orders, how many were closed or lost. Our company has data related to mortgages so that's what we use it on. In our division, directors and VPs get insight from the data.

Workbench is deployed on-premises and then we have a web application, a cloud application, for visualization purposes.

Users can log in and directly view the data. Unlike some other visualization tools, they don't need to play around. They don't need to do more steps, like with Tableau or Power BI. Those solutions are a little bit complicated whereas Domo is quite helpful.

There are so many charts available to visualize our data in various ways. There are donut charts, stack charts, bar graphs, and we have geographic displays. We can select things based on the given requirements and on what needs to be displayed. 

In Workbench 5, they have come up with a very useful feature called Upsert. When you're pushing data into the data set, if the data is already available it will update the data, and if that the data is not there it will insert it. That is a beneficial feature that they introduced in the latest version.

It's very user-friendly. When you get into Domo you just search for what they call a card, the one which will serve your purpose. You can click on it and you see the visualization. To see the data, you just click on the card and you can view it. You can also export those reports as well.

Connecting Workbench to your data source is really easy and then you can visualize it or choose among many other options. You can connect through Amazon Redshift, or any AWS-based database, or any cloud-based data sets. You can also upload your data set through Excel and CSV files. It provides a lot of convenience.

They also provide many plugins to collate data. If you want to extract the data from Facebook, Twitter, etc., the plugins are built-in. All you need to do is add the plugins to your Domo Workbench and you can extract the data.

Domo as a solution can be improved in various ways. For example, when you're exporting a graph out of Domo — suppose it is in the form of a donut chart or it is in form of a stack — the data comes out in tabular format, not as a graph. When exporting the data, I would like them to create a tab for graphs and another tab with the data in tabular format.

I have been using Domo for more than two years.

When we started using Domo, it was only one or two years old and it wasn't quite stable. It was still in development/beta mode, but now it's quite stable.

It's quite scalable because they keep on adding new features. It keeps up with the market trends.

We used Tableau prior to using Domo. It was because of the organization and licensing that we switched to Domo.

The initial setup is very straightforward. All you need to do is have Workbench set up in an on-prem server, and you need Domo access, the cloud link. That's it, and you're ready to develop or publish any report. It doesn't take much time. All you need to do is create a data set and, once your data set is available, you create cards. However long it takes you to create a card is how long it takes until you have results.

Domo consultants will be assigned to each of your projects. They are really helpful if you come across any gap. You can directly contact them, have a call with them, and they will help a lot. That's part of their standard tech support.

In our organization, Domo is widely used. The division I work in has one of Domo's staff to support us, dedicatedly our division. Somebody else is assigned to another division.

It's saving use effort and time but I can't talk about how they affect ROI because I'm not familiar with the cost of the solution.

I'm familiar with Tableau. Tableau is more evolved and has many more features than Domo does, but Domo is still evolving. At some point in time it may be in a parallel position.

One of the major differences between them is the UI look and feel. In that area, Tableau is better. In Domo, you upload the data set and then you create the job which will be NRT — near real-time. You keep on scheduling the job; you can schedule it to run every minute. But in Tableau you can have a data set cached in your system or you can have a live data set from the DB. You can directly connect it from the database.

There are more than 500 people using it in our company, although that's just a rough estimate. They are mostly in high-level management: SVPs, VPs, and CFOs. And it doesn't take many people to support and maintain it. It's low-maintenance.

It's a good tool, overall. I would rate it at seven out of 10. There are a few features that Domo doesn't have. If they keep on adding features and work on the UI, that could make it a 10. I would rate Tableau higher.

We used it for data crunching, analytics, and business intelligence to take it to a new level.

We built a culture around Domo. We built the culture around numbers, and sales guys not being able to hide anywhere, because we had the whole office plastered with 60-inch screens. We built a culture in the company around transparency and numbers and being able to crunch any numbers from any direction or any angle. That was the foundation of my startup. I could take any Excel sheet, for example, if I wanted to crunch analytics or numbers, connect it to Domo, and do the number crunching in Domo.

In addition, when we developed software internally, we were able to leave all the business intelligence and reporting out of it, so it actually changed the way we built software. We used Domo for all of that. We had a pretty big database and when we made changes to it we'd just connect the entire database to Domo and do all the analytics there. That was pretty helpful. It cut a lot of costs.

And the tech guys used it for getting alerts on anything from HTTP errors to whatever else you can think of. They would get alerts when somebody was scraping our database or when something was down.

The fact that you can add any data source is valuable. The entire data handling suite they have, all the apps, etc., is pretty amazing.

One of the key things, not being a techie or a data-warehouse guy, is that you can connect data sources and do all kinds of pretty amazing things. Even I used to do it. I was the founder and owner of the company and I was managing the whole staff, etc., yet I still used Domo myself, to a certain extent. It's pretty user-friendly. Of course, when you have massive data sources, it's different. But the way we used it, it was quite straightforward. We had 100 million-plus rows of data in Domo, and we were a small startup.

We struggled to keep up with it but I don't really know if there were any bad things about the product itself. Their organization or client service didn't always keep up. But as software, it's pretty far ahead of anything else. It's like the Rolls Royce of business intelligence.

It's more about you, yourself, having the resources to keep up with their development because it's pretty stellar.

We never had any issues with its stability at all. There were scheduled maintenance breaks. We did have a couple of stops when there was a data table that wouldn't load correctly, but that was something that they usually solved within just a few hours.

We went from a couple of thousand rows of data to 100 million rows of data with no issues at all. But we were not an enterprise. Domo is really an enterprise tool and that's where you get the big bang for the buck.

We began with three people and we grew up to about 100 users, plus some board members and some external investors. We were able to give dashboard access, different rights to different groups of people. We could build a "Board of Directors dashboard," or an "investor dashboard." Everybody used Domo in our organization, either to view, analyze, or for daily use. Some used it more, some used it less.

We used Domo for five years. In the beginning, the first three-and-a-half years or so, technical support was amazing. They would answer six things immediately. But they took on more and more clients and the processes slowed down a little bit. I don't know if they've gotten that fixed, but in the later stages it slowed down a little bit.

I'd say they're still ahead of a lot of other platform providers or software providers. It wasn't like Microsoft where you can never talk to anybody, or Google where you can never reach anybody, ever.

I received a presentation of up-and-coming types of software and in the business intelligence category there was one slide on Domo. I went to their website and I looked at their demo. I said, "Holy smokes, this is what I need." It wasn't like I was looking for a solution. I just found Domo, and realized, "Okay. This can change my business."

Back then, we were a two-person company. I went to my board and said, "I'm going to spend $50,000 on this business intelligence tool," and they looked at me like, "You're crazy. Have you lost your mind?" And I said, "No, no. Trust me. This is going to be good." So we bought it. It wasn't sold to me. 

We were thinking of building our own CRM that would be part of our own applications, a backend to our own systems. But we skipped that when we took on Domo.

The initial setup was pretty straightforward. We bought it as a yearly package and got ten licenses to begin with and then a bunch of U-licenses. The setup was included in that. They set it up according to what we wanted included in the price. They didn't come back to us at any point and say, "You've run out of hours." They did it quite elegantly. We got up and running nicely.

The initial deployment took two to three weeks. That's one of the crazy things about Domo. If I have a huge database or an ERP or a CRM, and it's in an SQL or another database, it's about a two-hour process to connect it to Domo. It's not complicated. If I want to get all my Twitter, Facebook, and analytics into Domo and into dashboards, that's something I can do, and it will take me about 15 minutes. It is "next-level." It is pretty amazing. 

There is an app in Domo - the Workbench - that picks up the information. You connect your LinkedIn or your Facebook to Domo and it just picks up all the relevant data. There's a ready-made dashboard for it and you can modify it if you want. But for most companies, the dashboards that they've already built are good enough to begin with.

It's a super quick process.

In terms of an implementation strategy, we talked with the implementation team about what's important, what's not, etc. We thought about it and discussed it over a couple of Skype calls and then we made it happen.

The deployment speed is one of the biggest advantages that they have.

We did it ourselves, with Domo. We had a couple of tech guys who built our software and they picked up Domo by watching a couple of videos in the Domo University. They did a lot of the integration and a lot of the deployment. They built a lot of dashboards. It's super-simple to get started.

When we started using it, I had one tech guy who helped a little bit. And then Domo did a lot of the deployment, and then we were up and running. We came back to Domo and asked them for a couple of bigger tweaks and they helped. They gave our tech guys some guidance and then we took over and did everything ourselves. So it required very little in terms of our staff. We had no full-time Domo guy. We'd do it on the fly.

Once it was up and running we didn't have anyone maintaining it.

I couldn't put a number on ROI but it has probably paid for itself a few times. The fact that we could leave out stuff from our own applications means we probably already saved the money there a few times over. But it's the effect of Domo on the culture of the company that I can't put a number on.

They keep on coming up with more and more apps; they've built an "app economy." Some of them are really expensive, so they're not for startups and smaller companies. They're more like enterprise tools. We couldn't afford some of them, because they were so crazy expensive. But if I was working for a bank, insurance company, or some bigger corporation then, for sure, they could justify those prices.

Back then, when we bought it, pricing was very mystical. It seemed like it depended on who you were. There were no prices on the website, nothing public. It was probably on a case-by-case basis. It was silly expensive back then and it probably still is, or even more expensive. But, again, I've sold EMC storage solutions where we were four times more expensive than others and we could justify it.

I'm a big believer in: "If you're poor you don't have money to buy poor quality."

I've used different ERPs, CRMs, and different types of analytics throughout my career, but I've never invested in anything like this before. This is "next-level."

If you implement Domo, go full-on with Domo and let go of all the legacy stuff. The big mistake is that you implement Domo and then you have something else as well. If you're thinking of consolidating analytics, go full-on because Domo can solve everything when it comes to data-handling, analytics, business intelligence, and reporting, etc. My advice would be: Have the courage to let go of all the old stuff.

I'm a big fan in many ways. I'm not a techie in that sense, I'm more a CEO. But I'm a big ambassador of Domo. When you compare storage, for example, you have Dell EMC and then you have all the others. In business intelligence, you have Domo and then you have the others. That's how I see it.

If the company I now work for, a new startup, ever grows to the size we need it to be, then I would be an ambassador for Domo again. Or if I was running a company, I would look at implementing Domo pretty quickly to get a really crisp understanding of how the business makes money, and what we can do to make more.

Every organization is different, so you would probably use it differently depending on what you do. My old startup was a very sales-heavy business. It was a lot about sales and customer data and the like. In another organization, you might use different kinds of analytics and business intelligence. How you use it really depends on what you do.

I would give it a ten out of ten. If you've actually lived the "Domo life," it's hard to get along with anything else after that. It is that good.

1. Domo is a single system of engagement in a simple browser.

2. There are tools that can only be used by extreme developers who have an in-depth knowledge of graduate level statistics. Domo handles this in Domo, in the same interface, without having to go through multiple systems or modules.

3. Grouping data together on the fly, not having to do your grouping ahead of time in data prep, and in creating views in SQL.

4. Drag and Drop ETL

5. Multi-Dimensional drilling

6. Lighting fast interface

7. Row Level security, which is easy to use and deploy.

1. The cost savings from redundant reporting and consolidation alone surpass the cost of Domo hands down.

2. Speed to market - able to deploy metrics, reports, complete data sets in hours/days compared to months/years previously.

3. The ability to help identify problems in our data that need to be corrected, whether it be formatting or actual logic.

More functions on the ETL side for the drag and drop ETL.

Four years.

None at all.

None at all. The only time Domo has not performed was when something on our side fails.

None. Completely scalable to any size organization.

A nine out of 10

Always responsive. Sometimes getting the right person from ticket to assignment is a little buggy, but I have had to call support less than six times in four years, so I consider that a win.

10 out of 10

They will always find a way to help the customer accomplish what they need, even if it means creating something that doesn't exist.

We currently use many BI solutions, as I am sure many enterprise-level companies do, but we are consolidating. It just takes time in large organizations.

Straightforward.

In-house. One person deployed the instance with very limited support from Domo at our request. This helped us understand that it was truly that simple.

More than 300%.

Seems out of this world, but it is the truth. This ROI calculation was done year two of using the system as a presentation with my management and it continues to increase.

Talk to your account manager. They will work with you on pricing and they will ensure that you get what you need for any size organization.

Birst, Tableau, Crystal, Power BI, GoodData, and Qlik.

In my 15 years of professional experience in IT and Project Controls, this system is truly the one that is the unicorn. That one system that we all wished existed, it finally does and it is real!

We currently use Domo for automation of our reports. I'm connected with a large company and I focus on talent acquisition and analytics. We are mostly pulling reports from Oracle BI, reports that are used by our talent acquisition staff. We connect our Domo database to OBI and pull the reports from there. The visualization and the rest of the analytics functions are stored in Domo.

Domo is a great help to our organization because, prior to Domo, we were using an Excel base. We were highly dependent on Excel, including manual entries and encoding of data. We were quite heavy on that. But as we shifted to Domo, most of our reports were automated and displayed real-time for our end users. It's a really great help with our business, here in the Philippines.

It saves a lot of time. Without Domo, we would need more manpower to support our reports. Before Domo, we had a report-focus which required a headcount of two and there are only two of us on this team. Eventually, most of our work time was diverted into the reports: extraction, preparation, and consolidation of all the data coming from individual Excel files. It saves a lot of time as well as cost because we don't need to hire more people to work on the reports.

What really helps us a lot with Domo is that we are able to focus on our core functions. We are heavily dependent on data collection, data gathering, and finalizing data. The clerical functions are being isolated or reduced, as we shift to Domo.

I don't have dollar numbers, but in terms of hours, we have certain reports that were being generated after four to five hours of work a day. But in Domo, we need just 30 minutes to create that report. That report is being published every day, so it really helps us a lot.

What makes me really fond of Domo is the ETL because it enables us to maximize a single platform for pulling reports and automating things. We can send the raw data from a third-party platform and do the rest of the ETL in Domo, including transforming data, adding columns, etc.

There is also a built-in viz mode which is really helpful for us. We can do computations there and, eventually, see the computation results in real-time.

We have been exploring the key functions which, for us, right now, include dashboard creation and using the Magic ETL. We are focused on them because we do a lot of stuff related to ETL. We are also doing some blending, data transformations from different data sources. It's quite helpful because we don't need to do it outside the Domo platform. Before that, prior to discovering the blend function, we used to do it in Excel first and then upload it to Domo. Since discovering that function, we just pull the raw data coming from a system and Domo does the rest of what needs to be done.

In terms of the dashboard that they have created, they can do better. If you are quite new to Domo, and you're not familiar with how to play with the buttons, the options, you might get lost.

They can further help the user by providing better customization and options. For example, for customizations, instead of displaying a dropdown, why not just have a button for selecting which filters to show? That would really help users to explore faster and understand the data better.

I'm also using Domo in mobile and it's quite impressive. However, there are no options to edit using your mobile. That's a limitation. In the future, they should consider adding the edit function in mobile.

In terms of the analytics, there is quite a limited set of options when using Domo. Whereas with Tableau we can perform heavy statistical computations, Domo doesn't have that capability. Domo is quite limited on that side. They may need to consider improving on that in the future.

But overall, what I'm seeing in the system right now is good. It really helps a lot in streamlining our processes and enables us to focus on our core function.

Domo is good, as long as you have a good internet connection. That's one of the challenges here in the Philippines, which is one of the countries with a slow internet connection. When I was working in another company with a good internet connection and bandwidth, we were able to access Domo very easily.

I would rate the scalability at 7.5 out of ten. What differentiates other business intelligence software from Domo is that with other business intelligence software you can find tutorials on YouTube. For example, you can find several tutorials for Tableau on YouTube, but for Domo, I don't believe you can find any. It's difficult to find a training module for Domo, unless you are in the Domo University.

I haven't tried contacting Domo's technical support since I joined this organization.

We were using Excel prior to Domo.

All the organization's data is really important. With data you can measure how you are performing. The challenges in using Excel were, number one, integrity. Maintaining extra spreadsheets over time is really hard. Gathering and updating the data is really hard. Second, of course, is that there is a lot of manual work in Excel, unless you have someone trained to do queries or Visual Basic macros. That can help speed up the reports, but it may take time, again, to develop queries and programming for Excel. The driver for our switch to Domo was to speed things up and be able to deliver reports on time, accurately, and more reliably when compared with Excel.

It's relatively complex to implement. 

One type of ROI is that have been able to reduce the number of staff needed to prepare certain reports. Before using Domo, I would estimate that the company needed at least four people on the team to handle just the reports for our talent acquisition team. Now, we need closer to two staff. And that's just one team.

I'm not sure about pricing, but I believe Domo is quite costly. Prior to joining this organization, I had a Domo license with my former employer and I think that license was around $500 to $600 annually. That was for a single license. I think it varies, depending on the organization that is acquiring Domo.

Domo is a great tool, in my opinion. But the first thing that you need to consider is what kind of return on investment Domo can deliver. There are a lot of things that Domo can deliver. There are a lot of things that I haven't tried yet with Domo and I'm quite excited about trying them. But in terms of the ROI, there's a really great opportunity to save cost and time with Domo, particularly for if you are heavy on reports. If your organization needs certain data or reports in real-time, reports that help you to decide on certain issues, Domo can be helpful.

For the setup, the first thing that really matters to me is the importance of the fundamentals and training for users. If a user has not been well-trained to provide technical explanations to other users who eventually join the organization, it's quite difficult to understand Domo.

When I joined this organization, they had already been using for Domo but for less than a year. In terms of the reports, they are not utilizing it fully because they don't have any dedicated person to handle it. In addition, they don't have any trained personnel here, so there's no one to set up the reports, there's no one to explore the functionality of the system. It's quite a challenging role. We have been working on overcoming those issues.

As for increased usage in the future, we have a mandate from management that we're eventually shifting everything, all the reports, into this platform, because of its usefulness. It's quite good and I think the organization supports it.

It is being used globally in our organization. We have counterparts in other regions including India, Bulgaria, and the US. Our team alone has more than ten people who handle the business analytics. We are the ones preparing our records and data in Domo for all talent acquisitions for this organization.

I would rate Domo at eight out of ten. It's really quite helpful for me to use Domo. Domo helps a lot in terms of reports and streamlining the reporting process. It helps the organization to make decisions quickly.

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.