Live data from Hacker News

Show HN: Document and automate your operations playbooks and business processes

workflow86.com

21–30 of 45 posts

Re: Show HN: Document and automate your operations playbooks and business processes

#21

Super excited to try this out. I've been hoping for a tool in this space for awhile.

Shoot us a message if we can help in any way! Happy to build out a sample workflow or proof of concept, all we need is a description of what is involved in a process of your choice.

Re: Show HN: Document and automate your operations playbooks and business processes

#23

I couldn't tell from an initial review of the feature set, but does this product incorporate any sort of digital signature / approval process? And I don't mean integration with DocuSign or similar, but something built in (and legally compliant). This feature alone has been a pain point for me for years when it comes to document flow and approvals, usually because of exorbitant pricing for per-user signing. Contract d…

I agree, the first thing I looked for in the docs was authorisation controls/checkpoints. I need a trail of approvals and review checkpoints. This is far more important than integrations, etc. Also, Business processes are not static. I would like to understand how changes in process are managed.

"the first thing I looked for in the docs was authorisation controls/checkpoints."

We've got a component called the Assign Task that was pretty much built for this - its pretty flexible, but it is mainly used to create authorisation/control/approval/decision points in a workflow.

Here's an example for a process to handle timesheets: https://app.workflow86.com/template/812aaa61-8e00-414d-9898-...

The Assign Task component acts as a step where you can accept or reject the timesheet that has been submitted.

The Assign Task component is probably our most popular component and I'd be happy to show how you can use it for controls/checkpoints in your use case.

"Business processes are not static. I would like to understand how changes in process are managed."

All workflows are version controlled. This means that when a workflow starts, it is attached to a particular version e.g. version 5. This means if you make changes to the workflow i.e. update to version 6, the workflow currently in progress remains at version 5 so nothing breaks. We are looking into the possibility of migrating in progress sessions from one version to another.

Re: Show HN: Document and automate your operations playbooks and business processes

#24
post #19

Looks great! Out of curiosity, how do you plan to compete with & distinguish yourself from well-funded players in the space like Integromat[1] etc? [1] https://www.integromat.com

Right now our main point of difference is consolidation. We allow users to build and manage more of their workflow with just one platform vs duct-taping together 6 different SaaS tools like you would in Integromat. Our thesis is that it is easier to build, run and maintain more complex workflows when as much of its functionality as possible is managed natively in one place.

Thanks for the reply! My experience is that the sad reality of most large businesses is a vast landscape of systems introduced over decades and glueing them together with some RPA tool is a necessary evil if you want to achieve some level of automation.

You sound like you’re targeting smaller businesses with less complex processes that might not be fully established in existing systems. I can definitely see the niche there. Best of luck to you!

Re: Show HN: Document and automate your operations playbooks and business processes

#26

Interesting choice of IF ... THEN ... ELSE ... for non-coders. I would have thought IF X ... OTHERWISE ... would have been a clearer choice in context coming from many human languages.

We've actually had this exact discussion - based on feedback, we might switch over from "else then" to "otherwise" very soon.

Re: Show HN: Document and automate your operations playbooks and business processes

#27
post #19

Earlier quoted context omitted.

Right now our main point of difference is consolidation. We allow users to build and manage more of their workflow with just one platform vs duct-taping together 6 different SaaS tools like you would in Integromat. Our thesis is that it is easier to build, run and maintain more complex workflows when as much of its functionality as possible is managed natively in one place.

Thanks for the reply! My experience is that the sad reality of most large businesses is a vast landscape of systems introduced over decades and glueing them together with some RPA tool is a necessary evil if you want to achieve some level of automation. You sound like you’re targeting smaller businesses with less complex processes that might not be fully established in existing systems. I can definitely see the niche…

Yes, large and established enterprise is a tough one to crack. As a consultant, I've seen teams still running Lotus Notes (!).

Re: Show HN: Document and automate your operations playbooks and business processes

#28
post #22

I like the idea of having humans within the flow, getting emailed, completing tasks and marking them complete. What other products are there in this space?

A few others in this space include Process Street and Piepfy. I am biased, but I do think we have them beat for functionality and pricing though. Give them a go, give us a go, let us know what you think!

Re: Show HN: Document and automate your operations playbooks and business processes

#29
post #22

I like the idea of having humans within the flow, getting emailed, completing tasks and marking them complete. What other products are there in this space?

Lotus Notes.. :-)

Seriously though, visual coding/drag and drop etc are great for non-technical users but in my experience the issue isn't code vs. icons. I worked in corporate workflow development for around 15 years using guess what, Lotus Notes, and the 'real' problem was getting end users to think programmatically, not remember syntax / tools. You can have all the easy to use tools in the world, but you still need to really be able to think through a process.

Re: Show HN: Document and automate your operations playbooks and business processes

#30
post #22

I like the idea of having humans within the flow, getting emailed, completing tasks and marking them complete. What other products are there in this space?

Lotus Notes.. :-) Seriously though, visual coding/drag and drop etc are great for non-technical users but in my experience the issue isn't code vs. icons. I worked in corporate workflow development for around 15 years using guess what, Lotus Notes, and the 'real' problem was getting end users to think programmatically, not remember syntax / tools. You can have all the easy to use tools in the world, but you still nee…

100% agree, there is a certain mindset required to go from "stuff I do everyday" into a structured process. We've found it sometimes takes a bit of pre-work, like mapping the basic process on paper or a whiteboard, to smooth the transition.

And I have come across many a Big 4 consulting team still running on Lotus Notes :)

Post reply on HN