OpenText acquired BPM solution Metastorm in 2011, and has rebranded the product as OpenText MBPM. It is an alternative BPM solution to OpenText's primary BPM offering called OpenText Cordys Business Process Management.
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 month
Pricing
OpenText MBPM
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
OpenText MBPM
Pipefy
Free Trial
No
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
OpenText MBPM
Pipefy
Features
OpenText MBPM
Pipefy
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
OpenText MBPM
7.0
3 Ratings
11% below category average
Pipefy
-
Ratings
Dashboards
7.93 Ratings
00 Ratings
Standard reports
9.02 Ratings
00 Ratings
Custom reports
4.03 Ratings
00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
OpenText MBPM
7.3
3 Ratings
13% below category average
Pipefy
-
Ratings
Process designer
8.13 Ratings
00 Ratings
Process simulation
7.13 Ratings
00 Ratings
Business rules engine
9.02 Ratings
00 Ratings
SOA support
6.02 Ratings
00 Ratings
Process player
7.02 Ratings
00 Ratings
Support for modeling languages
8.02 Ratings
00 Ratings
Form builder
6.93 Ratings
00 Ratings
Model execution
6.13 Ratings
00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
OpenText MBPM
7.6
3 Ratings
9% below category average
Pipefy
-
Ratings
Social collaboration tools
7.63 Ratings
00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
Metastorm is well-suited for scenarios in which internal stress testing an application is needed in a hurry before showcasing it to potential customers. It supports different views of the process from Swimlane perspective, so different methodologies can be handled. It is an Enterprise level tool and handles both small and large projects quite well, although smaller companies may be stressed out by the amount of time it takes to properly maintain the application.
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.
The Metastorm process engine is based on an older version of .NET. Updating to a newer version would resolve several known issues with .NET email functionality.
Metastorm builds web pages at run time. While the UI presented to the end user is fine, the Document Object Model is convoluted and subject to change with new releases. Providing a more simplified DOM or at very least a custom function to replace document.getElementById() would make client-side scripting a much more powerful tool.
One function that I've seen Metastorm competitors do well, is email wizards. Having a WYSIWYG email editor would be really nice.
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
We found that OpenText MBPM held its own quite well against IBM BPM. We ended up choosing OpenText MBPM due to the analytics, complex routing, and the ease of SOA service integration. Furthermore, the ability to quickly develop simple User interfaces make this tool a daily component of our most-used toolbox components.
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.
Our processes are more organized and we are not missing any steps.
We are able to touch base with customers easier since we have all potential/missed clients in one pipe, with automated alerts (i.e. it has been 60 days since contact with this customer).
We are able to keep track of customer billing changes easier.