Fill in three fields, copy the prompt, paste it into a new Lovable project. Unedited, it built a working opt-in page with stored, duplicate-safe sign-ups for 1.8 credits in one round.
By Marco Kohns · Prompt written and run by us
# ContextBuild a single-purpose landing page: capture an email address before a product launches. The visitor arrives from one known traffic source, so the page carries one offer and one action, and nothing that competes with them. ## Core Features (Priority Order)1. Hero: the offer in one sentence, the form visible without scrolling2. Email capture writing to Supabase with UTM parameters stored per signup3. Inline success state replacing the form, no redirect, no alert4. Duplicate handling: resubmitting the same address confirms instead of erroring5. A substantive copy body below the fold: what it is, who it is for, three concrete FAQs ## Capture & Consent- Client and server-side email validation; the server is the one that counts- Store source, utm_source, utm_medium, utm_campaign and referrer on every row- One-line consent text under the form stating what will be sent and how to leave ## Copy & Conversion- One accent color, used by the submit button and nothing else- Proof elements are placeholders clearly marked as placeholders; never invent names or numbers- Maximum 65 characters per line of body copy; generous vertical rhythm ## Build OrderStatic page with final copy first, so something exists to index. Then the form and write path with duplicate handling, then UTM capture, then analytics last. ## Safe-Guard Instructions- The signups table accepts inserts and forbids reads from the client, with no exceptions for debugging- No second call to action anywhere on the page- The form must not lose the typed address on a validation error ## Before BuildingAsk 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.
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.
Measured run
Fresh Free-plan project, prompt pasted as is, no follow-up message. 31 July 2026.
Why each line is there
Lovable's design guidance says a landing page prompt that leaves the look open gets design questions first. This is what each section of ours does in practice, and what goes wrong when a line is missing.
With it
One page, one job, one known traffic source. Lovable wrote the headline for a launch list and added nothing that competes with the form.
Without it
Generic SaaS copy and a hero, three feature cards and a footer that look finished and convert nothing.
After the first build
Each one is a follow-up message in the same project. None is measured yet, so the cost shows a question mark.
Know which post or ad worked before you spend more on it. The UTM columns already exist.
Lovable creates a robots.txt with every project but not always a sitemap, per its SEO docs.
App emails need a paid plan and a verified domain, so the page confirms on screen first and the email is the second copy.
Only once traffic and the stats page exist. Before that, results are noise.
Launch checklist
0/7
Ticks stay on this page while it is open. Steps and plan rules from Lovable's docs, read 23 October 2026.
If it goes wrong
Cause: the backend was not enabled, or the form is not wired to a table. In our run Lovable enabled it on its own because the prompt named the write path.
Cause: the one-job rule got lost after a later message.
Cause: a proof section with no placeholder rule, or the rule was removed in an edit.
Cause: a tall hero or a long headline at 375 px.
Not quite your page?
Pro version · Organic SEO
The Pro version adds the channel section: the copy body expanded server-rendered with an FAQ that answers what your audience searches, a canonical tag, a title written for the query, and a share moment after sign-up. Unlocked in the bundle, with every other prompt and kit.
Yes. Our run used a fresh Free-plan project and cost 1.8 credits, inside the 5 daily credits Free gets; the credits panel read 3.20 of 5 left afterwards. A custom domain needs a paid plan, per Lovable's docs.
Into a signups table on Lovable's built-in backend, created on the first build. The prompt makes it write-only from server code, so the browser can never read the list. You export it from the database view or connect an email tool with a follow-up prompt.
Since Lovable added design guidance, a landing page with no stated look gets a question card with up to 4 questions on palette, typography and layout, each with up to 4 options, at no extra credit cost per the docs. Name your fonts and colours in the builder above, or connect a design system, and it builds straight away. Our July run predates the card and asked nothing.
Lovable's prompting guide says a full-page prompt gets you noise and a section-based prompt gets you signal. For a one-job opt-in page one message was enough: ours came back complete in one round because the prompt carries its own build order. Go section by section for a longer page with several offers.
It makes Lovable ask about the audience and the offer first and save the answers to project knowledge, so later prompts in the same project build on them. It was added to every library prompt on 26 September 2026. The 1.8-credit run predates it; on the two runs since, that closing line produced 2 and 4 questions before any code.
On a paid plan. Publish first, then either buy the domain in Lovable or add the A record to Lovable's edge and the TXT verification record at your DNS provider. Most changes go live within hours and the docs allow up to 72 hours. Then re-run the SEO and AI search review on the new domain.
Marco Kohns wrote the prompt and ran it on 31 July 2026 in his own Lovable workspace. The Pro version and the bundle are our own products. Lovable Prompts is independent and not affiliated with Lovable.
