Prompt Details
Model
(claude-5-opus)
Token size
2,262
Example input
[FUNNEL_DESCRIPTION]: Signup → email verification → 3-step onboarding checklist → first project created → hits free-tier project limit (3 projects) → upgrade prompt shown
[FUNNEL_DATA]: 68% complete email verification, 45% complete onboarding, 30% create a first project, of those only 12% ever hit the free-tier limit within 30 days, and of that group 22% convert to paid
[PRICING_MODEL]: Free tier: 3 projects, 2 collaborators. Paid tier: $12/user/month, unlimited projects and collaborators
[COMPETITIVE_CONTEXT]: Main competitor gates at 1 project instead of 3, reportedly converts at a higher rate but with more user complaints about being 'too limited too fast'
Example output
# Freemium-to-Paid Conversion Funnel Audit
## Product Name Not Specified — 3 Projects / 2 Collaborators Free, $12/user/month Unlimited
---
**Interpretive note (affects every card below):** `[FUNNEL_DATA]` states "68% complete email verification, 45% complete onboarding, 30% create a first project" as a sequential list. I've read these as cumulative percentages of the original signup cohort (standard funnel-reporting convention), not as step-over-step conversion off the immediately preceding step. This assumption is not confirmed by the data and materially affects the marginal drop-off math below — it's flagged again in Card 8.
---
### CARD 1 — EXECUTIVE SUMMARY
The strongest documented evidence points to a **distributed activation problem**, not a single bottleneck: email verification, onboarding, and first-project-creation each lose ~32–34% of the cohort still in play at that point, compounding so that only 30% of signups ever create a project at all. The single largest raw falloff in the funnel — only 12% of activated users hit the free-tier limit within 30 days — is real but its cause is not diagnosable from this data; it could reflect a value-gap, a free tier so generous it rarely binds, or simply normal usage volume. The pricing model itself does not look like a clear contributing factor: once users do hit the wall, 22% convert — the healthiest per-step progression rate anywhere in this funnel. Overall signup-to-paid conversion, by direct multiplication of the given figures, is under 1% (~0.79%) — a result of several moderate losses compounding, not one dominant failure point.
---
### CARD 2 — FUNNEL STEP MAP
| Step | Drop-off Evidence | Status | Friction Type |
|---|---|---|---|
| Signup → Email verification | 68% of signups complete verification (32% loss) | DOCUMENTED DROP-OFF | Usability / trust-gap (tentative — no cause data) |
| Email verification → Onboarding checklist | 45% of signups complete onboarding (≈33.8% of verified users drop at this step)* | DOCUMENTED DROP-OFF | Usability / value-gap (tentative — no cause data) |
| Onboarding checklist → First project created | 30% of signups create a first project (≈33.3% of onboarding-completers drop here)* | DOCUMENTED DROP-OFF | Value-gap (tentative — "activation energy" gap) |
| First project created → Hits free-tier limit (3 projects, ≤30 days) | 12% of first-project creators hit the limit within 30 days | DOCUMENTED DROP-OFF (severity contested — Card 3) | UNKNOWN — cannot distinguish value-gap / generous-gate / normal usage volume |
| Hits limit → Upgrade prompt shown | No isolated measurement | UNKNOWN | — (prompt-shown ≠ limit-hit isn't separately instrumented) |
| Upgrade prompt shown → Converts to paid | 22% of limit-hitters convert (78% decline) | DOCUMENTED DROP-OFF | Pricing-mismatch (tentative — no decline-reason data) |
*Marginal (step-over-step) figures depend on the cumulative-cohort interpretation noted above.
---
### CARD 3 — STEP-BY-STEP DIAGNOSTIC
**Step: Email Verification**
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Drop-off Severity | 3/5 | DOCUMENTED | 32% relative loss (100%→68%) — moderate |
| Data Confidence | 5/5 | DOCUMENTED DROP-OFF | Stated directly as % of signup cohort; unambiguous base |
| Friction Type Clarity | 2/5 | INFERRED FRICTION (type only) | No cause data; usability (deliverability/broken link) and trust-gap both plausible |
| Value-Price Alignment Index (OPERATIONAL EXTENSION — NOT A STATISTICAL MEASURE) | N/A | UNKNOWN | Pre-value stage; alignment isn't assessable before any product value is experienced |
**Step: Onboarding Checklist**
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Drop-off Severity | 3/5 | DOCUMENTED | ≈33.8% relative loss of verified users |
| Data Confidence | 4/5 | DOCUMENTED DROP-OFF | Hard number, but marginal rate rests on the cumulative-cohort assumption |
| Friction Type Clarity | 2/5 | INFERRED FRICTION (type only) | No detail on which of the 3 checklist steps causes drop |
| Value-Price Alignment Index (OPERATIONAL EXTENSION — NOT A STATISTICAL MEASURE) | N/A | UNKNOWN | Still pre-first-value |
**Step: First Project Created**
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Drop-off Severity | 3/5 | DOCUMENTED | ≈33.3% relative loss of onboarding-completers |
| Data Confidence | 4/5 | DOCUMENTED DROP-OFF | Same base-population caveat |
| Friction Type Clarity | 3/5 | INFERRED FRICTION (type only) | Completing onboarding but not creating a project points more specifically toward value-gap or creation-flow usability than the earlier steps do |
| Value-Price Alignment Index (OPERATIONAL EXTENSION — NOT A STATISTICAL MEASURE) | 4/5 | ALIGNED | The gate (3rd project) sits after this point — the first value-creation moment is fully ungated, unlike the competitor's 1-project cap |
**Step: Hits Free-Tier Limit (≤30 days)**
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Drop-off Severity | 5/5 | DOCUMENTED | 88% of first-project creators never reach this point in 30 days — the largest raw falloff in the funnel |
| Data Confidence | 5/5 | DOCUMENTED DROP-OFF | Explicitly stated as % of the first-project-creator cohort — no base ambiguity |
| Friction Type Clarity | 1/5 | UNKNOWN | Three materially different explanations fit equally well: (a) value-gap / low habitual engagement, (b) gate too generous to ever bind for most users, (c) genuinely normal usage under 3 projects. Data cannot distinguish these |
| Value-Price Alignment Index (OPERATIONAL EXTENSION — NOT A STATISTICAL MEASURE) | 3/5 | ALIGNED (tentative) | Not premature relative to value (contrast with competitor's tighter gate), but its rarity of encounter raises a separate monetization-coverage question — see Card 5 |
**Step: Upgrade Prompt Shown → Conversion**
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Drop-off Severity | 4/5 | DOCUMENTED | 78% of limit-hitters decline |
| Data Confidence | 5/5 | DOCUMENTED DROP-OFF | Explicitly stated as % of the limit-hitting cohort |
| Friction Type Clarity | 2/5 | INFERRED FRICTION (type only) | No decline-reason data; pricing-mismatch is the natural read for this moment but unconfirmed |
| Value-Price Alignment Index (OPERATIONAL EXTENSION — NOT A STATISTICAL MEASURE) | 4/5 | ALIGNED | 22% conversion once the wall is hit is the strongest per-step progression rate in the entire funnel |
**Core Friction Reading:** The best-evidenced pattern is not one bottleneck but a three-step activation cascade (verification → onboarding → first project), each losing ~33% and compounding to 70% pre-activation loss. The single largest number in the dataset — 88% non-progression to the paywall — is equally well-documented but carries the lowest friction-type clarity of any step; it should be treated as an open question, not a diagnosed problem, until instrumented further.
---
### CARD 4 — HIGHEST-LEVERAGE FIX CANDIDATES
1. **Activation cascade (email verification → onboarding → first project)** — tied top priority. Joint Data Confidence 4–5, consistent ~33% severity at each step, compounding to the largest total addressable loss in the funnel even though no single step is individually worse.
- Instrument/redesign email verification (deliverability check, consider magic-link)
- Usability-test the 3-step onboarding checklist to locate the specific abandon point
- Reduce "activation energy" for first-project creation (templates, pre-filled defaults)
2. **Habitual-use gap (12% reach the limit in 30 days)** — second priority, but the correct next move is the diagnostic experiment in Card 7, not a design fix. Friction Type Clarity is 1/5; building a fix before knowing the cause risks solving the wrong problem.
3. **Paywall conversion (22%)** — lowest priority for immediate change. This is the healthiest per-step number in the funnel; any pricing change here should wait on the decline-reason data flagged in Card 8 rather than being guessed at.
---
### CARD 5 — PRICING/GATING FIT CHECK
The 3-project gate is not premature: it sits after the first value-realization moment (project #1 created), unlike the competitor's 1-project cap. That avoids the "too limited too fast" complaint pattern reportedly seen there. But the same evidence shows the gate rarely binds — 88% of activated users don't reach it within 30 days — and the data can't say whether that's because the free tier is generous relative to genuine near-term needs, or because 30 days is simply too short a window to observe real usage. Separately, the **collaborator limit (2 collaborators) has no drop-off or limit-hit data at all** in what was provided — it's an entirely untested gating dimension that may be a hidden second path to the paywall for team-based users. Net: the gate's *placement* looks structurally reasonable, but its low bind rate is an open monetization-coverage question, not a confirmed misalignment.
---
### CARD 6 — COMPETITIVE CONTEXT NOTE
The competitor's 1-project gate reportedly converts higher but draws more "too limited too fast" complaints. Framed strictly as a hypothesis: tightening this product's gate might raise the paywall-encounter rate (currently just 12% within 30 days) and lift overall conversion volume — but it could also pull the gate back to before the first-value moment, recreating the exact complaint pattern attributed to the competitor. This is a hypothesis about gate-tightness trade-offs worth testing via controlled experiment (Card 7), not evidence that this product's users would behave the same way the competitor's do.
---
### CARD 7 — EXPERIMENTS TO RUN
| Hypothesis | Test | Success Metric |
|---|---|---|
| Onboarding drop-off is usability-driven | Session recordings/heatmaps on the 3-step checklist | Onboarding completion rate (baseline 45%) |
| Email verification drop-off is deliverability/trust-related | Audit deliverability logs; A/B test magic-link vs. code verification | Verification completion rate (baseline 68%) |
| First-project drop-off is an "activation energy" problem | A/B test templates/pre-filled defaults in project creation | % of onboarding-completers who create a project (baseline ~67%) |
| 3-project gate rarely binds because it's generous, not because users are disengaged | A/B test lowering the limit to 2 for a cohort | Paywall-encounter rate + complaint/churn rate vs. control |
| Collaborator limit is an untracked second paywall path | Instrument collaborator-limit hits as a distinct event | New metric: % of active users hitting the collaborator cap |
| 78% decline reasons are price-driven | Post-decline micro-survey or exit-intent prompt at the paywall | Distribution of stated decline reasons |
---
### CARD 8 — DATA GAPS
- No tracking of collaborator-limit hits (only project-limit is measured) — a plausible second, currently invisible paywall path.
- Ambiguity in whether 68% / 45% / 30% are cumulative-of-signup-cohort or step-over-step conversions; this audit assumed cumulative and flags the resulting marginal-rate calculations as dependent on that assumption.
- No qualitative data on *why* users drop at verification, onboarding, or first-project (usability vs. trust vs. value-gap remain inferred, not confirmed).
- No visibility beyond the 30-day window — unknown how many additional users would hit the project limit at day 31–90.
- No decline-reason data for the 78% who see the upgrade prompt and don't convert.
- No top-of-funnel (Awareness-to-Signup) data — pre-signup friction is entirely out of scope of what was provided.
- No segmentation (team size, use case, acquisition channel) that might explain variance across steps.
---
### CARD 9 — METHOD NOTE
This audit is a hypothesis-generation aid, not a definitive diagnosis — every friction-type label above is tentative unless marked otherwise, and should be treated as a prioritized list of things to test, not confirmed findings. It's grounded in the five-stage Funnel Friction Taxonomy, extended by the Value-Price Alignment Index (OPERATIONAL EXTENSION — NOT A STATISTICAL MEASURE), a structural read on gate placement that never substitutes for actual drop-off data. Competitive context (the competitor's 1-project gate and complaint pattern) was used only to generate a testable hypothesis about gate-tightness trade-offs in Card 6, never as evidence about how this product's own users would behave. The experiments in Card 7 are the mechanism for converting any hypothesis raised here into a confirmed finding — none of the above should drive an engineering or pricing decision on its own.
---
**VERDICT: MULTIPLE CONTRIBUTING FACTORS — a compounding ~33%-per-step activation cascade across email verification, onboarding, and first-project creation (leaving only 30% of signups activated at all), combined with a separate and evidence-ambiguous habitual-use gap in which just 12% of activated users ever reach the paywall within 30 days; the paywall conversion step itself (22%) is comparatively healthy and is not the primary lever here.**
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View SelectBy purchasing this prompt, you agree to our terms of service
CLAUDE-5-OPUS
🔁 Describe your funnel steps and whatever usage data you have, and get a 9-card conversion audit that ranks friction points by evidence strength — never by which step "feels" most important. Separates value-gap, trust-gap, usability, and pricing-mismatch friction (they need different fixes), and includes a structural read on whether your paywall sits before or after users actually feel the product's value. Ends with concrete, testable experiments, not vague growth-hack advice. 🧪
...more
Added over 1 month ago
