How Speakeasy uses v0 to ship faster with features like Figma import and custom Tailwind config.

Speakeasy specializes in building developer-focused SDKs—to help developers build their products. They adopted v0 to bridge the workflow from design to code, using it to accelerate rapid prototyping and reduce implementation time.

Speakeasy's product is highly technical, and their team embraces a "design as code" philosophy. Without v0, this approach wasn’t straightforward. While Figma is used for initial design explorations, static pixel designs weren't enough to convey new ideas or get buy-in. Design at Speakeasy focuses on movement, behavior, and interaction—how a product feels, not just how it looks. Given the need for quick iteration, meticulously designing every feature in Figma wasn’t practical.

Link to headingUsing v0 to iterate on experiences faster

v0 helps the whole Speakeasy team quickly explore ideas, even if they’re not designers or engineers. v0 leverages AWS Bedrock's foundation model infrastructure to power its AI-driven code generation capabilities, enabling developers to rapidly prototype and build full-stack applications through natural language prompts.

They use v0 as a dynamic design descriptor, a way to share interactive prototypes and demonstrate feature behavior. Some designs start in Figma and are imported into v0, but many concepts are designed directly in v0. This allows, designers and engineers collaborate in real time, refining ideas without the friction of design-to-code translation.

For instance, the initial concept for the Terminal Preview in the Speakeasy dashboard was created in a single day using v0. This rapid prototyping allowed the team to focus on refining interactivity and user experience rather than translating static designs into code.

The reason I jumped to v0, was a bias towards code. It meant less time having to redo ideas in Figma. When it comes to getting ready to ship, I was already in the right medium. I saved whatever time it would have taken me to translate Figma to code.

Faraz Khan, Design Engineer

A key element of their workflow is a custom Tailwind configuration, which v0 users use to build and style components according to their design system. For example, the font weights and colors used in their Terminal Preview feature were all defined and used within v0.

Everyone from designers to backend developers at Speakeasy use v0. The team often shares Loom recordings of their v0 prototypes to communicate design ideas effectively. In fact, the phrase “Share a v0” has replaced lengthy Slack discussions and meetings.

By prototyping directly in a code-native environment, Speakeasy accelerates iteration, improves product quality, and keeps design and engineering in sync. For them, v0 isn't just a tool—it’s how they build better developer experiences.