Key findings
- All 18 accounts that discuss speed praise how fast v0 produces a working prototype, and all 10 that discuss deploys praise publishing to Vercel. 13 of 20 that discuss interface quality praise it.
- All 13 accounts that discuss regressions complain about them, and 13 of 18 that discuss credits complain about spend. Every one of those credit complaints was posted on the Vercel Community forum or r/v0_, after the May 2025 move to token-based credits and the 2026 plan changes.
- 13 accounts say they shipped v0 output to production, and 4 say they kept it a prototype. Team accounts lean the other way, with 3 of the 5 that say keeping it a prototype.
- 13 of the 18 team and leadership accounts use v0 to show an idea to the people who must approve it, before engineering builds it.
- 9 accounts describe building and shipping inside v0, and 8 describe moving the output into a repository and another editor early.
In public accounts from January 2025 to October 2026, teams use v0 to make an idea concrete before engineering starts, and engineers still build what ships. Individual builders ship straight from v0 and complain about credit spend and the GitHub workflow.
Who wrote the accounts
67 accounts come from individual builders: developers, designers, product managers, and founders writing about their own use. 24 speak for a team or as a leader. They include Neon's design team, product designers at Entrata and DubiCars, Cisco Security's head of design, product leaders at Relyance AI and Luxury Presence, Release's CEO, and Chess.com's growth chief. Others are an agency that runs about 200 client apps in v0 and product teams on Hacker News that prototype epics before engineering commits to them.
15 accounts come from the Vercel Community forum and 13 from r/v0_, where users go to report problems. Those two sites supply most of the negative posts, so complaints about credits and regressions are real and weigh more in these counts than in the wider user base.
| Audience | Accounts | Positive | Mixed | Negative |
|---|---|---|---|---|
| Leaders and teams | 24 | 19 | 3 | 2 |
| Individual builders | 67 | 35 | 10 | 22 |
| All practitioners | 91 | 54 | 13 | 24 |
GILD count of 91 public accounts, January 7, 2025 to October 4, 2026, opened Oct 12, Oct 25, Oct 26 or Oct 27, 2026.
Where teams put v0
Team accounts put v0 in one place, between an idea and engineering. On one team, product owners and architects build working prototypes for epics, get agreement on them, and discard the code. Neon's designers build working prototypes of console changes, test them with users, and settle feasibility with engineers before the build. One of their slider designs took about a hundred iterations. Cisco Security's head of design describes product managers prototyping while designers focus on strategy. At Entrata, a product designer feeds PRDs into v0 with the team's design system and presents a working design with code in three or four days. This is down from two to four weeks per feature. A DubiCars designer prototypes app flows from Figma imports for management and saves 25 to 30% of prototyping time.
The same accounts set limits. A product manager who won approval with a v0 prototype then had a UX designer redesign the idea from scratch. An agency with about 200 client apps in v0 reports an auto-diagnosis feature that edited apps when they were opened. An advertising-site team saw the cost of one standard generation rise from about US$1 to up to US$4 in January 2026.
What individual builders report
Builders praise the time from prompt to deployed app. Their examples include a YouTube Shorts downloader in two prompts and an insulin calculator in an afternoon. Others built a small business site on a custom domain in minutes and a Web MIDI tool in an hour. 10 of 20 who compared v0 with Lovable, Bolt, Replit, Cursor, or Claude tools preferred v0, mostly for UI. One builder who has spent more than US$4,000 prefers it for server-rendered pages that rank in search.
Their complaints bunch up after two changes: v0's May 2025 move from message limits to token-based credits, and the GitHub branch workflow changes of early 2026. Forum and Reddit posts describe credits spent on fixes that broke working code, a failed agent run that still charged, unused credits reset after an account change. They also describe branch and pull errors that stalled projects.
| Theme | Accounts | Praise or complaint |
|---|---|---|
| UI and design quality | 19 | 12 praise |
| Credits and cost | 17 | 12 raise |
| Prompt to prototype speed | 16 | 16 praise |
| Regressions and fix loops | 12 | 12 raise |
| Day-to-day experience | 10 | 3 praise |
| Deploys and integrations | 9 | 9 praise |
| Code handoff | 8 | 6 praise |
| Stack and hosting lock-in | 6 | 5 raise |
| Beyond the frontend | 5 | 3 raise |
GILD count of 85 public accounts, opened Oct 12 or Oct 25, 2026.
What this means for a buying decision
Buy v0 for the step before engineering, where product managers, designers, and planners make ideas concrete in your design system. Decide per project whether output is a prototype or production, connect production projects to GitHub from the start, and give someone ownership of credit spend from the first week.
24 accounts speak for teams, and none of the 91 describes an organization-wide rollout at a named company. The named rollouts that exist are Vercel's own case studies, such as Stripe's. Ask Vercel for a reference customer of your size and call them before you sign. Before buying seats for every team, pilot v0 with one product team.
Methodology
GILD opened every account on October 12 or October 25, 2026. It recorded its author, publication date, audience, sentiment, and the positions it takes, using the tag list GILD built for its Claude Code research. The accounts come from Hacker News, the Vercel Community forum, r/v0_, a company design blog, DEV Community, videos, newsletters, outside tests, PeerSpot reviews, and X. GILD read Hacker News comments through the Algolia API and Reddit posts through the Arctic Shift archive with links to their reddit.com pages. It read DEV Community articles through their API and forum posts through the Discourse API. Accounts published before 2025, posts by Vercel staff, Vercel's own posts, and its customer case studies are left out. The counts cover public accounts, so they show what people chose to post.
Products in this piece
Sources
- Official documentation
- 5
- Public source
- 16
- v0 docs: Pricing
- Vercel blog: Updated v0 pricing (May 13, 2025)
- v0 docs: GitHub
- Vercel blog: Introducing the new v0 (Feb 3, 2026)
- v0 docs: What is v0?
- Lachezar Petkov, Neon blog: Using v0 for UI design exploration (May 13, 2025)
- Shardul Badave, Product Designer at Entrata, on PeerSpot: design workflows shrunk from weeks to days (Jan 1, 2026)
- Rana Hammad, Product Designer at DubiCars, on PeerSpot: prototyping car valuation flows (Jan 5, 2026)
- Roger Wong: Beyond the Prompt, eight AI design tools scored on one checkout prompt (Apr 28, 2025)
- exiguus on Hacker News: product owners and architects prototype in v0 (Jul 9, 2025)
- ashryan on Hacker News: a v0 prototype for an internal pitch, then a designer's rebuild (Jan 22, 2025)
- kadhirvelm on Hacker News: prototypes as a communication tool for a product team (Aug 11, 2026)
- Soerensen on Hacker News: a non-technical founder's SaaS front end built with v0 and Cursor (Feb 2, 2026)
- DevGlyphX, Vercel Community: auto-diagnosis editing code without consent (Mar 18, 2026)
- Peterjohnson101986, Vercel Community: increased token costs after January 17 (Jan 21, 2026)
- ryado on Hacker News: a v0 weekend, a working app, and a US$50 bill (Sep 7, 2025)
- Winter_Stretch259 in r/v0_: more than US$4,000 spent on v0, with model recommendations (Aug 5, 2026)
- Efficient_Ad2826 in r/v0_: a failed agent run that still spent credits (Mar 30, 2026)
- Free-Pickle-3621 in r/v0_: unused Pro credits reset to US$5 (Oct 4, 2026)
- Fabi, Vercel Community: the forced branch-per-chat workflow (Jan 26, 2026)
- Emil, Vercel Community: v0 has gotten insanely expensive (Jun 12, 2025)