I work at LittleHorse, though I'd been on the other side of this problem: owning services coordinating complex business flows that nobody could see end to end. We'd sometimes get questions like "why hasn't this account been activated yet?" and the honest answer was "give me a couple hours to track down and check the logs of each service involved."

The pitch that landed for me wasn't durability, it was the process itself becoming a first-class object: versioned, typed, and navigable. Something you can put in front of a non-engineer and they'll actually understand it. With Business-as-Code you can now see and own the entire process end to end.