Sign In
Register

Partnership opportunities

Secure your seat

Call to action
Your text goes here. Insert your content, thoughts, or information in this space.
Button

Back to speakers

Louis
Hénault
Senior Machine Learning & Simulation Engineer
Red Bull
Louis Hénault is a Senior Machine Learning & Simulation Engineer at Red Bull Racing & Red Bull Technology, where he has worked since 2021. He brings more than a decade of experience across engineering, quantitative methods, data and AI systems at scale, working mainly with Python, PyTorch, distributed systems and large language models. Before joining Red Bull, Louis was Lead Machine Learning Engineer at L'Oréal and Lead Data Scientist at OgilvyOne Worldwide in Paris, and earlier served as Chief Data Officer at unltd.fm. He also writes about open source LLMs and MLOps, including how to build and deploy your own AI chatbot using only open source models and tools.
Button
01 December 2026 16:30 - 17:00
Panel | From GenAI to autonomous workflows: How teams are evolving their AI systems
Many teams start with contained generative AI pilots: a narrow use case, a couple of integrations, and a human checking every output before it goes anywhere. Once that same system is expected to carry a full workflow instead of a single feature, the assumptions behind how the generative layer was originally built stop holding up. This session looks at what actually shifts inside a generative stack as a project moves from a contained pilot to something a real workflow depends on. It focuses on where prompting, retrieval and evaluation start to strain once outputs stop being one-off answers and start becoming inputs the next step relies on. What this session will cover: - Where a feature-level generative AI pilot starts to break down once it is asked to carry an entire workflow end to end - How prompting and retrieval design need to change once an output becomes a dependency for the next step, not just a one-off result - What evaluation has to measure once a generated output feeds a downstream step, not just when it produces an acceptable answer on its own - How teams are rebuilding their generative stack for reliability before layering any further automation on top of it