Bizagi Reviews

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.

I use this solution internally for my company to support departments that want to visualize their processes.

This is a free solution that allows us to create quality visualizations for our company.

The solution's interface could be a bit more user-friendly and I would like to see more integrations with other Office products, not just Office 365.

The stability of the product is fine, I have not had any issues in regards to this manner.

I don't have much to comment on the scalability as we use it as a standalone. We currently have about twenty to thirty people working on this solution locally who are a part of the design management team in addition to some consultants.

I have not needed to contact support. All of the questions that I had were answered in the FAQ's.

The initial setup was not too difficult. Though, the process during registration was not 100% clear, so this required a bit more time than I was expecting. All-in-all the process took ten to fifteen minutes.

I was able to implement the solution by myself.

This is a free solution.

We may decide to increase our usage in the future and may consider switching to Visio.

Bizagi is a good, free solution for companies that do not need to make complex diagram or flows. For those looking to create more complex visualizations, such as electrical schedules, or if you want to integrate better with other standard products, I would suggest going with Visio.

I would rate this solution a seven out of ten.

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.

Right now, I am just using the modular version of the product.

The export feature is very valuable to us. The export is nice due to the fact that there's a different way to find different formats. It's easy to modularize, with some flow. It's quite convenient. I didn't really use a simulator. I'm interested in it, however, I haven't used it yet.

In terms of navigation, when you're exporting HTML, it's good. It means you can go inside within the subprocess to get the view.  

The initial setup is super simple.

What I like about Bizagi is you just add data. You say this user is using this in the flow chart, and then you add some forms. This is what I like about it.

There's a new design and it's more modern. They've even updated the logo. It's beginning to look much better.

I'm not really satisfied with the reporting aspect. It's not really nice. It's a bunch of data that isn't really organized for reporting. The design just isn't that great. The report should be concise and nicer looking - something you'd be proud to show to third parties. 

I would be happy if I could use the studio and engine side. It has been redesigned. However, if I could use it for two to three months of intensive work, I'd have better relevant feedback. 

I'd also like the capability to double click on the sub-process to access the corresponding tab directly instead of clicking on the right button. There needs to be a shortcut. Maybe there need to be more properties on each activity and each task. 

I've been using the solution for five to six years.

I previously used Visio as well. Currently, in our company, we have a Peoplesoft and Pega system, however, I'm looking to implement Bizagi within the client environment. The Pega system is a bit too big for me. I'd like something that is easy to use.

The initial setup is super easy. It's user-friendly to me. That's why I like Bizagi. The design itself is nice as well. 

I used to be very pleased with the pricing. Now, it's a bit more complicated. I don't remember exactly, however, it might be $10 a month per user. I don't really remember. 

Previously it was super easy to at least use a modular version. I'm not yet using the professional version.

I prefer to have a free solution to start with. 

Bizagi is a great BPM tool, however, I am also interested in looking at Signavio, as there's a GMN inside with decision-making notation. I'm curious about KiSSFLOW as well and KiSSFLOW is really modern. I've never had a chance to use them, however.

I was thinking to get a certification from Bizagi. I actually passed the first level, and have not yet done the ones where you purchase the professional site. I'm not using the professional version. Someone else from my company is studying the other levels on the professional version right now.

I'd rate the solution at a seven out of ten, as I have yet to try Studio and the Engine. 

I'm not a reseller. I'm just a consultant. I'm using some tools. I'm trying lots of tools and out of everything, Bizagi is my favorite right now. However, if there was no more free plan I might have to look for another option. 

We'd be curious to learn how to become partners with Bizagi as we do have clients who want to use it as well. 

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.

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.