What problems is Process Street solving and how is that benefiting you?
Everything with our business, it does it all!
If there was a chatGPT model that could be trained against our process, so then the staff could ask it what process to run based on the tasks they are trying to complete, or it would appear right within zendesk... MG, that would be absolutely amazing! Just imagine finding the perfect process with ease. Though, with all the subprocesses involved, I'd be a bit wary of it trying to launch a subprocess on its own. Nonetheless, we use this incredible tool for everything!
Picture every single aspect of your business seamlessly flowing through this fantastic solution. Customer sign-ups, onboarding, employee onboarding, support tasks, even complex endeavors that require meticulous step-by-step guides. It's like having a Q/A and cross-checking powerhouse at our fingertips. We've gone above and beyond by building custom interfaces to their API and directly integrating it into our zendesk system. As zendesk is used, it automatically launches Process Street, passing along custom variables such as contact names and ticket numbers. This way, all the essential data is readily available when the processes kick off. It's truly impressive to witness how much effort has been poured into this product.
While there haven't been any recent improvements that directly benefit us, out of the box, it has everything you need, except for the lack of subprocesses and process linking. So, I'm marking it as "I don't know" if it's heading in the right direction because I don't want to say "no." I'm genuinely content with the product, but I am disappointed that they haven't recognized the importance of a subprocess library. Truth be told, it's probably not essential unless you dive deep and consolidate all your processes into one. However, once you reach that point, you'll become so hooked and dependent that canceling won't even be an option because our entire company relies on it. Perhaps they know this and that's why they haven't addressed my requests for a subprocess library.
The question of "price" is a tad confusing. Are you inquiring if it's priced high or low? Instead, I would suggest rephrasing it to something like, "On a scale of 1 to 7, with 1 being overpriced and 7 being perfectly priced, how do you rate the current pricing?" Personally, I find the current price to be quite expensive. However, I feel immensely blessed and grateful that, because we supported them from the very beginning, they have honored the processes we signed up for. It brings me great joy to say that Process Street is one of those rare companies that truly value their customers who have been there from the start. Thank you for that! Nevertheless, my suggestion would be to introduce a more comprehensive pricing plan to showcase the awesomeness of this tool. If the cost exceeded $415 a month, I might hesitate as it pushes the limit for me. Any SaaS product that exceeds $300 a month for a small team of fewer than 10 people is a significant ask. Once you cross the $499 mark, things get a bit crazy, and the value needs to be truly outstanding. Considering that it took nearly 12 months for one dedicated employee to create all our processes, paying that amount on top of their salary would be quite the commitment. Personally, I would propose the following pricing structure:
FREE - Builder Plan: This new plan allows you to build everything but not run it, giving you the chance to explore and set everything up. Once you're ready to use it, you can start paying.
$100 - Start-up
$299 - Pro
$499 - Enterprise
In conclusion, Process Street is an exceptional tool that brings immense value to our business. Its comprehensive functionalities and continuous support for early adopters like us make it a standout solution. With some minor improvements, a subprocess library, and a revamped pricing plan, I have no doubt that Process Street will continue to Review collected by and hosted on G2.com.