The canonical prompt for a SaaS landing page (v0, Lovable, Bolt, Claude)

What this prompt produces

One-shot generation of a complete SaaS landing page: hero (headline ≤ 9 words, one CTA), logo bar, 3-column feature grid where each feature maps to a user pain, product screenshot section, testimonial with real-sounding specifics, 3-tier pricing with a highlighted middle tier, 6-question FAQ, and footer. Responsive, semantic HTML, no lorem ipsum anywhere.

You are a senior conversion-focused product designer and front-end engineer. You have shipped 50+ SaaS landing pages that convert above 4%.

Build a complete landing page for: [PRODUCT — one sentence: what it does and for whom].

STRUCTURE (exactly this order):
1. Hero — headline of max 9 words stating the outcome (not the features), subheadline of max 20 words naming the user and the pain, ONE primary CTA button ("[CTA text]"), no secondary CTA. Product screenshot or abstract product visual on the right.
2. Logo bar — "Trusted by" + 5 grayscale placeholder logos.
3. Problem → Solution — 3 short pain statements the target user says verbatim, each answered by one product capability.
4. Feature grid — 3 columns × 2 rows. Each cell: icon, feature name (2-3 words), one sentence of benefit written as outcome, not mechanism.
5. Social proof — one testimonial with concrete numbers ("cut onboarding time from 3 days to 4 hours"), name, role, company.
6. Pricing — 3 tiers, middle tier visually highlighted and labeled "Most popular". Annual/monthly toggle. Each tier: 5 bullet features, one CTA.
7. FAQ — 6 questions real buyers ask (pricing, security, migration, cancellation, support, integrations) with 2-3 sentence answers.
8. Final CTA band — restate the outcome headline differently + the same primary CTA.
9. Footer — product, company, legal, social columns.

HARD RULES:
- Every word of copy must be written for the actual product. NO lorem ipsum, no "Feature 1", no placeholder text anywhere.
- One CTA text used consistently everywhere.
- Semantic HTML5 landmarks (header/main/section/footer), accessible contrast, alt text on all images.
- Mobile-first responsive; the hero must not exceed one viewport on mobile.
- Load no external UI libraries unless the platform requires it.

BEFORE OUTPUT, VERIFY:
- Headline states an outcome in ≤ 9 words.
- Each feature cell answers "so what?" — benefit, not mechanism.
- Pricing middle tier is the obvious choice.
If any check fails, rewrite that section before responding.

Why this prompt works

• ✓The fixed 9-section skeleton removes layout decisions — the model spends its capacity on copy quality.
• ✓Word-count caps on the headline force outcome language instead of feature lists.
• ✓'No placeholder text' is stated as a hard rule — the single most common failure of landing-page prompts.
• ✓The self-check list catches the three highest-impact conversion mistakes before output.

What weaker prompts get wrong

• ✕Asking for 'a beautiful modern landing page' with no structure — yields random sections and lorem ipsum.
• ✕Two competing CTAs in the hero (e.g. 'Start free' + 'Book demo') — splits conversion.
• ✕Letting the model choose section order — testimonials land before the product is explained.