What v0 actually builds, explained for founders

What does v0 actually give you?

v0 is a tool from Vercel that turns a written description into working screens, and the result is genuine code rather than a mock-up. You describe a dashboard or a sign-up page, and v0 writes the code that draws it, which you can preview, tweak by chatting and publish to a live web address.

That code is a Next.js project. It's the same kind of project a professional team would start with, which is good news: nothing about it ties you to v0, and any web developer can open it, run it and carry on. You can connect it to GitHub, where v0 works on its own branch and proposes changes for review, or download it as a ZIP file.

The catch is about depth. v0 is excellent at what users see and much lighter on what happens behind the screen. Many v0 projects look finished while still showing sample data, and buttons that appear to save things sometimes don't save anything anywhere. v0 can connect a database through Vercel's integrations, such as Neon or Supabase, but connecting one isn't the same as designing one.

The words you'll hear, in plain English

When a developer looks at your v0 project, these are the terms that will come up. You don't need to learn them deeply, just enough to follow the conversation.

• Frontend. Everything that runs in the user's browser: the screens, buttons and forms. This is v0's strength.

• Backend. The part that runs on a server: saving data, checking who's allowed to do what, taking payments, sending emails. Often thin or missing in a v0 project.

• Next.js. A popular framework for building web apps. It can do frontend and backend work in one project, which is why a v0 app has room to grow.

• React. The library Next.js uses to build screens out of reusable pieces called components.

• shadcn/ui. A set of ready-made, good-looking components, such as buttons, menus and tables, that v0 uses to give apps their clean look. The code sits inside your project, so it can be changed freely.

• Tailwind CSS. The styling system that controls colours, spacing and layout in v0's code.

• Mock data. Made-up sample content typed into the code so a screen looks real. It never changes and isn't stored anywhere.

• Database. Where real information lives, such as customers, orders and messages, so it's still there tomorrow.

• Authentication. Signing users in and proving they are who they say they are.

• Repository. The folder of code, usually on GitHub, with a full history of every change. Whoever owns it owns the app.

What's usually missing before launch

In short, the backend and the safety checks. The screens are often close to done; what's missing is the machinery that makes them trustworthy with real customers and real money.

• A designed database, so information is stored properly and stays fast as you grow.

• Secure sign-in, built on a proven service rather than written from scratch in a chat.

• Permission checks on the server, so a customer can't see another customer's data by guessing a web address. Hiding a button isn't a permission check.

• Secret keys kept off the user's browser. In Next.js, any setting whose name starts with NEXT_PUBLIC_ is visible to anyone, so payment and AI keys must never be named that way.

• Sensible behaviour when things go wrong: a slow connection, a failed payment, an empty list.

• One tidy set of components, because each chat tends to produce its own slightly different version of the same button.

• Tests on the important journeys, plus backups and error alerts.

What to do next

Get ownership sorted first, then let a developer finish the backend behind the interface you already have. You rarely need to start again.

1. 01

   Move the GitHub repository, the Vercel project, the domain and any connected database into accounts your business owns, not a personal login.

2. 02

   Ask a developer to list which screens use real data, which use mock data and which buttons do nothing yet. That list is the real scope of work.

3. 03

   Budget for the backend, sign-in and security work. A typical project takes four to eight weeks to reach a production first release.

4. 04

   Keep using v0 for new screens if you like it, with its changes going through review before customers see them.