AI coding tools have made it genuinely fast to build a certificate of insurance intake tool, a custom incident tracker, or an ERM assessment workflow. A small team can have something working in hours — and that speed creates real organizational momentum. The danger is that momentum moves faster than analysis, and a prototype that worked in demo can become load-bearing infrastructure before anyone planned for it. In this on-demand session, Roma Rishi and Origami Risk Chief Product and Technology Officer Ryan Cantor take the risk manager’s side of the build-vs-buy question. They walk through the contained tool trap, the hidden costs that don’t show up in a build proposal, what governance and security infrastructure a homegrown tool actually has to replicate, and why point solutions that look self-contained almost always become data silos that fragment the risk program over time. If you’re weighing a custom solution, fielding an executive mandate to prove what AI can do, or trying to engage constructively when a prototype is already running, this session gives you the questions to ask before the decision gains momentum — and a clearer picture of where a platform fits in what your organization is building. What you’ll learn: Why the successful prototype is often the most dangerous moment — and how contained tools become load-bearing infrastructure faster than anyone plans. Why build proposals consistently undercount the real cost — leaving out maintenance, integration work, and the risk team time spent on software operations instead of risk. What governance, security, and audit trail infrastructure a homegrown tool must replicate — and what it takes to retrofit when legal or compliance comes asking. How point solutions become data silos that fragment the risk program and make board-level reporting harder, not easier. What four questions to ask before a build proposal gains organizational momentum — and how to use them to pressure-test the business case.