IDENTIFY lead-capture page

Objective. Assemble the lead-capture page as a straight line from arrival to completed form — recommended mechanism, on-page section flow, and the trust signalling and field economy that make the exchange feel obviously fair.

Inputs this skill needs

• Foundation: [Brand Voice Adjectives] — to keep the page copy on-brand.
• Upstream: [elevate-gift-landing-headline-bullets] — the gift landing-page headline and benefit bullets, which this page wraps a capture form around.

ROCKET prompt

ROLE: You are a conversion-optimisation specialist for the IDENTIFY step, expert in the chapter's fourth anatomy component — structural flow — and in choosing the capture mechanism (inline form, two-step, chatbot) that fits the offer and traffic.

OBJECTIVE: Produce a section-by-section layout for the lead-capture page: a recommended mechanism with its rationale, the on-page flow from headline to form to confirmation, and the trust signalling placed where the prospect feels the perceived cost.

CONTEXT: Filter every decision through the Foundation Blueprint, using [Brand Voice Adjectives] to set the page's voice. The page is built around the upstream gift landing copy from [elevate-gift-landing-headline-bullets] — reuse its headline and benefit bullets; this skill adds the capture mechanics, not new gift selling. This is the IDENTIFY step: the ideal path is a straight line — the prospect arrives motivated, sees the form immediately, the form asks for as little as possible, and the button labels the reward. Every extra decision point carries a probability of loss.

KEY INSTRUCTIONS:

1. Recommend one capture mechanism — inline form, two-step (button reveals form), or chatbot — and justify it against the gift type and likely traffic temperature. Default to inline form when in doubt.
2. Lay out the page top to bottom: hero (reusing the upstream gift headline and bullets), the form placement, the trust block, and the confirmation/thank-you state. Keep it a straight line — flag and remove any avoidable extra step.
3. Apply field economy: email only by default; first name only if justified. Specify the benefit-labelled button (never "Submit") in the form block, deferring full button-label variations to the optin-form-copy asset.
4. Place trust signalling deliberately — a one-line privacy reassurance beneath the email field and a visible privacy-policy link — because their absence is noticed even when their presence is not.
5. Specify the confirmation state: what the prospect sees after submitting, and the note that the welcome/delivery email and tracking pixel fire here.
6. Reference the single vs double opt-in decision as a documented choice for the page (per the chapter's decision table) without re-litigating it; name which the page assumes and why.

EXAMPLES:

• Mechanism rationale: "Inline form — warm traffic, evidently valuable gift; the extra click of a two-step adds friction without a reactance problem to solve."
• Flow line: hero headline + bullets → inline form (email + benefit button) → privacy reassurance + policy link → thank-you state with delivery confirmed.
• Confirmation state: "Check your inbox — your [gift] is on its way" + note that the tracking pixel fires here.

TONE & FORMAT: Adopt the Foundation [Brand Voice Adjectives]; defer to elevate-voice for all customer-facing copy (British English, no hype register, no fabricated stats, em-dashes welcome, exclamation marks not). Output as structured Markdown under the headings in the Output contract.

Output contract

Write Markdown to companies/<slug>/playbook/3-identify/lead-capture-page.md with these sections, in order:

1. # IDENTIFY Lead-Capture Page — H1 title.
2. ## Recommended mechanism — 1–2 sentences naming the mechanism (inline form / two-step / chatbot) and the rationale.
3. ## Page flow — a numbered list of the page sections top to bottom (hero, form, trust block, confirmation), each with a one-line description; the hero reuses the upstream gift headline and bullets.
4. ## Form block — the field(s) requested (email, or email + first name with reason), the benefit-labelled button, and the one-line privacy reassurance + privacy-policy link placement.
5. ## Confirmation state — 1–2 sentences on what the prospect sees after submitting, plus a note that the welcome/delivery email and tracking pixel fire here.
6. ## Opt-in type assumed — one line stating single or double opt-in for this page and the reason.

Conforms to _shared/asset-schema.md: this Markdown is the markdown field; asset is lead-capture-page; foundation_used lists the slots drawn on; upstream_used includes elevate-gift-landing-headline-bullets.