Blue Prism Reviews

We've started to use some of the new features such as translation, cognitive, and we are finding them useful. We are also finding API integrations very useful.

We would like to have something, not particularly within the tool, that gives flexibility to the end-users to schedule the bots themselves. There should be some kind of control room flexibility so that they can go in. We don't have to always keep that centralized with us. 

We would also like to have inbuilt scheduling and resource pooling to distribute the bots on servers from within the platform. I should be able to distribute or orchestrate them internally so that if one bot takes a little longer than planned, it automatically shifts to another server. 

We would also like its price to be lower.

I have been using this solution for about one and a half years.

It is stable.

It is absolutely scalable. We have close to 200 automations written in Blue Prism. We have five to six people who work on this solution.

They're good. We didn't find any issues.

This was our first platform for automation. We have used other tools such as K2, but Blue Prism is the only full-fledged RPA platform that we've used.

The initial setup was easy.

Its price should be lower.

I have heard that UiPath is catching up in a big way and offers a lot of flexibility. You can also evaluate UiPath.

I would rate Blue Prism an eight out of ten.

I'm an IT consultant and I implement Blue Prism for my clients.

The only good thing about Blue Prism is the execution speed.

The interface is okay; it is like drawing a workflow map, which some people prefer.

For developers, they should have some kind of recording feature. Their competitors have this capability, so it is a big thing.

If you execute too fast then your code dies.

The stability can be improved by building something on top of it, code-wise. When you are running the software, it needs to attach to whatever window you are on, and then you need to build it separately. This is where you get stability.

This solution is scalable because they have an object library, which others do not have. In terms of reusability, it's great.

My clients are enterprise-level organizations.

In terms of support, they have almost everything for Blue Prism. They have tutorials and other such materials.

I haven't raised any tickets with them, so I do not know about their real support model.

I use UiPath for the most part.

I have some experience with Pega RPA but it's garbage, so I don't use it.

The initial setup is straightforward. You just need SQL and then you can install it.

Ultimately, this should be set up on the cloud using Azure or another provider. however, there are lots of companies that haven't brought their automation off-site, so they are on-premises deployments.

This is a very expensive product and this is the reason that they're losing their market share.

I know that Blue Prism is trying to improve because they have acquired some other vendors.

To summarize, I think that this product is good for business but it's terrible for developers.

I would rate this solution a seven out of ten.

The primary use case of Blue Prism is for financial services. It can't be accessed via a simple web application like you can do with its competitors. For financial services where the main requirement is to retain data in-house, Blue Prism is the way to go. I'm an RPA engineer and we are customers of Blue Prism. 

Blue Prism has helped the company in areas such as invoicing, requests on an augment coming from customers and things like that.

I love the development phase of Blue Prism because there are simple things you can put in place that help you understand workflow and how implementation acts. I love how Blue Prism can use the same variables and objects used on other processes, the really key value is the object sharing. I like that you can forward so you can speed up the process while it's executing which you can do on other RPA tools, but you can also simulate the feed tool from two to four and reach the output quite nicely.

For me, a web application that can improve the connection between robot and human, and share information simply without any file sharing, without any access from the machine, that has the tower controlling it, is the easiest way to share information.

The user interface could be improved and I would like to see a web interface to easily access robot information. The key value of Blue Prism is also its main weakness because Blue Prism is quite connected to its data, so anything you do on Blue Prism is logged on the database. It's quite difficult to read these logs, so I would like to have a more valuable way of understanding how robots work on the environment. Blue Prism doesn't manage variables well. It's annoying because you have to declare visually every variable but there's not a list of the variables. You have to open the graphical elements and check the variables.

I've been using this solution for one year. 

It's a stable solution. It has a quite simple architecture and is very connected to the machine on which Blue Prism works. The RPA tools are connected with the machine, with the applications, with the credentials, and that improves stability.

The solution is very scalable because you can deploy a robot on the machine and with the same licenses you can deploy another robot on another machine. 

Technical support is quite good although I think not as good as with some other solutions. UiPath, for example, has great support, great speed, and they're right on the issues. Blue Prism has that too but they're not as good as the others. 

The initial setup is quite straightforward and similar to other solutions. 

This is an expensive solution. I think Blue Prism has a licensing mode quite different from the other RPA tools.

Blue Prism is a very secure solution because you can implement a structure as a high availability infrastructure. If you have, for example, three machines and one license, you can put this license on any of the machines. If the first machine is down, then you can put that license on another machine.

I would rate this solution a seven out of 10. 

I work for the healthcare industry, and I use it for claims orders. We have claims orders, and we have integrated service manager tickets to bring tickets from different locations or websites and update them to the SharePoint tracker. From there, we send any notifications to the concerned person.

I am currently working with an on-premise solution that is connected to the cloud UI.

We are trying to speed up the process for our client because, being in the healthcare industry, they do have a lot of defects and issues. They are working on the latest products, which have different defects and issues. Being able to speed up this process, provide information to different business people, and make things easy is the value add. These tickets are also related to claims audits, so it would also speed up the claim process.

Blue Prism supports the multi-bot architecture, which is really good. It is also really good at OCR. Blue Prism is integrated with Abbey OCR, and it provides at least 90% right information on period documents. This is something that is really good in Blue Prism.

Blue Prism can deal with a huge amount of data. We can track each and every record, and then we can see the data. If you don't have much coding experience, it makes it easy to build automations and deploy them. It is also easy to learn and easy to work with. It has a lot of features, which makes it reliable for any sort of automation.

The activities that we do are a bit difficult to do in Blue Prism as compared to UiPath. UiPath provides create activities and create packages related to AI analytical skills. This is something that Blue Prism doesn't have.

I have been using this solution for more than one and a half years.

We don't interact with their technical support. I work in an environment where we implement use cases and give them to the clients. We build use cases, do UAT for these use cases, and then deploy them for our clients. The clients already have their production support team for support. If there is any issue in the production, we do support the clients.

All these use cases are something on which we work with a fixed scope. These are not things that can be built on long-term projects. We just focus on trying to get the use cases from them, and we then build, implement, and deploy them.

I also use UiPath. When comparing Blue Prism and UiPath, there are some pros and cons in both tools. UiPath does some of the things really well but lags behind in some aspects and vice versa. Blue Prism is really good at something like multi-bot architecture and tracking of the tickets for the records. UiPath provides create activities and create packages related to AI analytical skills, which is where Blue Prism lags behind.

It was a bit complex because when I started with RPA in 2018, Blue Prism was not a free source tool for us, which is where I found difficulty in learning things and becoming familiar with all the products in Blue Prism. UiPath was a free source tool, and they provided most of the training and made it easy for us. They also provided a free community version for us, which was helpful in learning it.

I don't have an idea about Blue Prism, but I have an idea about UiPath. UiPath is scaling its business in different products. It has got products for intelligent document processing (IDP) to test or log integrations for chatbots. If you want to work on something like a true test automation, you have to buy a test book. In such cases, they have a predefined way of working with, implementing, or running things. This is where I see that UiPath might be a bit costly or expensive when compared to Blue Prism because UiPath charges for each and every product.

I would rate Blue Prism an eight out of ten. It is a good tool. 

We were trying to integrate Blue Prism for an insurance solutions company. Without manual intervention, they wanted some bots to qualify and make some selection procedures easier for certain customers and integrate them with the CTI, which is a computer technology exchange. This means that when somebody calls up, they will go to a bot and CTI. They run a bot, and the bot will guide them about how they can answer some queries for the insurance customer.

It has a centrally managed infrastructure, and it is secure. Our client was using it because of its ease of use. They had already identified some workflows that were trained on Blue Prism RPAs. It was much more convenient for them to preselect Blue Prism as compared to other vendors.

Its pricing is sometimes higher. Its price can be better.

Its presale support should be increased. Currently, its presale support is very less. System integrators generally position Blue Prism in front of customers. Though they have an ecosystem, they don't have people who can train for the partner ecosystem. They have to increase the presales consultants for partners. In addition, their L1 and L2 support can also be improved. 

Its stability is pretty good. That's the reason why they have 98% of renewals.

It depends on how you code this.

People find it difficult to get L1 and L2 support. They're pretty weak at L1 and L2 support, so you have to have your own people for that. They don't have people to answer the queries. They want system integrators to do that for them.

It depends on the use case. Some use cases are pretty simple, and some use cases are pretty complex. It also depends on how the consultant would choose to configure it, but generally, it is pretty okay in terms of configuration. 

Its price is sometimes higher.

I would rate Blue Prism an eight out of ten.

Our use cases are account receivables and account payable. In insurance, our use cases are for vetting beneficiaries, upgrading client portfolios, and updating customer's policies.

The entire tool is valuable because it is an enterprise tool. It is on par with other tools like Automation Anywhere or UiPath with the OCR/ICR facilities, analytics, and the entire package for enterprise-level security. It has the highest level of security as compared to any other tool. 

There are a lot of things coming up, such as Discovery Bot and Process Discovery. A lot of other aspects are also maturing. We have definitely started using it for our clients, and it is maturing as a solution, but it is all about how you integrate the enterprise with all the automation projects, such as your chatbot, Conversational AI, and robotics. How they are integrated and talk to each other creates a very good business case with all three aspects. The next level should be about integrating it with other automation tools as well. It can have integration with other tools or automation projects, such as your chatbot, Conversational AI, and robotics.

I am in robotics for the last seven to eight years, and I have been using Blue Prism for about three to four years.

Stability-wise, it is a good tool. 

It is definitely scalable. The whole market of RPA is definitely scalable, but it again depends on your feasibility and complexity when you study a particular environment and process. It also depends on whether you want to scale in the whole organization or different departments or you want to scale up into different areas. All RPA solutions are on par in terms of scalability. There is no difference between them.

I don't have any direct experience with them. My solution architect used to handle that. I haven't seen many technical issues because if you are going to deploy the solution and if you've studied enough about the organization and the architecture, then something major is not going to come up. Anything minor, such as securities, passwords, or anything else, can be easily managed.

It is completely run by the solution architects, which is the support team from the RPA side. All technical issues definitely involve the IT team, which is your internal architecture support team and the application support team. You need the support team from the architecture and the IT perspective to manage the technical follow-ups.

I have also used UiPath and Automation Anywhere. All these three solutions stand out because they are at the enterprise level. As compared to UiPath and Automation Anywhere, to use Blue Prism, you need developers who have hardcore development experience. It requires quite a bit on the development side. In Blue Prism, you can also code separately and write a script, which adds more value to it.

Blue Prism came too late into the market with its analytics and process discovery features, whereas Automation Anywhere and UiPath were the first ones in the market. Blue Prism is catching up, and it is in the Gartner quadrant, Forrester, etc. It is not lagging far behind.

In Europe, Blue Prism has captured a lot of markets. In the US and Asia, you will see Automation Anywhere and UiPath in the front race. Microsoft, WorkFusion, and Pega are also catching up now.

It is not that complex. It is about how you study an organization and how an organization's architecture runs through. If it is a big organization or an enterprise, then you have to have solution architects from the customer side and also from our side. Solution architects will go and study the customer's architecture. Based on that, we can select which tools are going to be used and how complex it is going to be. It is very much dependent on how the architecture of an organization is because you are going to place the automation tool into that particular organization. Therefore, the initial feasibility and study play a major role in defining the complexity of your design and the entire format or automation.

Initially, the deployment used to take quite long. Now, it is not client-based; it is web-based, and the installation process has been reduced. You just download, and there is no starting a client and all that kind of stuff. It is much easier now than it was before.

In terms of the staff required for the deployment and maintenance of Blue Prism, it depends on what kind of process you're managing. It is not about the tools; it is about the processes. You need to know:

• How complex they are?
• What is the risk factor for these processes?
• How do they impact the entire automation in terms of cost? That is a very important aspect of support because it is in production, and it is going to have a straight impact on the client's revenue.
  

Generally, one person can easily support around five processes if they fall into the simple category. If the processes fall into the complex category, then you need at least two people managing five processes. By complex, I mean when you have applications that are lengthy and the number of steps of the process are more than 500 or so, and you have to monitor the bots very closely. When the bot or the process breaks, the support team needs to take over and act accordingly. 

The roles and responsibilities and the kind of people needed for maintaining the solution vary based on whether you have agile project management or a lot of projects going on. Typically, you will need a solution architect. You would require an analyst only in the first two or three months or whatever is the period for taking care of the process you want to deploy. After that, you don't require the analysts because it only needs to be overseen from the business side, which will begin with SMEs and the production support team.

Any changes or optimization after 90 days, six months, or a year, due to multiple factors such as legislation changes or anything else, have to be done in the process that is robotized. At this stage, the SMEs and the support team play a very vital role. There should definitely be a very good support function because a lot of follow-ups happen in the process and the production in robotics. To manage them, there should be a very good ticketing system in place. The Agile methodology works perfectly fine, and it adds great value to run your process effectively and having an efficient process, but you definitely need the solution architect, application owner, project management team, and the COE team to manage the entire workflow, work items, or backlog items coming into the support function.

It is a bit higher in cost as compared to Automation Anywhere and UiPath. The rate also differs from client to client. Margins are also important when it comes to costing and licensing. There are some additional costs involved besides the standard licensing costs. You have the development team cost, which includes the project manager, development team, analyst, and testers. You also need a team manager. You also have the tools cost, architecture cost, platform cost, and the licensing cost of each bot.

You should suggest a tool only after you study the architecture of an enterprise. Every tool has its own features, upside, and downside. It is not about necessarily going for Blue Prism, Automation Anywhere, or UiPath. For implementing a solution, you definitely need to look in the market to find out what suits you. You can then go for it.  

Blue Prism, Automation Anywhere, or UiPath are on par. There is not much difference in those tools at an enterprise level. The early development cost and the cost of the platform differ in these three tools. There are some clients who say that "We want only Blue Prism. We don't want to look at anything else." In such a scenario, you can definitely go for Blue Prism because it is on par with other competitors. 

The biggest lesson that we have learned from using Blue Prism is that it is important to choose the right processes and the right complexity of the processes. You can't choose highly complex processes where you have around 800,000 steps or very volatile processes where the team is involved in the application layer or at the process level very frequently. These kinds of things could be avoided.

I would rate Blue Prism an eight out of ten because it is a very old tool. It has been around in the market for quite a while, and they have their own learnings. It is a complete package at an enterprise level, where you can have analytics and attended and unattended automation. You can run your scripts, and at an enterprise level, even security aspects are very strong as compared to what is generally required by a client. There is room for improvement. All the new features that are coming up are not being used by many clients, and a lot of learning has to happen.

We have about 20 use cases in production. Probably half of them are related to finance, monthly closures in our company, invoices, and bank reconciliations. On the IT side, use cases are about audit requirements with user attestations, user reviews, and schedules.

We're currently using the on-premises version, but we're internally moving to Azure cloud rather than moving to Blue Prism cloud.

The ease of development is the most valuable. Standard VBOs are pretty useful there with Excel and different things. Our custom developments for SAP and things like that are pretty easy to set up and quick to get going.

The control room is its worst feature. It can be laggy, and it is not as user-friendly.

We're with staying Blue Prism, but we're moving it from on-premises to Microsoft cloud for cost savings. We looked into Blue Prism cloud. It has a lot of features, but it comes with a lot of costs. Right now, we have six spots, and we're only at 13% utilization. The cost didn't really weigh out for us for moving to Blue Prism cloud, but on-premises, it is working for what we need.

Once it is set up and gets the steamroll, it seems pretty good to stay. It is self-sufficient in many ways with the processes. Change control and password are a bit of a struggle sometimes, but that's general with automation and trying to be fast-moving. Overall, it is pretty stable and self-sustaining.

It is scalable. We are using some central objects.

We probably haven't gone through their standard support channels, but we reach out to our contact there when needed, and he gets us in touch with somebody right away. So, within a week, we're talking to an expert and getting some assistance.

We just started with Blue Prism. We didn't deploy anything else previously.

I'm more on the production side. I didn't really do any of the setup functions.

I don't recall what it was. Initially, we had our licensing through the consultant, and when we stopped using them, we renegotiated licensing. Blue Prism gave us temporary licenses during the negotiation. When all things were said and done, it came out to a decent price even without the vendor. So, our management has been happy with that.

Try to think of standard automation questions related to security, change control, and things like that before you get started because once you get developing, it is hard to go back and implement those things.

I would rate Blue Prism an eight out of ten.

We are a relatively new company, which specializes primarily in finance. I believe roughly 5% of our company uses this solution, which is quite low.

Some fields in our company require the use of this solution daily, but other fields use it only monthly. So, we use it on-demand.

When we initially started using Bue Prism, it was actually acquired by the financial department in our company, but soon after, it was put across as a legacy to IT. We then expanded our use cases to other areas of IT throughout our company, but primarily, our major footprint in Baxter has been in finance. Blue Prism dominates in finance at the moment. We also have a few use cases relating to HR.

Blue Prism was our first automation platform. Originally, we used version 6.2, which was very geared toward core development. You need to have some development background to develop the bots, and they were pretty much heavy in terms of the monolithic way of the solution. But from version 6.4 onwards, there became a feature known as an API call. Technically speaking, they have actually increased their capability in API calls, which means that Blue Prism has a lot of flexibility to integrate with other enterprise applications. This API feature, which is available in version 6.4, has made our lives a lot easier compared to version 6.2.

I have been speaking directly with Blue Prism's engagement manager about making the solution more web-based. It's not quite there yet. Currently, the latest version is still under the beta version, so, as a customer, we don't have access to it. They are making it much more web-based, but for now, everything you have to log into requires an enterprise server — It's still more client-based than web-based. They are aware of these issues, but it's not available yet. If they would have done this earlier, it would have helped them occupy the market space better.

In the next release of Blue Prism, they are bringing in some great features, like deployment. I believe it's really going to focus on centralized monitoring. They are making it web-based. I think the scalability and the ease of installation are also going to get an upgrade in the new version. They are working on merging technology, like OCR capabilities — they are bringing everything under one banner. That's definitely going to help. This reboot of Blue Prism is definitely required. It's a little late, but at least they're doing it.

We have been using Blue Prism for roughly three years.

We used to have some issues with the older version of Blue Prism, which required technical support, but this has been addressed in the newer versions. Overall, after the upgrade, I'd say it's very stable.

Is it scalable? Yes and no. From Blue Prism's perspective, it's easy: you spin up a server and start deploying your blocked runners, making sure to keep them running; but from an organization's point of view, there is a lot to do on the infrastructure side — you have to pay special attention to the infrastructure where you can run your bots. So, it's scalable, but there is a cost associated with it. Every organization needs to be very careful in regard to how they're scaling it: are you going to scale it horizontally? Are you going to scale it vertically? Are you going to scale out? These are the questions that must be carefully considered when scaling it up. Otherwise, your cost will be exponentially higher if you don't pay attention to these factors.

As I mentioned earlier, we get our support from a third-party vendor and our partner — they log the tickets with Blue Prism. They engage all of the support that we are entitled to, for example, tier one, two, and three. Also, we have client engagement from Blue Prism who is constantly in touch with us, and they are always open to our feedback surrounding areas of improvement. Overall, I would say our relationship has been good with Blue Prism.

We also have experience with Automation Anywhere. From a marketing perspective, Automation Anywhere has done a lot, but since we have just started using Automation Anywhere, our lower environments are built, but our higher environment is yet to be built. 

So, why did we make the choice to use Automation Anywhere when we have Blue Prism? The simple answer is because the marketing of Automation Anywhere is better. They were offering IQ bots and attended bot runners; Blue Prism wasn't really offering these. These were big areas of consideration between the two, because when we were actually evaluating, Blue Prism didn't have a similar offering for IQ bots or attended bots that Automation Anywhere had.

The initial setup sounded simple when we started, but when we were upgrading to version 6.4, we needed our vendor partner and Blue Prism to come together. Originally, the upgrading process was estimated to take eight weeks, but we almost spent four to five months getting it set up. I think there's still a lot of complexity involved, It's not that simple. They are not very lightweight yet. There is a lot of heavy software involved, which makes the set up a little complex.

The maintenance is primarily done by us. We do have a complete license, including support, and we are in a tough IT agreement with the vendors, so we do have premium support with Blue Prism. If we require assistance, we write a ticket on the vendor platform and they will eventually hook up the Blue Prism guide. In short, we do have content enterprise support with them.

We got a discounted price after negotiating with Blue Prism, as well as Automation Anywhere through our procurement. From a list-price perspective (due to the marketing strategy of Automation Anywhere), Automation Anywhere appears to be much cheaper compared to Blue Prism; however, if you do a detailed analysis in regards to the total pricing, I think both are pretty much at war with each other. Automation Anywhere has broken down the licensing costs into multiple factors, whereas Blue Prism is very straightforward — you purchase a production license, that's it. This looks much more expensive compared to Automation Anywhere prices, but with Automation Anywhere, you have to start from scratch. I'd say they are pretty much head-to-head with each other. 

With Blue Prism, there are no additional fees. The price depends on the number of processes that you run in production and you get a license for that. Also, the lower environments are free of cost. It's pretty straightforward.

I think it's very important for an organization to evaluate what kind of use cases they have: what's their roadmap and how long is the journey that they're looking at. As the market says, most organizations are looking for this digital transformation, and Blue RP is only part of it. For any organization that needs to adapt to a digital transformation, automation RP does play a good role. They need to evaluate what exactly they want to do and then engage with Blue Prism about how to go about doing it. Remember to always bring in the experts in the market at the beginning of your journey, and work together. That helps a lot.

On a scale from one to ten, I would give Blue Prism a rating of seven.

Anything which is redundant and has the same steps can be easily automated with Blue prism hence reducing manual operation and manpower.

We have a project in which a user requests through an email, Blue prism pickups that email and according to the request finds out which access has to be provided and follows the same procedure to give access. Once access is provided a business notification is reverted back. In case of an exception the business is notified in such scenarios after maximum retries. 

We started with a very small team and small projects. As the project started getting success with Blue Prism we have a large number of teams now just for automating all the business procedures. Larger time was saved after automating the processes.

The business was very much satisfied with the results. Many projects involving Java, Mainframe SAP, Web browsers, and Windows were made. We did also use PDF automation using OCR and Surface automation which helped tremendously as our company is payroll-based and involves lots of file processing in which the toughest is interacting with PDFs. 

• Automating: Blue prism helps in reducing manual operation and manpower.
• Reporting: As cases are handled by Blue Prism we can extract all the logs and provide reports and analyze reports as per the need. We can use the reporting and dashboard feature of Blue Prism. And if the business needs a separated report we can create a separate report for such cases also by creating a process.
• Higher Productivity: Blue Prism can run in unattended mode for 27*7. No manual person needed other than Support.
• Cost-effective: As manpower is reduced.
• Higher Security: Blue Prism has inbuilt security features.
  

It can be improved more in :

1. Surface automation techniques: using region mode. Identifying images more properly.

2.OCR: Can improve more in OCR, to read text more correctly, currently can say OCR in blue prism only works for less cases and is only effective 50%. so mostly OCR's of Blue prism is very less used and other API's or tools are integrated with Blue prism for OCR techniques. 

3. Integration Support: To integrate any tool, API with blue prism. the team support is very less and also no proper details are available in Blue Prism. This can be improved much more.

4. AI: AI techniques will make Blue prism more powerful which is currently not done. 

I have been using Blue Prism for three years until now.

I was trained in .Net, and from then working in Blue Prism.

We used UiPath which was not so much effective than Blue Prism.

For simple processes use UiPath and Automation Anywhere.

For medium to high complexity processes use Blue Prism.

For much complex process involving decision making and much more of AI use Work fusin.

We did evaluate other options:

• Automation Anywhere 
• Work fusion

I use the tool for automation in various sectors like banking, telecommunication, and trading. 

We've automated web applications in the banking domain using Blue Prism. This involved automating long and complex banking processes. Every action we automate with the tool generates an audit log, which is safe within the LogRhythm environment. I do find the Decipher feature very useful when it comes to document automation. 

I would like to see a cloud version of Blue Prism available. Both cloud and on-premise options would be beneficial, as they would reduce maintenance costs. I'm using the Blue Prism desktop, which is still in the initial stages. I want enhancements in the Object Explorer and Application Model features to ensure stability in upcoming versions. I have suggested a few ideas, such as incorporating triggering mechanisms, but I haven't seen them implemented yet.

I have been using the product for the past six years. 

Earlier versions of Blue Prism, like version six, used to have a lot of issues with browser automation. Now, it has been fixed in version seven and onwards. Now, it looks good. 

Regarding scalability, we design processes very modularly with separate object and process layers for each application. This modular approach makes it highly scalable. 

The tool's installation is easier than that of other RPA tools. When deploying a process to production, we ensure that we work in a separate, unmonitored environment with restricted access. We install a centralized application server on a separate machine to avoid database load issues. Additionally, access restrictions are enforced so that only authorized personnel with restricted access can deploy packages in the production environment.

The deployment time for one process varies depending on its complexity. Complex processes could take one to two months or even longer. Testing and deployment typically take about two to three weeks for a single person working on a process from design to development.

A dedicated support team facilitates maintenance, especially when best practices are followed and a robust solution design is in place. However, the ease of maintenance also depends on the applications involved in the process.

The tool offers the best security compared to other automation tools. However, the lack of a cloud version can lead to higher maintenance costs when using Blue Prism.

Given the current market situation, I would recommend Blue Prism to other users, especially if a cloud version becomes available. Everyone has been running back behind the Gen AI and AI center. integrating it would be good. 

I rate the overall product an eight out of ten.