Tech Talks Daily

What would change if your building could help explain what needs attention, why it matters, and whether the action you took actually worked?
In this episode of Tech Talks Daily, I welcome Bert Van Hoof, CEO of Willow, back to the show to discuss operational AI for buildings and infrastructure. Bert spent about 20 years at Microsoft, where his work included launching Azure Digital Twins. He now works with environments such as hospitals, airports, universities, corporate campuses, and data centers, where the condition of a physical space can directly affect the work happening inside it.
We begin with a problem familiar to many facilities teams. Buildings already have sensors, management systems, meters, maintenance records, and dashboards. Having access to information does not necessarily help an operator decide what to do next. Bert describes operational AI as a way to move through a sequence of questions: what is happening, why is it happening, what might happen next, what should we do, and did the action produce the expected result?
Context gives those questions meaning. A temperature reading alone cannot tell us whether a room is operating correctly. We need to know the room's purpose, occupancy, equipment, weather conditions, and recent maintenance history. Bert explains how digital twins and knowledge graphs connect those relationships so that a system can assess the situation rather than interpret a sensor value in isolation.
The discussion then turns to predictive maintenance. A probability of failure may be useful to an analyst, but a technician also needs to understand the consequence, urgency, and next step. Bert describes how condition-based maintenance can support equipment decisions and how earlier detection can reduce the disruption caused by refrigeration problems or water leaks.
These are practical examples of the types of outcomes Willow targets, rather than a claim that every customer will achieve the same result.
There is a human side to the conversation too. Bert describes operators opening numerous browser tabs each morning to assemble a picture of their buildings. Daily briefings and natural-language questions could reduce that search effort, helping teams focus their attention on the issues that deserve it.
We also discuss the relationship between occupancy, ventilation, energy consumption, comfort, and maintenance. Bert describes Willow's Active Control and the use of schedules and occupancy signals to help buildings respond to how spaces are being used. His argument is that these decisions should account for the whole environment. Saving energy in isolation can create different problems if comfort, reliability, or safety is overlooked.
Trust runs through the interview. A poor recommendation in a hospital has different consequences from an awkward paragraph in a document. Bert argues for explainable recommendations, operational evidence, defined limits, and verification after an action. He also sees experienced facilities engineers as part of the solution, with responsibility for setting objectives and judging trade-offs.
For me, the larger question is how building operations connect with the organization's purpose. A hospital needs spaces and equipment ready for patient care. An airport needs to account for passengers, flights, gates, and changing demand. Understanding the environment means understanding what it needs to support.
Where would operational AI make the most useful difference in your buildings, and what evidence would you want before allowing it to take action? Please listen and share your thoughts.

How much damage can a proven leadership playbook cause when it is applied to the wrong company? Experience can give executives confidence, but Sameer Kazi argues that confidence becomes dangerous when it replaces diagnosis.
In this episode of Tech Talks Daily, I welcome Sameer Kazi, CEO of the Pantheon Platform, back to the show for a conversation about copy-and-paste management, first-principles thinking, AI adoption, and the value of listening before making changes. Pantheon supports major websites and provides DevOps tools for agencies and enterprise web teams, placing Sameer close to the changing relationship between SaaS, web development, and agentic website creation.
Sameer describes a familiar mistake in technology companies. A new executive arrives with a formula that worked elsewhere, hires people from a previous team, and assumes the same inputs will produce the same growth. In the early SaaS era, for example, a company might have treated its sales efficiency ratio as a direct signal to hire another quota-bearing sales representative.
 Product-led growth, changing buying behavior, and different forms of product market fit have weakened that assumption. Adding salespeople does not automatically create demand.
His alternative begins with product market fit and the way buyers discover, evaluate, and purchase a product. From there, leaders can study the mechanics across marketing, sales, customer success, support, and product development.
Sameer argues that rapidly growing AI businesses do not come with a settled operating manual, so executives need curiosity and evidence instead of a formula copied from the past.
Customer feedback provides one source of that evidence. Pantheon runs a public Slack channel where customers and partners speak directly with the company. Sameer says those conversations can reveal customer experience problems and, in some cases, signal a platform slowdown before observability tools detect it.
 A small piece of feedback may not represent every customer, but it can give an experienced leader a reason to investigate immediately.
We also discuss AI return on investment and the growing cost of adding token consumption to an organization's existing workforce and infrastructure. Sameer does not claim to have one universal metric. Instead, he recommends looking at customer reactions to AI across sales, support, and internal processes. If AI makes a process faster for the company but worse for the buyer, customer evidence should reveal the problem.
The conversation then turns to data ownership. Sameer compares the hesitation companies once felt about moving data into the cloud with the speed at which some now provide business data to frontier AI labs. He expects small language models and open-weight models to give companies additional choices, including the option to run systems on their own hardware and isolate proprietary information where appropriate.
One of the strongest leadership examples comes from Sameer's arrival at Pantheon. He promised to speak with every employee and spent four months holding small roundtables. The format began with introductions and favorite movies before moving to a direct invitation: tell me what works, what needs attention, and what should be addressed first.
Sameer describes the result as a treasure trove of information from people closest to customers, prospects, products, and daily operations.
That approach also challenged the lazy assumption that long-serving employees represent outdated thinking. Sameer found experienced practitioners who had built agencies, developed large fleets of websites, and worked directly with customers.
Recognizing that knowledge can strengthen commitment, while dismissing it can leave employees disconnected and encourage quiet quitting.
Can leaders keep the principles that made them successful while treating every familiar method as a hypothesis to be tested? Listen to the episode and share how your organization balances executive experience with customer evidence and employee knowledge.

What matters most when you land in another country and your phone has no data? The cheapest plan may have looked like the obvious choice before departure, but priorities change quickly when you need a map, a translator, a ride to the hotel, or a way to tell your family you arrived safely.
In this episode of Tech Talks Daily, I speak with Alfonso Mata Villa, Head of Strategy at Holafly, about the growth of travel eSIMs and why they have moved from a specialist product to a far easier alternative to physical SIM cards and traditional roaming.
Alfonso explains that modern smartphones now make it possible to keep a normal number active while adding a separate data connection for an international trip. The result is a product that feels less like replacing a phone service and more like adding connectivity for a destination.
We talk through the practical experience for someone using an eSIM for the first time, including installation, activation, turning off the home data connection, and avoiding an unexpected roaming bill. Alfonso also describes Holafly's Always On benefit, which the company says gives customers one gigabyte of data each month so they can access basic services after arrival before buying another plan.
The apparent simplicity hides a demanding operating model. Holafly works across over 200 markets, where network quality, device behavior, carrier restrictions, hardware differences, and local regulation can all vary.
Alfonso explains why providers need strong operator relationships, redundancy, and the ability to move traffic when coverage becomes unreliable. His argument is that travelers should never have to see the complexity required to make a connection work.
That raises a useful question for anyone comparing travel eSIM providers. Price and data allowance matter, but what happens after the purchase? We discuss network reliability, data routing, latency, access to local services, privacy, and the speed of customer support when an installation or connection fails. Alfonso says Holafly treats multilingual support, unlimited data, transparent pricing, and reliable connectivity as parts of the product rather than extras.
The conversation also looks at the changing relationship between eSIM companies and mobile operators. Travel eSIMs compete with traditional roaming, but they still depend on operator networks. Alfonso sees an increasingly connected model in which operators supply infrastructure while global providers package connectivity for travelers and distribute it through airlines, travel agencies, hotels, online travel platforms, and financial services.
There is also a risk of leaving some travelers behind. Older phones may lack eSIM support, while carrier-locked devices and regional differences can create additional barriers. Alfonso argues that progress should be measured by whether the technology becomes simple enough for almost any traveler to use, rather than by technical sophistication alone.
If mobile connectivity can become another digital part of planning a trip, will travel eSIMs finally retire the anxiety and surprise costs associated with international roaming? Listen to the episode and share your experiences with eSIMs, roaming charges, and staying connected abroad.

Could your board explain where the organization's most valuable data resides, who can control it, and how quickly it could be recovered
In this episode of Tech Talks Daily, I speak with Adam Gale, CTO for Cybersecurity and Artificial Intelligence at NetApp, about why digital sovereignty is moving from compliance teams into boardroom discussions.
Adam argues that data has measurable business value, so decisions about its location, ownership, protection, and recoverability should be treated with the same seriousness as other financial risks.
We discuss how the US CLOUD Act, Europe's sovereignty agenda, and wider geopolitical tensions are changing cloud decisions. Adam explains that sovereignty extends beyond physical data location.
Hardware supply chains, software development, labor, access, operational control, and recovery all influence the level of sovereignty an organization may require. His advice is to treat sovereignty as a scale rather than impose the same controls on every workload.
The conversation also turns to sovereign AI. Adam describes why businesses and governments want greater control over training data, intellectual property, model activity, and audit records. He explains how poisoned data can produce plausible but unsafe outputs, and why controlled AI environments, traceable logs, and immutable records matter when systems begin making consequential decisions.
We then connect data visibility with business value. Adam shares how uncertainty over data location can affect a company acquisition and explains why insurers increasingly ask organizations to prove how information is protected and recovered.
He also describes the growing role of behavior analytics, automated responses, immutable storage, and storage-level ransomware protection in limiting damage and restoring trusted data.
If digital sovereignty begins with responsibility, control, and security, who owns those decisions in your organization today?
Listen to the conversation and share your thoughts with me.

Why do promising AI pilots struggle when they become services that real customers depend on?
In this episode of Tech Talks Daily, I'm joined by David Hughes, Chief Technology Officer at Stelia, to talk about the engineering decisions behind enterprise AI deployment. Dave's responsibilities cover networking, cloud infrastructure, and customer-facing products, giving him a view of what happens when an application meets the physical systems expected to support it.
We begin with a question that can get lost in the excitement around a successful demonstration. What problem was the system designed to solve, and what happens when the number of users changes? Dave describes reviewing a proof of concept that had worked for one external customer, only to identify a messaging component he believed would become a bottleneck under heavier demand. His lesson is to understand the intended workload before treating a working prototype as a production service.
The discussion also offers a balanced view of cloud computing. Dave praises elastic resources and programmatic control, while arguing that demanding AI workloads require teams to understand how storage, networking, and compute interact. A fast network cannot compensate for storage that cannot feed it. His steamship analogy makes the point familiar: the engine needs a steady supply of fuel if it is going to maintain its speed.
We talk about lessons from high performance computing, Dave's experience at Genesis Cloud, and the practical constraints of finding data center space and power. He explains why location and available capacity can influence architecture before a team even starts comparing GPUs.
For business leaders, the conversation becomes especially useful when we turn to measurement. Dave describes assessing internal model services through their effect on spending and judging customer projects by their output. His hotel occupancy analogy raises a question for anyone approving an infrastructure budget: how much of the asset's capacity will actually be used?
There is also a tension between engineering discipline and experimentation. Dave describes starting an internal inference service with existing servers and GPUs, then expanding it as demand grew. Proving that people wanted the service helped establish a case for a fuller investment. The lesson is to distinguish a useful experiment from evidence that a system is ready for wider demand.
We close with the Stelia newsroom and its engineer-written technical content. The supplied guest notes also introduce Stelia AI OS, described by the company as a full-stack operating system for enterprise AI. The interview focuses on deployment principles rather than a detailed assessment of that platform.
Where does your organization encounter the biggest obstacle when moving AI into production, and what evidence helps you decide where to invest next? Please share your thoughts.