Code and Theory cut prototyping time by 75% with Vercel v0

Digital agency Code and Theory has replaced traditional wireframes and technical documentation with code generation in Vercel v0. The result: time to first prototype dropped by 75%, and deployment timelines shrank by 50–75%.

Who are Code and Theory

Code and Theory is an American digital agency that works across strategy, design, and engineering. Its client roster includes Microsoft, Amazon, NBC, and dozens of other Fortune 500 companies. This isn't a startup experimenting with new tools. It's an established organization with mature processes and large clients who expect predictable timelines.

Until recently, the agency's workflow looked like the industry standard. A client describes what they need, the team goes away, and some time later comes back with wireframes. Then comes a PRD (product requirements document), then alignment with developers, then a first prototype. Every handoff between stages added delays and risked losing the nuances of the original request. The cycle could take weeks. For an agency running dozens of projects in parallel, that meant constant pressure on deadlines.

How v0 changed the workflow

Vercel v0 generates user interfaces from text descriptions. You describe the interface you want in plain words, and v0 produces working code, typically React components you can run, demo, and edit right away. Not a diagram full of boxes. Not a Figma mockup. Working code.

Code and Theory built v0 into its client engagement process so that the prototype appears during the meeting, not after it. The results went well beyond speeding up a single stage:

• Time to first prototype dropped by 75%
• Time from project kickoff to deployment fell by 50–75%
• Wireframes and PRD documents have effectively fallen out of use
• Product, engineering, and go-to-market teams work in a single flow
• A client brief becomes a working prototype in minutes, right on the call

Crucially, every team — product managers, designers, engineers — now works from the same live artifact instead of separate documents at different stages.

How the client meeting changed

It's not just the speed that changed. The nature of the client meeting itself changed.

Before: the client describes an idea, the agency goes away, and a week later comes back with diagrams and boxes for sign-off. Then another round to refine requirements, then another for engineers to assess feasibility. Only after all that did a live interface appear. It was a weeks-long chain in which every link could distort the original request.

Now the team drafts a prompt in v0 during the call and shows a working prototype a minute later. Instead of a diagram labeled "button goes here," the client sees a real interface they can interact with. Iteration happens in real time. Approvals shrink naturally, because everyone is looking at the same thing.

What this means

The Code and Theory case is one of the first publicly documented examples of a major agency systematically rebuilding its production process around prompt-to-code — not as an experiment, but as standard operating practice.

If a 75% speedup is reproducible in other teams, the entire traditional design cycle comes into question: wireframes, PRD documents, multi-stage approvals. The tool turns every client meeting into a collaborative development session.