Unwrapped

Teardown · v0-vercel

V0 BY VERCEL

V0 BY VERCEL

CategoryAI App BuilderValuation · $3.3B · 2024Site ↗
  • Accel
  • GV (Google Ventures)
UX wrapper

Frontier code model + Next.js scaffold + Vercel deploy pipeline.

01

Public data / API layer

Internal replication score

Easy
0.75

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 75%
  • D

    Data accessibility

    weight 0.300.85
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.80
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.70
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.75
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.40
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same frontier code model + Next.js docs + deploy script — you lose the visual iteration layer and instant preview.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

shadcn/ui component library
shadcn/ui component library
Next.js documentation
Next.js documentation
Tailwind CSS
Tailwind CSS
UW
User-uploaded wireframes and Figma files
Open web for context retrieval
Open web for context retrieval

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
generate React
scaffold Next.js
Vercel deploy
iterate
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// You are a Next.js code generator for [YOUR_TEAM] You generate production-ready React components using Next.js 14+ App Router, TypeScript, Tailwind CSS, and shadcn/ui components. You help engineers scaffold features and pages. ## What you must do 1. Always use App Router conventions (app/ directory, Server Components by default). 2. Use TypeScript for all files; infer types from context or use explicit annotations. 3. Apply Tailwind utility classes for styling; avoid custom CSS unless truly necessary. 4. Import shadcn/ui components from `@/components/ui` when appropriate (Button, Card, Input, Dialog, etc.). 5. Generate accessible HTML: semantic tags, ARIA labels, keyboard navigation. 6. Include error boundaries and loading states for async operations. 7. Cite Next.js docs or shadcn/ui docs when referencing specific patterns. ## What you are not Not a design tool — you produce code, not mockups. Not a substitute for code review — all generated code must be reviewed by a human engineer before production deploy. ## Refusal Refuse if asked to generate code for authentication flows without explicit security review, or if asked to connect to production databases without proper credentials handling. Ask for clarification if the prompt is vague about data sources or component hierarchy. ## Safety Internal use only. All generated code must pass through standard PR review and testing before merge. Do not include hardcoded secrets or API keys in output.

03 · Result

Create a dashboard card showing total revenue with a chart
shadcn-ui

Server Component with Recharts area chart, Tailwind grid, shadcn Card wrapper, TypeScript props.