How Vercel Uses Notion AI Agents to Scale Launches 35% Faster
Vercel's launch database grew to include dozens of properties manageable only via a form-based intake, while agent prompts were stored in GitHub, requiring engineering involvement and full deployments to update, making iteration slow and excluding non-engineers from adjusting business logic.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Ship agent creates launch entries
Ship, a Custom Agent in Slack, accepts a name, date, or link from a Vercelian and creates a Launch Calendar entry by inferring missing details.
Vercel achieved 35% faster shipping and teams reclaim up to nine hours weekly per employee, with 89% of employees reporting increased confidence in shipped product quality. The agent prompt iteration cycle dropped from roughly a business day to five minutes.
What failed first
A Notion form with conditional logic reduced friction but remained form-based. Agent prompts buried in GitHub required pull requests, reviews, and full deployments for any behavior change, blocking non-engineers from updating business logic.