Write Onboarding Copy

Draft conversion-focused CTAs and microcopy to guide users through a product flow or feature adoption.

Inputs

• Product or feature — the specific capability being introduced (e.g., "API key generation", "workflow templates"). Required.
• User segment — the persona or role experiencing onboarding (e.g., "first-time users", "power users enabling automation"). Required.
• Core benefit — the single strongest reason to engage (e.g., "saves 2 hours per campaign", "reduces manual data entry"). Required.
• Onboarding stage — which step in the journey (sign-up, first login, feature discovery, first action). Defaults to feature discovery.
• Tone preference — brand voice style (e.g., "friendly and playful", "professional and direct"). Defaults to your app's established tone.
• Conversion goal — desired outcome per microcopy (e.g., "click button", "complete setup", "share with team").

Steps

1. Map the onboarding touchpoints — list every screen, modal, email, and notification in the user's path.
2. Identify the core objection or concern at each step — what would cause a user to drop off?
3. Draft primary CTA copy (3-5 words) that names the benefit, not the button (avoid generic "Next" or "Submit").
4. Write supporting microcopy (1-2 sentences) that repeats the benefit and removes friction.
5. Test for clarity — read aloud; ensure no jargon assumes prior knowledge.
6. Review against your brand voice guide for tone, terminology, and perspective.
7. Propose A/B variants if the step is a known conversion bottleneck.

Constraints

• Keep all copy under 10 words per line; break longer thoughts into bullets.
• Avoid internal terminology or feature names users have not yet learned.
• Do not mention pricing, discounts, or limited-time offers unless explicitly part of the funnel.

Done when: copy is drafted for all onboarding stages, tested for tone consistency, and ready for design handoff.