Lovable
Lovable prompt for an agency landing page
This Lovable prompt produces an agency landing page with a contact pipeline that actually works: validated form, database-stored submissions, email notification, then deploy. Proof leads the page — a full-width featured case sits above the grid. The customizer swaps style, palette, typography, and motion while the structure holds.
Last updated
Prompt
Create a one-page site in Lovable for {{product}}, aimed at {{audience}} — an agency page where the work does the talking and the contact form actually submits.
Page order:
1. Hero — a two-line claim built from {{product}}'s specialty (what they make, who wins from it), with a thin strip of 5 client names underneath.
2. Featured case — one project at full width: large image area, client name, the problem in one sentence, the result as a number.
3. More work — 4 additional projects in a 2-up grid, each with title, category tag, and a single result stat.
4. Capabilities — an accordion of 4 service groups; each opens to a 2–3 sentence description plus 3 deliverable bullets.
5. Process — 3 phases (shape / build / ship — rename to fit {{product}}'s discipline) with a week-range and an outcome per phase.
6. Studio — a 2-sentence manifesto beside a team grid (photo placeholder, name, role) for up to 6 people.
7. Contact — a working form (name, email, budget range select, message) with inline validation; store submissions in Lovable's database and send an email notification on submit. Beside the form, a direct email address and a response-time promise.
Visual direction:
{{style}}
Palette: {{palette}}
Typography: {{type}}
Motion: {{motion}}
Rhythm and responsive behavior:
- Keep section spacing on one scale: 96px desktop, 56px mobile; accordion rows use 20px internal padding.
- On phones the featured case stacks image-over-text, the team grid drops to 2 columns, and the budget select becomes a full-width control.
The primary call to action is "{{cta}}" — a button in the hero and the label on the contact form's submit. When the page works in preview, deploy it and give me the live URL.
Before handing it back, verify: the form rejects an empty email and writes a row to the database; all 5 work entries show a stat; the accordion opens one panel at a time; nothing overflows at 390px; the deployed URL loads.Customize it
Runs in your browser. Nothing you type here is sent anywhere.
Your customized prompt
Create a one-page site in Lovable for a project management SaaS, aimed at engineering managers at startups — an agency page where the work does the talking and the contact form actually submits. Page order: 1. Hero — a two-line claim built from a project management SaaS's specialty (what they make, who wins from it), with a thin strip of 5 client names underneath. 2. Featured case — one project at full width: large image area, client name, the problem in one sentence, the result as a number. 3. More work — 4 additional projects in a 2-up grid, each with title, category tag, and a single result stat. 4. Capabilities — an accordion of 4 service groups; each opens to a 2–3 sentence description plus 3 deliverable bullets. 5. Process — 3 phases (shape / build / ship — rename to fit a project management SaaS's discipline) with a week-range and an outcome per phase. 6. Studio — a 2-sentence manifesto beside a team grid (photo placeholder, name, role) for up to 6 people. 7. Contact — a working form (name, email, budget range select, message) with inline validation; store submissions in Lovable's database and send an email notification on submit. Beside the form, a direct email address and a response-time promise. 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. Rhythm and responsive behavior: - Keep section spacing on one scale: 96px desktop, 56px mobile; accordion rows use 20px internal padding. - On phones the featured case stacks image-over-text, the team grid drops to 2 columns, and the budget select becomes a full-width control. The primary call to action is "start a free trial" — a button in the hero and the label on the contact form's submit. When the page works in preview, deploy it and give me the live URL. Before handing it back, verify: the form rejects an empty email and writes a row to the database; all 5 work entries show a stat; the accordion opens one panel at a time; nothing overflows at 390px; the deployed URL loads.
Same task in other tools
Questions about this prompt
Where do contact form submissions actually go?
Lovable stores each submission as a row in its built-in database and fires an email notification on submit, both of which the prompt requests explicitly. You can browse rows in Lovable's backend view, and later ask it to forward submissions to a CRM or a shared inbox.
Can I run this page without the database wiring?
Yes — tell Lovable to replace storage with a plain mailto link or a form service like Formspree, and keep the inline validation. You lose the submissions log, so only do this if leads already land somewhere else you check.
Lovable rendered the featured case as a second hero — how do I correct it?
Reply in the same chat naming the section: remind it the featured case needs a client name, a one-sentence problem, and a numeric result, at full width below the hero. Lovable iterates best one section per message, so fix this before touching anything else.
Part of the Lovable landing-page cluster — start from the main Lovable landing page prompt.