Blog

Building a marketing website with Vercel’s v0: Our honest experience

Diario del capitán, fecha estelar d608.y41/AB

Jordi Vendrell Farreny
Founder & COO
Astronauta Vercel

When we first tried v0 about a year ago, it felt promising but unfinished. Recently, we decided to give it another shot, this time to build and publish a complete marketing website for a real company. The difference? Night and day.

What is v0?

v0 is a Vercel tool that allows teams to build full web projects using natural language prompts. Integrated directly with GitHub and Vercel, it generates a working Next.js frontend (using shadcn components) without requiring coding knowledge. You simply describe what you want, sections, layout, style, and v0 assembles a functional, modern-looking website that can be refined and published instantly. It feels like having an AI-powered front-end developer on your team.

Seamless integration

One of v0’s strongest points is its tight integration with GitHub and Vercel:

  • You can work on different branches and sync changes easily.
  • Push updates to GitHub automatically or pull existing code into v0.
  • And with one click, deploy your site live on Vercel, free for basic projects.
  • For teams without deep technical knowledge, this end-to-end connection is incredibly smooth.

Design and customization

v0 uses shadcn components and includes a Design Mode where you can define project variables, colors, typography, spacing, etc. The AI does a surprisingly solid job creating attractive, responsive layouts. It’s clearly improved a lot since early versions. The built-in code editor is another plus. If you’re familiar with Tailwind CSS or basic frontend concepts, you can manually tweak elements and preview changes instantly.

Speed and efficiency

This is where v0 really shines. In about 30 minutes, you can have a fully functional, decent-looking landing page. Spend a day or two refining it, and you’ll have a polished corporate website ready for launch. For startups, MVPs, or new products that need a fast web presence, this might be the most efficient and affordable solution available today.

The downsides

v0 isn’t perfect, especially for developers who care about clean code. Two key issues stand out:

Tailwind variable handling: v0 often hardcodes color values instead of using defined variables, which makes the code less maintainable.

Messy underlying code: While the generated site looks great, the codebase can be inconsistent, leftover commented sections, redundant styles, or unused components.

For long-term projects or scalable websites, you’ll eventually want a developer to refactor or clean up the code.

Pricing

v0’s pricing is based on user seats (around $30 per seat) plus credit usage. For small teams, this can add up quickly. Still, considering how much time it saves, it’s often worth it for early-stage projects.

Final thoughts

Building and deploying a production-ready website with v0 was an overall positive experience for our team. It’s ideal for quick launches, MVPs, and marketing pages, especially when time or technical expertise is limited. However, if your project grows or requires fine-tuned code quality, it’s worth transitioning later to a more traditional development workflow. Next, we plan to test Lovable and Cursor 2.0 to see how they compare, but for now, v0 feels like a glimpse into the future of web development: AI-powered, fast, and surprisingly capable.

Compartir este post

Artículos relacionados

Happy Scribe logo

How we rebuilt HappyScribe’s website with a headless CMS

How we gave HappyScribe full control of their website, and made their marketing team faster than ever.

Leer el artículo
Ruby

How we make the right app for you (part 2)

A full breakdown of the MarsBased tech stack as of early 2014. Discover the languages, frameworks, and tools we used to build the right apps for our clients.

Leer el artículo
How to build a Node.js API (part one)

How to build a Node.js API (part one)

We want to share with you how we built a Node.js API for a client, describing some patterns and javascript conventions we used.

Leer el artículo