Operator Insights

Reported by others3

1. 

   Lachezar PetkovSenior Product DesignerNeon

   Serverless Postgres company, part of Databricks. Product design team. Console UI explorations. Neon also supplies databases to app builders, v0 among them.

   Neon blog, published May 13, 2025Read the write-up (opens Neon blog in a new tab)

   Observation

   Neon's design team builds working v0 prototypes of console changes, so engineers judge feasibility before the build.

   Takeaway

   Let designers prototype the interactions engineers will build, and have an engineer review the prototype for feasibility before the ticket is written.

   What happened

   Neon's designers use v0 to turn Figma designs into working React prototypes they share with teammates and test with users. A redesign of the database connection modal reached a responsive prototype after a few rounds of prompting. Testing it showed the engineers early that click-to-copy layered over the whole snippet would not work. The autoscaling sliders took about a hundred iterations, mostly on alignment and layout, to reach three working versions. Petkov copies style values from Figma Dev Mode without using the Figma import, prompts with specific layout and behavior, and checks every output.

   • Public engineering write-up
   • No team metrics reported
   • Designer's first-person account

   Deployment details

   Serverless Postgres company, part of Databricks. Product design team. Console UI explorations. Neon also supplies databases to app builders, v0 among them.

   • Public engineering write-up
   • No team metrics reported
   • Designer's first-person account

   Team

   Neon's product design team

   Workload

   The database connection modal and autoscaling sliders in the Neon console

   Product version

   v0 as of May 2025

   Measurement

   About a hundred iterations for the slider prototypes, as the author reports

1. StripeJan 28, 2026Vercel customer storyA Stripe business value consultant with no engineering training replaced a spreadsheet model with a v0 app built on one flight.

   

   Mario BrazGTM Business Value ConsultingStripe

   Payments company. Go-to-market business value team. Customer-facing value calculator that replaced spreadsheet models.

   Vercel customer story, published Jan 28, 2026Read the case study (opens Vercel customer story in a new tab)

   Observation

   A Stripe business value consultant with no engineering training replaced a spreadsheet model with a v0 app built on one flight.

   Takeaway

   Give the owner of a spreadsheet model v0 and a deployment path, and measure the app's use against the spreadsheet it replaces.

   What happened

   Stripe's business value models lived in spreadsheets that account executives found too complex to use without help from a small team. Braz, who has a finance background, prototyped a web app in v0 on a long-haul flight and had a first working version by the time the plane landed. Vercel's story reports 92 unique weekly internal users against 23 for the spreadsheet, about 10 customer presentations exported a week, and initial value hypotheses produced about 80% faster three weeks after launch. Solution architects and product managers at Stripe then started building their own apps and prototypes in v0.

   • Vendor case study
   • Team metrics reported by the vendor
   • Builder quoted by name

   Deployment details

   Payments company. Go-to-market business value team. Customer-facing value calculator that replaced spreadsheet models.

   • Vendor case study
   • Team metrics reported by the vendor
   • Builder quoted by name

   Team

   One builder in Business Value Consulting, building for the account executives

   Duration

   First version during one flight; results measured three weeks after launch

   Workload

   Value calculator that exports to customer-facing presentations

   Product version

   v0, deployed on Vercel

   Measurement

   Weekly users from 23 to 92 and value hypotheses about 80% faster, as Vercel reports

2. Code and TheoryAug 20, 2025Vercel customer storyAt Code and Theory, working v0 interfaces replaced requirement documents, and apps ship through GitHub and the agency's QA.

   

   David DiCamilloCTOCode and Theory

   Creative and technology agency. Client and internal web applications.

   Vercel customer story, published Aug 20, 2025Read the case study (opens Vercel customer story in a new tab)

   Observation

   At Code and Theory, working v0 interfaces replaced requirement documents, and apps ship through GitHub and the agency's QA.

   Takeaway

   Treat v0 output as code entering your normal pipeline. Version it in GitHub, run it through existing QA, and enforce the design system, so speed in early design carries into delivery.

   What happened

   Code and Theory's designers, strategists, and engineers use v0 to replace strategy documents, wireframes, and static design files with working interfaces in client and internal reviews. Generated apps are versioned in GitHub, tested with the agency's existing QA stack, and deployed through Vercel. The CTO estimates that app timelines that ranged from 2 to 12 months are coming down by 50 to 75%.

   • Vendor case study
   • Organization metrics reported by the vendor
   • CTO quoted by name

   Deployment details

   Creative and technology agency. Client and internal web applications.

   • Vendor case study
   • Organization metrics reported by the vendor
   • CTO quoted by name

   Team

   Mixed creative and engineering teams across client engagements

   Workload

   Internal and client-facing web applications

   Product version

   v0, with GitHub versioning and Vercel deployment

   Measurement

   Time to prototype down 75% and app timelines down 50 to 75%, as the case study reports