onboarding-web2app-funnellisted
Install: claude install-skill ua5er/user-acquisition-skills
# Onboarding and web-to-app funnel design
Produces a small set of distinct onboarding concepts, each with a clear hypothesis, so a team tests ideas and not just visual variants.
## When to use
- Drop-off between install (or ad click) and paywall is high.
- The onboarding is a tour of features and does not sell the outcome.
- A move from app-first to a web funnel with payment before install is being considered.
- A designer or an AI design tool needs a brief with real constraints.
## Inputs
1. Product in one sentence and the aha moment: the first moment a user feels the product works.
2. Traffic sources and the promise of the ads that feed the funnel.
3. Current flow: screens, steps, where users leave (user's own funnel data).
4. Constraints: store rules, tracking events needed, payment stack, markets, languages, permissions needed.
5. What already ran as tests, and the result.
## Method
### Step 1. Map the current flow
List every screen with its job, the data collected, and the event fired. Mark screens with no job. Mark where the first value is shown and where the first payment ask appears.
### Step 2. Choose the strategic question
Pick one: should value come before the ask (demo-first), should the user invest effort first (quiz and personalisation), should the flow mirror the ad (story-first), should the user build something that the paywall then unlocks (profile or result-first). One question per concept set.
### Step 3. Generate concepts
Create 3 to 5 concepts