Vercel has been part of Zapier's stack since the company adopted it for web experiences, and the relationship has widened as teams found new uses for it. The platform now supports work in engineering, partnerships, and marketing, and Zapier describes the common driver as speed with security guardrails already in place. The outcomes span interactive partner prototypes, internal tools built by people without deployment backgrounds, and the isolated execution behind AI workloads.

Shrinking partner prototypes from weeks to a single sitting

Zapier's Powered by Zapier team turns signed partnerships into product, helping SaaS and AI companies embed Zapier's automation directly into their own tools. Prototyping for these collaborations used to drag: each one required screenshots, design time, and frontend resources, and weeks could pass before a partner saw something clickable. With v0, the team produces a multi-view interactive prototype of an embedded Zapier experience inside the partner's product in under two hours.

"In two hours using v0, I can now create a fully clickable prototype with 10+ different views. That just wasn't possible before."

Michelle ChuBackend Engineer @ Zapier

Chu comes from backend development rather than frontend engineering or design, and v0 means she no longer has to coordinate a separate design and frontend effort for every partner conversation. Partners click through the flow, circulate it internally, and use it as an implementation blueprint alongside the API documentation.

Internal tools from non-deployers

In marketing, Joe Stych wanted to consolidate scattered team knowledge. A former product marketer who became an agentic go-to-market engineer, he had never worked out of a Git repository or deployed an application before building Marketing Hive at an internal hackathon. The Hive collects positioning, messaging, personas, and competitive intelligence, so it couldn't simply be shared as a link.

"The Hive holds our positioning, personas, and competitive intel, so I couldn't just send people a link. On Vercel it was behind our SSO from the first deploy, so I could share it without exposing it."

Joe Stych, Senior Lead, Agentic GTM at Zapier

Zapier's data and security teams had already signed off on Vercel, so Stych deployed through the company's approved internal tooling environment with access gated behind Zapier single sign-on. He develops in Cursor and keeps code and source material in GitLab, where changes trigger Vercel builds and deployments; an update that goes wrong can be undone with an instant rollback of the deployment. The first versions of three internal applications each took roughly a day, and within about two months the hackathon project had become production software used across marketing.

Briefings, dashboards, and a sales coach

Marketing Hive stores the knowledge; Marketing OS applies it. More than 60 marketers get a daily Slack briefing and a dashboard summarizing what changed across marketing: one update per team, a win worth noting, and progress against goals. Instead of assembling the same picture from separate channels, each marketer starts from the briefing.

"The first five minutes of your day, you need to look at the Marketing OS update," says Dan Slagen, Zapier's CMO. Readers flag what they found useful, which helps Stych order improvements, and the briefings feed discussion in a company-wide marketing channel.

He is also building a sales coaching application that pulls account context and industry messaging together before a call, then reviews the Gong recording afterward to surface what worked and suggest changes to the talk track. On the internal applications, Stych verifies reported numbers and the evidence behind claimed insights. Positioning decisions stay with people, and he says further safeguards will precede any agents publishing without human review.

Model routing and sandboxed execution

A separate Zapier team uses AI Gateway to route requests to AI models on behalf of customers using Zapier products.

"AI Gateway gives us one endpoint for every model provider. When the best model changes, we change with it. No rebuilt integrations, no migration projects."

Ryan AndersonHead of Product Marketing @ Zapier

One shared endpoint means an application can swap or add models without maintaining an integration per provider. Failover reroutes requests when a provider can't serve them, and unified reporting shows usage across providers in one place. On the execution side, Zapier created 3.3 million sandboxes in a single month to isolate the code running behind its AI workloads.

Where the pattern spreads next

Vercel's role at Zapier now covers both the software the company runs for customers and the tools employees build for each other. Marketing is the clearest template: other teams are beginning to borrow the approach, with a goal of more such versions across the company and possibly a Revenue OS for customer-facing teams, each built by someone close to the problem. Trust comes first, which is why Stych still checks reported numbers and supporting evidence and why safeguards precede unreviewed agent publishing.