When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Guides product-market fit (PMF) validation and measurement. PMF occurs when a product precisely meets market needs, creating widespread demand. ~99% of startups fail primarily due to PMF issues (vitamin problems, premature scaling). Use this skill when validating before scaling, measuring PMF, or diagnosing traction problems.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Product-market fit (Marc Andreessen): "Being in a good market with a product that can satisfy that market."
Signals: Customers buying rapidly; usage growing; word-of-mouth spreading organically; high retention, low churn.
Question: "How would you feel if you could no longer use [product]?"
| Response | Meaning |
|---|---|
| Very disappointed | Strong PMF signal |
| Somewhat disappointed | — |
| Not disappointed | — |
| N/A – I no longer use | — |
Threshold: 40%+ answering "very disappointed" = PMF achieved. Below 40% = iterate.
| Score | Action |
|---|---|
| Below 25% | Significant changes needed |
| 25–39% | Close to PMF; iterate and improve |
| 40%+ | PMF achieved |
Best practice: Survey 40–50 active users (used product 2+ times in last 14 days). Segment by user type—some segments may have PMF while others don't.
Limitation: Combine with retention curves, engagement, organic growth; avoid false positives in early stages.
| Type | Definition | Adoption |
|---|---|---|
| Painkiller | Solves urgent, acute problems; users actively seek solutions | Fast adoption; high retention; willing to pay |
| Vitamin | Nice-to-have; incremental benefit; users can live without | Slow adoption; expensive marketing to succeed |
~99% of failures: Solving vitamin problems instead of real pain. Validate: Would users be genuinely inconvenienced if your product vanished?
Validation: Talk to users; listen for frustration; run pre-sells; check frequency and time-sensitivity of the problem.
| Indicator | Strong PMF |
|---|---|
| Retention | High; low churn |
| CAC vs CLTV | CAC decreasing relative to CLTV |
| Activation | Strong conversion to paying customers |
| Growth | Organic; word-of-mouth |
| NPS | High; enthusiastic advocacy |
| Failure | Avoid |
|---|---|
| Vitamin problems | Solve urgent pain, not nice-to-have |
| Vanity feedback | Use retention data, not polite opinions |
| Premature scaling | Validate PMF before scaling acquisition |
| Misalignment | Customer-problem fit before product-build |
| Area | Notes |
|---|---|
| Product positioning | Target audience; core value; competitive differentiation |
| Market research | Competitor analysis; surveys; interviews to validate assumptions |
| SaaS form | Cloud delivery; subscription; ease of use; dependency on industry standardization |
| Enterprise / ACV | Customization; data security/private deployment; procurement cycles; buy vs SaaS trade-offs |
Use: When discussing PMF for SaaS or enterprise—factor in product research rigor and ACV-specific challenges. See gtm-strategy for enterprise GTM.
PMF is increasingly a continuous validation—markets evolve; re-measure as you expand. Target "PMF for a niche" first (40%+ in one segment) before broadening.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
The English summary is being prepared. Showing the original description.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
The English summary is being prepared. Showing the original description.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
The English summary is being prepared. Showing the original description.