← Back to posts

AI Super-App or Vertical Agent: Who Owns the First Intent?

General assistants own frequency, identity, and distribution; vertical agents own workflow, responsibility, and domain data. The likely outcome is a negotiated split between gateway and delivery layer.

The AI super-app thesis is compelling: one assistant holds identity, memory, payments, and a tool ecosystem, and the user only needs to state a goal. A high-frequency interface can distribute new capabilities to a vast audience almost instantly.

Vertical agents derive power from depth. Legal, clinical, design, sales, and research work are not generic prompts with different vocabulary. Each field has its own data structures, approvals, liability, and acceptable error boundaries.

The two products therefore compete at different layers. A super-app is an intent router: it recognizes a goal, chooses a service, and carries context across domains. A vertical agent is a contractor: it uses specialist tools, produces the deliverable, and supplies evidence for review.

Platforms will move downward through apps, connectors, and built-in tools. Memory and payments increase switching cost. Yet every regulated or complex domain brings local workflows, professional responsibility, and data separation that erode some economies of scale.

Vertical products will move upward by adding general conversation, cross-project memory, and third-party tools. Low-frequency specialists still struggle to own a consumer gateway, making distribution through platforms, channel partners, or incumbent SaaS attractive.

A two-layer market is the most plausible equilibrium. General assistants own consumer intent, identity, and discovery; vertical agents own professional context, execution, and accountability. Standards shape interoperability, while control of customer relationships determines profit allocation.

Startups should ask whether they own a delivery loop that a broad platform cannot scale cheaply: proprietary workflow, trusted data, expert feedback, outcome guarantees, or regulatory standing. Feature differentiation is absorbable; a defensible responsibility boundary is much harder to copy.

Users ultimately care less about which layer performed the task than whether context survived, authority stayed bounded, and the outcome can be accepted. The winner will make the contract between gateway and specialist feel invisible without making it unaccountable.

— End —