Rethinking prototyping, requirements, and project delivery at Code and Theory

Code and Theory is a digital-first creative and technology agency that blends strategy, design, and engineering. With a team structure split evenly between creatives and engineers, the agency builds systems for global brands like Microsoft, Amazon, and NBC that span media, ecommerce, and enterprise tooling.

With their focus on delivering expressive, scalable digital experiences, the team uses v0 to shorten the path from idea to working software.

“We’ve seen lots of products hit the market (Replit, Lovable, etc) but none of them were enterprise-ready engineering tools. Vercel created v0 with a purposeful vision to make the highest quality outputs – and being the maintainers of Next.js definitely aided in that goal.We’ve seen lots of products hit the market (Replit, Lovable, etc) but none of them were enterprise-ready engineering tools. Vercel created v0 with a purposeful vision to make the highest quality outputs – and being the maintainers of Next.js definitely aided in that goal.”

Josh Wolf, Director of Technology at Code and Theory

What started as a prototyping tool is now central to how they concept, refine, and build internal and client-facing web applications.

Prompt-driven workflows

Code and Theory uses v0 to bypass the traditional flow of strategy documents, wireframes, and static mockups. Instead, teams go straight from prompt to code. Working MVPs replace decks and features are tested, not explained.

This shift shortens the feedback loop and turns early concepts into production UI faster. Teams use v0 to:

• Replace requirement documents with working interfaces

• Visualize features for internal and client reviews

• Rapidly expand on ideas through live iteration

In client engagements, teams use prompt iterations to refine ideas and rapidly generate high-fidelity interfaces that can be evaluated on the spot.

“Where developing web apps used to range between 2-12 months depending on what we were looking to achieve, we are now operationalizing v0 and bringing those deployment horizons down by 50-75%. Increasing the speed to market means we can provide value to our clients faster and focus on how we optimize the apps to continue to deliver better results.Where developing web apps used to range between 2-12 months depending on what we were looking to achieve, we are now operationalizing v0 and bringing those deployment horizons down by 50-75%. Increasing the speed to market means we can provide value to our clients faster and focus on how we optimize the apps to continue to deliver better results.”

David DiCamillo, CTO at Code and Theory

Open-ended tooling for cross-functional teams

v0 works out of the box for every discipline. Designers, strategists, and engineers all use the same interface. Prompting becomes the shared entry point without any technical ramp-up, handoffs, or bottlenecks.

This accessibility has surfaced ideas that previously never made it into a sprint. People who aren’t in the codebase every day are now contributing working prototypes, exploring edge cases, and generating unexpected directions from vague prompts.

The structure is lightweight enough to allow for experimentation, but grounded enough to feed directly into production workflows.

Rethinking how teams deliver work

v0 removes the lag between idea and implementation, meaning teams spend less time describing functionality and more time delivering it.

Generated apps are versioned through GitHub, tested with the agency’s existing QA stack, and deployed securely through Vercel. Data sources are integrated formally, design systems are enforced, and outputs are optimized for real use.

The result is faster delivery, more creative exploration, and better clarity across teams.