
Hosted by Neil C. Hughes · EN

Could the disaster recovery plan designed to protect your company make a ransomware incident even worse? In this episode, I speak with Darren Thomson, Vice President and Chief Technology Officer for EMEA at Commvault, about Resilience Operations, commonly known as ResOps, and why cyber recovery now requires security, infrastructure, identity and data teams to work from one coordinated plan. Darren argues that many companies are accepting a difficult reality. Even with considerable investment in prevention and detection, a breach may eventually succeed. That does not make cybersecurity controls any less necessary, but it means recovery can no longer be treated as a secondary activity managed by another department. The problem is that security operations and infrastructure teams have traditionally worked toward different objectives. Security specialists concentrate on identifying and stopping threats. Infrastructure teams protect data, maintain backups and restore systems after outages. During a cyberattack, a successful recovery requires both sets of expertise. A backup administrator may be able to restore data quickly, but a forensic specialist must establish whether that data is clean. Without that confirmation, the company risks restoring malware and restarting the incident. Darren explains why a conventional disaster recovery plan may be particularly dangerous during ransomware. These plans were commonly designed for physical failures such as a lost data center. Data would be copied from one location to another so operations could continue. If the source data is infected, however, fast replication can carry the malware into the recovery environment. This is where ResOps enters the discussion. Darren describes it as an operating model rather than a product. It combines established practices from security and infrastructure management into a continuous program for testing, learning and improving recovery. Individual technology projects may come from the program, but resilience itself never reaches a final completion date. AI adds pressure on both sides. Criminals can use it to create faster and more effective attacks, while defenders can use machine learning to inspect large volumes of information, detect patterns and identify the newest clean recovery point. Companies must also protect AI systems as they would any other business application, including the models, data repositories and identities connected with them. Darren offers one practical starting point for CIOs and CISOs: Mean Time to Clean Recovery, or MTCR. This measures how long it takes to restore an application and its data with evidence that both are free from compromise. Before measuring MTCR, leaders must define their minimum viable company. These are the systems and services the business cannot operate without. Once that list exists, teams can test how long a verified clean recovery would take and replace assumptions with evidence. The initial answer may be uncomfortable. Teams may know how to restore an application without knowing whether the backup is clean. Security may know how to inspect the system but lack an established workflow with the recovery team. Darren sees those gaps as the starting point for a useful ResOps program because they provide everyone with a shared problem and a measurable objective. If your most important systems disappeared today, how long would it take to bring the minimum viable company back using verified clean data? Listen to the episode and share your answer with me.

Why can we track a meal traveling across town almost minute by minute, yet an international parcel can seemingly disappear between checkout and delivery? In this episode, I speak with Dieter Van Putte from Crossborder Global, a division of Bnode that provides global commerce and logistics services. Dieter oversees technology and operations across Landmark Global and Apple Express, giving him a close view of what happens when retailers attempt to sell and deliver products across international markets. Dieter explains why cross border delivery remains so difficult to track despite years of investment in supply chain technology. A domestic shipment may involve one main carrier, but an international order can pass between warehouses, road carriers, airports, airlines, customs authorities and final-mile delivery companies. Each participant may record events differently, operate at a different level of technical maturity or provide information at a different speed. We discuss why the customer rarely sees this complexity. They simply expect to know when their order will arrive, what duties and taxes they must pay, plus what will happen if the product needs to be returned. When retailers cannot provide those answers, the problem quickly becomes one of trust rather than logistics alone. Dieter also describes the less visible cost of manual reconciliation. Teams can spend hours checking carrier websites, comparing rates, reviewing spreadsheets, correcting customs information and translating inconsistent tracking events. Mistakes create further work through delayed parcels, billing disputes, customer inquiries and complaints. The direct labor cost matters, but the effect on repeat purchases and customer reviews may prove even more expensive. Our conversation then turns to the role of automation and AI. Dieter explains how technology can support product classification, customs documentation, landed-cost calculations and exception handling. We also examine logistics control towers, which combine data from multiple parties to provide an end-to-end view of an order. With enough reliable information, these systems can detect patterns, predict delays and recommend or initiate corrective action before the customer is affected. There is plenty of promise here, but good software cannot remove every customs rule, carrier handoff or data-quality problem. Retailers still need the right partners, accurate product information and a clear understanding of the promise they are making at checkout. Could better use of data finally make international delivery feel as dependable as domestic shipping, and what would need to change first? Listen to the conversation and share your thoughts with me.

Do you need to understand code before you can build a technology company or lead a team of developers? Five years after our previous conversation, I welcome Sophia Matveeva back to the podcast. Sophia is the founder of Tech for Non-Techies, where she helps founders and business professionals understand how technology products are created, tested, managed and turned into commercial ventures. A great deal has changed since we last spoke. Generative AI tools can now turn a written description into a working prototype within hours. For someone who has spent years believing a lack of coding experience disqualified them from building a technology business, that removes a significant barrier. Sophia believes this is the best time yet to be a non-technical founder, although her reasoning goes beyond AI-assisted coding. Research into billion-dollar technology companies shows that non-technical founders now make up a much larger share of founding teams than they did a decade ago. Many of these businesses sell technology to other companies, where commercial knowledge, customer relationships and an understanding of industry problems matter enormously. We discuss where AI belongs in the founder journey. Sophia recommends using tools such as Lovable or Replit to create a simple test product, show it to potential customers and learn whether people would use or pay for the idea. This allows founders to test their assumptions before committing substantial money to development. The boundary appears when that prototype becomes a real product. Once software stores customer information, processes payments or supports a commercial service, security and technical architecture cannot be treated as optional details. Sophia argues that professional developers are still needed to inspect the code, prepare the product for production and address problems a non-technical founder may not know exist. Her point is simple. AI can help a founder reach the testing stage sooner and at a lower cost. It cannot tell someone with no engineering experience whether the generated code is safe, maintainable or ready to support paying customers. Sophia also shares what she learned from managing her first development team. After raising investment, she attempted to compensate for her technical insecurity by taking a coding course and becoming involved in work she did not fully understand. The result was micromanagement, constant interruptions and frustrated developers. A better approach begins with business priorities. Founders should explain what customers want, ask developers about effort and tradeoffs, agree on what will be delivered during the next work cycle, then give the team the space required to complete it. They should also allow time for technical debt, the less visible maintenance work that prevents hurried development from creating larger problems later. We finish with advice for any business leader who wants greater technology fluency. Sophia recommends joining product meetings, contributing customer knowledge and building relationships with technical colleagues who want to understand the commercial side of the company. Neither side needs to become the other. They need enough shared language to make better decisions together. If AI has removed the cost of testing many technology ideas, what is stopping you from finding out whether yours could work? Listen to the episode, try Sophia's exercise and share your experience with me.

What happens when an AI agent begins influencing business decisions without fully understanding the systems, processes and dependencies behind them? In this episode, I speak with Bert van der Zwan, CEO of Bizzdesign, about the gap between enterprise AI expectations and the results many companies are seeing in practice. Bert has spent more than 25 years in software and SaaS leadership, including executive roles at Webex, Bynder, Twinfield and Unit4. Bert offers a candid assessment of the current AI market. He believes AI will have a lasting effect on businesses and society, but argues that expectations for near-term financial returns have become inflated. Many companies are spending money on tools and experimentation without reducing costs, consolidating software or producing new revenue. That does not mean experimentation is a mistake. Bert sees it as a necessary stage. The harder question is how companies move from a growing collection of pilots to AI capabilities that can operate dependably inside the business. One barrier is fragmented organizational context. Large enterprises have often grown through a combination of internal expansion and acquisitions, leaving behind disconnected applications, inconsistent data definitions and processes that cross several departments. An AI system working with only part of that picture may make a fast decision, but that does not make it a good decision. Bert argues that AI needs an authoritative view of how the enterprise works. Systems, processes, ownership, dependencies, approval status and policy restrictions must be visible and consistently defined. Without that shared context, AI may reproduce existing silos or make them worse. We also discuss the risks boards and technology leaders should consider as AI agents become involved in operational decisions. These include unreliable data, unclear accountability, legal exposure, weak governance and an incomplete view of the process being changed. Human oversight remains necessary, particularly when an automated decision could affect customers, employees or major investments. Bert then introduces the idea of "bespoke from the cloud." Traditional SaaS products were built around largely standardized interfaces and workflows. AI-assisted development could make software far easier to personalize around individual customers and use cases. This may give users greater control, but it could also challenge long-term software contracts and the economics that have supported the SaaS market. For leaders trying to connect AI spending with business results, Bert recommends beginning with visibility and a clearly defined outcome. Every initiative should be judged by whether it reduces costs, increases revenue or shortens the time required to deliver value. If AI depends on understanding how a company actually works, have businesses invested enough in creating that shared understanding before adding agents to their operations? Listen to the episode and share your thoughts with me.

Can you still trust an incoming phone call when AI can imitate a familiar voice, personalize the conversation and target information specifically to you? In this episode, I speak with Alex Quilici, CEO of YouMail, about how artificial intelligence is changing phone fraud and why the personal devices carried by employees are becoming part of the corporate attack surface. Alex explains how YouMail uses data from its consumer call-protection service to identify scam behavior, understand the type of fraud taking place and connect those patterns with the phone numbers involved. Advances in large language models have improved this analysis, but the same technology is also helping criminals build far more convincing campaigns. Generic robocalls are being replaced by personalized conversations designed to extract information, impersonate trusted people and manipulate victims. Fraudsters can use AI throughout the attack chain, from identifying targets and analyzing stolen data to generating dialogue and adapting an approach during the call. Alex argues that attackers have adopted these capabilities faster than many defenders expected because successful fraud produces an immediate financial return. The conversation also examines why voice biometrics can no longer be treated as sufficient proof of identity. As voice-cloning tools improve, companies may need to combine multiple forms of authentication and move sensitive communications into trusted applications. A call received through a banking app, for example, could give the customer greater confidence that the caller really represents their bank. For businesses, the risk extends beyond company-managed technology. Attackers can identify where someone works, learn about their role and contact them through a personal phone that may sit outside corporate monitoring. An employee's private number can therefore provide another route into the business through impersonation and social engineering. Alex also makes a persuasive case for collecting less personal data. Personalization can improve a service, but every additional piece of information becomes something an attacker might obtain during a breach. His advice is to identify the minimum information needed to deliver the intended experience rather than gathering data simply because it may prove useful later. Despite the seriousness of the threat, Alex offers evidence that coordinated action can produce results. He has seen brand-impersonation campaigns reduced from tens of millions of calls each month to around 100,000 through monitoring, disruption and cooperation between businesses and telecommunications providers. If AI is making fraudulent calls harder to recognize, should businesses stop treating the telephone network as a trusted communication channel by default? Listen to the episode and share your thoughts with me.

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.

What if the biggest barrier to better customer service isn't how quickly employees work, but how much time they lose coordinating with everyone else? In this episode of Tech Talks Daily, I speak with Kevin Yang, Head of AI at Front, about why customer conversations are becoming a valuable source of business intelligence, how AI can improve work across entire teams rather than simply making individuals faster, and the hidden coordination costs affecting customer operations. Kevin brings a unique perspective to the conversation. Before joining Front following its acquisition of his AI voice-of-customer company, Syllable, he spent 15 years as an entrepreneur. While building an office food delivery business, he experienced firsthand how customer conversations could reveal problems that traditional surveys and dashboards failed to identify. By analyzing customer feedback at scale, his team could connect specific issues directly to retention, account growth, and referrals. Today, AI makes it possible for companies to analyze enormous volumes of customer conversations and turn unstructured feedback into intelligence that can inform decisions across product development, sales, marketing, and customer success. Kevin shares how Front analyzes conversations to understand why deals are lost, why customers leave, and which topics are associated with higher sales conversion rates. The result is a feedback loop that helps companies direct product investment toward problems customers genuinely care about while giving sales and marketing teams a clearer understanding of the conversations that influence buying decisions. But the episode also challenges the assumption that giving every employee an AI assistant will transform productivity. Front's Coordination Tax research found that teams can spend almost three hours coordinating work for every hour spent solving customer problems. When a single customer request requires input from sales, finance, support, operations, or external systems, employees can lose time to emails, Slack messages, meetings, handoffs, and information searches. Kevin explains why making one person faster does little to solve this problem if the rest of the workflow remains fragmented. The bigger opportunity is to use AI across end-to-end processes, automatically handling research and analysis while allowing people to concentrate on work requiring judgment, empathy, relationships, and human decision-making. We also discuss the growing use of AI agents in customer operations and why governance becomes harder as companies move from experimenting with one agent to managing many. Kevin outlines the need to measure whether agents follow processes correctly, understand customer satisfaction, identify where failures occur, and continuously improve the knowledge and guidance available to AI systems. For business and technology leaders considering where to apply AI, Kevin offers a practical starting point. Map the work your teams perform into three categories: tasks AI can automate, tasks AI can support with human review, and tasks that should remain human. This helps companies focus investment where AI performs well rather than forcing automation into customer interactions that depend on empathy, context, and relationships. For anyone responsible for customer experience, AI strategy, operations, or digital transformation, this conversation provides practical ideas for turning customer conversations into business intelligence, reducing coordination friction, designing better workflows, and introducing AI agents with greater visibility and oversight. The opportunity is not simply to make individuals work faster. It is to redesign how work moves across the organization so employees spend less time coordinating and more time solving the problems that matter to customers.

What happens when your next customer is represented by an AI agent that can research products, compare prices, evaluate suppliers, negotiate terms, and make purchasing decisions? In this episode of Tech Talks Daily, I speak with Ian Kahn, Partner and Customer and Commercial Excellence Platform Leader at PwC, about the rise of the Intelligent Customer Edge and why companies need to rethink how they sell, market, price, serve customers, and compete as artificial intelligence changes the buying process. Much of the enterprise AI conversation has focused on helping employees become more productive. Ian argues that this overlooks a much bigger change already taking place. Customers are using AI to research products, compare alternatives, evaluate pricing, and make decisions. In some consumer and business markets, AI agents are already being given permission to make routine purchases. Companies are no longer selling only to people. They increasingly need to serve customers whose AI agents expect accurate product information, transparent pricing, availability, service history, and performance data that can be discovered, verified, and understood by machines. This creates a serious problem for companies operating with fragmented front offices. Marketing, sales, pricing, commerce, and customer service have traditionally operated as separate functions, each with its own technology, data, processes, incentives, and performance measures. Customers do not experience companies through those internal structures. They expect consistent information and relevant experiences across the entire relationship. Ian explains why adding AI to each department independently will not solve this problem. Companies risk making existing processes faster without improving the customer experience or business performance. Instead, he argues that leaders need to reconsider the operating model behind the entire customer journey. The Intelligent Customer Edge is PwC's approach to bringing these commercial functions together into a connected system centered on the customer. Powered by proprietary company data and AI, the system can continuously learn from customer interactions, support real-time decisions, and help companies respond to changing customer needs. We also discuss the idea of the commercial brain and why proprietary data could become one of the most valuable competitive advantages available to companies adopting AI. Most businesses already possess customer records, transaction histories, operational information, market signals, service interactions, and other data their competitors cannot access. Yet much of that information remains fragmented across systems and departments. Ian explains how connecting these sources can create an intelligence layer that informs pricing decisions, marketing activity, sales opportunities, service interactions, and the moments that matter throughout the customer relationship. For CEOs, chief customer officers, marketing leaders, sales executives, CIOs, and technology teams, the conversation offers an important lesson about AI transformation. The companies achieving meaningful results are not starting with the technology. They begin with customer outcomes and redesign the work, decisions, workflows, and operating models required to achieve them. Human judgment remains an important part of that model. AI can process large amounts of information, identify patterns, provide recommendations, and handle routine tasks consistently. People continue to bring judgment, creativity, empathy, relationship-building, and strategic decision-making to customer interactions where trust and context matter. Ian argues that the goal is not to choose between people and AI. Companies need to design customer systems that use the strengths of both, determining where automation can improve speed and consistency and where people can create greater customer and commercial value. Trust, governance, explainability, and accountability also become more important as AI agents are given greater authority. Rather than treating guardrails as barriers to adoption, Ian explains why companies should design controls into AI-enabled customer processes from the beginning. The conversation also examines the cost of waiting. Customers are already adopting AI, and businesses that continue relying on fragmented front-office operations risk falling behind competitors capable of responding faster, providing better information, and creating more relevant customer experiences. Ian offers practical advice for companies deciding where to begin. Start with the customer journey. Understand how customer behavior is changing, identify where friction exists, determine how AI could improve the experience, and establish clear measures for customer outcomes and business value before investing heavily in new technology. For business and technology leaders under pressure to deliver growth, improve margins, control costs, and demonstrate returns from AI investment, this conversation provides a practical framework for redesigning the front office, using proprietary data more effectively, preparing for AI agents as buyers, and creating better customer experiences. Your customers are already using AI. Some AI agents are already making purchasing decisions. The question for companies is whether their customer systems, data, commercial models, and operating structures are ready to compete for business when the buyer on the other side of the transaction is no longer always human.

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.

What if one of the biggest obstacles to digital transformation isn't your technology stack, but the agreements connecting it all together? Recorded live at Docusign Momentum in London, this episode continues my conversations from the show floor by looking at one of the most overlooked challenges facing modern organisations. Companies have spent years investing in CRM platforms, ERP systems, HR software and cloud infrastructure, yet many of the agreements linking those systems together still rely on manual processes, email chains and static documents. Joining me is Stéphane Barberet, President of EMEA at Docusign. Having spent more than three decades helping organisations across Europe use technology to improve the way they work, Stéphane shares why he believes agreements have become one of the biggest blind spots in enterprise transformation and how AI is beginning to change that. We discuss why organisations are starting to view agreements as business intelligence rather than administrative paperwork, where businesses unknowingly lose value after contracts have been signed, and why removing friction from everyday workflows often delivers greater returns than simply introducing another AI tool. Stéphane also explains why organisations across financial services, healthcare, manufacturing and many other industries are all asking the same questions about AI, how leaders should approach adoption without trying to automate everything at once, and why measurable business outcomes matter far more than launching ambitious AI programmes. Throughout our conversation, we also explore how executives should measure success, what separates organisations making genuine progress from those still experimenting, and why the future of AI may be one where the technology becomes almost invisible, quietly improving the way businesses operate every day. After spending the day speaking with customers, executives and attendees at Momentum, one message kept coming back to me. The organisations creating the greatest value from AI aren't chasing the latest trend. They're solving meaningful business problems, building trust and helping their people spend more time on work that truly matters. Where do you see the biggest opportunities to remove friction from the way your organisation works? I'd love to hear your thoughts after listening and continue the conversation.