IBM Business Automation Workflow is a solution that helps users automate digital workflows to increase productivity, efficiency and insights — on premises or on cloud.
N/A
Pipefy
Score 7.5 out of 10
N/A
Pipefy headquartered in San Francisco offers their process management and workflow software providing processes for customer success, service desk, sales operations, and other processes.
$22
per user, per month*
Pricing
IBM Business Automation Workflow
Pipefy
Editions & Modules
No answers on this topic
Business
$22
per user, per month*
Enterprise
$36
per user, per month*
Unlimited
Custom
Starter
Free
Offerings
Pricing Offerings
IBM Business Automation Workflow
Pipefy
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
*Discounts available for annual billing.
More Pricing Information
Community Pulse
IBM Business Automation Workflow
Pipefy
Considered Both Products
IBM Business Automation Workflow
Verified User
Anonymous
Chose IBM Business Automation Workflow
IBM BPM makes development easier, which is faster when compared to the others. IBM's customer support is good. Easy for the user to learn while providing powerful integration. More secure when compared to others. It provides the reusability of components. Monitoring and report …
BPM was purchased together with other products from IBM's InfoSphere and WebSphere offerings before I came here. I have personally worked with alternatives at a previous jobs. I have developed workflows using SharePoint. I have developed workflows using Documentum's workflow …
Pega Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product. However Pega, falls short on integration centric capabilities and very rigid to customize. …
Pipefy
Verified User
Anonymous
Chose Pipefy
We started using software we already had (such as Slack and Sheets) but this software is not actually ideal to manage processes, which led to errors, miscommunication, and execution problems. Trello is good for managing demand but offers no process customization or approval and …
Trello is a much simpler tool in general ways, it does not provide nearly 1/100 of the customization from papery. Also, Trello seems to be stuck in the past, the design never got refreshed, and on Pipefy, they are constantly keeping up the design fresh and beautiful.
Pipefy was suggested by our new developer and we switched from Freshdesk. It was a lot better looking and easy to navigate. We used Google Forms at first but that isn't really what you should be using to keep track of bugs. Freshdesk focused more on the outside of the …
Pipefy is very process-oriented and not task or project-oriented. Other tools might offer different views such as the Gantt chart that makes a lot of sense if the project you are working on requires it. But Pipefy is better when the complexity of the process demands automation …
Pipefy is very well suited if you have a team doing any sort of process... for real! It simplified everything from our sales and marketing objectives/processes, to our onboarding and accounting side of things. Since you can share different pipes with others, it's easy to see where others are at in the process and move the card along while keeping others informed. It makes sure you don't miss any information or steps along the way, which is great if your process is detail-oriented. It is a little less appropriate for marketing efforts, but we still try to use it to keep track of things in a central space. Definitely best suited for sales, technical things, and accounting.
Installation is (typically) a bit painful out of the box and requires expert help.
Following installation, initial projects require outside consulting expertise to be successful. Projects without importing BPM expertise tend to have much higher failure rates. Though individually the technologies involved are widely available and not complicated, combined and collectively BPM solutions require a flexible, creative, technical talent to help deliver. It takes time to learn the judgment and craft required.
The out-of-the-box UI controls (widgets) are not terribly inspiring- on desktop or mobile. Use of third party toolkits (e.g. Brazos) is recommended. Silver lining: those third party toolkits are quite good.
This particular decision will be made by other people. Overall IBM BPM is the best BPM engine that I have worked with. It is implemented at our company and IT and business are already somewhat familiar with it. Therefore if asked I will recommend renewal as long as the price is reasonable.
Building complex UIs can be cumbersome. Calling complex SOA services that have a lot of objects, types, anyType attributes, recursive object references, etc can be cumbersome. The Process Designer IDE communicates with the server side Process Center a lot and as a result it is pretty slow. The IDE is also Eclipse based which doesn't make it faster.
Issues can be raised through tickets and it works based on the priority of the issue. The Support Team response is also good and the solution is provided in a short span of time. In a case where the issue is serious, they try to find out the root cause and provide an alternative for it.
Pipefy support is pretty good. There were a few instances where the agent didn't really understand what I was trying to get help with, but that was only once. Every other time it has been pretty fast and efficient. They are also very kind and understanding. I don't think they need much help in that dept
• Attended on premise sysadmin training for 4 days, 8 hours per day. Although further follow-up training was available, I never felt the need to go back. Training was very hands-on with real modeling (rather than just following a manual). Very effective.
• Very satisfied – not too difficult at all. • We had a consultant available as part of our contract, but we didn’t really need to use (except for some advice on ActiveDirectory and single sign-on)
Pega Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product. However Pega, falls short on integration centric capabilities and very rigid to customize. On the other hand IBM comes with array of products which suits needs of varying degree. Advanced integration is solved by BPEL Process Server which has support for state based patterns and mediation. Dynamic rules and event management can be solved with WODM, Cloud to on-premise connectivity with Cast Iron, Enterprise gateway and security usecases with DataPower, Social BPM with IBM BPM , WODM, mobify with Worklight. Pega has a little bit of eveything here and there. It solves the dynamic rule management, brings out the flavor of Social BPM and mobility with Antenna ( I guess) and predictive analytics as well in one single suite. There are certain usecases which needs to have a little bit of everything, however this little bits and pieces of functionality when its blows, Pega would have problems to scale. With IBM its a bit nightmare to maintain a variety of technologies, however you can wish to go for one without the other and go for something only when you truly need it. Pega vs IBM Its difficult to pick a winner. In nutshell when you want a full scale BPM with rich integration capabilities go for IBM BPM. On the other hand if you hava mature integration capability already, Pega can yield quick results for you as well. Pega's strength is its methodology. IBM BPM's strength is integration. Actually you can't go wrong with both in terms of implementation. My strong recommendation is to invest time to process analysis and pick a good vendor to support consulting and implementation.
We started using software we already had (such as Slack and Sheets) but this software is not actually ideal to manage processes, which led to errors, miscommunication, and execution problems. Trello is good for managing demand but offers no process customization or approval and Jira is too focused on development for our needs, and also hard to customize.
It scales from small team interactions to business processes serving thousands of employees, as well as straight-through-processing needs that go well beyond. Of course, scale is always in the eye of the beholder, but IBM BPM does a good job of giving you all of the hooks, APIs, and data that you need to take on whatever scaling approaches you need to meet the load
Easier to implement and does not take much effort to work on it.
Versioning made easy. We can even degrade to the previous version in case of any issue, which is not easier to do in other BPM suites, thereby, saving a good amount of time.
Helped in achieving client requirements faster, which results in a higher return of investment.