There has always been an arms race in the vendor space, and this year it has been about AI. At the same time, the practitioners I talk with are building far more than they used to. A few weeks ago I spoke with a risk leader who described what her team built in house, and it was impressive. That made me wonder whether the ground is shifting beneath vendors, and whether we will still need them in a year or two.
I invited Netanel Kabala to help me think it through. Netanel and I met at PayPal 17 years ago, when he started as a fraud analyst after the acquisition of PayPal’s Tel Aviv fraud sciences team. He later co-founded Simplex, the first crypto on-ramp provider, led AI and analytics at Nuvei after the acquisition, and recently co-founded Duly, which helps payment providers and fintechs own their decisioning stack. We look at building vs buying fraud vendors from several angles, including vendor fatigue, what teams build first, and what foundation models and decision models change. We don’t land on a yes or no answer, and I think that’s the honest result. Instead, we sketch where to build, where to buy, and where joint development makes sense.
What you’ll hear in this episode:- Why vendor fatigue is pushing teams to build, and what that means for the vendor relationship
- Why the most successful in-house builds so far are small tools that save one expert time and don’t replace a whole platform
- How vendors are shifting from end-to-end solutions toward data providers, with network data and device intelligence valued most by larger teams
- Why manual review viewers are easy to build with AI coding, and why a rule engine is a very different kind of project
- How AI slop shows up in risk teams, from dozens of models built overnight to latency and drift monitoring problems nobody planned for
- What foundation models and decision models change about features, anomaly detection, and who can deploy a real-time fraud model
- Why segmentation is the best place to start, and why building generic capabilities like KYC or sanction screening is a trap
- How to judge whether your organization is ready to build, including engineering support, access to risk talent, and leadership buy-in
- Why the maintenance trap catches analysts who become product manager, DevOps engineer, and backend engineer at once
You should listen to this episode if you:- Lead a fraud or risk team and are deciding what to build and what to keep buying
- Feel vendor fatigue and want a clearer way to think about which relationships still earn their place
- Have built something in house with AI and want to know whether it can scale
- Need to explain to leadership what a build roadmap requires beyond a quick proof of concept
- Want to know how foundation models and decision models may change the feature layer and vendor data