12

I kept iterating on landing page prompts and finally landed on one that reliably produces a polished SaaS landing page in a single shot: hero, feature grid, pricing table, FAQ, and footer, all responsive.

The trick was specifying the visual hierarchy explicitly instead of just saying "make it look good". Sharing the exact prompt below. It has worked across three different models for me.

What would you add to make the testimonials section less generic?

THE PROMPT
Build a single-file HTML landing page for a SaaS product called {PRODUCT}. Requirements:
- Hero: bold headline (max 8 words), subheadline (max 20 words), primary CTA button, product screenshot placeholder with subtle drop shadow
- Social proof bar: 5 grayscale company logos
- Feature grid: 3 columns, each with an icon, 4-word heading, 2-sentence description
- Pricing: 3 tiers (Free/Pro/Team), middle tier visually emphasized, annual toggle
- FAQ: 5 questions in an accordion
- Footer: 4 columns of links
Design constraints: system font stack, one accent color #4f46e5, 8px spacing grid, max-width 1120px, generous whitespace, no stock-photo cliches. All copy must be specific to {PRODUCT}, no lorem ipsum.
The 8px spacing grid instruction is doing so much work here. Stolen, thanks. – vibecoder 1 hour ago
add a comment

2 Answers

9
✔

The generic-testimonial problem is that you're letting the model invent people. Pin the personas instead. I append this block to your prompt and the testimonials come out specific and believable:

Add three testimonials, each from a named persona with a job title and a concrete metric ("cut onboarding from 3 days to 4 hours"). One should mention a hesitation they had before buying. No exclamation marks.

THE PROMPT
Add a testimonials section: 3 cards. Each testimonial must (a) name a persona with role and company type, (b) cite one concrete before/after metric, (c) include one mild hesitation overcome ("I expected setup to be painful, but..."). Ban: "game changer", "10x", exclamation marks, and any sentence that could apply to a different product unchanged.
4
✔

One addition that helped me: ask for the pricing tier features to be differentiated by verb, not by adjective. "Unlimited projects" vs "Priority support" reads like every SaaS page ever. Forcing verbs ("Export to PDF", "Invite 10 teammates") makes the tiers feel real.

Your Answer