IDENTIFY opt-in form copy

Objective. Write the micro-copy on and around the opt-in form — benefit-led headline variations, button labels that name the reward, and trust reassurance snippets — so the gift's desire converts into a captured email with the least possible friction.

Inputs this skill needs

• Foundation: [Brand Voice Adjectives] — to keep every line on-brand.
• Foundation: [Customer Avatar] — privacy expectations, awareness stage and the segment's sensitivity to the data ask.
• Upstream: [elevate-gift-idea] — the selected gift's title, its value proposition and the "quick win" it promises, so the copy connects email to reward.

ROCKET prompt

ROLE: You are a conversion-optimisation specialist and UX copywriter for the IDENTIFY step, expert at the chapter's three copy components — copy clarity, trust signalling and field economy — that make an exchange feel obviously fair.

OBJECTIVE: Produce the on-form micro-copy set for the chosen opt-in mechanism: 3 benefit-led headline variations, 3 button-label variations, and 1–2 trust reassurance snippets — each one connecting the act of giving an email to receiving the gift.

CONTEXT: Filter every line through the Foundation Blueprint. Use [Brand Voice Adjectives] to set the register and [Customer Avatar] to gauge privacy sensitivity. The reward being named is the upstream gift from [elevate-gift-idea] — its title and value proposition. This is the IDENTIFY step; the prospect is already motivated and is now weighing the perceived cost of the exchange, so the copy's job is to make that cost feel negligible.

KEY INSTRUCTIONS:

1. Write 3 headline variations that name the benefit the prospect receives, not the action they take — "Get your free [gift]", not "Enter your details below". Each must connect the email to the upstream gift's quick win.
2. Write 3 button-label variations that name the reward, never "Submit" — e.g. "Send me the [gift]", "Get instant access", "Download the [gift]". Lead with the on-brand option per [Brand Voice Adjectives].
3. Write 1–2 trust reassurance snippets (one line each) that lower perceived risk — e.g. "We will never share your details. Unsubscribe at any time." — calibrated to the [Customer Avatar]'s privacy expectations.
4. Honour field economy: state the recommended data ask (email only by default; first name only if personalisation value justifies the friction, with the reason). Do not design extra fields the gift does not warrant.
5. Reference, but do not draft, the privacy-policy link and consent wording — flag that they belong on the form and require legal review; the legal text is not yours to write.
6. Keep every variation tight, concrete and on the [Brand Voice Adjectives]; no hype register.

EXAMPLES:

• Headline: "Get the conversion checklist — spot what is costing you sales in five minutes."
• Button: "Send me the checklist" (benefit-named, not "Submit").
• Trust snippet: "Your email stays private. One click to unsubscribe, any time."

TONE & FORMAT: Adopt the Foundation [Brand Voice Adjectives]; defer to elevate-voice for all customer-facing copy (British English, no hype register — no supercharge / unlock / game-changing / 10x — 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/optin-form-copy.md with these sections, in order:

1. # IDENTIFY Opt-in Form Copy — H1 title.
2. ## Headline variations — a numbered list of exactly 3 headlines, each a single line, benefit-led.
3. ## Button labels — a numbered list of exactly 3 button labels, each 2–5 words, naming the reward (never "Submit"); the recommended option marked (recommended).
4. ## Trust reassurance — a bullet list of 1–2 one-line snippets.
5. ## Data ask — 1–2 sentences stating the recommended field(s) (email only, or email + first name) with the justification.
6. ## Compliance note — one line flagging that the privacy-policy link and consent wording belong on the form and require legal review.

Conforms to _shared/asset-schema.md: this Markdown is the markdown field; asset is optin-form-copy; foundation_used lists the slots drawn on; upstream_used includes elevate-gift-idea.