Verified against v0 · 2026-07-05
Generate a SaaS landing page hero section with a product visual
A v0 brief for a Next.js SaaS hero section with exact copy, CTA hierarchy, and a concrete visual description, so the output reads as shippable copy rather than generic AI-landing-page filler.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Generate a hero section component for a Next.js App Router marketing page, built with Tailwind CSS and shadcn/ui primitives. Content: - Eyebrow/badge text: Now with team workspaces - Headline: Ship customer support that actually reads the docs — large, tight leading, should read as one confident sentence, not a pile of slogans. - Subheadline: Connect your help center once. Every reply cites the real answer. — one sentence, muted color, smaller than the headline. - Primary CTA button: Start free trial, plus a secondary ghost or text-link CTA: Watch a 2-min demo. - A visual on the right on desktop, below the text on mobile: a mock chat widget showing an AI reply with a citation chip underneath it. Build it as an actual styled mock (cards, a stat row, a chat bubble, whatever fits the description), not a grey placeholder box. Layout: - Two-column on desktop, stacked with the visual below the text on mobile. - Generous vertical padding on desktop, with a constrained max-width container. - A subtle background treatment behind the whole section — a soft gradient or a faint grid pattern, not a flat white or black background. Constraints: - Server component — no client-side state unless the visual mock genuinely needs interactivity. - Use next/image, with a placeholder src, for any images. - Ship it as a self-contained Hero component with typed props for all of the text content above, so it's reusable with different copy.
Customize the highlighted detailsoptional — the prompt above already works
Why this works
v0's output quality tracks how concrete the brief is, and hero sections are where that's most visible — the tool has to invent headline copy, a CTA hierarchy, and whatever goes in that big visual slot on the right if you don't supply them, which is exactly why so many AI-generated SaaS landing pages read identically. Giving v0 the actual headline, the exact secondary CTA, and a real description of the visual, not "something nice," is the difference between a component you ship and one you immediately rewrite.
What you get back
A self-contained Hero.tsx with the supplied headline and subheadline rendered at full size, a two-CTA row, and a styled mock chat-widget visual on the right rather than a placeholder rectangle.
Verified against
v0 v0 by Vercel (Next.js + shadcn/ui default stack) · 2026-07-05
Changelog
- 2026-07-05 — Initial version, added an explicit visual_description field after a draft without one returned a plain grey placeholder box instead of a styled mock.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE

