How to Use v0 for Prototyping

Generate a UI component from a feature description

Why it matters for PMs: This is the core v0 workflow for PMs. Instead of describing a UI in words and waiting for a designer to mock it up, you get a visual artifact in seconds. Use it to show engineers exactly what you mean, not what they think you mean. The component is production-grade React, so it's hand-off-ready, not just a picture.

Create a [component type: e.g. settings panel / onboarding checklist / feature comparison table] for a [product type] SaaS app. It should include: [list key elements]. Use a clean, modern design with [specify: e.g. a sidebar layout / card-based grid / tabbed sections]. Make it responsive.

• Be specific about the component type — 'a three-column pricing comparison card' beats 'a pricing page.' v0 generates better components from precise descriptions.
• After the first generation, iterate with natural language: 'Add a toggle switch for the middle plan', 'Make the CTA button wider', 'Use a darker header.'
• Export the code and paste it into a GitHub gist or Storybook for your eng team — the component uses standard React + Tailwind, so it drops into any Next.js project.

Prototype a landing page for a new feature

Why it matters for PMs: PMs routinely need landing pages for beta features, internal tools, or new product launches. v0 collapses the brief-to-mockup cycle from days (designer backlog) to minutes. You get a page you can show to stakeholders for sign-off before any engineering work begins.

Build a landing page for [feature name], a new [one-line description]. Target audience: [who]. Key value props: [3 bullet points]. Include: hero section with headline + CTA, 3 feature highlight cards, a testimonial section, a 4-item FAQ, and a final CTA band. Use a [color scheme / brand vibe] aesthetic.

• Include your real headline and subheadline copy — v0 will place it correctly and you avoid the generic AI-generated marketing speak.
• Ask v0 to 'add a sticky nav bar with links to Features, FAQ, and Pricing' for a more realistic prototype.
• Share the v0 preview link directly in a Slack thread or Loom video instead of screenshotting — stakeholders can interact with it.

Build a dashboard mockup from a metrics list

Why it matters for PMs: Dashboard design is one of the hardest things to communicate in words. PMs say 'I want to see churn by cohort' and engineers interpret it six different ways. A v0 dashboard mockup eliminates ambiguity — everyone sees the same layout, chart types, and information hierarchy before a single API is wired up.

Create a product analytics dashboard for a [product type] SaaS. Include these KPI cards at the top: [list 4 metrics, e.g. MRR, Active Users, Churn Rate, NPS]. Below that, add: a [line chart] showing [metric] over time, a [bar chart] comparing [segments], and a data table with columns [list columns]. Add a date-range filter dropdown at the top right.

• Specify chart types explicitly — 'a stacked area chart for revenue by plan' is clearer than 'a revenue chart.'
• Ask for 'a filter sidebar with checkboxes for [segment dimensions]' to prototype the interactive filtering your users will expect.
• Use this mockup in your PRD's 'UI mockup' section instead of a wireframe — it's interactive and looks real.

Create a user flow prototype with multiple screens

Why it matters for PMs: Single-screen mocks don't capture flow. PMs need to show how a user moves from step A to step B to step C — the transitions, the state changes, the decision points. v0's component-by-component approach lets you build a full flow prototype that stakeholders can click through, which surfaces flow problems before you commit to engineering.

I need a [N]-step [flow name: e.g. onboarding wizard / checkout flow / settings setup] for a [product type]. Step 1: [description]. Step 2: [description]. Step 3: [description]. Generate each step as a separate component with a progress indicator at the top showing the current step. Include Back and Next buttons.

• Generate each step in a separate v0 conversation for cleaner, more focused output — then combine them in a Next.js project.
• Add 'include form validation errors for [specific fields]' to prototype the error states, not just the happy path.
• Ask for 'a summary/review screen as the final step' — this is a common UX pattern that's easy to forget in a verbal spec.

Mock up a competitor's feature for comparison

Why it matters for PMs: Competitive feature analysis often stops at screenshots because PMs can't produce visual alternatives. v0 lets you go from 'they built this' to 'here's how we'd build it better' in minutes. Use it in competitive review docs, PRD rationale sections, or stakeholder presentations to make the case for a feature with a visual, not just words.

Recreate this UI layout: [describe or paste screenshot of competitor's feature]. Now modify it with these improvements: [list 3-4 specific UX improvements, e.g. 'add inline filtering', 'simplify the header to 2 actions instead of 5', 'use a card layout instead of a table']. Keep the same information density but make it cleaner.

• Use v0's image upload feature — paste a screenshot of the competitor's UI directly and ask it to 'recreate this layout.'
• Don't copy the competitor's exact copy or branding — ask v0 to 'use placeholder text and a neutral color scheme.'
• Generate a 'before' and 'after' version and put them side-by-side in a Loom video for your team — the visual delta makes the case for your design direction.

Generate a form + validation UI for data collection

Why it matters for PMs: Forms are the backbone of SaaS products — signup, settings, intake, feedback. PMs spend hours describing form behavior in PRDs ('if the user enters an invalid email, show a red message below the field'). v0 turns that description into a working form in seconds, with all the validation states rendered. It's a spec and a prototype in one.

Create a [form type: e.g. customer feedback form / lead intake form / feature request form] with these fields: [list fields with types: text, dropdown, textarea, checkbox, radio]. Validation rules: [e.g. email must be valid, rating is required, max 500 characters for the textarea]. Show inline error messages below each field. Use a single-column layout with a submit button at the bottom.

• Specify the validation rules explicitly — 'phone number should be 10 digits, show error if fewer' is better than 'validate the phone.'
• Ask for 'a success state after submission showing a confirmation message' to prototype the full form lifecycle.
• If your form has conditional logic ('if they select Other, show a text field'), describe it — v0 handles conditional fields well.

Build a stakeholder demo with live UI

Why it matters for PMs: The gap between a PRD and a stakeholder's understanding is enormous. Words on a page don't convey the feel of a product. A live v0 prototype lets stakeholders experience the feature, not just read about it. This leads to better feedback, faster sign-off, and fewer 'that's not what I expected' moments after you've already built it.

Create an interactive demo of [feature name] for a [product type] SaaS. It should include: [list the key UI elements the user will interact with]. Make buttons clickable with state changes (e.g. [describe a toggle or expand/collapse behavior]). Add placeholder data that looks realistic for [industry/domain]. The demo should be self-contained and work without a backend.

• Keep the demo focused on 3-5 interactions — don't try to prototype the entire product. The goal is to convey the concept, not ship a working app.
• Before the meeting, test the demo on a colleague who wasn't involved — if they can't figure out what to click, your stakeholders won't either.
• Share the v0 link in the meeting invite so stakeholders can explore it on their own screen during the discussion.

Get the free 2026 AI Tools Landscape Report

50+ AI tools categorized by PM use case — prototyping, evaluation, research, analytics, roadmapping, and more. Each with a one-sentence description, a why-it-matters-for-PMs line, and a link. Free PDF, no credit card required.