We have seen ROI for our original automations. They were mostly low-hanging fruits with savings of a few FTEs, but the moment any automation has an ROI of only one FTE, it is not an economical solution for us to use. Power Automate Desktop is cheaper for us to use.

We get a significant ROI even though the licensing cost is higher than average. The gains we realize from the initial development make up for it. In the last three years, I estimate we have saved around 2,200 hours of labor. To date, we've saved almost $6 million. 

We saw a return on investment with 50 percent of our automation processes. 

We are investing a lot in the licensing cost. If there was no ROI, our organization would not invest in it. We calculate the efficiency in terms of the effort saved by our full-time employees, which could vary depending on the processes. There could be 2% or 5% savings monthly, and based on that, we calculate the annual savings. Overall, there could be a 10% to 12% improvement in efficiency.

The solution is definitely worth the money. It is up to you to add quality use cases and utilize the digital workforce along with the human workforce. The tools are there, but the actual metrics derived are your baby. There are many benefits to automation solutions. 

I won't give 100% credit to the solution. Perhaps UiPath would have given us the same results. The way you use a solution makes all the difference in ROI. 

Our ROI was roughly 10 months.

By implementing processes using Automation Anywhere, we can save up to 3,000 euros within two weeks of development.

We have saved us both money and time. 

Calculating ROI for us is pretty simple. We identify efficiency at the beginning, then based on that we will just move the headcount out of the process. We try to compare with the cost spent versus the quote of the money that we have saved on the fully loaded employee cost. That's a simple comparison of what we do. This is a very crude way of calculating our return on investment because there are other benefits that are derived by doing an automation. Other benefits include:

• Improving the quality of the process.
• Eliminating some of the duplicate payments to save some dollars. 
• Making timely payments to the vendor to have better negotiation skills with them. 

These are some of the other overall business benefits that you can derive out of it, but they are too tedious to take into consideration when you're trying to do an archive. That's why we keep it very simple by comparing the labor cost saved versus the cost spent on the technology.

To realize a return on investment, we must utilize Automation Anywhere for several years.

You get a return on investment only after 18 months. You can get 50% savings.

It has saved us a lot of hours, manual effort, and we can focus on more important tasks, which helps us with our ROI.

We will see a return on investment eventually, but we need to be patient in order to realize the potential that Automation Anywhere offers three years down the line.

Our ROI has ranged from thousands to hundreds of thousands, depending on the type of process being automated.

I have seen an ROI on the solution. The ROI depends on the use case. Some use cases have more documents we have to read, and we need to feed them into some applications. We check the FTE benefits and calculate the ROI based on it.

We have witnessed an ROI while using Automation Anywhere. 

Our organization has seen up to four times the return on investment.

We have saved customers 400% in terms of time saved by implementing this product.

We implemented automation in an HR domain. We had 60 percent reduced error rates, 25 percent freed working hours, and the response time from the HR department was faster than before. We automated candidate screening, payroll automation and expense management. In finance and accounting, they had a reduction in 70 percent error rates, 35 percent working hours were freed, and there was improved satisfaction for the internal customers after the automation implementation. Finally, in IT, there was 90 percent is the reduced error rate, because in IT everything is binary.

I have dealt with all sorts of customers, from small and medium-scale enterprises to large conglomerates. Across all of them, one commonality is that after the first year, they have all doubled their license count. 

They get a return on their investment very quickly, probably within six months the majority of customers get their ROI. After that, it is just a mushrooming effect. 

It is not only about cost savings. This technology impacts the top line as well as the bottom line of a company's P&L and balance sheets. Once they also realize its value, they come up with more asks and we scale up the journey.

Our clients do experience a return on investment through the reduction in costs for tasks that were previously carried out by humans and are now automated. Automation Anywhere is five times faster than humans and more efficient.

As I am currently part of a team of developers and people who perform functions, we are not directly involved in the deliberation of assets or ROIs. However, it is apparent that there is a return on investment, and we are noticing it.

We have many benefits reaped from the automation work we have done. So, I don't have the exact information about the cost and what our return on investment is, but it is benefiting the organization in a much bigger way by channeling efforts away from wasting manual time on processing.

Post implementing AA, ROI numbers have grown exponentially. Given the scalability and dynamics that Automation Anywhere platform supports.

We measure ROI by a number of factors: 

• Hard savings from cost dollars
• Looking at the NPV over number of years.
• Labor
• What control or compliance things that we could be saving.
• Productivity
• Employee satisfaction. 

In the first year, we got 20% to 30% ROI. In the second or third year, we got the complete amount that we invested. There is also an improvement in the business because of data accuracy.

It all depends on the scale. In one project that I have worked on, we had a savings of $200,000 over a three-year period and a payback period of 6 months. The typical ratio is that one bot will replace two people.

A cost savings example is processing parental leave applications. The volume per day that one FTE can do is eight or nine applications. When using Automation Anywhere, we can do 15 applications per day. Another thing is the improvement in accuracy and reduction in errors.

We have a good dashboard to measure ROI. Whatever investment, licensing, and resource costs together are put in for development and delivery, we are still at an ROI of 250 percent.

To measure ROI, whenever we get a use case from the business when we do an assessment, one of the factor that we capture is the time saving. We try to measure and apply the country rates for the locations where they are doing manual efforts. We measure the time savings by applying the country rates and deriving the hours and value.

The time that it takes to develop and deliver is within two to three weeks.

We started utilization of the tool with a target of generating productivity, specifically by saving 10,000 hours between August and December 2018, regardless of the number of bots deployed.

Our clients definitely see a return on investment because that's how we gain business.

In our organization, we are focusing on continuous improvement through this tool. We are improving day by day, but not focusing on the elimination of any employees. We are just focusing in our improvements and accuracy in our SLAs. Therefore, there are three things that we are focusing on:

1. Implementing our SLAs on time. 
2. Focusing on accuracy.
3. Focusing on our continuous improvement.

Automation Anywhere is profitable for us. As volumes increase and we have a lot of data, this takes time to complete manually. Bots can complete the work without impacting the business. 

We are saving time. Some processes that have taken 24 hours for our guys to do, now take seven to eight hours for our bots. That's our achievement. It also brings accuracy.

We save money indirectly. We are also improving the accuracy of our SLAs. 

So far, we haven't seen return on investment, but I think we're getting there.

We have already seen ROI. We show ROI in terms of productivity. We are already clocking in around 7000 hours of savings per month

It's an ongoing process. I have done more than 400 processes for our client over a four-year period. The time a process takes to automate depends on the complexity of the process. Within three or four weeks, a process is generally completely done, from development to production.

I have not see ROI in my current organization. However, I did see ROI in my previous organization.

In the initial year after deployment, you won't see return on investment. Eventually, when your bot is more stabilized and your processes are streamlined, in the one and half years to two years window, you will start seeing return on investment. The FTE cost is definitely higher than the license cost of each bot. If your program has been thought through, then one bot can be used to do the work of approximately two human beings worth of labor. That is where the benefit is, which will start from the second year onward. 

As an RPA developer, I do not personally have a number to share here that would reflect our organization's ROI. 

In some ways, we have seen a return on investment. For example, we have one customer who is aware of the FTE reduction (Full-Time Employee) on the repeated Bot creation jobs. They have scaled up by having their workers work in a different way. We are actually automating the repetitive Bot creation jobs and reducing the FTE where that human effort is not actually required. The company resources can spend more time focusing on the creative part of the work rather than creating the Bots.

We look forward to ROI in next three to six months. There is no direct cash savings.

With the scheduled mails that we send out to our clients every six to eight hours, it use to take one hour for a single person to create that report, then send that out to clients. This was done twice a day. Now, after every six hours, we send out a mail to clients so they can know the success or failure of their application or process. This is automatically done within three to five minutes. The report that we are doing is now more frequent and much faster with fewer errors. 

In terms of time, we are saving four to six hours daily. We have increased productivity to do more things and can monitor other applications much better now. Clients can get emails faster, which makes them happy. We are meeting SLAs.

Our previous programs have run successfully with it.

In my current organization, we have yet to see results because we are going with a small launch with two Bot Runners and one Bot Creator. We need to asses the right approach, selection processes, choosing what to automate and what not to automate, and what would be the scale of automation. That is where a lot of hard work is required going ahead to see the results coming in the next financial year.

in my previous organization, I could see a lot of cost savings and returns from automating processes. 

Our initial project had to have an ROI, and that's why we started small. We have never not had a yearly ROI. We've always greatly exceeded the cost of, or the investment in, the tool. In terms of how much it's saving us, I don't want to be quoted on the exact amount, but it's more than millions of dollars a year.

Companies now are not willing to put a large investment up front into these tools, unless the service provider that is developing the bots can assure that the bot will be successful and there will be certain savings. Clients are actually talking to the service providers first, rather than the RPA Software Vendors. It used to be that Automation Anywhere would go to the customer, convince them and sell them five licenses, and then the client would go out and start hunting for Automation Anywhere service providers or resources. The whole model has now changed 180 degrees. Now the clients are more interested in talking to consultants and trying to figure out which tool would be good, how many licenses they would need, what the scalability roadmap is, what will they be doing again in six months, 12 months, two years, etc.

It's hard to get a clear picture of the financial value that it can bring. For example, when we go in, we look at a process and we look at the value that automating the process can bring in, but there are other aspects which we look at, which are a kind of "chain effect." If I automate this, what else will break in the whole chain of processes? When there are processes A, B, and C, if I automate B, either A or C or both will feel the heat from this automation effort. If A and C are not conducive to screen-based automation, then I am in a fix because I can automate B using Automation Anywhere, but for A and C, I might need to use something else.

That type of analysis is now coming into the picture. Earlier, it was: Pick a process, automate it, feel the benefit, and then go for another. That is one reason why now we can also recommend hybrid models where multiple tools could be used via a single interface. We have to build the interface to Automation Anywhere and UiPath, or Automation Anywhere and Blue Prism to get the job done. That becomes an additional cost to the client.

For accounts payable, we saw a return in about five months from the time we started. There was a significant reduction in the number of hours that invoicing was taking. We went from 18 people to 4 people. We didn't let all those people go, but we did let a few people go, or we moved them into different job functions. 

We have seen at least 30 % savings in time and 12% saving in costs.

We have seen ROI but we are not up to the mark.

From the setup, we have spent somewhere between one and two million dollars over the past two years. I would say that our ROI is less than one million dollars. I don't want to say that it is a failure, but I would like to see a better ROI.

Had things gone the way we expected then we would have seen ROI by this time.

We measure our ROI by the money that we save.

We are currently measuring ROI based on cost, labor and time to market metrics.

We have seen an ROI. It's hard to give a solid metric because every organization has a different way of calculating it and it varies between processes. However, I can say that Automation Anywhere reduces costs while increasing productivity and accuracy. By automating repetitive tasks, we can shift our human employees to more productive work that requires imagination and creativity. 

1.5

We have seen ROI factors. I'm not able to quantify them right now. With the number of our bots, we have been able to let go contingent workforce that has been brought into the organization to cover certain operational processing, simply because we needed to supplement that permanent workforce to do those roles.

We've now gotton to the point where we don't need to hire those people or employ those people anymore, so there's cost-saving driven there. Our bots are helping with some increased revenue opportunities by acting on signals from the market for both our clients and candidates. Cumulatively, I think within the first year, I'd be very surprised if we weren't closed to ROI, which is a great story to be able to tell.

The return of investment on Automation Anywhere very good because I have automated some processes, like scraping the data from websites and updating some applications, and if we deployed full-time employees on these tasks, it would take more than a year and a half. However, if we automate the process and deploy a bot, it can be completed in just a month of time. The ROI is very good because the output is very accurate and the speed is very fast.

Our company is investing a lot of money in Automation Anywhere. They have saved money wherever humans are working. They invest a lot of money in FTEs and other logistics, so the money saving is very pretty good with Automation Anywhere. While I don't know the exact figure, the tool is saving us millions of dollars as well as saving about 40,000 hours in the last year. 

We are still in the process of deploying and evaluating both the solutions and the benefits. However, I definitely think we will see a return on investment. Looking into the number of tickets and seeing that they have decreased now because of some implementation of the solutions we intend to deploy is a good sign. We have around 40+ such use cases that we still need to deploy. Definitely, we are going to see some ROI using this product. It will develop more over time.

In one of the use cases, we use to have around 300 tickets per month which has been reduced to almost zero now.

Knowing about return on investment is not in the normal scope of what I do. But we have a lot of bots running which are saving time and effort while being more accurate, so I'm sure the company has an ROI.

We measure our success with our customers' happiness.

We have seen some return from the product.

We have seen ROI in terms of cost and time with a couple of our projects.

We have released at least $400 to $500 a month during our peak period, so we have really seen ROI with the product.

ROI is often associated with FTE, or full-time employees, but we are now increasingly finding that we could acheive ROI in different ways, not just as cost elimination. It could be cost avoidance or revenue acceleration. The ROI actually differs by use case, but in most situations, we're able to accomplish sufficient ROI to justify scaling the solution.

On average, the return that I've seen is about three dollars for every dollar spent on RPA.

Time-wise, I would say you're still bound to the pace of the systems that you are applying RPA to, so you're not getting an acceleration to the systems themselves, but you do get the ability to process transactions in those systems faster, because a bot tends to transact things a little faster than we do.

For time savings, we do time and motion studies with our business partners, so we truly know how long it takes them to do a process and calculate that in. 

Depending on the area and department, we use different rates of pay to calculate dollar savings. We also break that down, whether it's actual realized dollar savings or just a dollar savings that's not realized to the department. 

There's also risk reduction, which is a lot harder to quantify, so we've taken that to more of a high, medium, and low type of deal, because there's a number of cases where we're eliminating manual keystroke entry. That has created huge risk reduction from our standpoint.

If we count the integrations that we have done with Appian, which is where a lot of our savings is from, we are well over a million dollars in savings. This is from only doing development for about a year and a half.

We have seen a return on investment in a lot of ways. We seen dollar and time savings. There was a department that was going to have to hire somebody to just copy files from one platform to another every day. Because of this automation solution, they didn't have to hire anyone to do that. That was a good cost avoidance there. 

One of the biggest things for us is getting the whole enterprise to start learning about RPA and about different ways to think about how they do processes, whether you can improve a process first manually, then make it automated, or if it's even ready for an automated solution. This type of thinking and mindset throughout our business partners has started to make a lot of improvements throughout the corporation, not just in RPA, but in processes.

We're just getting into production right now and we're handling the first wave of production issues for getting it into production. Unfortunately, we got our code from a vendor that was helping out initially. Even though I've been here six months, I just got my hands on that code a couple of months ago, so we're having to do some cleanup.

We're really hoping by the end of next month or the month after to get a good idea of metrics on what our performance is, how fast we can work, the ROI, and the offset. We're almost there, but it's a little premature to determine ROI.

Regarding areas for ROI with this solution, the first one is that we will be able to terminate a contract for doing all this work that is going to be replaced with the bots. That immediately means lower legal costs, less overhead, less money that needs to be paid out. It's two or three bots that will be replacing multiple people. That's the initial type of ROI we can see.

It's a scale game, as well. The same code that we're doing is very applicable to a couple of other groups within compliance, within audits, which will be collecting very similar type of information from a couple of different apps. The ROI there is going to only increase because we'll have this reusable code that we can extend to other groups very quickly. I think that's why they chose this particular path. So hopefully, we'll be able to scale this ROI tremendously in the next 12 months.

Policies and procedures always change. The question is, can we be nimble enough? Can we build a platform that is solid enough, and have a pool that is talented enough to be able to produce bots in a cheap enough fashion to realize that ROI? So far, I don't see anything that would restrict that or cause that not to happen.

We have some processes to analyze the ROI, but right now, we are not focusing on knowing that information. Our main need is automation. ROI is important, but it is not critical at the moment. We are still automating projects in the company.

ROI of the current project delivered saved 4 hours of time per day of the end user.

We have to calculate ROI before the process creation to get clarification and to understand the benefits of automation. 

I invested around 2-3 weeks in learning this and creating my first bot. Then it took me a week to use it for targeting parts of my day-to-day work. And now, I am using it for the past 6-7 months without any investments and saving a lot of effort on a weekly basis.

I shouldn't be projecting this out but would say there is a grace ROI with our current clients.

I am not 100% sure. Revenue is nominal as of now. The business model defines it more in order to sustain a customer but I am sure it's doing well.

There are a lot of savings in terms of effort and time as well as costs. Automation Anywhere automates a lot of processes. It allows an organization to save the efforts of a lot people. It saves a lot of time because people can't work a whole day (24/7), but Automation Anywhere bots can.

We have not seen ROI at the present moment.

We have just deployed and are still in the validation process, so we have not seen a return on investment yet. It will take a little more time to see ROI. 

One of the first steps that we do before automating anything is we determine if it is a process where there is enough ROI involved to dedicate development resources or a bot to? Sometimes, in all honesty, the use case is we want to learn something, so we do it anyway. But, generally, we do a time and motion study, so we understand how much time we are saving somebody. We measure that. Additionally, we measure cost. That varies depending on the department that we're doing the automation for. But, we can measure that, and usually that is a straight hourly rate times the time saved.

Cost avoidance is something that we do, too. In other words, there was a process that we automated where a department was considering hiring someone just to do some file transfers and copies, etc. We automated that process, and they just didn't have to hire somebody.

It definitely saves us a lot of time and money.

We measure ROI by evaluating the entire process: 

• How long does it take to run everything? 
• How many FTEs are running the process? 
• What are the savings from a quality standpoint?
• What processes are now able to be run over the weekend without someone monitoring them over the weekend?
• What are the penalty if something is not automated?

When we measure ROI, we look at four buckets:

1. Capacity creation
2. Cost avoidance
3. Cost reduction
4. Increased accuracy and reduction of errors. 

We have a calculator that we created. We have some inputs, then based on what we realize, we receive an output or number stating, "This is the benefit that the automation gave us."

Currently, we are not looking to eliminate people. We are looking to save time or generate revenue. Cost avoidance is pretty big for us.

We have seen ROI as we keep on increasing bot utilization and building our own solution. We have optimized a few bots and integrated them into our solution. These bots have helped us prioritize our operations.

We are increasing our SME's time. Depending on the bots that we code, we are sometimes increasing or decreasing our developers' time.

the ROI of the automation investment for tax processes is very strong as apart from the process efficiency, there is also a financial aspect of lost tax credit that our solutions help to capture.

One thing that we are just changing now: When this automation journey started, everyone was talking about ROI. E.g., I'm investing X amount into the technology, and I'm now trying to cannibalize on efficiency. We are not leveraging automation just for cost reduction. The business is now leveraging automation to get it into this space where we were not able to get so far. So, the dimensions of ROI are not only cost reduction. The dimension of all ROI have been changed to scalability, compliance, some other new business go-to market strategies, etc. Those things are very much changed from the way it was here previously.

We have been able to witness a return on the investment. We have had clients where their scope was very broad and we have helped them reach their goals. The ROI that we see is not an instantaneous one because it occurs over time while you build out processes. Here and there you have greater success and the target for return on investment is made up over time.

We have certainly seen ROI when it now only takes twenty minutes to perform a job that use to take us two days.

From the second year onward, ROI is achieved, which is a great thing because year-over-year you are accruing those benefits.

We have deployed it across multiple processes: reporting, data management, or sales strategy work. We have achieved a scale where we are in a position to close $1M of benefits.

We measure ROI. The way we do it though depends on each client and whether we as a service provider have access to that information, which also depends on the client. But our clients, they measure it in a bunch of different ways. My favorite example is one where we were enabling service providers for them, basically a set of new sales reps coming onboard that have to be certified with government and have to go through an approval process. That process used to take months to run through, but with RPA, we were able to automate it and get it done in a week. So, from a revenue enablement point of view, we took all the friction out of that process, which has huge ROI for our clients.

We are thinking of implementing Bot Insight and the CoE dashboard to calculate our ROI, since our bots are not analytics-based. We are just using our bots as a bot. They are not integrated with any analytics. I know that they have a CoE dashboard, where you can define parameters to automatically calculate ROI. At the moment, we are manually calculating our effort savings.

It frees individuals up from mundane tasks so they can concentrate on being more active and creative other things that they need to do. There are two use cases that we have around for this: 

1. We receive benefit and reduce tying up of valued resources. 
2. For processes which are executed less frequently. E.g., there may be monthly processes with one to two people, and instead of relying on those individuals to run those processes, I can automate them. Then, I can get more consistent results when relying on a process which is manually driven.

We initially started with a number of full-time employees (FTEs) who we can now reassign. 

For example, with the collections process, millions of dollars might be gained by a company, because now the automation can handle the collection of unpaid bills. Previously, it was too much for human workers to handle.

Time and monetary savings can range from 20 to 90 percent.

I don't remember the exact number, in one of my bot runner I had seen a $5million change.

If the process was totally VBA-driven, e.g., sending a mail to a client and attaching so many document to emails, that's very tedious stuff. Something might happen if you do it by VBA automation. E.g., if you're Excel is not responding or what will happen if your system will get hung. The Automation Anywhere tool is in cloud so we don't worry about that. It's all about Internet speeds and servers that are stalling out. I feel that it save us time and provides ROI as a monetary benefit because it reduces FTE, the number of headcount working for a particular project.

We are focused on reducing repetitive jobs.

We have definitely experienced an ROI in terms of saving. For example, the costs of service delivery contracts have come down because of our use of automation. 

ROI is determined by how much the account saves versus the cost of licensing that I have to pay to manage the bots. It saves me around $100,000 a year.

The extent of our usage is still quite limited. I think we can do a lot more. We had other priorities that took over and couldn't focus on getting the tool more widely used. In the coming year, we are focusing more on increasing the use of bots.

We are definitely seeing positive ROI on this, between some cost reductions as well as some FTE replacement for the more repetitive or mundane tasks.

We don't have an ROI in any of our processes. We are just trying it out now to see if it works.

We haven't had any savings yet. We have been putting more time in than saving time at this point.

We have saved time and money using this solution. It varies pretty heavily by use case. We have some bots which are saving a week or month of multiple employees' times. We have some bots saving an hour a half during a day of a team of 30 people's times. So, there is some significant savings that we've uncovered.

Currently, we are using it for the labor savings, we are not very particular about what the cost savings are. We look at how much time we are spending on manual efforts and where we can reduce them.

So far we have saved about 15 FTEs in the last one-and-a-half years.

We measure our ROI mostly by time saved, from a real person doing a task versus a bot. In some cases, we have been able to recoup revenue because processes weren't being followed correctly. Because the bot was doing the task the same way every time, we have recouped some revenue that we had lost in the past.

We save 34,000 hours of time per year and have recouped up to $6000 in lost revenue.

We couldn't put the math together. When we decided to actually procure and get the quotes, they gave us free trials for a while and extended them for months. But when it came down to it, we couldn't do ROI because our company outsources to India. Our employees are in India, and in India, $250,000 goes a very long way. We just couldn't make up the money fast enough.

It has been fair to be honest.

I don't have the exact figures but it does provide ROI.

If we talk about time, normally bots take more time than users. The benefit is the bots can work 24/7, if your application supports. With the solutions that we have now, we can have attended and unattended bots.

There are savings in terms of ROI, but It's not only about savings. It's about the customer experience nowadays. If we talk about the customer experience, your experience will be improved. There will be a lot of reversals which happen when you are processing transactions manually. When you are implementing the RPA, you eliminate those reversals. You deliver the product right the first time. That is more important in terms of keeping your organization having consistent growth. That is a very important thing. 

You will see savings, not in the same year, but in the coming years. In two to three years, you will definitely save money.

It has provided us ROI.

It saves us man-hours, headcount, and processing time.

We have automated the equivalent headcount of 500 FTEs since we started. Those people haven't been laid off. They are just doing different types of work activities.

We have established a CoE and we take our bot opportunities based on their ROIs. The best ROI opportunity goes to development first. Our ROI opportunities are compliance, profitable growth, productivity enhancements, productivity gains, number of hours the productivity saved, and resources not available that the work can be done by the bot. However, the single most important criteria that we use to measure ROI is how much time does the bot cut down from an analyst's work, as this has the best ROI. E.g., if an analyst is spending a 100 hours of work that a bot can do in one hour, we calculate the 99 hours saved as ROI.

At the end of the day, finance analysts expect faster outcomes while having their manual work taken away. There should be a more diligent way for them to add value and contributing to the organization through analytics and providing valuable insights. This removal of manual work can be done using a bot. That is the goal.

While our Automation Anywhere's implementation is in a premature stage, it has really decrease the workload on our service desk. We are looking to decrease the ticket counts too. I definitely see this solution helping us in the future.

Our tickets have decreased. We have more than 40 uses cases. We definitely see some ROI in the future from this product.

Based on our use cases, we have seen a return on our initial investment for the PoC, and we are continuing to leverage the platform as we scale.

It saves time and money. If a bot does the same work as nine out of 10 people, then you are saving money through wages. Also, a bot will work all hours without interruption, whereas FTEs may need time off or vacation. 

We have automated one process, which was running with 109 people. We reduced it down to 69 with automation.

It's too early for a return on investment.

We do automation ROI using three dimensions:

• absolute time-savings
• efficiency improvement 
• reduction in manual labor.

In some cases, we see savings on the order of $100,000 and, in the newer processes that we are trying to do, it may be up to $1,000,000.

In health care, providers need to follow up after every visit within 10 days, 15 days, 20 days, 30 days. There are different frequencies with which they need to go back to the patient and come up with personalized communication. For that reason, we have created about 10 bots that have saved our clients a lot of time on operations.

The return on investment that our customers experience with Automation Anywhere typically revolves around the saved processing time and reduced headcount.

We say an ROI after six to nine months.

The ROI of AA is best when utilized for processes involving a high volume of data. 
It plays a pivotal role in cost saving by replacing the existing time and resource-consuming project with a fast and efficient RPA solution.

Since it can be utilized 24/7, the ROI is pretty high with minimal efforts and resources by using unattended automation.

Money-wise, we get a lot of ROI. Efficiency-wise, it removes all the repetitive tasks from a person. An engineer's job is not to enter the data, check the Excel everyday, and put the data from Excel to somewhere application. If you automate the process and let Automation Anywheret do it everyday, you have a lot of time for more complicated issues. Engineers are meant to resolve issues, not doing the repetitive tasks, like Excel. Efficiency-wise, it is very good. ROI, It's also pretty good.

Just an example, in a period of two to three years, we have a positive ROI. We have a positive return. We've delivered 25 to 30 bots, which equates to over 1000 atmx files. So, for a relatively small team, we've been able to scale up quite effectively.

What we did was we took the Automation Anywhere ROI calculations and added quite a few things to it. We actually ask 15 to 18 questions around process time, number of systems used, how people, and how many hours. Ultimately, we can stack rank those ROIs on a process, then we typically try to start with the largest ROIs first. So far, with what we have done, we have seen has been relatively close (as it is almost impossible to hit the ROI exactly), but the ROI on the product is good.   

We can define certain procedure we already know, but we continue develop more user cases, which bring from the other end users.

I cannot say how much exactly we have made regarding ROI, but we can see the saving down the road.

We evaluate ROI as time savings and resource costs not needed resulting from deployed automation.

We save approximately 10,000 hours per year.

We look at ROI in a couple of different ways: FTE reduction, hours saved of human work, or errors caught. We are also looking at finding errors in our invoicing for our accounts payable team to be able to reduce those errors.

We have triple-digit returns, in percentage. I feel it's worth every dollar we paid for it. We have seen a lot of the returns in operations and back office because we had so many manual tasks there.

A good example is a process that we automated where, on that specific process, the return on investment is above 30,000 percent. The total cost of ownership is around $1,000 and the return is something like $400,000 in direct cost savings. And that's still increasing. It's an ad-hoc cleaning job that we're doing, but for every contract we change, we save about half-a-dollar per month, per letter we're sending. It amounts to a lot.

We spent one day creating that process and four days running it so the cost of ownership is really low. Those kinds of processes are unicorns. You won't find them in every business and you have to have the right people and the best ideas. But we were lucky to find that process and, by itself, it has paid for a lot of the license cost.

ROI is high; usually, one process automation is equivalent to three FTEs in our organization.

Since I am not directly involved in the ROI calculation, I would not comment on this.

I am currently able to save 2-3 hours of manual effort per week.

Not sure as it is from higher management. As of now we cannot share it.

I would rate the ROI a ten out of ten. I can say it is profitable to use Automation Anywhere as your RPA solution.

ROI achievement for most of the customers is observed from four to eight months from the time of implementation.

Our customers have better use of their manual resources. 

Costs savings have been seen by employing bots for multiple shifts instead of people. Bots are also more stable.

We have seen ROI on one of the process, but not on the other processes yet.

I have personally worked on an insurance use case where there were production teams 24/7. With the bots that we developed, they were able to do the ticketing and production support. There are multiple scenarios where the development of Automation Anywhere has improved cost efficiency and worker efficiency too.

We just started looking at the fruits of our labors to understand the return on investment so we do not have a clear picture of the actual value yet.

We are not converting to a dollar amount. We are saving time. Last year, we save around 50,000 hours.

We have seen ROI with this product. With this product, we go for any RPA use case. If it is not solving anything or giving quantifiable benefits, it does not make sense.

Our return on investment has more been based on improving things which we could not do earlier. There were some aspects of processes which we had to outsource because we were not able to do these in-house. Our return on investment is based on bringing these outsourced services and processes back in-house. In addition, ROI is based on doing things to improve the customer experience.

We have also seen ROI based on employee experience. Quantification is not easy. We cannot quantify it, but we have millennials coming into the workforce who don't want to do "boring" activities. If you tell them that the organizations has a digital workforce concept, this is a driver for them to think that the organization is the way that it should be. This is bigger than dollars when quantifying value.

We have saved time and money using this solution.

We have saved money with the solution.

This tools allows us to remove two FTEs from repetitive tasks to work on other things.

We are focusing on time saved. We have almost 27 use cases in production and, as of now, we have saved almost eight FTEs per annum.

We don't see ROI immediately. It takes from six or seven months to one year to get the ROI from what we develop. The client needs to trust the RPA solution. Once they trust it, the process, etc., they have more confidence and say, "Okay, you can do automate these other things as well." Build a client's confidence takes time.

But at the end of the day or, really, the end of the year, we can see that the ROI is there. There are benefits and they can see the benefits.

It has contributed to a positive ROI.

This information is with project senior leadership.

We have saved around 90% of the time that would be required to perform tasks manually.

Now, with the implementation of the solutions, the clients are really happy to see that the time and the cost are being saved due to the automation of their projects, without any variations in the results.

The same results are being achieved in other automation projects using this product. Our company has also partnered with Automation Anywhere to deliver more solutions to different clients.

I hope other clients also get the same benefits that we have achieved in our project. In our project, we have reduced the manual effort by 90% and have also reduced the variations in results achieved using automation by 40%. I hope this percentage should increase over time so as to benefit the team more.

We haven't seen ROI yet, but we will see it in the future.

We have just started using this solution, so we have not seen ROI yet.

You will usually see return on investment easily see because of the depth of things you can automate with it is huge.

My way measuring ROI of an automated process is that first, even before starting any automation, I will see what the input is for the process, how the process works, what the output from the process is, and I'll measure how much time it takes, end-to-end in the manual process.

There will be some initial investment ahead of time and, after that, everything is a return on investment. Based on the number of minutes it takes manually, versus automation, the reduced amount of time will be the savings that I calculate, per request. I'll put a dollar amount to it based on who the user is. If they are, for example, paid $50 per hour, and the automation saves 40 minutes, that's a savings of $33 per request.

Every time we do an automation, we definitely note how many requests it processes. For example, in ServiceNow we count every automation request that goes through, without manual intervention. It writes to a table and we go there and run a report on the table. Straight away, I know my return on investment from that part of the automation.

We have seen more efficient processing and less number of errors due to quality control.

Savings have not been able to catch it that much. I believe there is huge potential here. This year, we are focusing a lot on the indirect benefits of speeding up the process. For example, we want our key customers to benefit, or buyers and suppliers boost up their business to receive benefits indirectly by freeing up their time.

ROI is very good. We measure processes that we automate and calculate the reduced cost.

The ROI in terms of finance cannot be disclosed due to company policy but the bots have made the everyday process of extracting logistics information from customer Excel sheets or PDF files much more efficient and faster than the traditional manual method.

There has been a great return on investment. We are interested in saving manual engineer man-hours. So far, we have saved $100,000.

I have seen customers save resources by using this tool. One of them replaced two hundred users with automation.

Our return on investment is that it costs us less. One of the problems with some licensing is if you have six employees and later 27 people are working, your cost can go up even if nothing extra is used. Now we need one developer's license only. One license and it is covered. There are more problems if you have to purchase one license per user. For example, if five people never work with the product and two of us work daily we are charged for the minutes for the CPU. It is not wasted.

We have seen ROI. In fact, before starting automation we performed an initial feasibility analysis which resulted in our proceeding with the implementation. Most of our deployments see ROI between six and nine months.

We have saved time and money using the solution.

We measure the ROI of automated processes by how much of a benefit we're getting from it. We look at how much time it takes and how many robots we're using and we include the licensing and operations costs. Finally, we take into account how much faster the performance of the bot is, compared to how long it took to do the process before automation.

We have saved time and money, but when people think of going with RPA they cannot expect that they will immediately see ROI. They have to sustain and increase the RPA options. They will have to spend a minimum of one or two years increasing their use cases for automation. Then they will see a good ROI. They should not expect, within three months, to say, "Hey, I have automated, where is the ROI?"

The time savings depends on the process. By using a bot, we have saved 40 to 70 percent. If the process uses unattended automation, it saves a lot of time.

Currently, I don't think that we have saved money with this solution.

It has saved us a lot of time and money.

Based on our department's statistics, we've been able to recover our initial costing after two-plus years.

We have more than 50 bots in the company. The FTE and ROI are very good. In the future, we have many projects in pipeline that we are about to implement. So, definitely there is a good ROI and FTE savings for us.

RPA implementation will be always fruitful. Return on investment will be always higher than the input costs.

What it takes a human ten hours to do, automation should complete it in one hour. In the past ten months, I have saved the work of two people. People are happy with the results.

We are measuring our ROI in terms of power saved.

We do a cost-benefit analysis along with a feasibility study. We do this initially when there is a project that is lined up. We look at how many hours the project will take. We also delivery time and its urgency. Even if the project may not save a huge number of hours, we still might pick it up because of the urgency. Sometimes, we also look at it from an error reduction standpoint. There could be a lot of errors coming out because it was manually processed and this may cause the company issues. With Automation Anywhere, we reduce these errors.

I was not involved in the cost or purchasing, but as far as I know, the return is great. There are a couple of projects that we have worked on where we could have saved approximately 4000 hours on just one project that we built in two to three weeks. This is the type of impact this solution has.

The initial setup is not that complex. We just download the software. Anyone can go and download it. It can be downloaded with two-way server. Then, the next step is to get a license for development and other things. Once development is done and it has been move to product, the client can use it.

I'm not 100 percent sure how we measure the ROI of a process we automate because a lot of that is handled by my manager. From what I know, we measure it based on time returned to the employee. Instead of calculating how much time it takes for the automation, we calculate how much time the employee was spending on this task beforehand, and now that we've moved it to an automated process, how much we have saved them.

Overall, I think we have seen ROI, but I don't have specifics.

I'm working as RPA developer so don't have any idea about the ROI.

It helps to increase the ROI by 25%.

From my experience, I can say that the initial setup cost is easily recovered over a period of time once the bots start running in production. We develop bots for our clients and as per their information, most of the time, the automation of a single process has returned their original investment amount.

The return on investment for most of our clients depends from scenario to scenario. Some of them look at it on a long-term basis and some of them look at it from the amount of time saved. For example, we are currently working on a solution for a CIO. We are saving about four hours of his time during a particular week. The return on investment for that particular person is humongous.

We have seen ROI in areas I mentioned earlier like time savings. We have seen good results.

We analyze ROI with what we call 3D or 3V. We look at the value proposition in three ways. First is, of course, the direct cost savings in terms of how many manual labor hours we are saving. The second thing is indirect, such as productive improvisation of the bot, and the third thing is the overall efficiency of the system. Today, when people do the ROI calculation, they just focus on a particular process. In the case of a supplier, if the requisition creation was taking a week, the rest of the processes were getting delayed.

The ecosystem processes what automatically improvises well even though RP did not even touch it. So those are some of the things what we try to bring into the picture when we do the ROI calculation other than the direct cost.

One way to measure ROI is based on how much customers are spending. Most of the customers start with the smaller licensing pack and they are increasing their investment in terms of the licensing and services every year. Some customers start with about $10,000 and end up spending about $300,000 just on the licensing over a two years period. That speaks for itself.

Our ROI is around productivity savings, agile headcount savings, but we also look at things like improvement in net promoter scores. Customer satisfaction is very important as well. There's no point necessarily just saving money if your customers aren't going to be any happier.

We have saved both time and money.

We measure ROI, but not with the Automation Anywhere tool. We have our own tool for that.

Automation Anywhere saves time and money.

Before the automation, it used to take about two to three hours. Now, with automation, it takes about 40 minutes. We measure ROI with time.

We measure ROI as in the number of hours saved not performing manual activities.

We have seen ROI, otherwise we would have stopped using the product.

At a base level, for ROI, we equate a dollar value out to the process owner, or the business user, and multiply that out by the number of hours being saved. However, that is really base level. There are other factors involved that will help:

• If you reduce the number of errors.
• If it's related to month-end or quarter-end close for a business cycle. 
• When automating a base level process, that saves time, but it doesn't always account for the additional time given back to the user to perform another higher value-added task, as well.

Our ROI is approximately USD $40k to $50k.

We saved millions of dollars and had FTE benefits.

>80%

Since the support for IE is discontinuing soon, we are now moving the base code to EDGE Chromium. ROI will be recounted after that. Previously as per the efficiency, we decreased the numbers from the process.

Our customers are effectively using more solutions on this with a good ROI.

We saved around 80% man-power.

So far, the organization has 20+ bots, which has generated more than $50K of ROI. As a developer, I am not familiar with all of the numbers.

We calculate our ROI as FTE and dollar savings.

We have seen ROI.

Using this solution has brought a lot of return on investment in terms of saving hours or FTEs. We are utilizing them in more constructive areas.

A bot is doing in one hour what it takes ten hours for a person to do. This savings in time is very important for the IT industry. Most of the time being wasted is on simple things, so if the bot is doing then work then it gives more time of other things, such as coding.

We have saved one to two FTEs per year. A bot processes their projects now.

It is too early to determine ROI.

We have saved a lot of time and replaced a few FPEs with this solution. It is a one-time investment for a year. You may replace people or alternatively put them elsewhere to work on better activities. This solution saves money for our clients, which is a good thing.

We have seen ROI since implementing this solution. We started with the HR processes and we are using healthcare information. It has given a decent ROI. We used to have fifteen employees, but now there are two or three who manage and support the bots.

In most of the cases, the product value is very good. If the infrastructure, implementation, and framework are good, then generally, the client can get a good return on investment. However, getting good resources is tough since most people have limited experience in RPA products who struggle a lot to use these tools.

We measure ROI by comparing hours saved to the cost of FTEs.

We measure ROI by how much we are saving for our internal people.

We measure our ROI through money and time saved. That's how we measure the product's value. We look at the hours performed by humans, and those hours have a cost associated with them. We multiply our transactions by the number of hours it used to take by humans.

Time-wise: We have saved hundreds of thousands of hours.

The ROI is really good. We have saved time and money.

I believe our clients do see a return on investment because they continue to use the solution for their automation needs.

Most of our ROIs were calculated based on the FTE hours saved since the teams were internal. for some projects it was around 4 hours weekly to 13 hours weekly for others.

We are expecting a significant ROI by the end of the year. 

Our ROI is 70% annually.

The ROI is pretty good. I have used it in one of my use cases where I have a dependency on three FTE, and I was able to reduce it by a considerable margin.

Our ROI is high.

Our ROI is very good by using AA. There are some projects where we can get close to 1:10 ROI.

ROI was much higher compared to what we have expected or calculated during our ROI calculation stage.

ROI depends on time, cost, output accuracy, and effective and consistent results.

ROI is as expected.

The initial numbers look good, so I think that we will see ROI over time.

We have seen ROI. Our business cases only get approved if there is an ROI.

We have seen ROI by having our employee do more value-add activities.

We have received 70 percent optimization using this solution.

We measure ROI through time and labor savings (FTEs). 

We save time through our reduction in cycle time: 30 to 35 days.

We have saved 53 minutes through automation.

It is negative right now. What we are expecting, for one bot creation, is a six-month turnaround for getting ROI, but that is only the developer man-hour versus actual time saved. If we include all the licenses and launch activities that we have done, we are far from getting a ROI. It will probably take another one to two.

We have definitely seen a return on investment with this product.

The ROI on major bots has been phenomenal.

ROI is important for the business case. ROI is good if you are going for long run, year on year. i never stayed on a project till we start getting the actual values, i see nowadays ROI is shrinking due to RPA vendors raising thier license costs , additional cost added to get the complex RPA solutions to be implemented

6 Months to 1.6 years depending on the process we looking to automate

We have developed 20 bots in our organization. We have a pretty good ROI as of now. 

We have seen ROI on two out of our three bot processes. We see ROI from hours returned back to us.

Our clients are seeing an economic downturn. In any economic downturn, margins are a great challenge. As a company, we can bring out profitability by automating a lot of processes on our clients' side. We always recommend to our clients is they can save as much as 25 percent of their CAPEX in the first year, then by second year, they should be able to save up to 50 percent of their OPEX. This can bring them huge profitability.

We have seen ROI.

If a company is getting work done by robots, work that is otherwise hard to get done, then Automation Anywhere is definitely a good investment for them.

We didn't go Big Bang on thinking how much money that we were going to save. I wanted to make sure that could we show improvements in the efficiency, in terms of headcount. Ultimately, it comes boiled down to cost, but then if I can get one headcount reduced from the team, and be able to utilize that to somebody else, that would be a winning situation for my client and me.

We measure the ROI through FTE. Of course, there is a dollar value associated with it.

We have started to see the ROI. We are starting to see the following:

• Activities in which resources in my team would have taken four to five hours are now done in 30 minutes. 
• Some of the weekend monitoring
• Some of the weekend missing report generations
• Monday monitoring of a heavy load system. 

These are things that we are already starting to see where the time taken to do a task has been drastically reduced. So, we are seeing the performance improvement as a result.

IQ Bot is useful but the price is not friendly. Many users are interested to try it, but the cost is not a good deal when you consider ROI.

ROI is good and impressive after using automation anywhere RPA platform.

I still need to experiment a lot with it. Whatever I've done so far. it's been at an 80 to 85 percent success rate.

We were spending 50 to 70 hours a month doing manual processes and possibly making errors. Introducing bots has saved us on hours and eliminated of errors (as bots don't make them). We have not had an accuracy issue since introducing bots.

In terms of monetary savings, we automated a bot in three days that has saved us $30,000 in costs.

Our return on investment is high. We have saved primarily time.

If you implement it right way the ROI can start within one year. It delivers quick benefits in terms of ROI.

I am just a developer so I have no idea about ROI.

We've delivered approximately 150+ bots and saved about 200 FTEs worth of time per annum. 

I think the organization has been making some real profits with the help of this product, although I don't really have access to the numbers.

We have not seen ROI in the last year. We should see ROI on the platform in two or three years.

If we use attended bots, there is no ROI in the product.

This solution will tremendously reduce the cost in terms of manual work that HR is doing.

The first one is the FT savings. That's directly proportional to the cost, what client is going to spend. The second thing is, once again, time to market or the optimization and process delivery.

We have automated over 2000 man-hours.

Our ROI has been cost and time savings.

Of course, yes, we have seen ROI. Especially in this market, human capital is valued in an ageing society. If you don’t find skilled people, who’s going to do the job? If you remove the neutrality of people and build it through the bots, that is the best way to do.

Our ROI is 22.81%.

On a very high level, I can say that we saved two days for two people per week with this automation.

Our customers have seen ROI.

We are using Bot Insight to measure our ROI.

We measure ROI by saved time, FTEs reduced, and number of errors reduced.

We measure ROI by number of man-hours saved.

We measure our ROI as time savings per month returned back to the business. We are currently saving about 150 hours per month.

Some of the factors that contribute to ROI are the low cost, ease of maintenance, and automatic updates.

Our ROI is an average of 6.5%.

We have seen a return of investment because it takes less time to market in our current process. I would estimate a times savings between 20 to 30 percent.

We have seen about a 10 percent monetary savings.

We measure ROI through a combination of hours saved, errors avoided, and quality of life, which are bots based on processes which humans can do quickly but hate doing them. We have a couple bots built around quality of life.

We have seen a return on investment. Every time we have these processes running, it's definitely helping out on that front.

With the bots that we have in production, we have two of them that are time savers. We have a third bot which takes longer being automated than it did with the human process.

At the moment, it is about even time. We are not using it as a money saver.

We haven’t seen any returns yet.

This initiative is not something that we expect will have a quick, huge impact. We are still in the process of expanding and penetrating the solution. We will enter the phase where we see targeted impact shortly. In order to achieve this, we would like to see the support by Automation Anywhere reinforced along the way. 

Anything above 50%. Most clients cannot go for anything less.

Using AA has improved the lifestyle of the employee. Monetary ROI cannot be revealed as per company rules and policies.

We have saved 60 to 70 percent on operations.

Automation Anywhere has save us more than $40,000 in the past year.

We have saved time.

We are measuring ROI through quality: Reducing errors, saving time, and saving money.

Measuring ROI is a combination of multiple factors. It could be saving time, saving money, or getting controls into the systems. It's a combination of all this things.

ROI has increased than earlier in much higher percentage.

It lessens the FTE required to complete our daily task and provided more time for us to expand our capability to accept additional tasks.

It's just the time; the pure amount of time. Imagine processing 5,000 to 6,000 documents, how much time does that take if a person does it? It saves on the quality of work, because the quality can be bad when somebody's doing it. If a bot does the work, it's faster and comes with good quality. These are two important things along with the cost saving in the long run. That's where the value is.

The tool is a huge time saver. If I want to do something manually, it will take half an hour, but the bot can do the task within minute or seconds. In a day, month, or year, this will be a huge amount of time for me. A reduction to a fraction of seconds will be a big impact.

We have seen ROI with this solution in terms of automating manual processes, resulting in FTE benefits.

We save only time, not money. We save 30 minutes every day using this solution.

A software Bot can cost one third the price of an offshore FTE and as little as one fifth the price of an onshore FTE.

ROI is something my management knows, but as a developer, I cannot say for. However, I am pretty sure that AA has benefited our company.

There is a return on investment. The automation and scalability provide benefits in terms of reinvesting or reusing what we have developed.

We measure ROI through our FTE savings.

We measure ROI based on the optimization that we have done and how much cost we can save.

• With the rebate processing automation that we did, it has provided us a savings of around an hour or two a person on a daily basis, which is quite a lot of savings. 
• With our accounts receivable process, we are still in the process of implementing it. Once it will be implemented, we are expecting about 30 to 40 hours a month in time saved.

We save time with the solution, so we have more time to reuse and spend on our clients. 

We do see ROI in the sense of staff reductions. However, if we are to apply it to the general administrative area, I think it’s not as easy to get a real ROI.

We have seen good ROI.

My clients have seen ROI. What would take them two to three days in work is now taking them two to three hours.

Initially, we did see ROI. The problem is that we could not re-use those licenses. One license is not going to be running for twenty-four hours. We considered planning and scheduling to make the best of this, but its split across multiple teams, so there are multiple license requirements. Not everything has huge savings attached.

We are measuring our ROI through time savings. We haven't done metrics for money yet.

We have not yet seen ROI, but our estimation is that it will occur within three years. We have made a huge investment in this solution.

Our CoE calculates our ROI.

I don't think that we have seen ROI yet.