From Natively Built to Prismatic | Connect 2026

Libby Stengel, who leads customer success at Prismatic, talks with Jeff Holmes of FMX about moving every integration to Prismatic, including the long-standing natively-built ones that were working fine. FMX is a facilities and maintenance management platform running on .NET, Azure, Next.js and Vercel. They have over 40 Prismatic integrations serving close to 400 customers, including Workday, ArcGIS and Fastenal. Jeff is candid about the path. They moved off a previous iPaaS provider on a three-month deadline and used low-code as a stopgap. They assumed customer success and customers themselves could build integrations, and that turned out to be wrong. They ran proofs of concept before committing. And the argument that finally changed things internally wasn't technical: code-native plus AI-assisted development shifted the rebuild math, so migrating became cheaper than maintaining. The numbers: 21 code-native integrations now carry 307 of their 394 Prismatic customers. Time to build is down 60%. Integration support tickets are down 50%, and Jeff says almost everything still coming in traces back to the few low-code implementations they haven't retired yet. He closes with best practices for teams considering the same move, and takes questions on building an agent context repository and whether code-native is genuinely better for troubleshooting. Full conference write-up and all session recordings: https://prismatic.io/blog/prismatic-c... Code-native integrations docs: https://prismatic.io/docs/integration... 0:00 Intro 0:36 About FMX and Jeff 1:42 Why move natively-built integrations 3:01 Where the resistance came from 4:11 The common objections 6:31 The hardest part to overcome 7:18 The migration journey 9:17 Invest or migrate 10:08 What to build first 10:52 Why code-native over low-code 11:48 Result: 60% faster builds 13:08 Result: 50% fewer support tickets 14:12 A business decision, not an architecture problem 15:45 Best practices 17:48 The takeaway 18:16 Q&A: building an agent context repository 19:20 Q&A: observability and troubleshooting #saas #apis #developertools #ipaas #integrations #typescript #technicaldebt #b2bsaas