Every fraud leader I've spoken to this year has heard the same message: cut costs. You've probably already had the conversation. You've explained why fraud isn't just another operating expense, why reducing investigators today often means higher fraud losses tomorrow, and why your team is already stretched thin. And yet the budget cuts are still coming.

Here's the question I'd rather ask. What if finance isn't actually your biggest problem?

In this episode, I introduce the idea of agentic fraud ops and explain why the real issue isn't shrinking budgets. It's that most fraud organizations are still operating at human learning speed while their adversaries have already moved to machine speed.

We talk about why fraud detection systems decay over time, why fraud rules and machine learning fraud detection models become less effective the moment they're deployed, and why the future of fraud prevention AI isn't about replacing analysts. It's about building systems that continuously learn.

Honestly, optimizing a slow system is still optimizing a slow system.

This episode explores what happens when AI-powered fraud detection becomes part of the reaction cycle itself instead of just another automation project. If we're going to redesign fraud operations, we first need to rethink what performance actually means.

• Why agentic fraud ops changes how fraud teams should measure success
• Why every fraud detection system begins decaying the day it goes live
• How fraud detection rules, machine learning models, and manual review age differently
• Why reaction speed is becoming the most important fraud metric
• How AI agents for fraud detection can compress learning cycles from weeks to hours
• Why fraud operations automation should focus on new capabilities instead of replacing people
• How fraudsters are already using AI-driven fraud prevention techniques against defenders

• Lead a fraud operations or fraud strategy team
• Want to modernize your fraud prevention system
• Are evaluating AI agents for fraud detection
• Need to reduce costs without increasing fraud losses
• Are planning the future of your fraud operations transformation

So this episode starts with a data executive walking into a fraud team.

Which sounds like the setup to a very niche joke. And maybe it is. But honestly, it also describes a real problem most fraud teams know too well: we rely on data for almost everything, but the relationship between fraud teams and data teams is often messier than anyone wants to admit.

In this episode, I’m joined by Shachar Meir, a data advisor and former director of data at Meta, to talk about LLM analytics, self-service analytics, data infrastructure, and why fraud teams cannot just throw AI on top of messy data and hope it becomes strategy.

Because yes, LLM-powered self-service analytics sounds amazing. Ask a question in plain English, get an answer, move faster, avoid waiting three weeks for a data team with 900 priorities. Great. I want that world too.

But then you’ve got to ask yourself: where did the answer come from? Which tables did it join? What definition did it use? Did it understand the business context? Did it hallucinate? Did you ask the right question in the first place?

Not a small detail.

This conversation is really about the gap between the promise of AI analytics tools and the operational reality of fraud analytics. Fraud and risk teams work in adversarial environments. The problem keeps changing. The signal-to-noise ratio is bad. The cost of getting it wrong can be massive, whether that means letting fraud through or blocking legitimate users. So if you want LLM analytics to actually help, you need more than a shiny interface. You need data foundations, governance, semantic clarity, and the humility to start small.

• Why fraud and risk teams are unusually complex data customers
• How fraud teams can work better with data teams instead of requesting endless point solutions
• Why self-service analytics failed so often before LLMs entered the picture
• What changes, and what does not change, when LLM analytics becomes the interface
• Why asking the right data question matters more than getting a fast answer
• How data governance, semantic layers, and data quality shape AI analytics results
• Why fraud teams should start AI adoption with one curated table, one use case, and one measurable outcome
• How to think about the one-hour, one-day, one-week, and one-month versions of a data project

• Work in fraud operations and depend on data teams to ship risk or fraud analytics projects
• Are considering LLM analytics or AI agents for data analysis inside your fraud stack
• Have been promised AI data querying that sounds too easy, because it probably is
• Need better ways to align with data engineering, analytics, or risk data infrastructure teams
• Want a practical way to think about AI data governance before deploying tools that affect real users

Here is the uncomfortable thing about fraud systems: even when every individual part looks reasonable, the whole thing can still behave like a maze.

You fix one rule. Great. You tune a model. Nice. You clean up a manual review flow. Very responsible. And then a good user still gets blocked somewhere else because another rule, partner response, payment routing decision, KYC check, AI agent, device intelligence signal, or some forgotten logic from three quarters ago decided to step in and say, absolutely not.

In this episode of the False Positives Masterclass, I’m talking about fraud override logic, which is one of the more powerful tools mature fraud teams can use when reducing false positives across a complex fraud stack. The idea is simple in theory: build a high-level safety net over the system that can recognize users you already have strong reason to trust, even if one actor in the stack tries to block them.

But simple in theory is where many bad fraud ideas are born. So we need to be careful.

A fraud system override is not a shortcut. It is not a “good vibes” approval layer. It is not an excuse to ignore bad logic underneath. It is a controlled, evidence-based mechanism that asks: before we block this user, do we have airtight evidence that they are actually legitimate?

That sounds obvious. It is not. Otherwise, more teams would do it well.

• Why even well-tuned fraud prevention logic can still create false positives
• How fraud override logic works as a safety net over rules, models, AI agents, manual review, KYC checks, and partner responses
• Why some fraud detection rules should never be overridden automatically
• How known good users and inherited trust signals can help reduce false positives
• Why high-exposure environments can be useful false positive indicators
• How geo-chaining can help distinguish travelers and legitimate mismatches from fraud
• Why non-resellable or low-risk items can support safer payment fraud approvals
• How to deploy fraud override systems safely using shadow mode testing and gradual rollout

• Work in fraud operations and your stack has too many independent blocking points
• Are trying to reduce false positives without weakening fraud detection rules
• Need a safer way to identify trusted users across accounts, devices, cards, or flows
• Want practical examples of fraud override logic beyond generic allowlists
• Are evaluating when to use device intelligence, geo-chaining, manual review, or challenger rules to improve decisioning