Free Daily Podcast Summary
Tech Talks Daily: Daily Summaries Delivered
by Neil C. Hughes
If every company is now a tech company and digital transformation is a journey rather than a destination, how do you keep up with the relentless pace of technological change? Every day, Tech Talks Daily brings you insights from the brightest minds in tech, business, and innovation, breaking down complex ideas into clear, actionable takeaways. Hosted by Neil C. Hughes, Tech Talks Daily explores how emerging technologies such as AI, cybersecurity, cloud computing, fintech, quantum computing, Web3, and more are shaping industries and solving real-world challenges in modern businesses. Through candid conversations with industry leaders, CEOs, Fortune 500 executives, startup founders, and even the occasional celebrity, Tech Talks Daily uncovers the trends driving digital transformation and the strategies behind successful tech adoption. But this isn't just about buzzwords. We go beyond the hype to demystify the biggest tech trends and determine their real-world impact. From cybersecurity and blockchain to AI sovereignty, robotics, and post-quantum cryptography, we explore the measurable difference these innovations can make. Whether improving security, enhancing customer experiences, or driving business growth, we also investigate the ROI of cutting-edge tech projects, asking the tough questions about what works, what doesn't, and how businesses can maximize their investments. Whether you're a business leader, IT professional, or simply curious about technology's role in our lives, you'll find engaging discussions that challenge perspectives, share diverse viewpoints, and spark new ideas.
Latest Episodes
The most recent episodes — sign up to get AI-powered summaries of each one.
- 2 days ago22 min
Current 2026: Why Confluent's Streamhouse Could Solve AI's Real-Time Data Problem
What happens when an AI agent makes a business decision using information that's already out of date? It's a question I wanted to put to Stephen Deasy, CTO of Confluent, when we met at Current 2026 in San Francisco. After attending more than 20 technology conferences this year, I've heard countless promises about what AI agents will eventually achieve. But there's a growing problem behind those ambitions. Businesses are still struggling to get accurate, current information out of the systems they already own. Confluent has introduced Streamhouse, a data architecture designed to address that problem. Stephen explains why the company believes existing approaches can leave applications working with delayed or incomplete information, and how the new architecture brings streaming, processing, governance, and querying together. We also discuss Lightning Tables, one of Confluent's major announcements at the event, and what direct access to current Kafka data could mean for developers and their businesses. I was particularly interested in what this means for companies that have already invested heavily in data warehouses and lakehouses. Stephen makes the distinction between analyzing past performance and running business operations using current information. He explains why Confluent sees these approaches working together, and why existing technology investments can provide the foundation for introducing Streamhouse. We also discuss the experiences of Instacart and Citizens Bank. Stephen recalls how Instacart faced a sudden increase in demand during the pandemic, when accurate information about orders, inventory, and deliveries became especially important. He also describes how Citizens Bank improved loan fulfillment processes through real-time data streaming. Both examples help explain why the speed at which information moves between business systems can affect customers directly. The conversation also covers IBM's relationship with Confluent, open technologies including Kafka and Flink, and the announcement that Tableflow is now generally available on Google Cloud. Stephen shares his thoughts on model evaluation, human oversight, and how companies should measure returns from their technology spending. One of my final questions concerns the misconceptions surrounding Streamhouse. Stephen explains that the architecture brings together approaches many organizations have already been working toward, and that its value lies partly in making those capabilities easier to use together. With so much money being invested in AI, are businesses paying enough attention to the information those systems depend on? Listen to our conversation and share your thoughts.
- 3 days ago19 min
Bringing enterprise AI inference on premises with Scality
What should a business consider before moving AI inference onto infrastructure it owns? In this episode of Tech Talks Daily, I speak with Paul Speciale, Chief Marketing Officer at Scality, about the decisions behind enterprise AI infrastructure. Following the launch of Scality AI Inference Factory, we discuss why organizations are assessing on-premises inference alongside cloud services, with attention to costs, model control and the location of sensitive data. Paul expects a hybrid approach, with different workloads running in the environments that suit their requirements. The conversation begins with the work a GPU repeats when an AI session needs to process familiar context. Paul explains how saving and retrieving that information can reduce recomputation, and why storage and networking deserve attention alongside compute. We discuss where the economics change as usage grows and why owning the infrastructure also means taking responsibility for utilization, performance and the operating bill. We then consider data placement across storage tiers. Paul argues that there is no single best location for every workload, with performance, cost and sovereignty requirements shaping the decision. I ask where automation should stop and human approval should begin. He describes automating health checks, forecasts and recommendations while retaining approval for consequential changes such as deleting data or changing policies. Cyber resilience is another part of the discussion. Paul explains why an immutable copy needs to be supported by tested recovery, and why sovereignty rules should be checked through attempts to perform actions the system is meant to refuse. We close with the responsibilities infrastructure teams take on as they manage inference directly, from tracking time to first token and context reuse to deciding when a model should change. For leaders assessing their next AI deployment, the conversation offers practical questions about control and the evidence behind the business case. Which workloads would you consider running locally, and what would you want to prove before making that decision? Please share your thoughts with me.
- 4 days ago26 min
Electrifying Collection Fleets and Improving Driver Safety With Republic Services
How do you introduce electric vehicles and AI-assisted safety technology into a collection fleet that customers depend on every day? On Tech Talks Daily, I'm joined by Brett Rogers, Vice President of Operations Technology at Republic Services, to discuss the engineering, infrastructure, and human decisions behind modern waste and recycling operations. Brett's background includes work at Toyota, General Motors, and Cruise. He describes arriving from the automotive sector and discovering how much complexity sits behind a service most people expect to happen without thinking about it. We give particular attention to electric refuse trucks. Range is part of the calculation, but the vehicle also powers equipment that lifts containers and handles material. Brett explains how Republic Services models energy use across the chassis and collection body, taking account of terrain, climate, speed, and the work required on a route. The goal is to identify where an electric vehicle can replace a conventional truck while maintaining service. Route selection can produce some surprising answers. A residential truck making frequent stops may benefit from regenerative braking, while a vehicle with fewer container lifts can spend much of its day covering distance. Brett describes why his team began with residential applications, then used operational data to inform expansion into other vehicle types. The number of lifts alone does not tell the whole story. Charging has its own planning cycle. Brett says utility discussions, design, and construction can require decisions roughly two years before trucks are needed. We discuss why depot readiness has to lead vehicle delivery, alongside the arrangements that keep service running if power is interrupted. He describes spare vehicles and equipment that can accept emergency power, while on-site storage and renewable energy form part of the options being considered. These approaches have different levels of maturity, and the conversation keeps that distinction clear. Technology-enabled safety is the other major focus. Brett describes adding a bird's-eye camera view to help drivers see around large vehicles, then working with vendors on systems that distinguish people from objects. Spoken alerts such as "pedestrian rear" are intended to tell a driver what is happening and where, without requiring them to keep checking another screen. The discussion goes beyond installing cameras. Brett says in-cab alerts were associated with an initial reduction of around 20% to 30% in what Republic Services calls unfocused behaviors. He reports a reduction of 95% after coaching was added to the approach. These are company-reported behavioral measures, not a claim that collisions fell by 95%. No evaluation period or underlying methodology is provided in the interview. The useful operational lesson is the connection between technology, explanation, and the opportunity for drivers to correct a recurring behavior. We also discuss employee adoption. Brett recalls drivers who were initially reluctant to move from diesel trucks and describes how time in the electric vehicles changed their view. He points to lower noise, vibration, and heat, alongside cab design. His account is a reminder that the experience of the person doing the job can determine whether a promising deployment becomes a useful everyday tool. We finish with routing visibility for municipal customers and plans to use AI and other tools to improve operations. For fleet leaders, the conversation offers practical considerations around duty cycles, charging resilience, driver support, and measuring results. For everyone else, it reveals the work behind a truck arriving on the right street at the right time. I'd welcome your thoughts. What would give you the most confidence in an electric fleet rollout, and how should organizations demonstrate that their safety technology is helping drivers and communities?
- 5 days ago26 min
Building Trust in Production AI Agents With Caylent.
What would make you comfortable giving an AI agent the authority to act inside a live business process? In this episode of Tech Talks Daily, I speak with Valerie Henderson, CEO of Caylent, about what has to happen between a successful demonstration and a system a business can depend on. The conversation centers on production readiness, including access controls, spending limits, traceability, workflow design, and the people responsible for the outcome. Valerie describes why introducing agents requires changes to how work gets done. If an organization adds new technology without reconsidering the handoffs and decisions around it, the hoped-for productivity gains can remain difficult to achieve. Her advice is to begin with a bounded problem where automating a few steps could provide a clear benefit, then build on the evidence rather than starting with an ambitious network of agents. We discuss the difference between read-only workloads and agents that can alter live systems. Valerie says many customers are already comfortable with agents retrieving information, while autonomous operations such as self-healing infrastructure are concentrated among the most advanced customers she sees. Those observations reflect her experience with Caylent engagements. They do not establish a universal level of enterprise adoption. For me, one of the most useful questions is what meaningful human oversight looks like. Valerie is clear that people remain accountable for the instructions and access they give agents. She emphasizes deliberate testing, appropriate governance, and the ability to understand what a system has done. We also discuss how agents can repeat work without producing anything useful, creating a bill that needs to be considered alongside accuracy and reliability. The conversation moves into Caylent's own operating model. Valerie describes moving away from assumptions built around human time and materials, making existing technical knowledge easier to reuse, and changing delivery incentives to reward speed and customer satisfaction. It is a practical reminder that organizations adopting AI may need to reconsider what they reward as well as which tools they buy. She also shares a customer example involving Smarsh. According to Valerie, redesigning its software delivery process with agentic AI freed engineering capacity that could be reinvested in the business. She describes that capacity in financial terms, but the interview does not establish a measurement period or separate capacity value from realized cash savings. The useful lesson is the connection between a defined objective and a decision about how to use the resulting capacity. We touch on Caylent's agentic AI readiness research, while keeping the broader discussion focused on practical experience. The useful question for leaders is what controls and evidence should come before greater autonomy, and how they will reassess that decision as the system changes. Finally, Valerie explains how she thinks about success for employees as well as customers. She wants technologists to have time for difficult problems and opportunities to develop their skills. She also argues that customers should be able to explain the value of the work they have undertaken. Model performance is part of that assessment, alongside the environment, permissions, costs, and business process in which the agent operates. I would love to hear how your team is making these decisions, so please share your thoughts. Which responsibilities are you ready to delegate to an AI agent, and what evidence would you need before going further? Useful Links Caylent website: https://caylent.com/ Caylent's Agentic AI Readiness survey report: https://caylent.com/blog/agentic-engineering-survey-report <
- 6 days ago25 min
Connecting AI Fall Detection With Care Workflows at KamiVision.
What makes an AI fall alert useful to the person who needs help and the team responsible for responding? In this episode of Tech Talks Daily, I speak with Mike Link, chief operating officer at KamiVision, about deploying computer vision in residential care. We discuss the connection between the sensor, the people receiving its notifications, and the decisions that follow. The conversation also looks at privacy, connectivity, false alarms, and why a system that works in a care facility needs further work before it can serve a wide range of homes. Mike describes KamiVision's path from home-security cameras to its KamiCare platform. His account of fall detection involves three stages. A device identifies a possible event, a cloud model filters notifications, and a person reviews a blurred, encrypted clip before an alert reaches the user. The human review is part of the service he describes, so it belongs in any discussion of how the system performs. I ask about the company's 99.5% accuracy claim and what buyers should understand before relying on a number like that. Mike explains the filtering process, but the interview does not establish a test population, a missed-event rate, or a complete statistical definition. His answer is a starting point for further questions about performance across the whole service, rather than proof that a device detects 99.5% of all falls by itself. One of the most useful examples concerns a resident found on the floor. Mike describes how reviewing an event can help staff understand whether someone fell or deliberately lowered themselves because they needed help with a task. That information may lead to a change in a routine or room layout. It is an example of how visual context can inform care, rather than an independently measured claim that the technology prevents injuries. We also discuss the difference between a managed care setting and a home. A residential facility can have relatively consistent room layouts and lighting. Homes introduce furniture, pets, several rooms, and areas outside a sensor's view. Mike talks about investigating other sensing technologies to address those gaps. He presents those ideas as work under consideration, not a set of generally available capabilities. Connectivity is another practical issue. Mike says the version discussed uses Wi-Fi and that a cellular option has been considered. He also explains that the consumer version was being tested with families and was not yet available to purchase at the time of recording. That distinction between an established care-facility offering and a product still being developed matters when assessing where the technology can be used today. Privacy and consent are part of deployment. Mike says facilities obtain consent from residents or an appropriate representative, and he describes the service as focused on event clips rather than live viewing into a room. Those explanations help frame the conversation a buyer should have about access, retention, review, and the information people are agreeing to share. Finally, we discuss the business case. Mike connects the value of event information with staff response, communication with families, and adjustments to care. He also describes possible reporting and risk-identification capabilities that had not been deployed. The interview offers a view of the operational questions involved, without establishing a controlled clinical result or a fully quantified return on investment. I would love to hear your thoughts, so please share your experiences. How should care providers assess whether an AI alert improves the work people do, while respecting the privacy and choices of those receiving care?
- 1 weeks ago27 min
What Proof of Reserves Can Tell You With LeveX
What can a crypto exchange's proof of reserves establish, and what might still be missing from the picture? On Tech Talks Daily, I'm joined by Harvey Liu, co-founder and CEO of LeveX, to discuss transparency, platform engineering, and the responsibilities that come with operating a centralized exchange. Harvey brings a computer science background, an MBA, and experience in venture capital. Our conversation looks at how becoming a founder changed the questions he asks about growth, spending, product delivery, and customer assets. We begin with the community idea behind LeveX. Harvey recalls meeting other crypto investors and wanting an online environment where people could discuss ideas alongside trading. He describes that as part of the motivation for building the company. The interview also makes clear that some social features remain in development or are planned for a later release. A community vision and a finished product roadmap are different things, and the discussion gives listeners a view of that work in progress. The central technology question is proof of reserves. Harvey explains why a snapshot should be considered in context, including its date, the assets it contains, and the liabilities it may not reveal. He discusses the limitations of relying on a platform's own token and the difficulty of understanding obligations outside the information shown. Publishing reserve information can contribute evidence, but the conversation does not establish that a snapshot alone proves a business is solvent or that customer assets are protected under every condition. We also discuss the engineering approach Harvey says LeveX uses. He describes Merkle-tree verification, user account inclusion, and separating parts of the reporting process from the live trading environment. The challenge is to provide useful information while managing privacy and system load. His explanation is a founder's account of the architecture, rather than an independent technical audit or a live demonstration. From there, the conversation turns to the realities of building the business. Harvey says he underestimated how much product development investment would be needed to compete with larger teams. He also describes the difference between taking a minority investment position and being responsible for the operation itself. Cash flow, customer growth, infrastructure decisions, and the consequences of a failure become immediate concerns rather than topics for a periodic review. Security and AI bring further tradeoffs. Harvey describes security reviews, operational controls, and the ability to suspend certain functions if something appears wrong. He also discusses AI-assisted development and analysis, alongside agents being built to help with order placement. These ideas raise questions about access, authorization, accuracy, and responsibility. The interview does not demonstrate those systems or establish that AI-generated analysis improves trading results. Availability is another part of the discussion. Harvey says LeveX restricts access from jurisdictions including the United States, the United Kingdom, Singapore, and mainland China. He describes licensing work as being in progress, rather than announcing completed authorizations. This episode examines a technology business and its founder's decisions. It does not recommend opening an account or imply the service is available in every listener's location. We close with Harvey's views on decentralized exchanges and plans for additional social features, competitions, and copy trading. These remain company plans as described at recording, without a verified delivery schedule or a promise of financial returns. For listeners interested in platform design and founder accountability, the useful thread is how to question evidence, distinguish current operations from future ambitions, and assess what a company is actually claiming. Please share your thoughts. What should exchanges make easier to understand about their reserves, liabilities, and operating controls so people can assess their claims with greater clarity?
- 1 weeks ago28 min
Reducing IT Firefighting With ControlUp
What needs to happen before an IT team can trust an AI agent to resolve a problem rather than simply report it? In this episode of Tech Talks Daily, I welcome Jed Ayres, CEO of ControlUp, and Gadi Feldman, Chief Product Officer, to discuss autonomous endpoint management and the practical work behind it. We begin with a familiar problem for enterprise IT teams, plenty of monitoring data and recurring issues that still require investigation, ticket transfers and manual intervention. Jed explains why the aim is to follow an operational problem through to an authorized action and then verify that the issue has been resolved. Gadi describes how specialist agents could bring together expertise across areas such as endpoint management, networking and storage. We discuss the connections those agents need to existing tools and why an understanding of the technology is only part of the job. Agents also need access to company procedures, priorities and knowledge, much as a new member of an IT team needs to learn how the organization works. Gadi explains how configurable human approval and other controls form part of that approach, with teams able to begin with analysis and recommendations before allowing additional actions. Jed shares a CHRISTUS Health example involving an audio driver issue across approximately 900 devices, illustrating the value of seeing a common pattern rather than treating every device as a separate support problem. We also discuss what a useful business case should measure. Alongside the time spent by IT, leaders need to consider the employee's experience of waiting for help or finding a workaround. Device performance and software usage can also inform decisions about equipment replacement and unused licenses. The conversation considers what becomes possible when repetitive work takes less of the team's time, while acknowledging the need to establish trust and define the limits of autonomy. For leaders looking for a starting point, Jed describes ControlUp's seven-day challenge, and Gadi recommends understanding the fleet already in place. Which recurring IT problem would you address first, and what evidence would convince your team that automation was helping? Please share your thoughts with me.
- 1 weeks ago23 min
Making AI the ERP Interface With NetSuite
When would you trust your ERP system to move from answering a question to carrying out the work? Recording at SuiteWorld in Las Vegas, I spoke with Brian Chess, who leads AI product and technology for Oracle NetSuite, about what that progression looks like in practice. Brian was an early developer when the business was called NetLedger, later left to build a company, and returned with a different perspective on the needs of small and growing businesses. Our conversation focuses on how AI can help people understand their systems, complete unfamiliar tasks, and gradually delegate work without losing control of the process. One of Brian's most useful ideas is AI acting as a teacher. He describes users asking Ask Oracle who has logged into their account, or asking it to explain a script they do not fully understand. The benefit is the answer and the explanation of how to find it. Someone who previously needed help from a colleague can begin to understand a part of the system for themselves. He also shares an example involving NetSuite customer MCNC. When the payroll administrator was unavailable, Brian says a controller who had not been trained on the process used Ask Oracle for guidance. The outcome he describes is straightforward and meaningful: payroll ran on time. It is a customer account from the interview, rather than an independently assessed result, but it illustrates how useful AI assistance can be without requiring a dramatic productivity claim. Financial close provides another practical example. Brian describes starting with the spreadsheet a finance team already uses, modelling that process inside NetSuite, and introducing automation in stages. I recognise the appeal of that approach from my own time supporting month-end and year-end work in IT. Teams need to understand how the process will run, especially when a mistake can affect reporting or the system of record. We discuss how permissions apply as software gains the ability to act. Brian says Ask Oracle operates with the permissions of the user, while an agent receives an assigned role governing its access. He describes a progression from read-only analysis to limited changes as users gain confidence. Human approval remains available for transactions, particularly while teams refine instructions and account for cases they may have missed. Business context and shared knowledge are part of the same discussion. Brian explains how written skills can capture procedures and the intended business outcome, making knowledge available beyond the colleague who usually handles the task. We also talk about accountability. He describes transaction records showing which agent acted and when, together with an activity log. Those records help establish what happened, although they should not be confused with a complete explanation of every internal model decision. The conversation also covers whether to build AI capabilities or use those embedded in a business platform. Brian's answer depends on the role the capability plays in a company's competitive position, the expertise available, and the time it wants to invest. His view of ROI is similarly specific to the business. Comparing vendor contracts with billing records may reveal savings, but the same result does not necessarily transfer to a company with different suppliers and arrangements. We finish with the opportunity Brian sees for smaller businesses that have fewer specialists available. AI assistance may help people undertake work they previously needed a consultant or experienced colleague to explain. The question is how to extend that access while retaining appropriate permissions, review, and responsibility. I would love to hear your thoughts, so please share your experiences. Where would conversational ERP make the biggest difference in your business, and which actions would you still want a person to approve?
Get Tech Talks Daily summaries in your inbox
Free AI-powered daily recaps. Key takeaways, quotes, and mentions — in a 5-minute read.
Get Free Summaries →Free forever for up to 3 podcasts. No credit card required.
You Might Also Like
Listeners also like.
The AI Daily Brief: Artificial Intelligence News and Analysis
A daily analysis of artificial intelligence news, exploring its creative potential, industry impacts, and ethical challenges.
Smart Talks with IBM
Conversations with leaders leveraging AI, quantum computing, and emerging technologies to transform global businesses.
AI Business Daily
Daily insights into AI, tech trends, and digital innovation for entrepreneurs and professionals navigating the future of business.
TED Tech
Experts examine how technology reshapes society, science, design, and business through TED Talks hosted by Sherrell Dorsey.
The AI in Business Podcast
Interviews with AI executives reveal practical applications and strategic insights for business leaders adopting AI.
The AI XR Podcast
Insightful interviews with tech founders and executives on AI, virtual reality, augmented reality, and the future of spatial computing.
Everyday AI Podcast – An AI and ChatGPT Podcast
Covers practical uses of AI tools like ChatGPT and Midjourney to help people work more efficiently and advance their careers.
Sources with Alex Heath
A podcast offering insider interviews with influential tech leaders and rising entrepreneurs shaping Silicon Valley's future.
"The Cognitive Revolution"
Explores the transformative impact of artificial intelligence through interviews with innovators shaping its future.
Expert Intelligence with Paul Estes
Explores the intersection of human expertise and AI in shaping the future of work through interviews with industry leaders and innovators.
What Comes Next with Arun
Explores how data and AI strategy create competitive advantage in business, based on real-world enterprise experience.
Me, Myself, and AI
Leaders from top companies share real-world strategies for turning artificial intelligence into measurable business results.
About Tech Talks Daily
If every company is now a tech company and digital transformation is a journey rather than a destination, how do you keep up with the relentless pace of technological change? Every day, Tech Talks Daily brings you insights from the brightest minds in tech, business, and innovation, breaking down complex ideas into clear, actionable takeaways. Hosted by Neil C. Hughes, Tech Talks Daily explores how emerging technologies such as AI, cybersecurity, cloud computing, fintech, quantum computing, Web3, and more are shaping industries and solving real-world challenges in modern businesses. Through candid conversations with industry leaders, CEOs, Fortune 500 executives, startup founders, and even the occasional celebrity, Tech Talks Daily uncovers the trends driving digital transformation and the strategies behind successful tech adoption. But this isn't just about buzzwords. We go beyond the hype to demystify the biggest tech trends and determine their real-world impact. From cybersecurity and blockchain to AI sovereignty, robotics, and post-quantum cryptography, we explore the measurable difference these innovations can make. Whether improving security, enhancing customer experiences, or driving business growth, we also investigate the ROI of cutting-edge tech projects, asking the tough questions about what works, what doesn't, and how businesses can maximize their investments. Whether you're a business leader, IT professional, or simply curious about technology's role in our lives, you'll find engaging discussions that challenge perspectives, share diverse viewpoints, and spark new ideas.
Customized Recaps
AI-powered recaps with compact key takeaways, quotes, and insights.
Straight to Your Inbox
Get key takeaways from Tech Talks Daily in a 5-minute read.
Save Hours Every Week
Stay current on your favorite podcasts without falling behind.
Frequently Asked Questions
What is Podzilla's Tech Talks Daily daily summary?
It's a free AI-powered email that summarizes new episodes of Tech Talks Daily as soon as they're published. You get the key takeaways, notable quotes, and links & mentions — all in a quick read.
How does the Tech Talks Daily podcast summary work?
When a new episode drops, our AI transcribes and analyzes it, then generates a personalized summary tailored to your interests and profession. It's delivered to your inbox every morning.
Is this an official Tech Talks Daily product?
No. Podzilla is an independent service that summarizes publicly available podcast content. We're not affiliated with or endorsed by Neil C. Hughes.
Can I get summaries of other podcasts too?
Absolutely! The free plan covers up to 3 podcasts, any in the catalog. Basic raises that to 15, Pro to 40 and Max to 100. Browse our full catalog at /podcasts.
How often does Tech Talks Daily release new episodes?
Tech Talks Daily publishes daily. Our AI generates a summary within hours of each new episode.
What topics does Tech Talks Daily cover?
Tech Talks Daily covers topics including News, Technology. Our AI identifies the specific themes in each episode and highlights what matters most to you.
Start getting Tech Talks Daily summaries tomorrow morning.
Free forever for up to 3 podcasts. No credit card required.
Free forever for up to 3 podcasts. No credit card required.