Replit Agent prompt for a SaaS landing page
This prompt makes Replit Agent propose a section plan for your approval before building, then deploy the finished SaaS page to a live URL. The structure leads with outcome-first copy and caps the CTA at exactly three placements. Style, palette, type, and motion come from the customizer dropdowns, so the plan-approve-deploy loop is identical across looks.
Last updated
I want a production-hosted landing page for {{product}}. Audience: {{audience}}. Start by showing me your plan — list the sections you intend to build and the copy angle for each — and wait for my approval before writing code, so we agree on structure first.
Build this section stack once the plan is approved:
- Nav with logo, two links, and the CTA button; collapses to a hamburger under 768px.
- Hero split 60/40: the left column carries an H1 that leads with the outcome rather than the product name, a subhead that names {{audience}} explicitly, and the CTA; the right column holds a product visual placeholder.
- Numbers band: three metrics with short labels, using placeholder values I can edit later.
- Feature trio: three columns, each anchored by a question the visitor is already asking, answered in two sentences.
- Full-bleed product screenshot with a caption describing a real workflow in {{product}}.
- Pricing glimpse: the starting price, four bullets covering what it includes, one button, and a link to a future /pricing page.
- FAQ with five entries; the final entry should handle the biggest objection to switching tools.
- Final CTA strip and a minimal footer (copyright, three links).
Visual direction:
{{style}}
Palette: {{palette}}
Typography: {{type}}
Motion: {{motion}}
Layout rules:
- Vertical rhythm on an 8px base: sections get 12 units of padding on desktop and 8 on mobile; never mix arbitrary margins between siblings.
- On phones, the hero stacks visual below copy and the numbers band becomes a vertical list.
The primary call to action is "{{cta}}" — hero, nav, and final strip, nowhere else.
Deploy to Replit hosting when done and give me the live URL. Then confirm: the deployed page loads over HTTPS; Lighthouse performance scores above 85; the hamburger opens and closes on a real 390px viewport; all three CTA buttons share identical text and destination. I'll iterate section by section in follow-up messages, so keep each section's code isolated.Customize it
Runs in your browser. Nothing you type here is sent anywhere.
I want a production-hosted landing page for a project management SaaS. Audience: engineering managers at startups. Start by showing me your plan — list the sections you intend to build and the copy angle for each — and wait for my approval before writing code, so we agree on structure first. Build this section stack once the plan is approved: - Nav with logo, two links, and the CTA button; collapses to a hamburger under 768px. - Hero split 60/40: the left column carries an H1 that leads with the outcome rather than the product name, a subhead that names engineering managers at startups explicitly, and the CTA; the right column holds a product visual placeholder. - Numbers band: three metrics with short labels, using placeholder values I can edit later. - Feature trio: three columns, each anchored by a question the visitor is already asking, answered in two sentences. - Full-bleed product screenshot with a caption describing a real workflow in a project management SaaS. - Pricing glimpse: the starting price, four bullets covering what it includes, one button, and a link to a future /pricing page. - FAQ with five entries; the final entry should handle the biggest objection to switching tools. - Final CTA strip and a minimal footer (copyright, three links). 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. Layout rules: - Vertical rhythm on an 8px base: sections get 12 units of padding on desktop and 8 on mobile; never mix arbitrary margins between siblings. - On phones, the hero stacks visual below copy and the numbers band becomes a vertical list. The primary call to action is "start a free trial" — hero, nav, and final strip, nowhere else. Deploy to Replit hosting when done and give me the live URL. Then confirm: the deployed page loads over HTTPS; Lighthouse performance scores above 85; the hamburger opens and closes on a real 390px viewport; all three CTA buttons share identical text and destination. I'll iterate section by section in follow-up messages, so keep each section's code isolated.
Same task in other tools
Questions about this prompt
Why make the Agent show a plan before building?
Replit Agent commits to structure early, and redirecting it after a full build costs more than approving a plan up front. Reviewing the section list and copy angles first means your follow-ups become small tweaks instead of teardowns.
The Lighthouse check comes back under 85 — what do I ask for?
Ask the Agent to name the top three flagged items and fix them one at a time — typically oversized hero imagery, render-blocking fonts, or unused JavaScript. Redeploy and re-run after each fix so you can see which change actually moved the score.
How do I iterate on a single section after the deploy?
Reference the section by its name from the prompt's stack — "rework the numbers band: replace the third metric" — since the prompt tells the Agent to keep each section's code isolated. It redeploys on each accepted change, so the live URL always reflects the latest state.
Part of the Replit Agent landing-page cluster — start from the main Replit Agent landing page prompt.