Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
Use this skill when the user asks to "analyze my funnel", "where are users dropping off", "funnel analysis", "conversion analysis", "activation funnel", "onboarding funnel", "purchase funnel", "what's my conversion rate", or has funnel data showing step-by-step drop-off rates and wants to diagnose where to focus.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:funnel-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are analyzing a conversion funnel to identify where users drop off, why they drop off, and what actions would most improve overall conversion.
Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".
Analyzes user conversion funnels, diagnoses churn causes, and generates optimization recommendations. Use when investigating registration, purchase, activation, or retention funnels.
Analyzes product funnels to identify drop-offs, diagnose low activation rates, design metrics frameworks, set up OKRs, and evaluate feature performance.
Share bugs, ideas, or general feedback.
You are analyzing a conversion funnel to identify where users drop off, why they drop off, and what actions would most improve overall conversion.
Framework: AARRR (Pirate Metrics — Acquisition, Activation, Retention, Revenue, Referral), Dave McClure's funnel stages.
Read memory/user-profile.md for product stage and business model. Read context/company/analytics-baseline.md for existing conversion benchmarks.
Ask the user to provide the funnel data. Accept in any format:
If the user describes the funnel without numbers, help them estimate or identify where to find the data.
From the funnel data, calculate:
Find the step with the highest combination of:
This is the "leaky bucket" — the one step that, if fixed, would most improve the entire funnel.
For each step with > 20% drop-off:
What happens at this step? (What does the user have to do?) Why do users drop here? (Likely causes — look for patterns in: UX friction, value perception, trust signals, cognitive load, technical issues) What would you need to know to fix it? (Qualitative insight from interviews? Quantitative data from heatmaps or session recordings? An A/B test?)
Common funnel drop diagnoses:
| Drop Location | Likely Cause | Diagnostic |
|---|---|---|
| Landing page → signup | Value prop unclear; sign-up friction | Session recording; copy test |
| Signup → first action | Onboarding too long; time to value too slow | Time to first action analysis; session replay |
| First action → second action | Not seeing value from first action | Interview: "what did you expect to happen?" |
| Free → paid | Paywall too early; wrong trigger; poor value communication | Behavioral analysis before upgrade prompt |
| Paid → renewal | Product not becoming habit; poor ongoing value | Cohort analysis; engagement depth |
For each major drop:
Recommend the top 1–2 improvements to try in the next sprint.
Produce: