What this prompt does
This prompt designs a full SaaS onboarding and activation framework that moves a new signup to their first value moment. You name [product_name], describe it, define the [aha_moment] and the [activation_window] to reach it, and give your [monthly_signups] and [plan_tiers]. ChatGPT then maps onboarding milestones, in-app guidance copy, a behavior-triggered email nurture, a stalled-user intervention system, an analytics dashboard, and persona-specific paths.
The variables shape how granular and personalized the flow is. [milestone_count] sets how many steps lead from signup to activation, each with success criteria and an expected completion rate that forms a natural funnel. [guidance_types] lists the in-app touchpoints to write copy for, [email_count] sets the nurture length, and [stall_milestone] plus [stall_threshold] define when to trigger help for users who get stuck. [retention_metric] connects onboarding completion to a downstream outcome, and [persona_count] produces separate paths for users with different goals and skill levels.
When to use it
- You are building the activation layer for a SaaS and want milestones mapped before designing screens.
- New users sign up but never reach first value and you need a structured path to the aha moment.
- You want exact in-app copy for tooltips, checklists, and contextual help written for you.
- You need a behavior-triggered email nurture that adapts to whether users progress or stall.
- You want a stalled-user intervention that fires automatically at a defined drop-off point.
- You need an onboarding analytics dashboard spec that ties completion to retention.
Example output
The response is an onboarding blueprint. It lays out [milestone_count] milestones from signup to activation, each with success criteria, the required user action, estimated time, and an expected completion percentage that forms a funnel. For each milestone it writes the in-app copy across your [guidance_types], then a parallel [email_count]-email nurture triggered by behavior, a stalled-user system that detects users stuck past milestone [stall_milestone] for [stall_threshold] days, an analytics dashboard tracking completion and its correlation with [retention_metric], and separate paths for [persona_count] personas.
Pro tips
- Define
[aha_moment]as concretely as possible — a fuzzy first-value moment produces a fuzzy milestone path. - Set
[activation_window]to a realistic target; an aggressive window pushes the framework to compress steps that may genuinely take longer. - Pick a
[stall_milestone]that matches where your users actually drop off, since the intervention only helps if it fires at the real bottleneck. - Keep
[email_count]restrained — a long nurture that ignores user behavior reads as spam and undercuts activation. - The expected completion percentages are estimates, not your real funnel, so replace them with measured rates once you have data.
- Run it once per major persona if your
[persona_count]users differ sharply in technical skill, rather than forcing one path to fit all.
