
How Predictive Analytics Stops Budget Overruns Before They Happen?
Agentic Conversations (formally mlops.community)Show Notes
Every engineer at Wayfair can now see, in real time, exactly what their code costs, and that's on purpose. Brent Eubanks, FinOps Architect at Wayfair, walks us through what happens when you stop treating AI spend as a finance problem and start treating it as an engineering one.The story that sticks with you: a team was burning $400k a month on an LLM-driven workflow, until they flipped the whole thing on its head - hard-coded logic doing the heavy lifting, AI called in only when it's actually needed. New spend: $80k. It's the kind of move that only makes sense once you realize more agentic autonomy isn't always the win it's sold as.From there we get into the machinery Wayfair has built to make cost ownership feel less like a punishment and more like a superpower: guardrails baked straight into coding copilots, predictive alerts that catch a team blowing its budget before the month even ends, a "spend captain" system that pushes budget decisions down to the people closest to the work, and a genuinely strange new question every tech leader is starting to ask: if you were staffing a company with a team of AI agents instead of people, what would that org chart even look like?Wayfair: https://www.wayfair.comBrent Eubanks: https://www.linkedin.com/in/brenteubanksDemetrios: https://www.linkedin.com/in/dpbrinkmTimestamps:[00:00] Intro & teaser [01:14] Meet Brent (FinOps Architect, Wayfair) [02:34] Making AI adoption easy for developers [03:30] Three-area cost governance framework [04:45] Automated FinOps guardrails in pull requests [07:29] Predictive analytics: 400% over budget warnings [08:26] The 400% spender: asset or liability? [10:06] The "spend captain" model [12:13] The goal: 1000x more token use in two years [13:05] The thought experiment [15:08] The $400k workflow rebuilt for $80k [16:42] Hardcoded first, LLM as fallback [19:49] Engineers now own their full cost stack [20:13] The FinOps companion that works overnight [24:10] Guardrails injected before the pull request [26:17] Recurring tasks become automated skills [27:46] Sankey diagram: cost per agent step in real time [28:40] "The bill didn't blow up - that doesn't happen by accident"
More from Agentic Conversations (formally mlops.community)
AI can write your code, choose its own tools, and book your next trip. But who checks that it actually did the job?
What happens when you give 200 engineers who have barely touched AI a coding assistant and a six-month deadline to rebuild their platform? Pepijn Senders, a principal engineer who previously led AI enablement at HelloFresh, has done exactly that, and he chose Sonnet over Opus on purpose.
An AI slips out of its sandbox. A chatbot won’t explain your cat’s stripes. And your next shopping spree might not involve you clicking anything.
What happens to the web when the ones browsing it are no longer people? Sarah Drasner, Area Tech Lead at Google, sits down with us ahead of her Agentic Web keynote at AGNTCon + MCPCon North America. She works through that question from both directions: rebuild the web so agents can use it properly, or build agents smart enough to handle the web as it already exists.
Everyone is racing to build one agent that can do everything. Justin Schroeder, co-founder of Standard Agents, thinks the future looks more like thousands of tiny ones. Ahead of his talk on domain-specific agents at AGNTCon + MCPCon North America, he explains why tightly scoped agents might be the smarter bet, even if it feels like a step back toward the single-purpose machine learning models of a few years ago.