Domo Reviews

Our business deals with B-to-B and B-to-C customers. Our main objective is to present an analysis of our business. From our databases we generate a report and we showcase it to our upper management team, showing them the exact analysis that has been done.

Earlier, in terms of analytics and data, it was slow going. We used to manually create the reports. We didn't have any interface or way of presenting any data to the CEO or CIO of our organization. We used to pull out reports by creating them in Excel. Domo has helped us directly present data to the upper management team. We have created particular dashboards on Domo and given direct access to upper management so that they can have a look and strategize for the future. We created the dashboard once to meet the requirements. Now, automatically, as the values of the data change, the job is done. They are able to understand the current status of the business.

On a daily basis, it is saving us four hours per day. We used to spend four hours extracting the data for a report. 

We've worked with all the features of Domo. Among the most important are Pivot and Sumo Cards. We can use drill-down from the top-most level with a click, generating charts.

Apart from that, we are able to connect with MySQL; directly with the database of the internal CRM to fetch data and create reports and present it.

The user interface is quite good. 

It's quite slow. We have about 2,000,000 rows of data. Creating certain reports takes almost a couple of minutes, which should not be the case.

One of the things Domo can work on is the filters it provides. I have created many dashboards and the filters are not that user-friendly. If we have two dates, we are not able to filter it on both, it allows only one date, which is not a nice thing. If they could improve on that, it would be great.

Finally, I would like to publish a dashboard for the employees so that they can also see the performance of our organization. But that is not a feature in Domo, although it's something that Zoho provided. I would request that Domo enable us to share a particular dashboard with the employees, providing the filters with that. Domo doesn't provide anything like that. This is one of the features we want. We are not able to share our data with the employees. We don't want to share all the data. Our objective is to enable an individual to look after his performance in the organization. We are not able to do that. That's why we are stuck with only a few people using it in the upper management team of our organization.

We haven't had any downtime or crashes, it's running absolutely fine. 

The performance should be improved in terms of data fetching from the external application. When you connect it with the database it takes some time to extract the data.

We haven't had to contact technical support. We did communicate with the salespeople. They replied whenever they received our messages.

We were using Zoho. My boss said to me, "We need something that we can use to present our data." We started looking for a tool that would help us. We came up with Domo and directly started the implementation.

The setup was straightforward, easy. You have to directly connect it with the database. We have a database for our internal application and integrated directly with that database and it was good to go. That process took one to two hours.

We started by creating one report, then another report. The initial R&D I did on Domo took me between ten and 15 days, and then I moved on to creation of the reports. After that, I was able to create the dashboards in a month.

I was the only one who developed the entire dashboard in our organization. I am the entire owner of Domo.

We did not use a consultant.

Over the last year we have saved about half of the amount of the subscription. It has reduced our costs more than we expected. It has saved us manpower, money, and made things more efficient. It doesn't require ten people working on it, one person can develop and that's why I am here, to run this entire project.

Pricing was a huge factor. Domo is slightly costly but it's much cheaper than some. If possible, when we renew our subscription we will be requesting a price cut. We can get the same features from competitors. We may have to look for a new subscription.

Zoho has created very advanced analytics but Domo is far better than Zoho. We looked at Cluvio and Grow. We went with Domo because it is easy to use and easy to understand.

It's easy to use. There's no need for Google or videos to learn something. You can just explore it and do whatever you want and it's very easy to understand with a good interface.

We have kept the number of users to not more than 15. We have kept it confidential and not made it available to the employees. 

We are planning to increase usage of Domo. We had a lot of negotiations with the team that was helpful regarding the sharing of a particular dashboard with other people. We have a one-user subscription and we want to share this with another one so that they can at least have a look at the performance in the organization. We are planning to share Domo with the employees. We have between 300 and 500 employees. Our target is that by the next financial year we will deploy this product throughout the organization.

I use Domo mostly for three reasons: 

1. To create connections with several applications and obtain data from those applications, e.g., Google Drive, Google Sheets, or Google Analytics. 
2. With those connections, I love to upload data to Domo and transform that data in different ways. I create ETLs to join the data. 
3. When I join the data, it is transformed into a card where the client can see his data in a graphical way. From this, he can understand how his company is performing, because the data which I upload is from their call center(s). 

Domo is not for fixing errors. We don't fix anything with the database. Domo is for processing data and showing the data to clients. They can see how their company is with calls, and if they are selling well or not. 

For our clients, who have call centers, it is very important. For example, they need real-time data and Domo allows them to obtain data every 15 minutes. It updates the data every 15 minutes with new issues to fix it for the moment and will detect if something is wrong, which is for the client, as they need to ensure their data is okay and everything is working. The client needs to know if their reps are working well and selling their products.

Domo has a lot of connections using APIs where you can use data from different databases, such as NoSQLs, SQL databases, and other connections. These connections exist to obtain data and transform whatever that you want. This is valuable because I work with Postgres.

You can also create two types of ETL: 

1. A graphical ETL.
2. It can be used cold with MySQL and transformed into whatever you want with the code.

It is pretty amazing; the things that you can do with this product.

If your ETL runs more than 24 hours, it always fails because we are logging a lot of historical data, and there is a restriction on the amount of data (in rows) that you can run. The technical support has not found a solution for this yet. Their recommendation is just to run less data, which does not work for us.

I would like the real-time reporting to decrease the range of output from every 15 minutes to every five minutes.

They could add create a card in a timeline to see how calls are going. Domo has a lot of features, but it does not have a timeline.

The stability is pretty good. We have not had a problem with losing data.

There is an issue with Domo's storage because there is a limit with it. In five years, the storage requirements for Domo will not work for companies.

We currently have 50 people using the solution, though we have only about ten full access accounts. The rest of the accounts are preview only versions.

If you have an issue with Domo, their response is less than an hour. Their support contacts you immediately when you send an email for an issue on a database or data set. Then, they follow their process and will always try to solve the problem in less than 48 hours.

We previously had a homegrown application that we used. We switched applications because of iOS limitations. 

Domo was already installed and configured when I started.

It's pretty simple to configure within a database and with another IP, like Google. It provides a step-by-step explanation of how to do something using stickers in the questions. Clicking on the sticker, it tells you more information about what you need to to do to configure something, which is pretty simple. It takes a minute to a minute and a half to set up.

We implemented in-house. 

It takes one person to create the configuration and the data sets to upload the data, then three or four more to create the cards. The cards will be where you will need more time to transform the information, because you need to know what clients need to create the card like the client wants or what they want to see in the card. Therefore, it needs around five to ten people working on the deployment, then maintaining the solution.

When implementing, you need to know what the client really needs and what do you want to create in Domo. 

We are making money from Domo, and all our clients are happy with the information that they receive from it. We have seen our customer base grow due to the product's usage.

Right now, we are trying to use Pentaho.

Domo has a lot of tools that other software, like Amazon, doesn't have.

Domo is a good tool, and you won't regret it if you chose it for your company, since it is a very useful tool if you want to check your data constantly and historically. You can compare and create graphics to compare the past with the present and estimate to see how your company is performing. 

Right now, the data is the most important thing in the world. Domo always tries to keep your data protected and available to you and your clients. This is something which  good with Domo. 

As our company increases in size, our usage of Domo will increase.

We use Datadog in conjunction with Domo, but they are two separate tools: Datadog is used for checking issues in the databases and Domo is used for uploading data from the databases. E.g., Datadog will inform you what is going on every second in the databases. It provides information if something is wrong or if one of the processes hasn't finished.

• User adoption (ease of use)
• Fast prototyping of data sets and analytics
• Collaboration (both inside and outside our organization)
• Pre-built connectors
• Access from mobile devices
• Data Awareness for enterprise
• Data democratization
• A jump start on Data Governance.

It's a night and day change. We've gone from an organization that had no awareness into its data quality, and where data requests would take weeks to months, to one where our culture has transformed to being data first. Communication, trust, awareness have all improved exponentially. Domo has broken down walls, freed people to ask questions, and brought accountability to all levels of the organization.

This isn't your typical BI tool. It flips some of those standard concepts we have around reporting tools on their heads. There are areas to improve on like visualization options, and there are areas I think would be valuable for Domo to explore, such as data governance, and providing sandbox or development instances, but updates are frequent and smooth, and the value of the tool in its simplicity and ability to drive user adoption far outweighs any missing visualization features.

16 months.

Hands down the smoothest, fastest deployment that I've ever seen. We barely used the implementation team at all, and we were up and running weeks before the PoC was even half over.

No. Uptime has been consistent.

We are moving fast, and updating how we use the tool all the time. Exploring new ways to make the information consumable to a host of customers both inside and outside our company. So far, so good.

Excellent customer service from the beginning.

Better than any other company I've worked with. Having direct access through buzz (collaboration tool) has been super convenient.

I've worked with many of the BI tools out there, and while I'd say every organization has specific needs, I've never seen user adoption happen so quickly. It's been amazing. Domo was the right fit for what was needed at my current organization. The next company may need something else for different reasons, but Domo has been so successful that I would recommend giving it a look.

We also still use SSRS.

Setup was very straightforward.

• Plug-in credentials for pre-built connectors
• Load data files
• Setup ODBC connections to existing databases.

All just take minutes and you won't have a dependency on IT (unless you want to).

Implemented through the vendor team at Big Squid. They were very experienced, a good team.

Our ROI was having an organization that we could trust and be aware of its data, and also make timely and educated business decisions. Not sure you can put a price on that, but it easily covers the investment.

It's comparable to the other tools out there. Domo will work with you.

We did. I have the most history with Business Objects, but evaluated about 30 different tools before landing on Domo and Birst. In the end, Domo was the better fit for the organization.

Domo was the right choice for where our organization is, and I'm confident that it will scale with us.

Every organization has multiple teams that work in different ways. The larger your organization, the more variation you're going to have. The important thing to remember is that the data is what's important. It shouldn't matter if marketing and finance want to use Domo, while your IT department is using SSRS, and Sales is using Salesforce or your actuarial department is using SAS and Tableau. As long as they're all hitting the same data, let them use the tool that fits them best.

This is not a popular notion with IT departments or organizations that already feel entrenched with existing tools and the expensive skill sets that you hire to support them, but those departments aren't typically profit centers either. Bring data to the users, make it easy to see, and easy to talk about. Domo excels where it matters.

In general, of all the reporting tools I've used in the past, I have never been able to rapidly report and build dashboards faster than I have with this tool. Specifically though, the features I value most are the massive amount of data connectors, as well as their third party tool. The tool enables us to schedule queries from SQL, CSV, and Excel to temporarily push a report out until it can be automated.

Domo has given us a far better insight into the company's performance. It has changed the pace at which managers and execs expect reports to be delivered.

The UI has issues with some browsers and small glitches that hinder performance or functionality.

I am coming up to my second year of using Domo.

Since this was purely SaaS, there was no issue with deployment.

For the most part, I have seen a 99% uptime.

Since this is cloud based, there have been no issues at all with more users running the same report.

With any start-up, having issues keeping up with the growth of customer needs, like support, is to be expected.

Knowledgable about the product and its functionality is adequate. Having no direct access to second tier engineering support is frustrating at times and the relaying of issues takes time.

We previously used Business Object 4. It had a lot of issues with bringing in data, very limited out of the box charts and graphs. It was, also, not scalable or available on mobile.

SaaS platforms remove any initial setup problems and it is ready to go out of the box.

We implemented it in-house.

I can' disclose figures, but what I can say is that this has been the best bang for the buck I have seen since I started working at Sage.

• Dundas Dashboard
• Telerik
• SSRS
• Tableau

If you need easy to use, rapid deploying dashboards available from any device or machine, Domo is the way to go.

One of our internal customers is a capital finance team. Before we reached out to them, they were pretty much handling all their data in Excel sheets. Their data has been expanding rapidly and they needed reporting in a visualization solution. They have different forecast methodologies and cycles, and different metrics within those forecasts types. They have various types of capital metrics. If you are from a finance background, you might have heard of what an IOI or an NPV or an IRR is. They had been doing it in Excel.

Ideally, to fulfill their needs, you would need two different solutions. One is a transformation solution. When you are handling huge amounts of data, you certainly need a database and, most commonly, what you prefer is SQL. Once your transmission is complete, you would also need a visualization solution. There are many available in the market.

With Domo, we can do everything in one place. We don't need a separate database. We can do ETL and the visualization in one location.

It's not on a device. It is completely cloud-based. Since we are a healthcare provider, we chose the secure instance of the public cloud: a PSI-certified instance.

Instead of having two different products, one for data transformation and one for visualization, we are able to do those functions using this tool, with one person or two persons at the max.

The day before yesterday, one of the teams wanted to see how its employees were performing in their line of business. That team has around 140 employees, and wanted to see what their current roles are, what their future roles will be, what their primary skills are, and what their secondary skills are. All this time, they've been using Excel sheets and they take a week's time to process. We put in a one-time effort of one week and, going forward, that particular team doesn't have to spend an entire week to provide an analysis to its leadership. All they have to do, once their data is updated, is push it into Domo and all the metrics that they want to see are readily available. It hardly takes five minutes, instead of one week. For that team it is definitely a great thing because the product manager doesn't have to sit for a week and do that. It has definitely made his life easier.

The same thing applies to the finance team. Our finance team gets its data on the 10th or 11th of every month and when they had to process that data in Excel sheets for another 10 days, the month was almost over. Here, again, things now happen in a couple of hours, and their data is ready the very next day and they are ready to present their finance metrics to their leadership before the 15th of the month. Based on that, they can plan their next month, or the upcoming forecast for financial metrics, more efficiently. Now they have 20 days instead of 10 days.

The most valuable feature is the ETL. With ETL transformations in SQL lists, you often write a lot of queries. You have to build a bunch of code for the data. With Domo, one of the pieces we have is Magic ETL. In Magic ETL, you don't need to write code. You don't need to be a specialist in SQL or any database query language. You just need to have common sense or to know how to use Excel and you can do a better job than a querying professional or a coding professional. Magic ETL is one of the best features I have ever seen in the ETL world.

Also, you can limit the users. Finance data is very critical so not everyone can be seeing it. We can create customized security options and provide privileged options to groups or a particular person, so only they can view things.

In Tableau, you can create virtually any kind of visualization. Based on your creativity, you can create a visualization on a human body structure, you can create a visualization on anything that you want. But Domo is limited to a few kinds of visualization views: standard things like bar, pie, and some other charts. You can't create something outside of the box. I would like to see them add new views for presenting the data in the visualization space. That definitely needs improvement. We have provided this input to the product owners at Domo, so let's see what comes out of that.

I have been using Domo for the last two years.

The solution is very efficient and very good. So far, we haven't seen any outages. It's very fast and very interactive. No matter if we're dealing with millions and billions of rows of data, we never experience any lag, which is something we used to see in Tableau, Power BI, and other solutions. With Domo, never. It's as fast as you can imagine.

It is scalable. Our company is a classic example of that. Our company deals with healthcare data for the entire United States, part of Canada, and some parts of South America, and additional international locations. So our data is huge. Really huge. I don't think any other organization deals with this much data. And Domo scales as much as you want.

We have around between 1,500 and 2,000 customers using this, and their roles range from CIOs to vice presidents, directors, analysts, and financial analysts. Currently, in our company, it is not being used as actively as Tableau, but we are expanding usage. When this product was introduced in our organization, we had a customer base of around 20 or 30 people; two or three different teams. We are further expanding it to the entire organization. Our target for this year is to have around 6,000 to 7,000 folks onboard.

A few of our internal customers are using Tableau, a few are using QlikView, a few are using Power BI, and a few are using Domo. We have varied usage but we are trying to expand Domo to be used in place of the other tools.

I was never part of the initial setup, but I think it's straightforward. As with anything that you're getting from the cloud, you only have to establish your data connections to the tool. We use several things, including Excel files. It should be a straightforward exercise, instead of taking time.

I have read about how it is done in other companies and what I've seen is that implementation took less than two days.

There is no specific maintenance for the solution. Two people can do the job for a large organization, because the only thing that you need to determine is how you want to give access and what kind of access. That is done by our customer success manager, and there is a product manager who takes care of who should be given a Domo license and who should not be, in our company.

We have seen ROI with Domo. For example, our finance team invested in Domo and they have saved around 20 days per month. They are now working more efficiently and their numbers have drastically changed compared to their previous year's performance. They can see how they're trending for the last month and they're efficiently planning their expenditures and forecasting accordingly.

Similarly, for our technology teams, we are doing different SLA metrics for incidents, problems, their availability, storage, etc. At one go they are now able to see the problem areas that are not performing and they can plan their technology maintenance accordingly. For some of the organizations within our company, their availability was around 91 percent. Against the standard of 99.9 percent available, they were losing 8 percent per month, which was going to cost us a lot in terms of penalties. They have identified their problem areas now and they are avoiding paying penalties. 

Each of our internal customers has its own ROI like that.

No matter if you're a developer or an end-user, the licensing cost is around $12 per user per month. I'm not aware of other costs but there would likely be some type of cost for the storage that we use, because we're using Domo's cloud storage.

Before choosing Domo we evaluated other options, including Tableau and QlikView. But the problem with Tableau was that it was very slow. It was extremely slow because of the amount of data that we are trying to push in. It was not efficient and stable.

And the problem is with Tableau and QlikView is that you would need a separate ETL tool altogether, like SQL. With Domo we don't need that. We can directly talk to any kind of data source that is available in the market. That is what separates it from the others.

The biggest lesson I have learned is that this makes the job very easy. To do some things in Tableau would take three days, but in Domo I do them in one day. It has made me a lazy person. But I'm now able to focus on other important things. I'm now learning other technologies whenever I have time. Domo has taught me that you shouldn't limit yourself to one area of expertise. You should always expand to new areas.

I would definitely suggest you consider Domo if you don't have any cost constraints. The way I see it, implementing Tableau is more expensive than using Domo. A Tableau user license, per annum, costs around $1,000, I think, in India. And then you need to have a Tableau server to publish the dashboards that you have developed. There is a lot of cost involved in that. This is a major selling point for Domo.

Also, with other dashboards, when you develop a new dashboard you have to develop a mobile version again, or you have to make some enhancements to a mobile version. But with Domo, you don't have to do that. What I've done on dashboards for the web works as well on the mobile application version. These are the things we pitch when we have an initial meeting with a potential new internal customer.

There aren't any version names, as such, for the product that we use here. All the updates and features get upgraded. Before any new feature is going to be released into the production version, we get to review the beta version of it. Based on the feedback from the customer, we decide whether we want to have that featured in our instance or not. So it's not like we have a version one, two, or three, rather that the features get updated as and when required.

I've used it as a platform to bring data together and pull insights out of it. I tried to connect different sources and match them. I'd utilize Google Analytics with data from Salesforce Marketing Cloud to be able to see how email activity in campaigns was impacting user activity on the sites.

It gave us an opportunity to get a closer look at how our campaigns were performing outside of just the email itself and the landing page, to get an insight into how people were interacting with our sites. We were able to look at how successful campaigns were in converting leads. 

We did a few studies where we looked into customers' data, connecting it from all different points, whether it was phone calls or the like. We were able to match it up with what it was that was causing that customer's activity to rise or drop.

It has a really easy platform to create user-friendly data models. It allowed us to click into the data, which was nice. Even though we could step back and see the bigger picture, we could also get into the details. At one point we were merging zip code to zip code data, so we could actually go all the way down to the zip code level and see how well a campaign was performing in a given area.

It definitely gave us the opportunity to figure out where there's room for us to grow or where there was room for our clients to grow. Getting down into that zip code level, we could do a comparison between different markets and say there were a lot of customers in a given demographic whom we could target.

It also let us know which of our campaigns was more successful compared to others.

The ability to create custom connectors was useful because you never know, with customers, what platform they want to utilize or what data they have. It gave us a lot of flexibility in being able to bring data in from different places.

Workbench works well and it uses local files. I had to set up Workbench integrations and it made things so much easier. There was never a point that it was down - and it would be really easy to spot the problem, generally user issues, if there was anything wrong. It was especially helpful during migration when we were trying to get everything into Domo. It can handle a lot.

They do have a feedback feature which is really nice, but it can take a long time to get any responses on that.

It is very difficult too, if we do have specific requests or errors that we can't get figure out - especially when it comes to the development platform, developing custom connectors or doing any kind of API work, custom cards - in that there's a lag in the response time. They do eventually respond, instead of issues getting lost, and they do make those improvements. If they are small improvements they do it rather quickly. If they need a developer then it's slow.

Sometimes it takes data a long time to run, especially when you're connecting data and running SQL queries. Sometimes an error is not caught right off the bat and you have to wait a couple of hours for it to run and then you can catch the error. That part could do with some improvement.

There is coding that you can manipulate data with on the actual card in Beast Mode and that part can get a little messy. It's not something where, if five people are working on one dashboard, each person can go in and edit and make alterations. It's not very collaborative, but it does work and it does wonders when you need to work with very specific data.

It's pretty stable. There hasn't been any downtime that we've ever experienced, any issues that required us to reset or that made us lose data. 

Scalability is pretty good. I didn't have any issues with it. I was able to do a wide range of things. There's a lot of room for growth and the ability to grow on the platform.

Technical support was great. You gave them a call, they put in a ticket. 

If it was something that required a little bit more technical work then it was a lot slower. And their updates could be a little lacking. There's definitely room to grow in their responsiveness. But other than that, with small editing, small issues that didn't require too much technical work on the backend, they were very good and very responsive.

My previous company was looking to grow in business intelligence and Domo was the best option among all of them. But I wasn't there when they made those decisions.

ROI can definitely come from the predictive analysis aspect. You can take any sort of data from any platform and put it into Domo and automate it so you're not wasting time. If you have a monthly analysis or monthly reports, you can automate all of that with this platform, making those processes a lot faster and much more efficient. It also leaves little room for user error that could normally happen in Excel or the like.

It is also good if you're using it internally, especially if you work with billing, to help navigate your resources or to figure out where you can best utilize your employees, etc.

It is on the pricier end.

One thing from my experience that we could have improved was that we had a limited number of technical people on it. You definitely need to be savvy with a lot of heavy SQL as well as API integrations. if you're trying to utilize it the most, the best thing to do is utilize their development platform. They have a developers page that really does wonders and takes it to the next step. If you're investing in it, then invest in being able to utilize that.

They also have a webpage where they show a lot of examples with different data models, showing you how to utilize tools to the best of their capabilities. That is really great as well.

The UI is definitely easy to pick up. If you do have a little bit of SQL experience, it's easier to use, rather than trying your own merge capability. It has its own user interface where you can do what you would initially do with queries or Redshift. That part is pretty good. But I prefer to use Domo's SQL and Redshift capabilities that require a little bit of coding, compared to what it has in its user interface, which allows similar processes.

That being said, everything else has been really easy and very self-explanatory. They do have good documentation and they have user groups and discussion boards that provide a lot of answers to your questions.

I definitely see use of the solution growing. There's so much more that it can be used for. There's a lot of predictive analysis that it can go into, and a lot of connectors that it can work with that allow you to use more and more functionalities and help with that whole predictive analysis aspect. In my previous organization, when I was there, they were growing the team to focus on what they could do with Domo.

Overall, Domo really transformed how we worked with data. Things that would normally take three or four weeks could be set up to take a day or two, if not less. The fact that it was able to take a whole workload off and provide a lot of analysis and even further insight, in that shorter amount of time, was great.

I use it for data modeling and data structuring for my clients. An entire data set cannot be utilized for visualization. There are a few data points which can give us exact output, which clients use for their KPIs.

We try to minimize the data and extract the required data for the key performance indicators, which helps us to drive more monitoring results for our clients and to give them exact information, even in the forecasting.

The design dashboard has given us more leverage to customize things. And with the click of a button we can quickly extract the required reports and then share them to the client if the client does not have access to Domo.

It allows our clients to see data on their day-to-day business and to review things at the management level: how the business is performing, what regions are doing good numbers, which region is performing best, and where business is low. They need to find the reasons for differences in performance, whether its marketing or recruitment lapses, etc. They are able to share the insights with their counterparts and this is where the decision-making comes from.

The most valuable features are the

• ETL
• SQL.

ETL is the feature where we can do much of the data structuring, per the client's requirements. With ETL there are things a layman can understand.

SQL is the most used database system and we depend on it for the extraction of required data. However, unlike the ETL, SQL can only be understood by a tenured person who is into the details of SQL coding etc. That's the major difference between the two. Both are highly utilized at my end.

Over the time I have been using Domo, I've seen many updates pushing great features into it in new versions. Every new release has more and more insights. A major improvement was the design dashboards wherein we can customize dashboards with the KPIs that clients want to monitor on a day-to-day basis. And in a significant number of cases, we showcase monthly-review or quarterly-review data. They are quick enough that our clients can download the entire dashboard in a PPT and start their review. Others review things within Domo itself.

The forecasting feature, the regression features, and the Python libraries could all be improved. They're all in beta. It is feasible to go out and extract data from libraries and attach work to the libraries, but with the respect to initial insights, I would like to see more help from Domo. I would like more information on how to utilize those libraries.

I've been using the solution for almost two years.

New releases are communicated with a popup saying a new release will be coming through on a certain date. We definitely check the data to make sure everything went smoothly. We'll reach out to about any bugs through the active community forum. We have received the answers we need there.

I do see limitations with respect to the Domo Appstore. If a client has a specific requirement, we need to reach out to Domo and get things installed for them.

There is the Domo Community which is a live brainstorming session with Domo experts who answer any queries. I make myself available to participate in that, so that I get quick answers to my queries. If there is anything beyond that, we, as an organization, reach out to the community. We will first try solutions if someone else has had the same kinds of bugs. If they have the answers we can finish it up ourselves. Otherwise, we have a BI team that will reach out to Domo and get the insights.

Overall, I would rate their technical support at eight out of 10. 

In the first year, when I joined the organization, I was introduced to Domo. Prior to that I had experience with Tableau. When I started diving into the details of Domo, I got to know it and found it has the best GUI. And it already has an ETL tool embedded in it, for extract, transform, and load. That was not available in the other tool I used.

Traditionally, things were done with Excel, but I don't think it is quick enough to turn things around for our clients.

The setup is simple for someone who knows the system. If it's the first time doing it, the setup will be tricky. 

We go with a four-week implementation strategy, wherein we gather requirements from the clients, we have a brainstorming session to understand what kind of system they are using and what sources they are using. We'll extract and build the dashboards for them. And then we come to the documentation, where we document the details of requirements and then we deliver it, based on the timeline. This is all done within the four-week period, and we give them the standard set of cards.

From our end, for the reporting from Domo, we need just one person involved and that same person handles the day-to-day maintenance.

One of our clients, for example, sees on a monthly basis how much money they are saving, on a cumulative basis. They say a certain type of conversion was only at 40 percent and now it has increased to 65 percent.

The pricing is partnership-based for us. There are no other costs for Domo aside from the standard fees. 

It produces the best output. I'm quite satisfied with the tool.

We take the initiative, on our end, to give the client the best insights on how to use Domo. If they are sharing Domo access, we help them to understand how they can best use the tool and how they can change the chart visualizations, to make them suitable for their review and for understanding. Those are the key factors where we advise clients so that, with the click of a button, they have their own insights coming in.

The end-users at our clients include program managers, in particular, and then the top level, the executive level. Most of our clients have around five users.

The tool is very popular in the Asia-Pacific region. It's spreading its wings. Even in India, I've seen people starting to use this tool. The major advantages are its GUI and that it's in the cloud. The visualization features, with its colors, are friendly to the eye. It doesn't display information in dark colors.

I would definitely be curious to explore Domo more and more because it has features such as data scientist rules. You can apply their forecasting. I intend to explore those areas more.

Distribution of visualizations via a web portal is valuable, but really is basic table stakes. If you are looking for a true analytical tool, skip Domo.

It has not helped materially. If anything it has hurt, since a better solution would have sped up the dissemination of valuable information in a more actionable manner.

1. Allow visualizations to stay locked in place relative to each other, rather than shuffling around based on screen size
2. More connectors
3. Better, more responsive tech support and customer service
4. Better visualization creation tools
5. More control over both primary and secondary axes
6. More control over each series' type (line, column, etc.)
7. Allow users to trigger a data refresh
8. Faster speed of rendering during visualization creation

I used it for about four months.

Yes. refreshing the data was unstable and would periodically stop working for weeks.

We did not try to scale to any meaningful level.

Poor as data refresh issues took weeks too resolve and there was minimal communication with my team.

Poor as data refresh issues took weeks too resolve.

Yes, I have used Excel, SSRS and Tableau for BI deployments and would do so again before ever deploying Domo. The sales team sold a non-technical executive on the concept of being able to chat about the data, which is a useless, gimmicky feature at best, since now your employees have to look an additional place besides email and IM for prior threads.

Significantly negative. It is a very expensive product with a lot of problems and limitations. I would strongly advise anyone to avoid it.

You should choose something else, like Tableau, BIME, SSRS, or even Excel.