BoilerPrompt
Lovable

Lovable prompt for a testimonial section

This brief has Lovable build a three-layer proof section — logo strip, featured quote, then a nine-card testimonial wall — backed by structured data. Distinct voices per quote and mandatory attribution are the rules that keep it from reading as filler. Set style, palette, typography, and motion in the customizer and the prompt carries them as spec blocks.

Last updated

Prompt
Ask Lovable to add a testimonial wall to the {{product}} landing page — a proof section placed right after the feature block, built for {{audience}} to skim, with carousel motion reserved for the small-screen fallback.

Build it in three layers:
- Layer 1, logos: a slim strip labelled "Teams using {{product}}" with six grayscale logo placeholders. Keep it quiet — its job is to prime the quotes below.
- Layer 2, the featured quote: one testimonial promoted above the rest, set in display-size type across about two-thirds of the container, with a headshot and a full attribution line (name — role, company). Pick the quote that names a measurable before/after.
- Layer 3, the wall: a 3-across grid of nine quote cards at staggered heights, each holding quotation then attribution. Write nine distinct voices from segments of {{audience}} — a converted skeptic, a numbers person citing a metric, a team lead describing rollout, and so on. No two quotes may share an opening word, and none may be generic praise.

Store the testimonials in a structured list in the app — or a small table if the project already uses Lovable's database — so entries can be added without touching layout. End the section with a short line ("Join them" or equivalent) and a button labeled "{{cta}}" hooked to the same destination as the hero button.

Visual direction:
{{style}}

Palette: {{palette}}
Typography: {{type}}
Motion: {{motion}}

Spacing: roughly 6rem vertical padding; 2rem between the three layers; 1.25rem card gap. On phones, layers 1 and 2 stack unchanged while the wall converts to a horizontally swipeable card row with snap points and a "1 of 9" counter.

Before publishing, confirm: nine attributed cards render from data rather than hardcoded markup; the featured quote is visually dominant; the mobile view swipes with snap; the "{{cta}}" button and the hero button share a destination; no quote repeats another's opening word.

Customize it

Runs in your browser. Nothing you type here is sent anywhere.

Your customized prompt
Ask Lovable to add a testimonial wall to the a project management SaaS landing page — a proof section placed right after the feature block, built for engineering managers at startups to skim, with carousel motion reserved for the small-screen fallback.

Build it in three layers:
- Layer 1, logos: a slim strip labelled "Teams using a project management SaaS" with six grayscale logo placeholders. Keep it quiet — its job is to prime the quotes below.
- Layer 2, the featured quote: one testimonial promoted above the rest, set in display-size type across about two-thirds of the container, with a headshot and a full attribution line (name — role, company). Pick the quote that names a measurable before/after.
- Layer 3, the wall: a 3-across grid of nine quote cards at staggered heights, each holding quotation then attribution. Write nine distinct voices from segments of engineering managers at startups — a converted skeptic, a numbers person citing a metric, a team lead describing rollout, and so on. No two quotes may share an opening word, and none may be generic praise.

Store the testimonials in a structured list in the app — or a small table if the project already uses Lovable's database — so entries can be added without touching layout. End the section with a short line ("Join them" or equivalent) and a button labeled "start a free trial" hooked to the same destination as the hero button.

Visual direction:
Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else.

Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge.
Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy.
Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission.

Spacing: roughly 6rem vertical padding; 2rem between the three layers; 1.25rem card gap. On phones, layers 1 and 2 stack unchanged while the wall converts to a horizontally swipeable card row with snap points and a "1 of 9" counter.

Before publishing, confirm: nine attributed cards render from data rather than hardcoded markup; the featured quote is visually dominant; the mobile view swipes with snap; the "start a free trial" button and the hero button share a destination; no quote repeats another's opening word.

Same task in other tools

Questions about this prompt

Why forbid quotes from sharing an opening word?

Nine cards that all start with "I" or the product name read as written by one hand, which kills the trust the section exists to build. Forcing distinct openings pushes Lovable into varied sentence structures and role-specific detail.

Should testimonials live in Lovable's database?

If the project already uses it, yes — the prompt allows either, and a table means adding quote number ten without touching the layout. For a purely static marketing page, the in-app structured list is simpler and works just as well.

My hero already has a logo strip — do I keep layer 1?

Drop it — tell Lovable to skip the logos and start at the featured quote, since repeating the same marks twice on one page dilutes both instances. The featured quote and the wall don't depend on the strip being there.

Don't have Lovable yet? This link may be an affiliate link; it never changes what you pay.

Try Lovable

Part of the Lovable landing-page cluster — start from the main Lovable landing page prompt.

Related prompts