Automation Hero vs. SAP Build

I recommend Automation Hero when you receive a lot of communications (email or fax) with a lot of attachments like documents or picture, for which there is a human operator that has to collect all the information from them and this information are basically always the same (same information, same fields, some pictures...). Automation Hero needs a little training to perform well, and this can be realized only if there is a large number of inputs. Instead, if your company manages few documents or only documents written by a human, I think Automation Hero isn't a good choice because the performance isn't good enough, and you have to dedicate too much time to the training (the value of Automation Hero is the possibility to arrange your activities quickly so if you need a lot of time, the solution is not so convenient). Also, in the classification field, I recommend Automation Hero if you have a lot of emails to manage and if you need the first classification of them before they are managed by humans (so, emails are always read by humans who provide answers, but the first step of the classification may be managed by the machine). In a few words, I think Automation Hero could work for large companies.

Incentivized

SAP Build is a strong and reliable partner with a rich FAQ and consulting power. New features make sense and are easy to distribute within the team and to end users. The community is nice, and there are many discussions on product development, shared solutions, and productivity improvements. UI is also one of the strongest points.

Incentivized

• Reading standard documents.
• Identifies key words inside a text and provides automatic replies.
• Emails classification.

Incentivized

• Its drag and drop editor is even simpler than the very popular WordPress
• No code feature to build any type of website
• Not a lot of technical expertise is required to use this tool
• The client loves it as they can themselves use it for quick tweaks

Incentivized

• The user interface could be more detailed (Robin).
• Also documents in txt or html format could be read.
• The help section for clients could be integrated into the platform without switching from one to another.

Incentivized

• Firstly there is a scope to reduce the pricing so that it can be more affordable.
• The customer support team is bit slow so it takes some time to get the answers for your queries.
• The integration is not so straightforward and it takes good amount of time.

Incentivized

Because I think it is fairly easy to navigate. But at the same time, I still think it’s not mature enough for non-developers. At least for our use cases, it has been needed to perform coding in some sense. But ofc. I think joule will help a lot here.

Incentivized

There are, for example, great blog writings about automation cases and examples. The studio version is updated often. There are also useful OpenSAP online courses.

Incentivized

Automation Hero has a great support service for its customers. They are available to work closely with our team, especially for the first steps/first implementations, and they give us a team who is confident with our local native language. When there is something that goes wrong, they have quick answers for us, so we don't have to wait for the problem solutions.

Incentivized

Compared to Mendix, we decided not to go for low code application building and in the other parts of Build, Build is stronger and better integrated with SAP. On the hand of Coding, using Build Code, gives us Joule, which understands SAP better and also have a tighter and more secure coupling with SAP services.

Incentivized

• Less IT costs because, with Hero Platforms, flows can be implemented without IT technical skills.
• Better customer services for standard questions (speed reply).
• Solutions are scalable so once you have created one you can reuse them in other departments (so the ROI for the implementation of Automation Hero must be considered for a lot of projects).

Incentivized

• SAP Build significantly reduces the effort on the integration side compared to other LCNC platforms.
• From a licensing perspective, the platform can kind of lock you in, but that's also true for other cloud platforms as well.
• Creating an app that fully works with your ERP (especially if you have S4HANA as the ERP System) is fast. It enables quick prototyping.

Incentivized