Series #2 Founder OS: Automate with Claude, Lead with Trust

Luma Event Page — Combined Session TITLE Founder OS: Build with Claude AI. Lead Without Burning Out. You saw what Claude can do. Now it's time to build the system and prepare the team. This session has two parts. The first is hands-on: you'll open Claude and build the infrastructure that makes it work like a Chief of Staff, not a chatbot. The second addresses what most AI rollouts skip entirely: the human side. How your team receives this shift, whether they trust it, and whether your culture is set up for adoption that actually sticks. The tool works. The question is whether your organization is ready to use it well. Part 1: Build Your Founder OS in Claude (90 min) Led by Pooja Kalita Load your company context into Claude once so it applies to every output automaticallySet up your voice and communication style so Claude never needs to be told againConnect your calendar, email, and design toolsBuild daily commands that take 30 seconds and replace 30 minutes of context-switchingCreate a system that gets sharper every week because it learns as you goEvery 15 minutes, Pooja pauses, shows what good looks like, answers questions, and troubleshoots live. You leave with something that works, not a draft you'll finish later. Part 2: Trust before tools: Building the culture that makes AI adoption stick (90 min)Led by Uma Uppin, Founder of Tathya.ai Your team already knows AI is coming. What they don't know is whether it's coming for them. That uncertainty lives in the body before it shows up in behavior. It surfaces as quiet resistance, slow adoption, people nodding in meetings and then doing things the old way. This session is about how to work with your team to understand what is showing up for them, and then address it. Values at the core: AI adoption reveals what your culture actually is, not what you say it is. We'll identify your core values and pressure-test whether your team experiences them in daily operations. Psychological safety and threat response: Change activates the nervous system. We'll cover how to recognize when your team is protecting rather than adapting, and how to lead through transitions without triggering resistance. Redefining roles: AI shifts what people do. We'll walk through how to have honest conversations about changing responsibilities in a way that builds trust rather than eroding it. From founder values to team culture: We'll tie the threads above together with how you talk about AI, how you introduce it, whether you use it yourself first. All of this signals what the team should believe. We'll look at how your own relationship with AI shapes the culture your team adopts. You'll put this into practice before you leave, by setting up the pilot on yourself first. A practical playbook: You'll leave with a step-by-step framework for introducing AI tools to your team grounded in your values and designed for real adoption. The first step is the capacity pilot below. The two-week capacity pilot: The playbook starts with knowing what your team is actually carrying, so you set up the pilot MVP for yourself live in the session. You audit two things: where your time goes, and where your energy goes. Time shows you the hours. Energy shows you the truth.You run it on yourself first, then take it to your team. Over two weeks you build a real capacity map together.The map shows you where to act: which work drains them, which work they guard because it matters, and where AI can lift the load instead of adding one more thing to learn.That baseline is why adoption sticks. Your team can feel you built it around their lived capacity rather than around a demo. WHAT YOU'LL WALK AWAY WITH A working Claude OS built on your real company context, ready to use tomorrow morning Your voice, calendar, email, and design tools connected and running Daily commands that replace hours of context-switching each week A values-based framework for introducing AI to your team Language and sequencing for role conversations that…