I've seen too many AI startup stories end in the same tragedy.
They spend two years building a beautiful product: an accounting AI, a legal AI, a medical AI. Workflow, interface, domain logic, accountability—all bundled together. Users find it easy, the company collects revenue, everything looks great.
Then foundation models leap forward, general AI agents arrive, and yesterday's moat becomes a wall overnight—not a wall against competitors, but a wall trapping the company itself.
At this point, some start preaching a "headless" transformation: hand workflows and interfaces over to agents, expose domain expertise as callable services.
Sounds trendy, right?
But the paper I'm discussing says: "going headless" may be a trap, and most companies are jumping right in.
What Is "Going Headless"?
Vertical AI companies provide AI solutions in a specific domain—law, medicine, accounting. Their traditional model is bundling: packaging workflow, interface, and domain logic into one application. Benefits:
- Simple UX: one piece of software solves an entire domain
- Clear accountability: when something breaks, users know whom to blame
- Coase's theory of the firm: firms exist because market transactions carry costs
- Eisenmann et al.'s platform envelopment framework: platforms gain power by enveloping competitors' products, even as interoperability improves
- Teece's complementary assets theory: durable value lies in assets highly complementary to core capabilities
But in the foundation-model era, general agents can book flights, answer email, and write code. Why not do your books, review contracts, read scans?
So the thinking goes: expose "professional capability" as APIs and let agents call them. That's the headless idea. The theory is beautiful. Reality is cruel.
A Dangerous Conflation: Interface Boundary vs. Accountability Boundary
The paper's core insight: the interface boundary (how users interact with the system—web, app, API) and the accountability boundary (who is responsible when things go wrong) are not the same thing.
Headless advocates treat removing the app as a mere technical decision—but in practice they may be moving the accountability boundary too, and that shouldn't happen.
The paper gives a vivid example: accounting software makes an error, a tax filing goes wrong, a company collapses. Who is responsible? If the software vendor is accountable, users know whom to seek redress from. But if the vendor went headless—exposing expertise as an API called by a general agent—who is liable? The vendor? The agent developer? The user?
Once accountability blurs, no one is truly accountable. That is the gravest danger of going headless.
An Analytical Framework: Coase, Teece, and Platform Envelopment
The paper combines three classic theories:
Orchestrators running on open protocols gain envelopment power—even as technical interoperability improves. And durable value concentrates in "co-specialized accountability assets": professional sign-off authority, regulated workflows, evidence chains, trusted record systems.
These accountability assets—not algorithms, not models—are vertical AI's real moat: the promise and track record of someone taking responsibility when things go wrong.
A Three-Part Taxonomy: Component, Integrated Platform, Dual-Track
The paper classifies firms not by industry but by task–accountability regime:
1. Component: provides professional capability with no accountability attached. E.g., a tax-calculation API that does not guarantee your filing passes an audit. 2. Integrated Software Platform: bundles workflow, interface, and domain logic, and bears full accountability. When problems occur, users go to the platform. 3. Dual-track: runs both a component business and an integrated platform, strictly separated by brand, legal entity, and accountability structure.
The key: which category you belong to is determined not by what you do, but by how much accountability you are willing to bear. An accounting AI that goes headless and becomes a pure API supplier slides from category two to category one—shedding accountability and gaining faster expansion, but losing its moat.
Rule Debt: The Hidden Cost
The paper also introduces Rule Debt: when business rules and professional standards migrate from governed systems into prompts and agent instructions, future governance, maintenance, and liability burdens accumulate like debt on customer organizations.
In plain terms: when accounting software computes your taxes, the logic lives in a regulated system—audited, compliance-checked, logged. If the logic becomes a prompt invoked by a general agent? Can it be modified? Can the agent "misunderstand" it? Who reviews its correctness?
These questions don't disappear—they're transferred to customers who lack the professional capacity to handle them. Superficially you "empower" clients; in reality you offload burdens onto them.
Four Principles
1. Decompose by accountability, not by interface. Before deciding what to expose, ask: where does accountability for this lie? If it's yours, don't go headless with it. 2. Invert the edge, retain the core. Let agents take over peripheral workflows, but hold tightly to the accountable core. 3. Position rule-debt reduction as value. If your integrated platform spares clients rule debt, that's what it's worth. 4. Avoid dependence on a single orchestrator. Don't expose all your expertise to one agent—or you become its vassal.
A Parting Thought for Founders
Going headless is seductive—modern, open, future-facing. But what I see is founders chasing a trend while abandoning their most valuable asset: not technology, not data, but the promise that someone answers when things go wrong.
An industry where no one is accountable becomes an industry no one dares to use.
Why does medical AI advance slowly? Not because the tech fails, but because no one will be the defendant when AI errs. Why does accounting AI struggle to spread? Not because AI isn't smart enough, but because no firm will sign a tax filing and absorb the fines.
Accountability isn't a burden—it is the moat. Before going headless, ask yourself: when this goes wrong, who is responsible?
If you can't answer, you probably shouldn't do it.
References
1. Hydari, M. Z., & Muzaffar, F. (2026). *Going Headless? On the Boundaries of Vertical AI Firms*. arXiv:2605.17812. 2. Coase, R. H. (1937). The nature of the firm. *Economica*, 4(16), 386-405. 3. Eisenmann, T., Parker, G., & Van Alstyne, M. (2006). Strategies for two-sided markets. *Harvard Business Review*, 84(10), 92-101. 4. Teece, D. J. (2010). Business models, innovation strategy, and the catch-up problem. *Strategic Management Journal*, 31(2), 151-174. 5. Zuboff, S. (2019). *The Age of Surveillance Capitalism*. PublicAffairs.