Onboarding Copy

Onboarding copy should lead with the user's outcome, not the product's feature list.

The current message structure:
❌ "Taskr is a powerful tool that helps you [feature list]"

Better structure:
✓ "[Your outcome]. Let's set you up in [X minutes]."
Example: "See exactly who's working on what — and ship projects on time. Let's create your first workspace."

Users at the welcome screen already know it's a PM tool — they just signed up. What they need is:
1. Confirmation they made a good choice (outcome reassurance)
2. A clear single next step (activation CTA)
3. A sense of how long it will take

Key vocabulary:
• Onboarding copy — UI text that guides users from signup to their first value moment
• Outcome framing — leading with what the user achieves rather than product capabilities
• Feature-led copy — the anti-pattern of listing features instead of user outcomes
• Activation CTA — the call to action that moves users to their first key action

Onboarding empty states must explain why it's empty AND provide a direct path to fill it.

The "no data yet" anti-pattern leaves users stranded — they don't know:
• Why it's empty
• What action they should take
• How long it will take

Good onboarding empty state formula:
1. Explain the cause clearly ("when you add your tracking code")
2. Provide one direct CTA that fills the gap
3. Reduce anxiety with time estimate ("5 minutes")

Option A — passive ("will appear once") — no clear action
Option B — developer-speak ("SDK installed correctly") — sounds like debugging, not onboarding
Option C ✓ — explains cause, links to action, time-boxes the effort
Option D — ("Waiting for data...") — implies passive waiting when there's actually an action required

Key vocabulary:
• Onboarding empty state — the first-time view of a dashboard or section before setup
• Cause explanation — copy that explains why the state is empty, not just that it is
• Time-boxing — communicating how long a setup step takes to reduce hesitation
• Activation step — the key action a user must complete to see their first value

Onboarding CTAs should be action-oriented and emotionally engaging — not generic system language.

Comparison:
• "Invite Users" — product-system language; "users" is an admin term, not how people think of their colleagues
• "Continue" — no information; could be anything
• "Add Team Members" — better, but still formal and transactional
• "Bring Your Team In" ✓ — human, collaborative, mirrors how people think about the action

For the "skip" path, "Skip for now" or "I'll do this later" is appropriate — "Skip For Now" in Option C would be a valid secondary action below the primary CTA, not the primary action itself.

Onboarding CTA language principles:
• Use human language over system language
• Mirror the user's mental model ("bring in" not "add")
• Create forward momentum ("Let's", "Bring", "Start")

Key vocabulary:
• CTA (call to action) — the button or link that drives the primary next step
• System language — vocabulary from the software's internal model (users, records, entities)
• Human language — vocabulary matching how people talk naturally about the action
• Momentum copy — onboarding language that creates a sense of forward progress

Permission coaching screens must give a specific benefit and address the fear of over-notification.

The OS permission prompt is high-stakes — once denied, it's hard to reverse. The coaching screen's job:
1. Make the value clear and specific ("don't miss important messages")
2. Pre-empt the main concern ("we'll only ping you for direct messages and urgent threads")
3. Build trust before asking

Options A and B — generic value propositions; "function correctly" is threat-based; "stay informed" is vague
Option D — just instruction; no benefit or reassurance
Option C ✓ — specific benefit + fear resolution + implicit commitment

Key vocabulary:
• Permission coaching screen — an in-app screen shown before a native OS permission prompt
• Permission priming — preparing users to accept a permission request with context and benefit
• Notification fatigue concern — users' fear of being spammed; must be directly addressed
• Benefit specificity — naming the exact use case rather than a generic benefit

Success states in onboarding should celebrate the milestone and immediately direct to the next activation step.

The "product saved" confirmation is a system message — it's not an onboarding moment. At this stage, the user needs:
1. Acknowledgment of the milestone
2. A clear picture of what's left before they get value
3. A direct next step

Option C does all three:
• "Your first product is live" — milestone acknowledged with outcome language
• "2 more steps to your first sale" — quantified remaining work
• Lists exactly what's next (concrete, not vague "set up your store")

Progress-to-value framing ("X steps to your first sale") is one of the most effective activation copy patterns in SaaS onboarding.

Key vocabulary:
• Milestone confirmation — copy that acknowledges the user completed a meaningful step
• Progress-to-value framing — quantifying remaining steps to the user's first valuable outcome
• Activation funnel — the sequence of steps from signup to the user's first value moment
• Next step nudge — a CTA or link that moves the user immediately to the next activation step