SOURCE

The AI Agent Every Company is About to Build | Vercel CEO Guillermo Rauch

Properties1
tagsvercel, ai-agents, eve, god-agent, agent-orchestration, openclaw, ai-assisted-development, riley-brown, guillermo-rauch
AUTHOR
Guillermo Rauch (guest); Riley Brown (host)
PUBLISHED
2026-08-06
ORIGINAL
view original

6 min read

The AI Agent Every Company is About to Build

Guest: Guillermo Rauch (Vercel CEO) · Host: Riley Brown | Published: 2026-08-06 | Source: transcript (54:22, 98K views at ingest)

Summary

Riley Brown interviews Vercel CEO Guillermo Rauch about the internal company agent almost 1,000 employees use, and Eve, the framework Vercel shared from that build. Agents have two killer apps: coding agents (agentic engineering down to vibe coding via v0/Lovable) and a “run your company better” brain (knowledge base + analytics + project management). ChatGPT/Codex are a taste; the new operator job is to create, tune, optimize, and disseminate your own agents. That layer is the firm’s IP.

Vercel’s agent is V (@V in Slack): a router/orchestrator (Star Trek / Jarvis — one ambient interface) that delegates to a content agent, D0 (data warehouse), support, docs, plus Codex and v0. It began as customer-facing @Vercel support; they split that from the company-running agent. Dogfood first, then productize. Building V was hard enough that they shipped Eve (eve.dev) — “what Next.js/React did for the web,” for owning an agent.

OpenClaw informed Eve: soul.md (the agent is yours, not Anthropic’s Claude), a computer of its own (Mac Mini phenomenon — space + tools, but dangerous), and a heartbeat for proactivity. Eve’s primitive is a folder: instructions.md, tools/ (e.g. wordpress.ts), skills/ as markdown (e.g. contentwriting.md after an intern ships “Claude slop”), plus a channel (Slack/WhatsApp/Telegram/iMessage). Runtime is serverless (hibernate when idle). Security is the actual job: tools, human-in-the-loop, identity, ACLs, audit trails. Vercel Connect wires 100+ systems as events. Slack thumbs-up/down feeds nightly self-improvement; Eve wants evals the way web apps want unit tests (accuracy and personality — V was once “too verbose”).

God-agent vs. team-of-agents: Rauch is UX-first — one @V, many capabilities, identity deciding who can do what (intern cannot ship WordPress to prod). Meta-work is not writing the blog post; it is improving the skill. Start: eve.dev, connect a chat medium, pick one toil task. Vercel’s changelog used to be engineer↔marketing grind; now one Slack thread, rewritten to benefit / cost / how to get it (they cite shaving 7 seconds off deploy).

Model layer is agnostic (AI SDK + AI Gateway). Fast Slack work → Grok 4.5 or GLM; night jobs → more reasoning or a model consortium. Open-weight competition is the speed story (GLM 5.2 got a 4×-faster variant in days). Closing thesis: own your intelligence like you own your domain — Claude-in-Slack is their agent. Before you build a website, you will build the agent that helps you build the company.

Key Claims

  • Two killer apps of agents: coding agents and a company-brain agent (KB + analytics + PM). (Rauch)
  • Competitive edge = ability to create, tune, optimize, and disseminate internal agents — ChatGPT is a taste, not the system. (Rauch)
  • Vercel V (~1,000 employees, Slack @V) is a god-agent UX (router) over specialized sub-agents (content, D0/data warehouse, support, docs) with identity/ACLs. (demonstrated internally; not independently audited)
  • Eve = the framework they used to build V, shared as the Next.js analog for owning an agent (eve.dev). Folder primitive: soul + tools + skills + channel. (product)
  • OpenClaw unlocks Eve copied: soul.md, give the agent a computer, heartbeat/proactivity; sandbox + serverless hibernate for safety/cost.
  • Difference between assistant and agent: an agent does things. Hard part is securely connecting systems, not the POC. Vercel Connect = 100+ systems as events.
  • Self-improvement loop: Slack thumbs-down → nightly aggregation → agent proposes skill updates; write evals (accuracy + personality). Humans stay in the loop.
  • Before the website, build the agent that helps you build the company. (prediction)
  • Model-agnostic routing: fast/interactive vs. slow/accurate (batch/“spot market for intelligence”). Open-weight inference competition is collapsing latency (GLM 5.2 4×-fast variant in days).
  • Own your intelligence like you own your domain; vendor Slack bots are lock-in. (positioning, commercial)

Notable quotes

“The future of what you would consider to be your intellectual property at the company or your edge against competitors is the ability to create, tune, optimize and disseminate these agents internally.”

Why citable: Recasts the company OS as owned agent infrastructure, not a ChatGPT seat — the web-dev thesis of this episode.

“What I believe will happen in the future is that even before you build a website, you’re going to build that agent that’s going to help you build a company.”

Why citable: Direct hit on this wiki’s web-dev pillar (sites as the first artifact) — Rauch says the first artifact becomes the agent.

“It’s not about having Claude in your workspace. It’s about having an intelligence of your own… I liken it to the web because the web was all about I own my domain name.”

Why citable: The anti-lock-in closer, and the bridge from Vercel-the-hosting-company to Vercel-the-agent-runtime.

Connections

Entities mentioned: Vercel, Claude, Claude Code, ChatGPT, Next.js, WordPress · NEW Riley Brown, NEW Guillermo Rauch · OpenAI Codex, v0, Lovable, OpenClaw, Slack, Anthropic, Kimi, GLM, Grok, Stripe (minor) Concepts referenced: AI-Assisted Development (coding agents, vibe coding, verification/evals, CLAUDE.md-like soul files) · NEW Agent Orchestration (god-agent router, sub-agents, skills/tools/permissions, events, self-improvement) · Web Architecture & Scalability (serverless hibernate, identity, ACLs)

Contradictions / Tensions

  • God agent vs. team of agents: Riley’s operator audience wants separate marketing/finance agents (data-isolation instinct). Rauch insists on one ambient UX that routes, with identity — not a swarm the user addresses. This is the design fork for Agent Orchestration.
  • vs. Paste This Into Claude, It'll Make You Build 10x Faster (6 Claude Code power phrases): Marchese launches parallel sub-agents to avoid anchoring; Rauch hides multiplicity behind one orchestrator. Complementary at different layers (dev-loop vs. company-OS), but they pull UX in opposite directions.
  • vs. Why Your AI Offer Isn't Selling, and How to Fix That: both want auto-routing (Jones: 95% open models; Rauch: AI Gateway / task-appropriate model) and warn that tool access ≠ org design. Jones sells storytelling to SMBs; Rauch sells own-your-agent infrastructure to companies that can staff a V team.
  • Commercial bias: Eve, AI SDK, AI Gateway, Vercel Connect, and “deploy on Vercel” are the product. “~1,000 employees use V” and “hundreds of millions of revenue depend on this agent” are CEO claims. Model bake-offs (Kimi vs. Opus 4.8 cybersecurity) are unsourced.

Notes

Highest-leverage web-dev adjacent source in this batch: takes Vercel from “edge host / Next.js company” to “company-agent runtime,” and gives AI-Assisted Development an org-scale layer (soul files, evals, skills, events) above Marchese’s personal Claude Code phrases. NEW entities to create later: riley-brown, guillermo-rauch. NEW concept: agent-orchestration (this interview is the strongest definition so far — god-agent router + skills/tools/permissions + evals). Backfill: Rauch’s 2026-08-02 X post on @v; eve.dev docs; OpenClaw soul.md.