The signs
- The monthly bill grows with task count faster than the business does.
- Automations chain into each other, so one failure breaks several processes.
- Nobody can say quickly what ran overnight and what failed.
- Important business rules live in a tool your team cannot test or version.
What the tax looks like
It shows up as middleware subscriptions, an automation bill that grows with task count, and a person whose morning starts by checking the sync. Every connector is also a promise to keep up with somebody else's API: Asisly, our own voice receptionist, reaches eighteen third-party connectors, and keeping them working is continuous work.
You do not have to rip it all out
On our own Growth Engine, the application kept the state and the workflow engine was demoted to a stateless task runner called by webhook — cheap tooling doing what it is good at, with the state living where it is owned. Business OS runs a self-hosted estate of 117 workflows on the same idea.
Where to start
Move the automations that hold state or move money first; leave the simple notifications where they are. The full guide covers the build-versus-buy arithmetic.