What is our primary use case?
We're using it for cooperative business processes. For instance, if you work with IT and you want to request access to a specific database, you make the request using Bizagi and create a ticket. Similarly, for many other processes, when you want to request access to a system or to a physical area in the building, you use Bizagi.
It's a company requirement because I work for a large French and Brazilian insurance company. I work supporting over 2,700 active users and developing new processes.
How has it helped my organization?
Since 2018, we have registered approximately 168,000 tickets on Bizagi. There are actually more than that, as those are just the queries in one database, not all of them.
It has helped free up employees to do more valuable work. We hear that from our inside customers that we develop processes for. It helps save time for our employees.
What is most valuable?
I very much like the reusable rules and forms, and the way Bizagi controls the process flow. I also like the document generating system to generate PDFs and then .doc files with information gathered from a flow. At the end of a process, you can generate a document that can be printed.
I like the orchestration capabilities very much. They are what help control the process flow.
Bizagi also helps us to automate processes. We have over 50 automated processes right now. We are able to adapt the processes that we created with Bizagi. That's almost a daily job here. We are always improving processes and upgrading them and it's easy to do. It mostly depends on the business requirements. If a change doesn't require a REST integration, it's easy to adapt the process.
What needs improvement?
In general, I appreciate Bizagi’s integration capabilities, but there is one area that consistently creates challenges: the need to manually develop certain connectors. While it’s positive that the platform allows custom connector development, Bizagi should offer native support for widely used standards. For example, integrating with REST services that use client ID and secret should be built in, not dependent on developing a DLL in .NET via Visual Studio. Relying on WAL and external assemblies for something as common as REST communication adds unnecessary complexity and slows down delivery. Native REST support would strongly benefit both developers and business users.
There is also room for improvement in Bizagi’s reporting and visualization features. The platform doesn’t need to become a full BI solution, but offering more modern, flexible, and visually appealing charts would significantly enhance the user experience. Reports have some limitations, but the graphical options in particular are outdated and could benefit from a substantial upgrade.
Additionally, Bizagi should consider revisiting its commercial flexibility. This year alone, I’ve seen at least three large Brazilian customers move away from the platform due to pricing negotiations that didn’t progress. The perception is that Bizagi’s commercial team offers little room for tailored deals, even for strategic accounts. On top of that, customers feel increasingly pressured to migrate to Bizagi Cloud, which is considerably more expensive. For many organizations, the added cost doesn’t clearly justify the move, especially when the value proposition is not fully aligned with their operational needs.
Overall, Bizagi is a strong platform, but addressing these technical and commercial points would help retain customers, increase competitiveness, and deliver a more balanced value proposition.
For how long have I used the solution?
I have been using Bizagi for modeling processes since 2007 and for business process automation since 2009.
What do I think about the stability of the solution?
The stability is pretty good. We don't have problems with Bizagi.
At the moment we are having a bit of a performance issue, but we are monitoring it to find out what is happening. It's taking a bit longer than we would like. That would be something that we would activate support for, but we don't have access to support right now.
Even though our company paid for support, it wasn't activated because of problems with the partner. We paid for the support license, but the partner didn't pay Bizagi. So we don't have support. But we should have it back in a week or so.
The performance issue is quite annoying. It's not fatal, just slow to approve and it takes five minutes to open the user options screen. It wasn't like this before.
How are customer service and support?
We have contacted their tactical support a lot. Right now, I rate them at 4 out of 10. They were much better in the past. They could be better, but they're really good.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
The tool our company used to was being discontinued. We brought the processes into Bizagi and we automated them. We are going to stop paying for the other tool and always use Bizagi.
How was the initial setup?
The one-click deployment feature in Bizagi is straightforward and efficient. The wizard manages the entire process, including versioning, which makes it the preferred option in most scenarios.
Our organization uses Bizagi enterprise-wide, with full Active Directory integration so users can authenticate with their standard corporate credentials.
In contrast, the advanced deployment process is considerably more complex and cumbersome. Developers must manually build deployment packages, manage configuration parameters, and handle all versioning activities themselves. While it offers greater flexibility, it demands significantly more effort and introduces additional points of control that must be managed by the development team.
From an operational standpoint, Bizagi requires minimal maintenance beyond standard infrastructure checks such as storage and server health. Overall, the platform is stable, but the disparity between the simplicity of the one-click deployment and the complexity of the advanced deployment remains a notable challenge.
What about the implementation team?
What's my experience with pricing, setup cost, and licensing?
We are using the paid version, not the free version.
Which other solutions did I evaluate?
I evaluated Intalio, Oracle BPM, and Aris BPA. None of them was able to automate the way I wanted.
What other advice do I have?
I like Bizagi a lot as a low-code BPMS platform. I don't have experience with other automation platforms, but I find it really simple and intuitive for business automation. You have to do the process flow mapping drawing correctly; otherwise, you can't start the automation. That's really its strength. To map correctly, you need to know it will affect automation. Most people just use Bizagi for process mapping; they don't use it for automation.
My advice is to compare the cost of the on-premises and cloud options. With the cloud option, Bizagi manages a lot of infrastructure for you, so you don't have to worry about it. If you have a problem, like we're having with the performance issue, you just call them, and they take care of the rest.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.