SaaS landing page prompt: six sections, run in Lovable, with what it built
A SaaS landing page has one job: turn a visitor from one traffic source into a trial sign-up. The prompt below specifies it in six sections, from an outcome headline to a final call to action, with pricing read from one config. I ran it unedited in my own workspace on 26 September 2026: Lovable asked 5 questions, built the page in six minutes and used 4.5 credits. Every section was checked against the raw HTML.
By Marco Kohns · Run 26 September 2026; docs read 23 October 2026
4.5credits
56.9 before, 52.4 after, read from the balance.
5questions
Asked before any code: the offer, the plans, the lead pain, the brand, the look.
6minutes
From the start of the build to a finished preview, 19:22 to 19:28.
The spec
What should a SaaS landing page contain, section by section?
Six sections, one action. Everything else on the page competes with the sign-up.
| Section | What it contains |
|---|---|
| Hero | An outcome headline, one sentence of how, one call to action, a proof line marked as a placeholder |
| Problem | Three pains in the visitor's words, then the product as the answer |
| Features | Each a heading in the form [result] without [cost], one sentence, a fixed-ratio screenshot slot |
| Pricing | Two or three plans read from one config object that also drives the comparison table |
| FAQ | Six questions that stall a sign-up, with FAQPage structured data |
| Final CTA | The hero's action again, nothing new |
The prompt
What is the SaaS landing page prompt?
The version run on 26 September 2026, unedited, so the results below belong to it. Replace Cadence and the audience with your own.
As run, 26 September 2026
# 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 - A 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.
Since 8 October 2026 Lovable builds the look from the prompt and asks design questions only when it is left open (design guidance, read 23 October 2026). The run below still showed a design picker. To skip that question, add a style direction with fonts and colours, as the library prompts now do; the prompting guide has the sections.
Measured
What did Lovable build from the prompt?
Five questions, then the page. Each claim below was checked in the HTML the preview served on 26 September 2026.
| # | Question and answer |
|---|---|
| 1 | What exactly does the sign-up give them? 14-day free trial, no card (the default) |
| 2 | How should the plans be structured? Two plans, Team and Business (the default) |
| 3 | Which pain should the page lead with? Calendar lives in scattered spreadsheets (the default) |
| 4 | Any brand details I should use? Left blank, so it picked placeholders |
| 5 | Which design direction should I build? Two rendered mockups offered; the first, Newsroom grid planner, selected |
| Check | Result |
|---|---|
| Server-rendered copy | Yes: the raw HTML fetched from the signed-in tab is 39,298 bytes with one h1 containing the headline text, one ld+json block and one table; anonymous requests get 401 because previews are private |
| Title, description, canonical, Open Graph | All present; title "Cadence, one shared content calendar for your team", canonical pointing at the preview URL |
| Hero: outcome headline, one sentence, one CTA, proof placeholder | "Every piece of content, on one shared grid.", one sentence of how, one button, and a proof line that reads as a placeholder |
| Problem block, three pains in the visitor's words | H2 "The calendar lives in scattered spreadsheets." with three H3s: no single source of truth, deadlines surface too late, ownership is fuzzy |
| Features as [result] without [cost] | Three H3s in exactly that form, e.g. "Spot conflicts without a weekly status meeting"; three 1280x720 image slots with a fixed aspect ratio |
| Pricing: two plans plus a comparison table | Team and Business cards and a table inside an overflow-x-auto container; whether both read one config object was not checked in the code |
| FAQ: six questions with FAQPage schema | Six questions, one FAQPage ld+json block |
| One CTA type only | Four buttons on the page, all Start free trial or Start 14-day free trial; no form, no newsletter box, no chat widget |
| Body copy length | 394 words on the page: enough to convert, thin to rank; the ranking job belongs to the SEO landing prompt |
Next to the other runs
How does a landing page compare with the other measured Lovable runs?
A capture page is the cheapest build; a page with pricing and a FAQ sits between it and an app foundation.
| Run | Credits | Questions first |
|---|---|---|
| Landing page + email opt-in | 1.8 | 0 |
| SaaS landing page (this page) | 4.5 | 5 |
| Empty states and skeletons | 9.5 | 2 |
| SaaS MVP with user auth | 10.4 | 4 |
Your version
How do you adapt the SaaS landing page prompt to your product?
Change four things and keep the rest; the rest is what made the run come back in one round.
- 01
The product and visitor
Replace Cadence, the audience and the traffic source in the Context paragraph. - 02
The three pains
In your visitor's words, from support emails, calls or the threads where they complain. - 03
The plans
Names, prices and limits in the pricing config, so the comparison table reads the same object. - 04
The look
A named style direction, fonts and hex colours, so Lovable builds without asking about design.
One word in the prompt shown above differs from the run: the adjective before title was replaced with A, because this site's style rules ban it. Nothing else was changed.
More landing page prompts
Disclosure: if you create a Lovable account through links on this page, we may earn a commission. It costs you nothing and does not change what we recommend. Create a free Lovable account
Frequently asked
What should a SaaS landing page include?
A hero with an outcome headline and one call to action, three pains in the visitor's words, features written as results, pricing from one config, six FAQs with structured data, and the same call to action at the end. One action on the whole page.
How much does a SaaS landing page cost to build in Lovable?
My run of this prompt used 4.5 credits on 26 September 2026, after Lovable asked 5 questions, and took six minutes from start to preview.
Does the page Lovable builds rank on Google?
The run served its copy in the HTML with a title, description, canonical, Open Graph tags and FAQ structured data. At 394 words it is built to convert; a page meant to rank needs a longer body, which the SEO content landing prompt adds.
Why only one call to action?
Every second action takes clicks from the sign-up. The prompt's safe-guards forbid a newsletter box, a chat widget and exit popups, and the run came back with four buttons, all starting the free trial.
Will Lovable ask about the design?
If the prompt leaves the look open, yes: since October 2026 Lovable asks design questions about colour, typography and layout. Name a style direction, fonts and hex colours in the prompt and it builds directly.
Can I use this prompt for a non-SaaS product?
Keep the structure and swap the pricing section for whatever the visitor decides on, such as a booking, a quote or a download. For a local business site, the small business website prompt in the landing page category fits better.
What we did not publish
- A re-run of the prompt revised to the 23 October standard; the page shows the run of the version above.
- Conversion rates; the page was never sent traffic.
- Whether both pricing views read one config object; the code was not inspected.
Sources
- My run, 26 September 2026, Marco's own workspace
- Lovable docs: Design guidance, read 23 October 2026
Written by
Marco Kohns
Founder of ProtoBites - Venture Growth Studio
Growth PM at a Silicon Valley scale-up (a16z and General Catalyst backed), ex-Techstars where he consulted 13 early-stage startups, Reforge-trained. Every prompt on this site comes out of shipping ProtoBites' own portfolio products.
Related reading
- landing page prompts by traffic source · The opt-in, pricing and SEO prompts this one borrows from.
- landing page kit · The leads table with an insert-only policy.
- three prompts and what they built · The other measured runs.
- Lovable pricing and credits · Plans read today and what one prompt costs in credits.
- Lovable SEO · Crawler evidence for generated pages.
- how to write Lovable prompts · The shape this prompt follows.
- app ideas · Fifty ideas that need a page like this.
- first 100 users · Where the visitors come from.
- product-channel fit · Why the page serves one source.
- Lovable SaaS prompts · The product behind the page.
- SaaS ideas · Fifteen SaaS ideas to point this page at.
- how to build an MVP · The whole day's build this page ends, as one ledger.
- build a SaaS · The landing page as step four of building a SaaS.
- the one-form opt-in page prompt · The shorter capture page, run for 1.8 credits.