measuring-product-market-fit▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Framework-based assessment of product-market fit using signals from 46 product leaders.
- ›Apply the Sean Ellis \"very disappointed\" survey as a leading PMF indicator, targeting 40% threshold before long-term retention data is available
- ›Diagnose stage through retention curves, reference customer counts, and customer pull signals; distinguish between vanity metrics and genuine PMF evidence
- ›Recognize PMF across four levels (nascent to extreme) with segment-specific fit; understand that P
Measuring Product-Market Fit
Help the user assess and achieve product-market fit using frameworks from 46 product leaders.
How to Help
When the user asks about product-market fit:
- Understand their stage - Ask how many customers they have, what their retention looks like, and what signals they're seeing (or not seeing)
- Diagnose the situation - Determine if they're confusing vanity metrics with PMF, if they have PMF in a specific segment, or if they're clearly pre-PMF
- Apply the right framework - Help them use the Sean Ellis survey, retention curves, or reference customer counts depending on their situation
- Guide next steps - Help them decide whether to scale or continue iterating based on the evidence
Core Principles
Use the Sean Ellis "disappointment" survey
Sean Ellis: "How would you feel if you could no longer use this product? Very disappointed, somewhat disappointed, or not disappointed. If 40% say 'very disappointed,' you're on the right track." This is a leading indicator of PMF before long-term retention data is available. Focus on the "very disappointed" segment as your core value indicator.
Retention is the ultimate metric
Uri Levine: "Product market fit has one metric. Retention. If you create value, they will come back. If they're not coming back, you're not creating value." Look for retention curves that flatten over time rather than decaying to zero. The "smile curve" - where engagement increases over time - is the strongest signal.
PMF is obvious when you have it
Matt MacInnis: "Product market fit is something where you absolutely know it when you see it. Therefore if you don't absolutely know it, you don't have it." If there's doubt, you likely don't have it. Look for the market pulling the product out of your hands.
PMF is not static - it can be lost
Casey Winters: "Protecting what you've built is increasingly important once you build scale. You might fall out of product market fit in a year or five years if you're not continually making your product better." Markets shift, competitors improve, and user expectations rise.
Reference customers validate PMF
Christian Idiodi: "The holy grail is really a reference customer - somebody who loves it enough to tell people about it. I want 6-8 references for B2B, 15-25 for B2C as an indication of PMF." Don't launch publicly until you have secured the target number of references from early users.
PMF exists in segments, not universally
Karri Saarinen: "The way we think about it is, 'Do we have the fit in specific segments?' and how strong that fit is." Find PMF in one segment first (e.g., early-stage startups) before expanding. Double down where you see natural pull.
PMF requires distribution, not just retention
Casey Winters: "If you have a product that retains well and you can't find more users for it, I don't think that's product market fit." True PMF requires both a retaining product AND a scalable, built-in distribution mechanism.
PMF is multi-stage, not binary
Todd Jackson: "There's essentially four levels: nascent, developing, strong, extreme." Level 1 (3-5 customers), Level 2 (5-25 customers), Level 3 (25-100 customers), Level 4 (100+ customers). Sequence focus: satisfaction at Level 1, demand at Level 2, efficiency at Level 3.
Look for customer "pull"
Raaz Herzberg: "We felt the questions change - 'How are you pricing this? When can we start a POV?' That's real intent." True pull is characterized by customers driving next steps, not just saying "this is interesting."
A lack of outrage during outages = no PMF
Jeff Weinstein: "During those 20 minutes our customers weren't furious. That was the signal we did not have product market fit." If your product goes down and nobody notices or complains, you haven't solved a mission-critical problem.
Questions to Help Users
- "If users couldn't use your product anymore, what percentage would be 'very disappointed'?"
- "What does your retention curve look like at day 7, 30, and 90?"
- "Do you have customers willing to be references and tell others about you?"
- "Is the market pulling the product from you, or are you pushing it on them?"
- "Are customers driving next steps (asking about pricing, timelines) or just being politely interested?"
- "What specific segment do you have the strongest fit in?"
Common Mistakes to Flag
- Confusing launch spikes with PMF - Product Hunt success or press coverage doesn't mean you have PMF. Look for sustained organic growth
- Ignoring retention data - If users aren't coming back, you don't have PMF regardless of how many you acquire
- Scaling too early - Paid growth before PMF just burns cash and can damage your brand
- Conflating TAM with PMF - A large market opportunity doesn't mean you've achieved fit within it
- Listening to "somewhat disappointed" users - Focus on what makes "very disappointed" users love you, not what would make lukewarm users slightly happier
Deep Dive
For all 64 insights from 46 guests, see references/guest-insights.md
Related Skills
- Designing Growth Loops
- Retention & Engagement
- Conducting User Interviews
- Startup Pivoting
How to use measuring-product-market-fit on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add measuring-product-market-fit
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches measuring-product-market-fit from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate measuring-product-market-fit. Access the skill through slash commands (e.g., /measuring-product-market-fit) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★73 reviews- ★★★★★Chen Abbas· Dec 24, 2024
Useful defaults in measuring-product-market-fit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Sofia Anderson· Dec 24, 2024
Solid pick for teams standardizing on skills: measuring-product-market-fit is focused, and the summary matches what you get after install.
- ★★★★★Noor Yang· Dec 20, 2024
I recommend measuring-product-market-fit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Chen Agarwal· Dec 16, 2024
Keeps context tight: measuring-product-market-fit is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Rahul Santra· Nov 15, 2024
measuring-product-market-fit fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Isabella Sethi· Nov 15, 2024
We added measuring-product-market-fit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sakura Khanna· Nov 15, 2024
I recommend measuring-product-market-fit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Alexander Rao· Nov 11, 2024
Solid pick for teams standardizing on skills: measuring-product-market-fit is focused, and the summary matches what you get after install.
- ★★★★★Emma Tandon· Nov 7, 2024
measuring-product-market-fit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aarav Reddy· Oct 26, 2024
Solid pick for teams standardizing on skills: measuring-product-market-fit is focused, and the summary matches what you get after install.
showing 1-10 of 73