We just raised a $30M Series A: Read our story

Pega Robotic Process Automation OverviewUNIXBusinessApplication

Pega Robotic Process Automation is #11 ranked solution in best RPA tools. IT Central Station users give Pega Robotic Process Automation an average rating of 8 out of 10. Pega Robotic Process Automation is most commonly compared to UiPath:Pega Robotic Process Automation vs UiPath. The top industry researching this solution are professionals from a computer software company, accounting for 33% of all views.
What is Pega Robotic Process Automation?

With Pega Robotic Process Automation (RPA), organizations can automate the mundane, tedious, time-consuming, manual work that is hampering productivity and efficiency. Whether adjudicating claims, onboarding customers or employees, reconciling financials, updating customer information in systems record, Pega RPA can manage the work across your enterprise.

Pega Robotic Process Automation was previously known as Pega RPA, OpenSpan.

Pega Robotic Process Automation Buyer's Guide

Download the Pega Robotic Process Automation Buyer's Guide including reviews and more. Updated: November 2021

Pega Robotic Process Automation Customers
eBay Enterprise, M&I Bank

Pricing Advice

What users are saying about Pega Robotic Process Automation pricing:
  • "Pega is pretty costly."

Pega Robotic Process Automation Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
LS
President at a tech services company with 1-10 employees
Real User
A very flexible solution with broad capabilities that gets easy to use with time

Pros and Cons

  • "Using the tool actually ends up teaching you about making workflows more efficient."
  • "The tech support is highly available and there is plenty of online training available."
  • "It is really flexible in what it can do."
  • "The ease-of-use could be improved."

What is our primary use case?

Right now we have large scale systems, like mainframes. It is very difficult to make changes on a mainframe. One of the more common things we are using robots for is in places where our customer service reps have to do dual entry or do entry over multiple systems. We are also trying to automate some other manual processes.  

What is most valuable?

I guess the most valuable thing that we get from using robotics is part of the process of using robots. Sometimes robotic solutions are limited. You can only do so much. But there is benefit in that. For example, sometimes people want robots, but what they really need are better workflows. I think what we get out of a Pega solution is that we look hard at improving workflows as a practice. Then on top of that, we get automation through the use of robots. It just makes everything more efficient even if it is not completely automated.  

What I have seen in the industry more often than not is that people just want a robot to do something for them. They think they know what they need but they might not really look at what problems they are trying to solve. In other words, they do not want to know what is going on, they just want a robot to do whatever some task is for them. I can ask them what they are trying to do, but they are sold on their idea and not understanding what other things are out there that would do a better job of solving their issues. Sometimes clients want me to do things that robots do not do. Like one person wanted a robot to scan something like a million documents. I do not have a robot to do that.  

I am getting challenged by people who just want a robot and they do not want ideas. I think they might want to consider that maybe robots are not leading the solution and solving the bigger issue, but they doing other things. Robots are not the ultimate solution for everything.  

What needs improvement?

My pain points with Pega Robotic come down to two big things. It is swivel chairing and dual entry. Those are the two big things that are an issue with old mainframe systems. That is what people are dealing with. It is just not doing the same thing twice.  

Ease of use could probably be improved. A lot of what you do in Pega is built on Visual Studio with OpenSpan. Pega is very user-friendly and it is easy to build. But you have to know Visual Studio .net to build with it right now. If you are used to Pega, it is a different way of building because it is still essentially Visual Studio. That is the issue. No question that it can be improved. It can be improved a lot.  

For how long have I used the solution?

The Pega company bought OpenSpan. OpenSpan used to be in the market as a separate company. It has technically been Pega Robotic Process Automation since 2016.  

What do I think about the stability of the solution?

The stability is good. We do not run into problems with crashes and such.  

What do I think about the scalability of the solution?

Scalability is not an issue. If anything, you are going to be more limited by your own environment than by the tool. Some Pega or RPA is not going to limit how you scale.  

We have one robot team at our company with about 10 members. That includes analysts, developers, and testers. Right now we are small, but we are going to try to grow it over the next one to two years.  

How are customer service and technical support?

The technical support is good. They have good people. They are very available. The bigger problem is more about knowing what you have to learn, what your team has got to learn, and the questions to ask. The technical support will be right there for you.  

How was the initial setup?

The initial setup is not bad at all. I would say it was medium complexity. We got up and running and we could build a robot pretty quickly. For us, what we spent more time on is deciding what we were going to build a robot for. It was more the opportunity assessment. Once people heard that we could build robots, they flooded us with requests for building all sorts of robots. When we started getting all the requests, we started having problems with how to balance what went first right from the start. Any problems had nothing to do with Pega in general.  

We had to decide which request to do first and which one was more valuable. What we put in place was an opportunity assessment. If we got 15 requests, of course everybody thought that their robot was the most important to build first. It was coming up with that understanding and assessing the value of each of the robotic opportunities that became more difficult.  

Which other solutions did I evaluate?

I was recently looking into other robotics solutions strictly as research. We have and use Pega for our robotics now. The organization I work with wanted to know what else is available out there. Robotics is changing so quickly that it makes sense to keep up on the developments in the industry. A lot of new products are entering the market. I do not know if we will make a change in the future, but maybe something will fit our needs a little bit better later on.  

What other advice do I have?

People who are considering Pega should be aware of a few things. Pega has got plenty of online training. Make sure that you take advantage of all the online training. You might even want to hire someone from Pega just to get you started. This will keep you from running into issues where you are going to struggle when using the tool. If you have a good start, then basically it is easy flying after that. Once you build something, you learn so much from building that first robot that you will have way fewer troubles building more. It might even be a good idea to hire someone on for 90 days just to get that first robot built. You learn and then you have a roadmap on how to move forward.  

Additional features that I would like to see in Pega in the next release all have to do with ease of use. Pega itself is really easy to use when you get away from Visual Studio. What I am mostly looking for is a better UI for better building.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate Pega Robotic Process Automation as an eight-out-of-ten. The good thing about Pega is that it is very flexible. You can do a lot so the capabilities are broad. It can be tough at first to understand and start building. That is the only thing I would say is a downside. Put that aside and it has got tons of capability.  

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Vijay_S
Practice Leader at a tech services company with 201-500 employees
Real User
Top 20
Reliable and strong, but cloud presence should be expanded to other regions

Pros and Cons

  • "They are leaders in the same industry."
  • "The handwritten structured and semi-structured data recognition accuracy is much lower and is an area that definitely needs to improve."

What is our primary use case?

We are not resellers. We implement Pega Robotic Process Automation.

What is most valuable?

Definitely, we are satisfied. It's a pretty strong product.

They are leaders in the same industry.

What needs improvement?

As part of the digital transformation, most organizations are looking for the cloud option, and Pega's cloud presence is pretty much restricted to North America and Europe. There is no cloud presence in the Middle East, India, and other regions. 

Financial customers in these regions are skeptical. They don't want to have their data outside of the geography for multiple reasons, mainly because of the government policies.

Pega should consider putting the focus on other regions such as India and the Middle East. They should also start to think about a data center that is hosted in that particular country.

It is not as easy, to implement bots in Pega with the features it carries as it is in UiPath. For example, implementing a chatbot or your email bot is not that straightforward in Pega.

When we consider OCR, the degree of accuracy is less with Pega when the data is structured or semi-structured. The accuracy of the OCR in UiPath or some other products is much high with structured and semi-structured data. The handwritten structured and semi-structured data recognition accuracy is much lower and is an area that definitely needs to improve.

For how long have I used the solution?

I manage the practice and have a team that has been working with Pega for 15 years. 

They are not only working with Pega RPA but the entire platform, the entire suite of products that are offered such as RPA, BPM, and CRM.

What do I think about the stability of the solution?

Pega Robotic Process Automation is a stable product. 

We had experienced performance issues at one point, but it had to do with the infrastructure that was procured by a particular customer. We are seeing larger implementations for financial customers.

Smaller customers have also had performance issues but again, it's because of the infrastructure.

What do I think about the scalability of the solution?

Our customers vary in size. We have small business customers to enterprise customers as well as corporate customers, and customers on a medium scale.

Which solution did I use previously and why did I switch?

Our experience is predominantly with ServiceNow and Pega.

We work with multiple products. Pega and Appian are two of the key products that we are working with. It is more in the RPA and BPM space.

We also have expertise in UiPath and Automation Anywhere. Our focus is on RPA, BPM with Pega, Appian, UiPath, and Automation Anywhere. 

We also work with other products such as Salesforce, Microsoft Dynamics, and ServiceNow.

What we would recommend would depend on the customer. If it is a high scale enterprise customer who is looking for a core platform implementation, such as card dispute or claims modernization, they should go with Pega.

If a customer is looking for safe automation and easy implementation, they can use Pega, but we would recommend SalesForce because it is pretty straightforward and easy to implement. 

With many customers, we see that they prefer Appian and UiPath to go along with having Pega and Salesforce already because Appian is a product that is straightforward and low-code. Anything that is implemented in Pega is a process that takes at least three to four months as a foundation. Any changes in Pega can take a lot of time, it is not low-code. Appian can be very easily implemented because of its model. If you have an operational implementation in finance operations, legal operations, HR operations, frequent changes, and for agility, we recommend Appian. 

For customers who already have an RPA in place and already have Salesforce and they don't want a CRM but want to process data then we suggest UiPath. UiPath is pretty strong and pure RPA but it does not have a processed platform. If there are tactical solutions required we recommend UiPath.

These are the four main products we recommend to the customers depending on their current needs.

What's my experience with pricing, setup cost, and licensing?

I would like to see pricing for different geography sites. Pega is predominantly US-centric with its pricing. When we see customers in the Middle East, or the APAC region where they are is definitely looking for lower pricing, Pega still more costly because they are still in the US pricing model.

Pega is pretty costly. When you look at the competitors such as SalesForce, Newgen, and multiple other products, they have India-centric pricing, as well as pricing for the Middle East.

Which other solutions did I evaluate?

We have many customers who are interested in a comparison with many different products. We are evaluating solutions such as Pega RPA, Power Automate, and ServiceNow to create points of view of the differences between the products.

We also want a better understanding of the differences, as we don't have a lot of experience with Power Automate.

What other advice do I have?

To use Pega RPA, you have to be mature. If you are interested in RPA, I would still rank UiPath first. Pega would be the second recommendation and the third would be Appian. 

Salesforce does not have a large RPA at this point. For pure RPA, there is no question that UiPath would be the suggested product.

Pega and Appian have to achieve a certain level of maturity. They are still a part of the product line and are still excellent products similar to OpenSpan, Jira, and also Appian. The integration is not as smooth as expected and it might take a year to get seamless integration.

If I were to rate Pega as a suite, I would rate it a nine out of ten. It has CRM, process implementations, customer experience, and has RPA.

I would rate Pega Robotic Process Automation a seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Flag as inappropriate
Learn what your peers think about Pega Robotic Process Automation. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
553,954 professionals have used our research since 2012.
Joe  Karlovich
Senior Business Automation Support Developer at TIAABANK
Real User
Top 20
Helpful access to the .net framework, and very stable, but difficult to set up

Pros and Cons

  • "The most valuable aspect for myself was access to the .net framework. If I couldn't figure something out using the objects that they had provided, I could bring in the .net objects and do so using similar logic that I would in a .net or C sharp coding language. Having that familiarity was helpful."
  • "Pega has a no-code low-code environment. We do everything based on established rules. You kind-of have to learn how all their rules work and how it works for robotics before you can use the solution effectively."

What is our primary use case?

Here at the bank, there's a fraud investigation unit team. If they discover fraud on an account, they have to put restrictions on the banking account and/or credit cards, depending on what type of fraud it is. They also alert the end-user (or our associates) that there's a fraud on the account. After that, transfer calls are made to FIU. From our end, alerts would be sent out to different systems including the banking deposit and the credit card system as well as our main CRM. Restrictions and alerts would be set up on the accounts to make sure everyone knows there was fraud detected. 

What is most valuable?

The most valuable aspect for myself was access to the .net framework. If I couldn't figure something out using the objects that they had provided, I could bring in the .net objects and do so using similar logic that I would in a .net or C sharp coding language. Having that familiarity was helpful.

What needs improvement?

Pega's main drawback was that you have to go and install their platform and their platform is meant to be their main selling point with robotics just a small part of what they do. It's the platform and the overhead that requires so much extra training and costs. In contrast, Automation Anywhere is just simple to control and all about the bots. 

Pega has a no-code low-code environment. We do everything based on established rules. You kind-of have to learn how all their rules work and how it works for robotics before you can use the solution effectively.

If Pega built out the robot manager side a little bit more (so you didn't have to learn the ins and outs of their Pega rules) that would be ideal. They have this robot manager application that sits on top of the Pega platform and it does most of what you need it to do. However, there are some initial steps that do need to be set up inside of the solution, or even inside workflow items. That way, I'm just learning how to use the space.

For how long have I used the solution?

We started the contract with Pega in March of 2019.

What do I think about the stability of the solution?

The solution is rather stable. I didn't run into any issues where I couldn't automate anything. In terms of automating the solution, I think they do a great job. Once we got the platform up and running, we didn't have any issues. There were no bugs and glitches. There were no crashes. It was reliable. 

What do I think about the scalability of the solution?

The ability to scale really depends on how you build it. It's my understanding that you can build them in a scalable way. You can do that for most of these RPA technologies, however, how you build it depends on how scalable they are.

How are customer service and technical support?

We had the most issues with the platform side of the solution. If it was regarding a technical issue or if I had issues related to automating something, technical support was pretty good, but on the platform side, I would say they were not the best.

Which solution did I use previously and why did I switch?

Technically, we are using both Pega and Automation Anywhere as we work through company mergers.

Pega never made it through to production. We're trying to get everything regarding AA set up, which has been a little bit tricky at the moment because we're trying to use the other company's control room. Due to this, we're on a different domain since we're technically two different companies and they don't necessarily set up with two different companies. We're working on getting access to everything on the other company's side, and getting through the firewall and tasks of that nature. We're chipping away at a bunch of different issues.

How was the initial setup?

The initial setup is a bit complex.

The deployment took a while to execute. It wasn't as simple as some of the other options that we had been looking at.

What about the implementation team?

We handled the implementation ourselves, although we did originally was to have someone assist. Our funding was cut, and we didn't get outside assistance, which hurt us during implementation.

What other advice do I have?

In the past, we had an RPA solution set up with Pega. Then our company got bought out. The other company was using Automation Anywhere, so we are in the midst of transitioning Automation Anywhere.  We have platforms paid for by the different entities right now. Before we could get Pega really started, the company that bought us kind of squashed it. We got it up and running and installed. However, I haven't developed an entire solution on it yet due to the changes in our organization.

With Pega, there are two different parts: the platform and the actual automation software. In terms of the versions we're using, I believe the automation software is called OpenSpan and is 19.1 and the platform is 8.1.

In terms of advice, I would give to users considering using Pega, I'd caution to make sure you get an outside contractor that knows what they're doing. We had something on the books for that. Then, due to budget cuts, there was a hiring freeze, so that never got implemented. That definitely hurt the implementation of the project.

I would give the solution a seven out of ten. It wasn't bad at automating. It was just a little complicated to implement.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
MT
RPA Lead Architect and Manager at a financial services firm with 501-1,000 employees
Reseller
Top 5
Good lookup tables and configuration tables, and can be easily updated on other machines

Pros and Cons

  • "The most valuable features are the loops to lookup tables to read the data."
  • "You cannot use a two-dimensional array to read the data."

What is our primary use case?

We provide services to our clients. We have a website with monthly and daily runs in which we extract the information. Depending on the account types from the different screens on the website, we add it to an Excel spreadsheet. There is a comparison between the months to see how many are added and how many have removed the products. Once the comparison has been completed we create a comparative report and publish it to the respective stakeholders. 

What is most valuable?

The most valuable features are the loops to lookup tables to read the data.

As it is a Java-based website, there have been several trial and error runs to get the exact match rules.

We develop a normal web adaptor, not an unusual web adaptor.

Another feature that we like is the configuration tables.

What needs improvement?

There is no two-dimensional lookup table implemented. There is one dimension then to a single dimension. You cannot use a two-dimensional array to read the data. 

First, you have to read the rows, then go to the columns, then repeat the rows from the columns. You have to write a simple C# script for this to work.

In the next release, I would like to see a better UI with the latest features to design and develop faster.

For how long have I used the solution?

I have been familiar with this solution for two years.

What do I think about the stability of the solution?

There has been integration with a robotic manager and when patches are created and released, they can easily be deployed to new machines. This is a very good feature compared to other tools, where they have to be done on the spectrum machines immediately. With this solution, we have the choice to delay the deployment of patches to particular machines.

How are customer service and technical support?

I have contacted technical support several times. The delay in response time is within eight hours, but that could be because of the regional differences. Also, it may be that there are a lot of tickets being raised.

Overall, we are satisfied with the technical support.  

Which solution did I use previously and why did I switch?

Previously, I worked with Blue Prism. Blue Prism and Pega Robotics are at the same level when it comes to implementation and development. 

With Blue Prism the consistency of the reports outputs the UI failed most of the time. We had to go through to ensure that everything was correct. With Pega Robotics, once we integrated it will work with any machines after deployment until there is a change. It is more consistent than Blue Prism.

How was the initial setup?

Initially, the setup is straightforward. With the upgrade to the new version 19.1, there were some challenges with the configuration files, the common config, the studio config, and the runtime configs.

When we work on a project we go on the config and look at the 19.1 version, but normally it was a simple set up.

I took one hour to set up the Pega Robotics.

What's my experience with pricing, setup cost, and licensing?

It comes as a package, not an individual license. Other solutions have better licensing terminology.

Pega Robotics mostly work with Fortune 500 companies. 

Individualized licenses are available, but most, are as an integrated package. There are supported add-ons for legacy application integration that are used with Pega Robotics.

What other advice do I have?

I think that they are improving the IDE with the new and latest features that will help to do things in a faster way.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
MadhuChaliyan
Sr Architect at Cognizant
Real User
Top 20
Offers all of the required features to build end-to-end process automation

Pros and Cons

  • "Pega Robotics offers all the required features to build end-to-end process automation like any other similar tools. It's unique development style using data line and control flow line makes it easy to debug through the flow."
  • "I have faced many scenarios in the business workflow, where a few applications run on the Citrix environment. That could be a critical part of the process without which business won't be able to accept the automation solution. Because of one small bottleneck, you will lose a very good candidate for process automation."

What is our primary use case?

I have used Pega Robotics (OpenSpan) to automate many (~50) business processes in the banking domain. Both RPA and RDA solutions have been implemented using different types of target applications - Web, Mainframe, Windows. 

This tool is very apt in Desktop Automations for creating user interfaces to display consolidated data, summary results, controls(elements) to trigger any automation. I have designed typical automation for Customer care agents that will automatically have a transition from IVR to a human agent, search for current customer records in different applications and display a 360-degree view of the customer in the context window. 

How has it helped my organization?

If the underlying applications are stable, then we can expect a consistent outcome from the automation. The FTE benefit mainly depends on the process complexity and volume. I can say 70% success rate in the automation solution because of various dependency factors.

Automations built on legacy age-old applications always have issues because on inconsistent application behavior. Data loading issues, response time, concurrency issues are some of the very common challenges.

Mainframe and windows applications give very good automation outcome. Same with any other data files, web service calls, etc. Should be careful when automating web applications, if you design and develop according to the suggested best practices then probably less to worry.

What is most valuable?

Pega Robotics offers all the required features to build end-to-end process automation like any other similar tools. It's unique development style using data line and control flow line makes it easy to debug through the flow. Separating fine-grained processes into Activities make it design reusable components and easily do plug and play. Another useful feature in the suite is Workforce Intelligence for CRM. This is using Robotic automation and AI to understand how sales and services agents work so that you can identify top performers and plan optimization.

What needs improvement?

I have faced many scenarios in the business workflow, where a few applications run on the Citrix environment. That could be a critical part of the process without which business won't be able to accept the automation solution. Because of one small bottleneck, you will lose a very good candidate for process automation. Pega Robotics needs to improve in this area by any means. Other tools are using OCR technology and sending keystrokes to the Citrix window. To automate a critical business process I used Pega Robotics and another automation tool just for the Citrix part. Even though both they had enough licenses for both tools the customer wants to build it in Pega Robotics.

For how long have I used the solution?

I have been working on this for more than six years.

What do I think about the stability of the solution?

Automation stability mostly depends on the performance of the target applications. As an automation tool, Pega Robotics is matured and stable now.

What do I think about the scalability of the solution?

Scalability depends on deploying additional robots to perform the operations. There could be tight coupling with an underlying application you need to consider when planning scalability.

How are customer service and technical support?

We get very good technical and customer support for registered users.

How was the initial setup?

The initial setup is very straightforward.

What about the implementation team?

An in-house team did the implementation.

What was our ROI?

Our ROI is an average of 2FTE benefits for each robot deployed in the organization. You can't count on this, it may vary considerably depends on your domain, process, application usage. There are a lot of parameters impacting ROI calculation.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AC
Technical Project Manager at a tech services company with 1,001-5,000 employees
Real User
Top 5
An intuitive workflow system, that is stable and easy to setup

Pros and Cons

  • "The workflow system is very intuitive."
  • "I would like to see an enhanced auditing feature included."

What is most valuable?

The most valuable feature is the workflow. The workflow system is very intuitive.

What needs improvement?

It would be nice if they brought in some pre-defined functions such as drag and drop coding.

I would like to see an enhanced auditing feature included.

For how long have I used the solution?

I have been working with Pega Robotic Process Automation for 36 months, three years.

We are using the latest version.

What do I think about the stability of the solution?

It's a stable solution. We have not had any issues.

What do I think about the scalability of the solution?

It's a scalable product.

I have a team of approximately 50 people who are core Pega developers.

How are customer service and technical support?

The community support is awesome. They answer your questions and they support them.

The technical support is okay. I would not rate them a ten, but maybe a six or a seven out of ten.

Which solution did I use previously and why did I switch?

I have used other solutions and if you were to ask me about Robotic Process Automation, I would first choose Blue Prism and Pega would be second. The last would be WorkFusion.

How was the initial setup?

The initial setup was straightforward.

It took a couple of weeks for the team to set it up.

What about the implementation team?

We have our in-house community for Pega deployment. In fact, I lead the community.

What's my experience with pricing, setup cost, and licensing?

Pricing is handled by my legal team. This is something that is out of my control or knowledge.

What other advice do I have?

For anyone who is interested in using this solution, I would suggest doing a POC, (Proof of Concept) before the implementation.

Blue Prism, is a little better.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
SJ
Senior Manager - Business Excellence at a comms service provider with 1,001-5,000 employees
Real User
Top 20
Stable and scalable with the ability to create adapters quickly

Pros and Cons

  • "The solution's ability to create adapters quickly is its most valuable feature."
  • "The OCR capabilities of the solution could be improved."

What is our primary use case?

We primarily use the solution for automation in all areas of our organization.

What is most valuable?

The solution's ability to create adapters quickly is its most valuable feature.

What needs improvement?

The OCR capabilities of the solution could be improved.

The ability to call different website services from the server would be helpful.

The solution should offer integration with applications in Citrix.

For how long have I used the solution?

I've been using the solution for one and a half years.

What do I think about the stability of the solution?

The solution is relatively stable. We haven't had too many technical issues.

What do I think about the scalability of the solution?

The solution is fairly scalable.

Currently, we have more than a thousand users on the solution. We use it every day.

How are customer service and technical support?

We have never contacted technical support. If we face any issues, we typically go through our consultants who can assist our team.

Which solution did I use previously and why did I switch?

We didn't previously use a different solution. It's the only RPA we have had experience with.

How was the initial setup?

The initial setup was straightforward. We didn't face any difficulties with the implementation.

Deployment took six months.

What about the implementation team?

We used a consultant to assist our technical team with the deployment.

What's my experience with pricing, setup cost, and licensing?

We haven't paid for anything above the standard licensing fee.

What other advice do I have?

The solution is relatively stable and we find it a good product. The only drawback which we found is a lack of OCR capabilities, which we'll need other software to cover for us.

I'd rate the solution eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Pega Robotic Process Automation Report and get advice and tips from experienced pros sharing their opinions.