{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Agentic Allocator","title":"The CIO Who Codes: Al Hemmingsen on Weaving AI Into the Fabric of a Multi-Generational Single Family Office","html":"","width":"100%","height":180,"duration":1565,"description":"Al Hemmingsen, CIO of a prominent US-based single family office, joins The Agentic Allocator to share what hands-on AI adoption looks like from inside an institutional family office. Al is the only CIO, we know of, in the LP world actively publishing open-source code on GitHub for use by fellow allocators.In this episode, Al walks through how vibe coding with Claude Code became a serious tool for unlocking legacy data and automating workflows, how he is building a culture of accountability across his team, and why the LP that gets to the best GPs first has a competitive edge that only widens over time.He also makes one of the sharpest points we have heard on the competitive stakes: some aspects of this work should be shared freely with peers, but the ability to process information faster than other LPs, build higher-quality manager meeting lists, and get to the best GPs before they fill their calendars at conferences, is a genuine edge. If you do not build it, someone else will.What You'll Learn:How a background in SQL and Visual Basic at business school laid the foundation for a career of hobbyist coding and eventually full vibe coding with Claude CodeWhy the single best measure of AI ROI at a family office is not efficiency gains but tasks that were previously too expensive or simply not feasibleHow $59.32 in API credits unlocked 50-plus years of legacy transaction data and saved $10,000 a year in perpetuity, in one afternoonHow Al thinks about the boundary between enterprise systems of record and the custom scripts that live in between themThe psychological dimension of AI adoption: how to take existential fear off the table so your team can actually engage with the technologyThe autopilot accountability principle: why the person who creates an AI tool is always responsible for what it does, regardless of what the machine decidedHow a standing Monday meeting agenda item and a shared Microsoft environment for corporate-owned apps is building a firm-wide culture...","thumbnail_url":"https://img.transistorcdn.com/QigjduDJIqFTeeJFynBiyzGolv4eHG5zocOf8vY173o/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9hZGY5/NTNkMjIzZGE0NWFj/YWEzYzY0ODU1ZTYx/NzE2Zi5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}