So, when's a good time to bring in Saga patterns for your microservices setup?

Hey everyone, I've been struggling with how to handle transactions over a bunch of services, particularly as our system gets bigger. We have situations where one user action starts updates in three or four microservices. Right now, we're kind of just doing our best, with some manual ways to undo things if they go wrong, and that's just not good enough. So, I'm wondering if and when others have found it helpful to bring in Saga patterns, like Choreography or Orchestration, for these distributed transactions. What made you decide it was time to put a Saga in place? Did you begin with something simpler and then change it later, or did you plan for Sagas from the start for really important stuff? I'm eager to hear about what people have actually done and the give-and-take involved.