Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How is this different than workflow automation (for non-developers) solutions? Or is the takeaway that any workflow automation is ripe for unbundling?


Ding ding ding.

This is what needs to happen.

To provide one painful example that I'm currently dealing with, at work we have a Marketing Automation platform, a CRM and a CX tool. Marketing use the MAP, sales use the CRM and customer success the CXM.

All 3 have their own data schemas, their own "customer view", their own segmentation tools, they own orchestration (workflows) tool, etc. Everything exists in a silo, and no one can see the big picture.

This area absolutely needs disruption, we're starting to see some of it at the MAP level with MessageGears, Vero and Supergrain but it's yet to feed through to those other customer facing functions as far as I've been able to see.


I think it's two things

Is the workflow automation tool big enough that subgroups of users are still a big number of users to service

Of those subgroups, does one (or more) stand to have a better product experience if someone focused on their core use-cases / workflows. (e.g. Reclaim takes a bunch of calendar automation around scheduling and makes a product that reduces the work needed to optimize your calendar).




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: