Podcasts about ctos

What does it really take to build an AI-ready enterprise when your data is fragmented, teams operate in silos, and years of technology decisions have created complexity that no large language model can magically fix? In this episode of Tech Talks Daily, I speak with Raymon Ohmori, Senior Principal Software Engineer at Valiantys, and Jiecheng Dong, Senior Software Engineer at Valiantys, about the work that goes into enterprise AI adoption and why successful AI transformation begins long before companies deploy agents, copilots, or autonomous workflows. Using Valiantys' work with Mercedes as a case study, Raymon and Jiecheng explain how modernizing software delivery and connecting data across teams can create the foundation required for AI systems to deliver meaningful business value. We discuss why fragmented data, organizational silos, poor governance, and unclear business problems continue to prevent many companies from moving beyond AI pilots. The conversation examines what it means to become AI-ready in practice. Jiecheng explains why enterprises need performant, structured, and queryable data rather than simply feeding huge volumes of information into large language models. Raymon shares why businesses must begin with real problems, stakeholder needs, and clearly defined outcomes to justify the cost of AI and successfully move projects into production. We also discuss the growing role of agentic AI and autonomous workflows in software engineering. How should engineering teams prepare AI agents to become active participants in software development? What tools, context, permissions, governance, and observability do these systems need to operate effectively? And why might treating an AI agent more like a new colleague than another software tool help teams think differently about deployment? Raymon and Jiecheng also share their perspectives on AI-assisted software development and developer productivity. As AI becomes increasingly capable of writing code, the role of the software engineer is shifting toward architecture, system design, requirements gathering, trade-off evaluation, and translating business needs into technical specifications. We also discuss the challenge facing junior developers and why companies still need to create pathways for new engineering talent. Finally, we examine the practical steps CIOs, CTOs, and engineering leaders can take today to build more connected, AI-enabled enterprises. From improving data ownership and governance to identifying costly problems that AI can realistically solve, this conversation offers a practical guide for companies trying to move from AI experimentation to production systems that deliver measurable value. Where is your company on its AI journey? Are fragmented data, organizational silos, and unclear business problems preventing your AI projects from reaching production, or have you found effective ways to turn experimentation into measurable results? Share your thoughts with me.   Useful Links   Valiantys Website: https://www.valiantys.com/  Valiantys LinkedIn: https://www.linkedin.com/company/valiantys/    

https://clearmeasure.com/developers/forums/ Michael Nygard advises consulting firms, private equity teams, CTOs, CEOs, and boards when they require senior technology judgment for limited-term, high-impact situations — including architecture assessment, platform rescue, cloud and data cost intervention, AI engineering enablement, technical diligence, divestiture and carve-out architecture, and operating-model redesign. Over a 35-year career, he has worked at the seam where people, processes, organizations, and the systems they build intersect. Most organizations treat those as separate problems. The hardest failures, and the most consequential wins, live precisely where they interact. That through-line is what Release It! is fundamentally about. The vocabulary it introduced — circuit breakers, bulkheads, stability patterns — is now standard in how the industry discusses reliability, and the book is widely cited as foundational to DevOps and cloud-native practice. At Nubank, he led the Data Business Unit with over $300 million in annual spend, then served as Chief Architect with reach across 2,500 engineers while the customer base grew from 75 million to 125 million across Brazil, Mexico, and Colombia. Results included cutting data-platform spend roughly 50% year-over-year, improving on-time data availability past 99%, building governance aligned with LGPD, GDPR, and CCPA, moving team engagement from the bottom decile to the 60th percentile, and rolling out AI coding tools to more than 90% of engineers without customer-visible quality regression. At Sabre, as part of the CTO office, he helped lead development-practice modernization, GCP migration strategy, mainframe offload architecture, technical diligence, and divestiture architecture across thousands of applications and hundreds of products. He is most effective when the stakes are real, the system is sociotechnical, and the solution must hold across architecture, execution, economics, and organizational behavior. LinkedIn: https://www.linkedin.com/in/mtnygard/ Personal Blog & Website: https://www.michaelnygard.com GitHub: https://github.com/mtnygard Twitter/X: https://x.com/mtnygard Release It! (Pragmatic Programmers): https://pragprog.com/titles/mnee2/release-it-second-edition/ 97 Things Every Software Architect Should Know (O'Reilly): https://www.oreilly.com/library/view/97-things-every/9780596800611/ Goodreads Author Page: https://www.goodreads.com/author/show/6089.Michael_T_Nygard LinkedIn Articles: https://www.linkedin.com/today/author/mtnygard Presentations Archive: https://github.com/mtnygard/presentations/wiki Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Why do AI agents and applications look impressive in demos but struggle when companies try to deploy them in production? In this episode of Tech Talks Daily, I speak with Nikunj Bajaj, co-founder and CEO of TrueFoundry, about why enterprise AI has become a systems problem, what companies need to move AI from proof of concept to production, and how better infrastructure can improve reliability, governance, security, observability, and cost control. Before founding TrueFoundry, Nikunj worked at Meta on conversational AI systems serving more than a billion users and contributed to the company's internal machine learning platforms. He explains how developers at Meta could concentrate on solving business problems while infrastructure handled logging, monitoring, deployment, and governance by default. In many enterprises, the same journey from an AI idea to a production application can still take weeks or months. Nikunj argues that increasingly capable AI models are not necessarily the biggest barrier to enterprise adoption. The harder challenge is building reliable systems around them. Companies need to know what happens when a model becomes unavailable, how an agent is behaving, which data it can access, how much it is costing, when a human should intervene, and whether there is a kill switch when something goes wrong. We discuss why AI proofs of concept often fail when exposed to real users. Controlled demonstrations rarely reproduce production conditions such as unexpected prompts, malicious actors, heavy workloads, model outages, latency, and dependencies between multiple components. Even when individual parts of a system perform reliably, combining them can create failure rates that businesses cannot accept for mission-critical workflows. The conversation also examines the infrastructure required as companies introduce multiple AI models and agents. Nikunj explains the roles of model gateways, MCP gateways, and agent gateways, and how bringing these components together through an AI gateway can give enterprises a control plane for observing and governing AI traffic. Cost is another major challenge. Nikunj explains why sending every request to the most powerful model can waste significant amounts of money when smaller or cheaper models could produce comparable results for simpler tasks. Intelligent model routing can help companies balance quality, latency, availability, and price. He shares how organizations using this approach have reduced model costs by as much as 75 to 80 percent in some production environments. We also discuss what reliable multi-agent systems require in practice. Companies need clearly defined boundaries for what agents can do, escalation routes to other agents or people, safeguards against infinite agent loops, and complete audit trails of interactions and decisions. For CIOs, CTOs, AI engineering teams, platform leaders, and companies trying to move generative AI and agentic AI into production, this conversation provides a practical guide to the infrastructure decisions that determine whether AI applications remain impressive prototypes or become reliable business systems. The next stage of enterprise AI will not be defined by models alone. Companies that can connect, observe, govern, secure, and control their AI applications while managing costs will be better positioned to turn experimentation into dependable production systems.

In this episode of Shift AI, Jared Wray, CEO and co-founder of Hyphen, joins host Boaz Ashkenazy for a wide-ranging conversation on how AI is poised to eliminate the complexity of cloud infrastructure and the DevOps role entirely.Jared shares his unconventional career journey from growing up in a small town in Idaho, where technology barely existed, to washing dishes at 15, teaching himself programming at the local ISP, and eventually founding five startups across cloud computing, energy tech, and developer infrastructure. From bootstrapping Tier 3 (acquired by CenturyLink) to co-founding Palmetto, now one of the largest energy lenders in the nation, Jared's path has been defined by a passion for solving infrastructure problems.The conversation dives deep into why DevOps has become painfully complex, with developers needing to glue together seven to thirteen different services just to deploy a single application across providers like AWS, Google Cloud, and Cloudflare. Jared explains how Hyphen is using AI to abstract away this complexity by asking developers only for business rules like uptime requirements and performance needs, then letting the AI determine the right architecture, deploy it, and operate it autonomously.Boaz and Jared explore why tools like Claude Code and other coding agents still cannot handle the full deployment lifecycle, what it would look like if AI agents replaced PagerDuty by calling you during an outage with a diagnosis and recommendation, and why the future of infrastructure is an autonomous cloud where humans are decision makers and agents handle everything else. The episode closes with a forward-looking discussion on agent-only companies, the death of cloud certifications, and why Jared believes DevOps was a good idea that we ran too long.This episode is essential listening for CTOs, platform engineers, and startup founders who want to understand how AI is moving beyond writing code to fundamentally transforming how software is deployed, operated, and scaled.Chapters[00:00] From Pocatello to Five Startups: Jared's Career Journey[02:49] Building Fonz, Co-founding Palmetto, and Finding Passion in Infrastructure[06:05] Why AI Led Jared Back to Infrastructure with Hyphen[07:05] First Job as a Dishwasher and Breaking Into Tech[08:46] What Is DevOps and Why Does It Exist[10:49] Why Cloud Infrastructure Has Become So Painfully Complex[12:36] How AI Can Apply Best Practices Without Reinventing the Wheel[14:35] The Hyphen Developer Experience: Business Rules Over Architecture[17:14] Why Claude Code and Coding Agents Cannot Solve Infrastructure Yet[20:26] The Full Context Problem: Operating Across Multiple Cloud Providers[23:07] Autonomous Cloud: When Agents Talk to Agents[24:17] Replacing PagerDuty: AI Agents That Call You During Outages[28:47] March Madness, Live Streaming, and Why Five Minutes Feels Like a Lifetime[30:59] Two Words for the Future of Work: Autonomous Cloud[33:20] Agent-Only Companies and Why Humans Will Be CEOs[35:12] DevOps Was a Good Idea We Ran Too Long[35:41] What Is Next for HyphenConnect with Jared WrayLinkedIn: https://www.linkedin.com/in/jaredwray/Email: jw@hyphen.aiConnect with Boaz AshkenazyLinkedIn: https://www.linkedin.com/in/boazashkenazy/Email: info@shiftai.fm

Why are companies investing heavily in AI, analytics, and data platforms while business leaders still struggle to see what is happening across their operations quickly enough to make confident decisions? In this episode of Tech Talks Daily, I speak with Massimo Merlo, Vice President for UK, Iberia, and Italy at Elastic, about why the next stage of enterprise AI adoption will depend less on who deploys the most advanced models and more on which companies can give people and AI systems access to relevant, trusted, and secure information when decisions need to be made. Massimo describes the problem as a lack of decision-grade visibility. Most large companies are not short of data. They have spent decades building data platforms, analytics systems, dashboards, cloud infrastructure, and reporting tools. Yet information remains fragmented across departments and applications, insights arrive too late, and employees often struggle to find the small amount of information that matters among enormous volumes of data. The result is a growing gap between having information and being able to act on it. Massimo explains why simply adding an AI model to this environment does not solve the underlying problem. If an AI system is connected to fragmented, outdated, poorly governed, or irrelevant information, it can produce convincing answers without providing reliable business outcomes. The quality of an AI model matters, but the context available to that model increasingly determines whether AI becomes a useful business asset or an operational liability. This leads to one of the biggest technology conversations emerging around enterprise AI: context engineering. Massimo explains how context engineering provides AI systems with the relevant data, tools, permissions, organizational knowledge, and guardrails required to complete a task safely. Rather than sending ever-larger volumes of information to AI models, companies need infrastructure capable of retrieving the right information and making it available at the moment a person or software agent needs to act. Fraud detection provides a practical example. An AI agent evaluating a transaction needs more than access to a powerful model. It requires customer history, behavioral patterns, company risk thresholds, permissions, compliance requirements, and the ability to recognize activity that falls outside normal behavior. Without that context, the system could block legitimate customers or approve fraudulent transactions while presenting its decision with complete confidence. We also discuss why digitally mature companies can still struggle with real-time decision-making. Massimo shares lessons from Elastic's work with organizations including Reed, the Met Office, and Rightmove, explaining why having sophisticated technology systems does not automatically make a company context mature. Information can still remain trapped between applications, teams, and databases, preventing employees and AI agents from seeing the complete picture when it matters. The conversation challenges another long-standing enterprise technology habit: adding more dashboards. Massimo explains why dashboards often provide visibility into what has already happened without helping people decide what to do next. Companies can continue adding reporting layers while employees become overwhelmed by information and remain unable to identify the actions that will improve customer experience, productivity, security, or business performance. A healthcare example demonstrates what becomes possible when companies solve this problem. Massimo shares how CogStack at King's College Hospital brought together unstructured patient information during the COVID-19 pandemic and made it searchable using natural language processing. Clinicians could find relevant information without waiting for technical teams to build new queries or systems, helping medical professionals access information when patient decisions needed to be made. For CEOs, CIOs, CTOs, data leaders, and technology teams trying to improve AI ROI, Massimo offers practical advice on where to begin. Do not start with another model, tool, or dashboard. Start with a business decision or workflow that is currently too slow, unreliable, or difficult to execute. Identify what information that decision requires, where the data is stored, who or what system needs access to it, which permissions should apply, and where information currently becomes delayed or disconnected. That process can reveal the visibility gaps preventing companies from turning their existing data and AI investments into measurable results. We also examine why search and retrieval are becoming infrastructure concerns for companies introducing AI agents. As software agents begin making recommendations and taking actions across business systems, their performance will depend on whether they can securely retrieve relevant information at scale. For business and technology leaders facing pressure to demonstrate returns from AI investment, this conversation provides a practical framework for improving enterprise search, context engineering, AI agent reliability, real-time operational visibility, and decision-making. The companies that gain the greatest value from AI may not be those collecting the most data or deploying the most models. They will be the companies capable of finding what matters, understanding its context, and getting trusted information to people and AI systems quickly enough to act on it. That is where better visibility can become better decisions, stronger productivity, and business growth.

Why are companies spending heavily on AI tools while struggling to show meaningful improvements in productivity, revenue, or business performance? In this episode of Tech Talks Daily, I speak with Matt Cloke, Chief Technology Officer at Endava, about what it takes to become an AI-native business, why deploying thousands of AI licenses does not amount to an AI transformation, and how companies can move from experimentation to measurable business outcomes. Matt has played a central role in Endava's own adoption of artificial intelligence and the development of Dava.Flow, the company's methodology for applying AI throughout the technology delivery lifecycle. With more than 11,000 employees and clients operating across multiple industries, Endava has treated itself as "client zero," testing AI internally before advising other companies about how to introduce it across their operations. Matt shares the story of a CEO who proudly told him that his company had completed its AI transformation after purchasing 10,000 licenses for an AI tool. Twelve months later, the business had seen little return on its investment and returned for help understanding what becoming AI-native actually required. The story captures one of the biggest problems with enterprise AI adoption today: buying technology is easy, but changing how people think about problems, redesign workflows, and create business value is much harder. We discuss why Matt believes becoming AI-native is primarily a mindset. Rather than treating AI as another application added to the technology stack, employees should become curious about where AI can improve existing processes, remove unnecessary work, and create new ways of delivering value. Matt also explains his idea that AI works best when it becomes invisible. Instead of requiring employees to constantly interact with chatbots and standalone AI applications, software agents can operate inside existing workflows, monitor information, prepare responses, identify problems, and bring people into the process when human judgment is required. His own use of AI agents provides a practical example. While attending meetings that prevented him from monitoring email for several days, Matt used agents to review incoming messages, redirect requests, identify urgent communications, and prepare draft responses. Rather than handing complete control to automation, he determined which actions required approval and where AI could operate independently. This leads to a wider discussion about human oversight and accountability. Matt argues that managing AI agents may increasingly resemble managing teams. Leaders do not inspect every decision made by every employee, but they establish responsibilities, controls, escalation points, and circumstances where intervention is required. Companies introducing agentic AI need similar approaches to supervision. We also examine two mistakes Matt frequently sees companies make. The first is treating AI adoption as a software rollout, buying tools for employees and expecting productivity gains to appear automatically. The second is creating centralized AI centers of excellence and expecting a small group of specialists to determine how every department should use the technology. Matt argues that employees closest to business processes are often best placed to identify opportunities for improvement. At Endava, the legal team runs monthly AI hackathons to redesign its own workflows, supported by technology specialists but led by people who understand the work itself. For companies operating in payments, financial services, and other regulated industries, the conversation turns to reliability, auditability, traceability, and risk. Matt explains how Dava.Flow allows companies to translate regulatory requirements and operational controls into policies that AI systems must follow and demonstrate throughout the delivery process. Rather than searching for a single killer AI application, Matt recommends examining end-to-end business workflows. Companies can map how information moves between employees, departments, and systems, identify unnecessary handoffs and manual processes, and determine where AI agents can improve speed, cost, and performance without replacing entire technology platforms. Leadership is another major theme throughout the episode. Matt believes the companies that achieve meaningful results from AI will be led by executives who personally use the technology, understand its capabilities, and demonstrate the behaviors they expect from their workforce. He shares how Endava brought senior leaders from legal, technology, people, and other business functions together to build software agents themselves. The experience changed how executives thought about technology investments, including one leader realizing that an existing vendor contract might no longer be necessary because the company could build the required capability internally. For CIOs, CTOs, technology leaders, and business executives under pressure to demonstrate returns from AI investment, this conversation provides practical lessons on becoming AI-native, redesigning workflows, managing software agents, maintaining human accountability, operating AI in regulated industries, and moving beyond technology adoption toward measurable business value. The companies that succeed with AI may not be those buying the most tools or making the biggest announcements. They will be the ones whose leaders understand the technology, whose employees rethink how work gets done, and whose AI systems quietly become part of everyday business operations.

Host Jason Pereira sits down with Suvrat Bansal, CEO of Clarista, to discuss how financial firms can safely launch AI applications without getting tangled in massive data-engineering projects. Bansal explains how Clarista acts as a secure "data fabric", streaming information directly from a firm's existing software without forcing them to completely overhaul their databases or risk platform lock-in.The conversation dives into how Clarista bridges the gap between fast AI development (like "vibe coding") and strict corporate realities, ensuring every app has ironclad data tracking, role-based security controls, and strict compliance audits. By providing a shared internal catalogue, the platform stops teams from accidentally building duplicate AI tools while helping wealth management firms quickly turn messy data into reliable, automated daily workflows.This episode is a must-listen for operations leaders and CTOs at wealth management firms who want to build custom AI workflows quickly while maintaining rigorous corporate data governance.Episode Highlights:00:00 Welcome and Guest Intro00:40 What Clarista Does01:10 Origin Story and Growth01:51 Building the Data Fabric04:59 Why Data Is Hard06:38 Outcome Focused Delivery07:34 From Insights to Workflows08:55 Agents and Vibe Coding10:37 Enterprise Pitfalls and Controls18:45 Avoiding Duplicate AI Apps22:27 Who Is Winning With AI25:08 Rapid Fire Closing Questions28:01 Wrap Up and SponsorResources:Facebook – Jason Pereira's FacebookLinkedIn – Jason Pereira's LinkedInWoodgate.com – SponsorClaristaLinkedIn - Survat Bansal's LinkedIn Hosted on Acast. See acast.com/privacy for more information.

AI isn't just speeding up recruiting; it's actually forcing companies to redesign work itself, blending human judgment with agentic execution across hiring, mobility, and skills development. As a result, most conversations these days are about AI in the enterprise centre on software development and engineering. Recruiting, hiring, and talent management get far less attention, but they may be where AI's impact is most immediate.In a recent episode of Tech Transformed, host Dana Gardner spoke with Meghna Punhani, Chief People Officer at Eightfold AI, about how organisations are rethinking talent acquisition, workforce planning, and employee development in an AI-driven world. Meghna Punhani's perspective is shaped by nearly two decades at Google, a stint leading employee experience at Palo Alto Networks, and her current dual role at Eightfold AI, where she both leads the people function and helps build the product her team relies on. That vantage point gives her a practical, ground-level view of what works and what doesn't when AI meets HR.Reimagining the Talent Lifecycle with AI Punhani's central argument is that most legacy HR systems were designed for a different purpose, one that has evolved as work itself has changed and the workforce now includes AI agents alongside people. Simply bolting automation onto existing processes, she argues, isn't enough. Organisations that are succeeding are the ones re-engineering roles, workflows, and organisational structures from the ground up, treating this as an operating-model shift rather than an IT upgrade.This shift touches the entire talent lifecycle, from how companies find candidates and evaluate skills instead of just job titles to how they support internal mobility. Punhani points out that skills now have a much shorter shelf life than in the past, which means static job descriptions are giving way to dynamic, skills-based decision-making. AI, she says, helps surface pathways for employees that traditional resumes and titles would never reveal, including her own nontraditional route into HR leadership.How AI Is Reshaping Workforce Strategy Trust is the recurring theme throughout the discussion. Punhani is candid that employees often fear AI-driven decisions, especially around jobs and evaluations. Her approach is focused on transparency first. When Eightfold rolled out digital twins internally, employees were uneasy until leadership explained how the technology worked and used it themselves, which helped build organisation-wide confidence.That same principle shows up in Eightfold's own hiring practice. One example is the company's campus recruiting programme in India, where its AI interviewer conducted roughly 90 per cent of interviews. This enabled recruiting to scale from around eight or 10 university partners to more than 150, and from approximately 5,000 applications to 15,000, without pulling engineers away from their day-to-day duties.Time-to-offer dropped from around six weeks to as little as four days in some technical roles, largely because interviews could happen around the clock rather than around a recruiter's or hiring manager's schedule. Beyond recruiting, Eightfold's internal initiative, nicknamed Project Andromeda, applies the same re-engineering approach across sales and finance, reportedly reclaiming thousands of employee hours through redesigned, agent-assisted workflows.AI and the Future of TalentLooking ahead, Punhani doesn't frame AI as a threat to human contribution, but she frames it as an amplifier of it. As tools become more accessible across every function, she believes the people who will succeed won't be the ones who know the most facts, since AI can answer those questions. Instead, it will be the people who ask better questions, orchestrate multiple AI agents, and apply judgment where the right answer isn't obvious.For HR leaders specifically, Punhani's advice is to claim a seat at the table now, rather than letting AI adoption happen without a people-first lens. This means learning the technology firsthand, demonstrating its value to non-technical teams, and partnering closely with CTOs and CIOs to shape decisions jointly. Her advice for individuals entering this shifting job market is similarly grounded: focus on learning agility over any single technical skill, since the skills in demand today may look different within months.Future of AI in Talent ManagementAcross the conversation, Punhani returns to one idea, and that is AI in talent management isn't primarily a technology problem; it's a leadership and trust problem. Organisations that treat it that way, redesigning work with both humans and agents in mind, are the ones seeing measurable gains in speed, candidate experience, and internal mobility.For HR leaders exploring AI adoption, the takeaway from this episode is to start before you feel ready, build trust through transparency, and let AI handle evaluation and execution so people can focus on judgment, empathy, and connecting the dots across the organisation. If you would like to find out more, visit eightfold.ai or connect with Meghna Punhani on LinkedIn.TakeawaysAI's impact on talent acquisition and management.Reengineering work processes with AI.Building trust and transparency in AI systems.Skills-based internal mobility and workforce planning.AI-driven candidate evaluation and employee development.Chapters00:00 Introduction to AI in Talent Management02:59 Understanding AI's Role in Talent Acquisition06:07 AI's Impact on Workforce Planning and Skills Development10:02 Building Trust in AI for Hiring Processes13:04 Internal Use of AI at Eightfold AI18:58 Measuring ROI from AI in Talent Acquisition25:02 Enhancing Candidate Experience with AI29:53 Future Directions for AI in Talent Management

Don’t let the AI wave crush you. Subscribe to our Newsletter: https://theultimatepartner.com/ebook-subscribe/ Check Out UPX: https://theultimatepartner.com/experience/ Dive into the seismic shifts happening within the AWS Marketplace and discover how AI, self-service product-led growth (PLG), and advanced co-selling strategies are redefining partner success. Matt Yanchyshyn, VP of Marketplace at AWS breaks down the recent announcements from the summit, illustrating how agility and adaptation are crucial to surviving the new agentic future. From lowering professional services fees to the explosion of business applications like ServiceNow, this conversation reveals the hidden mechanics of modern cloud procurement and how you can position your organization to capture massive enterprise opportunities before your competitors do. https://youtu.be/gaWxU1kgCLk Key Takeaways Adapting to the new agentic future requires agility rather than fighting the influx of AI tools. Lowering the listing fee for professional services from 2.5% to 0.5% drastically improves partner economics. Organizations without a self-service or PLG motion on the marketplace are literally leaving money on the table. Millennial buyers increasingly initiate complex enterprise procurements through self-service and AI-driven research. New AI-powered opportunity scoring empowers partners to prove their value internally and to AWS. Marketplace success hinges on optimizing metadata for AI agents, not just traditional SEO. If you're ready to lead through change, elevate your business, and achieve extraordinary outcomes through the power of partnership—this is your community. At Ultimate Partner® we want leaders like you to join us in the Ultimate Partner Experience – where transformation begins. Key Tags: AWS Marketplace, agentic workflow, med pick scoring, phoenix.ai, Cara Cloud, branded storefronts, product-led growth strategy, intrinsic value boost, SaaS evolution, self-service motion, Databricks credit model, Trend Micro companion app, MCP servers, opportunity score tracking, PPA drawdown, concurrent agreements, AAMI structural debt, CXML procurement Transcript: Matt Y Audio Podcast [00:00:00] Matt Y: The ability to adapt with change and kind of roll with punches. ’cause a lot of people are saying like, agents are gonna destroy everything. And, and the opposite has been true. [00:00:08] Vince Menzione: You can feel it happening. The ecosystem is shifting beneath us, the way hyperscalers are partnering, how AI is remaking the channel and what it means to win in 2026. [00:00:19] Vince Menzione: Welcome to the Ultimate Partner Podcast. I’m Vince Menzi, own your host. And each week I sit down with leaders at the intersection of technology, partnerships and outcomes. The voices shaping how ecosystems actually work. We talk about what’s real, what’s changing, and what it takes to lead in this era where the partner channel isn’t just part of the strategy. [00:00:42] Vince Menzione: It is the strategy because being in the room changes everything. [00:00:46] Matt Y: Let’s start. [00:00:50] Vince Menzione: And now on to the really important stuff. So, Matt, I don’t wanna butcher it ’cause I, a couple people have told me how to pronounce your last name and they said use the word magician and you’ll get close to it. But I’m just gonna introduce you as Matt Wy and I’m gonna ask you to pronounce your name on stage, but I want to have you join us. [00:01:08] Vince Menzione: So excited to have Matt wy. After a super busy day and night last night, come over from Brooklyn and join us today. Matt, so great to have you. Thanks. Thank you so much. Thank you so much. Alright, so pronounce your name for us. [00:01:23] Matt Y: Anyone wanna guess? Ian’s? It’s like magician. [00:01:27] Vince Menzione: It’s not that hard, [00:01:28] Matt Y: it’s not that [00:01:28] bad, [00:01:28] Vince Menzione: but I don’t wanna butcher. [00:01:29] Vince Menzione: I wanted to let you do it. Good. [00:01:30] Matt Y: What calls me Matt White. [00:01:31] Vince Menzione: That’s great. [00:01:32] Matt Y: Yeah. [00:01:32] Vince Menzione: So 13 years. [00:01:34] Matt Y: Four coming up on 14 next month. Yeah. [00:01:36] Vince Menzione: Wow. Congratulations. Yeah. So you’ve been there, you’ve been there since the early days. And we, we had a conversation. I had some Microsoft, former Microsoft colleagues. Uh, Theresa Carlson, for those of you who knew the public sector business. [00:01:48] Vince Menzione: Yeah. Who started, I mean, Andy came out, it was so funny because I was there and she was hosting Andy for a dinner and with all the CIOs of the federal government. [00:01:57] Matt Y: Yeah. [00:01:58] Vince Menzione: And she was still at Microsoft and it was actually kind of an interesting time. And she came over and did a lot of great things for a number of years. [00:02:04] Matt Y: Yeah. She [00:02:05] Vince Menzione: and a lot of great [00:02:05] Matt Y: business. [00:02:06] Vince Menzione: Yeah. She really like, it went from employee number one to 7,000. [00:02:09] Matt Y: Yeah. [00:02:09] Vince Menzione: And you, you were, you’ve been there all that whole time. Pretty much. [00:02:12] Matt Y: Yeah, I guess when I started in New York, just down the road, we were, uh, in a Regis facility. There were like 11 of us in, uh, just sitting around a table and we had to speak quietly sometimes because there was a, um. [00:02:21] Matt Y: Some type of a financial services organization down the hall and they’d listen to try and get stock tips on Amazon. Yeah, [00:02:28] Vince Menzione: I love it. [00:02:29] Matt Y: Never leaked. That’s [00:02:29] Vince Menzione: good. I love it. [00:02:30] Matt Y: Yeah, [00:02:30] Vince Menzione: you probably got some great stories and, um, we won’t have time for today ’cause I wanna leave some room for conversations on marketplace end questions. [00:02:38] Matt Y: Yeah. [00:02:38] Vince Menzione: But I would love to invite you back for a real, like, in-depth podcast and I would love to get the whole genesis story. [00:02:44] Matt Y: Let’s do it. [00:02:45] Vince Menzione: We’ll do it. Okay, so let’s talk about, let’s talk about yesterday for you. Uh, some, some really big announcements as well. I thought maybe you could recap a little bit of what’s been going on in the marketplace business and it’s an, it’s been an exciting time. [00:02:58] Matt Y: Yeah. Yeah. You know what’s, I think what was really nice yesterday is it was sort of the combination of bringing, uh, our partner services like Partner Central and all those other services together closer to marketplace. We’ve been doing that over, over several years. So Marketplace has some of its own. [00:03:12] Matt Y: Big announcements, like, uh, we have a, we formalized our list and sell initiative. For example. We have a new, so it we essentially reducing the cost, uh, to list on marketplace through a partner program. [00:03:22] Vince Menzione: Yep. [00:03:22] Matt Y: And incentives associated with that. We have a new AI powered listing experience, which I think is particularly important ’cause I think many of you are like me and watching your SEO numbers go down and watching your agent traffic go up. [00:03:33] Matt Y: And so having, uh, an AI assistance in marketplace to optimize your listings for not just to, you know, retain what you can of your SEO, but prepare for the newent future and improve your GEO as we’re calling it. So that, [00:03:45] Vince Menzione: so it’s GEO now? [00:03:46] Matt Y: Yeah. You know, there’s a little debate right now in the acronym Moral A A EO versus GO I’m going, I’m on the G team, so, yeah. [00:03:52] Vince Menzione: Alright. GEO [00:03:54] Matt Y: It’s like the, the, yeah, they’re gonna win. They’re like the Knicks, but the, um, [00:03:57] Vince Menzione: yeah, yeah, exactly. [00:03:57] Matt Y: But yeah, so AI assisted, uh, I mean, making. The most of, like, essentially marketplace is an excellent conversion engine. And so using AI to help improve that conversion engine in the form of your PDPs for both humans and agents. [00:04:08] Matt Y: So that was an exciting launch. Um, I got the most applause when I announced that. We lowered, we made the economics better for, uh, consulting offers professional services, nice to marketplace. We lowered the listing fee from 2.5 to, to 0.5% and wow, it goes even lower in certain circumstances. So just improving the economics. [00:04:24] Matt Y: I’m really excited to. Really partner with a lot of you to reinvent services through, through the marketplace like we did with SAS and other areas. Uh, and we’re doing with agents right now. So that was a big one. And then a whole series of announcements around, um, how we’re making it easier and more cost effective and more efficient to partner with AWS. [00:04:41] Matt Y: So using AI to, uh, using med pick scoring to automatically progress opportunities so you don’t have to kind of wait on a human. To, to click and progress, you know, that that can take days. And, uh, if you, if you wanna have an opportunity and have that be cos sold with AWS, that can be through a mix of agents for the long tail and with humans in the, in the sort of top end and more complex. [00:05:00] Matt Y: And allowing AI to help all the partners improve their opportunity quality so that we can better co-sell together. So. Yeah, I said AI a lot intentionally. Um, [00:05:09] Audience Guest: yeah, [00:05:10] Matt Y: AI sort of in the whole cycle for buyers, for sellers, uh, for operational efficiency, cost of sales. So a lot of announcements. I think I hit the big ones, so yeah. [00:05:18] Matt Y: I’m Might have missed something there. There we go. [00:05:21] Vince Menzione: George. [00:05:21] Matt Y: Oh, and storefront. Yeah. Thanks George. See, I look at George to see what I missed. Uh, we, we acquired a great company called phoenix.ai late last year. Okay. And you, you actually were said Caresoft and Yeah. Be down. Uh, [00:05:30] Vince Menzione: yeah. [00:05:30] Matt Y: So if you’re familiar with Cara Cloud, they have a procurement portal. [00:05:33] Matt Y: It’s heavy use by the US government, and they, um. Uh, we, we acquired them, uh, the really great growth company. They have over 70 logos now, and they help you build a branded storefront on marketplace, which obviously is important in the government space. If you’re procuring on a certain contract with a certain reseller, um, you know, there’s a certain set of products you’re allowed to buy. [00:05:51] Matt Y: But what we’re finding is even down on Wall Street, you hear, um, enterprises are, are using storefronts for internal procurement and they wanna have a curated collection of, of partner products and, and your own ecosystems internally. So we’re selling to both customers. And also to channel partners to build custom storefronts, branded storefronts for, and [00:06:07] Vince Menzione: it makes total sense, right? [00:06:08] Vince Menzione: Yeah, because you wanna li you wanna limit the, the viewing and, uh, and get, because I mean, how many different listings do we have? Like over 30,000? [00:06:16] Matt Y: Yeah. Yeah. There’s, I think the official numbers over th we have over 36,000. I was checking from over 6,000 vendors. Um, it’s a lot. And, and that’s gonna explode with the AI powered, uh, listing, uh, experience that we launched. [00:06:26] Matt Y: We’re gonna make it easier. And I guess what I’ve been telling partners is. You know, customers aren’t clicking through categories anymore. They’re using AI to search. And so it doesn’t matter how big our catalog is, what matters is being found. And what matters is converting that buyer. So if you have a. [00:06:39] Matt Y: If you’re running a demand gen campaign for say, like, you know, life sciences in, in Jersey and there’s a specific buyer at j and j, you wanna capture, that person doesn’t wanna be just dropped onto a generic marketplace, 30,000 listings. They wanna be dropped in a very specific place where they’re seeing like life sciences offers from Accenture, for example, coupled with a life sciences power thing with Elastic, you know, like, but a solution. [00:07:00] Matt Y: And that they want to land in a curated place where that highly intention buyer can be converted effectively. So that, that’s what we’re doing with all this. [00:07:06] Vince Menzione: And that’s where the GEO comes in because [00:07:09] Matt Y: Yeah. ’cause that buyer might be an agent That’s right. With, and that agent has is even more fickle, honestly. [00:07:14] Matt Y: And you know, what used to be milliseconds for the human before they kind of click away is, is now perhaps microseconds. Yeah. And so, uh, you know, having the right metadata and, and the right positioning, uh, the right story that an agent or a human can pick up to ultimately. Uh, complete their product research and choose your product is, is critical. [00:07:30] Vince Menzione: Very cool. Very cool. So before I, I, I’ve been asked to ask you this because I, I’ve had this con, people have brought come to me and said, you gotta ask Matt about music. He’s a big music guy. And, uh, so what are your favorite bands? [00:07:49] Matt Y: So, I mean, the, the real answer is, uh. I, I go to about a show about every week. [00:07:54] Matt Y: As, as Mike Trill knows, uh, we heard a show last night. Um, we were, uh, just a few hours ago, really? And, uh, um, favorite band, uh, well, I’ll tell, I’ll tell a story. I, I had a side hustle with MTV for years. Um, I used to run a music website. Um, oh, that’s cool. I didn’t know that. It got, it got kind of popular. It got sponsored by, if, if anyone’s into like early hip hop. [00:08:16] Matt Y: It got sponsored by a group called Jurassic Five. ’cause he, one of them reached out to me and said, nice. Hey, uh, you know, I’ve been, I like your website. And he ended up paying for a web, hosting a Dream host, if you remember, of cost back then. [00:08:26] Vince Menzione: Oh, Jesus. [00:08:26] Matt Y: Because I was broke and couldn’t afford it. And then, uh, and then this band sent me like a, a single and said, Hey, you know, trying to get the word out about our little band, can you help us out? [00:08:35] Matt Y: And I put their, uh, I put their, you know, single up on my, on my website and it blew up. And that band is Vampire Weekend. So they’re kind of big now. Wow. Yeah. Um, and uh, that got picked up by like Vanity Fair and all these other guys. And then I got sponsored by MTV to essentially write. Music reviews for years on the side. [00:08:51] Matt Y: So I was working for the Associated Press, laying cable in sports and war and, and, uh, yeah. So Vampire Weekend was good to me that, that they, they kind of paved a way to go to a lot of free shows over the years and a lot of bands and see a lot of great music. But yeah. [00:09:03] Vince Menzione: That is very cool. And that, and how did that get your day? [00:09:05] Vince Menzione: WS It was just a, it was just the technology path that was like, [00:09:09] Matt Y: I mean, it’s a, it’s a, I guess it’s a bit of a long story, but, um, the. There’s many versions of this story. I’ll tell the, tell the one quickly. I was living for free in a Fulbright scholarship house in West Africa. You, we can talk about how that happened another time. [00:09:23] Matt Y: And, uh, a guy had sort of fallen down on the floor ’cause he’d had too much to drink. And I, I sort of lay down beside and be like, Hey man, are you all right? And, um, he, uh. He worked, he, he worked for the Associated Press and next day I had the job, um, being West Africa, head of technology for West Africa. [00:09:37] Matt Y: And because of that, um, and as I learned years later, the AP didn’t have dr they had no disaster recovery. Yeah. And I, I can tell you that now ’cause um, you know, 16 years since I worked there, but they, uh, I put the DR in, um, on AWS and we’re talking like, yeah, 16, 17 years ago. This is early. It was early days. [00:09:56] Matt Y: And I, I swear to God, I paid for. Uh, our AWS bill using, um, taxi receipts, fake taxi receipts that I bought in on Nigerian market, um, because there was no budget and so, you know, it was like 30 bucks. [00:10:08] Vince Menzione: I was gonna say swipe a credit card, but they didn’t [00:10:09] Matt Y: knew that this is the entire press this before. [00:10:11] Vince Menzione: This is before, yeah. [00:10:12] Matt Y: Yeah, like the entire ap. Um, and, uh, so AWS called me like, who are you? Like, why, why are you paying on like this like low limit credit card for like the ap? Like, who are you? And, uh. Next day I had the job. Well, a week later I had the job with aw WS. That so cool. So that’s the story’s [00:10:29] Vince Menzione: cool thing. [00:10:29] Matt Y: Yeah. [00:10:30] Vince Menzione: Very cool. [00:10:31] Vince Menzione: Uh, sports teams. So Knicks fan. [00:10:34] Matt Y: Yeah, I mean, I like the Knicks. Um, they’re h hockey, I’m not allowed to say anything different. No. I appreciate them. Uh, I’m a Raptors fan. I grew up in Toronto mostly. Yeah, yeah. Uh, so, and you know, when they won, uh, that was very exciting as well. So no, Nicks are great. I like the Knicks. [00:10:49] Matt Y: Nothing against the Knicks. Um. They’re fine. Yeah. [00:10:54] Vince Menzione: Hockey, hockey fan. Favorite hockey teams? [00:10:56] Matt Y: Oh yeah. Itron. Maple leaf. Maple leaf. Yeah. They’re gonna, they’re gonna win. Of course. Of course. Yeah. Um, like every year they’re actually, we [00:11:02] Vince Menzione: have some Canadians laughing in the sand. [00:11:03] Matt Y: Well, the leaf are, are, are the Knicks of hockey? [00:11:05] Matt Y: Like Yes, they are. You know, it’s 67 years out, coming up on 68 since they won, so That’s crazy. 53 is nothing. I know. Pain. So. Yeah, definitely the least. Yeah. [00:11:15] Vince Menzione: I love it. I love it. It’s so cool. Yeah. So what was the, uh, what was the, what was the last concert you went to? [00:11:22] Matt Y: Well, literally last night. Oh, it was last, [00:11:23] Vince Menzione: oh, that [00:11:24] Matt Y: was actually concert were my favorite bar in the world. [00:11:26] Matt Y: This place called Sunny’s. Uh, it’s, you know, I, I took Mike and, and Matt from, from Texas and from TGS down there to sort of see my neighborhood and they’re like, where are we? And I’m like, yeah, I live here. Uh, sort of an industrial part of Brooklyn. And, and we went to see, um, I dunno what you would call it, like. [00:11:40] Matt Y: I guess it’d be like roots music. There was a woman with an accordion and a guy with a big cowboy hat. Yeah, it was, it was fun. Yeah. [00:11:47] Vince Menzione: That is so funny. Alright, we’re gonna shift back years. Um, important time right now for partners. What, what should partners be looking out for the most? What would you say to them in terms of what’s the, what’s their real headline for them? [00:11:59] Matt Y: Well, I, I, you know, to borrow from you actually, you know, I liked, uh, the, the principles you had up there and, and with agility, um, you know, there’s a lot of fud flying around right now. You know, people. People were like, oh, it’s the demise of sis with the arrival of ai, you know, everyone’s gonna be using agents. [00:12:13] Matt Y: And then it turns out it’s been a huge boon for most, uh, you know, system integrators and consulting companies that I work with. They all have, you know, the, the good ones especially have vibrant consulting practices now, and everyone is deploying fds, uh, you know, um, the new, the new cool acronym. But it’s, it’s essentially created a huge opportunity for the consulting space. [00:12:31] Matt Y: Uh, and similarly, uh, you know, there there’s this narrative around the sa sa apocalypse, which I really hate, you know, ’cause it was, uh, premature and kind of a trigger reaction from the stock market. And, you know, just look, look what Snowflake did. And, you know, they did what a lot of SaaS companies are doing, but they, they added a nice sort of glaze of positioning and, and, you know, their stock popped and they did pretty well. [00:12:50] Matt Y: And so I think the ability to adapt with change and kind of roll with the punches. ’cause a lot of people are saying like, agents are gonna destroy everything. And, and the opposite has been true. For the more successful consulting companies and software companies who have become agentic. But SaaS hasn’t gone away, you know? [00:13:05] Matt Y: No. Look at our own marketplace. We have this agent marketplace, but people aren’t buying atomic agents at scale. They’re buying ified SaaS solutions with sort of agent sidecars, which has created new opportunities for candidly additional licenses, [00:13:16] Vince Menzione: right? [00:13:16] Matt Y: Um, as customers sort of want to consume more AI services on top of their. [00:13:20] Matt Y: On top of their SaaS solutions. So I think being agile, you know, you see like ServiceNow as part of our billionaires club. Yes. They’re not going anywhere. They’re, yeah. They’re gentrifying. You know, Salesforce has pivoted to this headless model, um, along with Asian Force and using sort of Slack as the operating system. [00:13:34] Matt Y: And, you know, you said like a lot of companies from the seventies aren’t around anymore. They’re gonna be winners and losers. Yeah. Um, but the winners are gonna win even more. And so I, I think what’s so important right now for partners is to not, not bite too hard at the, the latest trend. You know, models are changing and everyone’s like, oh, you know, philanthropics really in the world and they’re wonderful, great to work with, amazing technology. [00:13:55] Matt Y: That’s what people are saying about open AI six months ago. That’s right. And before that, you know, and it, I, I was with Fireworks AI yesterday, a great company and they have some really cool stuff with sort of, um, they believe in more cost effective, uh, open source models essentially, that you can find tune. [00:14:08] Matt Y: Maybe that’s gonna win. I don’t know. Um, is it gonna be sort of domain specific models? Is it gonna be highly capable LLMs? Are LLMs gonna level off as soon as Fable and Mythos are allowed to launch? Maybe. I, I don’t think anyone can predict the future right now. So you have to be agile and you have to kind of seize the opportunities and take a couple punches. [00:14:25] Vince Menzione: Yeah. [00:14:26] Matt Y: You know, and marketplace too, like we’re, you have to be unafraid to experiment right now. Um, you know, that’s hard if your stock’s taking a beating. Um, but this is, it’s a, it is a disruptive time, uh, but it’s creating actually enormous opportunities for growth for partners and, and we really see that, you know, in marketplace specifically within AWS. [00:14:45] Vince Menzione: It, it, it does still feel like the deer in the headlights moment. Right. Would you agree? Like you’re probably taking a lot of meetings and, and calls from ISVs specifically? [00:14:54] Matt Y: Well, [00:14:54] Vince Menzione: that are still trying to figure it out. [00:14:56] Matt Y: Yeah. But it’s everyone. Yeah. I think what’s really interesting, I had a meeting [00:14:58] Vince Menzione: with, it’s not just one. [00:14:59] Matt Y: Yeah. I, well, I had a meeting with one of the leading AI companies, like one of the biggest ones. And they, uh, they demonstrated how they work and they were really proud. They were like, you know, look at our agentic workflow. And I came out at me. I’m like, that’s it. Ours is way better. Like really like, you know, ’cause we we’re, we’re using quick desktop with MCP servers and connectors and all this, and you know, we, we have our own sort of ecosystem of partners, a mix of homegrown software and third party. [00:15:20] Matt Y: And I kinda walked out there and, and looked at, you know, my phone, which has been populated by agents this morning with all the, and I was like, I have a way better agent workflow than this world’s leading supposedly AI company. And I think, um, that really, so during, I, I would, during the headlights, you can call it deer in the headlights, I call it chaos. [00:15:36] Matt Y: And in times of chaos there are people who create. Opportunity again. And so, yeah, there are some people who are stuck and who don’t know what to do, who are over worried about token costs, um, who are not experimenting. But there are a lot of companies, uh, taking this opportunity to kind of pivot their business. [00:15:53] Matt Y: Um, I think, I think we’re in a moment and, uh, yeah, I, I candidly I see more of the latter. I see more experimenting. [00:15:59] Vince Menzione: You mentioned ServiceNow. Any other great examples of that? Organizations that really embraced it? [00:16:04] Matt Y: Uh, yeah. Well, you know, ServiceNow is part of this business applications category, as we call it, in marketplace. [00:16:09] Matt Y: That outside of AI, I think is the fastest growing category in marketplace, which is wild when you think about it. ’cause we’ve historically been an infrastructure partner marketplace with security and data and analytics and, you know, security with channel partners, et cetera. But Salesforce, ServiceNow, Workday, Adobe, you know, I could go on. [00:16:23] Matt Y: They, they are actually. You know, our fastest growing category and yeah, ServiceNow, obviously reinventing itself for ai, Salesforce, but Workday, you know, the workday’s done some, who knows if it’s gonna work, but they, they’re experimenting with essentially like a Databricks, uh, credit style model for like, units of work, uh, which I think is fascinating. [00:16:41] Matt Y: Like everyone’s talking about value-based, outcome-based pricing and meter. And, and you have companies that are ERP companies, you know, like traditional business applications, experimenting with effectively like a metered pay as you go, value based credit model. Again, like who knows if it’s gonna work. [00:16:54] Matt Y: But I think that’s really amazing to see and we need more ISVs experimenting. I, I was talking about trend ai and I know they’re, they’re, they’re one of the sponsors yesterday. You know, many of you know them as Trend Micro back in the day. They’ve successfully reinvented themselves. They built that companion app. [00:17:10] Matt Y: Um, you know, that I think we’re seeing. Just a ton of experimentation in the market across categories. Uh, I could go on and on about partners. Um, yeah, there, I I wouldn’t pick a winner right now. Yeah. [00:17:24] Vince Menzione: You, you, we’ve talked about ai. We’ve talked, talk more about the buying journey and how that’s changing, because again, it feels, it feels like that’s also [00:17:33] Matt Y: Yeah. [00:17:33] Matt Y: So, you know, one of, one of the core, uh, strategic objectives, or we’ll say like the philosophy marketplace is that. Um, financial incentives are important, you know, EDP or PPA drawdown, uh, credits. Like we need to act as an efficient and effective vehicle for allowing buyers to exercise their discounts for, and, and sort of partners to exercise their credits, et cetera. [00:17:55] Matt Y: That, that’s actually important. But what, what a lot of people over rotate on that, and we’re really, one of the things we say a lot inside at Amazon or at AWS marketplace is we want to continue to boost the intrinsic value of marketplace beyond the financial incentives. And well over a quarter of all private offers, private pricing, private, uh, custom terms, et cetera. [00:18:14] Matt Y: Um, begin with a self-service or PLG motion. And partners who don’t have a PLG or self-service motion are literally leaving money on the table. Like if you look at like a Databricks for example, and they did a good job integrating buy with a WS within their SaaS application. They have free trials, they have really strong pego and, and, uh, and PLG motion. [00:18:33] Matt Y: They’re making, I can’t share their numbers obviously, but they’re making a ton of money. On purely self-service motions. And importantly, they’re acquiring new business, new logos that they nurture, you know, really like not just leads but closed opportunities, right? That they lead, they’re growing, uh, at a reasonable conversion rate or or success rate into the next big logos. [00:18:50] Matt Y: And these are over multi-year horizons. They’re patient, you know, they bring in these new logos with PLG, and they’re also bringing banking, a lot of large enterprises. Through self-service. I, I was with data Mask. There’s this great little startup from New Zealand. They’re a New Zealand based company. Um, super nice guy. [00:19:06] Matt Y: And, and, uh, they, they got huge logos. I think they got, what was it? A DP and some huge American logos. Okay. And this like logo in, I think it was Chile, or no, it was Peru. They’ve never been to Peru. They don’t have sales in Peru. Um, and they. Buyers were discovering them self-service and they, they, I think they got something like 13 logos entirely through a self-service motion. [00:19:26] Matt Y: One password will tell you the same thing. I was just with them in Toronto and companies big and small startups and the largest are getting enterprise wins in addition to net new small logos through that PLG. Buyer motion. And that’s because you have a whole generation of CFOs, CTOs, CROs, whatever. The C is [00:19:43] Vince Menzione: millennial [00:19:43] Matt Y: who grew up on their phones. [00:19:45] Vince Menzione: Yeah. [00:19:45] Matt Y: And, and it sounds like, you know, hyperbole, but it’s true. They, they want immediate apps, immediate access. And that actually, you’re like, oh, that never translates to business applications. Turns out it does. It does. And they might not be buying on their phone, but what they are doing is researching and we see the numbers, the amount of customers who are doing their research, and then eventually landing on the page from chat, GPT. [00:20:06] Matt Y: From major financial, like Fortune 500 companies is extremely high. Yeah. Uh, you have procurement team, sourcing team, uh, developers who are starting the research increasingly, like in clawed in chat, GPT, and then, you know, building a proposal and then handing it to their enterprise procurement team. Yeah. [00:20:22] Matt Y: Which is still largely unchanged. So buyer behavior is on the front end, on the research side is really changing. So the [00:20:29] Vince Menzione: discovery is happening through PLG. [00:20:32] Matt Y: Yeah. [00:20:32] Vince Menzione: And then the backend work on private offers and things like that sometimes still happens the old way. [00:20:36] Matt Y: Yeah. Well, and so, you know, it’s [00:20:37] Vince Menzione: fax machine, [00:20:38] Matt Y: some people Yeah, sure. [00:20:39] Matt Y: They’re bringing the deal directly to Marketplace last minute. But even if that deal goes direct, sometimes they’re still beginning their research journey and increasingly using Marketplace as a research vehicle, which is why we launched Agent Mode, um, to help you sort of help you and agents do research. [00:20:51] Matt Y: But that I think if, if I have one piece of device for any partner consulting or ISV is. Don’t leave those leads and that money on the table by not having a PLG self-service strategy like you’re fooling yourself. Uh, and it’s, it’s a huge, it’s a huge, huge business for us. The, the majority of all customers by far on marketplace don’t even have a PPA, uh, and a huge percentage of even those with PPA spend beyond the p. [00:21:17] Matt Y: And so if you’re just think if you’re just using marketplaces as like BPA retirement, you are literally losing money. [00:21:22] Vince Menzione: Yeah. [00:21:22] Matt Y: Yeah. [00:21:23] Vince Menzione: We have a session with Vinod. We’re gonna talk a little bit about that right after. Great. So good. Um, so I, yeah, I think, um. We talked about, we talked about agents, we’ve talked about the millennial buyer, the change in buying behavior. [00:21:40] Vince Menzione: What other, what other areas of aspect I, I, I, I do wanna think about like opening it up though for a second. I think that maybe with maybe nine minutes left. Sure. I just want to get a read from the people in the room. People have questions for Matt that we weren’t able to ask them. Yeah, I think, I think we probably have a few of those. [00:21:57] Vince Menzione: I think that would probably be great. [00:21:58] Matt Y: I can sense the hardball coming. [00:22:00] Vince Menzione: You’ve known each other [00:22:00] Matt Y: a long time. [00:22:01] Vince Menzione: Yeah. No, no. Hardball. We have a mic back here. Okay. I’ll just, we’ll, we’ll, we’ll get you a mic as we are recording. So good. Thank you. [00:22:11] Audience Guest: Uh, Boris Geller with a, a Click PLG is near and dear to my heart. [00:22:17] Audience Guest: We’ve been doing a lot of business in marketplace and I’m still struggling to sell my vision internally on, on, uh, on PLG. Uh, I think. Ag Agent AI is gonna be one of the drivers, and we are already on, uh, agent Marketplace, but I would appreciate guidance on, uh, best practices. How do we kind of, uh, operationalize it? [00:22:41] Audience Guest: It’s, it’s on us, not on you. [00:22:43] Matt Y: Well, no, I think it’s on both of us. You know, we, uh. One thing that we’re trying to do is give you more data to, to sell to your internal stakeholders in your executive suite. The value of co-sell with AWS all up, like finally with what we launched at, uh, the summit yesterday, you now get an opportunity score. [00:23:02] Matt Y: You, you get a number. People have been asking for this for years, so, so you can say when we do this and we, when we give AWS this information. The score goes up and we have a higher propensity to be cos sold by humans or agents before you had to kind of, it was like this mystery you had to guess. And similarly with marketplace, um, we, we have new dashboards that you can use to sort of, you used to have to sit down with us and go through spreadsheets to trace sort of lead to trace the funnel to sort of a close opportunity. [00:23:28] Matt Y: And we’re gonna continue to launch more there. But you now have more data that you can show. You can be like, listen, these are our inbound leads, this how’s converting, and now we have PRM, the partner revenue measurement where we can say like, this is what it’s translating into in terms of. AWS service revenue driven by our product. [00:23:41] Matt Y: And so that being able to tie from that inbound lead from your demand gen campaign through to a converted opportunity to what you actually drive from an AWS impact perspective, so you can, and then what your opportunity score is that data you can use to sell. Not only internally, but to us as well. Yeah, to a skeptical sales team or whatever who’s not maybe, you know, hype on partners in the, in the US West. [00:24:03] Matt Y: You can be like, listen, I don’t care what you think about my business. This is what I’m gonna drive for you with your quarter retirement from an AWS perspective, and this is how the shape of your customer accounts are gonna change. And this is why you should pay attention to my opportunities. ’cause my opportunity score is, is crazy high and I’m giving you insights into business that AWS would not otherwise have. [00:24:19] Vince Menzione: That’s your brand story we’re talking about. [00:24:21] Matt Y: Yeah. [00:24:22] Vince Menzione: Building your story up with within [00:24:25] Matt Y: So it’s, it’s about the data, I guess. And, and you should, you know, you should all actually be [00:24:28] Vince Menzione: Yeah. [00:24:29] Matt Y: Asking me for more data, so, you know, and tell me like, what do you need to sell to your internal stakeholders? ’cause if I can draw a clear line. [00:24:35] Matt Y: From your demand chain campaign that lands on a marketplace, which I know is a conversion machine, it has way better than industry levels of, of conversion rates. And then you can show, hey, if we have a PLG strategy and we land those leads on marketplace, we will convert them with high efficiency, low cost of sales and, and, and have sort of a bifurcated where we can close some through self service, some through express private offers and some through private offers, depending on deal size. [00:24:57] Matt Y: Like you tell A CFO that, and they’re my number one customer now and they love it ’cause they see cost of sales going down, cost of operations going down and business going up. Um, so I think we have more data than we used to use that data. And let me know what other data do you need to make that pitch and make that pitch to the CFO go around the head of sales, all those other people. [00:25:15] Matt Y: Honestly, the CFO is where we get the best leverage. [00:25:18] Vince Menzione: Awesome. Great question. [00:25:23] Matt Y: Gonna bring your mic. [00:25:23] Vince Menzione: We’re, we’re gonna get your mic here. There you go. Oh, [00:25:25] Audience Guest: thank you. So my name’s Jody Cheval and I’m a consultant now, but I was at Workday during when they adopted AWS and it, a sales organization needs propensity to buy data. [00:25:34] Audience Guest: To really drive the sales team to realize the opportunity kind of makes them visualize it. We didn’t struggle, but it was challenging to get that data because at that time we’re getting spreadsheets. So does AWS have a vision of making that API based data that our client, my clients, can get at and bring into a tool to start building account hypothesis based on that data? [00:25:57] Audience Guest: ’cause it really is important to an enterprise sales guy to have the sense that OAWS can help me close this deal. [00:26:03] Matt Y: Yeah. I mean. Part of that. So we, we launched, we’ve been launching part of that in stages and we’re not done. There’s, there’s more coming. Um, part of that is embedded really within the new, uh, partner agent workflows. [00:26:13] Matt Y: We are giving sort of more, uh, information back to you, not just about like what funding programs you’re eligible for, but like, you know, and when, when we will co-sell this deal with you, which is effectively a signal like we, we see this as a high value opportunity, that you have a likelihood of winning internally. [00:26:28] Matt Y: We, we have this solution matching engine that we’re using and we announced. That, that that ties you the partner to a customer specific opportunity that you have a high propensity or the partner has a high propensity to assist with and ultimately win. And now we’ve tied that to our express private offers, which we announced this week. [00:26:44] Matt Y: So it’s an indirect answer to what you’re asking, but a rep can essentially say. Send a private priced offer to the customer on behalf of the partner without having to ring up the partner because they have a high propensity to win this deal with the customer. So we’re progressively launching features like that. [00:26:59] Matt Y: In addition to the propensity to buy data that we do now share. It used to be kind of, again, manual magic depending on who you knew we could share. Now we do share that programmatically, and there’s more to come specifically in that space. Uh, I’d say watch that space. In the next few months, there’s gonna be more data coming away, but we do have the APIs, we have the agent. [00:27:16] Matt Y: We have things like express private office solution matching, and we have been sort of in that space progressively launching features over the last six to 12 months. And, and you should expect to see some more there soon, not just from us or from our partners. [00:27:27] Vince Menzione: Nice. Any announcement dates? [00:27:30] Matt Y: I can’t commit to a date or else my engineers will get mad at me. [00:27:33] Vince Menzione: It looks like we Another question number. Is the mic still back there? Okay. There’s a gentleman over here [00:27:40] Audience Guest: first Go leaves. Um, it’s awesome. I’m right next to. I was right next. [00:27:46] Vince Menzione: We’ve got a lot of great plants here, so, [00:27:49] Audience Guest: um, so this may be a little bit myopic or, or a challenge that we run into, but I love a lot of the innovation that’s looking forward and all the future things that we’re doing. [00:28:00] Audience Guest: One of the things that we’re struggling with is a little bit of almost like tech or structural debt. How do you think about bringing flexibility to the core pieces that underpin all of the innovation, which is. We are self-hosted. So one of our listings is an a MI. You can’t amend an a MI, you have to cancel and start over. [00:28:18] Audience Guest: So a lot of the building blocks, when you think about PLG, if somebody wants to add to that in an a MI listing, it’s, it’s sort of broken. So how are you thinking about taking all of the, the rapidly changing buyer behavior and then looking back at the structural foundation that underpins all of those things, like offers and, and amendments and changes and all of that? [00:28:39] Matt Y: Yeah. I, I promise I didn’t seed that question, but that, that’s a great one. Um, so not to get too in the weeds, but fundamentally, marketplace was built up, um, a bit like AWS like a set, a series of services somewhat independently. And each product type was effectively its own service, SaaS, server images, ais. [00:28:59] Matt Y: Um, what we’ve done recently is now we, we have, we got rid of product types basically on the backend. You, you don’t see it, but what that means, for example, like another thing AAMIs don’t support today, future data agreements. Um, or concurrent agreements, uh, they will all be supported by amis before the end of the year. [00:29:14] Matt Y: ’cause what we’re doing, this fundamental thing that you won’t even see called product offer decoupling. Uh, and it’s a fundamental piece of things that we need to unwind. ’cause we built up, we were moving very quickly over the years. We had a distributed engineering model and we built each product type independently. [00:29:28] Matt Y: And so yeah, if you’re a seller and you’re selling containers, agents, SaaS, amies, um, we’re breaking down the silos between those so that each of them will get the same benefits. And, and by the way, we’re taking the same approach to international. Hopefully you’ve noticed now that. It’s not like a feature launches in the US only and then takes five years to launch in either public sector or another country. [00:29:48] Matt Y: We, we’ve taken a global approach to feature launch and increasingly a product type neutral approach to feature launches. Uh, that’ll be largely resolved before the year’s out. We’re working on it right now. So again, it’s, it should be transparent to you, like you shouldn’t actually see any difference in the, in the experience. [00:30:05] Matt Y: Except that all of those features will be available. So, so that is, uh, actively under work. And that’s actually something if you’d like to try, um, you’re, you’re welcome to. So, yeah, [00:30:17] Vince Menzione: we have time for maybe one more question and we we’re actually gonna have you up here with a couple partners. [00:30:24] Matt Y: Sounds [00:30:24] Vince Menzione: good. Kind of fun. [00:30:32] Audience Guest: Hey, Matt, uh, met Natasha from Dondo. Uh, quick. So great announcements. And you know, you talked about the million, multi-billion dollar, uh, club, and, uh, that’s all great. Uh, in terms of the. Propensity data. I think that’s coming at the center of a lot of things, right? You know, for enterprises, oh, there’s an investment and you tap into that investment. [00:30:53] Audience Guest: But also there’s the other side of the procurement where a lot of customers, sometimes we work with, they’re like, they still wanna go direct for whatever reason, right? So I think there’s an education piece there, but also trying to understand like how we can work together to, you know, get some of that side of the things sorted out as well. [00:31:11] Audience Guest: You know? ’cause a lot of times it’s not about. Just, you know, retiring the, uh, the, the spend comets, but also like, Hey, I’m used, I’m already used that for something else. So maybe that’s not an, uh, something that applies here. And in also in tying that the PLG motion, uh, you know, for the customers you said, you talked about, you know, if there is. [00:31:34] Audience Guest: Leads on the TA table, like where the, it’s not the enterprise, but you know, the others. Um, I feel like it’s more to do, changing the business model at some times. Like with the enterprises, you have the revenue stream coming through, say large deals, right? And all of a sudden you tap into this, you know, PayGo. [00:31:51] Audience Guest: Where it flips the whole equation with, you know, the financing and the, and the, and the revenue measurement. So I think there’s two aspects of how do you kind of cons reconcile those things in terms of, you know, the revenue measurements going forward. [00:32:05] Matt Y: Yeah. So, so two things real quick on the procurement. [00:32:07] Matt Y: Um, yeah, like, yeah, I sort of alluded to this earlier, but, uh. Procurement is a bit late to the AI ag agentic transformation. They’re trying, and there’s a lot of great new incumbents in this space. And the big leaders like, you know, Coupa and Ariba and Oracle are, are, are evolving their products, albeit a bit slowly. [00:32:26] Matt Y: Um, but the, I think, uh, it’s still the long pole in the tent. You know this. And so like, there are two reasons why deals tend to go direct, because it kind of hits a wall of. Legal, uh, you know, procurement, governance, like all that kind of after the selection’s been made, et cetera, or, or they’re, you know, we can’t change. [00:32:44] Matt Y: People are gonna optimize for, for finance, you know, they’re, they’re going to, if they’re getting big discounts. I mean, that is life. I always say it’s like sellers at the most agented company are still gonna chase quota no matter how, you know, crazy. Uh, your, your company is, and it’s the same with, um, with the chief, uh, financial officer and chief procurement officer. [00:33:01] Matt Y: They are going to, they’re literally. Paid to find discounts. And so we’re not, we’re not gonna get rid of financial engineering. That’s a, that’s a thing. What we can do is reduce the friction for procurement. So we launched, for example, like mandatory purchase orders. That was a big thing. We, we have buyer notifications, now we’re making other procure to pay enhancements. [00:33:17] Matt Y: I mean, procurement systems still use like CXML. It’s like, that was, that was cool when I worked for the ap. And like I, I have teenagers that are old, like older than, so they, I, I think, um. Procurement needs to evolve and we’re gonna help it evolve. We’re gonna push it forward and, and we need to make it more seamless for procurement teams so that we remove those objections. [00:33:38] Matt Y: Uh, I can’t remove the financial engineering objection, like, you know, that’s just life. Um, but I can make it irresponsible not to use marketplace ’cause it’s so easy to use. And, uh, that, that’s kind of the approach we’re taking on, on the front end. Uh, you, you know, I think you, you, again, I didn’t see this question. [00:33:52] Matt Y: You, you stepped into a trap. Un unwittingly, um, PLG is not just is for enterprise. And, and PLG doesn’t necessarily mean pego or self-service. Uh, doesn’t necessarily like, uh, most of our self-service efforts are actually focused on private offers. And not necessarily for pego. Uh, when, when I say self-service and, and PLG, uh, it, it can mean all kinds of things like it. [00:34:14] Matt Y: We have requested private offer, requested demo call to actions, buttons that you can put on your listing. For example, you don’t necessarily need a free trial or a metered pay as you go listing to take advantage of those inbound self-service leads. So, and those inbound self-service leads are often massive enterprise deals, like I mentioned specifically, uh, the data mask. [00:34:31] Matt Y: Those giant enterprise deals that they launched came from an enterprise like Fortune 1000 Enterprise in the US that organically discovered their solution on the marketplace using our AI search. And that was a massive enterprise. And so I, I think yes, there is the long tail, you wanna capture a new logo acquisition, but you should think of your product like growth in your self-service strategy as a way to, um, acquire all kinds of leads, including large enterprise. [00:34:54] Matt Y: And so when I say leave money on the table, I’m not just talking about things that are gonna mature over two years or tiny little deals. These could be massive deals. Uh, and, and you’ll accelerate those deals by accelerating their discovery and, and research so that I think that, so, and my advice is don’t, you don’t have to go all in if you don’t have, if you don’t have metering, if you don’t have PayGo, that’s cool. [00:35:13] Matt Y: Start with something simple. Start with a public listing, with a request to private offer like that. That is a, a huge step. That doesn’t take much, and, and it kind of blows my mind still that a lot of companies aren’t doing that yet. [00:35:25] Vince Menzione: Great answer. Well, it’s now time we’re gonna bring, we’re gonna bring, it’s time. [00:35:29] Vince Menzione: We, we’ve got some great partners coming up here, Nvidia Elastic, Accenture gonna all join us for a conversation. Great. And I’m glad that you’re gonna stay with us. And let’s, let’s, well, let’s thank Matt, by the way, for that session. [00:35:41] Matt Y: Thanks. [00:35:42] Vince Menzione: And [00:35:42] Matt Y: thanks for listening to the Ultimate [00:35:44] Vince Menzione: Partner Podcast. If today’s conversation resonated, share it with a partner leader in your network. [00:35:51] Vince Menzione: Subscribe where you listen. And head over to the ultimate partner.com. For show notes related content and the resources for this episode. And if you haven’t already, now’s the time to register for the Ultimate Partner Live Event in Reston, Virginia, October 26th through October 28th. Until next time, keep showing up in the rooms that matter because being in the room changes everything.

In this episode of Shift AI, Patrick Hillmann, Chief Strategy Officer at Logical Intelligence, joins host Boaz Ashkenazy for a conversation about why the next era of AI cannot be built on probability alone.Patrick shares his unconventional path into AI, from crisis communications and cybersecurity work at Edelman and General Electric, to steering Binance through its most turbulent years and a major DOJ settlement. At Logical Intelligence, Patrick now works alongside Yann LeCun, a Fields Medalist, and engineers from Meta, Google, and Cruise to build deterministic, energy-based reasoning models.Patrick explains why LLMs behave like a confident intern, fast and articulate, but wrong in ways you only catch if you already know the answer, and why critical systems like power grids, hospitals, and self-driving cars need a layer of certainty that probabilistic systems cannot provide. He and Boaz dig into Logical Intelligence's benchmark results, including a 98% score on the notoriously difficult Putnam math competition, and a public Sudoku test where their energy-based model, Kona, beat every major LLM combined while running on a fraction of the compute cost. This episode is essential listening for CTOs, technical leaders, and anyone trying to understand what comes after the current generation of large language models.Chapters[00:00] Patrick's Improbable Path: From Grad School to the Front Lines of a Geopolitical Crisis[02:43] From Binance to Chief Strategy Officer at Logical Intelligence[02:54] The First Paid Job: Unloading UPS Trucks in 100 Degree Heat[04:31] The UPS Lesson That Still Shapes How He Thinks About Work[04:47] Why LLMs Are Confident Guessing Machines, Not Truth Machines[07:14] The Team Behind Logical Intelligence: A Fields Medalist, Yann LeCun, and Math Olympiad Engineers[08:55] Is Logical Intelligence Betting Against LLMs?[10:32] The AI Sandwich: Where LLMs, Reasoning Layers, and World Models Fit[12:36] The Putnam Benchmark and Why Formal Proofs Don't Get Partial Credit[15:44] What Is an Energy-Based Model, Really?[19:54] Eve Badia's 15-Year Path to the Energy-Based Reasoning Model[22:04] Formal Verification and the Future of Secure Code Generation[23:33] When Unverified Code Fails: The Molson Coors Ransomware Story[25:39] Why AI Coding Tools Create Rat's Nests Engineers Can't Debug[28:53] The Sudoku Test: 98% Accuracy for $4 vs $14,000 for the Leading LLMs[31:13] ByteDance, China, and the Race for Formal Methods[33:42] Two Words for the Future of AI: Chaotic Determinism[37:12] Where to Follow Logical Intelligence and Founder Eve BadiaConnect with Patrick HillmannLinkedIn: https://www.linkedin.com/in/crisiscommunicationsConnect with Boaz AshkenazyLinkedIn: https://www.linkedin.com/in/boazashkenazy/Email: info@shiftai.fm

Pat Casey was the first person besides founder Fred Luddy to write code at ServiceNow back in 2005, when it was called Glide and lived above a friend's restaurant. Twenty years later, he's CTO of a company where 85% of the Fortune 500 are customers, and until recently ran all of engineering: 10,000 people, 7,000 of them writing code. Almost nobody survives the journey from first engineer to public-company CTO. Pat did. Tobi and Pat dig into how ServiceNow actually works under the hood: a metadata processing engine running 90,000 single-tenant databases and over 25 billion queries an hour, why they bought a 15-person German database company and turned it into RaptorDB, and why tearing apart a 20-year-old monolith is harder than every senior engineer thinks. Then the conversation turns to AI. Pat bought 7,000 Windsurf licenses and measured a real, but unglamorous, 15% productivity bump, with a small subset of engineers going 5–6x while most barely changed. His thesis: AI coding is like playing five chessboards at once, and it's reshuffling the deck on who the top engineers will be. On agents, ServiceNow's answer is disarmingly simple: create a user called "AI Pat," assign it cases, and make it follow the exact same rules as humans because you should not trust an LLM more than you trust a human being. Topics covered: - From Atari 400 and floppy-disk jockey at Aldus to first engineer at ServiceNow - Scaling engineering from a stuffed fish on a monitor to 10,000 people — and the productivity trough at ~100 engineers - Single-tenant architecture: 90,000 databases, 25B+ queries/hour, and the monolith-to-Kubernetes migration - Why ServiceNow bought Swarm64 and built RaptorDB on a Postgres fork - 7,000 Windsurf licenses, Claude Code, and the real numbers on AI coding productivity - "AI Pat": the anthropomorphic model for enterprise agents outcomes, not toolkits - Whether AI kills seat-based SaaS, and why incumbents may have the inside track - Pat's advice to CTOs: this is not a time for excessive caution

Autonomous AI and agentic AI are moving from experiments into real enterprise workflows. But are businesses truly ready to let AI systems plan, decide and take action on their behalf?In this interview, I speak with Shayan Mohanty, Chief Data and AI Officer at Thoughtworks, about the next phase of enterprise AI and what leaders need to do now to prepare.We explore the shift from AI assistants and copilots to autonomous agents, why governance and accountability need to be built into the architecture, and how enterprises can move beyond proof-of-concept projects toward scalable, production-grade AI systems.Shayan also explains why competitive advantage in the AI era may come less from access to the latest model and more from orchestration, AI-ready data, responsible engineering and the ability to redesign work around intelligent systems.This conversation is essential viewing for CEOs, CIOs, CTOs, CDOs and business leaders who want to understand what autonomous AI means for enterprise transformation, governance, software development and the future of work.If you'd like to explore how enterprises are preparing for this next wave of agentic AI, Thoughtworks' latest white paper, The Agentic Enterprise, offers practical perspectives and real-world insights.  https://www.thoughtworks.com/about-us/partnerships/cloud/aws/building-the-agentic-enterprise-ecosystem?utm_source=organic-influencer&utm_medium=influencer-marketing&utm_campaign=eai_tsi_rp-gl-pspt_rewire-for-agents_2026-05&utm_term=bernard-video-interview&utm_content=video#Sponsored Autonomous AI in the enterpriseAgentic AI and AI agentsAI governance and accountabilityEnterprise AI readinessMoving AI from pilots to productionAI-ready data and orchestrationThe future of software development#AutonomousAI #AgenticAI #EnterpriseAI #AIagents #ArtificialIntelligence #AIGovernance #AITransformation #DigitalTransformation #Thoughtworks #AIworks #FutureOfWork #BusinessTechnology

In this episode with Tamara Tomasevic, Head of Program Development at CIONET Germany, we discuss how cloud, data, and AI are driving digital transformation in supply chains. Tamara shares insights on fostering enterprise intelligence, encouraging cross-functional teamwork, and scaling AI through mindset and skill development. The episode explores leadership strategies and the future of supply chain connectivity and sovereignty.Download the ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠episode transcript⁠⁠⁠⁠⁠⁠===== In this episode Richard and Sin talk with Tamara Tomasevic, Head of Program Development at CIONET Germany, about what really drives digital transformation. From digital sovereignty and exit strategies to re‑architecting processes around enterprise intelligence, Tamara cuts through the hype and gets real about what works. Learn why data quality makes or breaks AI, why mindset matters more than budget, and how leaders can scale AI with confidence in an increasingly complex supply chain world. ===== Guest: Tamara Tomasevic, Head of Program Development at CIONETTamara is Head of Program Development at CIONET Germany, connecting CIOs, CDOs, and CTOs across the country. She is passionate about building strong communities in the digital era. Previously, she helped establish the Bavarian State's AI Network and, as a communication scientist, believes communication is at the heart of digital disruption.Host: Richard Howells⁠⁠⁠⁠⁠Richard Howells⁠⁠⁠⁠⁠ has been working in the Supply Chain Management and Manufacturing space for over 30 years. He is responsible for driving the thought leadership and awareness of SAP's ERP, Finance, and Supply Chain solutions and is an active writer, podcaster, and thought leader on the topics of supply chain, Industry 4.0, digitization, and sustainability.Host 2: Sin ToSin To brings over 15 years of experience in the digital media and technology industry – primarily in marketing, business development, thought leadership, and editorial. At SAP, they ensure that SAP's supply chain solutions are properly visible with a focus on future trends and sustainable innovations as part of the Thought Leadership & Awareness Supply Chain Team.===== Show Links:SAP Digital Supply Chain: www.sap.com/scmCIONET Germany: https://www.cionet.com/cionet-germanyFollow Us on Social Media : Tamara TomasevicLinkedIn: https://www.linkedin.com/in/tamara-tomasevic-community/ Richard Howells:LinkedIn: ⁠⁠www.linkedin.com/in/richardjhowells⁠⁠ Sin To: LinkedIn: ⁠⁠www.linkedin.com/in/sin-to-5334208⁠⁠ SAP Digital Supply Chain:LinkedIn: ⁠⁠www.linkedin.com/showcase/sapdsc/⁠⁠ Please give us a like, share, and subscribe to stay up-to-date on future episodes!  ===== Chapters: 00:00:00 Sovereignty And Resilience00:00:31 Welcome And Power Triangle00:01:07 Meet Tamara And CIONET00:01:59 Digital Leaders Hot Topics00:05:10 Cloud Strategy In Supply Chain00:08:03 Data Quality And Ownership00:09:52 Turning Data Into Assets00:11:20 AI Misconceptions And Use Cases00:14:21 Scaling AI Beyond Pilots00:16:21 Why Networks Matter00:18:42 People Skills And Culture Shift00:20:46 90 Day Action Plan00:22:00 Future Outlook And Wrap Up

In dieser Paneldiskussion live vom TechRiders Summits 2026 beleuchten CTOs und Tech Leads gemeinsam mit Eberhard Wolff, wie KI die Kosten- und Komplexitätswahrnehmung in der Softwareentwicklung beeinflusst – von dem Versprechen einer “billigen” Umsetzung bis zu den verborgenen Risiken. Die Diskussion adressiert zentrale Fragen: “Billiger” vs. “einfacher”: Was steckt hinter diesen Begriffen? “Einfacher” ist nicht gleichbedeutend mit schneller oder wartungsfreundlich – vielmehr entstehen neue Abhängigkeiten von Drittanbieter-APIs, die Wartung komplexer machen. Versteckte Kosten der KI: Die Illusion einer kostengünstigen KI-Lösung ignoriert oft unsichtbare Aufwände – etwa für Modell-Training, Monitoring, Compliance (z. B. DSGVO), QA und Lizenzabhängigkeit von Anbietern. Team & Kompetenzen: KI verändert die Rollen von Architekt:innen – weg von reiner Code-Optimierung hin zu KI-Management und ethischer Bewertung. Während Junior-Entwickler:innen vermeintlich durch KI-Assistenten profitieren, droht der Wissenstransfer zu erodieren, wenn KI “Black Boxes” für Entscheidungen nutzt. Strategische Grenzen: Lohnt sich KI aus architekturhistorischer Sicht? Welche Prinzipien (z. B. Modularität, Observability) bleiben unverändert, um Systeme auch im KI-Zeitalter kontrollierbar und skalierbar zu halten? Gäste aus dem Speaker Line-Up des TechRiders Summit: Sebastian Kleinschmager Axel Schulz

When companies mandate AI adoption without a use case, without a strategy, and without a business outcome in mind, they don't get transformation. They get jazz hands and nightmare token bills.This month's System Update pulls apart what's actually happening beneath the headlines: Oracle's 21,000 layoffs attributed to "AI adoption," Amazon arming junior developers to replace senior engineers, and enterprises burning through AI budgets they cannot predict or control.The deeper argument George K. and George A. make is harder to dismiss than the headlines. You cannot drive deterministic business outcomes with probabilistic means of production. The CEOs and CTOs who greenlit LLM adoption at scale are now facing a math problem that no earnings call language can paper over.The free water is now a metered utility. Will the bill ever be worth paying?The episode also turns to labor theater and what we're giving our attention to: what we lose when institutions optimize for engagement over depth, and what it costs when an entire generation learns to consume rather than think.Mentioned: NYT on Schneider Electric's AI adoption without layoffs Amazon tokenmaxxing mandate goes sideways Oracle sheds 13% of its workforce amid so-called AI adoption Amazon still hiring junior employees while also doing layoffs…? The Intellectual Life of the British Working Classes, by Jonathan Rose Snap's intentional targeting of teens' attention Denmark invests in de-screening its schools

Daniel Crook, founder of School Harbor and co-founder of AEG Systems, joins Dr. Michael Conner for a direct, infrastructure-first conversation about what K–12 districts are getting wrong about AI adoption.Daniel has spent years working inside the systems that districts rely on to manage data, make decisions, and integrate technology at scale. His assessment is clear: the AI problem in education isn't a platform problem, it's a foundation problem. Too many districts are evaluating AI tools before they've built the data infrastructure that would allow those tools to function effectively.In this episode, Daniel walks through why the data warehouse is the non-negotiable starting point, what interoperability actually requires in practice, not in theory, and the three criteria every district leader should apply before selecting or expanding any AI platform. He also introduces the concept of AI sobriety: an implementation philosophy that grounds strategy in the technology's current capabilities rather than its projected future state.The conversation also touches on the Netflix analogy for understanding where edtech sits in the broader AI development cycle, and why the districts building administrative intelligence now will have a significant structural advantage over those still chasing student-facing tool count.A grounded, no-hype episode for superintendents, CTOs, instructional technology leads, and anyone responsible for AI strategy in K–12 education.Episode 127 | Voices for Excellence

In this episode of the Shift AI Podcast, Cynthia Tee, former CTO of Smartsheet, joins host Boaz Ashkenazy for a wide-ranging conversation on what it really takes to integrate AI at enterprise scale responsibly, securely, and in a way that earns lasting customer trust.Cynthia shares her unconventional journey from growing up in Manila and working her first job at a library at age 12, to earning a computer science degree from MIT, building her career at Microsoft, running Ada Developers Academy, and ultimately leading engineering at Smartsheet through one of its most consequential chapters, including the company's transition from public to private and the rollout of its first generation of AI-powered features.The conversation dives deep into how Smartsheet approached AI integration: using generative AI to simplify formula generation and data visualization, being deliberate about what information was and wasn't sent to LLMs, and communicating transparently with enterprise customers who needed to trust the system before they would adopt it. Cynthia explains why trust, governance, and data classification aren't afterthoughts, they're the foundation that makes AI deployment possible at scale.Boaz and Cynthia explore the emerging role of MCP in connecting LLMs like Claude to applications like Smartsheet, translating user intent into real-world action across complex workflows. They also get into what SaaS executives often underestimate: that shipping AI features is the easy part, and evolving the rest of the organization, pricing, enablement, customer support, and role definitions is where companies get stuck.The discussion turns to the next generation of workers and the genuine tension young people face between learning a craft and leaning on AI to accelerate it. Cynthia shares a perspective on hustle, curiosity, and what it looks like when someone who's never written a line of code builds an inventory system for vintage clothing because a tool like Claude made it possible.This episode is essential listening for CTOs, engineering leaders, and product executives who want to understand what responsible AI deployment actually looks like inside a company operating at scale.

For more thoughts, clips, and updates, follow Avetis Antaplyan on Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/avetisantaplyan⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠In this solo episode of The Tech Leader's Playbook, Avetis Antaplyan explores one of the most overlooked yet critical leadership skills: decision-making. Drawing on insights from conversations with CEOs, CTOs, founders, professional athletes, Hall of Fame coaches, and executives from companies including Apple, Google, Amazon, National Geographic, and Radical Candor, Avetis breaks down what separates exceptional leaders from everyone else.He argues that leadership success is rarely about having perfect information, superior intelligence, or flawless strategy. Instead, the leaders who consistently create momentum are those who can make sound decisions despite uncertainty. Avetis shares practical frameworks used by high-performing leaders, including Amazon's "one-way door vs. two-way door" decision model, Jeff Bezos' regret minimization framework, and the importance of principle-based decision-making.The episode also examines how AI is changing the leadership landscape. While artificial intelligence can accelerate analysis and provide recommendations, Avetis explains why human judgment, accountability, and courage remain irreplaceable. Through real-world examples and actionable leadership lessons, he challenges listeners to identify the decisions they've been avoiding and take decisive action before delays become the real obstacle to progress.TakeawaysExceptional leaders distinguish themselves through decision-making, not intelligence alone.The greatest organizational threat is often indecision, not making the wrong decision.Most leadership decisions must be made with incomplete information.Leaders are paid for their ability to navigate uncertainty and create momentum.A mediocre decision made quickly often outperforms a perfect decision made too late.Amazon's "one-way door vs. two-way door" framework helps determine when to move fast and when to proceed carefully.Great leaders commit fully after making a decision rather than remaining trapped in doubt.Principle-based decision-making allows leaders to make consistent decisions faster.Technology leaders often make the mistake of optimizing for technical perfection instead of business outcomes.AI can provide information and recommendations, but accountability and judgment remain human responsibilities.When a decision is inevitable, delaying it often causes more damage than acting on it immediately.Chapters00:00 Why Decision-Making Separates Great Leaders01:12 The Myth of Intelligence and Leadership Success02:13 Why Indecision Damages Organizations03:25 Amazon's One-Way Door vs. Two-Way Door Framework04:38 Lessons from Hall of Fame Coach Dick Vermeil05:15 Radical Candor and the Courage to Act05:55 Technology Leaders and Business Outcomes06:30 Framework #1: Speed Over Perfection07:00 Framework #2: Regret Minimization08:00 Framework #3: Reversible vs. Irreversible Decisions08:55 Framework #4: Principle-Based Decision Making09:55 Why AI Makes Judgment More Valuable11:05 Creating Momentum Through Action11:40 The Decisions You're Avoiding Right Now12:10 When It's Inevitable, Make It Immediate12:45 Closing Thoughts and Final TakeawaysResources and Links:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.hireclout.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.podcast.hireclout.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/hirefasthireright⁠

Charlie Fink, Ted Schilowitz, and Rony Abovitz take the full hour to work through the most consequential AI and spatial computing stories of the moment — unfiltered, in depth, and without the usual polite hedging that comes with having someone on to promote something. This is a pure news and commentary episode, and the news is strange enough that three experienced people sitting in a room still cannot fully account for it.AI XR News You Should Know:The OpenAI vs. Elon Musk case concluded without a clear ruling, but the more durable observation is what the whole saga revealed about Sam Altman. He has now survived being ousted by his own board (which he subsequently dismantled), a high-profile lawsuit from Elon Musk, and senior rivals leaving for government roles. Rony frames this through the Overton window — Altman studies what society is prepared to accept at any given moment and positions himself precisely there. Ted references a New Yorker profile that describes Altman as having a politician's gift for telling people what they want to hear until it becomes true. The financial architecture underneath the AI boom looks precarious on close inspection. SpaceX, widely assumed to be profitable, is losing five billion dollars a year. Anthropic is spending three dollars for every dollar of revenue it generates — and is paying SpaceX approximately one billion dollars a month for compute through roughly 2030. Rony's framing lands hard: two money-losing entities are funding each other while NVIDIA captures all the margin in between. Sequoia published a fifty-page analysis arguing the economics cannot work — while simultaneously holding positions in the companies it is critiquing. Google I/O delivered less on wearables than expected, but the real story was a deliberate strategic decision to put Gemini at the center of the company's entire product surface — effectively cannibalizing an eighty-two-billion-dollar search business before a competitor does it for them. The Innovator's Dilemma, run on purpose. On the hardware side, Android XR glasses are designed to be imperceptible as technology — thin temples, hidden camera portals, frames that belong in an optometrist's display case rather than a trade show floor. Rony notes that Google's glasses almost certainly incorporate Magic Leap optics, following a partnership announced in fall 2025. [00:00] – Cold open and episode framing: why there is no guest today and what the trio plans to cover.[04:15] – OpenAI vs. Elon Musk non-verdict: what the outcome (and lack of one) actually reveals.[09:30] – Sam Altman and the Overton window: Rony's read on how Altman has survived everything thrown at him.[16:00] – Anti-AI backlash on campuses: Eric Schmidt booed at University of Arizona, YouGov poll showing 69 percent of young people negative on AI, and what the demographic gradient means.[24:45] – SpaceX financials and the AI funding loop: the five-billion-dollar annual loss, Anthropic's burn rate, and Charlie's Ponzi scheme framing.[33:20] – Sequoia's fifty-page report and the ad model endgame: Ted's argument that Google wins because they already know the business model.[41:00] – Google I/O: the deliberate destruction of the search business, Android XR glasses, and why distribution beats specifications.[49:10] – AI accountability and the airplane analogy: Ted's line, Rony's "underground noise" from generals and CTOs, and the problem of regulatory vocabulary.[55:30] – Palantir, dual-use opacity, and the Lookout Mountain Air Force Station story: Rony on Jared Leto, classified film studios, and Cold War bunkers in Laurel Canyon.[01:01:00] – The success ledger: who is measuring impact, and what should actually count as winning.This episode is sponsored by Zappar and Mattercraft. Mattercraft is Zappar's web-based platform for building augmented reality experiences without an app. Find them at mattercraft.io. Hosted on Acast. See acast.com/privacy for more information.

In this episode of The Broadband Bunch, host Pete Pizzutillo sits down with Rob Lawrence, Technology Strategist at Microsoft, to separate the reality of agentic AI from the growing hype surrounding autonomous systems. As organizations race to experiment with AI agents, Rob argues that the biggest challenges aren't the models themselves—they're the operating environments, governance frameworks, data quality, accountability structures, and organizational readiness required to deploy them successfully. Pete and Rob discuss why many AI pilots succeed while production deployments struggle, the return of disciplines like project portfolio management and process engineering, and why data governance may be the most important prerequisite for successful AI adoption. Rob also talks about the role of identity and permissions, the risks of poorly governed agents acting on flawed data, and why organizations need better observability into AI-driven workflows. Along the way, he shares advice for CIOs, CTOs, and broadband operators looking to move beyond experimentation and build a responsible foundation for agentic AI.

Kishore Ravilla: How CTOs Influence Business DecisionsKishore Ravilla is a CTO with 25 years of leadership across healthcare, insurance, and financial services. In this episode, we explore how technology leaders can better communicate with business stakeholders, why storytelling matters in digital transformation, and how strong execution and operational excellence create lasting business value. To learn more about Kishore, visit https://www.linkedin.com/in/kishoreravilla/__TEACH THE GEEK (http://teachthegeek.com) Prefer video? Visit http://youtube.teachthegeek.comGet Public Speaking Tips for STEM Professionals at http://teachthegeek.com/tips

Rory O'Neill, CMO of Checkout.com, doesn't just solve for payments- he's solving for brand preference in a crowded payments space. And he's doing it by competing on what's different, not what others do better. That insight changes everything, from how you position payments to how you build a team that can sustain growth as a challenger. In the latest episode of Scratch, Rory breaks down the playbook that lets Checkout compete with global giants. Brand preference wins 95% of B2B deals before salespeople ever show up- so your marketing owns the invisible 60% of the buyer's journey. Challenger brands win by picking one fight and building culture around it, not chasing everything competitors do. He reveals the three-part formula: focus your core business, build your culture, reinvest profit. Consumer marketing skills-data, insight, action-are B2B's secret superpower. And his rule: if you wouldn't say it at dinner, don't write it in marketing. The key takeaway: Brand preference wins deals - 95% of the time, the brands on the day-one top-five list are the ones that win. B2B buyers spend 60% of their journey before contacting a salesperson. Define your focus as a challenger - Compete on what's different, not on what competitors do better. Checkout only does digital payments to stay focused while competitors spread across multiple business lines. Three elements beat category norms - Focus on your core business, build the human operating system (culture, people, vision), then reinvest capital in new products. Consumer marketer skills are powerful in B2B - Data, insight, action, brand building, and performance marketing from the consumer world unlock B2B success. Understand stakeholder maps - B2B is complex: CTOs influence CFOs, recommenders influence buyers. Map those relationships to win. Simplify your language - Ditch jargon like "frictionless" and "seamless." Use words you'd use at dinner. Marketing becomes more interesting and understood. Marketing is logic and magic - Be both data-driven and creative. Avoid letting fiefdoms kill integrated work. Join everything together. Watch the video version of this podcast on Youtube ▶️: https://youtu.be/chR0mn9Pum0 Scratch is a production of Rival, a marketing innovation consultancy that develops strategies and capabilities that help businesses grow faster. Scratch is hosted by Eric Fulwiler, and he's joined by Rory O'Neill of Checkout.com in this episode. Find Rival online at www.wearerival.com, LinkedIn  Find Eric on LinkedIn Find Rory on LinkedIn  Say hi at media@wearerival.com, we'd love to hear from you. Rival is a marketing consultancy for brands that want to challenge convention in their category. We're on a mission to understand what challenger brands do differently to grow in categories that are being disrupted, and use a challenger playbook to deliver outsized impact through an integrated, tech-enabled approach. Past guests include CMOs from Mastercard, GE, Shell, Hyperloop, Adobe, PepsiCo, and Papa Johns.If you're interested in learning more about marketing from successful CMOs, we compiled a list of the top 5 CMO podcasts to listen to in 2024; check it out here

In this episode of Future Finance, Paul Barnhurst and Glenn Hopper sit down with Dave Trier, CEO of ModelOp, to discuss how enterprises can govern, manage, and operate AI at scale. Dave shares insights on implementing AI responsibly, tracking ROI, managing risks, and creating an enterprise-wide AI portfolio that drives value while ensuring compliance and governance.Dave Trier leads ModelOp with a focus on customer value, product innovation, and enterprise execution. With over 20 years in data science, AI, analytics, cloud, and enterprise software, he brings technical expertise and a pragmatic leadership style, helping CIOs, CTOs, and AI leaders deploy AI effectively across organizations .In this episode, you will discover:How enterprises can scale AI responsibly and reliablyThe CFO's role in AI oversight and portfolio managementMeasuring AI value through ROI, usage, and internal feedbackDistinctions between AI governance and traditional data governanceImportance of change management and structured AI adoptionDave provides a framework for enterprise AI adoption, emphasizing disciplined management, measurable impact, and alignment with regulatory and operational requirements. This episode is essential for finance and tech leaders looking to integrate AI at scale while ensuring oversight, efficiency, and business value . Follow Dave:Website: https://www.modelop.com/LinkedIn: https://www.linkedin.com/in/davidetrier/Follow Glenn:LinkedIn: https://www.linkedin.com/in/gbhopperiiiFollow Paul:LinkedIn: https://www.linkedin.com/in/thefpandaguyFollow QFlow.AI:Website - https://bit.ly/4i1EkjgFuture Finance is sponsored by QFlow.ai, the strategic finance platform solving the toughest part of planning and analysis: B2B revenue. Align sales, marketing, and finance, speed up decision-making, and lock in accountability with QFlow.ai. Stay tuned for a deeper understanding of how AI is shaping the future of finance and what it means for businesses and individuals alike.In Today's Episode:[00:00] – Trailer[02:38] – AI Compliance & Governance Challenges[04:35] – Distinction Between AI & Data Governance[07:28] – Measuring AI Value & ROI[12:41] – Treating AI as a Portfolio of Investments[15:05] – Change Management & Enterprise Adoption[17:39] – Wild West of AI & Need for Rigorous Processes[18:54] – CFO Oversight in AI Implementation[21:00] – Closing Remarks

Most enterprises are renters, not owners, of their technology and AI. Raffi Krikorian, Chief Technology Officer of Mozilla, explains why dependence on a handful of closed model providers means losing control over model behavior, pricing, and your own data.In CXOTalk episode 920, Krikorian lays out where open-source AI actually wins in the enterprise, how lock-in happens quietly, and what CIOs and CTOs should do about it now. Krikorian draws on his experience building infrastructure at Twitter and running the self-driving division at Uber to ground the discussion in real engineering and economic tradeoffs, not hype.YOU'LL DISCOVER✅ Why 85% of enterprises believed they could switch AI vendors, but only about 30% actually could when they tried✅ The "renters vs. owners" framing and what it means to control your AI destiny✅ Why Krikorian wants data "protected by architecture, not legal handshakes"✅ How Pinterest reportedly saved on the order of $10 million in a single quarter by switching from closed to open models✅ Why IT is becoming "the HR team for agents," and the read/write "dangerous triangle" of agentic permissions✅ The case for recording your prompts and running your own evaluations instead of trusting public benchmarks✅ Why roughly 70% of enterprise GPUs sit idle, and the missing "LAMP stack for AI" that could put them to work✅ How closed "validation machines" can quietly steer answers toward sponsored outcomes⏱️ TIMESTAMPS (estimated, verify before publishing)0:00 Renters vs. owners: who controls enterprise AI2:26 The risks of depending on closed model makers6:23 How lock-in happens and where open source fits9:53 Regression testing and building your own evals13:24 Pricing instability and the post-IPO cost question23:31 Governance: IT as HR for AI agents32:38 Can a small organization own its AI stack end-to-end?38:47 Validation machines, trust, and sponsored answers43:39 Keeping humans at the center, not in the loop47:23 Can open source beat big tech in AI?51:39 Inside Mozilla.ai: Otari, CQ, Octanus, Thunderbolt55:21 The "rebel alliance" strategy

What does it take to go from helping millions of people breathe easier to helping patients keep their legs?   Join The Heart of Innovation as Kym McNicholas talks with Sarvajna Dwivedi, Ph.D., entrepreneur, inventor, and CEO of AngioSafe, whose career has spanned some of the most challenging problems in medicine.   Sarvajna co-founded Pearl Therapeutics, a company focused on breakthrough respiratory therapies that was ultimately acquired by AstraZeneca for $1.15 billion. Along the way, he helped develop inhaled therapies and drug-device combinations designed to improve the lives of patients with asthma and COPD. (AngioSafe United States)   Today, his focus has shifted from the lungs to the arteries.   As CEO and co-founder of AngioSafe, Sarvajna is leading the development of the Santreva-ATK Endovascular Revascularization Catheter, a novel device designed to restore blood flow through some of the most challenging chronic total occlusions (CTOs) physicians encounter in patients with peripheral artery disease (PAD). The technology is designed to cross completely blocked arteries, compress plaque, create a new channel, and restore blood flow without relying on a guidewire or external power source. (Medical Economics)   In this episode, we discuss:   • How a pharmaceutical scientist became a medical device innovator   • The story behind Pearl Therapeutics and its $1.15 billion acquisition   • Why chronic total occlusions remain one of the biggest challenges in PAD treatment   • How AngioSafe's Santreva-ATK technology works   • What it means to restore blood flow through arteries that are 100% blocked   • The future of cardiovascular and vascular innovation   If you or someone you love has peripheral artery disease, diabetes, leg pain while walking, non-healing wounds, or has been told an artery is completely blocked, this is a conversation you won't want to miss.  

In this episode of the Finovate podcast, host Greg speaks with Oren Buskila, CEO and co-founder of Cobalt, a FinovateSpring 2026 Best of Show winner. Cobalt has developed enterprise architectural intelligence specifically designed for financial institutions, addressing a critical challenge in modern banking: the lack of understanding of complex system dependencies.Banks operate on enormously intricate systems comprising their own code and dozens of third-party vendor applications, yet most institutions don't fully comprehend how these systems interconnect and depend on one another. This knowledge gap leads to significant problems, including development slowness—with banks spending 70% of their IT budgets on maintenance rather than innovation—and costly production failures that can result in millions of dollars in direct and indirect costs when changes are deployed without full visibility into system dependencies.Cobalt's solution automatically maps both IT systems and business processes in real-time by scanning existing data sources including event logs, API logs, code, and database tables. The platform creates a comprehensive topology map that aligns business processes with their underlying technical infrastructure, allowing banks to see exactly which systems support which business functions and understand the full impact of any proposed changes. This "bank on a page" architecture view enables technical teams to anticipate the consequences of modifications before implementation, preventing failures and ensuring safer deployments. The platform maintains a live, continuously updated view of the system architecture by taking frequent snapshots that can be compared to detect changes and investigate issues, a capability that was previously impossible with manual architecture mapping methods.The demo at FinovateSpring resonated strongly with attendees, particularly technical leaders like CIOs and CTOs from medium and large banks who recognized the transformative potential of having complete visibility into their systems. The presentation also attracted significant interest from venture capitalists and leaders from smaller banks and credit unions, the latter group seeing opportunities to introduce agentic AI into their operations by first mapping existing business processes. Looking ahead, Cobalt positions itself as the essential architectural layer for AI-driven development in banking, as the industry moves toward having AI agents generate, maintain, and modify code at unprecedented velocities—a shift that will require the contextual understanding and change management capabilities that Cobalt provides.More info:Cobalt AI: https://www.getcobalt.ai/; https://www.linkedin.com/company/getcobalt/Oren Buskila: https://www.linkedin.com/in/oren-buskila/Greg Palmer: https://www.linkedin.com/in/gregbpalmer/Finovate: https://www.finovate.com; https://www.linkedin.com/company/finovate-conference-series/FinovateSpring: https://informaconnect.com/finovatespring/#Finovate #FinovateSpring #Banking #banks #creditunions #personalization #data #communitybanks #AI #backoffice #corebanking #digitaladoption #podcast #fintechpodcast #financialservices #innovation #digitraltransformation #fintech #finserv #modernization

In this episode of Future Finance, Paul Barnhurst and Glenn Hopper sit down with Dave Trier, CEO of ModelOp, to explore the challenges and opportunities of implementing AI at scale in enterprises. Dave shares how organizations can manage AI responsibly, measure ROI, and move from scattered pilots to a disciplined, industrialized approach. He also discusses the critical role of CFOs in AI oversight, change management, and creating measurable business value from AI initiatives Dave Trier is CEO of ModelOp, leading the company with a focus on customer value, product innovation, and enterprise execution. With over 20 years of experience across AI, data science, analytics, cloud, and enterprise software, Dave is a patent-holder and trusted partner to CIOs, CTOs, and AI leaders. Prior to becoming CEO, he shaped ModelOp's product strategy and held senior roles at Think Big Analytics, Powered by Action, and Accenture Technology Labs. He holds a BS in Electrical Engineering from the University of Notre Dame. In this episode, you will discover:How to industrialize AI delivery across an enterpriseManaging risk, governance, and compliance for AI implementationsMeasuring AI ROI using financial, feedback, and usage metricsThe CFO's role in AI oversight and rationalizing AI investmentsKey lessons for change management and process discipline in AI adoptionDave Trier highlights how enterprises can move from scattered AI pilots to a disciplined, industrialized approach that delivers measurable business value. He emphasizes the importance of governance, change management, and cross-functional collaboration to ensure AI initiatives succeed. CFOs play a key role in oversight, setting financial parameters, and rationalizing AI investments. Follow Dave:Website: https://www.modelop.com/LinkedIn: https://www.linkedin.com/in/davidetrier/Follow Glenn:LinkedIn: https://www.linkedin.com/in/gbhopperiiiFollow Paul:LinkedIn: https://www.linkedin.com/in/thefpandaguyFollow QFlow.AI:Website - https://bit.ly/4i1EkjgFuture Finance is sponsored by QFlow.ai, the strategic finance platform solving the toughest part of planning and analysis: B2B revenue. Align sales, marketing, and finance, speed up decision-making, and lock in accountability with QFlow.ai. Stay tuned for a deeper understanding of how AI is shaping the future of finance and what it means for businesses and individuals alike.In Today's Episode:[00:00] – Trailer[02:07] – Meet Dave Trier, CEO of ModelOp[04:57] – ModelOp & AI Governance Explained[06:21] – AI vs Data Governance[08:11] – Evaluating AI ROI for CFOs[13:24] – AI as a Managed Investment Portfolio[16:43] – Change Management & Process Discipline[20:48] – CFO's Role in AI Oversight[27:38] – Tips to Maximize AI ROI[30:16] – Enterprise AI Complexity & Coordination[32:13] – Dave's Journey: Electrical Engineer to AI CEO[35:12] – Closing Thoughts

In this episode of The New P&L TO THE POINT, Paul explores the growing conversation around AI that increasingly positions it as an ‘existential crisis' for businesses and society.Drawing on insights from dozens of executive roundtablesheld across the UK and Europe with CIOs, CTOs, CMOs, HR leaders and transformation executives, Paul reflects on how the AI conversation has evolved at remarkable speed. In just a couple of years, organisations have rapidly shifted from asking What is AI? to How do we deploy it? and now increasingly Why are we using it in the first place?At the heart of the discussion is a critical observation: many organisations approached AI implementation in reverse order. Businesses rushed into experimentation and deployment before establishing strategic clarity around purpose, culture and long-term impact. According to Paul, this is where the real challenge lies.Rather than focusing solely on future fears around AGI orsuperintelligence, this episode argues that today's AI crisis is more immediate and human: a leadership, capability and adaptability crisis. AI is not simply another technology tool; it is transformational and foundational, requiring organisations to rethink leadership, culture, communication and workforcedevelopment.Paul also examines how AI acts as a mirror for organisational health, exposing weak leadership, fragmented data, siloedcultures and poor communication. Without clear vision, employee trust and meaningful upskilling pathways, businesses risk creating fear, disengagement and resistance internally.Ultimately, this episode challenges leaders to rethink their relationship with AI: not as a transactional solution, but as a force that will fundamentally reshape the nature of work, organisations and leadership itself. Those who fail to adapt may face their own existential crisis far sooner than the technology does.To discuss the topics outlined in this episode on moredetail, email: hello (at) principlesandleadership.com To learn more about The New P&L and the work we do, goto: ⁠⁠⁠www.principlesandleadership.com

Most sales teams are reactive — waiting for buyers to fill out a form, book a demo, or respond to an email. Tal Peretz, co-founder and CEO of OnFire AI, is building the infrastructure to change that. OnFire monitors millions of public signals across Reddit, Stack Overflow, LinkedIn, Slack, and technical forums to identify high-intent buyers before they ever contact your sales team.In this episode, Tal breaks down how AI is transforming go-to-market for companies selling to technical buyers — CTOs, CISOs, and engineers — who notoriously resist generic outreach and respond only to context-rich, well-timed conversations. Tal shares his journey from engineer to CEO, how he and his co-founder interviewed 275 revenue leaders before writing a line of code, what it's really like to raise a $20M seed round, and the hard-won lessons of learning to sell as a first-time founder. From ICP discovery and outcome-based pricing to the future of AI in sales, this is a masterclass in signal-driven, intent-based revenue growth.Key Takeaways0:00 — Why most sales teams miss buyers who are already signaling intent publicly2:07 — Intro to Tal Peretz: Co-founder & CEO of OnFire AI3:56 — The origin story: 275 revenue leader interviews before building the product4:36 — How OnFire works: Capturing public web signals, de-anonymizing prospects, and delivering real-time context to sales teams6:25 — Why selling to CTOs, CISOs, and engineers is uniquely difficult — and uniquely valuable7:36 — The 50-million-engineer insight: Turning public technical conversations into revenue intelligence10:04 — What true AI ROI looks like: efficiency gains + directly attributed pipeline11:15 — The 4X pipeline result: What customers see in their first quarter with OnFire11:52 — Speed + personalization + human touch: Why all three are required for signal-based outreach13:03 — Raising a $20M seed round and what hypergrowth pressure really means13:47 — What makes a great investor: shared values, chemistry, and true partnership in hard moments15:59 — Managing pressure: Working backwards from a 24-month North Star to break goals into milestones17:07 — Building vs. selling: What was harder in the early days17:59 — An engineer who learned to love sales: How Tal found his passion for closing deals19:21 — The ICP trap: Why selling to everyone early is the most costly mistake a founder makes20:51 — The outbound playbook: Cold calling, LinkedIn, and the "stealth company" message that landed their biggest customers22:10 — The consulting approach: Why leading with curiosity instead of a pitch built their enterprise pipeline24:41 — The three-layer go-to-market machine: Brand, field/events, and outbound working together26:45 — Selling six-figure enterprise deals: Going on-site, acting as a partner, not a vendor28:51 — Staying focused in a crowded AI market: The "build on top of the platform" rule30:02 — Building go-to-market teams as a technical founder: The hardest challenge32:14 — The biggest AI pricing mistake: Why outcome-based pricing is the future35:03 — Sales-led vs. product-led growth: How Tal thinks about when and how to make the shift38:09 — The future of go-to-market: How AI eliminates the 80% of busy work reps do today40:53 — The one thing founders must nail to break through from product to real revenue41:38 — Where to find Tal and OnFire AITweetable Quotes"We monitor the public web for signals — competitors, pain points, product mentions — and surface them to your sales team in real time. Your buyers are already talking. You just have to listen." — Tal Peretz"It's not about quantity. It's about the quality of the data. Act fast, personalize based on the pain point, and always keep the human touch in the loop." — Tal Peretz"We take your existing team and infrastructure and make the pipeline 4X better — not by adding headcount, but by giving them the right signal at the right moment." — Tal Peretz"Every revenue is not good revenue. Nail your ICP first — where you see the biggest pain, the best retention, and the growth potential — then press the pedal." — Tal Peretz"The best investors aren't just writing checks. When something breaks — and something always breaks — that's where you find out if you have a true partner." — Tal Peretz"AI will eat the 80% of the sales rep's day that is busy work. The reps who win will be the ones who know how to leverage those tools and still build real relationships." — Tal Peretz"Outcome-based pricing is the future. Align what your customer pays with the value they actually receive — then you're never fighting about ROI again." — Tal Peretz"We started with outbound and a simple message: 'I'm a stealth founder. I want to learn from your experience.' No pitch. Just curiosity. Our biggest customers today came from that exact message." — Tal PeretzSaaS Leadership Lessons1. Validate the market before you build the product. Tal and his co-founders interviewed 275 revenue leaders before writing a single line of code. They didn't fall in love with a solution — they found the problem first. For early-stage founders, this discipline separates products that get traction from ones that get ignored.2. Your ICP is not a marketing decision — it's a survival decision. Selling to every prospect early feels like progress, but it's a trap. Tal's hard-won insight: identify the customers with the biggest pain, the highest retention potential, and the best growth trajectory early, then build everything around them. Chasing the wrong customers burns runway and muddies your product roadmap.3. Great investors are chosen for the downside, not the upside. When everything is working, any investor looks great. The real test comes when something breaks. Tal defines great investors by shared core values, authentic chemistry, and willingness to engage as a true partner — not just a capital source — when the hard moments arrive.4. Act like a consultant before you act like a vendor. OnFire's biggest enterprise wins came from going on-site, meeting the full revenue team, mapping the customer's strategic goals, and co-designing a plan — before ever talking contract. For founders selling complex, high-ACV solutions, acting as a partner rather than a vendor changes the entire sales dynamic.5. Outcome-based pricing aligns your success with your customer's success. Charging by seat or token puts you in constant translation mode — always proving value. Pricing tied to outcomes (pipeline generated, conversations resolved, deals influenced) makes the value self-evident and creates a partnership, not a vendor relationship. The companies doing this best in AI are winning stickier, larger contracts.6. The future sales rep is an AI orchestrator, not a data processor. Today's reps spend ~80% of their time on research, sourcing, and admin — not selling. AI will progressively eliminate that 80%. The reps who thrive won't be those who resist the change, but those who master AI tooling and redirect all of their energy to the irreplaceable human skill: building trust and closing deals.Guest Resourcestal@onfire.aihttps://onfire.aihttps://www.linkedin.com/in/tal-peretz/instagram.com/peretztalx.com/TalPeretz13Episode SponsorThe Futureproof Series - https://www.youtube.com/playlist?list=PLfkXKUPZ5xuOqMPR7_gzGybncTtavyR1NThe Captain's KeysSmall Fish, Big Pond – https://smallfishbigpond.com/ Use the promo code ‘SaaSFuel'Champion Leadership Group – https://championleadership.com/SaaS Fuel ResourcesWebsite - https://championleadership.com/Jeff Mains on LinkedIn - https://www.linkedin.com/in/jeffkmains/Twitter - https://twitter.com/jeffkmainsFacebook - https://www.facebook.com/thesaasguy/Instagram - https://instagram.com/jeffkmains

For more thoughts, clips, and updates, follow Avetis Antaplyan on Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/avetisantaplyan⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠In this solo episode of The Tech Leader's Playbook, Avetis Antaplyan breaks down what he calls “The Great White Collar Compression”, the growing disconnect between a strong-looking economy and the pressure many white-collar professionals are feeling in real time.Avetis explores why corporate profits, AI investment, and stock market strength are not translating into the hiring booms many workers expected. Instead, companies are flattening teams, raising performance expectations, slowing hiring, and demanding more output from fewer people. Drawing from his perspective inside the hiring market, Avetis explains how AI, remote work abuse, salary inflation, and shifting leadership priorities are reshaping the future of work.He shares candid stories from conversations with CTOs, candidates, and professionals who feel uncertain about their roles despite working at successful companies. The episode also digs into the decline of the “comfortable middle,” the rise of hybrid roles, the need for AI fluency, and why adaptability may now be the most valuable career currency.This episode is a direct, practical warning and roadmap for leaders and professionals who want to stay relevant, valuable, and hard to replace.TakeawaysThe economy can look strong while white-collar workers still feel pressure.AI investment is increasing productivity without creating proportional hiring.Companies are flattening teams and cutting unnecessary management layers.Average performance is becoming more vulnerable in the modern workplace.Remote work abuse and inflated salaries contributed to employer distrust.Hiring is slower because companies now expect rare hybrid skill sets.Professionals need to get closer to revenue, customer impact, and business outcomes.AI fluency is no longer optional for most white-collar roles.Adaptability and learning velocity are becoming premium career skills.Building a reputation matters more than relying on a resume alone.The future belongs to builders, operators, and people willing to evolve quickly.Chapters00:00 Introduction to the Great White Collar Compression02:36 Why Traditional Hiring Growth Is Changing05:00 Fewer Layers, Higher Expectations, and AI Pressure07:20 Why Workers Feel Weak Despite a Strong Economy09:43 Hiring Freezes, Salary Pressure, and Market Uncertainty11:46 Efficiency, Profitability, and Leaner Operations12:49 The Death of the Comfortable Middle14:55 Why Hiring Feels Broken Right Now17:19 The Rise of Team-Elevating Talent20:03 Adaptability as the New Career Currency22:28 Getting Closer to Revenue and Business Outcomes24:50 Building Hybrid Skills and Becoming Indispensable27:13 Reputation, Network, and Proof of Work28:40 Final Thoughts on the Future of White-Collar WorkResources and Links:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.hireclout.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.podcast.hireclout.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/hirefasthireright⁠

Background checks sound straightforward. Until you try to build the infrastructure behind them at scale. In this episode of CTO Confessions, TC Gill sits down with Luca Bonmassar, CTO of Checkr — a platform that helps millions of people find meaningful work and helps companies hire with confidence. Luca brings over 20 years of experience across Fintech, Crypto, Social Media, and AI/ML, and has co-founded and sold three startups. He's one of the rare CTOs who moves as comfortably in a business conversation as a technical one. In this episode: → Why understanding the business side isn't optional for a CTO → The surprising complexity of data that still exists only in physical form → Why hiring fast and firing faster may cost you more than you think → His philosophy on over-engineering — and why patience often wins "It's better to be late knowing that what you build will have greater impact than building things and hoping someone will use them one day."

In this episode of the AI at Health series on The Beat Podcast, host Sandy Vance sits down with Venky Ananth, Executive Vice President and Head of Healthcare at Infosys, for a wide-ranging and energizing conversation about what it actually means for AI to transform healthcare at scale. Venky brings a refreshingly honest and structured perspective to a conversation that is often dominated by hype, breaking down why AI is fundamentally different from every other technology wave healthcare has been through, laying out the five areas where Infosys is seeing real traction with payers, providers, and PBMs right now, and sharing the story behind two exciting developments: the acquisition of Optimum Health IT and the Pacesetters podcast and executive leadership community. If you are a healthcare leader trying to figure out where to start or how to think about AI as a whole-enterprise challenge rather than a point solution, this episode is essential listening.  In this episode, they talk about: AI is not a point solution; it is a new operating system that will touch every function in every organization Healthcare is broken, fragmented, and frustrating, and AI is the first technology with the potential to fix all three at once Legacy modernization must come before AI adoption because you cannot layer intelligence on top of broken processes AI can now reverse engineer legacy systems that used to depend entirely on tribal knowledge The five pillars of AI transformation are strategy and engineering, legacy modernization, data, process reengineering, and physical AI Training AI on your own private data is the competitive wedge that separates leaders from followers Agents are the new team members, and organizations need to rethink how humans and agents orchestrate workflows together Infosys acquired Optimum Health IT, the number one-ranked Epic implementation partner according to KLAS, to deepen its provider capabilities Epic now covers an estimated 220 to 230 million distinct patients in the US and is growing internationally The Pacesetters podcast and annual executive gathering bring together CIOs, CTOs, academics, and analysts for candid, off-the-record dialogue about the future of healthcare A Little About Venky Ananth: Venky is a technology and transformation executive with deep experience leading a global business unit, scaling high-performance organizations, and delivering large-scale change through AI, cloud, and modern growth operating models. His career has focused on helping enterprises modernize core systems, improve operational efficiency, and unlock new growth through platform innovation and disciplined execution. He founded and scaled Infosys Helix, a cloud-native platform business that continues to shape payer and health platform modernization. In addition, he has led global teams across engineering, delivery, consulting, and product, giving him a broad view of strategy, technology, operations, and organizational scale. He operates at the intersection of technology, business model transformation, and leadership development, with a track record of strengthening enterprise performance and building organizations capable of sustained growth. Beyond his operating role, I host PaceSetters, a CXO leadership platform featuring conversations with leaders from healthcare, academia, private equity, and technology. 

Autonomous software development creates a dilemma for leaders in regulated industries: adopt AI coding at scale or fall behind on product velocity without compromising auditability and code quality. In CXOTalk episode 917, Kris Tokarzewski, Group Chief Technology Information Officer at Vitality, describes how a 14,000-employee multinational insurer is rebuilding its software development life cycle around AI. This episode examines the impact of agentic AI on software development in the enterprise.Recorded at Blitzy's headquarters, the conversation examines deterministic code generation, Blitzy's infinite code context, context engineering, test-driven development, and the shifting bottlenecks that surface as throughput accelerates.YOU'LL DISCOVER✅ Why regulated industries require deterministic, auditable code rather than the probabilistic output most AI coding systems generate✅ How Blitzy's infinite code context (ingestion of codebases, engineering standards, and business rules) creates high-quality software aligned with compliance requirements✅ How Vitality reverse-engineers legacy systems with autonomous AI, achieving a measured 5x acceleration over manual methods✅ Why optimizing end-to-end SDLC throughput matters more than local efficiency at any single stage✅ How code review of 50,000 to 100,000-line pull requests becomes the next limiting factor, and how AI reviewers close the gap✅ How test-driven development pairs with autonomous code generation to raise quality and compliance pass rates✅ How the roles of requirements engineers, software engineers, and product teams converge inside an AI-native SDLC✅ How to instrument AI spend against velocity, quality, end-to-end throughput, and customer value rather than isolated gainsTIMESTAMPS0:00 Deterministic code vs. probabilistic AI output0:14 Meet Kris Tokarzewski, Group CTIO of Vitality0:32 Why Vitality is modernizing legacy insurance systems1:30 Event-driven architecture as agentic AI's natural partner3:00 Building an AI-native software development life cycle with Blitzy4:28 Throughput optimization versus local efficiency6:02 Reverse engineering legacy systems and deterministic code generation9:05 Infinite code context: ingesting codebases, standards, and rules10:00 Test-driven development with autonomous code generation10:49 Results: 5x faster legacy reverse engineering13:17 Product, engineering, and DevOps convergence15:04 Roles level up: requirements engineers and software engineers16:18 Reviewing 50,000 to 100,000-line pull requests17:56 Instrumenting AI spend against business outcomes19:16 Executive sponsorship for autonomous development20:16 Advice for CIOs and CTOs adopting AI-driven development

In this episode of The Brand Called You, host Ashutosh Garg interviews Eddie Irvin, an accomplished AI Strategist and Fractional CTO at Nashville AI Advisory.Explore actionable leadership lessons on AI adoption, including:The biggest mistakes leaders makeHow CEOs and CTOs approach AI differentlyWhy hands-on experience is criticalGovernance frameworks and risk managementWhere AI delivers measurable efficiency gains

Should proptech be defined as a real estate specific problem to which a technology solution is applied to? Why can new real estate applications not ignore the workstream they are a part of and the ecosystem they must work nicely within? How is it possible for companies to balance encouraging innovation but not concurrently creating shadow IT departments? Why is the build vs buy decision front and center again for CTOs and other innovation leaders in proptech? Why was it a blessing in disguise for David to start off his professional career as a custody fund accountant? What led David to start a business operations group? Why is bottoms up technology adoption much easier than top down mandates? What led Dave to uncover the opportunity in real estate AP coding? What percent of general ledger transactions originate in AP? Who are the different purchasers of PredictAP? What new insights has the deployment of PredictAP within customers surfaced? In the fast changing world of AI, how do companies differentiate between solutions that demo well and give the appearance of solving a problem versus well architected and researched solutions that truly solve the fundamental business problem?David Stifter - Founder and CEO of PredictAP, joins Proptech Espresso to answer these questions and discuss how we worked at the first social network in college just prior to the early 2000s dot-bomb crash.

Welcome to another episode of Data Debrief, the companion show to Driven By Data: The Podcast, where hosts Catherine Dowden-King and Kyle Winterbottom sit down to unpack Tuesday's conversation, share what's been on their minds, and explore what's really happening across the data and AI landscape.Fresh off Kyle's return from holiday, the pair dive into Tuesday's episode with Daragh Kelly, Chief Data Officer at The Economist, unpacking the ideas that stood out most, and a few that challenge the dominant narratives in the market right now.They cover:Why the concept of “Trad AI” (traditional machine learning and data science) is a useful lens, and how the market is blurring the lines between legacy AI and the new wave of generative and agentic capabilitiesThe ongoing hype cycle in AI, why it's nothing new, and how organisations risk getting distracted by buzzwords rather than focusing on real outcomesThe growing gap between building AI solutions and making them scalable, reusable, and commercially viableThe importance of defining what “AI” actually means inside your organisation, and why vague language is creating confusion at the board levelThe tension between speed and direction, and why moving fast means nothing if you're not solving problems that actually matterWhether operating models really need to change for AI, and why Dara's perspective challenges the prevailing narrativeThe shift from analysts as insight generators to “toolmakers”, and what that means for the future of data and analytics rolesThe rise of self-serve capability across organisations, and the risks of uncontrolled experimentation without governanceThe ongoing power struggle between CDOs, CIOs, and CTOs over AI ownership, and why the answer is far from settledThe role of optics, titles, and external brand in shaping career progression for data leaders in an AI-first marketPlus, in this week's Thoughts of the Week, Kyle challenges the long-standing narrative around “having a seat at the table,” arguing that it's often used as an excuse for not delivering value, and that true impact comes from driving outcomes, regardless of reporting lines. Catherine reflects on the role of diversity, equity, and inclusion in the data community, why the conversation is still far from where it should be, and the responsibility leaders have to actively shape a more inclusive industry.Like and subscribe wherever you listen, and if you've got a question or topic you'd like the team to cover, email community@orbitiongroup.com

Early bird discounts for the San Francisco World's Fair, the biggest AIE gathering of the year, end today - prices will go up by ~$500 tonight so do please lock in ASAP!From near-universal AI tool adoption inside Shopify to internal systems for ML experimentation, auto-research, customer simulation, and ultra-low-latency search, Mikhail Parakhin joins us for a deep dive into what it actually looks like when a 20-year-old, $200B software company goes all-in on AI. We cover why Shopify has become much more vocal about its internal stack, what changed after the December model-quality inflection, and why the real bottleneck in AI coding is no longer generation, but review, CI/CD, and deployment stability.We also go inside Tangle, Tangent, SimGym, which are three major AI initiatives that Shopify is doing to make experimentation reproducible, optimization automatic, customer behavior simulatable, and search and catalog intelligence faster and cheaper at scale. Along the way, Mikhail explains UCP, Liquid AI, and why token budgets are directionally right but often measured badly, why AI-written code can still increase bugs in production, what makes Shopify's customer simulation defensible, and what he learned from the Sydney era at Bing.We discuss:* Mikhail's path from running a major Microsoft business unit spanning Windows, Edge, Bing, and ads to becoming CTO of Shopify* Why Shopify is talking more publicly about AI now, and why staying at the frontier has become necessary for the company* Shopify's internal AI adoption curve, the December inflection, and why CLI-style tools are rising faster than traditional IDE-based tools* Why Jensen Huang is directionally right on token budgets, but raw token count is still the wrong way to evaluate engineering output* Why the real unlock is not more agents in parallel, but better critique loops, stronger models, and spending more on review than generation* Why AI coding can still lead to more bugs in production even if models write cleaner code on average than humans* Why Shopify built its own PR review flow, and why Mikhail thinks most off-the-shelf review tools miss the point* How PR volume, test failures, and deployment rollback are becoming the real bottlenecks in the agent era* Why Git, pull requests, and CI/CD may need a new metaphor once code is written at machine speed* What Tangle is, and how Shopify uses it to make ML and data workflows reproducible, collaborative, and production-ready from the start* Why Tangle is different from Airflow, and why content-addressed caching creates network effects across teams* What Tangent is, and how Shopify is using auto-research loops to optimize search, themes, prompt compression, storage, and more* Why Tangent is becoming a democratizing tool for PMs and domain experts, not just ML engineers* Why AutoML finally feels real in the LLM era, and where auto-research still falls short today* Why Tangle, Tangent, and SimGym become much more powerful when combined into one system* What SimGym is, why simulated customers only work if you have real historical behavior, and why Shopify's data gives it a moat* How SimGym evolved from comparing A/B variants to telling merchants what to change on a single live storefront to raise conversions* Why customer simulation is so expensive, from multimodal models to browser farms to serving and distillation costs* How Shopify models merchant and buyer trajectories, runs counterfactuals, and thinks about interventions like discounts, campaigns, and notifications* Why category-level behavior is so different across commerce, and why ideas like Chinese Restaurant Processes are showing up again in practice* Shopify's new UCP and catalog work, including runtime product search, bulk lookups, and identity linking* Why Shopify is using Liquid AI, and why Mikhail sees it as the first genuinely competitive non-transformer architecture he has used in practice* Where Liquid already works inside Shopify today, from low-latency query understanding to large-scale catalog and Sidekick Pulse workloads* Whether Liquid could become frontier-scale with enough compute, and why Shopify remains pragmatic and merit-based about model choice* Who Shopify is hiring right now across ML, data science, and distributed databases* The Sydney story at Bing, why its personality was not an accident, and what Mikhail learned from deliberately shaping AI character early onMikhail Parakhin* LinkedIn: https://www.linkedin.com/in/mikhail-parakhin/* X: https://x.com/MParakhinTimestamps00:00:00 Introduction: Mikhail Parakhin, Microsoft, and Shopify00:01:16 Why Shopify Is Talking More About AI00:02:29 Internal AI Adoption at Shopify and the December Inflection00:06:54 Token Budgets, Jensen Huang, and Why Usage Metrics Can Mislead00:10:55 Why Shopify Built Its Own AI PR Review System00:12:38 AI Coding, More Bugs, and the Real Deployment Bottleneck00:14:11 Why Git, PRs, and CI/CD May Need to Change for Agents00:18:24 Tangle: Shopify's Reproducible ML and Data Workflow Engine00:21:19 Why Tangle Is Different from Airflow00:26:14 Tangent: Auto Research for Optimization and Experimentation00:30:07 How Tangent Democratizes Experimentation Beyond ML Engineers00:33:06 The Limits of Auto Research00:36:36 Why Tangle, Tangent, and SimGym Compound Together00:37:20 SimGym: Simulating Customers with Shopify's Historical Data00:42:47 The Infra Behind SimGym00:46:00 Why SimGym Gets Better with Real Customer History00:47:30 Counterfactuals, HSTU, and Modeling Merchant Trajectories00:51:55 CRPs, Clustering, and Category-Level Customer Behavior00:53:30 UCP, Shopify Catalog, and Identity Linking00:55:07 Liquid AI: Why Shopify Uses Non-Transformer Models00:59:13 Real Shopify Use Cases for Liquid01:03:00 Can Liquid Scale into a Frontier Model?01:09:49 Hiring at Shopify: ML, Data Science, and Databases01:10:43 Sydney at Bing: Personality Shaping and AI Character01:13:32 Closing ThoughtsTranscript[00:00:00] swyx: Okay. We're here in the studio, a remote studio, with Mikhail Parakhin, CTO of Shopify. Welcome.[00:00:08] Mikhail Parakhin: Thank you. Welcome.[00:00:10] swyx: I don't even know if I should introduce you as CTO of Shopify. I feel like you have many identities. Uh, you led sort of the, the Bing ML team, I guess, uh, uh, or ads team. I, I don't know, I don't know, uh, you know, it's, uh, people va-variously refer you as like CEO or, or, uh, I don't know what that, that, that said previous role at Microsoft was.[00:00:29] Mikhail Parakhin: Uh, that was... Yeah, my previous role w- at Microsoft was the-- I actually was the CEO of one of Microsoft's business units, which included, as I, you know, as we discussed, all the things that people like to laugh about, uh, including Windows and Edge and Bing and ads and everything.[00:00:47] swyx: Yeah, yeah. What a, what a, what a wild time.You've obviously, uh, done a lot since you landed at Shopify. Uh, one of the reasons I reached out was because you started promoting more sort of internal tooling, uh, primarily Tangle, but also a lot of people have seen and adopted Tobi's QMD, uh, and obviously, I think, uh, Shopify has always been sort of leading in terms of, uh, engineering.I think more-- it's just more recent that you guys have been more vocal about your sort of AI adoption. Is that, is that true?[00:01:16] Mikhail Parakhin: Well, I think AI tools in general are fairly recent development, uh, and we've-- Shopify, you know, at this stage of its development, we're developing AI in-in-house and other, uh, building tools that use AI and, you know, interfacing with the wider AI community, uh, you know, are on the sort of the, uh, runaway trajectory.So it just did by sort of natural byproduct. We, we talk about it more also. We just, uh, just even yesterday, Andrej Karpathy was famous in tweeting about, oh, are there some, uh, ways, uh, that, that you can organize your agents to store the data and then, uh, look up the data so that you don't have to research or, or lose context every- Yestime. And a little bit tongue in cheek, I tweeted that, “Hey, we've, we've done it much earlier, and we even have different approaches, Tobi and I.” Tobi, of course, is a big fan of QMD, and I'm more of a SQL, SQLite fan. But, uh, yeah, very similar things that we've already done here. The point is, yeah, we're very dynamic, you know, explosively growing company, and we have to be at the forefront of AI adoption, obviously.[00:02:29] swyx: Yeah. Yeah. Um, you, your team kindly prepared some slides actually that we were gonna bring up on to, uh, the screen. I think I can, I can screen share, and then we can kind of go through some of the shocking stats that maybe, maybe put some numbers to what exactly is going on. So here we have, uh- An internal AI tool adoption chart.What are we looking at here? What ?[00:02:54] Mikhail Parakhin: Yeah, this is very interesting statistics. Uh, this is number of daily active workers, you know, think of, uh, DAO, basically the active users of-[00:03:05] swyx: Yeah ...[00:03:05] Mikhail Parakhin: AI tool as a percentage of all the people in the company, right? And then- Yeah ... different AI tools. And, uh, you could see two things here is that one is the green is total.Uh, green is just total. So you could see that it approaches really % by now. It's hard not to do your job now without interacting deeply, at least with one tool. You could see another interesting thing is just as many people commented in December was the phase transition when suddenly models gotten good enough that, that everything took off and started growing.Uh, it, it was many people noticed that the thing is that small improvements accumulated into this big change in Sep- December roughly timeframe.[00:03:52] swyx: Yeah.[00:03:52] Mikhail Parakhin: The other thing I would claim you could see is that, uh, CLI-based tools and tools that don't require you to look at the code becoming more popular, and you could see, yeah, various versions of, uh, Cloud Code and Codex and Pi and internal development tools taking off.Uh, exactly, yeah, uh, and blue is our River, just internal agent for coding, where tools, uh, that require IDEs such as, uh, GitHub, Copilot or Cursor, they're not exactly shrinking, but they're not growing as fast. Like, uh, red, red line is, is the IDE kind of tools. So you could see that they're, they're not experiencing as, as fast of a growth.[00:04:37] swyx: As I understand it, basically, every employee has their choice, right? Of choose whatever tool you use, and then you're just kind of doing a, a daily sur-survey or something.[00:04:47] Mikhail Parakhin: Exactly. And, uh, we- Yeah ... the, the push is to get your job done, you can use any tool, and we effectively fund unlimited tokens for everybody.Uh, we, we do, we do try to control the models that, uh, people use, but from the bottom, not from top. Like we basically say, “Hey, please don't use anything less than Opus four point six.”[00:05:09] swyx: Oh .[00:05:10] Mikhail Parakhin: Some people, some people end up using GPT five point four extra high. Some people use Opus four point six. Um, uh, you know, uh, there are some, uh, there are plus and minuses in going for full one million context window versus not.But, uh, we try to discourage people from using anything less than that.[00:05:28] swyx: Yeah, yeah. Got it, got it. Uh, I mean, uh, that's, you know... The, the next chart here, it really kind of shows the expansion and the sort of December twenty twenty-five inflection, right? That, uh, people are using a lot of tokens. I think it's also really interesting that no one was kind of abusing it in twenty twenty-five.Like it was- Had comparatively, uh, to this year, there was almost no growth. I mean, it's still like, you know, probably, probably gave fifty percent.[00:05:56] Mikhail Parakhin: Yeah. This is just a different scale. It's still exponential- Yeah, yeah ...growth at just a different- ...rate of expansion. Uh, there was inflection point, and Sean, I would claim the, the super interesting part here is that you could see that the distribution becoming more and more skewed.Yes. The top percentiles grow faster. So that means- Yeah ...the people in the top ten percentile, they, their consumption grows faster than seventy-five and so forth. So, uh, the distribution skews more and more towards the highest users, which is... I don't know what it tells me. It's like it feels not ideal, to be honest.Or maybe it's okay. We'll see.[00:06:36] swyx: Why does it feel not ideal? Is, is it because of, um, quantity over quality, or what's the concern?[00:06:42] Mikhail Parakhin: Because take it to the limit. That means, you know, if, if this rate of separation continued- Ah, yes ...a year, there will be one person consuming all the tokens. So it's just, it's kinda strange.[00:06:54] swyx: Yeah, I mean, um, uh, I, I think internal like teaching and all that, uh, will, will help sort of distribute things more widely. But in, in the early days, of course, the people who are sort of more AI-pilled will obviously find more ways to use it than the people who are less AI-pilled. Maybe let's, let's call it that.I'll just, I'll just kinda quickly, uh, pause from the, the... You know, we will go back to the rest of the slides, but I just wanna, um, review, you know, there are a lot of CTOs of, of large companies like yourself where they're all considering some kind of token budget, right? Like I think it's something, something that Jensen Huang has been talking about, where like if your 200K engineer is not using 100K of tokens every year, like they're, they're underutilizing coding agents.Of course, Jensen Huang would say that, but like it seems a very quantity over quality approach and like some, some people are basically saying like, well, is this comparable to judging engineer quality by lines of code, right? Which we also know is like kind of flawed, but better than nothing. So I, I don't know if you have like a sort of management take here on, on how to view this kind of, uh, metrics.[00:08:02] Mikhail Parakhin: Well, I mean, you're, you're baiting me. I, I like... This is my favorite topic. Uh, if you let me, I'll probably talk for two hours on just this. I have a lot of things to say. Like I do think Jensen gotten a lot of bad press saying, “Oh, of course you're, you know, this, uh, the- ...the cake seller says you don't need enough cakes.”You know? Like, of course. Uh, but, uh, I actually, uh, think that's undeserved. I think he, he's actually right. Uh, I do think- He,[00:08:33] swyx: he's directionally correct.[00:08:35] Mikhail Parakhin: Yeah. Yeah. He's directionally correct for sure. Uh-[00:08:37] swyx: Who knows what the right number is? Yeah.[00:08:39] Mikhail Parakhin: The thing that I do Uh, want to say, and this is something that we learned through trial and error and very important is like two things.One is that it's not about just consuming tokens. Uh, you can consume tokens and, and in fact, the anti-pattern is running multiple agents, too many agents in parallel that don't communicate with each other. That's almost useless, uh, compared to just fewer agents and burns tokens very efficiently. Uh, setting up the right critique loop, especially with the high quality models, where one agent does something, the other one, ideally with a different model, critiques it, uh, suggests ways to improve it, the agent redoes it with this critique and, and so it takes much longer.So people don't like it because latency goes up. You know, they, they have to wait until this debate is happening. But, uh, the quality of the code is much higher. And another thing, just since you mentioned like, look, uh, uh, yeah, the overall budget is just like, uh, lines of codes. Lines of codes are exploding for everybody right now, or partially because AI is really mover balls, but partially just because AI can write a lot more code, you know, doesn't get tired.And so you have to have to have a very strong narrow waist during PR review. Otherwise, just the number of bugs will go through the roof. It's, uh, it's this unexpected consequence of the just volume trumping everything. I would claim by now good model writes code on average with fewer bugs than, than the average human.But since they write so much more of it, like more of it will make it into production. So you have to- You still[00:10:26] swyx: have[00:10:26] Mikhail Parakhin: more bugs. Yeah. Have to have a very rigorous PR reviews, also automated of course. But, uh, yeah, that to spend a lot budget there. Like this, this for me, for me, actually, the important metric is the ratio of budget spent during code generation versus, uh, spent, uh, expensive tokens like GPT, uh, five point four Pro or, uh, uh, Deep Think from Gemini, you know, checking on PR reviews.[00:10:55] swyx: Yeah, totally. Uh, I noticed in your chart you didn't have any review tools. Do you just use like, like let's say a Claude code to review tools? Or do you have another set of review tools like the Greptiles, the Code Rabbits, uh, Devin Reviews has a review tool. I don't know if you've had those specialist review tools.[00:11:13] Mikhail Parakhin: You are a little bit jumping on my store tool right now because the graphs I was only showing public tools. Uh, uh, the-- I haven't found a good PR review tool that, that does what I think should be done. And, uh, partially my, my thinking is because it's so... It just goes against both what people feel like emotionally they prefer and, uh, some of the, uh, you know, frankly Even business models that, that the companies run.At peer review tool, uh, time, you want to run the largest models. That means, I don't know, Codex or, or, uh, Cloud Code is not gonna cut it. You need to have pro-level models if you really want to, uh, stand the tide of bots from going into production. And you need us to spend a lot of time, the models taking turns, but you don't want, like, a big swarm of, uh, of, uh, agents.So in fact, you end up in a different dual-dualistic world where you generate not that many tokens. You, in fact, generate few tokens, but it takes f-a long time because these are expensive models taking turns rather than many, many agents trying to do many things in parallel. So that's, that's why I feel like I haven't found good tools, so we are using our own for peer review for now.[00:12:33] swyx: Yeah. Yeah. I mean, uh, I think a lot of companies are building their own, uh, especially to their needs, right?[00:12:38] Mikhail Parakhin: Mm-hmm.[00:12:38] swyx: Um, I, uh, you also have a chart here going back to the slides on, uh, PR merge growth, where we're now at thirty percent, uh, month on month rather than ten percent. Uh, and also the, the estimated complexity is going up.You know, this is productivity, right? ‘Cause y- presumably there's more stuff going into the code base and more, more features getting worked on. I'm curious about the backlog, right? Like the, the, the-- I actually don't mind a pro-level model taking an hour or two hours to review my PR, because I've dealt with humans who take a week to review my PR, right?And I keep pinging them on Slack, “Hey, hey, review my PR.” So, you know, I think there's some trade-off here where, like, it still doesn't make sense.[00:13:18] Mikhail Parakhin: Exactly. That, that's exactly m-my point. Uh, that on one hand, you can tolerate longer latencies at, uh, PR. On the other hand, like right now, the real problem is not in spending time waiting for PR.It's real problem is since there's so much more code than- Yeah ... uh, probability of at least some tests failing going up, and then you, like, keep de-failing, then you have to find the offending PR, evict it, retest it without that PR, and so deployment cycle becomes much longer. Uh, so it actually, in terms of the overall time to deploy, it's total time savings if you spend more time on a longer model, like thinking for an hour, because then, then you, you don't have to spend all that time during testing and rolling, you know, rolling back the deployment.[00:14:03] swyx: Yeah, totally. That's still worth it. You know, you don't look at the individual, look at the aggregate, and look at the, the, the change in the aggregate system.[00:14:11] Mikhail Parakhin: Exactly.[00:14:11] swyx: I'm kind of curious if, like, there's this PR mentality and, like, c-- the, the, the CICD paradigm will be changed eventually. Some people are like, obviously a lot of people want new GitHub, but I even wonder if, like, Git is the problem, right?Like, is that the bottleneck? Is the concept of a PR a bottleneck? Do you guys use stack diffs? I don't know if, uh, that's a, like, a merge queue stack diff type of thing.[00:14:34] Mikhail Parakhin: We, we use, we use Stacks, we u- we use Graphite. We worked with, uh, Graphite a lot. Uh, so we use Stack, uh, PRs. I think, uh, like that's clearly the overall CICD in general, and the interaction with the code repository right now is the, clearly the sort of the, the main issue and the bottleneck for us, uh, and highest top of mind.I would say we probably need a different metaphor or different whole design of how to process it in new agentic world. I haven't seen anything dramatically better yet. I, I think everybody right now is just trying to keep their head above the water ‘cause, ‘cause there, there's so many PRs and then everybody's CICD pipelines start creaking, the, the times are increasing, the number of bugs slipping by increasing, and you have to, have to clap on down.And so we are a little bit in this situation when we need to first stabilize that story and then start thinking, hey, what, what it could be a completely different and new world, which I haven't... I know some people working on it. I haven't seen something, like anything super compelling yet, but clearly the old thing were designed for humans will need to be morphed into something new.[00:15:53] swyx: One of the thing that I, I think about is kind of like the merge conflict is basically a global mutex on the whole system, right? And in, in hu- in human organizations, we do have something like that. It's the company standup. But like, other than that, it's like it's actually fitting for us to be somewhat decentralized, somewhat plugged into one stream of information source, but somewhat lossy.Like it's okay, you know, that, that not every delivery is like atomic consistency. Like we're not dealing with a database sometimes.[00:16:27] Mikhail Parakhin: This is a very good point, uh, because since humans don't write code too fast, you know that global mutex is not too bad. Once you-[00:16:36] swyx: Yes ...[00:16:37] Mikhail Parakhin: start writing code at the speed of machine, it becomes the, you know, the bottleneck.Then what do you do? Maybe, and I can't believe I'm saying this because I, I'm long-- lifelong opponent of, uh, microservices, and I always thought that was, like, a really bad idea. And now that you're saying it, like, maybe in new guys like microservices will make a comeback, you know, because then you, you can ship things independently in tiny things and, and the managing all that complexity automatically will be much easier.I don't know. Like, we'll s-- we'll have to see.[00:17:10] swyx: Yeah. I mean, I don't know what the Microsoft or, or Shopify thing is, but I, I read this paper from Google where they have a monorepo that deploys into microservices, right? And then, uh, the other concept that I think about a lot is the Chaos Monkey concept from, from Netflix.Being able to create, like, this robust system where, um, uh, you know, you, you have the service discovery, you have the, uh, the independent, independent microservices discovery and, and, uh, you know, probably going to be a fair amount of duplication. That's how an organic system sort of scales, uh, that, that you have that...I don't know how you call it. Slack? Robustness? Depend-- uh, d-duplication. I, I, I forget the-- I, I'm-- And this-- those-- these are not exactly the terms- Hmm ... I'm looking for, but I c-can't really think of the words. Okay. I was gonna go into Tangent and Tangle. Uh, so, uh, we, we sort of discussed the overall stats that, uh, Shopify has.Uh, but, you know, I, I think some, some pretty cool stuff that you guys are working on is your ML experimentation, uh, and your, your sort of auto tr-research training pipeline. Presumably you're much closer to this one because it's, it's a sort of personal hobby of yours. How, how would you explain them in, together?I thought we have a slide that, like, uh, has the s- the system diagram.[00:18:24] Mikhail Parakhin: Yeah. Tangle first and then Tangent as a-[00:18:27] swyx: Yeah ...[00:18:28] Mikhail Parakhin: as a thing on top of Tangle. And, uh, Tangle is the third generation, I claim, of, uh, systems of, uh, running any data processing, but a bit with a skew for ML experiments, but not necessarily. Any sort of data processing tasks where you need to iterate, share, and you have scale so that you want maximum efficiency.You know how, like, normally you would work, you would-- Imagine you're a data scientist or an ML practitioner, you would get Jupiter notebooks or, or maybe you would get, uh, you know, Pyth- your Python scripts, and you would manage the data, and you produce those TSV files, and you put them in some JFS or something.Then you would notice that, oh, it has this, uh, weird missing values. You go and write another script that, uh, goes and replaces them with, uh-[00:19:20] swyx: Ah ...[00:19:21] Mikhail Parakhin: dash S. And then, then you, then you run some, some, uh, “Oh, I need to filter bots.” And so you run some light GBM model that, uh, removes the bots. And then, then you like-- And then you, you kind of like get into shape, and then you start experimenting, and you run multiple experiments, and then you're like, “Oh my God,” like, “this experiment is worse.”You undo, and you cannot get to previous result. And like, “Ah, what did I do?” Like that. Again, then, then you finally like get everything working. Then you like start throwing it over the fence to production. You, you replicate it, those things don't work, and then sometimes you like don't notice that you forgot some feature naming and the, the features don't match.But then, like imagine you, you did everything, and then six months later you're like, have to repeat it because now there's more data, or you wanted to do another pass, and you're like, “What, what did I do?” Or like, or like, “This script crashes now,” or the, “the path has changed.” And then, then you're trying to, like you spend another month just doing ar- digital archeology on your own, you know, history, right?Now multiply that by many, many teams. Now imagine you got an intern that you wanna ramp up. Now you have to show that intern, “Oh, you know, look, here's the folder, there's the scripts, you know, ask your cloud agent to do, and then, uh, to, to figure it out.” And then cloud agent does something, and then you're, “Ah, yeah, right, right, it was the wrong folder.I forgot to tell you, I actually have this other thing I forgot myself.” And, and that's, that's the, like, the daily life we all, uh, all know it, uh, if, if you're a data scientist, machine practitioner, ma- machine learning practitioner or, uh, or even like any data managing, uh, person.[00:21:00] swyx: Yeah. So I, I used to do this, uh, f- uh, on the quant finance side, uh, in, in my hedge fund.So we did this before Airflow, and then, uh, obviously Airflow came along and, uh, then more recently Dagster, uh, I would say is like, in my mind, what I would use for that shape of problem, uh, where you had to materialize assets and create a pipeline.[00:21:19] Mikhail Parakhin: And that's, that's very good segue because... So Airflow is great, but Airflow is more about you, you have something and you wanna repeatedly run it in production on schedule.It's less about you as a team developing things and being able to share, and you grabbing the standard pipeline and saying, “Hey, I wanna change this tiny little component in the huge sea of data processing, and I don't wanna-- I wanna run ten experiments on this, and I wanna do hyperparameter optimization.”All that is very hard to do with Airflow. It's very easy to do with Tango. Tango is m- more about, it's everything about group of people Running experiments, it might be agents too nowadays. Uh, running experiments cheaply, collaborating, sharing results. Uh, you don't need to understand fully. You, you grab-- you clone somebody else's experiment or somebody else's pipeline, uh, run, uh, change small piece, run it, be, like, get it to production state, and then ship in one click.So then the... You don't have to port it into any other system to, to run in production. You can just run the same experiment. It's, it's fully production ready. And, and it's, uh, it has lots of... Again, as I said, it's third generation system. The original one was, I would claim there was Ether and then, uh, at least in my career, Ether was the first, first, uh, that pioneered this type of approach.And then there was, uh, Nirvana, which, uh, uh, at Yandex, which did kind of sec-second take on this. And now this one aggregates the, the learnings from all of those and, and Airflow as well to, to get to the state where you try it, it, it feels kind of magical. Uh, ‘cause now everything is based on content, uh, hashes.So even if the version changed, but if the output didn't change, nothing is being rerun. It's very efficient. If you... Multiple people start experiment that needs the same sort of data preprocessing, it's not repeated multiple times. It's automatically done only once. If you start ten experiments that all require, you know, some, some data preparation first as the first step, and you don't have to coordinate for that.Like, you don't have to know that other people are starting it. You now, it's very easy compos-, uh, composability, any language you can u- uh, you wanna use, and it's very visual. So you can see immediately, you can edit it easily, you can assemble small things with just even mouse clicks if you want to, and, uh, share, clone.And everybody knows also it's fully kind of static in the sense that we rerun it second time, it will exactly have the same results. Like, you will never have to do digital archeology. So full versioning and everything is also there.[00:24:06] swyx: Uh, so, so people can, uh... It's open source. Go to the GitHub repo and, and, uh, check it out.Uh, and it is also a really good, uh, blog post about it. I think all these is, like, really appealing. The, the, the, the thing that I think sells me the most about it is that, um, sort of development to production transition, right? Which I think, um, a lot of people haven't really solved that, uh, strictly, right?Like, we develop really, really well in, in Python notebooks, but then, you know, that's obviously not a sort of production ready process. I think that, like, any way in which that is solved, I think is, is very appealing. Then the other thing that you mentioned, which also raised my eyebrows, was content-based caching, which you mentioned is, is, um, you know, is ve-very much, uh, um, a sort of efficiency measure about, uh, you know, just like recalculation only on, on sort of content addressing Which I think makes sense.Uh, it surprised me that the savings could be this much, but maybe I just haven't worked at your scale where there's so much duplication, uh, that people just rerun because they change a single ID upstream.[00:25:10] Mikhail Parakhin: It does, yeah. But it's not only you rerun. The, the main savings are coming from the fact that you ran it, you got your job done, and you moved on.Then- Yeah ... somebody else in some department you don't know existed runs the same task, but on a newer version.[00:25:27] swyx: Yeah.[00:25:27] Mikhail Parakhin: Like right now, you can't, in, in most of the organizations, you can't even find out about it so that you can't even measure that you're spending that time twice, right? Here- Yeah ... if everybody's on Tango, that's detected automatically and detected that the output is the same.And then for that person, all it looks like is like experiment just suddenly moved, jumped forward, right? Uh, uh- Yeah ... so that's because, because the, there's network effect of multiple people helping each other.[00:25:51] swyx: Yeah. This is one of those things where it's designed to be a platform from the beginning rather than an individual developer's tool from the beginning, right?And, and everything's gonna streams down from there. That is the sort of Tango, uh, orchestrator, and it's, it manages jobs. We've seen a few versions of this, and this is obviously, uh, uh, the sort of, uh, unique approaches that you guys have, have, uh, figured out. And then there's Tangent.[00:26:14] Mikhail Parakhin: Yeah. And Tangent is basically an automatic auto research loop that can help and kind of do your work for you.Uh- ... you know, uh, effectively, effectively, Andrej Karpathy recently popularized it with auto research. Yes. Remember he said like he was, uh, speed running this, uh... Yeah, uh, you know the story. The, here we're basically bringing the same capability into Tango so that, uh, the, uh, Tangent can analyze it. It's just an agent that can run multiple experiments, figure out what can be changed, and keep on rerunning it, keep on modifying until, uh, maximizing some goal, some loss function, whatever you need to, to achieve.And in general, I would say if you're not using auto research-like approach in whatever you do, like literally whatever you do, then you're missing out. We saw at Shopify that taking like a wildfire, anything where you can put measurements can be done dramatically better. Our-[00:27:19] swyx: Mm-hmm ...[00:27:20] Mikhail Parakhin: uh, speed of, uh, templatization HTML, uh, completely new UX tem- uh, templatization of, uh, reducing latency for liquid themes.Uh, we-- Our, uh, search, uh, recently we moved from It's hard even, uh, quote from eight hundred QPS to forty-two hundred QPS with the same quality just by pure optimizations and not a research loop that kept running and changing code in our index serve on the same number of machines, just increasing the throughput.We, we managed to improve the quality of gisting and machine learning process. Uh, you know, gisting is the prompt compression technique that[00:27:59] swyx: allows for[00:28:00] Mikhail Parakhin: lower latency and, and lower and, uh, actually higher quality slightly. So like literally whatever different walks of life, and it doesn't have to be AI related.Uh, we, we had a reduction in, uh, storage because the agents would go and find data sets that clearly are derivative, uh, and then you don't need to store things twice. You know, we, we, we found somewhat embarrassingly that it was one of the largest tables was hashing random IDs into another random ID, and we literally- Oofput only one. So it was translating, yeah, two random IDs hashed[00:28:36] swyx: into[00:28:37] Mikhail Parakhin: each. So, so[00:28:37] swyx: it has access to the code as well, so it can, it can check the, like what, what the hell is it doing?[00:28:42] Mikhail Parakhin: So there, there cou- it could be run in two levels. You, uh, you know, at the superficial level, it could just use ex-existing components and, uh, reshuffle them.Uh, you know, like you can grab- Yeah ... uh, XGBoost, and you can grab some, some Py- PyTorch module, and then can grab some, you know, grab another tools and, and combine them. At a deeper level, since Tangle is all sort of CLI based underneath you, every, every component is a wrapped really CLI, uh, call and a YAML file, it can analyze code and create new components and, and, uh, keep on iterating as well.So, so you can, you can both have quick modifications of existing t- uh, pipelines with the, with components that are already there pre-baked, or you can create new components, uh, and-[00:29:29] swyx: Yeah ...[00:29:29] Mikhail Parakhin: keep iterating on those. So auto research is, again, this is probably the, the thing I was excited the most in the last two months happening, and we see it taking like, like totally like a wildfire.Just, uh, everybody, every day, every... well, every day, every minute, I would, uh, have somebody Slack message saying, “Oh, look how much better I made it.” And, uh, it's all throughout the research.[00:29:53] swyx: Is this democratized in some way in, in the sense that like is it your ML, uh, engineers and researchers doing this, or is it your regular PMs and software engineers also have the ability to auto-- to use Tangent?[00:30:07] Mikhail Parakhin: This is an awesome question. Like, Tango in general and Tangent in particular are extremely democratizing. Like they- Yeah ... they are the main tools for- ‘Cause I don't[00:30:15] swyx: need the details.[00:30:16] Mikhail Parakhin: Yeah. Exactly. Initially used by ML and AI engineers, but then literally, as you said, PMs are like the highest user right now is one of PMs on our org, uh, Sartak and he was, he was number one by, by usage of, of this ‘cause they're just, uh, energetic and knowledgeable, and now it, it unlocks a lot of capability where you don't have to co-change code manually.[00:30:39] swyx: I mean, I mean, because it kind of cuts out the ML, ML engineer from the process because the, the, the PMs have the domain knowledge and the ability to think about, uh, from first principles about, okay, what, what results do I want? And they can-- they even have the access to the data that, that needs to go in.So it's like in some ways, like this is the magic black box that we've always wanted for, for training and, and for, uh, I guess, uh, uh, hill climbing, whatever.[00:31:04] Mikhail Parakhin: It's basically cloud code for your AI development- ... uh, situation, right? Like now, now you don't have to know exactly how algorithms work. You can just, uh, bring your domain knowledge and expertise and product knowledge and iterate within Tangent until you've gotten the results that you need.[00:31:21] swyx: In my previous roles, every time that someone has pitched AutoML, you know, I've always been like, “Uh, this is not, this is not gonna work. It's, you know, it's, it's always gonna be a flop.” Somehow it's working now. I mean, presumably the answer is now we have LLMs and it's good enough, right? It's, it's an emergent property that we can do auto research, but like, it doesn't feel that satisfying that how come we didn't do this before, right?Like we just did like parameter search and like, I don't know. That's maybe that's it.[00:31:48] Mikhail Parakhin: Yeah. Bayesian optimization and hyperparameter optimization was, was the one that, or facet of AutoML that was used very actively, which incidentally also built into, uh, Tango. But, you know, I know Patrice Simard very well, and, uh, he was such a, uh, such a proponent of AutoML, and he put, like literally spent careers trying to democratize it.Without LLMs, it just turned out to be very hard. Like it, you, you would have flexibility within certain narrow domain, but it was hard to wider scale, and now with LLMs suddenly it's like magic wand, and so suddenly everybody- ... is an AutoML expert.[00:32:28] swyx: Yeah, I, I think it's multiple things, right? Like I'm, I'm just gonna bring up the, the, the chart again, right?Like LLMs can do the monitoring very well. That is the very potentially unbounded, super unstructured. It can do the analysis very well, it can do the... Uh, and basically it is much more intelligence poured into every single step. Uh, there's maybe nothing structurally changed about AutoML, but this is just m-more intelligent and more unstructured.[00:32:53] Mikhail Parakhin: Exactly.[00:32:54] swyx: Any flaws that you've run into? Like everyone is like drinking the Kool-Aid, oh my God, time savings, uh, you know, performance improvements. Like what, what, uh, issues have you have, uh, come up?[00:33:06] Mikhail Parakhin: This is really cool. It's not a solution to all the world's problems for sure. The limitations are usually the ones I-- And this is where we get into a bit of a subjective territory.Uh, I can only share what I've, I've seen so far, and I'm sure the situation, uh, is changing, and, you know, maybe after I say it, like many people will reach out and say, “Hey, what about this?” And you don't know that, and then, then we'll be probably right. But what I've seen is auto research is very good at doing kind of obvious things that you don't have bandwidth to do or you didn't notice or maybe you're not aware of like the-- some standard practices.It is not good at doing something completely out of distribution, something that, you know, you have to think for, for multiple days, uh, and, and do something like none of this. So, so it's, uh, I, uh, set an experiment once, uh, on, on my sort of, uh, hobby thing, and I let it run for, uh, ended up, uh, several weeks run, uh, you know, it's like full production kind of scale, so it, you know, slow runs and, and it ex-- it performed in the end, uh, over four hundred experiments, and only one was successful.I'm like, “Okay, that's, that's good.” But-[00:34:18] swyx: But it saved time.[00:34:19] Mikhail Parakhin: Yeah, I saved time. Like it, it was the, that thing. Yeah, if I, if I were doing four hundred experiments myself, my betting average, as I said, would have been much higher, I'm sure. But also, first of all, it would take me like three years to do four hundred experiments.And, uh, I didn't have to do them. Like the machines were just, uh, the price of electricity did that. So, and I got one improvement, uh, that in, uh, my, my-- Honestly, when I was starting that experiment, my thinking was to go and show that, “Hey, Andre, maybe you just don't know how to optimize.” And I was super smart because in, in my pro-problem, it was optimized for many years, and it was like fully improved.Uh, and I didn't expect it, you know, auto research to find anything at all. Yet it did. So instead of making fun of Andre, I ended up, uh, a big, big supporter. Yeah, that's exactly the tweet. Yes.[00:35:10] swyx: You and Toby really, really go back and forth on-online a lot, which is really funny. Uh, think of it as, as an eval for the optimalness of the code it's running on.Uh, it's almost like it reminds me of like a Kolmogorov complexity thing, but, uh, I guess it's-- there's some optimal thing that you're trying to sort of reduce down to, I guess. Um, and so, so you, you, you know, you should congratulate yourself that you had, uh, you know, uh, ninety-nine percent, uh, optimality.[00:35:36] Mikhail Parakhin: Exactly, yeah. I think Andre really deserves a lot of credit for popularizing this approach. This is, uh, this is incredibly, I think, powerful and cool and You know, the, uh, even him, him just mentioning it led to a lot of gains in a lot of places in the industry, so we should be thankful.[00:35:56] swyx: Yeah. I think he also has a just...I don't know what it is. Like, um, you know, it, it is a simple self-contained project that people can take and apply to other things, which is, is, is one thing, but also just the name. Just like somehow no one, no one managed to call their thing auto research. It's just naming things is very important. I think that that is mostly, uh, our coverage of Tango and, and, uh, Tangents.I think obviously, you know, there's a lot of, uh, ML infra at, at Shopify that people can, uh, dive into. We're about to go into SimGym, but before I do that, any, any other sort of broader comments around this whole effort? Like where is it, where is it leading to?[00:36:36] Mikhail Parakhin: As a segue to SimGym, like all those things start composing strongly.And, uh, you could see a huge unlock when you can look at each one of the tools and, and you see, oh, they're extremely useful. Uh, Tango is useful by itself. Auto Research is useful by itself. SimGym is useful by itself. If you combine all three, you create like synergetic effect. I think that's why we wanted to even, uh, cover them today is because this is something that if you go back even, you know, five years ago, would've been unthinkable.Uh, replicating that, uh, would, would be either incredibly costly or impossible, right? With probably thousands of people are required.[00:37:20] swyx: Well, we have serverless human, uh, serverless intelligence, right? Like, uh, so yes, you do have thousands of hu-- of, of intelligences, not just, not humans. And that's, that's close enough, right?Even if they're not AGI, they're, they're close enough to do the, the task that you need them to do. And, and, you know, that's, there's plenty for, for a lot of routine work, knowledge work. Okay, let's get into SimGym. Um, this is one of those things I, I was surprised to see actually it's apparently your, uh, one of your most popular launches, and I think something that, uh, I think Sim AI, I think Yunjun Park, who did the Smallville thing, there's a very small cottage industry of people trying to do like the simulate customer thing.I think a lot of people maybe don't super trust this yet because they're like, well, obviously they would just do what you prompt them to do, right? But maybe just think, uh, tell us about the sort of inspiration or origin story.[00:38:10] Mikhail Parakhin: That's exactly actually the thing I wanted to cover, because if you don't have the historical data, all you can do is prompt a-agents in a vacuum, and they will do exactly what you prompt them to do.In fact, when I first proposed it, and this is a bit of, um, my brainchild initially, if I, I can boast, even Toby said like, “But wouldn't they, they just repeat what, what you tell them?” And, uh, but I'm like, “Yes, except Shopify has decades of history of how people made changes and what there is, uh, there, what it resulted in terms of sales.”So now what we can do is we can-- we have this... It's not, it's a noisy data. There's a small, usually websites, uh, you know, like things, things are never in isolation. It's almost never AB experiment. It's always AA experiment when there's has two meanings, but basically, you know, in different time you run two different things.But if you aggregate in general, uh, like everything together, and you apply, uh, denoising and collaborative filtering like approach, you can extract a very clear signal. And then you can optimize your agents. And that's why it took so long. It took almost a year of that optimization of just us sitting and fiddling, and, and we had this internal goals of correlation of hitting-- internal goal was to hit zero point seven correlation with, uh, add to cart events, for example.Like that, that if we run real AB test experiment, that it should, it should go and, and rep-uh, replicate, uh, same sort of success that, that humans had or lack thereof. And it, it took forever, and I don't think that's easily replicatable because, uh, like who else would have that data? You have to have this historic, you know, decades, uh, worth of data.And now, now the, like the other thing you need is in-infrastructure and the scale, right? Because, uh, w- again, what we found, uh, stat sig results, you need to run a lot of simulations, a lot of agents, and, and it's-- Those are expensive things. Like you're, you're making actions in the browser because you want a real friction.You want to, to be able to get the image like of what humans will see because you wanna, uh, detect effects like, “Hey, if I make my images larger, will I have more sales or l- uh, fewer sales?” And like usually people's intuition here, by the way, is that I increase my images, I will have more because they look nicer.You know, designers all look sparse and big images. Like usually your sales tank, right? But, but, uh, you know, from HTML, all the characters look the same only the, the size tag looks different, right? So it's very hard. So you have to take visual information, you have to run this in simulated browser environment on the big farm and, and of course, you have to have, uh, like very, very expensive model, good model with multi-model model.So all this it's-- is what's taken so long and, uh, to share my personal fail a little bit there, Sean, is like, you know, we always had this bias to-- for like large company bias. You know, we always, uh, whenever you-- we do, we're like, “Hey, we'll run an experiment,” right? We make, make a change, and we will run an experiment and then, uh, see, uh, see which one's better or like, “No, this is worse,” and most of them are worse, so you discard it and keep iterating, hill climbing.And we're like, “Oh, like smaller merchants, they cannot get stat sig results. They cannot really run experiments simply because, you know, in a week there would be not enough data for them.” So we thought from this perspective. What we didn't realize is that most people don't have A and B, they just have one thing, and they need suggestions of What A and B should be.So, uh, we first build this, hey, we run simulation on two separate teams and, and, uh, say, “Hey, which one is better?” We then morphed it into, and very recently just released it, when you have just your site, your theme, we run over it and we say, “Hey, here's what predicted values of, of, uh, uh, conversions are, and here's how we think you should modify it to increase your conversions.”And then circling back to what you started with, the proof is in the pudding. Like, if we are not correlating with reality, like, people will not be using it. And, uh, thankfully, we see literally every day more users than the previous day. So, so right now, uh, right now- It's working. Yeah. I'm-- Right now my problem is how to pay for it all because the so our major thing is how to optimize the LLMs, do distillation, how to run the headless browsers, uh, and handful browsers, uh, uh, cheaper so that we can accommodate the increase in traffic.[00:42:47] swyx: Yeah. I, I understand that you, uh, you published a lot of technical detail at GTC, so I was just gonna bring it up a little bit. I think s- was this in, in con-conjunction with some kind of GTC presentation? Or something like that, right?[00:42:59] Mikhail Parakhin: Well, we, yeah, we, we did it in several place, but yeah, we had the engineering- Yeahblog, uh, as well. Yeah.[00:43:05] swyx: Yeah. So you're running, uh, GPT OSS. Uh,[00:43:08] Mikhail Parakhin: the, this is an older version. You know, now we run multimodal model. But yeah- Yeah ... GPT OSS, we still run GPT OSS as well for[00:43:15] swyx: And then you have the VMs, and you also have browser-based. I really like this one where it you said, “It violates almost every assumption that standard LLM serving is designed for.”And then you had like, basically orders of magnitude differences between everything.[00:43:29] Mikhail Parakhin: Exactly. Which is, which, uh, which was, you know, a bit of a challenge to implement, like when, like even simple things. Uh, be- since it violates all the assumptions, for example, multi-instance GPUs, like MIGs don't work as well.But we needed, uh, to get MIG to work because, ‘cause otherwise it's way too expensive. And so we had to deal with the, yeah, with, uh, lots of infrastructure and, and, uh, work with, uh, uh, Fireworks and CentML, uh, you know, to help with optimizations and browser-based, as you mentioned. Yeah, like, takes a village.[00:44:04] swyx: Okay. So there's a lot of like, I guess, experimentation in the infrastructure so far, and you've published more or less what you have here. I guess I'm, I'm less familiar with CentML. I, I don't do, uh, that much work in this, this part of the stack. But why was it the sort of preferred instance platform?[00:44:22] Mikhail Parakhin: There are really three probably top companies. There used to be, uh, uh- Three top companies, uh, at least I was aware of that did, uh, LM optimization. You know, together Fireworks and Santa ML, not necessarily in that order. Santa ML recently got acquired by NVIDIA. Uh, what they did is if you have a model and you want to optimize it to a specific prof-- uh, profile of usage, uh, they would go and do it.And, uh, we work with, with those companies, uh, this was work particularly in with Santa ML and NVIDIA to get them the best possible results out of it. And, and sometimes you, you have to retune depending on, like sometimes you want the maximum throughput, sometimes you want minimal latency, sometimes you want like the cheapest, right?And, yeah, or some combination. And so yeah, these are people who would come and help you.[00:45:14] swyx: I see. I see. Yeah, yeah. I'm familiar with these people for the LLM, you know, autoregressive stack. But the other interesting category of these optimizers is also the diffusion people, whereas like Fel and, you know, uh, Pruna recently has come up a lot as well, which I think is like really underappreciated, uh, at least by myself, because I, I thought, oh, all the workload would be LLMs, but actually there's a lot of diffusion as well.[00:45:38] Mikhail Parakhin: Exactly.[00:45:38] swyx: There's a lot here, so I, I, I... it's, it's, uh, it's, it's, it's hard to cover. But I, I do think like people underappreciate the importance of customer simulation, basically. I think this is something that I'm candidly still getting to terms with. Uh, you know, uh, you also-- your team also like prepared this, like, really nice diagram.Uh, I, I assume this is AI generated.[00:46:00] Mikhail Parakhin: Yeah, it looks-[00:46:01] swyx: Maybe it's not.[00:46:01] Mikhail Parakhin: Yeah, it looks, uh, Gemini-ish. Yeah, but, uh, uh, honestly, I, I don't know where, where the hell they generated. It looks, look, uh, looks like it's, uh, Google. But the interesting part, John, that, that, uh, we haven't covered, but I, I wanted to mention is if your store had previous customers, rather than it's a new store, you're like new merchant just launching things, it helps tremendously in just correlation and forecast.Yeah, we take your previous, uh, customer's behavior, and we create agents that replicate those specific distribution of, of customers that you get, and then we a- we apply those to your changes, and then that, that raised raw, you know, the re-- uh, just correlation with the add to cart events or to-- with conversion or whatever it, it, it may be, uh, quite dramatically.So, uh, replicating humans in general seems like an interesting, cool challenge.[00:46:58] swyx: As a shareholder, I think this is the-- like if people are Shopify shareholders, they should really deeply understand this because this is basically the moat. The, the more you use Shopify, the more it will just automatically improve, right?Like you're, you're doing the job for them.[00:47:13] Mikhail Parakhin: Yeah, that's what we started with. Like, uh- ... uh, otherwise, if you're just a startup, I wouldn't do it if, uh, you know, if it was my startup because Without the data, it, yeah, as, as you said, it's, it's exactly the case that, uh, whatever you say in prompt, that's, that's what the agents will be doing.[00:47:30] swyx: The statistician in me wants to like really satisfy the sort of, um, statistical intuition, I guess. Um, to me it's kind of, uh, the, the word that comes to mind is, um, ergodicity. Uh, so let's say a, a customer takes this path, customer takes this path, customer takes this path, right? Um, the... In my mind, the way I explain it is like, okay, here, here's the ninety-five percentile, here's the five percentile, and here's the median, right?Um, but to me, what SimGym is potentially doing is that it can, uh, modify... It can sort of model the sort of in-between sort of journeys as well, that, that maybe are dependent on the previous states. This may be like a very RL-type conclusion where like basically the summary statistics, if you only did naive AB testing, you only have the, the statistics at, at, at a certain point, and you only judge based on the sort of overall summary statistics.But here you can actually model trajectories. Does that make sense? Or-[00:48:31] Mikhail Parakhin: That makes total sense because like, well, that, that makes even more sense that maybe even you realize bec- because-[00:48:38] swyx: Okay. Please,[00:48:38] Mikhail Parakhin: please. Yes ... we do-- Yeah. The, so internally, uh, we have this system, we talked about it briefly once at NeurIPS.We have a huge HSTU-based system that models the whole companies, uh, and their possible paths. And like- Yeah ... what you are, what you are showing, like actually at any point of time, you can either model the user's behavior or you mo- can also think about, uh, the whole merchant as a company, as the entity that acts in the world.You can model that as well. And then you can do, can do counterfactuals. In your graph, like in your blue graph, uh, if you're... Imagine in the center there, uh, somewhere in the middle, you would have an intervention. I give that person a coupon, or I don't know, I send a personal thank you card, or give a discount in some- somewhere.And then you can, uh, then you can do forward rollouts from that counterfactual. So what would have happened with that intervention or without the intervention? And you can even ch- change where that intervention, uh, in time can happen, right? Like some- where, where in this journey. So we, we do this at the Shopify scale for our merchants, and then if we notice that something that they can be fixing, like there's a strong counterfactual, like we have Shopify policy, they basically get a notification like, “Hey, we think your...something is wrong with your-” I don't know, Canadian sales. Like, uh, it looks like it's misconfigured. Here's what you need to do. Or do you think like, uh, you have to set up this campaign with these parameters? And we do that at the buyer level to literally offer discounts or cashback or, or things to buyers.So this is-- I'm getting very excited. Like this is my sort of area of, uh, interest, I guess, and, and hobby. But being able to m-model something complex as human beings or companies and model counterfactuals on it, where you can have interventions in the future and optimize when to make intervention, what kind inter-- uh, what kind of intervention to make.It's such an unlock that previously was completely impossible. Like the-- it was, it was always dreamed of, but never... Like how would you even simulate it without LLMs or HTUs? I think very, very exciting times.[00:50:59] swyx: I just wanted to, uh, to maybe illustrate this. I, I'm not the best illustrator, but I, I am a conceptual statistics guy.And y-you know, you cannot just do this. Like this is a dimensionality AB test doesn't do, right? Like, uh, because it doesn't have the, the, the change over time, uh, stochastic nature, uh, and it doesn't have the sort of contextual like... Here's all the context to this point. Um, okay, cool. Um, that's SimGym.You're, you're gonna burn a lot of tokens on this thing. But you're, you're one of the, the only scale platforms in the world that can, uh, that can do this across a huge variety of workloads, right? I'm even curious on a sort of human, uh, research level of like, well, do, does retail behave d-differently from like clothing sales?D-does that behave differently from electronic sales? I, I don't know. I don't know what else you guys... The Kardashian shoppers, do they differ from like people who buy, uh, I don't know, cars and, uh, whatever.[00:51:55] Mikhail Parakhin: Well, very different, and different sensitivities and different modes of, uh, shopping and, and different levels of what's important.Now, to-totally, you can do aggregations at, uh, at a store level. You can do aggregations at a different, uh, category level. I don't know if, uh, you know, for our statisticians among us, I couldn't believe, but we-- recently we're looking at it, and we had to bring back, uh, CRPs, you know, Chinese restaurant process.It's a, like, way of aggregating and, like, naturally grow clustering. So across... Specifically to answer questions that, uh, like you were just posing on how, how if, if buyers behave different categories. And I'm like, “I haven't seen CRP since two thousand and one.” It's[00:52:37] swyx: so What? It's so- What is... No, I haven't, I haven't seen this.No. This is not in my training. Uh,[00:52:44] Mikhail Parakhin: but, but yeah, it, uh, uh, it actually, like the, the-- there was a very popular kind of theory, popular neurips HTML circles in early two thousands, uh, kind of nice. And now, now it has practical applications, uh- Yeah ... that we were resurrecting.[00:53:03] swyx: Yeah, amazing. Uh, I, I can see, I can see how this is like a, uh, a fun job for you where you get to apply all these things.Um, yeah, yeah, so super cool. Super cool. So, okay, so, so anyone who, who knows what CRPs are and has always wanted to use them at work, uh, they should, they should definitely join Shopify. Okay, so w-we have a lot and but I, I'm, I'm being mindful of the time. I, I do wanted to, to sort of cover some other things.Um, I-I'll give you a choice, UCP or Liquid?[00:53:30] Mikhail Parakhin: Liquid. I think, I think on UCP, you know, like UCP is very important for us and, and it just we are-- UCP, we have a structured, uh, discussions, and you can read about them, and we have, uh, blog posts, and we have a big release this week, in fact, like with our catalog.Oh,[00:53:46] swyx: okay.[00:53:46] Mikhail Parakhin: Uh, yeah,[00:53:46] swyx: but- Le-I mean, we, we can, we can discuss the, the, the release briefly because we'll release this after the-- after it's already announced so whatever. There's a catalog that you guys are doing?[00:53:55] Mikhail Parakhin: Yeah. So we are, we are- Okay ... we are bringing in capabilities of a whole, uh, Shopify catalog.Basically, you now you can search for products, you can do lookups by specific ID, you can do bulk lookups when you need to bring m-multiple products. You don't need to know in ad-in advance what you're trying to show or to sell or check out. Like, you can now, you can now have this decided at, at runtime, and this big area for investment for us for both non-personalized and personalized searches, trying to provide basically a win-window into whole universe of products that are being sold everywhere in the world.And Shopify is really not exactly, but almost like a super set of any-anything being sold. Now we are bringing it into UCP and, uh, and, uh, identity linking is another big thing for us, uh, so that you, you can use, uh, like Google or whatever, whatever identity you have, uh, they're minimizing friction.[00:54:56] swyx: Yeah. So[00:54:57] Mikhail Parakhin: yeah, big release for us.But Liquid AI of course we never talk about, and the problem might be more, more aligned with what we d-discussed previously on this chat.[00:55:07] swyx: Sure. The main thing that everyone understands about Liquid is that it is inspired by Worm, and I still don't know why. I'm curious on your explanation. I think you, you, uh, you can make things very approachable.And also I think like what is the potential of like the, the level of efficiency that you get out of Liquid?[00:55:23] Mikhail Parakhin: You- we all familiar with transformer architectures. And, uh, for the longest time, there was a competing architecture, it's called the state space models. So, so Sams, uh, you know, Chris, Chris Reyes, one of the pioneers and, and lots of startups, uh, trying to make those realities.They have, uh, significant benefits being main being, uh, being much faster and, uh, lower footprint and not quadratic in length, you know, sort of, uh, linear in, in, uh, in your context length. But with state space models- They never quite made it. Like they're used-- They have, uh, certain niches when they thrive, their hybrid architectures are useful, but they never quite made it.And liquid neural networks are, you can think of them as a next step, like, uh, sort of, uh, state-space model square. It's non-transformer architecture that's more complicated than sta-state space and really difficult to code if you-- if I'm being honest. But it's, um, very efficient. It's, uh, subline-- sub, uh, quadratic in, in length of your context.Uh, it's very compact way to represent things, and that's a liquid AI company. They... Their goal is to productize it, and very often you have this need, uh, when you need to have long context and small model, and you want to have low latency. Like in general, it's basically on par with transformers, and if you do hybrids with transformers, it's, it's even better.That's why we at Shopify, when we tried multiple and we constantly try multiple models, multiple companies, we found that for small, particularly with low latency applications, when you have low latency and/or if you need longer context lengths, liquid was the best. And so we still use the whole zoo and always like obviously test and use everything, uh, every open source model and, you know, it feels l

EPISODE 703 - Michael Hunter - Resilience for leaders in tech, integrating heart, mind, body, and spirit to sustain leadersIn this episode of Living The Next Chapter, host Dave welcomes Michael, a seasoned guide for tech leaders who positions himself not as a fixer, but as a partner uncovering hidden dynamics that sap energy and stall progress in teams. From Columbia, Missouri—near the quirky geographic heart of the continental U.S.—Michael shares his winding path: childhood passions for drawing floor plans and self-taught coding on an Apple IIe, a pivot from architecture school to software engineering, and now, three decades later, authorship of The Resilient Tech Leader. Releasing in early 2026 alongside an online workbook and audiobook, the book distills his 16 practical tools, refined through personal reinvention and client work, into a roadmap for building resilience amid tech's chaos.​Michael emphasizes resilience as the foundation for leadership evolution, likening it to a personalized diet: universally applicable yet uniquely tailored. Tech pros excel at logic, he notes, but overlook heart, body, and spirit—leading to paradoxes where "every technical problem is a people problem" due to ambiguous human communication. His chapters blend TL;DR summaries, whimsical vignettes of CTOs and engineers, core problem-solution frameworks, personal examples, and team-application strategies, appealing to all learning styles with whimsy akin to Mary Poppins' spoonful of sugar.​Guests and clients rave about its impact, like one veteran who revisited basics and found fresh relevance in focusing amid distractions. Michael's agnostic illustrations and simple, safe, sustainable approach amplify the message: integrate your whole self to lead authentically, boosting personal gusto and team metrics like efficiency and engagement. More evolutions await in future books, with his newsletter at resilienttechleader.com offering updates, podcasts, and metaphors customized to real-world tech hurdles.​Key Takeaway: Cultivate resilience by tuning into your heart, mind, body, and spirit—your unique path to sustained leadership energy starts with one resilient step forward.https://uncommonteams.com/Send us Fan MailSupport the show___https://livingthenextchapter.com/podcast produced by: https://truemediasolutions.ca/Coffee Refills are always appreciated, refill Dave's cup here, and thanks!https://buymeacoffee.com/truemediaca

What does it take to modernize healthcare infrastructure when uptime is not just an SLA, but a patient outcome?In this episode, Amir talks with Jeff Sponaugle, CTO of Surescripts, about building and operating mission critical healthcare systems, navigating the move from on premises infrastructure to the cloud, and figuring out where AI can create real value without compromising reliability. It is a sharp conversation on engineering judgment, modernization, workforce evolution, and why technical leadership still needs real technical depth.What stood outCloud migration in healthcare is not just a cost or architecture decision. It is a reliability decision with real downstream impact on patients.The best reliability strategy is not pretending nothing will ever break. It is designing systems so the customer never feels the break.In regulated industries, structure can be an advantage. Standardized data and consistent formats make AI more useful, especially in healthcare.AI can already improve the patient and clinician experience in practical ways, from transcription to summarizing complex records and surfacing relevant context faster.Technical leaders cannot afford to drift too far from the work. Jeff makes the case that strong CTOs stay close enough to the technology to understand the tradeoffs, guide teams well, and spot what matters next.Timestamped Highlights00:00Jeff Sponaugle joins the show to unpack mission critical technology in healthcare, cloud migration, AI, and workforce upskilling.01:57Why Surescripts sits in a critical layer of healthcare, and why reliability matters when prescriptions need to move in real time.04:02A simple but powerful view of reliability: things will break, but the customer should not know they broke.06:47How to adopt new technology without risky hard cutovers, and why parallel systems matter in high stakes environments.08:53Upskilling legacy teams, preserving tribal knowledge, and why continuous learning matters more than any single technical skill.11:58How regulation can actually help AI in healthcare by creating more consistency in the data.17:33Where AI and agentic systems could create meaningful value in prescribing, diagnostics, and clinical workflows.20:29Why AI has changed executive and boardroom conversations in a way cloud migration never did.A line worth remembering“The customer should not know that something broke.” Pro TipsIf you are modernizing a high stakes platform, avoid the big overnight cutover. Run systems in parallel where possible and learn behind the scenes before customers ever feel the change.If you lead technical teams, do not treat upskilling as a one time event. Give people a path to split time between legacy work and emerging systems so the transition is real and sustainable.If you are evaluating AI in a regulated environment, start with narrow, useful workflows where context, speed, and summarization matter, then expand from there.Stay connectedIf you enjoyed this episode, follow the show, subscribe wherever you listen, and share it with someone building in healthcare, cloud infrastructure, or AI. You can also connect with Amir on LinkedIn for more conversations at the intersection of technology, leadership, and the future of work.

In this episode of the Shift AI Podcast, Derek Slager, CTO and co-founder of Amperity, joins host Boaz Ashkenazy for a conversation that spans 10 years of company building, the evolution of AI-assisted software development, and what it really means to lead a technical organization through genuine disruption.Derek shares the founding story of Amperity, how he and co-founder Kabir Shahani stumbled into the customer data problem while building marketing automation at their previous company, Aperture, and how that experience became the thesis for building an entire platform around getting data right. The conversation moves into the heart of how AI has transformed Derek's work as a CTO and as an engineer. He describes the moment the shift felt real, the team dynamics of moving from individual AI exploration to a true team sport, and how Amperity is compounding the institutional knowledge locked in a decade of after-action reviews into something agents can now actually learn from. Derek addresses the "SaaS is dead" narrative head-on arguing that Amperity's data foundation is precisely the asset that makes agents genuinely useful for their customers.Boaz and Derek close with a forward-looking exchange on agentic workflows in marketing, the importance of redesigning process and what a learning mindset means for individuals and organizations navigating what comes next.This episode is essential listening for CTOs, data leaders, and operators who want to understand how the companies with the best data foundations are positioned to thrive in the agentic era.Chapters[00:00] Introduction: Derek's Path to Building Amperity[02:13] What Amperity Is and Why It Took 10 Years to Build[04:41] First Job: Early IT Work at Dad's Small Business in Monroe, WA[06:14] The Founders Club: How Amperity Went to Market in 2016[08:20] Why They're Running a New Founders Club 10 Years Later[10:13] Both Sides of Claude Code: What Changed and When[13:30] Living Through Disruption as a CTO and Engineer[15:36] Making AI a Team Sport Instead of an Individual Pursuit[17:04] The Moment It Really Clicked: A Simple Tool That Took 5 Minutes to Build[19:09] Cultural Adoption: Skeptics to Believers Inside Amperity[21:50] Compounding Engineering: After-Action Reviews as AI Training Data[23:45] The Agent Wave Is Real: What It Means for a Customer Data Platform[25:09] Amperity's Data Foundation as the Perfect Agent Substrate[27:00] Redesigning Process, Not Just Adopting Tools[28:57] Systems Thinking and the Future of Work[30:04] Two Words: Learning Mindset[33:01] How to Connect with Derek and AmperityConnect with Derek SlagerLinkedIn: https://www.linkedin.com/in/derekslager/Website: amperity.comConnect with Boaz AshkenazyLinkedIn: https://www.linkedin.com/in/boazashkenazy/Email: info@shiftai.fm

Timothy Li, CEO and Co-Founder of LendAPI, has spent nearly a decade trying to solve the same problem: launching a lending product takes too long and costs too much. With LendAPI, he's built a no-code platform that lets banks, credit unions, fintechs, and retailers go from idea to live lending product in weeks, not months or years. Think of it as a GoDaddy-style experience for financial services. Timothy joined me again on the show (he was last on in 2017) to talk about what's under the hood, what the Sunglass Hut deal reveals about embedded finance, and where he thinks AI is actually useful in lending today.What We CoveredTimothy's path from the Fluid college credit app to building LendAPIHow the drag-and-drop product builder works for non-technical usersPython model deployment for credit risk officers inside the same platformWinning Best in Show at FinovateThe Sunglass Hut deal and how it came together in three monthsWhy retailers are moving away from pure-play BNPL providersIntegration options: bank cores, side cores, and direct e-commerce embedThe 300-plus partner marketplace and the SEO strategy behind itDoc AI and single-task AI agents for document processing and underwritingTimothy's experience in the CURQL accelerator and how credit unions differTeaching FinTech Fundamentals at USCThe five consumer verticals with the most opportunity in fintechKey TakeawaysThe build vs. buy debate is essentially over. When Timothy talks to bank CTOs today, the conversation is "can you launch this next week?" not "should we build this ourselves?" Speed to market has become the dominant concern.Pure-play BNPL approval rates are outside a retailer's control and can swing 10 points overnight. Private label embedded finance, built on infrastructure like LendAPI, lets retailers and banks own the underwriting criteria and the customer experience, which matters especially for high-ticket items where the financing decision happens in-store.Single-task AI agents are the near-term opportunity in lending, not fully automated credit decisions. Automating document verification, data extraction, and intake workflows saves minutes per application, and at scale, that compounds quickly.The five consumer fintech verticals worth building in: mortgages, auto, credit cards and personal loans, payments, and bank accounts. If it's in someone's wallet, there's still work to do.About Timothy LiTimothy Li is the CEO and co-founder of LendAPI, a no-code lending platform that launched in 2024 and won Best in Show at Finovate. He previously built Fluid, a credit-building app for college students, and has been building lending infrastructure across multiple ventures over the past decade. He also taught FinTech Fundamentals at the University of Southern California.Connect with Fintech One-on-One:Tweet me @PeterRentonConnect with me on LinkedInFind previous Fintech One-on-One episodes

Episode 360: The #1 AI Governance Mistake Schools Are Making ft. Betsy CooperWhat's the biggest mistake schools are making with AI right now? According to Betsy Cooper, it's not taking it seriously from day one. In this episode, Dr.Alfonso sits down with Betsy Cooper, Founder and Executive Director of the Aspen Policy Academy, for a powerful conversation on the AI governance decisions quietly reshaping schools — and what educators, leaders, and parents can do about it.Betsy brings a one-of-a-kind perspective shaped by her work as a former DHS attorney, her time leading the UC Berkeley Center for Long-Term Cybersecurity, and her doctorate from Oxford. Through Aspen Policy Academy, she's on a mission to democratize policymaking, helping teachers, parents, technologists, and community advocates learn how to identify problems, build solutions, and actually drive change.Together, Dr. Alfonso and Betsy unpack why "ooh, that looks pretty, let's try it" is the wrong way to evaluate new tools, how smooth vendors and shrinking budgets are pushing districts into risky decisions, and why K-12 students need adult stewards more than ever in this moment. Betsy also shares the castle and moat metaphor every school leader needs to hear, a three-step crisis plan for overwhelmed CTOs and superintendents, and her four-step policy impact framework for educators ready to advocate for change.Whether you're a teacher, CTO, superintendent, or parent, this episode will leave you with practical tools and a renewed sense of agency to push back, ask better questions, and advocate for the students who can't speak up for themselves.Chapters00:00 — Welcome & Sponsor Shoutouts01:30 — Meet Dr. Betsy Cooper & The Origin of Aspen Policy Academy07:00 — What Policy Literacy Means for Educators (and Why It's Free)14:00 — The 4-Step Policy Impact Framework19:30 — The #1 AI Governance Mistake Schools Are Making24:30 — How CTOs Should Evaluate AI Tools & Vendors31:00 — Who Should Be Writing AI Policy for Schools35:00 — Cybersecurity in K-12: The Castle, The Moat & The Breach Plan39:30 — Cyber Civic Engagement & Becoming a Local Advocate43:30 — Speed Round & Closing ThoughtsDon't forget to:✅ Subscribe to My EdTech Life on your favorite podcast platform✅ Leave a review and share this episode with a fellow educator✅ Visit www.myedtech.life for more amazing conversations

Piyush Jain, Founder and CEO of Simpalm and co-founder of Ducknowl, is on a mission to solve real-world challenges by combining technology and entrepreneurship. With over 15 years of experience building custom software solutions, Piyush helps businesses turn complex ideas into practical applications by blending technical depth, business acumen, and a strong problem-solving mindset. We explore Piyush's AI Ideation Framework—Validate idea, Proof of concept, Design, Competitor analysis, and Feature selection—a practical approach to building software in the post-AI era. Piyush explains how AI can help teams better understand user personas, validate product assumptions, and rapidly prototype ideas, while human expertise remains essential in design, architecture, and production-grade development. He also shares how prompt engineering, peer-reviewed prompting, and a right-shoring delivery model can help businesses build smarter, faster, and more cost-effectively. — 3D Print Your Software with Piyush Jain Good day, dear listeners. Steve Preda here with the Management Blueprint, and my guest today is Piyush Jain, the Founder and CEO of Simpalm, a custom software development company, and the co-founder of Ducknowl, a candidate screening and assessment application business for high-volume recruiting. Piyush, welcome to the show.  Thank you, Steve. Thanks for inviting me.  Well, I’m very curious about the stuff that you have to share with us, and I’d like to ask first about your personal purpose. What is your “why,” and how are you manifesting it in your business?  Yeah, so that’s a very interesting question. And I think for every entrepreneur or tech founder, really, that's the motivation—why you want to do certain things. So for me, if I look at it, my personal “why” is: why are we not solving challenges? Or why are we not solving them the right way? Why are we not transforming our lives? I grew up in India and then came to the US, so I've seen many different parts of the world—from Asia to North America. I see people face different challenges, but then we are not focusing on solving those problems. A lot of it I see is there’s a lot of challenges in the world because I believe there are not enough entrepreneurs. Because entrepreneurs are the ones who really take risks, combine everything, and create solutions. That was like me, right? That’s what I learned growing up, that I think I can do that, right? I can combine the technical knowledge and the business acumen and create solutions that people like, solve their challenges. Growing up, like I'm more on the technical side.Share on X I was inclined more toward science and technology, but then as I got into my undergrad and grad school, I realized that I have that entrepreneurship aspect, but it's still around science and technology. That’s when I realized that, you know what, I cannot be a pure scientist or maybe a pure entrepreneur, but I can be someone who can combine these two, because my main driving factor is problem-solving. I can combine these two and then live my life, be very happy with what I do. That has been my motivation. I like it. So solving challenges and being an entrepreneur, and kind of combining the two—being the technical expert and the entrepreneur in one. Now, one of the things that we always talk about on this podcast is frameworks. And you have developed a really good one for AI ideation, which I think is something that everyone needs to do these days or use these days, and it helps you create business apps and other business applications. Can you share with me how that framework works, and what are the steps in it?  Sure, yeah, definitely. So just to give you a brief background, we've been building software for the last 15 years. Some companies have used different frameworks, whether it's Agile or Waterfall in SDLC, in building the software, right? There are different methodology that companies have used, and they've been good, successful—they've played their role. But now, with the advent of AI, things have changed. We had to figure out, in our organization, how to use AI, and that's how this framework was built. My team helped me building this framework as well.Share on X But we realized that we were losing business—we were losing clients—since we didn't have an AI framework that would fit our clients. Again, for me, it's a challenge. So anytime I see a challenge, it create brain juice in me, right? So I said, okay, let's figure out how we create this framework. How did you do it?  So really, we built this framework—very interesting. A lot of the steps are similar, but then a lot of things are different.Share on X Whenever client comes to us and says, “Hey, we want to solve this challenge,” what we do is we do enough research. And now we use a lot of AI tools to really understand the problem better and understand the user persona. When you build any software application, there is a person who's going to use that. Sometimes we used to do user research or focus studies to understand that. Now, with the help of AI, we can get a lot of ideas about the user persona. For example, maybe we are building a healthcare application for an anesthesiologist. I don’t know much about that. I know, I mean, because I have been through some medical surgery and all that, but I can't fully understand their user persona or their requirements with respect to the application we're building. But now, with AI, I can actually ask different AI models, “Hey, we are building this app for anesthesiologists. What are their pain points? How would they see it?” So all that deeper mindset and psychology we can get using AI.  You are validating the idea by interrogating AI applications.  What users are going to like and all that. So I will always use this term earlier. In software engineering, now we have this pre-AI and post-AI, right? If you read history, we talk about before Christ and after Christ, right? Yeah. So it's a similar thing now. Yeah, exactly. Or before Covid, after Covid. Before AI, after we did all the user research and everything and created a requirements document, we would usually do design, create like a visual design of the software. But now, with the AI framework, we don't do that. That's not the next step. What we do instead is create a quick prototype using AI platforms.Share on X  So there are a lot of AI platforms—like Lovable, Claude. Now ChatGPT launched Codex for coding, and Replit. Depending on what kind of application you're building—for example, maybe if you're building a web-based application—then I recommend using Lovable or Replit. They're very good at creating that. Whatever software you want to build, whatever user personas that you’re addressing, you can feed into that and it’ll create like a prototype application. Okay.  So what that does is actually, then this prototype, clients can just take it to their customers or internal users and get feedback. A picture is better than a thousand words. Organizations discussing an idea is very different from when they actually see something. Then everybody starts chipping in—“Oh yeah, I see this in the prototype, but I don't want this,” or “I want to move things around,” or “This is what I want.” Basically, building a prototype on AI platforms is much faster than building wireframes and design prototypes like we used to do earlier. So that has changed. So you're 3D printing your software, right?  Yes, exactly. There you go. Well, that’s a very good way you put it together. Yeah. So, yeah, exactly. You’re just 3D printing the software, right? So you can see it, visualize it, and then once you go through that, it creates a lot of better ideas about the software in faster time. So once you have that, then you go into UI/UX design. So in that also, there are two steps. One is wireframing. Wireframing is like creating the flow in black and white. It's like creating a skeleton of your software. It does not have the color, the font, or the branding, but you just create all the different user journeys, the screens, the flow, and the fields that will be there on the screen. So we have integrated AI into that step as well. Earlier, it used to be created by a designer or a business analyst. Now we are using software like Uizard or UX Pilot, where we define what we want—what kind of user journey, flows, and screens—and it creates that. It spins out those wireframes in minutes. So really that has reduced now. The time it used to take to create wire frames is faster now.  So you're designing the wireframes with AI?  Yes, but it's just the wireframe part of it, and it's still guided by our expert VA or designer—someone who knows how to really visualize things and has done a lot of wireframes and sketches. So they know what to tell the AI. Prompting is very important. It's very important that you know how to prompt—what to ask for—so that you can get variations and differentiation in the wireframes. You don't want a standard AI-created wireframe. Everybody can recognize AI-generated images now, right? If I show you one, you'd say, “Oh yeah, it's AI-generated.” I know that, right? Yeah. So again, we keep the human intelligence. We're not asking AI to create the full software end-to-end. It never works—it'll never work. It just doesn't. I know that's a strong statement, but I'm saying that based on experience and an understanding of human behavior and psychology. So AI agents will not be able to code software, in your opinion?  No, they can do the coding, but they cannot build the whole software end-to-end—a production-deployed software. Because these software are being used by humans. You have to have human intelligence to understand and define what you need and how it works.Share on X You can maybe create some software, but it doesn't work very well. Even if you use all these platforms, you can cut down your production time and cost by 30%, 40%, 50%, right? That's the number we are seeing—30 to 50% reduction, depending on the software you're building and the objectives. So just to recap—you validate the idea by interrogating Claude and ChatGPT, asking about the needs of that customer, the psychology of the customer—that's step number one. Step number two is 3D printing the software with Lovable or Replit—so proof of concept. And then you design the wireframes. And then what's next after you design the wireframes? What's the next step?  So that’s a good thing. That’s it. Now I'm going to talk about the human element—some people listening to this podcast will be surprised. Now it comes to visual design, right? So you've created the skeleton, and now you have to add the skin, the tone, the color, the emotion to the design, to the workflow. Now, we have tried AI, but it doesn't work. It's very monotonous. So we use an experienced visual designer, a UX designer, for that step—to give it emotion. When you use AI—I wish I could show you some examples—it creates very similar kinds of designs for apps and software. So what we did is we gave it three different apps with very different objectives and everything, and the designs it came up with were very similar—blocks, buttons—very monotonous. So there's no differentiation. And design is the main thing that becomes the differentiator, right?  Yeah.  So that's what we learned from our experience. And I say that very categorically in all of my talks—that visual design, final UX, has to be human, not AI.Share on X Because you are communicating emotions, right? And AI is still not there to communicate emotions.  Yeah. It doesn’t have emotions.  Well, some people will argue with you and say, “No, it can understand if you're sad or unhappy.” But my response to that is—it's because we've programmed it that way. But things change based on situation, context, ethnicity, culture, fear—how people express nervousness, fear, and all that—it's very different. So there was this AI video interviewing company five or six years ago. They were sued by the Department of Justice because they were trying to detect emotions of people like anxious, nervous, when the interview was happening.  It turned out their model was trained only on one race—they didn't account for other races or ethnicities. So their model failed, and they were sued by Department of Justice for that. So yeah, emotions is something—maybe they have unlimited dimensions, we don't know. So it's hard to program that. So basically: ideation, prototype, wireframe, and then final visual design—that's the discovery and design framework. Now, when it comes to development framework, this is where AI has been a game changer—the coding part. But again, you have to be very careful about how you use AI in your coding pattern with your coding team. It depends on the application, it depends on the tech stack, right? Every platform has its own strengths and weaknesses. For example, if you want to build a web-based application in the React JS framework, then Lovable is great. That's very good—very efficient and cost-effective. Then Claude is there. Claude has been really good in software engineering. I would say it has been built and designed mostly for coding, right? Anthropic—their idea, their starting point—was coding, how to make coding and software engineering better.  So they've been a front runner in the race. ChatGPT is trying to catch up using Codex, and Copilot is great. Copilot is mostly used by enterprises who are on the Microsoft stack. They use Copilot a lot for coding in .NET and enterprise-level applications. They’re used to co-pilot. It’s because they feel comfortable with Microsoft security policies and all that. That’s fine. But in general, we see Claude to be at the top—from our perspective. We've also built a framework for software coding. In software development, there's a popular process called peer review. So when you create source code, you get it reviewed by your peer—your colleague.Share on X  Is this what happens on GitHub?  Yeah, yes. So basically anywhere—any source code repository—you can do that. So your team members can help you make your code better and more efficient.  Yeah, I understand. But now we have a step called prompt peer review. When you're using prompts to build software, those prompts get reviewed by team members. Because if your prompts are not very specific or good enough all the way through the SDLC, you can run into a lot of challenges trying to fix the code. Because now you have a situation where you have code that you have not written fully, and when you ask AI to change something in the code, sometimes it ends up changing a lot of things that you don't want it to change. Yeah.  That's what we've seen, and that's why we evolved. Before we build any software, we create maybe a 10-, 20-, 30-page prompt document, where we go through each screen and function and write it out. It's very sophisticated—it has evolved really well. But the thing is, it takes a few days to do that within the team, because we know if we do it right, the next step is faster and more accurate. So really, the prompt document—think of it more like an architecture document. Earlier, we used to create a solution architecture document, defining all the tools, the design, everything.  But now it's more like an AI-driven solution architecture document with prompts, which get reviewed by team members. So we do that, and then we run that, and we get the code and everything. So I have a CTO club—I run a CTO Club in Maryland—and I was talking to CTOs. They're all using this, but some of them are so advanced that they actually define the test cases in the beginning. They define, “Okay, this is what I want, this is the function I want, and these are the test cases I want it to pass.” That's even more advanced. If you can do that, you can have very efficient code.  Yeah, I love it.  So is that the end? You have your test cases, you design the prompt, you peer-review the prompt, and you already had the prototype, so now you're coding the software—what's the last step?  Yeah. Then there’s an integration as well. So AI doesn’t do the integration so well. You can do the front-end coding, you can do the back-end coding, you can probably create the APIs. APIs require a lot more human intervention. But once you have that, then you have to connect it, right? You have to connect the front end with the backend. A lot of that is still done by the programmer. It's hard to rely on AI for doing that. And again, it depends on the application. Maybe if it's a smaller application, maybe you can have AI do that. But if it's a bigger application—we mostly build bigger applications—then integration, then final QA and testing, and deployment.  So all that is there. But in each of these steps, you can use some sort of AI tool to speed up the process. But the key is you still have to have your architecture, the process. You have to know the steps more. You have to be a good, experienced developer to use AI efficiently if you want to build a production-ready application. You can build a prototype. Anybody can build a prototype on Replit or Lovable, but it's not going to be production-ready that you can give to your customer and charge them money. So that’s the differentiator.  Yeah, I understand. So Piyush, I’d like to switch gears here. I understand the AI ideation framework—that's great. We talked about the technical part of it, the curiosity, the technical challenges. Let’s talk about the entrepreneurship part, which is also part of your profile. So what drives the growth of your business? What would you say drives it?  For us, there are multiple factors that drive the growth of our business. The first is, again, our problem-solving attitude. Any client that comes to us we communicate in that modelShare on X The problem, the challenge, the solution, the business part, the value proposition we bring. And the second factor is our location. We are here in Maryland, and we have another office in Chicago. So being here, we have a global shoring model—that's a main driving factor of our business from the entrepreneurship perspective. So what the global shoring model is: our client-facing team, the senior team, is here—solution architects, sales engineers, designers, project managers, business analysts—they are here in the US, client-facing. And our dev team and testers are in our offshore locations.  Some people call it hybrid shoring. I call it right shoring. The reason I call it right shoring is because in this model, you have the right people at the right shore, so you get the most value. Here, you have people who understand the culture, the product, the context—because products are used by people in a certain culture. And if you are not in that culture, if you haven't experienced it, it's always harder to design the right software solution. I was one of the first people to start that model here in the DMV area for mid-size and smaller companies. This model existed before, but mostly for large enterprise companies. They have used that. But I started to offer that 16 years ago to smaller companies. Either companies were just going offshore, or they were doing onshore, right? I introduced this hybrid—or right-shoring—model, and it has been well received by our customers. So that’s it.  So what is one thing that you’re trying to figure out in your business right now?  Right now, what I'm trying to figure out in my business is scaling. I mean, we have built solutions for many different industries. We have built solutions for different clients in fintech, healthcare, education, nonprofit, startups, IoT, construction. But now what we are trying to figure out is how do we create some off-the-shelf solutions for different industries? Because one challenge we see is that, from the client's perspective, getting custom software built takes time and money. But in certain use cases, we can have off-the-shelf, industry-specific solutions, and then customize those based on the client's needs.  So that's what we are trying to figure out—across different industries, what those solutions can be—so we can scale and also make it easier. And these are more like AI-driven, off-the-shelf solutions that are customizable. So think of it like Salesforce—its core is off-the-shelf, but then you can customize the front end and a lot of other things. Not exactly like Salesforce, but more like industry-specific solutions for different use cases—nonprofit, construction, right? With those, overall, we can build solutions faster.  That’s fascinating. So how has the offshoring—or right shoring, as you call it—model evolved over the past 10 years? Is it different now than it was 10 or 20 years ago?  Yeah, I think that's a great question. It has evolved and changed. Earlier—maybe 10, 12 years ago—when we were talking about hybrid shoring, we were mostly talking about the US and Asia. But now we have different players. We have the nearshore model, which has become quite popular as well—like South America. We have team members in nearshore locations as well, in South America, because we want to leverage different time zones, resources, and culture. And we've seen very positive results. Then you have Eastern Europe. We have competition from countries like Ukraine, Belarus, Romania, Poland. I think it’s the part of the globalized world, right? It's like energy flowing in different spaces—it's not limited to one place, which is great. That's one way it has evolved.  I also know some companies working in Kenya—there are developers there. Some companies are setting up in East Africa, West Africa. So different places are playing roles now. That’s one thing I see. And now, with the help of AI, what's going to happen is it will play two roles. One— in many situations, with AI, you can do more things onshore. That’s one aspect of it. And second—with AI, someone sitting offshore who knows how to use AI can become very competitive as well. We don't have enough data yet to fully see how this will evolve, but maybe in a year or so, we'll see how it plays out.  But I also find that with these simultaneous translation tools—like Apple, I think an iPhone can now translate in all languages. Essentially, another barrier falls that if the language and knowledge of your offshore contractor is not perfect, they can understand things much more clearly because of simultaneous translation. Even on Zoom, you can now flip a switch and they can read what's being said in their own language during a conversation. So that's amazing, I think.  Yeah. That’s amazing. That’s amazing. They can understand more about the culture and mindset. So that's something have to see. Again, I think it depends on the use case, the application, the problem we're solving. But in some cases, it might be great news for onshore—we can keep more dollars here. But keeping dollars here with AI also means a lot of that spend is going to AI, right? So that's one thing—we have to be very careful. Yesterday, in our tech breakfast, our presentation was about how to optimize your AI tokens. There are some companies spending $150,000 per year per employee on tokens. Wow.  That's like the salary of one employee.  Yeah.  A mid-level developer—$150K—they're spending that much. And then they’re trying to figure out how to optimize it. And on top of that, they have cloud costs, right? AWS, Azure—those costs are still there—and then you add AI. So it's a lot of money. You really have to be very smart about understanding and optimizing it. That’s why the prompting is so important, right? It's not just about getting the right software—it's also about getting the cost down.  Yeah. Again, you need expert people who can prompt well, because it's about being able to communicate well. Prompting is about communication—it's about clarity, brevity, security, all that stuff. So, Piyush, we're coming close to the end of the recording. If someone would like to learn more about the applications you develop, how you're using AI, and how you can help their business develop technology, where can they find you? What's the best way to get in touch with you? Sure, there are many ways people can reach out to me. They can go to my website, www.simpalm.com—we have a contact form there. They can submit the form, or they can reach out to me via email directly at contact@simpalm.com. They can also connect with me on LinkedIn. I'm on LinkedIn—message me there if somebody needs anything. I always like discussing problems and what the solutions can be. If anybody reaches out to me, I'm always very quick to respond.  That's awesome. So Piyush Jain, the CEO of Simpalm—and we didn't even talk about your other business, Ducknowl—thank you for coming, and thank you for sharing your insights and your framework on how to build an ideation framework for AI. So thanks for sharing that. And if you're listening and you enjoyed this conversation, then stay tuned, because every week we have another entrepreneur sharing their insights and frameworks with you. So make sure you follow us on YouTube, subscribe, and give us a review on Apple Podcasts. So thanks for coming. Thank you, Steve. It was a pleasure talking to you. Important Links: Piyush's LinkedIn Piyush's website

Send us Fan MailYour AI looks 80% done. In reality, it's 20% done, and the last mile is a cliff. Greg Whalen, CTO of Prove AI, breaks down why CTOs are getting blindsided by AI, why vibe coding creates a false sense of progress, and what most teams are missing when it comes to AI telemetry and observability.Greg has led engineering at global scale as CTO of ZendIt, GM for Amazon WorkMail at AWS, and was an AI researcher at Columbia's NLP group. Now he's building Prove AI to help enterprises move from "mostly working" to production-grade AI systems.We dig into: why AI isn't just another tool in the toolbox, the morning coffee debugging nightmare, how agents exploit other agents for restricted data, why thumbs up/down tells you nothing about outcomes, the vibe coder vs. super principal divide, why CTOs need to "get back in the ring," and why being a first mover beats waiting for convergence that isn't coming.Prove AI → https://proveai.comClick Here to Subscribe: FUTR.tv focuses on startups, innovation, culture and the business of emerging tech with weekly podcasts talking with Industry leaders and deep thinkers.Occasionally we share links to products we use. As an Amazon Associate we earn from qualifying purchases on Amazon.

THIS is how you know you're not really ready for primetime. Today, we're bringing you our most timeless advice from our last conversation with Alan Williamson, Author of Think Like a CTO. We discuss why most first-time CTOs struggle to communicate with non-technical executives, how to think about budgeting and engineering costs like a true technology leader, and why the ability to articulate a clear vision is what separates a real CTO from a CTO in name only. All of this right here, right now, on the Modern CTO Podcast!  To learn more about Alan Williamson, check out his website here.

Are leg arteries ever "too small to treat"?   Around the world, many patients with Peripheral Artery Disease (PAD), especially those with below-the-knee and small vessel disease, are told their arteries are "too small" or "too distal" for intervention.   In this episode of The Heart of Innovation, hosts Kym McNicholas and Dr. John Phillips interview Dr. Naoki Hayakawa, Chief and Director of Endovascular Therapy at Asahi General Hospital in Japan.Dr. Hayakawa is internationally recognized for tackling the most complex chronic total occlusions (CTOs), including small-caliber below-the-knee vessels that others may consider untreatable.  He has served as a live demonstration operator at major international meetings including JET, CCT Peripheral, Kokura Live, and Peripheral CTO Seminars, and has published extensively on:  • IVUS-guided wiring techniques  • Below-the-knee chronic total occlusions  • Drug-coated balloon therapy  • Transradial approaches for complex PAD  • Advanced re-entry and retrograde access techniques   His work challenges outdated assumptions about what is and isn't possible in limb salvage.In this conversation, Dr. Hayakawa sets the record straight on:  • What can truly be treated in small vessel PAD  • When vessels are actually too small  • The importance of imaging and IVUS guidance  • Why patients must seek experienced operators for complex disease  • What global standards of care should look like  If you or someone you love has been told "nothing more can be done," this episode is essential viewing.   - Concerned about leg circulation or told your vessels are too small?Call the Leg Saver Hotline: 1-833-PAD-LEGSBecause "too small to treat" should never be the final answer without expert evaluation.   Subscribe to The Heart of Innovation for global leaders in vascular innovation, limb salvage, and PAD care.  #PeripheralArteryDisease#PAD#LimbSalvage#BelowTheKnee#ChronicTotalOcclusion#EndovascularTherapy#IVUS#CriticalLimbIschemia

Unlock the future of cybersecurity where AI agents no longer just assist—they act autonomously, making decisions that could impact your entire organization. In this eye-opening episode, Vidit Arora, founder and CEO of Quillr AI, reveals how rapidly AI-powered agents are transforming the digital landscape—and why traditional security systems are already obsolete.As AI agents gain full control over data movement, system modifications, and even decision-making processes, security professionals face unprecedented challenges. Vidit uncovers why existing frameworks like DLP and CASB fall short in this new era, and how the lack of contextual understanding enables agents to bypass legacy controls. You'll discover how the speed at which AI agents evolve makes zero-day threats look slow—and the urgent need for inline reasoning and adaptive defenses to keep pace.We break down critical topics such as:The shift from AI assisting to AI acting with autonomy and intentWhy current security paradigms can't catch or control fully autonomous agentsHow understanding agent context, intent, and ecosystem visibility is now a security imperativeThe role of a new decision layer that inlines reasons over agent actions in real timePractical strategies for achieving comprehensive AI footprint discovery and controlFailing to adapt to this new AI-driven environment risks data breaches, operational chaos, and the loss of control over your digital assets. But by embracing a proactive, context-aware security approach, you open the door to innovation—without risking your organization's future.Perfect for security leaders, CTOs, and AI strategists, this episode will challenge everything you thought you knew about cyber defense. If you're serious about safeguarding your organization amid AI's explosive growth, you'll want to hear this now.Visit quiller.ai to explore cutting-edge AI visibility tools and learn how to future-proof your security stance. Don't let autonomous agents catch you off guard—stay ahead of the curve before the next disruptive move takes you by surprise.

At Davos this year, some of the biggest names in tech sent a clear signal. AI is no longer a novelty. It is no longer a proof-of-concept exercise. As Demis Hassabis of Google DeepMind suggested, AI will shape more meaningful work. And Satya Nadella of Microsoft was even more direct. AI only matters if it improves real outcomes for people. So what does that look like inside the enterprise? In this episode of Tech Talks Daily, I'm joined by Andrew Boyagi, Customer CTO at Atlassian, to unpack how the conversation has shifted from experimentation to execution. Developers, in many ways, are the perfect lens for understanding this moment. Over the last two decades, their role has expanded far beyond writing code. They now own products, infrastructure, operations, and business outcomes. AI is simply the next chapter in that evolution. Andrew argues that AI will not replace engineers. It will raise expectations. As intelligent tools absorb repetitive work, the real value moves up the stack. System design. Architectural thinking. Reviewing and refining AI-generated output and orchestrating solutions that solve genuine business problems. And through it all, humans remain firmly in the loop. We also explore what this means for leadership, why mindset is starting to matter more than technical skill alone, how organizations can avoid layering AI on top of broken processes. And why the companies pulling ahead are treating AI as a strategic discipline, not a feature upgrade. This is a conversation grounded in reality. It speaks to product leaders, CTOs, CIOs, and anyone asking a simple but powerful question. If we are investing in AI, what are we actually getting back? And before we close, we look ahead to Team '26 and the themes Andrew and his team are already working on.  If this year has been about proving value, what will the next chapter demand from enterprise leaders? As always, I'd love to hear your thoughts. Are you seeing proof of value in your organization yet, or are you still working through the pilot phase?

What happens when leaders are confident about AI, but the people expected to use it are not ready? In this episode of Tech Talks Daily, I sat down with Caroline Grant from Slalom Consulting to explore one of the most persistent tensions in enterprise AI adoption right now. Boards and executives are spending more, moving faster, and expecting returns sooner than ever, yet many organizations are struggling to translate that ambition into outcomes that scale.  Caroline brings fresh insight from Slalom's latest research into how leadership, culture, and workforce readiness are shaping what actually happens next. We unpack a clear shift in ownership for AI transformation, with CTOs and CDOs increasingly leading organizational redesign rather than HR. That change reflects how deeply AI now cuts across technology, operations, and business models, but it also introduces new risks.  Caroline explains why sidelining people teams can create blind spots around skills, incentives, and trust, especially as roles evolve and uncertainty grows inside the workforce. The result is what Slalom describes as a growing AI disconnect between executive optimism and day-to-day reality. Despite the noise around job losses, the data tells a more nuanced story. Many organizations are creating new AI-related roles at a pace, yet almost all are facing skills gaps that threaten progress. We talk about why reskilling at scale is now unavoidable, how unclear career paths fuel employee distrust, and why focusing only on technical capability misses the human side of adoption.  Caroline also challenges assumptions about skill priorities, warning that deprioritizing empathy, communication, and change leadership could undermine effective human-AI collaboration. We also dig into ROI expectations, with most UK executives now  expecting returns within two years. Caroline shares why that ambition is achievable, where it breaks down, and why so many organizations remain stuck in pilot mode. From governance and decision rights to culture and leadership behavior, this conversation goes beyond tools and platforms to examine what separates experimentation from fundamental transformation. As AI becomes a test of leadership as much as technology, how are you closing the gap between vision and execution within your organization, and are you building a workforce that can keep pace with change rather than resist it? Connect With Caroline Grant from Slalom Consulting The Great AI Disconnect: Slalom's Insights Survey Learn More About Slalom

Matt is joined by Karell Ste-Marie, founder of The Serious CTO YouTube channel. Together, they tackle one of the biggest hidden challenges in software companies: the language and cultural barrier between engineers and executives.Karell and Matt break down why innovation is so rare in large organizations, why engineers and business leaders often talk past each other, and how the CTO role often becomes the critical bridge between the two worlds.Key Discussion PointsThe cultural resistance to change inside enterprisesHow introversion and communication style shape engineering cultureWhy the best CTOs speak “both languages”Lessons from mistakes made on the path to leadershipResources & LinksThe Serious CTO on YouTube – Karell's channel where he shares insights on engineering leadershipProduct Driven - Get the BookSubscribe to the Product Driven NewsletterWhat Smart CTOs Are Doing Differently With Offshore Teams in 2025Subscribe to the Global Talent SprintFull Scale – Build your dev team quickly and affordably