Discover
Tech Transformed
Tech Transformed
Author: EM360Tech
Subscribed: 17Played: 171Subscribe
Share
© Copyright 2026 EM360Tech
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.
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.
434 Episodes
Reverse
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 committeeRead the full episode page: Watch more from the Tech Transformed Podcast: https://open.spotify.com/show/4rbDpZnuDKB53VKBZO2NmfRelated reading from EM360Tech Why AI Is Forcing Organisations to Rethink Data Governance: https://em360tech.com/tech-articles/why-ai-forcing-organisations-rethink-data-governanceDigital Literacy Has Changed: When Not to Trust Tech: https://em360tech.com/tech-articles/digital-literacy-knowing-when-not-to-trust-technologyAI Search Governance: Enterprise Guide: https://em360tech.com/tech-articles/ai-search-governance-enterprise-guideWhen to Use Human-in-the-Loop at Inference Time: https://em360tech.com/tech-articles/human-in-the-loop-decision-stageMore B2B tech podcasts: https://em360tech.com/podcastsFollow EM360Tech on LinkedIn: https://uk.linkedin.com/company/em360Follow EM360Tech on X: https://x.com/EM360TechFollow Private Equity: https://www.linkedin.com/company/yfm-equity-partners/home/#TechTransformed #AI #PrivateEquity #UKBusiness #AIGovernance #EM360Tech @yfmequitypartnersuk @enterprisemanagement360
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 guests00:28 The move beyond screen-based AI to physical AI00:58 Defining physical AI and its significance01:26 Why physical AI will be larger than cloud AI02:12 The large upheaval AI is causing in various sectors03:23 The shift from rule-based to reasoning machines04:22 How models are getting smaller and more efficient05:54 Enabling new capabilities through AI in physical devices06:12 Current innovations in drones, robots, and autonomous vehicles07:35 The role of agentic software and agent engineers08:59 Democratisation and ease of developing physical AI systems10:03 Unlocking new business models with physical AI11:56 The future of AI development and agentic engineering12:50 The impact of physical AI on industries like manufacturing and healthcare21:38 How to lead and join the physical AI revolution23:16 Closing remarks and next steps for listenersRead the full article: https://em360tech.com/podcasts/what-physical-ai-outgrow-cloud-aiWatch episode on YouTube: https://youtu.be/GE4sTiBk95ASiMa.ai: https://sima.aiEM360Tech: https://em360tech.comWatch 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
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 significance01:08 Defining the components of an AI harness: context, identity, policy, action, observability05:12 The role of centralization in AI harness architecture06:44 Governance challenges in multi-agent AI environments17:48 Implementing a five-step governance process22:20 Why focusing on the harness is key for AI progress27:17 The importance of governance as AI agents gain authority28:24 Final thoughts on controlling autonomous AI agentsWatch the previous episode with David Hsu, CEO of Retool: https://youtu.be/rvdl4Fy2taw?si=3nMzO...Learn more about Retool: https://retool.comMore 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
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...
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 LeadersVisit 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








