
Advertise on podcast: Tech Transformed
Rating
5from
This podcast has
300 episodes
Language
EnglishPublisher
EM360TechExplicit
No
Date created
2019/03/01
Latest episode
2026/11/19
Average duration
27 min.
Release period
9 days
Description
Explore how tech is shaping the future of business and share best practices for implementing these innovations. With expert interviews, in-depth analysis, and practical advice, you'll stay ahead of the curve and make informed decisions for your enterprise. Join us to debunk myths, dive into the latest trends, and cut through the AI noise with “Tech Transformed.” Tune in and transform your understanding of technology and its potential.
Unlock Tech Transformed podcast Email contact info,
Listeners & Audience details
Email contact information
Direct podcast contact details

Listeners
Audience numbers & engagement insights

Audience details
Podcast Insights

Social media
Check Tech Transformed social media presence
Podcast episodes
Check latest episodes from Tech Transformed podcast
Why Do 1 in 4 AI Agents Run Without Monitoring?
2026/11/19
Picture an AI agent left running overnight. It edits a config file, closes a ticket and moves on to the next task. Every dashboard stays green. No human sees why it acted.
That is the reality for roughly one in four organisations with agents in production.
New Relic's 2026 Observability Forecast surveyed 2,575 IT and engineering leaders. It found that 93 per cent of enterprises are adopting AI agents, yet 24.6 per cent run them unmonitored.
"We're in a space race," Jemiah Sius, Vice President of Market Strategy and Developer Relations at New Relic, told BARC's Kevin Petrie on the Tech Transformed podcast. Teams are setting aside enterprise software discipline to move fast and prove return on investment, he said. It takes only one major outage, he warned, for leaders to slow down.
In this episode of Tech Transformed, Kevin Petrie, VP of Research at BARC, talks to Jemiah Sius, Vice President of Market Strategy and Developer Relations at New Relic, about how teams should inspect what AI agents actually do, and how to scale past human sign-off safely.
They discuss why teams ship agents first and instrument later, the Hugging Face sandbox breach, why there is no control without observability, how to earn trust in autonomy by limiting an agent's tools and MCP servers, and how pre-deployment testing can stop a bad agent release before it reaches production.
Key takeaways
93% of organisations adopt AI agents; 24.6% run them unmonitoredTeams ship agents first because leaders need to show a return Observability has traditionally watched, not blocked Limit an agent's tools and MCP servers before removing human approval An orchestrator plus narrow sub-agents adds determinism Pre-deployment testing can catch jailbreaks and PII leakage Sius expects EU rules to demand proof of agent behaviour
Chapters00:00 The Rise of AI Agents and Observability Challenges02:23 Understanding the Gap in Monitoring AI Agents05:51 The Risks of Shadow AI and Governance Issues08:49 Building Trust in Autonomous AI Agents12:56 The Role of Observability in Security and Governance18:17 Real-World Use Cases of Observability in Action22:41 Future Trends in AI Agent Observability25:45 Strategies for CISOs and CIOs to Enhance Observability
Research mentioned in this episode New Relic 2026 Observability Forecast: https://newrelic.com/sites/default/files/2026-09/new-relic-2026-observability-forecast-report.pdf
BARC: AI is in production at 97% of organisations: https://barc.com/news/ai-is-in-production-at-97-of-organizations-but-no-control/
Further reading:
The Hugging Face sandbox breach: https://techwireasia.com/2026/07/openai-agent-sandbox-breach-hugging-face/
Agent observability on the Claude Platform: https://claude.com/resources/articles/agent-observability-on-the-claude-platform
EU AI Act: what it means for UK businesses: https://em360tech.com/tech-articles/eu-ai-act-what-it-means-uk-businesses-and-how-stay-compliant
Shadow AI and shadow agents: https://em360tech.com/podcasts/shadow-ai-shadow-agents-whats-actually-changed-2026
How to monitor AI agents in production: https://em360tech.com/podcasts/how-do-you-monitor-ai-agents-production-without-breaking-incident-response
Learn more about New Relic: https://newrelic.com
Subscribe to Tech Transformed for weekly conversations on how technology is changing the way businesses run.
Website: https://em360tech.com
LinkedIn: https://www.linkedin.com/company/em360tech
𝕏 X: https://x.com/EM360Tech
#AIAgents #AgentObservability #AIGovernance #AgenticAI #NewRelic #AISecurity #ShadowAI #OpenTelemetry #TechTransformed #EM360Tech
AI agents, agent observability, AI observability, agentic AI, AI governance, AI security, shadow AI, sandbox escape, MCP, OpenTelemetry, EU AI Act, human in the loop, New Relic, BARC, Tech Transformed
Would You Invest in a Business That Ignores AI?
2026/11/16
92 per cent of directors used AI for board work in the past six months. 60 per cent of them sit on boards with no formal AI policy, according to the 2026 OnBoard Board Effectiveness Survey.
Take an investment firm, for example: a new deal lands in the investment lead's inbox, and minutes later a report arrives on why to be excited about it, with a first draft of the investment paper attached. All that is left to do is edit it.
In this episode of the Tech Transformed Podcast, Shubhangi Dua, Podcast Host and Producer at EM360Tech, speaks with Jamie Roberts, Managing Partner at YFM Partners. YFM Partners is an independent UK-based private equity and venture capital investment firm founded in 1982.
In particular, they address the key questions: how AI is impacting economic growth, what end-users need and what actions leaders should take to get ahead in the AI race.
They also cover what happens when AI changes an investment decision, why the editing step is where the risk sits, and what a UK board should have in place before AI gets near a vote.
“AI’s great for a first draft, for the first headline thinking, but then you need the human,” said Roberts.
Key takeawaysYFM has made about 4,000 investments in 44 years.Their internal AI model runs every new opportunity before a person sees it.About 15 of YFM’s 1,500 yearly opportunities become investments.Their internal AI model flagged a world-leading expert YFM had forgotten it knew.Editing an AI draft takes less thinking than writing one.Roberts uses AI for first drafts and validates everything.A management team that dismisses AI is hard to back.Roberts’ advice to CEOs: start with one small problem, like buying a car.
Chapters00:03 Intro: AI, boards and investors02:17 Confirmation bias and validating AI output04:26 Why YFM built an internal AI model08:52 AI slop and the audit trail17:44 Data protection before adoption21:38 The second brain at the investment committee
Read the full episode page: Watch more from the Tech Transformed Podcast: https://open.spotify.com/show/4rbDpZnuDKB53VKBZO2Nmf
Related reading from EM360Tech Why AI Is Forcing Organisations to Rethink Data Governance: https://em360tech.com/tech-articles/why-ai-forcing-organisations-rethink-data-governance
Digital Literacy Has Changed: When Not to Trust Tech: https://em360tech.com/tech-articles/digital-literacy-knowing-when-not-to-trust-technology
AI Search Governance: Enterprise Guide: https://em360tech.com/tech-articles/ai-search-governance-enterprise-guide
When to Use Human-in-the-Loop at Inference Time: https://em360tech.com/tech-articles/human-in-the-loop-decision-stage
More B2B tech podcasts: https://em360tech.com/podcasts
Follow EM360Tech on LinkedIn: https://uk.linkedin.com/company/em360
Follow EM360Tech on X: https://x.com/EM360Tech
Follow Private Equity: https://www.linkedin.com/company/yfm-equity-partners/home/
#TechTransformed #AI #PrivateEquity #UKBusiness #AIGovernance #EM360Tech
@yfmequitypartnersuk @enterprisemanagement360
What Is Physical AI and Why Will It Outgrow Cloud AI?
2026/11/10
Think of a robotic prototype that functioned well in March. Its robotic arm sorts through parcels flawlessly on the lab bench. It runs on a power-demanding compute module with a fan attached to the side. Finally, the production specifications are announced: battery power, a sealed case, a budget of 10 watts at most, and no connection to the cloud. Porting the application to hardware that fits those limits is the part of the roadmap nobody put on the slide.
This is where many physical AI projects stall between demo and shipment.
In the recent episode of the Tech Transformed podcast, host John Santaferraro, CEO and Head Research Analyst at Ferraro Consulting, sat down with Krishna Rangasayee, Founder and CEO of SiMa.ai, and Manuel López Roldán, GenAI Product Manager at SiMa.ai.
They break down everything you need to know about physical AI, why it’s taking machine intelligence out of the data centre and into the device itself, and explain the changes that SiMa.ai has made to its software so that AI agents and human engineers can build complex AI applications for that hardware in days and hours, making imagination the limit.
"You could run very high accuracy models entirely on device. You don't need the cloud at all,” the CEO of SiMa.ai states, setting the agenda for this episode.
Rangasayee says that we’re living through what is likely to be the largest upheaval of experiences. “AI is completely overhauling everything we know. We've gone through the social media revolution; now we're going through the cloud AI revolution.”
He believes that everything will be AI-enabled in some form or another, from the infrastructure enabling it in manufacturing, or in robotics, or in automotive, to everything we experience in our home, in our work, in medicine.
TakeawaysPhysical AI transfers reasoning from the cloud to the device itself.Rule-based control is replaced by systems aware of context & memory.Majority of physical AI customer applications require a sub-10 watt power envelope.Smaller & more optimised models operate on-chip with high accuracy.SiMa.ai carried out a complete rebuild of its industry-first agentic Palette Software Suite for use by agents.Palette lets developers explain and build systems in plain English.Current builds now take days or even hours, not "six to nine months".Humans retain the ideas & the decisions while the agents execute.Current use cases involve inspection, warehouse robots, drones & cars.
Chapters00:00 Introduction to the podcast and guests
00:28 The move beyond screen-based AI to physical AI
00:58 Defining physical AI and its significance
01:26 Why physical AI will be larger than cloud AI
02:12 The large upheaval AI is causing in various sectors
03:23 The shift from rule-based to reasoning machines
04:22 How models are getting smaller and more efficient
05:54 Enabling new capabilities through AI in physical devices
06:12 Current innovations in drones, robots, and autonomous vehicles
07:35 The role of agentic software and agent engineers
08:59 Democratisation and ease of developing physical AI systems
10:03 Unlocking new business models with physical AI
11:56 The future of AI development and agentic engineering
12:50 The impact of physical AI on industries like manufacturing and healthcare
21:38 How to lead and join the physical AI revolution
23:16 Closing remarks and next steps for listeners
Read the full article: https://em360tech.com/podcasts/what-physical-ai-outgrow-cloud-ai
Watch episode on YouTube: https://youtu.be/GE4sTiBk95A
SiMa.ai: https://sima.ai
EM360Tech: https://em360tech.com
Watch more from the Tech Transformed Podcast: https://www.youtube.com/playlist?list=PLXoSlBGE35NqhHbvDxnrEKw2bVoNBQ8U1
@SiMaTechnologiesInc @enterprisemanagement360
#PhysicalAI #AgenticAI #Robotics #TechTransformed #EM360Tech physical AI, SiMa.ai, agentic AI, AI agents, on-device AI, cloud AI, robotics, autonomous vehicles, drones, industrial automation, AI chips, technology, enterprise technology, Tech Transformed, EM360Tech
Why Is AI Governance the Real Bottleneck for Enterprise ROI?
2026/10/27
In the previous episode of the Tech Transformed podcast, EM360Tech's Shubhangi Dua sat down with David Hsu, founder and CEO of Retool, to tackle an uncomfortable truth for CIOs: vibe coding is already happening inside your organisation, whether you've sanctioned it or not.
From customer data turning up in AI-built apps on the public internet, to duplicate tools showing conflicting numbers, to AI bills climbing with no clear view of the return, David made the case that the answer isn't to ban AI-built software but to put guardrails around it. One central platform, with controlled access to trusted data, gives IT visibility, auditability, and control, because "with governance comes freedom." He finished with a bold prediction: by 2030, most of the work in your company, and the CIO's role, will become closer to a chief people officer for AI.
In this Big Data London special edition, host John Santaferraro picks up where that conversation left off with Ryan Wong, Head of Engineering at Retool. As AI moves from generating apps and content to agents that take real action, what does governing them actually take?
TakeawaysThe harness is the layer around the model that a business controls. AI harnesses context, identity, policy, action, and observability.Governance, not model quality, stops agents from emailing or touching sensitive data.Employees connecting Claude or ChatGPT to company data is hard to govern, so centralise access like an API gateway.Enforce data policy at the resource, not app by app, so employees can vibe code freely.Start agents with tight limits, then widen them. Log every action with the identity behind it.Vibe coding made building cheap. Deployment, access control, and observability are now the hard part.Retool says its platform has long handled those layers.Retool’s Assist tool struggled because it used a proprietary language. Building closer to what LLMs know works better.Models will change; the harness will last for years.
Chapters00:00 Introduction to AI harness and its significance
01:08 Defining the components of an AI harness: context, identity, policy, action, observability
05:12 The role of centralization in AI harness architecture
06:44 Governance challenges in multi-agent AI environments
17:48 Implementing a five-step governance process
22:20 Why focusing on the harness is key for AI progress
27:17 The importance of governance as AI agents gain authority
28:24 Final thoughts on controlling autonomous AI agents
Watch the previous episode with David Hsu, CEO of Retool: https://youtu.be/rvdl4Fy2taw?si=3nMzO...
Learn more about Retool: https://retool.com
More from the Tech Transformed podcast: https://youtube.com/playlist?list=PLX...
#AIHarness #AIGovernance #AgenticAI #EnterpriseAI #Retool #TechTransformed #BigDataLDN #RetoolAI #VibeCoding #AIAgents #AIContext #AutonomousAIAgents #AIROI
@Bigdataldn @Retool @enterprisemanagement360
How to Take AI Agents From Pilot to Production at Scale
2026/10/27
Plenty of organisations have an AI agent pilot that worked well in a demo. Far fewer have hundreds or thousands of agents running reliably in the real world, and that gap is where the hard work sits. AI agents are moving beyond experimentation, but taking them from promising pilots into production at scale is proving to be much more difficult. At the same time, AI is reshaping technical teams, changing traditional career paths and forcing organisations to rethink how technology creates value.
In this episode of Tech Transformed, host Christina Stathopoulos, founder of Dare to Data, explores what that transition looks like in practice. She is joined by Italo Vietro, VP of Engineering at Parloa, and Joshua Burks, Global Managed Services Head at Thoughtworks. They cover platform foundations, workforce change and agent management at scale. Their shared message is that powerful models are only part of the answer.
From Task Execution to OrchestrationBurks opens with a clear observation he has seen, and that is AI is shifting technical teams from task execution towards architectural orchestration. For decades, he says, engineering and operations teams have spent around 75 per cent of their time and capacity clearing tickets, sifting through alerts and writing boilerplate syntax. Agentic AI and automated coding tools are making that kind of syntax generation and routine triage a commodity. So the bottleneck has moved downstream. Burks describes a new kind of team built from T-shaped pods of engineers who manage autonomous agents, validate complex system behaviour and focus on continuous modernisation. The aim is to stop merely keeping the lights on.
The Rise of the Product-Minded ArchitectVietro sees the same pattern at Parloa and has a name for the people at the centre of it, which, as he calls them, product-minded architects. Instead of fixating on the solution itself, they spend more time in the problem space.
On the positive side, he thinks this is good news for engineering. Engineers generally want to solve problems, and understanding the problem has become more important than ever. The practical challenge is how to architect many agents together so they deliver the outcomes you expect. For Vietro, this also means ownership of something. People need to feel they can deliver the solutions they want, with the right outcomes, rather than simply carrying out tasks.
What Value Arbitrage Really MeansStathopoulos asks Burks to unpack a phrase he used early on, and his answer is one of the most useful parts of the conversation.
For roughly 40 years, he says, managed services has been a race to the bottom on a pricing model built entirely on labour arbitrage. Vendors bill for headcount, hours, utilisation and ticket throughput. The flaw is that the vendor profits from the complexity, manual effort and lingering technical debt in a client’s systems.
Technology arbitrage flips that. AI agents reduce the headcount needed to run operations or development. Burks believes the industry is now heading towards value arbitrage, where platform automation, predictable observability and agentic workflows take on the toil.
The question then changes from how many people or agents are on the account to what the organisation gets back. That means less technical debt, smaller ticket and development backlogs, and systems that are continuously modernised and ready for whatever demands come next, whether internal or external. Burks describes them as systems that never age.
Making The Jump From Pilot to ProductionStathopoulos points out the big difference between an agent working in a controlled playground and deploying hundreds or thousands of them in the real world. Vietro, whose company deploys agents at enormous scale, walks through what the transition involves. Let’s take a look at how he breaks it down:
Start with value, not just costMany organisations begin with the savings: fewer people, lower costs. Vietro encourages them to look at value instead. What better service will customers receive, and what problem is the agent solving?
Know how many agents you haveHis second priority is observability, and he offers a simple test. Can you say how many agents are running in your organisation right now? If you can, you probably have a reasonable setup. If you can’t, there’s room for improvement. He adds that the question is far from trivial to answer.
Stathopoulos says she suspects many companies don’t realise how many agents are running in the background and can’t count them. Vietro agrees that this matters well beyond performance. Observability also supports security, because you need to know what agents are doing, spot when something goes wrong and steer them back on course.
Test until you trustThe third priority is evaluations and simulations. Parloa runs millions of them across its agents to check that they do their tasks with a given level of confidence. Vietro’s benchmark is demanding. You test until you can give customers the same quality of service an agent provides as they would get from a human.
Once that confidence exists, he says, deploying agents across enterprises becomes easier, as does replacing different work streams within an organisation.
The platform foundations agents needIf pilots work in a playground, production needs infrastructure. Burks says the current moment closely echoes the early days of cloud. Back then, accounts were spun up all over the place, there were no guardrails, and everything went everywhere. Today he sees the same thing in what he calls the “agentic brawl”. His view is that enterprises need a centralised control plane. Thoughtworks has one called AgentWorks. He frames the foundations in three parts:
Observability and telemetry. Agents are only as good as the real-time context they receive. Unified observability across logs, metrics and traces lets AI triage agents correlate incidents and carry out root cause analysis, including for other agents across the enterprise.Governed skills. Rather than letting every team write its own isolated prompts, organisations should capture expert architectural knowledge in reusable, version-controlled skills applied across the business.Governance, safety and security. A robust control plane manages model execution costs, token budgets and access controls. It also acts as an LLM-as-a-judge within evaluation loops. Burks says you can’t scale agents unless security and compliance teams have full auditability over every agentic action. Without it, budgets spiral, and security loopholes appear, just as they did in the early cloud years.
Lessons Cloud Already Taught UsStathopoulos says all of this gives her a feeling of déjà vu, and both guests agree the cloud era holds real lessons. Burks was in the middle of those migrations. His biggest warning is the lift-and-shift trap. Enterprises moved monolithic, brittle applications straight to the cloud without refactoring them, and ended up with the same technical debt at a different cost point.
The AI version of that mistake is easy to make. If you plug generative AI into fragmented legacy architecture, chaotic data, messy ticketing queues and poor observability, you simply produce bad outcomes faster. His advice is to modernise the underlying operational engine as you adopt the technology.
Vietro says the same thing in different words: work on your fundamentals. AI will magnify whatever it’s given. Put it into an unstructured environment, and it amplifies the bad. Build solid foundations, and it amplifies the good, helping teams deliver better software.
He also stretches the comparison. Cloud was big, but he believes today’s AI shift is closer to the arrival of the web in the 2000s, and may be even bigger. His advice for navigating it is to stay sceptical and curious in equal measure, as the industry did back then.
What getting it right looks likeAfter a lot of talk about what can go wrong, the conversation ends on the positive side. For Vietro, successful scaling starts with model routing, which Parloa calls its model mix. Each incoming task goes to the model with the best track record for it, based on earlier simulations and evaluations. Success is a good conversation, whether by voice or chat, handled reliably and at lower cost.
He gives a vivid example. A German-language agent serving Germany would use standard Hochdeutsch. In Switzerland, the same task would land better if the agent spoke Swiss German, with the right accent and customer warmth. Stathopoulos recognises the same effect from living in Spain, where accents and...
What Is Self-Driving Production? The Future of AI SRE Explained
2026/10/07
Envision this: A ServiceNow ticket arrives at a big bank, and 50 customers can't log into their accounts. All the dashboards show a red indicator. About 60 to 100 people end up in a war-room meeting and remain there for about two hours. They discover the problem was a slow SQL query in a database ten hops down the stack, a system neither the login team nor their monitoring system had originally identified.
That is the situation which Anish Agarwal, CEO of Traversal, alludes to when explaining why incident response is becoming more difficult and why he believes the solution must be designed differently from the observability tools that most enterprises currently operate.
In the recent episode of the Tech Transformed podcast, Dan Twing, President and COO of Enterprise Management Associates (EMA), sat down with Agarwal, also a professor at Columbia University. They discuss how code laid out by artificial intelligence (AI) is affecting production incidents.
They also talk about what is needed to trace symptoms back to their causes within a portfolio of 5,000 applications, and how businesses decide when to switch from using AI suggestions to adopting autonomous remediation.
In terms of reliability, Agarwal says that the enterprise has to question whether the task was not just initiated but completed. However, it's also possible for a job to finish, yet the answer might not be the one you want.
Key Takeaways"Did it run?" no longer proves an AI-built system worked.Coding agents are trained on compile-and-run, so they can sideline the real goal.Same configuration, three runs, three different results.Engineers now write specs; agents write code, so code comprehension drops.Testing improves, but failures still happen at the seams between systems.Agents need to search far more data than dashboards were built for.Traversal's production world model maps entities, connections and live telemetry.Customers are using it to validate CMDBs, which was unplanned.Causal analysis separates upstream and downstream anomalies from spurious ones.Multiple paths converging on one cause builds confidence in a root cause.L4 cut a war room from 60–100 people to five to 10.Reported MTTR fell from two or three hours to 20–30 minutes.Coding agents now call Traversal's MCP to write production-aware code.Decide up front when to build in-house versus buy.
Chapters00:00 Introduction to Hybrid Cloud Challenges02:53 The Role of AI in Production Systems06:34 Complexity of Troubleshooting in AI Systems12:03 Causal Analysis in Production Environments18:03 Agentic Systems and Human Collaboration22:56 Framework for Agentic Readiness in Reliability27:03 Future of Self-Driving Production29:55 Practical Steps for Tech Leaders
Visit traversal.com.
agentic SRE, self-driving production, site reliability engineering, AI SRE, AI incident response, root cause analysis, causal AI, MTTR, mean time to resolution, production world model, CMDB, CMDB validation, ServiceNow, observability, AIOps, incident management, Traversal, Anish Agarwal, Dan Twing, Tech Transformed, EM360Tech, Enterprise Management 360, AI-generated code, coding agents, DevOps, enterprise IT
Vibe-Coding: Will Software Engineers Disappear by 2028?
2026/09/28
“Vibe coding is already present in your company,” according to David Hsu, CEO of Retool and governance is the only way to secure it.
Let's put this into context. Think of a Fortune 500 company’s CIO who has recently come across a vibe-coded application spotted on the public internet. This app was developed by an employee of the Fortune 500 company in question. The developer obtained a data dump from Salesforce pertaining to customers, then fed this data to an external AI tool not part of the company’s set of AI tools. The employee prompted the tool to host the resulting application on a public URL.
Since it was an external AI tool, a security review couldn’t be carried out, nor could the IT department view it. Without any internal visibility into a tool created by the employee, the actual customer data was live on the open web. It’s a scary situation, a breach of trust, so imagine the CIO’s wrath upon seeing it.
This is why, in the recent episode of the Tech Transformed podcast, host Shubhangi Dua, Podcast Producer and B2B Tech Journalist at EM360Tech, sat down for a conversation with David Hsu, CEO and Founder of Retool. They talk about the repercussions of vibe coding in addition to examining why most enterprises have no conception of how much of it is already taking place within their own enterprise.
The discussion then turns from the immediate issue of governance concerning uncontrolled AI app-building to Hsu's prediction that software engineering as a profession could vanish within two to three years.
“All the CIOs that I speak to are genuinely frightened about vibe coding, and even if you don't want to admit it, vibe coding is already present in your company,” he tells Dua. This is partly why Hsu founded Retool.
Retool secures vibe coding for enterprises. Hsu explains that Retool can be connected to a company’s Snowflake database, for instance or their Databricks data lake. “Users should be able to have access to particular tables only,” he says. Access controls are required at the group level.
“If you're in this particular Okta group, you can only access this table, and it's read-only. Whereas if you're in this other Okta group, you can actually write back to this other Salesforce over here." So one Okta group could be granted read-only access to a particular table, while another group might be given write access to a connected Salesforce instance. All applications that are built on top of that connection automatically inherit the same restrictions.
Once rules of such a nature are put in place, people could then be set free, explaining why he views governance as something that enables freedom rather than something that restricts.
TakeawaysVibe coding is already happening inside most enterprises, sanctioned or notA Fortune 500 CIO found a vibe-coded app exposed on the public internetOne customer's AI coding spend hit 30x their original budget estimateTwo employees independently built duplicate apps that returned different numbersHsu forecasts fully automated coding arriving by late 2027 or early 2028By 2030, Hsu estimates 90% of company work will be done by AI employeesThe CIO's future role: a "chief people officer" governing AI agents, not humans
Chapters00:00 The Rise of No-Code and Low-Code Development
04:52 Governance in the Age of Rapid Development
12:40 Centralisation and Control in Software Development
20:04 The Future of Software Engineering and AI
25:13 The Role of Humans in an AI-Driven World
vibe coding, AI governance, enterprise AI, CIO, AI agents, software engineering, Retool, David Hsu, enterprise software, AI security
The Rise of Autonomous Customer Experience: How Should Enterprise Leaders Prepare Today?
2026/09/28
AI is reshaping how businesses interact with customers, from handling routine enquiries to delivering more personalised and responsive experiences. As organisations automate more of the customer journey, however, customer support is increasingly being reconsidered not simply as a cost to reduce, but as an important part of how businesses build lasting relationships with their customers.
On this episode of Tech Transformed, host Christina Stathopoulos welcomed back Pranay Jain, CEO and co-founder of Enterprise Bot, to discuss what this shift means in practice. The conversation moves beyond the usual AI hype to consider how businesses can scale automation without losing meaningful human connection, while navigating growing regulatory expectations across Europe and the UK.
Jain has been building EnterpriseBot for almost a decade, since, as he puts it, "artificial intelligence was more artificial than intelligent." This vantage point shapes a conversation that's less about what AI can do and more about how enterprises should think about doing it.
Stop Treating AI as a Cost-Cutting ToolJain sees AI as an opportunity to rethink how customer service teams work, using automation to handle routine tasks while giving people more time to focus on interactions where human judgement and empathy matter most. Password resets, invoice lookups and basic status checks can be handled instantly by AI, allowing human agents to spend more time with customers during moments that require greater care, such as a major life event or an insurance claim following an accident.
He points to IKEA as a real-world example of this working. Rather than laying off staff as AI took over routine tasks, the company retrained employees to help customers plan their homes in a more personal, consultative way and saw sales increase as a result. It's a useful reframe that automation isn't about removing people from the equation; it's about repositioning them where their judgment and empathy are still needed.
Jain also flags a metric that trips up a lot of contact centres, which is average handling time. Teams are often rewarded for keeping calls short, but a one-minute call with a 40 per cent resolution rate is worse than a three-minute call that actually solves the problem. His recommendation is to automate the parts of a call that eat time without adding value - identity verification alone can consume up to a quarter of a call, so agents can spend the time they save on getting things resolved properly, not just quickly.
Why AI Needs GuardrailsGiven EnterpriseBot’s European roots, regulation naturally comes into the conversation. Jain explains how the EU AI Act, Spain’s new customer service rules and the UK’s FCA expectations are starting to shape what “autonomous” really means in practice. For example, businesses can track sentiment at a general level, but analysing an agent’s tone of voice or emotions crosses into much more sensitive territory. The same applies to financial transactions. An AI agent can’t simply be left to make those decisions on its own. There needs to be a clear workflow and defined controls around what it can and cannot do.
His concern is that a lot of the AI tooling on the market is built with a US-first lens and simply wasn't designed with these boundaries in mind. This creates real exposure for enterprises that adopt a slick-looking solution without checking if it can actually operate within EU or UK rules. Jain sees these regulatory changes as a positive step, particularly as AI becomes more embedded in customer interactions. "I actually think it's very important that you do have the right regulation, and there's a very good reason why these things are there."
This point extends into data sovereignty too. With geopolitical tension pushing some organisations to reconsider public cloud dependence, Jain suggests flexibility- the ability to run on-prem, in a private cloud, or across different regions depending on the customer; this is becoming one of the more undervalued priorities on a CIO's list.
Connected Customer Experience With AIThe conversation closes on something every customer feels but rarely thinks about, which is the disjointedness of switching between voice, chat, email, and messaging with the same company. Jain's push is for a single AI agent that carries context across every channel and every language. He uses his own background in Switzerland, a country with four national languages, to illustrate the scale of the problem. Without a unified system, a company could end up managing a dozen separate AI agents just to cover language and channel combinations.
His final advice focuses on what enterprise leaders can put into practice now. Start by actually listening to your customer data to figure out where automation adds value and where human time matters most. Then be honest about whether building AI in-house is really core to your business, or if it's a distraction from what you're actually good at. As he notes, insurance companies aren't in the business of building voice agents and trying to keep pace with shifting regulation on your own is an expensive, ongoing commitment few teams are set up for.
Jain’s perspective is his focus on making AI useful rather than simply more autonomous. His approach puts the customer experience first, while recognising that trust, human judgment and the right guardrails still matter. For businesses considering what comes next, that balance may be the difference between adopting AI for the sake of it and using it to create a better customer experience. If you would like to learn more, visit enterprisebot.ai or connect with Pranay Jain on LinkedIn.
TakeawaysThe shift from cost centre to strategic asset in customer support.How AI can augment human agents and improve emotional connection.Regulatory challenges and compliance in AI deployment.Data sovereignty and AI sovereignty considerations.Building connected, multi-channel customer experiences.The importance of governance and safeguards in AI systems.
Chapters00:00 Introduction to autonomous customer experience and guest Pranay Jain
01:55 Transforming customer support from a cost centre to a strategic asset
02:54 Using AI to handle mundane tasks and enhance human agent capabilities
04:53 Balancing automation with human connection in customer journeys
05:58 Analysing customer journeys to identify emotional impact areas
06:52 Automating verification and wrap-up to improve efficiency
07:55 Regulatory landscape: EU AI Act, UK FCA, and Spain's requirements
08:54 Compliance challenges and designing regulation-friendly AI solutions
10:53 Data sovereignty, data security, and flexible deployment models
13:09 Creating a seamless, multi-channel customer experience
14:09 Ensuring connected AI interactions across voice, chat, and email
15:10 The importance of multilingual AI agents for global support
23:09 Final advice for enterprise leaders: customer-centric, compliant, and scalable AI strategies
How Agentic Voice AI Is Changing the Customer Experience
2026/08/26
For years, voice has been the channel most enterprises have quietly dreaded. The reason stems from it being harder to automate than chat. It's also harder to scale across markets, and far less forgiving if the experience is clumsy. Yet according to Pranay Jain, CEO and Co-founder of Enterprise Bot, that reluctance is exactly why so many businesses are still losing customers to frustrating IVR menus while their competitors move ahead with something smarter.
In a recent episode of Tech Transformed, Jain sat down with Trisha Pillay to explore the changing role of voice AI in customer service. Together they unpacked the technological advances making it possible, right to the practical strategies businesses need to use it effectively.
Jain, who built Enterprise Bot alongside his wife and co-founder after a detour through real estate, explained where agentic voice AI is heading and why treating it as a bolt-on to existing digital channels is a mistake. He pointed out that voice was never really solved; businesses simply learned to live with its limitations. As conversational AI becomes better at understanding intent, maintaining context and taking action rather than reciting scripted responses, the calculus for enterprise AI deployment is now changing.
Why Voice Still Carries the BusinessThe figures Jain cites indicate the shift is already underway. In much of Europe, somewhere between 60 and 80 per cent of customer requests still arrive by phone, while chat accounts for a sliver of total contact centre volume in markets like Switzerland. This may surprise people who think digital channels have already taken over. They haven't, especially when customers have complex or urgent problems to be attended to.
Jain explains that customers choose their channel based on how important or difficult their issue is. A quick balance check or a password reset happens over chat or an app. But when something feels uncertain, urgent, or emotionally loaded, people still reach for the phone. They want to be heard, not routed through a flowchart. That's why a robotic voice bot can be more damaging than a mediocre chatbot. Customers often turn to voice when they want a more personal interaction, so a cold or scripted response can make them feel ignored and not valued rather than helped.
This is also where the case for treating voice, chat, and email as one connected system rather than separate builds becomes obvious. Jain described meeting a client running a twenty-person team just to maintain their AI stack while only ten people handled actual customer service. This was a sign that channel-by-channel and language-by-language builds spiral out of control fast. A single underlying AI that can operate consistently across languages and touchpoints isn't a nice-to-have, in his view; it's the only version of enterprise AI that scales without collapsing under its own maintenance burden.
Voice AI’s Real Value Jain says that the interesting thing about voice AI is not just that it sounds natural but what it can actually do. Most companies just use voice AI to answer questions. Jain says that about 80 per cent of customer calls are about transactions, not just information. Customers don't call just to ask questions; they call to get something done, like a refund or a change to their account.
Enterprise Bots work with Generali Switzerland to show the difference between answering questions and actually resolving issues. When the AI could complete transactions on its own, customer satisfaction went up. When the AI couldn't complete transactions, it was still helpful by directing customers to the right person, which saved time and improved accuracy
Scaling AI Starts With Governance
Jain warns that none of this works without taking compliance and data privacy seriously. Companies in services have to follow rules about where they can use generative AI. The EU has rules about what data can be processed and how, and some things, like sentiment tracking, are allowed in some places but not others. Adding in industry rules, the technical build is secondary to getting the governance right.
Language is another challenge. Building a system for the US market might mean supporting English and Spanish. Building for Switzerland means supporting four national languages, plus dialects and regional variants. Jain says that many companies fail because they can build a demo that works in one language but can't make it work in real-world conditions.
His advice for companies considering AI is to start with a pilot, involve IT and security from the beginning and make sure the technology is solving a real business problem. Jain says that successful AI adoption is not about using the advanced technology but about showing that it can deliver real value before scaling it up. If you would like to find out more about this, visit enterprisebot.ai or follow Pranay Jain on LinkedIn.
TakeawaysThe importance of voice AI in customer interactions.Multilingual and multi-channel AI support.Regulatory and data privacy challenges.Transactional vs informational AI use cases.Real-world deployment success stories.Technical considerations for scalable AI.Customer experience and emotional engagement.Future trends in voice AI technology.
Chapters00:00 Introduction to Voice AI and Its Growing Importance
02:57 Why Voice Remains a Key Customer Channel
04:46 The Evolution of Voice AI and Emotional Understanding
07:20 The Role of Voice in Multilingual Europe
09:22 From Answering Questions to Taking Action
11:01 ROI and Business Impact of Voice AI
12:14 Key Factors in Choosing AI Solutions
14:28 Real-World Customer Success with Generali Switzerland
18:04 Handling Multilingual and Dialectal Variations
21:00 Regulatory and Security Considerations
23:42 Common Mistakes and Best Practices in AI Governance
What's Behind Temporal's Unlikely Rise to Unicorn Status?
2026/08/17
The fact that OpenAI has quickly adopted Temporal, a rapidly expanding AI ecosystem, and has even entered into a partnership with Crystal Palace FC shows that its business strategy is to pursue community-first innovation.
For years, tech enterprises competed against each other on the grounds of innovative features. However, the competition has changed recently. Now the winners are those who build communities.
In the recent episode of the Tech Transformed podcast, host Christina Stathopoulos, Founder of Dare to Data, is joined by Melissa Herrera, Senior Developer Advocate at Temporal, and Les Jackson, Staff Developer Advocate, to discuss the pivotal role of the community in technology.
They further explore how Temporal's open-source philosophy fosters developer engagement, the impact of community feedback on product development, and the significance of partnerships, such as with OpenAI and Crystal Palace. The conversation emphasises the importance of authentic community relationships and the future direction of Temporal, highlighting the need for continuous integration and collaboration with developers.
TakeawaysCommunity is a central part of Temporal's growth.Temporal's philosophy is rooted in open-source software.In-person community interactions are invaluable for developers.Feedback from the community directly shapes product direction.OpenAI's adoption of Temporal led to significant scaling.Partnerships should focus on community engagement, not just transactions.Temporal's collaboration with Crystal Palace merges tech and sports communities.Investing in community fosters trust and collaboration.Continuous integration with developer tools is essential for success.Authentic community relationships drive technology innovation.
Chapters00:00 Introduction to Tech Transformed Podcast
02:45 The Importance of Community in Technology
05:13 Feedback from Developers: Shaping Product Direction
07:51 OpenAI's Adoption of Temporal: A Case Study
10:02 Unique Partnerships: Temporal and Crystal Palace
15:12 Looking Ahead: Future of Temporal and Community Engagement
19:38 Final Thoughts: Investing in Community
Temporal, Enterprise AI, Developer Communities, Developer Advocacy, Open Source, OpenAI, AI Agents, AI Infrastructure, Durable Execution, AI Orchestration, Enterprise Software, Developer Experience, AI Workflows, AI Adoption, Community Led Growth, Developer Led Growth, Temporal SDK, Software Engineering, AI Engineering, Enterprise Technology, Crystal Palace, Tech Transformed
Scaling AI Across the Enterprise: From Builders to Business Impact
2026/08/12
In this day and age, there is probably no meeting or conversation in the tech world that doesn't concentrate on how artificial intelligence (AI) can improve the work streams of organisations worldwide. There will definitely be a moment in almost every AI strategy meeting where someone says, "We need agents."
In this episode of Tech Transformed, Sara Maldon unpacks with host Christina Stathopoulos how she has heard this sentence countless times. As the head of AI and automation at Make, she's learned to treat that sentence as a starting point because most of the time, the business problem sitting underneath it doesn't actually need an agent at all.
This conversation is less about hype and more about when a workflow needs autonomy, and when a simple if-this-then-that rule is doing the job just fine. Maldon's answer comes from two and a half years of running AI transformation inside a company that was automating things long before "agentic" became a buzzword.
Where Agentic AI Fits on the Automation SpectrumOn the other end of the spectrum is agentic AI. Rather than following a fixed sequence of instructions, it gives an LLM a goal, the right tools, and enough context to decide for itself what needs to happen next. Maldon points to a simple example. A car-leasing company needed product images pulled automatically from manufacturers' websites. A traditional scraper did the job well enough until BMW redesigned its website. Overnight, the automation failed because the image had moved. "An agent doesn't care where the picture is on the page," she explains. "It just knows it needs to get the BMW photo."
This indicates that Agentic AI isn't valuable because it's more "intelligent"; it's beneficial because it can adapt when the environment changes instead of breaking down the moment something shifts. Even Make's own AI sales agent isn't fully autonomous. It's deployed across 60 sales representatives, but, as Maldon points out, it's "95 per cent deterministic." Most of the workflow still follows predefined rules. The agent steps in only when a judgment call is needed, deciding a conversation should be escalated, followed up by email, or moved into a Slack channel. The plumbing remains deterministic because the agent simply adds decision-making where it creates the most value.
Building With AIMaldon believes the people best equipped to build workflows are those who understand the business firsthand. Operations teams, customer success, marketing, and other business users see where processes slow down because they work with them every day.
She knows this because she has been through the same journey herself. Before leading AI and automation at Make, she trained as a lawyer, not a developer. Today, she describes herself as one of the company's most active builders.
For Maldon, technical expertise isn't the defining quality. Domain knowledge comes first, followed by an instinct for improving processes, a desire to solve problems for other people, and enough curiosity and persistence to keep experimenting until something works.
This philosophy shapes how Make develops automation internally. Employees rarely begin inside the automation platform itself. Instead, they sketch ideas in Claude, using it to think through the workflow and refine the logic. If an automation proves useful beyond one or two people, the AI team then helps turn that prototype into something production-ready using AI co-worker, Maia by Make. Starting from scratch is becoming the exception rather than the rule. The first draft already exists; the job is to refine, test, and scale it.
Scaling Automation Across the BusinessHere's the part leaders don't want to hear: the hard part isn't the AI. It's everything around it. Maldon points to Make's sales agent again, the one handling escalations, follow-ups, and CRM updates after every call. Building the agent itself took two days. Planning and mapping the deterministic pipeline around it took four weeks. Rolling it out to 60 people, with training, feedback loops, and adoption? Four months.
Patience, she believes, is the least-discussed skill in AI transformation and maybe the most necessary. Not because the technology is slow, but because people aren't robots; they need time to trust a new process before they'll actually use it.
The HR team's onboarding redesign makes the point without needing sales numbers to prove it (though the numbers help - a 10 per cent lift in AI adoption from something as small as a personalised pre-start video). Ninety-six per cent of Make's employees now run an AI agent they built themselves. Not because leadership mandated it, but the tools got low enough friction, and the culture rewarded people for trying. Maldon's advice to leaders stalling on where to start is to stop assessing tools and pick one. Run a hackathon or set aside an afternoon to experiment for a small section of your enterprise. The market moves faster than any evaluation process can keep up with anyway, so get a foot in the door, then figure out the rest as you go. If you would like to find out more, visit make.com or follow Sara Maldon on LinkedIn.
TakeawaysOrganisations should start small and iterate quickly with AI projects.Building a culture of builders and curiosity accelerates AI adoption.Patience and soft skills are crucial for scaling automation.Agentic AI allows for more flexible and resilient workflows.Empowering non-technical teams to build with AI democratises innovation.
Chapters00:00 Introduction to AI transformation and automation at Make
00:57 Meet Sara Maldon and her role at Make
01:59 Understanding the spectrum: deterministic vs agentic AI
02:52 The agentic spectrum and real-world examples
07:04 Building automation in the age of AI
09:54 The rise of builders: no-code and operational roles
12:02 Scaling automation across organisations
16:13 Customer success story
18:58 How Make uses AI internally to innovate
22:01 Advice for leaders starting with AI and automation
24:04 Conclusion and key takeaways from the episode
Why AI Transformation Is Really a People Problem
2026/08/12
Every enterprise leader has heard the numbers by now as billions poured into licences, seats and tokens, with productivity gains still trailing well behind the promise. On a recent episode of Tech Transformed, host Christina Stathopoulos sat down with Jay Richman, Chief Product and Technology Officer at Multiverse, to unpack why so many organisations remain stuck in what he calls "tinker mode" and what it actually takes to move past it.
Richman's view is shaped by a career spent at the sharp end of three separate technology shifts. A decade at Spotify saw him build out the company's advertising business and early subscription platform from scratch. Roughly four years at Amazon followed, working on agentic AI systems within the advertising division, effectively rebuilding the old-fashioned creative agency model using specialised generative media tools. Four months ago, he relocated from New York to London to join Multiverse, drawn by a mission he sees as almost the reverse of his previous work. Rather than using people to make machines smarter, the task now is training machines to make people smarter. That framing sits at the centre of this conversation.
The AI Adoption GapRichman suggests that the widely reported gap between AI spend and AI-driven output isn't really a technology failure; it's a human one. Tools sit unused, licences go unopened, and organisations struggle to move employees from curious onlookers to confident, habitual users. Multiverse's answer is what it calls the "adoption layer", which is a diagnostic approach that pinpoints where skill gaps actually sit across a workforce, builds tailored learning paths around them, then embeds coaching directly inside the tools people already use, whether that's Claude, Gemini or ChatGPT.
Crucially, Richman distinguishes between what he wryly terms "token maxing" and value creation. Blunt incentives, leaderboards, usage dashboards and mandates to switch from manual coding to AI-assisted development. All this can help people over that first hurdle, and he admits to having used some of these tactics himself. But the real measure of success has to be defined customer by customer, tied to a specific business outcome, not simply how many prompts someone fired off in a week. As he puts it, the value of any given AI initiative can only be judged against what that particular organisation set out to solve in the first place.
Human Skills AI Can't ReplaceOne of the most interesting parts of the discussion explores how generative and agentic AI are reshaping team structures. Richman describes a flattening of traditional boundaries: product managers writing code, designers contributing to technical documents, and engineers drafting strategy papers. Functions that were once tightly specialised, such as a dedicated user-research team and a standalone copywriting role, are increasingly being absorbed as skills within more generalist, multi-hatted employees. At the same time, he notes, the opposite is happening at the model layer, with AI agents becoming ever more specialised. The result, in his telling, is smaller teams working with far greater autonomy and considerably less coordination overhead than in years past.
Asked what he prioritises when hiring now, Richman is candid that mastery of a single discipline matters to him less than certain behavioural traits: curiosity, high agency, sound judgment. He shares an interview technique he relies on, asking candidates how they spent their time during the pandemic lockdowns, as a rough proxy for whether someone tends to seize initiative or simply wait for circumstances to dictate their next move.
Moving Fast Without Cutting CornersOn responsible deployment, Richman insists culture has to start at the top. Leaders, he argues, need to be visibly hands-on and honest about their own gaps in knowledge rather than issuing mandates from a distance. At Multiverse, that meant lifting caps on AI coding tools, resetting the expectation that new work should be AI-generated by default, and investing heavily in quality assurance and evaluation frameworks so that human reviewers still hold a meaningful checkpoint before anything reaches customers. He contrasts this with the slower, more cautious approach he sees at many other organisations — one he believes is not only less efficient but also less likely to stick once the initial push fades.
Measuring What Actually MattersTying this back to the earlier point about value over volume, Richman suggests the real test of an AI initiative is how closely it maps to a business's own stated objective, not adoption figures in isolation. That means starting with what a customer or team is actually trying to achieve, building learning around the specific gaps standing in the way, and only then judging success by whether the resulting behaviour change shows up in the metrics that organisation already cares about.
The conversation closes on a personal note, with Richman sharing the advice he'd give his own children as they weigh careers in a fast-shifting landscape: run towards disruption rather than away from it. Having entered the workforce at the tail end of the dot-com boom, he sees clear parallels with the present moment, a period, in his words, where nobody can credibly claim expertise, which makes it as good a time as any to jump in. For organisations still puzzling over why their AI investment hasn't translated into measurable returns, Richman's message is simple: the technology was never really the difficult part. If you would like to find out more, please visit multiverse.io or connect with Richman on LinkedIn.
TakeawaysSuccessful AI adoption hinges on people, not just technology.The AI adoption layer helps bridge the gap between investment and productivity.High agency and curiosity are key traits of successful AI practitioners.Leadership must lead by example and foster a culture of experimentation.Rapid technological change requires teams to be flexible and multi-skilled.
Chapters00:00 Introduction to AI transformation and people-centred approach
00:54 Jay Richman's background at Spotify, Amazon, and Multiverse
03:47 The challenge of AI adoption and pilot mode
07:04 The concept of the AI adoption layer and its purpose
12:54 Distinguishing token maxing from value maxing
16:03 Impact of generative AI on product and engineering teams
19:09 Building teams in the AI era: blurring roles and skills
21:49 Qualities and skills for future AI teams
25:49 Leading responsibly with AI and fostering a culture of experimentation
How Physical AI Is Rewiring Machines
2026/08/11
Artificial intelligence has spent the last several years getting smarter on screens, recommending what to watch, drafting what to write, answering what we ask. This type of progress is now spilling out into the physical world, where machines are starting to move, sense, and adapt on their own. In this episode of Tech Transformed, host John Santaferraro, Founder and Analyst at Ferraro Consulting, talks with Prith Banerjee, Senior Vice President of Innovation at Synopsys, about what happens when AI has to obey the laws of physics instead of just the patterns in a dataset.
Banerjee brings a rare vantage point to the conversation. Before Synopsys, he led HP Labs worldwide, served as group CTO at ABB and Schneider Electric, and ran engineering simulation software company ANSYS as CTO until its acquisition by Synopsys roughly a year ago - a deal that now anchors much of what he describes as Synopsys's "silicon to systems" strategy.
The Road to Physical AIBanerjee traces AI's progress through distinct phases he's tracked across his career. It started with analytics, which was the correlation engines behind a Netflix recommendation, or the placement and routing improvements Synopsys has long applied inside its own chip design tools. Generative AI came next, giving machines the ability to produce original language, images, and video from a prompt rather than just surface existing content. Agentic AI followed close behind, handing off entire tasks, drafting a slide deck, prepping a sales call to systems that act more like assistants than tools.
Physical AI is the phase Banerjee sees unfolding now, and it's a different kind of leap. Instead of learning from words or pixels, these systems learn from real physical measurements: pressure, temperature, stress, and strain. Training that kind of intelligence takes synthetic data generated across structural, fluid, and electromagnetic physics precisely the simulation capability ANSYS brought into Synopsys.
Teaching Robots to Learn Like HumansThe shift shows up clearly in how robots are built today. A decade ago, getting a robotic arm to pick up a bottle without crushing it meant writing enormous programs, sometimes 100,000 lines of code specifying exactly how each motor should move. Physical AI throws that playbook out. Banerjee compares it to teaching a child to ride a bike: nobody narrates which pedal to push. The child watches, tries, falls, and adjusts.
Robots now learn the same way, refining their behaviour through reward and penalty as they attempt a task thousands of times. Autonomous vehicles follow the identical pattern at far greater scale, learning from millions of hours of driving footage until they recognise, for instance, that a pedestrian stepping into the street means stop. Synopsys works with autonomous vehicle and robotics companies to generate the synthetic training data that makes this kind of learning possible without requiring endless real-world testing.
Engineering the Intelligent Systems of TomorrowThat intelligence has to run on something, and the conversation turns to what it takes to build the silicon underneath it. Chips that once held a few hundred thousand transistors now carry tens or hundreds of billions, some approaching trillions, stacked using advanced 3D and chiplet techniques. Designing them means balancing power, performance, and thermal limits simultaneously rather than simply over-engineering for safety margin, which Banerjee calls co-design.
Synopsys is tackling that complexity with what it calls agent engineers. AI systems introduced at its Converge conference that work alongside human chip designers on tasks like RTL design, test benches, and sign-off, effectively multiplying engineering capacity without multiplying headcount. The same pressure shows up at the edge, where trained AI models have to run inside a drone, car, or warehouse robot on a fraction of the power a data centre would use, with no room for cloud latency. Banerjee shares his perspective on why many AI projects struggle. He argues that the real challenge lies in balancing innovation with trust: robots operating alongside people raise questions of safety and collaboration, while autonomous systems connected to networks demand security, traceability, and clear explanations for the decisions they make.
His advice to engineering leaders is to treat this shift as organisation-wide rather than a single team's problem, from legal and marketing functions already using agentic tools to engineering teams rethinking how code gets written. The goal, as he puts it, isn't replacing people but making them capable of far more than they could manage alone. If you would find out more about this, visit Synopsys or follow Prith Banerjee on LinkedIn.
TakeawaysEvolution of AI from analytics to physical AI.Role of synthetic data in training physical AI.How robots learn through physical interactions.Complexity and innovation in chip design.Agentic AI and its applications in engineering.Challenges of edge AI in autonomous systems.Security, governance, and safety in physical AI.
Chapters00:00 Introduction to AI's Evolution and Physical AI
01:15 Prith Banerjee's Career Journey and Role at Synopsys
04:19 The Phases of AI: Analytics, Generative, and Agentic
07:55 What is Physical AI and How It Learns from the Physical World
09:23 Robotics and Autonomous Learning Through Physical AI
19:41 Impact of AI on Chip Design and Complex Systems
23:29 Design Challenges of Complex, AI-Driven Chips
26:57 Edge AI and Challenges in Autonomous Devices
28:09 Implications for Organisations and Future Investments
How AI Could Bring More Joy to the Workplace
2026/08/10
Most conversations about artificial intelligence eventually return to the same concerns: is it going to replace my job, disrupt, and create an uncertain future? But what if we are looking at AI through the wrong lens?
On the latest episode of Tech Transformed, host Trisha Pillay sits down with Kevin Surace, an author, AI expert and technology pioneer who has spent three decades working on technologies that helped lay the foundations for products such as Siri and Alexa. His perspective is very different from the usual debate. Rather than viewing AI primarily as a threat to human work, Surace sees it as a tool that can expand what people are capable of achieving.
This shift changes the conversation from what AI might replace to what it could make possible. The discussion explores how AI can help people work faster, tackle problems that were previously out of reach and spend more time on areas where human judgment, creativity and experience still matter. For Surace, the question is not whether AI will change the way we work. That change is already happening. The more important question is what we choose to do with the capabilities it puts in our hands.
Silicon Valley Author and AI ExpertSurace holds 95 patents and is often credited as the father of the AI assistant. His work goes back to General Magic, an early-1990s Apple spinout where his team built the first digital agents and a programming language called Telescript. That early assistant technology had millions of users well before anyone was talking about chatbots.
His upcoming book, The Joy Success Cycle, grew out of a question people kept asking him: Why does he seem to enjoy his work so much? The answer, he told Pillay, comes down to sequencing. Most people wait for success before they let themselves feel joy. Surace argues it works the other way. Joy has to come first, and success follows from it.
How AI Brings JoySurace's favourite example is presentations. He used to spend a full week getting slides right, not because the ideas took that long to develop, but because formatting, alignment, and design details ate up all his time. Now he outlines what he wants to say, hands it to an AI tool, and gets a polished deck back within the hour.
The lesson he draws from that isn't about speed for its own sake. It's about separating the parts of a job that actually bring satisfaction from the parts that never did. Moving a font two pixels to the left never gave anyone joy, he says. Delivering an idea to a room full of people can. AI, in his view, quietly removes the first category and leaves more room for the second.
AI and the Case for More JobsSurace pushed back hard on the idea that AI shrinks the job market. He pointed to every major shift he's lived through from the PC, email, the smartphone, and the internet. Each one triggered the same fear, and each one ended up creating more roles than it eliminated.
He sees the same pattern playing out with software development right now. Coders using AI tools are shipping features and fixing bugs far faster than before, and instead of trimming teams, many companies are hiring more developers to keep pace with the new demand their own speed has created. The job itself has changed. Writing code line by line matters less than guiding the output and checking it. But the need for people hasn't gone away.
Rethinking Workflows With AIOne point Surace kept returning to was how companies get AI wrong when they try to automate their existing process instead of questioning why that process exists in the first place. He used car insurance claims as an example. The old approach sends an inspector to look at damage, fills out paperwork, and routes it through several people before a check gets issued. An AI-first approach skips most of that. A customer photographs the damage, uploads it, and a payment can go out the same day. This kind of redesign, he argues, is where the real gains sit. Businesses that only bolt AI onto old workflows will see modest improvements. Businesses willing to rebuild the workflow from scratch stand to cut costs dramatically and outpace competitors who don't.
Cybersecurity in the Age of AIThe conversation also turned to security, an area where Surace runs a company building biometric authentication devices. He explained that attackers rarely bother breaking into networks directly anymore, since most data sits encrypted. Instead, they use AI to generate convincing phishing emails and fake login pages designed to trick people into handing over multi-factor authentication codes. Surace believes fingerprint-based verification is where things are headed, since voices and faces can now be convincingly faked, but a fingerprint can't. He expects verified-identity badges to become common online within the next few years, giving people a way to confirm they're actually talking to the person they think they are.
What Leaders Should Do NowWhen asked what businesses should do now, Surace's advice was simple: get every employee using AI tools regularly, not occasionally. He compared it to the early days of the PC, when companies had to run training sessions just to get staff comfortable with word processors and spreadsheets. Adoption took time, but the alternative was falling behind. He sees AI the same way. Leaders who wait for their teams to come around on their own risk losing ground to competitors who move faster. If you would like to learn more, visit Kevin Surace's website or follow him on Linkedln.
TakeawaysAI removes repetitive work so people can focus on higher-value tasks.Joy drives success in the AI era.AI will create new jobs by accelerating innovation.An AI-first culture is key to staying competitive.Biometric security will help counter AI-powered fraud
Chapters00:00 Introduction to Kevin Surace and AI's Potential
01:52 Kevin's Journey and the Joy Success Cycle
04:14 AI as a Joy Maker in Daily Work
06:07 The Cycle: Joy Leads to Success
07:39 AI's Opportunity for Increased Jobs
12:15 Is AI a Technology Cycle or a Transformation?
13:50 The Ubiquity of Smartphones and AI's Role
14:39 Workforce Transformation and AI Adoption
23:06 Cybersecurity Challenges in the AI Era
26:55 Advice for CEOs and Leaders in an AI World
Can AI Modernise Legacy Systems? What Leaders Need to Know
2026/07/27
AI is changing the conversation around legacy modernisation, but successful transformation demands far more than powerful models and automated code generation. It requires engineering discipline, governance, and a clear-eyed view of where AI genuinely adds value and where it doesn't.
On a recent episode of Tech Transformed, host Christina Stathopoulos, founder of Dare to Data, sat down with Shodhan Sheth, Enterprise Modernisation Platform and Cloud Lead, and Alessio Ferri, Lead Software Engineer, both part of Thoughtworks' Global Legacy Modernisation Service Development Team, to unpack exactly that.
Legacy Modernisation With AIThe conversation around AI in legacy modernisation is often muddied by marketing noise. As Sheth puts it, "value and hype can coexist". Overpromising doesn't automatically mean a technology is worthless. The real question for technology leaders is whether AI meaningfully improves the cost-time-value equation for a specific problem.
This will always start with problem-solution fitness: has someone already solved a comparable challenge with AI, and does the proposed use case genuinely fit that pattern? As Sheth notes, "most things can be judged by cost, time, and value", which is a simple but effective filter for cutting through the noise.
Rethinking Legacy ModernisationGenerative AI is inherently probabilistic, while enterprise software has always relied on deterministic, predictable behaviour. Ferri unpacks this tension by separating two very different use cases: using AI to build systems, and embedding AI within operational systems.
When AI writes code, inconsistency is manageable; developers review, test and refine the output before it ships. Production systems are a different matter entirely, where unpredictable behaviour carries real operational risk. As Ferri explains, "AI in production requires different guardrails than AI for building."
The practical answer is controlled use. AI might suggest alternative products in a marketplace, for instance, while deterministic rules still guarantee that only in-stock items are ever shown. This lets AI add value within a firm, enterprise-grade constraints.
Why AI Alone Won't Modernise Legacy SystemsTechnology is only part of the story. Sheth is clear that modernisation is fundamentally about change, and change is hard, especially across large enterprises with tangled, interconnected systems. Tasks that resist automation are often the hardest, like upskilling teams, explaining complex trade-offs, and winning buy-in; these cannot be solved with code alone. These human and organisational factors are routinely underestimated. Where the impact of a change is broad, he also advises either aligning teams properly across the business or breaking the change into smaller, more manageable pieces, a strategy that reduces resistance and smooths the path to adoption.
If you would like to learn more about this, visit Thoughtworks or connect with both Sheth and Ferri on LinkedIn.
TakeawaysApplying AI to modernise complex enterprise systems.Distinguishing hype from practical AI applications.Balancing probabilistic AI with deterministic enterprise software.Organisational and leadership challenges in AI modernisation.Building control, traceability, and abstractions in AI workflows.Advice for CIOs and CTOs on AI adoption.
Chapters00:00 Introduction to AI and Legacy Modernisation
01:18 Meet the Experts: Shodhan and Alessio
02:47 Distinguishing Hype from Value in AI
05:51 The Tension Between Probabilistic and Deterministic Systems
10:13 The Human Element in Modernisation
17:12 AI's Role in Enterprise Transformation
19:26 Distinguishing Hype from Value in AI
22:13 Probabilistic vs Deterministic Systems
27:45 People and Processes in Modernisation
29:03 Lessons in AI for Legacy Modernisation
Podcast sponsorship advertising
Start advertising on Tech Transformed relevant audience podcasts
You may also like to advertise on these Podcasts

4.82494978
The 1000 Hours Outside Podcast
1000 Hours Outside

4.715161997
Thrivetime Show | Business School without the BS
Clay Clark

4.6620172000
The Dan Bongino Show
Cumulus Podcast Network | Dan Bongino

4.98711800
The Adam Mockler Show
MeidasTouch Network

4.824781904
Deck The Hallmark
Bramble Jam Podcast Network

4.916171639
The Kristian Harloff Show
Kristian Harloff

4.847132000
Pat Gray Unleashed
Blaze Podcast Network

4.713452000
The NewsWorthy
Erica Mandy

4.7368531302
Louder with Crowder
Louder with Crowder

4.84326906
The Liz Wheeler Show
Blaze Podcast Network

