Prompt · Intermediate

Prompt for a SaaS landing page

Create a product landing page with a concrete audience, defensible claims, understandable pricing, and an honest signup state.

Author: Editorial team
Reviewer: Publication review pending
Review tier: 90-day

Version 1.0.0 · complete-websites

Variables

[PRODUCT_NAME] · Product name: The verified public product name. Required.
[USER_JOB] · User job: The concrete task the product helps complete. Required.
[SIGNUP_STATE] · Signup state: Whether signup, waitlist, or demo is actually available. Required.

Expected output

Claim Inventory
Hierarchy
Components
Files
Audit

Common failures

Fabricated metrics
Fake logos
Unclear pricing period

Compatible modes: Chat, Agent, Ide Assistant

Build an original landing page for [PRODUCT_NAME]. Its audience needs to
[USER_JOB]. The actual conversion state is [SIGNUP_STATE].

First return a claim inventory with evidence supplied, unsupported claims,
missing product facts, page hierarchy, and component list. Do not invent user
counts, savings, integrations, customer logos, security certifications,
testimonials, or performance metrics.

Use semantic HTML, mobile-first CSS, and minimal progressive behavior. Explain
the problem, mechanism, concrete benefits, limitations, pricing or availability
when known, and one honest primary action. The action must reflect
[SIGNUP_STATE] and must not pretend an unavailable flow works.

Meet keyboard, focus, contrast, reduced-motion, responsive, performance, and
crawlability requirements. Return complete files and an evidence, action-state,
accessibility, and mobile audit.

Complete prompt

Build an original landing page for [PRODUCT_NAME]. Its audience needs to
[USER_JOB]. The actual conversion state is [SIGNUP_STATE].

First return a claim inventory with evidence supplied, unsupported claims,
missing product facts, page hierarchy, and component list. Do not invent user
counts, savings, integrations, customer logos, security certifications,
testimonials, or performance metrics.

Use semantic HTML, mobile-first CSS, and minimal progressive behavior. Explain
the problem, mechanism, concrete benefits, limitations, pricing or availability
when known, and one honest primary action. The action must reflect
[SIGNUP_STATE] and must not pretend an unavailable flow works.

Meet keyboard, focus, contrast, reduced-motion, responsive, performance, and
crawlability requirements. Return complete files and an evidence, action-state,
accessibility, and mobile audit.

Common AI mistakes

Watch for synthetic customer logos, vague feature cards, “save 10 hours” claims without evidence, and annual pricing shown without its billing basis.

Follow-up prompts

Ask for a claim table mapping every benefit to supplied evidence or an explicit placeholder.