Key Takeaways

  • Quinn Slack, co-founder of AMP and former CEO of Sourcegraph, argues that AI agents make complex SaaS settings menus, data pipelines, and MCP connectors obsolete for internal tooling.
  • Slack introduces "jellyware" as malleable internal software that sits between rigid enterprise applications and uncontrolled vibe coding, easily modified on demand.
  • swyx predicts that “coding SaaS will be the last SaaS in the world” because developer-focused AI tools will let engineers build and spin up every other software tool on the fly.
  • Small teams can ditch expensive off-the-shelf subscriptions for lightweight, forkable applications where natural language and source code serve as the primary configuration interface.

Code Is the New Settings Menu

Traditional enterprise software forces you into an endless series of configuration screens. When you buy a dashboard or a project tracking tool, you spend weeks configuring role-based permissions, setting up complex integrations, and fiddling with dropdown menus. Slack points out that AI agents eliminate this overhead entirely.

“You don't need a setting screen. You don't need a complex integration and MCP and all of the overhead that's entailed by buying some off-the-shelf software package to do dashboards when really an agent is the ultimate settings screen for any software and code is the ultimate setting screen for any software,” Slack explains.

When you want to tweak an internal dashboard, you should not have to submit a ticket to an external vendor or read through API documentation. You tell an agent what you want changed in plain language. The agent alters the source code directly in a cloud sandbox. Code replaces the brittle administrative UI that product managers spent years building.

The Shift to Disposable Jellyware

Slack calls these malleable tools jellyware. It is software designed to bend and adapt whenever an engineer touches it. It provides more structure than pure vibe coding, but avoids the frozen rigidity of enterprise SaaS packages.

“We will be releasing a lot of these little jellyware is what we're calling it. It's like softer than software but it's not totally vibe coded and you can customize it with your own agent,” Slack says.

Think about how internal tools get built today. A team needs a custom metrics view or a specialized triage queue. In the past, they had two bad options. They could buy an expensive off-the-shelf tool with dozens of features they never use, or assign two senior engineers to spend three months building an internal app from scratch. Jellyware creates a third path: spin up a minimal, forkable template, let an agent wire it to internal data in ten minutes, and throw it away or mutate it when team priorities change next month.

As Slack puts it, “I think it is just the very beginning of agents now changing how you actually use software and how you run software and how you distribute software.”

Why Coding SaaS Swallows Everything Else

If creating customized mini-apps takes minutes, the economic logic behind vertical SaaS starts falling apart. swyx notes that software categories outside engineering will struggle to defend their pricing power.

“Coding SaaS will be the last SaaS in the world because all the other SaaS will just be buildable via coding SaaS. So you might as well just only do coding SaaS,” swyx argues.

This dynamic favors forkable software architectures. Teams do not need complete open-source transparency for every line of business logic, but they do need the ability to adjust the interface and endpoints on demand. As swyx notes, as long as backend contracts, security boundaries, and privacy protections remain solid, founders should let agents mold the user interface however they want.

What to Do With This

Audit your team's software spending this week and identify one internal tool that costs over $200 per month just to display basic dashboards or triage tickets. Have one engineer spend two hours with an agent generating a lightweight, self-hosted fork of a minimal open template to replace it. If the agent can replicate the core functionality in a single afternoon, cancel the subscription and establish code as your internal configuration layer.