What is our primary use case?
We had a client who wanted to use a BPM to track user subscriptions on their website. They had 20 steps from different areas and different people who wanted to join as new users of their services.
We had to use Camunda BPM to track those services because they used to lose track of some clients in the past. They then had to spend more, add some more steps, and add new user subscriptions for months.
The key here was always to track a new user and guarantee that they will get subscribed to their service in good time.
What is most valuable?
There's this graphic that tells you how many lines or how many tickets are in each step. In that way, you know where you stand. I find this feature very valuable.
These are your bottlenecks, and you can see what the tasks are, the problems, see how much time must be spent on them. Then you can propose to fix it or make some improvements to make things go faster.
What needs improvement?
Documentation can be improved. Right now, the documentation isn't properly organized. We have a lot of documentation. We follow the instructions. We follow some blogs and videos on YouTube. But it doesn't feel like we have all the information we need to implement Camunda BPM.
For how long have I used the solution?
I have been using Camunda BPM for two years.
What do I think about the stability of the solution?
Camunda BPM is a stable solution.
What do I think about the scalability of the solution?
Camunda BPM is a scalable solution. It's a JAVA-based application, and we were able to install it in AWS and do all the things we wanted to do.
How was the initial setup?
The initial setup was complex. We really needed to study and understand how it worked. It was difficult because we didn't have enough information in the manuals.
We did what was said in the manual and then wanted to do more. We watched several videos, and we started to connect the dots. With our own solutions or conclusions, we were able to implement Camunda BPM.
What about the implementation team?
We implemented Camunda BPM by ourselves, in-house.
What's my experience with pricing, setup cost, and licensing?
I think Camunda BPM can improve their licensing costs. It isn't easy to find clients with Camunda BPM licenses mainly because it's quite expensive. I think the license for an on-premise system is about $50,000, and that's expensive when you have only 100 users.
Which other solutions did I evaluate?
I used Bizagi before. It's easier to implement, but the problem is that you have to use their suite. You have to use their screen, their admin screens, or user screens. The UX and UI experience is also not good.
We decided to go with Camunda BPM because it gave us what we needed. That is, we can get inside Camunda and use only the tracker of the application. We don't need to use mandatory things like your pages or your web forms.
We can really code what we want and use it. We can create our own UI while using Camunda BPM at the same time. We really liked that because in my company specifically, we use a lot of UX, so all the UIs were very important for us.
Camunda BPM allows us to have a BPM bot with our own UI, and that's what we liked most about Camunda.
What other advice do I have?
I would advise potential Camunda BPM customers to be patient. Perhaps all the information isn't available in one click, but it's possible to implement Camunda BPM, and it's quite flexible. It's worth a try.
On a scale from one to ten, I would give Camunda BPM an eight.
Which deployment model are you using for this solution?