In an agentic world the UI stops mattering because the agent isn't accessing software through it — the data, the logic, everything stored beneath the workflow layer is where the real value is.
Sema explains that 'headless' software reflects a shift where agents bypass human-facing UIs entirely, revealing that the true value of software was always the data and logic beneath the interface, not the workflow screens themselves. ✦ AI generated
Sema Amble · a16z Podcast · 2026-07-07 · original ↗
starts at this moment · 2:31
“So, Sema, can you just walk me through first what headless software means and explain kind of what changes it introduces?”
traditional software had been built around humans accessing it and it was workflow to capture data and we could talk more about what that meant in an agentic world do you actually need that the UI doesn't matter because the agent isn't accessing the software via the UI... the data, the logic, everything stored below it is really where the value is, not just the workflow software that's being tracked at the top.
verbatim transcript · starts at 2:31
2:31what's happening which is you know traditional software had been built around humans accessing it and um it was workflow to capture data and we could talk more about what that meant in an agentic world do you do you actually need that the UI doesn't matter matter because the agent isn't accessing the software via the UI. We could unpack whether the UI matters or not. But in the idea of the being headless is the
2:59the data, the logic, everything stored below it is really where the value is, not just the workflow software that's being tracked at the top. >> Gotcha. Um, and uh, this was announced a couple months ago. I'm curious kind of in in the past couple months, what have we seen? I mean you wrote even in the piece kind of you at the beginning you were a little bit you know funny maybe
3:23and you said is this really even that big of an announcement? Is this sort of a rebrand of you know APIs that they had kind of already made available? So does this feel like a significant change? Is this maybe more of a branding exercise? Um and kind of like what have we even seen in the past couple months since we've been able to kind of observe what
3:43changes have have really happened? So I'll separate it out into the Salesforce context and then like the broader context which I think the broader context is more interesting. In the Salesforce context probably not that interesting. Uh I think Salesforce I think rightfully again it was acknowledging a shift that's happening in the market. I don't from what I could tell nothing actually changed. Their 360 product was uh the same APIs that had
4:06always been exposed now rebranded as as as their 360 product. How and and APIs have always existed. So you know many uh or I shouldn't say always but for a long time have existed. Um but I think the broader trend here is there you know Salesforce among others are thinking about how they build themselves for the agentic world. Um and so if an agent needs to access the data in a CRM like