Every fast-growing CS team eventually builds a playbook, and every playbook eventually meets a customer it wasn't written for. The tension between running a repeatable process and staying flexible enough to actually serve the account in front of you only gets sharper as headcount grows. This session brings together CS leaders working through where standardization genuinely helps a team scale, and where it quietly starts working against the outcomes it was meant to protect, covering how they decide what belongs in a playbook, what should stay a judgment call, and how to keep both from collapsing into either chaos or box-ticking. What this session will cover: - Where standardized playbooks help a growing team and where they start to hurt - How to decide what should be documented process versus CSM judgment - How to keep consistency from turning into box-ticking that customers can feel - What signals suggest a playbook needs revisiting rather than reinforcing

Customer success hears what customers need before anyone else does. Getting the rest of the company to act on it is the hard part. Feature requests pile up in spreadsheets, product teams push back on anecdotes, and customers stop sharing when nothing changes. How does a CS leader turn what the team hears every day into decisions product and leadership actually make? This session looks at how customer success can build the relationships, rituals and evidence that give it real influence over product and company priorities. Through practical examples of what earns trust across functions and what falls flat, attendees will see how to turn customer insight into action and keep customers in the loop once their feedback lands. Key takeaways: → How to turn scattered customer feedback into evidence product teams will act on → Which cross-functional rituals give CS lasting influence, not one-off wins → How to close the loop with customers so they keep sharing what they need