Automation Anywhere (AA) Scaling Bots

How long did it take you to scale from pilot to the number of bots you’re currently using? Please describe the process.

Director2299
Director at a tech services company with 51-200 employees
It took one month to scale to the amount of bots which we are currently using.
View full review »
Operatiobf07
Operations Leader at a financial services firm with 10,001+ employees
It took us eight months to a year to scale from zero bots to 100.
View full review »
ChiefArc74eb
Chief Architect at a financial services firm with 10,001+ employees
The initial pilot was for two processes, which took us about four months. Then, the other processes were more extensive, so that took longer, only because we needed to do more with the process documentation, not so much in the bot creation. It just depends upon the complexity of the process, but also how well-documented your processes are.
View full review »
BPMan456
BPM Analyst at a financial services firm with 1,001-5,000 employees
It took us two years to scale from pilot to the number of bots that we are currently using. I wasn't involved in the early days of the PoC. I came into the group a little later after that, but now, we use a federated model. We were sort of the center of excellence for it, working with our business partners. In a number of cases, our business partners are now developing their own bots. We have developed some, where the business partners didn't have much of an interest to doing the development. They wanted to be involved in the creation, so they understood it, but they didn't want to do any of the coding in the background, so we do it for them. We do all the production support. I like to go by actual executions, not number of bots, because we have some bots that need to be executed multiple times during the day. Last time I looked, we were well over a 100 different executions in a week.
View full review »
ITProjec26f6
IT Project Lead at a financial services firm with 51-200 employees
Our first business unit who started their journey two years ago went from one bot initially to about 55 over a two-year period. Typically, they were averaging a new bot about every two to three weeks. That was with a team of five to six people sort of dedicated to the process. We have had consistent growth with our numbers over that time.
View full review »
Bruno Rocha
Workforce Coordinator at a mining and metals company with 10,001+ employees
It took us three months to scale from pilot to the number of bots that we are currently using. We started by experimenting with a very low number on the license: two Bot Runners and five Bot Creators. Now, we have 60 Bot Runners and 35 Bot Creators. We are improving as we are seeing new opportunities.
View full review »
Sunil Ranka
Founder at Predikly
To scale from pilot to the number of bots we're currently using, it took us between eight and 12 weeks.
View full review »
SeniorIT8b1c
Senior IT Design Analyst at a retailer with 1,001-5,000 employees
The company started the pilot a year and a half ago. That phase was probably six or seven months. Then, it took a little over a year to get it up and running. We also did an upgrade to the newest version, and that took some time. Overall, it took about a year to scale up our bots.
View full review »
Technica28f7
Application Lead at a financial services firm with 1,001-5,000 employees
It took a few months for us to scale from pilot to the number of bots that we are currently using.
View full review »
SeniorMad942
Senior Manager at Genpact - Headstrong
It took us two months to scale from pilot to the number of bots we're currently using.
View full review »
Will Haskell
Supervisor at a energy/utilities company with 5,001-10,000 employees
We can scale the bots in about a year. When we started, we went from a pilot of about 14 bots, which all got stripped away. Then, we ended up implementing 30 different bots about a year later.
View full review »
Buisness39d3
Senior Manager at a tech vendor with 10,001+ employees
From pilot to production, we scaled our last bot in about nine weeks. It was a very interesting process because the building deployment can be done pretty quickly, but if you don't narrow down the scope early, you can face a lot of challenges. I don't think this necessarily has to do with the platform. It is more about understanding and narrowing down your scope from the beginning. It's okay to add more functionality later, but that adds delay to your overall timeline. However, being that it's very easy to configure the bot and add components to it, this is one of the benefits of building with Automation Anywhere. You can make changes pretty quickly. With everything, you will have to be careful and not get caught up always making changes. You have to really narrow the scope down quickly and build it in very small components. Don't build everything end-to-end. Break down your processes, as much as possible, and deploy as little functionality as possible. This makes it way more easy to manage. It is also a much better way to build a bot.
View full review »
Software66b3
Software Engineer at The Travelers Companies, Inc.
To scale from pilot to the number of bots we’re currently using has taken about two years. We did a lot of experimenting before we committed to it, but once we got through a couple of those experimentation projects, we were able to form a team, figure out exactly what we were going to have to accomplish from a business point of view, and dive in. After those couple of pilots, it took about a year from when we initially starting playing with it. There was a little bit of getting our feet wet, feeling comfortable with it. But now, we have several teams and it's working great.
View full review »
Directorb51d
Director Solution Architect at a financial services firm with 5,001-10,000 employees
We started out with three production bots last year. From the time that we were deploying them into production to being able to use them in a production mode, it took somewhere between four to six months.
View full review »
Rahul Sualy
Director at a manufacturing company with 1,001-5,000 employees
At pilot, we had around four bots. Today, we have 85 bots, and that is over 12 to 13 months.
View full review »
Configur7384
Configuration Specialist at a energy/utilities company with 1,001-5,000 employees
We started with zero bots. In our first cycle, we developed around eight bots. In our second cycle, we created around five or six bots. Now, we are on our third bot cycle.
View full review »
SupplyChe0e0
Supply Chain Manager at a manufacturing company with 1,001-5,000 employees
It took us four months to scale up to our current number of bots.
View full review »
VpCorpFi5a75
VP Corporate Finance Systems at a financial services firm with 1,001-5,000 employees
It took us three months to scale up our first bot.
View full review »
ChiefITA7b2f
Chief IT Architect at a consultancy with 10,001+ employees
It took one to one and a years to scale to our current number of bots.
View full review »
Software66cd
Software Engineering Manager at a financial services firm with 10,001+ employees
It took a couple of months to scale from our pilot to the current number of bots that we are using.
View full review »
ProductM6aa8
Product Manager at a university with 5,001-10,000 employees
It took us six months to scale to our current number of bots.
View full review »
Sreeraj Nadarajan
Service Intergration Expert at a pharma/biotech company with 10,001+ employees
It took us eight months to scale to our current number of bots.
View full review »
James Luxford
VP Automation at Genpact
We can scale from the bots to the pilot to the bots we're using very quickly. It can be a handful of weeks. Depends on the complexity of the process. We like to get things out there quickly because if it's going to take six months, then the business is going to go off and do other things. So in a number of weeks is our target, usually.
View full review »
Sunil Ranka
Founder at Predikly
People are deploying hundreds of thousands of bots. We haven't hit any scalability issue at this point in time.
View full review »
Brian Dsouza
Sr IS Manager at Amgen Inc.
To scale from pilots to the current number of bots that we are using, it took three to six months. That was the time frame. We started pilots on some functions, and learning from our pilots was key.
View full review »
Bill Weathersby
Board member at Transform AI
Probably one of the faster scales that we have done is we did a prototype with IQ Bot that had about 500 invoices and a 1000 vendors. In about two and a half to three months time, start to finish, we went from the original amount to 15,000 invoices and 2500 vendors. I would suggest in that 90 to 120 day time frame, if you have done things properly and your architecture is good, that you should be able to scale at any pace that you care to.
View full review »
Farid Karmadi
Site Operations Coordinator at a retailer with 5,001-10,000 employees
We are just in the initial phases. I personally have created about three to four bots.
View full review »
Principa4a5a
Principal Analyst at a Consumer Goods with 10,001+ employees
We don't have any problems enhancing what we do except for the time in programming and troubleshooting.
View full review »
Dona Manuel
Technical Lead at Titan company
Scalability is one of the most important things for us. We were looking for that when we went to upgrade our process. We want to automate any of the processes that we can by using Automation Anywhere.
View full review »
Abdul Subhan
Senior Automation Engineer at Ryan india
It took about three to four months to transition from the PoC to using the bots.
View full review »
Amrutabandhu Choudhury
RPA Consultant at a tech services company with 10,001+ employees
It took us two months to scale from PoC to our current number of bots.
View full review »
Sagakumar Gangipelly
Sr. Software Engineer at Ryan India Tax
If the process is huge and involves 10 to 20 steps, then it might take from creation to production three to four weeks of time. If it is a simple bot, it involves just launching a website and scraping data from the PDF, then putting it in Excel. For that type of bot, we can build it in one week and deploy it in seven to 10 days.
View full review »
Principa8942
Principal Analyst at a Consumer Goods with 10,001+ employees
Scaling bots to production depends on the process and how complicated it is. For a simple process, it will take two to three weeks. If the process is a bit complex, it may take close to one to two months. It also depends on how your internal compliance is organized in the company. We have a compliance check done at every phases of automation, so it will take us more time to get the process live even for a simpler process since we have to get compliance sign off during every phase.
View full review »
Venkata Sreedhar Nalam
Technical Architect at a financial services firm with 10,001+ employees
We scaled up pretty fast. Initially, it took a couple of months for our pilot, then we were up and running pretty fast.
View full review »
Technica8809
Technical Lead at Verizon Communications
Based on the complexity of the bots, it takes six to 16 weeks for us to create bots (pilot to completion).
View full review »
SubhamMahanta
Cognitive Lead at Quosphere
We initially started off with a customer who had just three bots. We've now scaled them to 15 bots. It didn't take us more than an hour to scale. Automation Anywhere helped us scale from one bot to 100 bots within a period of hours, if not minutes.
View full review »
MichaelWilliamson
Automation Lead at Universtity of Melbourne
We started off with accounts payable type of processes. That was our proof of concept. We built that within two or three months. It was highly successful, then we got a high level of endorsement from the wider organization.
View full review »
Sign Up with Email