Scott Lavery unpacks what really happens when integrations shift from a "nice to have" feature to something the company can't function without.

## No-Code vs Code First: Why Visual Builders Often Lead to Integration Dead Ends

In this episode of _Between Product and Partnerships_, Pandium CEO [Cristina Flaschen](https://www.linkedin.com/in/cristina-flaschen/) sits down with [Scott Lavery](https://www.linkedin.com/in/scott-j-lavery/), Senior Product Manager at Arkestro. They unpack what really happens when integrations shift from a "nice to have" feature to something the company can't function without.  Scott shares hard-earned lessons from a decade in B2B SaaS, covering sectors from martech to procurement. He discusses the headache of inheriting messy stacks and why iPaaS tools often hide long-term costs. The conversation explores what makes integrations fundamentally different from core product work, and why owning your integration strategy isn’t just a technical decision... it’s a product and business decision.

## Listen on [YouTube](https://www.youtube.com/watch?v=egyHB0Erhvo), [Spotify](https://open.spotify.com/episode/4rRkeUXFEnympPoz7XEVEm?si=8b8c45c40a6c45c4), and [Apple Podcasts](https://podcasts.apple.com/us/podcast/no-code-vs-code-first-why-visual-builders-often-lead/id1624736210?i=1000747061275)

## Key Topics
**1) Why integration PM work is fundamentally different**  
Integration success is defined by invisibility. Unlike standard features, value is found in reliability and trust rather than how often a user clicks a button.  
**2) The hidden costs of low-code and iPaaS tools**  
Teams often end up writing code blocks inside "no-code" tools. We discuss how pricing models can distort architectural decisions and where velocity eventually hits a wall.  
**3) What to do when you inherit a messy integration stack**  
Practical advice for PMs walking into undocumented systems filled with inherited workflows and vendor dependencies they can’t control.

### “The hidden maintenance cost adds up. And in the long run, owning your integrations pays dividends.”  
### — Scott Lavery

## Tactical Takeaways
- Measure integration success by reliability, not engagement.  
- Talk to customers to understand real-world system usage before building.  
- Avoid relying on inherited knowledge, documentation and ownership matter.  
- Evaluate integration decisions based on long-term maintenance cost, not just initial speed.  
- Treat integrations as core product infrastructure, not temporary solutions.

## Episode Links & Resources
🎧 [Listen](/content/podcast/no-code-vs-code-first-why-visual-builders-often-lead-to-integration-dead-ends/index.html) to the full episode  
🔗 [Scott Lavery](https://www.linkedin.com/in/scott-j-lavery/) (Guest) on LinkedIn  
🔗 [_Cristina Flaschen_](https://www.linkedin.com/in/cristina-flaschen/) (Host) on LinkedIn