Lovable prompt for an ecommerce landing page

Build a product landing page in Lovable for a project management SaaS, aimed at engineering managers at startups. This is a one-product page, not a store: everything drives toward a single purchase action, and the page should deploy at the end.

Section order:
1. Hero buy section — an image gallery (5 images, click-to-swap main) on one side; on the other, the product title, a benefit-led subhead answering "what changes for me", review stars with a count, the price, and the purchase button with a reassurance line under it (delivery estimate plus returns policy).
2. Social proof bar — press or rating badges in one row.
3. Why it works — 3 benefit sections, each with a headline in the buyer's words, a short paragraph, and a visual slot; alternate which side the visual sits on.
4. Details — a tabbed block: Specs, In the box, Shipping, and an FAQ tab with 4 questions specific to buying a project management SaaS.
5. Reviews — average rating, 6 entries with reviewer name, stars, and text, plus a "load more" that reveals 6 additional entries.
6. Final offer — the price restated, the strongest benefit line, guarantee terms, and the purchase button again.
7. Sticky mobile buy bar — on phones only, a bottom-fixed bar with price and the purchase button.

Wire the purchase button to a checkout placeholder route and log each click to the database so I can see conversion counts. In Final offer, add an email field ("get 10% off") that validates and stores addresses.

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 and responsive:
- Sections separated by 88px desktop, 52px mobile; tab content keeps a fixed min-height so switching tabs never jumps the page.
- On phones the gallery becomes swipeable and the hero stacks gallery-first.

The purchase action reads "start a free trial" on every buy button. Deploy when preview passes and give me the URL.

Verify: buy clicks write rows to the database; the email capture rejects invalid addresses and stores valid ones; the mobile bar shows only under 768px; switching tabs causes no layout shift; the deployed page loads over HTTPS.