PM OS · Internal Evaluation · March 2026

Single-Source Skill vs Full System

Head-to-head comparison of an external Lenny MCP skill against the complete PM OS — same prompt, different toolsets, scored on 7 dimensions.

Test Prompt

"We have 1,000 DAUs growing 5% week-over-week. Revenue is $15K MRR. Three enterprise customers want features that'd take us away from our core product. How do I know if we have PMF, and should I build for enterprise?"

Overall Scores

External Skill (Lenny MCP only)
2.1 / 5
Delta
+2.5
PM OS Full System
4.6 / 5
Breadth of sources
2
5
Framework density
2
5
Actionability
3
5
B2B specificity
2
4
Decision structure
2
5
Lenny coverage
3
4
Follow-up resources
1
4

Response Comparison

What each system produced from the same prompt

A
External Skill
Lenny Podcast MCP only

PMF Measurement

The Superhuman PMF Engine — Run the Sean Ellis test: ask users "How would you feel if you could no longer use this product?"

  • Below 40% "very disappointed" → no PMF. Focus on core.
  • Above 40% → you likely have PMF. Now decide where to expand.
"You have to deliberately not act on the feedback of many of your early users." — Rahul Vohra, Superhuman

Vohra transcriptSean Ellis transcript

Enterprise Decision

Vohra distinguishes solution deepening (better for existing users) from market widening (available to more segments). Enterprise = market widening. His lesson: pour everything into solution deepening first.

"We rarely scale a project until we know the Sean Ellis score hit a threshold that we find really compelling." — Jag Duggal, Nubank

Vohra transcriptDuggal transcript

Growth Rate Context

Casey Winters: at 5% WoW with 1,000 DAUs, you may be in Kindle territory — non-scalable hacks that prove demand but don't compound.

"Start by assuming you no longer have product-market fit, because you had product market fit in a different market." — Adam Grenier

Winters transcriptGrenier transcript

Recommendation

  1. Run the Sean Ellis survey on your 1,000 DAUs
  2. If below 40%, don't build for enterprise — double down on core
  3. If above 40%: does enterprise solution-deepen or only market-widen?
  4. If features benefit core users too, consider. If not, don't.
  5. Check if 5% WoW is "Kindle" or "Fire" growth

Further Reading

No newsletter articles available — MCP only surfaces podcast transcripts
B
PM OS Full System
Knowledge/ + MCP + Newsletter + Skills + Workflows

PMF Measurement — Three Lenses

Lens 1 — Sean Ellis Test — Same 40% threshold, but PM OS adds Vohra's segmentation: filter "somewhat disappointed" by whether they value your core benefit.

Lens 2 — Hierarchy of Engagement — Sarah Tavel's ladder: core action → retention → habit → network effects. Check which rung is solid before anything else.

Lens 3 — Growth Benchmarking — 5% WoW = ~12x annual. Promising but early. Is it organic or manufactured?

Sean Ellis framework Hierarchy of Engagement Vohra transcript Lenny Newsletter

Enterprise Decision — Four Frameworks

The Wedge: own your niche completely before expanding. Three enterprise customers is "wedge diffusion" risk.

Post PMF Strategy: enterprise features are Type 3 work (PMF Expansion) — a post-PMF activity. At $15K MRR, you're skipping the sequence.

Pivot Triggers: set explicit stop conditions before starting enterprise work.

Naval's Lion Strategy: keep WIP low. Three customers pulling different directions is the anti-pattern.

The Wedge Post PMF Strategy Pivot Triggers Naval's Lion

Decision Architecture

Before any framework — one question: "If you build for enterprise and your core product stalls, how hard would that be to reverse in six months?" — /decisions workflow, reversibility check

Make Great Decisions workflow

Recommendation — 7 Steps

  1. Run Sean Ellis survey this week
  2. Map retention curve — D7 above 25%? D30 above 15%?
  3. Classify 5% WoW: organic referrals or paid/manual?
  4. If Sean Ellis <40%: enterprise off the table
  5. If ≥40%: evaluate enterprise against The Wedge
  6. Set pivot triggers before starting enterprise work
  7. If proceeding, cap enterprise at ≤20% of R&D capacity

Further Reading

What This Reveals

Where Lane A holds its own

  • Vohra's PMF Engine is genuinely excellent. The full methodology is in the transcript — hard to beat.
  • Solution deepening vs market widening directly answers the enterprise question with high signal.
  • Lower cognitive load. One framework, clearly explained, easy to act on.

Where Lane A falls short

  • No decision structure. "Here's what Rahul did" without a framework for your decision.
  • No B2B-specific content. All episodes are prosumer/consumer companies.
  • No complementary frameworks. Sean Ellis is one lens on a multi-dimensional question.
  • No follow-up resources. Can't link newsletter articles — only 1-2 hour podcast episodes.

The structural takeaway

PM OS's advantage isn't more content — it's synthesis. Connecting frameworks to decisions to sequenced actions. The Lenny MCP is a commodity input anyone can build a skill on. The moat is the 50 prioritization frameworks, 118 PM frameworks, the workflow routing, and the skills that chain them together.

Try It Yourself

The full system that scored 4.6 out of 5

PM OS is a Claude-native operating system for product managers — 118 PM frameworks, 50 prioritization models, workflow routing, and skills that chain them together into decisions.

Get PM OS

prodmgmt.world · Claude-native · Works in Claude.ai & Claude Code