An operator's view of personal tools, central systems and the line between them: Every CS leader is being told their team should be AI-native. Few agree on what that looks like day to day: which tools people should build for themselves, which ones need to be owned centrally, how much access to give, and how to keep one source of truth when everyone can build. This talk comes from building a customer success team from scratch, where every person has the access and the tools to build what they need. It's an operator's view of what holds up once the novelty wears off and the real work starts. We'll look at what people build for themselves, and why personal tools spread fastest. We'll cover what we deliberately run centrally with RevOps, where we draw the line between the two, and why it points to a headless CRM: one governed system of record and centralized processes, with screens each team can shape for itself. Then we'll get to what it changed for the team: less time on admin, more on the hard work of helping customers get value and grow. You'll leave with real examples, a simple test for who builds what, and a few starting points to try with your own team this week.