The $285B SaaS selloff has everyone asking whether AI will kill software. I think that's the wrong question.
The better question: which parts of SaaS get replaced, and which become more valuable? And whatβs that mean for #martech?
I've spent the last 18 months talking to 150+ mid-market and enterprise companies about their stacks. They're not preparing to rip everything out. But they are rethinking what to buy versus build.
Here's where I think the lines are forming.
WHAT GETS DIY'd
β Workflow UI. When one person can spin up a decent interface in days with Codex or Claude Code, they stop tolerating clunky vendor UX. Chat-based interfaces will replace purpose-built screens for more and more marketing workflows. AI agents will use software, not humans.
β Integration glue. Custom connectors between your tools (syncing CRM data to Slack, routing leads between platforms, chaining enrichment steps together) are perfect for agentic coding.
β Commodity features. Basic βif this then thatβ logic is wrapper functionality any competent engineer can vibe code in a weekend.
WHAT ENTERPRISES WILL STILL PAY FOR
I predict enterprises will still subscribe to systems of record, and more importantly, Systems of Control.
β Marketing-grade trusted data. Not "store all data", the warehouse will handle that. But the layer that determines what's trusted enough for marketing to act on: identity resolution, permission, suppression rules, deduplication. Nobody's going to vibe-code their consent management.
β Governed decisioning. This is essential. It's easy to build an AI agent that decides what email to send. It's very hard to build one that knows why your team sends two webinar invites instead of one, why certain contacts are limited to three emails per week, and why last quarter's campaign structure outperformed the one before it.
This "why" β the campaign patterns, the segment logic, the institutional knowledge that lives in your MOps team's heads β is what makes AI useful versus generic. Without it, you get "confident errors": technically correct decisions that are strategically wrong. The AI picks your best-performing campaign for a product launch, not knowing your team learned last quarter that this audience needs a customer story before the pitch; that insight came from three launches and sales feedback, not from any field in your CRM.
β Execution infrastructure. For email specifically, AI can draft the HTML, but it cannot manage sender reputation, IP warming, or domain throttling. Deliverability is a domain expertise problem, not a coding problem. (Other channels will connect over via API/MCP.)
The short version: vibe-coding eats workflow UI. But enterprises still subscribe to the systems that keep them SAFE β trusted data, governed decisions, and reliable execution.
Where's the line forming between build and buy in your martech stack?
The better question: which parts of SaaS get replaced, and which become more valuable? And whatβs that mean for #martech?
I've spent the last 18 months talking to 150+ mid-market and enterprise companies about their stacks. They're not preparing to rip everything out. But they are rethinking what to buy versus build.
Here's where I think the lines are forming.
WHAT GETS DIY'd
β Workflow UI. When one person can spin up a decent interface in days with Codex or Claude Code, they stop tolerating clunky vendor UX. Chat-based interfaces will replace purpose-built screens for more and more marketing workflows. AI agents will use software, not humans.
β Integration glue. Custom connectors between your tools (syncing CRM data to Slack, routing leads between platforms, chaining enrichment steps together) are perfect for agentic coding.
β Commodity features. Basic βif this then thatβ logic is wrapper functionality any competent engineer can vibe code in a weekend.
WHAT ENTERPRISES WILL STILL PAY FOR
I predict enterprises will still subscribe to systems of record, and more importantly, Systems of Control.
β Marketing-grade trusted data. Not "store all data", the warehouse will handle that. But the layer that determines what's trusted enough for marketing to act on: identity resolution, permission, suppression rules, deduplication. Nobody's going to vibe-code their consent management.
β Governed decisioning. This is essential. It's easy to build an AI agent that decides what email to send. It's very hard to build one that knows why your team sends two webinar invites instead of one, why certain contacts are limited to three emails per week, and why last quarter's campaign structure outperformed the one before it.
This "why" β the campaign patterns, the segment logic, the institutional knowledge that lives in your MOps team's heads β is what makes AI useful versus generic. Without it, you get "confident errors": technically correct decisions that are strategically wrong. The AI picks your best-performing campaign for a product launch, not knowing your team learned last quarter that this audience needs a customer story before the pitch; that insight came from three launches and sales feedback, not from any field in your CRM.
β Execution infrastructure. For email specifically, AI can draft the HTML, but it cannot manage sender reputation, IP warming, or domain throttling. Deliverability is a domain expertise problem, not a coding problem. (Other channels will connect over via API/MCP.)
The short version: vibe-coding eats workflow UI. But enterprises still subscribe to the systems that keep them SAFE β trusted data, governed decisions, and reliable execution.
Where's the line forming between build and buy in your martech stack?