home / skills / coowoolf / insighthunt-skills / 4p-opportunity-framework

4p-opportunity-framework skill

/decision-thinking/4p-opportunity-framework

This skill helps you rapidly evaluate opportunities using the 4P framework, balancing potential, probability, passion, and prowess to spark bold, informed bets.

npx playbooks add skill coowoolf/insighthunt-skills --skill 4p-opportunity-framework

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.4 KB
---
name: 4P Opportunity Framework
description: Evaluate opportunities by assessing Potential BEFORE Probability, then check Passion and Prowess. Prevents risk aversion from killing high-upside ideas.
---

# The 4P Opportunity Framework

> "If you apply a filter that says, 'Oh, I only have a one in 10 chance to pull this off... not going to do that.' Well, if it's a one in 10 chance at 10 billion, it might be worth it." — Dharmesh Shah

## What It Is

A quantitative approach to weighing opportunities that forces a **separation between outcome size and success likelihood**, preventing risk aversion from stifling innovation.

## When To Use

- Deciding between **multiple strategic directions**
- Evaluating **new product lines** or startup ideas
- Breaking **analysis paralysis** on high-stakes bets
- When team is only pursuing **"safe" opportunities**

## The 4Ps (In Order)

```
┌─────────────────────────────────────────────────────┐
│  1. POTENTIAL (0-10)                                │
│     "If this works, how big could it be?"           │
│     → Assess BEFORE looking at risk                 │
├─────────────────────────────────────────────────────┤
│  2. PROBABILITY                                     │
│     "What's the likelihood of success?"             │
│     → Expected Value = Potential × Probability      │
├─────────────────────────────────────────────────────┤
│  3. PASSION / PROXIMITY                             │
│     "Do we care enough? Are we close to the pain?"  │
│     → Passion sustains through hard times           │
├─────────────────────────────────────────────────────┤
│  4. PROWESS                                         │
│     "Do we have unfair advantages?"                 │
│     → Assets, code, market access, relationships    │
└─────────────────────────────────────────────────────┘
```

## How To Apply

```
STEP 1: Rate Potential First (0-10)
└── 10 = Trillion-dollar outcome
└── 7-9 = Billion-scale opportunity
└── 4-6 = Hundred-million scale
└── 1-3 = Modest outcome

STEP 2: Assess Probability
└── Don't let low probability kill high potential
└── Calculate: EV = Potential × Probability

STEP 3: Check Passion/Proximity
└── Would you work on this for 10 years?
└── Do you deeply understand the customer pain?

STEP 4: Evaluate Prowess
└── What unfair advantages do you have?
└── Why are YOU uniquely positioned to win?
```

## Common Mistakes

❌ Assessing **Probability before Potential** (kills big ideas early)

❌ Using low probability to filter out **high-EV opportunities**

❌ Pursuing high-potential ideas with **no passion or proximity**

## Real-World Example

Dharmesh used this thinking to justify HubSpot's "Zig" strategy of building an "all-in-one" platform (low probability, high potential) rather than a safer niche tool.

---
*Source: Dharmesh Shah, Lenny's Podcast*

Overview

This skill teaches the 4P Opportunity Framework: evaluate Potential before Probability, then check Passion and Prowess. It helps teams separate outcome size from likelihood so high-upside ideas aren’t prematurely discarded. The framework yields a simple expected-value filter plus qualitative checks to ensure commitment and advantage.

How this skill works

First, score Potential on a 0–10 scale based on the size of the possible outcome without regard to risk. Next, estimate Probability and compute expected value (Potential × Probability) to compare ideas quantitatively. Then validate Passion/Proximity to confirm willingness to persist and customer closeness. Finally, assess Prowess—unfair advantages that increase odds or defensibility.

When to use it

  • Choosing between multiple strategic directions or product bets
  • Evaluating new product lines, platform plays, or startup ideas
  • Breaking analysis paralysis on high-stakes, uncertain opportunities
  • Counteracting a culture of excessive risk aversion
  • Prioritizing roadmap items where upside and commitment matter

Best practices

  • Always rate Potential before estimating Probability to avoid killing long-shot, high-upside bets
  • Use the expected-value calculation as a guide, not an absolute rule
  • Require both Passion (or proximity to the problem) and some Prowess before greenlighting work
  • Document assumptions behind Probability and revisit them as you learn
  • Combine quantitative EV with qualitative judgment for final decisions

Example use cases

  • Deciding whether to invest in a risky platform that could become a market standard
  • Prioritizing a roadmap item that has modest odds but could unlock billion-dollar revenue
  • Choosing between a safe feature with near-term ROI and a long-term transformational bet
  • Screening startup ideas during early-stage evaluation or accelerator selection

FAQ

How do I score Potential objectively?

Anchor scores to outcome scales (e.g., 10 = trillion, 7–9 = billion, 4–6 = hundred-million) and document the revenue or impact assumptions behind each score.

What if an idea has high Potential but zero Passion?

High potential alone is risky. Require at least some passion or proximity from the team or a committed sponsor before proceeding; otherwise de-risk or deprioritize.