Headless is the new mobile-first. Agents are about to become your biggest user

Here is a question worth asking your product team this week. What percentage of your software's use, twelve months from now, will involve a human looking at a screen?

If the honest answer is anything less than 80%, your product has the wrong shape.

In April, four companies that sit at very different parts of the software stack said the same thing. Box CEO Aaron Levie posted that as agents become the biggest users of software, software has to be available in headless form because agents will talk to APIs, not click through UIs. Zapier CEO Wade Foster told an Axios audience that agents are likely to become the predominant users of software. Salesforce shipped "Headless 360," with cofounder Parker Harris framing the provocation directly: why should a user need to log into Salesforce at all when an agent can act through APIs and tools? Stripe, Mastercard and OpenAI quietly built the rails for agents to make purchases on a user's behalf.

This is not a niche prediction. The next generation of users is software, not people, and the software you built for clicks is now being asked to serve callers.

What "the wrong shape" actually means

For the last fifteen years, most B2B products have been built around the same loop: a user logs in, navigates a UI, takes an action, sees a confirmation. Roadmaps optimised that loop. Designers shortened the click path. Product managers measured engagement, session length, retention.

Agents do not log in. They do not navigate. They do not see the confirmation toast. They call an endpoint, pass parameters, parse the response, and move on. Most products, including most of the SaaS your business pays for today, were not designed for that. The API exists for integrations, but it covers maybe 30% of what the UI can do. The auth model assumes a human at a keyboard. The error messages are written for users, not callers. The pricing model charges for seats that nobody is sitting in.

I learned how big this gap is the hard way. A few months ago I wired an agent into a well-known mid-market SaaS product on behalf of a client. The marketing pages promised a "complete API." The reality was that two of the four actions we needed were UI-only. The vendor's answer was to use browser automation. That is the 2026 equivalent of telling someone to fax their tax return. The product wasn't bad. It was simply built for a world where the user had hands.

Salesforce's Headless 360 announcement is the clearest signal of where this is going. More than 60 MCP tools and 30+ coding skills exposed for Claude Code, Cursor, Codex, Windsurf, and others. The promise is that anything you can do in the UI, you can do through an API, an MCP call, or a CLI command. Salesforce is the largest enterprise software company in the world. If they are doing this, every serious B2B platform will follow within eighteen months.

The three layers your product now needs

The shift is not "add an API." Most products already have one. The shift is that you now need to design for three different consumers of your product, and treat all three as first-class.

The human layer. The traditional UI. Still essential, still where decisions get made and judgment lives. But it is no longer the only interface, and probably not the dominant one for routine work.

The agent layer. A complete, agent-addressable surface. Every meaningful action in your product needs to be reachable through an API, MCP tool, or CLI command. Schemas need to be machine-readable. Errors need to be parseable. Permissions need to be inherited from the human the agent is acting for. This is where Salesforce, Microsoft, and a growing number of vertical SaaS players are investing right now.

The governance layer. This is the one most teams haven't started thinking about, and it's the most interesting. When an agent is about to act on a user's behalf, the user needs a preview of what it plans to do, a confirmation flow for irreversible actions, and a clear log of what happened. The governance layer is the human in the loop, surfaced as a product feature, not buried in admin settings.

Three layers. One product. Most teams are still building one.

The pricing question this forces

If the agent becomes a user, what do you charge? Per-seat pricing assumed a human consumed the licence. An agent might do the work of fifty seats while occupying zero. Microsoft has already started shifting Dynamics customers to a mix of seats plus consumption credits, with around 60% of Dynamics service customers now buying usage-based credits. Microsoft also moved GitHub Copilot to usage-based pricing, explicitly aligning what they charge with what the customer consumes.

This is not the death of seat-based pricing. It's the start of hybrid pricing, where seats cover platform access and consumption covers agent-driven work. The hard part, and where I'd be spending CFO time right now if I were on your board, is protecting gross margin when agent usage can spike unpredictably. SaaS economics assumed flat-rate consumption per seat. Agents break that assumption.

The practical answer is simple to state and hard to implement. If you don't have a unit of work in your product that you can measure and charge for (a resolution, a workflow completed, a document processed, a lead qualified), build one before your competitors do. Once your competitor is charging per outcome and you are charging per seat, the comparison gets very uncomfortable very quickly.

The mobile-first analogy is exact

In 2010, every software company had a website that worked beautifully on a 1280-pixel monitor and barely worked on a phone. Then mobile traffic crossed a threshold, and the companies that hadn't rebuilt for touch, latency, and a smaller viewport spent the next five years losing ground to ones that had. The phrase "mobile-first" became shorthand for "rebuild your product around how people actually use it."

We are about to repeat that, with agents. The companies that get there first will look the way responsive-design pioneers looked in 2013. The companies that wait will rebuild under duress with their customers already comparing them to a faster competitor.

The good news is that the work is more tractable than mobile was. You don't need to redesign for a new viewport. You need to expose what already exists, structure it for machine readers, and add a governance layer most users will value even when they're using your product directly.

What I'd do in your position

If you run a B2B product, I'd put four things on the next quarterly roadmap:

Audit your API coverage. Map every meaningful user action in your product. For each one, mark whether it is reachable through your API. The honest number is rarely above 40% for products older than five years. That gap is your roadmap.

Build an MCP surface. Don't rebuild your API, wrap it. MCP is the emerging standard for how agents discover and use tools, and the integration cost is low compared to the strategic optionality it buys you. Start with the five actions agents would most plausibly want to take in your product.

Design the preview and approval flows. What does it look like when an agent is about to act inside your product? Where does the user see it? How do they cancel? How do they review what happened? This is product design work, and it is currently being skipped by every team I look at.

Pick a unit of work to charge for. Resolutions, workflows completed, documents processed, leads qualified, transactions executed. Agents make per-seat pricing leak value. The companies that figure out the right unit early will protect margin. The ones that don't will find themselves negotiating discounts against unbounded usage.

The board reframe

For founders and operators reading this, the simplest reframe is: your competitive moat for the next decade depends on how many of your users are software. If the answer is "almost none," your product is being designed for a market that is shrinking relative to the one being built for agents. If the answer is "more than we expected," you are early to a shift that most of your competitors are still treating as marketing language.

Headless software is not a feature. It is a posture toward where computing is going. The shape of your product is the most strategic decision you'll make this year, and the window to make it is shorter than the time it took most of you to ship a mobile app.

If you'd like to talk through what an agent-addressable product surface would look like for your business, get in touch. I've spent the last decade building production AI systems and the platforms underneath them, including the agentic insurance automation work where the customer's agent had to call our system, not the other way around. The patterns travel.