SaaS Landing Page Prompt: The Section Spec, Run in Lovable, With the Page It Built

What does the page have to do, section by section?

Turn a cold visitor from one source into a trial sign-up, and nothing else. Unbounce's examples post (updated 14 August 2025, read 26 September 2026) lists the elements as USP, hero, design, features and benefits, social proof, a demo, CTA, forms and mobile; its benchmark from 44,000 pages puts SaaS at a 9.5% average and a 3.0% median conversion rate. The list is right and unordered. The order is what the prompt adds.

The prompt

Written in the library's shape: context, features in priority order, rules, build order, safeguards, and the closer that makes Lovable ask before building. Swap the product and visitor lines for yours.

# Context
Build the marketing landing page for a SaaS product: one page whose job is to turn a cold visitor from one traffic source into a trial sign-up. The product is Cadence, a shared content calendar for marketing teams of 3 to 10; the visitor is a marketing lead arriving from a LinkedIn post. Server-rendered throughout so the copy can rank.

## Core Features (Priority Order)
1. Hero: an outcome headline (what changes for the visitor), one sentence of how, one primary CTA, one proof line marked as a placeholder
2. Problem block: three concrete pains in the visitor's words, then the product as the answer
3. Features written as outcomes: each feature is a heading in the form "[result] without [cost]", one sentence, one screenshot placeholder with a fixed aspect ratio
4. Pricing: two or three plans reading their limits from one config object; the same object drives the comparison table
5. FAQ: six questions that stall a sign-up, marked up as FAQPage structured data
6. Final CTA repeating the hero's, and nothing else new

## Copy & Conversion
- One primary action on the page; secondary links go to docs or pricing anchors only
- Proof elements are placeholders clearly marked as placeholders; never invent names, logos or numbers
- Maximum 65 characters per line of body copy; headings state results, not nouns

## Technical Requirements
- Real title, meta description, canonical and Open Graph tags; the body copy is text in the HTML, not an image or a client-only block
- Mobile first; the comparison table scrolls inside its own container
- No layout shift when images load

## Build Order
Final copy as static sections first, so there is something to index. Then the pricing config and the components that read it. Then FAQ and schema. CTA wiring to the sign-up route last.

## Safe-Guard Instructions
- Do not add a second call-to-action type: no newsletter box, no chat widget, no exit popup
- Every limit shown in the pricing section is imported from the config, never retyped
- No alert() dialogs and no modals for anything on this page

## Before Building
Ask me any questions you need in order to fully understand the audience and the offer, then save the decisions to the project knowledge so later prompts build on them.

What happened when we ran it?

Pasted as one message into a new project in Marco's personal Lovable workspace on 26 September 2026. Lovable asked 5 questions before building; the answers given: What exactly does the sign-up give them? 14-day free trial, no card (the default); How should the plans be structured? Two plans, Team and Business (the default); Which pain should the page lead with? Calendar lives in scattered spreadsheets (the default); Any brand details I should use? Left blank, so it picked placeholders; Which design direction should I build? Two rendered mockups offered; the first, Newsroom grid planner, selected.

Build started 19:22 and was finished by 19:28. Lovable's summary: "The Cadence landing page is live: hero, the spreadsheet problem, three outcome features with screenshots, Team/Business pricing with a scrollable comparison table, six FAQs, and one repeated trial call-to-action leading to a sign-up page." The hero reads "Every piece of content, on one shared grid." with one button, "Start 14-day free trial", the line "No credit card required", and a proof line that says it is a placeholder. The billing page lists the project at 4.44 credits; the balance moved 56.9 to 52.4.

Cost, read from the billing page: 56.9 credits before, 52.4 after, 4.5 for the run.

How does this run compare with the other measured runs?

The credits guide explains what the numbers pay for; the prompt examples page has the other runs' screenshots. The landing page prompts category holds the email opt-in, pricing page and SEO landing prompts this one borrows its rules from, and the landing page kit adds the leads table with its insert-only policy.

What do the top results for this term leave out?

• Lapa Ninja, Saaspo, Dribbble, Behance. Galleries of hundreds to thousands of screenshots. Inspiration, no method, no build.
• Unbounce, 27 best SaaS landing page examples. About 8,500 words, 27 screenshots, the benchmark figures cited above, an unordered element list, and templates that assume its own builder.

What we did not publish

• A conversion rate for the page we built. It was never published to traffic, so it has none.
• Copy claims for a product. The run used the fictional Cadence with proof lines marked as placeholders, as the prompt requires.
• A design verdict. Whether the page looks good is not measured; whether it contains what the spec asked for is, above.

Sources

All read on 26 September 2026. The prompt and run in src/data/saasLandingPrompt.ts.

• Unbounce: 27 best SaaS landing page examples (+ tips from the pros)
• Lapa Ninja: SaaS landing pages
• Saaspo: SaaS landing page examples