Write Optin Page

---
name: write-optin-page
description: Write an opt-in page — a page that sells the opt-in itself, trading one specific free thing for an email and doing nothing else. Titles first, then the sections. TRIGGER when a page's job is to grow a list by trading for a lead magnet. DO NOT TRIGGER for a page that closes a paid offer (write-sales-page), a page that lists several offers or pages (write-catalog-page), or a standalone headline or lead (write-headlines, write-leads).
---

# Write Opt-in Page

One Process: the opt-in page sells the free thing, not the product — design the short title chain first, then write the compressed sections that trade a specific, instantly-useful magnet for an email.

Write under the plan's Reader.md, Brief.md, and Proof.md, and the product's Voice.md, which names the WHO speaking; the page speaks in that one voice to Reader.md's Audience — the named buyer whose wanted quick win the magnet trades on, never a generic reader. Never assume an offer mechanism the owner has not approved, and never invent a subscriber count, testimonial, or result.

## 1. Design the title chain before any body

The chain follows the structure readers expect for an opt-in page; creativity lives in the words, not the skeleton (the expected-structure ruling in write-sales-page governs here too). The opt-in skeleton: compressed hero (headline = the magnet plus its one benefit) → mockup of the deliverable (a design requirement) → 3-5 bullets of what they get → single-field form (email only) with a benefit-CTA → one line of social proof. No nav, no footer, no product pitch.

Each title is standalone and true out of context; proof and reassurance slots take the reader's own first-person carried question, never a page-voiced "you" question.

## 2. Write the bullets as fascinations

Each "what you get" bullet names one wanted payoff and withholds the one piece needed to claim it, so curiosity pulls the reader to the form. One benefit and one open loop per bullet; vary the patterns; strongest bullets at the edges. Keep every loop honest — it closes on something the magnet actually delivers, never a tease the deliverable cannot honor.

## 3. Sell the magnet, promise the quick win

The magnet promises instant gratification — a quick win the moment they open it. The CTA says what they get ("Send me the teardown"), never "Submit". One field beats two: never ask for name, company, and role before the reader has received anything. Strip every exit so the only move is the trade.

## 4. Hold the bar

Fifth-grade words, one read. No metaphors, no metaphorical verbs. Be specific. Punctuate for consumption. Never narrate the reader — no "you"-assertion of what they do or have; reference the reader only through a first-person carried question, a subordinate time clause of visit-proven behavior, a generic subject, or the approved possessives. Express the mockup, and any enumeration a visual carries better, as a design requirement (the named visual plus its copy strings), never a prose list. Every section also carries a layout block in Wireframe.md — section shape, element placement, and CRO notes (CTA size and prominence, above-fold rules) — per the wireframe format in [../write-sales-page/references/wireframe.md](../write-sales-page/references/wireframe.md); copy owns where things go and why. Once the copy is locally clean, the writer wireframes the finished page into Wireframe.md as a production output.

Verification: the bare title chain reads as one trade for one free thing; the page sells the magnet and never pitches the product; every bullet opens an honest loop; no unpermitted fact appears.