🎯 Design
Landing Page Wireframe in Words: Sections, Copy, and CTA Stack
Describe a landing page as a section-by-section wireframe in words: layout, copy blocks, CTAs, and what not to put above the fold.
0Reviews
Prompt
Act as a product designer and conversion writer describing a landing page as a wireframe in words. No Figma. No screenshots. A developer or designer should be able to build from the sections. Inputs: - Product: [Product] - Audience: [Audience] - Primary CTA: [CTA] - Secondary CTA: [Secondary] - Proof I can use: [Proof] - Objections: [Objections] - Brand constraints: [Brand] - Device priority: [Desktop / mobile / both] - Must include / must not: [Must] - Competitors' pages I can describe: [Competitors] Generate: 1. Page job: one sentence. One primary CTA. What "done" is. 2. Fold (mobile first if both): 8-12 lines on what is on the first screen: heading, sub, proof chip, CTA, what is NOT here (pricing table, 6 logos, a video that autoplays). 3. Section list (in order): for each section: name, purpose, layout in words (1 col mobile, 2 col desktop if needed), copy blocks (headline, 3 bullets max, CTA or none), component notes (accordion, quote, form fields). 7-10 sections typical. 4. Copy: write the actual headlines and CTA labels, not lorem. Use only Proof. If a number is missing, do not invent it. 5. CTA stack: where the primary repeats (fold, mid, end). Secondary placement. What happens on click (URL or modal) if known; else "unknown, do not fake." 6. Objection handling: map Objections to a section. Do not hide price if Must says to show it. 7. Don'ts vs Competitors: 5 things those pages do that we will not copy, based only on described patterns. 8. Annotation for design: spacing rhythm (8px grid), type role (H1 once), image slots (what to photograph, not stock "team laughing"). Constraints: - Words, not ASCII art unless a simple 3-line box helps. - No fake testimonials or logos. - Honor Must. - One H1. Primary CTA label stays identical every time it appears. - This is a landing wireframe, not a full UI design system.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Product: BatchNotes, changelog tool for ops at 20-200 person companies Audience: ops leads tired of "what's new" tickets Primary CTA: Start Friday changelog (free) Secondary CTA: See a live example Proof I can use: 16-week Friday habit story from one 3-person team; waitlist-to-paid 4% to 7% on that team; we will not claim "thousands of customers" Objections: another tool to update; looks like build-in-public social; will it post to X by default Brand constraints: navy/paper, dry voice, no rocket Device priority: both, mobile first Must include / must not: must show that X auto-post is off unless Zap; must not use fake logos; must not autoplay video Competitors' pages I can describe: a social "build in public" hero with a feed screenshot; a generic purple SaaS with 6 logo clouds and "AI-powered"
Example Output
1. Page job Convince an ops lead to start a Friday changelog in BatchNotes. Done: click Start Friday changelog (free). One primary CTA. 2. Fold (mobile) H1: Ship a Friday changelog your team will actually keep. Sub: For ops leads. A page, an email, a time. Not a social feed. Proof chip: One 3-person team: 16 Fridays, waitlist-to-paid 4% to 7%. Not a customer-count claim. Primary button: Start Friday changelog (free) Text link: See a live example Not on fold: logo cloud, pricing grid, autoplay video, AI sparkle, rocket. 3. Sections S1 Fold: as above, 1 col mobile; desktop H1+form left, static product shot right (changelog list, not a feed). S2 How Friday works: 3 steps (write 3 bullets, pick Friday 10am workspace time, publish). No CTA. S3 Not a social product: 2 col. Left: we do not auto-post to X unless a Zap is connected. Right: contrast vs a feed UI. S4 Proof: the 16-week story, 4% to 7%, team of 3, no ads. Quote only if we have one (we do not: skip fake quote). S5 Objections accordion: time, "another tool," X posting. S6 Example: screenshot slot of a real changelog page. Secondary CTA repeats. S7 Close: repeat H1 in H2 form "Keep Friday." Primary CTA again. Footer legal. 4. Copy H1: Ship a Friday changelog your team will actually keep. H2 How: Three bullets, one time, publish. H2 Not social: Publishing does not post to X unless you connect a Zap. H2 Proof: 16 Fridays. 4% to 7% waitlist-to-paid. Team of 3. Accordion labels: "How long does this take?" "Is this another feed?" "Will this tweet?" CTA label always: Start Friday changelog (free) 5. CTA stack Primary: fold, S7. Secondary: fold + S6. Click target unknown: do not fake a URL. Same label every primary. 6. Objections Another tool -> S5: it replaces the "what's new" ticket, not your docs home. Social fear -> S3 + accordion. X default -> S3 explicit Zap line. 7. Don'ts vs competitors No fake logo cloud. No purple AI-powered. No feed-as-hero. No autoplay. No rocket. 8. Annotation 8px grid. One H1. Buttons 44px min height. Image: real changelog list on paper/navy, not stock high-fives. Mobile: CTA sticky optional at 600px, same label.