Prompt Details
Model
Chat - (gpt-5.4)
Token size
893
Example input
[PROBLEM_DOMAIN]: We can't retain users past the first 30 days of our SaaS product
[EXPERT_ROLE]: growth product manager
[INDUSTRY_CONTEXT]: early-stage B2B SaaS startup
[DEPTH_LEVEL]: investor pitch meeting
[OUTPUT_FORMAT]: one-page executive brief
Example output
Very well, sir. Initiating assumption deconstruction—expect some mild intellectual turbulence.
PHASE 1 — Naïve Genius Question Generation
A. Hidden Axioms
Why do we assume user retention is the correct success metric at all?
Disruption: 9 | Taboo: High | A
Why must users stay continuously active rather than return episodically when value is needed?
Disruption: 8 | Taboo: Medium | A
Why do we assume the product should adapt to users instead of users adapting to the product?
Disruption: 7 | Taboo: High | A
B. Inverted Assumptions
What if losing users after 30 days is actually the optimal outcome?
Disruption: 10 | Taboo: High | B
What if onboarding friction—not simplicity—is what drives long-term retention?
Disruption: 9 | Taboo: High | B
What if the product is too useful too quickly, eliminating the need to return?
Disruption: 8 | Taboo: Medium | B
C. Phantom Dependencies
Why do we assume feature expansion is necessary to improve retention?
Disruption: 8 | Taboo: Medium | C
Why must retention depend on product usage rather than external ecosystem integration?
Disruption: 9 | Taboo: Medium | C
Why do we assume user dissatisfaction is the cause of churn?
Disruption: 10 | Taboo: High | C
D. Temporal Blind Spots
Was this retention problem present at launch—or did we introduce it later?
Disruption: 7 | Taboo: Low | D
What changed between days 1–30 and day 31 in user perception of value?
Disruption: 9 | Taboo: Medium | D
Did early adopters behave differently—and are we ignoring that pattern?
Disruption: 8 | Taboo: Medium | D
E. Stakeholder Invisibility
Who benefits internally from focusing on acquisition instead of retention?
Disruption: 9 | Taboo: High | E
Do investors actually prefer growth optics over sustainable retention?
Disruption: 10 | Taboo: High | E
Are we optimizing for metrics that make us look good rather than reflect reality?
Disruption: 10 | Taboo: High | E
PHASE 2 — Deep Legitimization Analysis
1. Retention as the “correct” metric
Premise: Retention = value creation
Alternative: Product delivers high-value, one-time outcomes (e.g., solves a task completely) → monetized upfront
Innovation Path: Pricing model redesign → higher LTV per session → revenue per user
Cost of Avoidance: Misaligned roadmap; optimizing for activity instead of value
2. Continuous vs episodic usage
Premise: Frequent usage = success
Alternative: “On-demand SaaS” → users return only when needed but pay premium
Path: Usage pattern segmentation → retention redefined → repeat activation rate
Cost: False churn signals; wasted re-engagement spend
3. Product must adapt to users
Premise: User-centric flexibility is always optimal
Alternative: Opinionated workflow → stronger habit formation
Path: Constraint-driven UX → reduced decision fatigue → activation-to-habit conversion
Cost: Weak positioning; commoditization
4. Churn is optimal
Premise: Churn = failure
Alternative: High-throughput model → rapid solve → upsell next problem
Path: Lifecycle compression → faster revenue cycles → CAC payback time
Cost: Fighting natural usage curve; bloated product
5. Frictionless onboarding is best
Premise: Less friction = better retention
Alternative: Intentional friction → higher commitment (psychological buy-in)
Path: Qualification gates → higher-quality users → retention cohort lift
Cost: Attracting low-intent users
6. Too useful too fast
Premise: Immediate value is ideal
Alternative: Progressive value reveal → sustained engagement
Path: Feature gating → curiosity loop → session frequency
Cost: One-and-done usage
7. More features = better retention
Premise: Feature breadth drives stickiness
Alternative: Radical simplification → clarity → repeated usage
Path: Feature pruning → faster core loop → time-to-value
Cost: Cognitive overload; churn
8. Retention must happen in-product
Premise: Product is the retention channel
Alternative: Ecosystem lock-in (API, integrations, workflows)
Path: Integration-first strategy → switching cost → retention
Cost: Weak defensibility
9. Churn = dissatisfaction
Premise: Users leave because unhappy
Alternative: Users leave because job is done
Path: Job-completion mapping → expansion revenue → NRR
Cost: Misdiagnosed churn
10. Problem existed from start
Premise: Retention issue is inherent
Alternative: Introduced via feature/market shift
Path: Cohort time analysis → pinpoint regression → fix
Cost: Treating symptoms, not cause
11. Value drop after day 30
Premise: Value decays over time
Alternative: Value plateau due to missing second use case
Path: Secondary JTBD discovery → multi-use adoption → retention
Cost: Single-use ceiling
12. Early adopters ignored
Premise: Current users represent ideal customer
Alternative: Early adopters had stronger pain
Path: ICP recalibration → higher retention cohorts
Cost: Wrong audience scaling
13. Acquisition bias internally
Premise: Growth is neutral
Alternative: Incentives skew toward acquisition metrics
Path: KPI realignment → retention ownership → LTV/CAC
Cost: Organizational misalignment
14. Investor preference distortion
Premise: Investors prioritize retention
Alternative: Growth storytelling bias
Path: Dual-metric narrative → honest retention + growth → credibility
Cost: Strategic dishonesty
15. Vanity metrics optimization
Premise: Metrics reflect reality
Alternative: Metrics are performative
Path: North star redefinition → true value metric → product focus
Cost: Illusion of progress
PHASE 3 — Executive Synthesis
Top 3 Disruptive Questions
1. “What if losing users after 30 days is optimal?”
This reframes churn from failure to signal. In certain B2B SaaS contexts, rapid job completion may indicate strong product-market fit. The strategic shift: monetize outcomes, not duration.
2. “Why do we assume churn = dissatisfaction?”
A critical diagnostic flaw. If users leave because their problem is solved, retention strategies must pivot from “keep them” to “expand them.”
3. “Are we optimizing for metrics that make us look good?”
This exposes organizational self-deception. Retention may be artificially framed to satisfy investors rather than reflect real user value.
2×2 Priority Matrix
High Impact / Easy
Q11 (Value drop after day 30)
Q10 (When did problem start?)
High Impact / Hard
Q4 (Churn is optimal)
Q9 (Churn ≠ dissatisfaction)
Q15 (Vanity metrics)
Q14 (Investor bias)
Low Impact / Easy
Q7 (Feature expansion)
Q12 (Early adopters)
Low Impact / Hard
Q3 (User adapts to product)
Q5 (Friction onboarding)
Q8 (Ecosystem retention)
Q6 (Too useful too fast)
Q1, Q2, Q13
Recommended Next Steps
Churn Reclassification Audit (Q9)
→ Segment churn into “problem solved” vs “failed experience”
→ Metric: % of “successful churn”
30-Day Value Cliff Analysis (Q11)
→ Identify missing second use case
→ Metric: % users adopting secondary workflow
Lifecycle Compression Experiment (Q4)
→ Test outcome-based pricing
→ Metric: Revenue per user vs retention rate
Sacred Cow Register
“Retention is always good”
“Churn equals failure”
“More features increase stickiness”
“Frictionless onboarding is universally optimal”
“Investors want sustainable metrics over compelling narratives”
“Usage frequency equals value delivered”
If I may, sir—your “retention problem” may in fact be a business model misinterpretation disguised as a product flaw.
Shall we proceed to designing a retention architecture—or dismantle it entirely and rebuild around outcome extraction?
By purchasing this prompt, you agree to our terms of service
GPT-5.4
Unlock breakthrough thinking by asking questions experts are afraid to ask. This prompt generates 15 laser-targeted "naïve genius" questions that expose hidden assumptions killing your strategy — then transforms each into a deep innovation pathway. Includes a Priority Matrix, Sacred Cow Register, and executive-ready synthesis. Just fill in 5 variables. Works for any industry, role, or problem. Think differently. Win differently.
...more
Added 2 days ago
