[swatcoder]

If you're modeling one workflow for one team at one organization, it's always been trivial. Same as making an issue tracker.

The complexity arrives when you need to support complex and branching workflows, teams that model things subtly differently, organizations that model things radically differently, strongly opinionated stakeholders at key teams/clients, endless demands to integrate with external systems, etc

[danielmarkbruce]

Right - for most companies, they are one org. The complexity of "product CRMs" as opposed to "roll your own CRM" seems to come from trying to satisfy mulitple orgs. A CRM that can satisfy two orgs seems about 10x more complex than a CRM that can satisfy one.

LLMs might tip the calculation of buy v build enough that "roll your own" becomes the standard for most business apps.