Bizagi Reviews

Some of our main use cases are in project risk planning and tender cost management.

Our organization's adoption of Bizagi has greatly improved governance, especially where the role of academic secretariat is involved.

I like that Bizagi is fully compatible with BPMN 2.0. It also eases the way in which we work with BPMN 2.0 itself, which is a comprehensive and rather complex notation standard.

I would like to see a facility for building a simple CRUD application. In Bizagi, you can use database modeling, diagrams, forms, etc., but in some circumstances I need CRUD (Create, Read, Update, Delete) functionalities which are not there yet.

I have been using Bizagi for the past five years. 

It is very stable and we have not had any problems.

We did not find any problems with scaling Bizagi. 

Technical support is quite satisfactory. They are very quick to resolve issues and to help new businesses get oriented with the transition to their BPM tools.

Early on, we used Excel spreadsheets for managing business processes. Then we looked into other BPM tools like IBM BPM, Oracle BPM, and Camunda BPM. However, we decided to use Bizagi because it provides rapid installation and immediate use of the various BPM tools. They also offer an easy installation script which has worked well for us.

It is fully compatible with BPMN 2.0 which is quite comprehensive and hard to learn, and Bizagi made using BPMN 2.0 much easier.

The initial setup is very easy, but only if you have well-stated requirements right from the beginning.

For academic notices, we have about 53 users. And for governance, we have about 14 users.

In governance, we have about five people in the strategic staff using Bizagi. We also have other people in management, as well as analysts, using the solution. In the academic notices, we have mainly management and operational staff.

Make sure that your requirements are explicitly defined from the outset. This will help you choose the right setup and licensing for your needs. 

I am very enthusiastic about Bizagi because it lets you see anything you need to see very quickly.

I would rate Bizagi an eight out of ten. 

We are using the solution to develop our purchase and contract system.

The solution works on BPMN functions, which provides ease of developing and sharing the process.

The solution could work faster on the cloud.

We have been using the solution for less than a year.

It is quite a stable solution. I rate its stability as an eight.

We have ten users of the solution in our organization.

The solution's initial setup is simple. It took us a week to develop the processes. Also, it requires one technical assistant for deployment and maintenance.

We deployed the solution in-house with the help of standard lessons available online.

The solution's cost is affordable.

I rate the solution an eight.

My primary use case of Bizagi was simulation, especially for office work manufacturing processes. So for these processes, you can input the number of people, the time, the responsibilities, etc., and run a simulation. 

Bizagi is really great for beginners because it's user-friendly and you can learn in it quickly, whereas other similar software are harder. 

Bizagi could be improved by more automation and machine learning. Now that I'm learning more about data analyzers, I'm realizing that many people have problems with data and how to understand them. 

I think Bizagi could use more manufacturing processes, but that's just because I specialize in that. Bizagi is better for office processes, whereas Siemens has software that is better for processes in manufacturing. 

I have been using Bizagi for a couple of years. 

Bizagi was stable. The performance was okay on my normal computer, but I felt that I wanted to move to other options. 

I have never contacted technical support. 

In the past, I have also used Vizor. 

From what I know of the market, I think Bizagi is a cheap solution for process engineering. Out of the solutions I've tried, from cheapest to most expensive, would be Vizor, Bizagi, Signavio, and then Siemens. I used a version of Bizagi that my university provided for free, so I have never paid for a license.

I'm now trying Signavio, which I prefer. I like that in Signavio you can connect it with SAP. I'm still learning, but I think Signavio is better for me. I'm also working in Siemens, so we are using SAP as our internal system. Because Signavio was bought by SAP, they are trying to integrate it, and these processes are going to be more and more automated in the future. 

I rate Bizagi a seven out of ten. I would recommend it to others who are looking to implement it.

We used it for the modeling part and some testing functionalities. We didn't use the licensed versions where you could go into automatization. So, we're more or less on the modeling level. We have used different versions of this solution.

The documentation capabilities are very good. Very structured documents and process versions are valuable features, and being able to communicate that to our customers is also a very good feature. 

It has a good balance between the effort and the result. So, you don't need to be too detailed. You can document while you are modeling, which is a very good feature.

Its performance needs to be improved. The main thing is that it is limited, especially in terms of the response times. When the processes become a bit large, it is very awkward to work with the Bizagi modeler.

When you have already modeled but start to rearrange, it is quite a bit of an effort to change the stuff. When you rearrange lanes or have new structures, it goes rather squiggly up and down and so on, which could be improved. The visual outputs of the DIREPs of the process models are pixelated and have a bad image quality. It is a PNG or JPEG, and you cannot export it as a PDF. When you have rather large processes, you should be able to arrange them hierarchically. Currently, it is not supported. If you use sub-processes and inflate a process, suddenly the arrangement is totally different, and although you know the process, you have to look where is it now. You need a good understanding of the levels of your processes before you start in Bizagi.

It can have automatic support for optimal presentation. In BPM, you should have it from the top left to the bottom right. However, in most cases, people don't know how they should arrange it. Therefore, it would be nice to have a suggestion system for different arrangements to be able to better present the process.

I have been using this solution for two years.

We are part of a larger company, and they meanwhile decided on FireStart, but they definitely want to go into the automatization of modeling and optimization. I wasn't involved in the pricing stuff, and I haven't worked too much on an operational level here, but all things I experienced with that product are very nice. The documentation and modeling are a little more complex, but the features are far richer than Bizagi. It is also direct, so you also have to pay for the modeler. I found it superior to Bizagi.

We didn't use the licensed versions where you could exactly go into automatization. However, we looked at the pricing in the beginning, and the only thing that I remember is that it was too expensive for the things we were using because our clients would also have to license the product. One client said that it was too expensive for the benefit they get out of it.

I would advise others to not make the processes too large because of the performance issues. If you have small processes, it is perfect. Before you start in Bizagi, you need a good understanding of the levels of your processes because when you have already modeled and start to rearrange, it is quite a bit of an effort to change the stuff. So, take some more time initially in organizing the processes.

I would rate Bizagi a seven out of ten.

We are using it for our processes. We have its latest version.

Its cost is the most valuable. It is not as expensive. It is also easy to make different types of processes for the users.

Bizagi doesn't have integrations with other solutions, such as ERP systems. In the industry and your company, you have a lot of systems with which you need to integrate, but Bizagi doesn't have such integrations, which makes it very difficult.

Its scalability can also be improved. It is good for a startup, but when you need something more complex, it is not good.

I have been using this solution for one year.

It is stable. We have a good impression of its stability and don't have any issues.

Its scalability is low. It is good for a startup, but when you need something more complex, this solution is not good. We have up to 50 users.

We have two to five engineers for its deployment and maintenance.

It is not expensive.

We are evaluating Appian and OutSystems to replace Bizagi. Appian or OutSystems can be implemented locally. This technology is good for transformation.

It is good for proof of concept. You can have a lot of issues if you don't know the features. It is a good solution, but when you have a complex problem, it is not enough.

I would rate Bizagi a five out of ten.

My primary use case of this product is to draw processes. I don't deal with any of the automatization or other features. I'm a customer of Bizagi and I work at a consulting company in Spain. 

The solution is very user friendly and the icons and options are high quality. I always use it as a modeler, not as a BPM.

The solution has issues when it comes to exporting in formats other than PDF, which is what I used to do. It's difficult sometimes to connect with a solution like Visio. For example, if I try to import, it's difficult because they don't keep the same pattern and process. The tools have been moved so I never connect Visio and Bizagi. The formats should be simplified, in my opinion. I'd like to be able to develop collaborative work but it's difficult to see how I could do this with Bizagi. Exporting is quite difficult and it's also impossible to attach documents. The design doesn't support this and it would be helpful if they could add this feature. 

I've been using this solution for almost four years. 

I haven't had any problems, this is a stable solution. 

The initial setup is very straightforward, it took me maybe four or five minutes. The product doesn't require maintenance. They update every new version as it appears. Sometimes there is an issue because the program comes out in English first, and it can take two or three weeks before the Spanish version comes out. I generally wait two or three weeks until they bring out the Spanish version and that's when I download it.

I'm using the free version so there are no licensing costs. 

Visio is also currently used in the company. It's now integrated with Office 365 and this is an advantage that Bizagi lacks. I think Visio is probably easier to use because they have more libraries of icons and things like that. Bizagi focuses on BPM while Visio can be used for a lot of things because it has a lot of libraries and different topics, more functionalities than Bizagi.

One thing Bizagi could implement would be the option for collaborative work because it's difficult to work with another person the way things are now. In my view, the collaborative factor is underdeveloped in Bizagi. Visio is used by most people in the company, I'm the only one using Bizagi. I used to use it on a daily basis but only occasionally now. 

I would recommend this solution because it's easy to use and very quick to install.

I rate this solution a nine out of 10. 

Our primary use case for Bizagi is about full automation. It's about the discovering process, modeling business processes, and training the people. It's at a very low stage of maturity. It's very early, it's in the beginning of this.

In our business space we are just researching, so everything is local.

To start with, the feature for training people is very interesting. Even if they had Bizagi in the office, you still have some tools that are just in the cloud, so you don't need to install things like IDOR, which is a series of tools for process utilization, what they call IU and IO. So, the feature for knowledge, discovery process, and drawing frameworks is very easy. It's the easiest at this moment. Even before we moved to process automation.

They have three or four tools for the entire SQL. They have mobility and process aging. This is good. But for the small business, this is very bad because it is still fragmented. The licensing policy should be more flexible and small company oriented. In micro-small companies, there should only be one or two. That's not the problem. Maybe it is too flexible, there are so many pieces that you need to put together.

When you have a small business, it can be a little complicated, not so easy.

I would like to see an intelligent architect included in the next release of Bizagi. There is a working process with intelligent process management right now, but that doesn't mean artificial intelligence.

I have been using Bizagi for five years.

So far its stability is good. It's not presenting a challenge. At the moment we are doing little experiments and so far it's not a problem.

Bizagi's scalability is good, but there are questions about how they will price it based on number of users. You don't know what it will cost with the number of users. It varies.

Their technical support is good. They have a lot of knowledge in whatever language. We are in Brazil and they have a machine that reads Portuguese. So that is a good thing.

I previously used the Bonitasoft tool, which is a business cross-management tool. Bonita is harder, but you can demand more from its technicians people.

We are now in the process of researching about other tools and changing to new tools. We are looking for a rather simple solution for end users with the same value chain for automation process management. We are evaluating WSO2.

Bizagi is simple. It's simple to learn. Bonita is more complex. Bonita is a tool of architecture. Bizagi is also an architecture tool and it is a business cross-management tool. They are a business cross-management system.

Bonita as a tool has an ecosystem within a better-end tool and other tools, so it's harder. It's harder than Bizagi and it's simpler than WSO2.

The complexity of the initial set up depends on the competencies of the people.

We do development in the healthcare industry, so there is a complexity with the decisions of who sees it first. There are a lot of holes in competencies.

At this stage it is just us implementing. In the next phase, we must do a selection for a contract for a specialist in each tool.

I would recommend people to test other tools. You need to compare these tools to Bizagi. 

On a scale of one to ten, I would give Bizagi an eight because it's simple. It's simple to implement. It's not perfect because of the cost aspect.

We use it in our company for the automation of processes.

We have used it for 50% of processes in our company. It has been good in converting 50% of manual processes to automatic processes.

The most valuable feature is that it is compatible with Visual Studio and .NET, and we can program it. 

Its speed is very good, and it is also stable and easy to deploy.

It would be useful if we can connect Bizagi to other solutions, such as a local financial solution or Power BI. It would also be good and helpful to be able to connect Bizagi to some services solutions. It should also support right-to-left languages, such as Arabic. 

We have been using this solution for two years.

It is stable. We didn't have any crashes or other similar things.

It is suitable for us. We have 1,000 people in our country. We can use it within the company or from other sites, such as from home.

We do everything inside our company. We don't use the support of Bizagi for incidents or other things.

Its deployment is simple. It not hard or complex.

It is expensive.

I would recommend this solution to others because it has been helpful for us.

I would rate Bizagi a seven out of ten.