PLG Activation Funnel Diagnostic Builder

Diagnose where self-serve users stall between signup and activation, then turn the findings into a prioritized product-led growth action plan.

Prompt Template

You are a PLG analyst. Build an activation funnel diagnostic for the product below.

Product type: [SaaS or app]
Target user: [role or segment]
Activation definition: [the moment a user gets value]
Funnel steps: [signup, verify email, import data, invite team, create project, etc.]
Current conversion rates: [step-by-step if known]
Traffic sources or segments: [organic, paid, referral, enterprise trial, etc.]
Known friction points: [support tickets, drop-off steps, slow loading, unclear messaging]
Experiment constraints: [engineering time, analytics gaps, lifecycle tools]

Provide:
1. Funnel summary with likely choke points
2. Segment comparisons worth prioritizing
3. Behavioral signals that predict activation
4. Instrumentation gaps that reduce confidence
5. A prioritized action plan using impact vs effort
6. Recommended experiments with success metrics
7. A short narrative leaders can use in a growth meeting

Keep the analysis practical for a team that needs clear next experiments, not abstract theory.

Example Output

Funnel Summary

Signup to workspace creation is healthy at 78%, but only 29% of users complete the data import step, making it the main activation choke point.

Highest-Value Segment Cut

Paid social traffic converts to signup efficiently but activates at half the rate of referral traffic, suggesting lower intent or weaker onboarding fit.

First Experiments

1. Add a guided sample dataset path for users without data ready

2. Trigger a lifecycle email when import is abandoned for more than 2 hours

3. Reduce required fields in the import wizard

Leadership Narrative

Activation is not failing everywhere, it is failing in one sharp middle step. Fixing import friction should matter more than chasing more top-of-funnel traffic this month.

Tips for Best Results

  • 💡Define activation in behavioral terms, not vibes, so the funnel can be measured cleanly.
  • 💡Include segment differences by source or role because the average funnel usually hides the real problem.
  • 💡Ask for instrumentation gaps explicitly, bad tracking can waste a whole quarter of experiments.