How do bigger teams manage Clay knowledge and access without duplicating work?

Hi all, Peter here from Pleo.io 🙌 We are having our kick-off today with Stefan K. and Jess B., and can't wait to get started! It's been a long journey to get here, but I am confident in the results! 🌎 Location: Vaasa, Finland (100% remote 🙌) 👩🏻‍🎨 Company / Role: Pleo.io, a Danish fintech scaleup, and myself and the team I am part of are trying to build the best tech stack possible. 🔍 Background: 20 odd years in customer facing roles, from tech support to building my own global Customer Success team, moved into RevOps 4 years ago, with Customer Success consulting on the side Clay Goals: Low level of familiarity (for now) and my goal is to open up our TAM for sales scaling 🌟 Fun Facts: Born in the Netherlands, with a Danish mother, and after 20ish years in Copenhagen, now living in Finland for 7 years with a Finnish spouse (from the Swedish speaking minority) and daughter, mixing up Danish, Swedish, English, and a whole lot more 🔥 Burning question: with bigger teams, how to you manage knowledge/access and not f**cking up or duplicating other people's work? I have mainly seen one man bands managing Clay, so I would love to learn from other setups!