nickgervasi

"All our team members are certified organic and non-GMO" Love it. Congrats on the launch!

Thanks for sharing your perspective. I can see how per-user pricing doesn't scale well for you.

> What questions do you have? We're curious what specific flows you were interested in migrating over? Who performs this work today? How does it work end-to-end? What tools do you use to track the work? If you prefer to message me privately, my email address is nick <at> flowdash <dot> com.

> I wonder if anyone has experience to make a comparison with more complex BPMN tools like Camunda and Zeebe? Or with Salesforce plugins like Process Builder?

I don't have any personal experience with these tools, but am also curious to hear from the HN community here.

> Can Flowdash handle fan-out/parallel stages for example?

Not at this time, but we're adding new features every week. If you're up for it, I'd love to learn more about your use case and how you're evaluating the different options on the market.

You're right, simple workflows can be wired up with Jira + Zapier. Tools like Jira are great at tracking work, but the work itself generally happens somewhere else. Our vision is for Flowdash to not only be the place work is tracked, but also where it's performed. We make this happen by providing common building blocks like reading from a database or kicking off a document signing flow and allowing teams to configure them to match their workflows.

We see Retool and Flowdash as being pretty different and, in some cases, complementary. Flowdash is focused on the types of internal tools that are about managing repeatable workflows. By choosing this specific use case, we're able to focus on features that operations teams need as they scale: things like task assignment, documentation, analytics, and SLA's.

Thanks for signing up! We tried reaching out but the email bounced. Can you message me directly at nick <at> flowdash <dot> com?

Happy to provide more details. We settled on our current pricing based on conversations with our early customers. For many of them, the alternative was to build something in-house, so they saw our pricing as pretty affordable when compared to the dev cost to build a custom solution.

That being said, we’re pretty early and still iterating on our pricing. If you’re up for it, we’d love to learn more about your use case.

Thanks! I actually hadn't heard of Orchestra before but will definitely check it out. Have you used it in production before? How was your experience?

My name is Nick and I work at ZenPayroll. Sorry for the delay - we'll be starting our multi-state rollout next month for a few states with many more to follow afterwards.