Post

Aaron Levie
Aaron Levie@levie·
“We’ve also been moving off legacy systems with poor, slow, outdated, and inconsistent APIs.” If you’re building software that can’t work fully headlessly in a way that agents want to use, you’re not prepared for what the future of software is going to look like. Agents will use software 100X more than people, and people will more and more interact with their data and workflows via agents across many different platforms. This is the real risk but also opportunity for platforms right now. Software doesn’t go away, but it becomes the guardrails and business logic for what agents are able to operate on. But if you can’t connect to wherever the agents want to do that work, you’re DOA.
Guillermo Rauch@rauchg

Almost every SaaS app inside Vercel has now been replaced with a generated app or agent interface, deployed on Vercel. Support, sales, marketing, PM, HR, dataviz, even design and video workflows. It’s shocking. The SaaSpocalypse is both understated and overstated. Over because the key systems of record and storage are still there (Salesforce, Snowflake, etc.) Understated because the software we are generating is more beautiful, personalized, and crucially, fits our business problems better. We struggled for years to represent the health of a Vercel customer properly inside Salesforce. Too much data (trillions of consumption data points), the ontology of Vercel was a mismatch to the built-in assumptions, and the resulting UI was bizarre. We generated what we needed instead. When you don’t need a UI, you just ask an agent with natural language. We’ve also been moving off legacy systems with poor, slow, outdated, and inconsistent APIs, as well as just dropping abstraction down to more traditional databases. UI is a function 𝑓 of data (always has been), and that 𝑓 is increasingly becoming the LLM.

English
65
41
440
130.1K
Decebal | Rust + Move Engineer ⚙️
This is the right framing. The API surface is becoming the product, not the UI. Software that was designed for humans clicking buttons is fundamentally wrong for a world where agents are the primary consumers. Clean, well-typed APIs with predictable behavior become the competitive moat. From the engineering side, this is why I think strongly typed interfaces matter more than ever. When an agent calls your API, there's no human to interpret a vague error message. The contract has to be explicit, the errors recoverable, and the behavior deterministic. That's where Rust-style type safety shines.
English
0
0
0
3
Paylaş