Key Takeaways
- Amp spun out of Sourcegraph as a 20-person startup with zero venture capital funding and immediate profitability.
- Thorsten on the Amp team coined the term "jelly wear" to describe personal, malleable software that bends to an individual's specific needs.
- Enterprise sales cycles distort developer tools because roadmaps get shaped by marketing teams rather than product builders.
- AI development is shifting away from line-by-line manual code reviews toward verifying completed software artifacts.
Enterprise Sales Distorts Software
Most enterprise software tools end up bloated for one reason: sales teams must explain them to procurement committees. When an engineering team builds for an enterprise contract, the product stops serving the person at the keyboard. It starts serving the enterprise buyer.
Quinn Slack saw this tension play out while co-founding Sourcegraph. Large organizations push product teams into endless ticketing chains and feature checklists that satisfy corporate buyers. Slack noted how this process warps development: “I think that maybe a lot of developers don't realize this, but so much of a company's decisions and product strategy is driven not by the founding team or the developers, but by how can you make a product's features be legible to an enterprise seller and marketing team that's several steps away from the product.” (play from 1:15:19)
When five layers of bureaucracy separate the builder from the buyer, the end product slows to a crawl. The software becomes heavy, rigid, and tedious to maintain.
Why Amp Took Zero Venture Capital
Instead of raising a massive venture round to scale Amp, Slack kept the team small and avoided institutional capital entirely. Amp operates as a profitable 20-person shop. That small headcount protects the team from the median demands of corporate software buyers.
Traditional venture capital demands hypergrowth, which inevitably forces developer tool companies into the enterprise sales machine. Slack sees capital differently: “I love VCs, but they are essentially fuel on a fire, and what we've learned is, with things changing so fast, the old playbooks just do not work.” (play from 1:14:43) Pouring fuel on a fire before the core product mechanics are clear incinerates flexibility.
By avoiding institutional funding, Amp can ignore standard enterprise requests. Slack points out that real progress comes from small, autonomous units rather than massive corporate divisions: “There's nothing that strangles creativity like being a cog in a big company, like taking tickets from one person that has filtered them from five other people. It gets created from small groups of crazy people building stuff, and that is how I think more and more software is going to be built.” (play from 40:58)
Personal Code Replaces Big Systems
The ultimate destination for developer tools is not a single, massive software platform that fits all companies. It is malleable software. Slack calls this “something softer than software.” (play from 13:38) As Slack explained, “Thorsten on our team calls it jelly wear.” (play from 13:43)
Jelly wear is software you mold on the spot. Instead of filing an IT ticket or buying an off-the-shelf SaaS seat, a developer uses an agent like Amp to generate custom code that solves an immediate task. Amp manages this through persistent threads and cloud agents known as Orbs, capturing user intent instead of just leaning on raw foundation models. The process discards the old ritual of line-by-line code review in favor of artifact verification: you check if the finished output actually works rather than auditing every individual line the machine wrote. Software stops being concrete and starts behaving like jelly.
What to Do With This
Audit your internal tooling requests from the last month. Take the single most frustrating internal workflow your team manages through spreadsheets or rigid SaaS software. Instead of buying another tool or waiting for engineering resources, prompt an AI agent to build a single-purpose, disposable script or web interface to solve that exact friction point tomorrow.