# How Featured's users make 100K media pitches per month on Vercel

Source: [Vercel](https://vercel.com/blog/how-featureds-users-make-100k-media-pitches-per-month-on-vercel)  
Feed7 permalink: https://feed7.dev/p/how-featureds-users-make-100k-media-pitches-per-month-on-vercel-1s0b8vk  
Published: 2026-09-11T04:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

A three-engineer team consolidated model routing, long-running agent jobs, and deployment on Vercel while serving 100,000+ users. The case study shows where managed abstractions can remove operational work.

## Source Summary

Featured supports **100,000+ users** across three brands with three engineers. It migrated **374 Sanity sites** from Elastic Beanstalk, routes model traffic through AI SDK and AI Gateway, and moved long-running jobs to Workflow SDK.

## Practical Implication

For a small agent team, the useful pattern is consolidation: standardize model calls, make provider changes configuration-level, and put work that outlives a request into durable workflows. Featured also made chat primary after users favored conversation over dashboard navigation.

## Agent-Ready Context

Featured supports **100,000+ users** across three brands with three engineers. It migrated **374 Sanity sites** from Elastic Beanstalk, routes model traffic through AI SDK and AI Gateway, and moved long-running jobs to Workflow SDK.

For a small agent team, the useful pattern is consolidation: standardize model calls, make provider changes configuration-level, and put work that outlives a request into durable workflows. Featured also made chat primary after users favored conversation over dashboard navigation.

This is a vendor-authored case study, not a cost or reliability comparison. Its **17-model** setup and **100,000+ monthly pitches** show operating scale, but the material provides no latency, failure-rate, or migration-cost data.

## Connected Context

Feed7 judgment across 757 accumulated Signals:

This turns gateway abstraction and durable workflows from product features into an operating pattern used by a three-engineer team across hundreds of sites and many models. It reinforces consolidation as a way to limit integration burden at scale, while narrowing the evidence to feasibility: without cost, latency, failure, or migration data, it does not establish that the architecture is efficient or superior.

- [How Searchable ships customer-requested features in 30 minutes on Vercel](https://feed7.dev/p/how-searchable-ships-customer-requested-features-in-30-minutes-on-vercel-1woiy7v) — Searchable independently reinforces the implementation benefit of keeping model swaps behind AI SDK and Gateway, though its evidence concerns delivery speed rather than Featured’s operating scale.
- [Introducing the Agents API](https://feed7.dev/p/introducing-the-agents-api-0550svl) — The managed Agents API addresses the same need for persistent, orchestrated work that Featured moved into durable workflows, but places more of the runtime inside a hosted agent service.
- [The Agent Behind the Curtain: Building the Oz Cloud Agent Platform — Safia Abdalla, Warp](https://feed7.dev/p/the-agent-behind-the-curtain-building-the-oz-cloud-agent-platform-safia-074nn9s) — Warp’s separation of runtime, harness, artifacts, and orchestration provides a broader portability model for the consolidation pattern Featured applies through shared model routing and workflows.
- [How Tailscale built a customer-facing model router on AI Gateway](https://feed7.dev/p/how-tailscale-built-a-customer-facing-model-router-on-ai-gateway-186s3tu) — Tailscale adds the identity, retention, and execution-isolation controls that become implementation requirements when Featured’s shared gateway pattern is used for customer-facing agents.

## Context Map

- Layer: infra
- Domains: coding
- Topics: gateways, cloud-agents, agent-sdks

## Uncertainty

- This is a vendor-authored case study, not a cost or reliability comparison. Its **17-model** setup and **100,000+ monthly pitches** show operating scale, but the material provides no latency, failure-rate, or migration-cost data.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.