Skip to content

/cs-pmf-check

Slash Command Source

Command: /cs:pmf-check

A focused slice of the cs-andreessen persona aimed at one question: are you before or after product/market fit? Per Andreessen, PMF is the only milestone that matters and it is not subtle — if you have to squint to see it, you don't have it.

When to Run

  • "Are we at product/market fit?"
  • You're deciding whether to scale (spend on growth/sales) or keep iterating on the product.
  • You're tempted to raise/hire/expand and want a hard read on whether the fit is real first.

What You Get

A focused interrogation, then a deterministic verdict:

  1. The felt-signal test (Andreessen): are customers buying as fast as you can make it? Is usage growing as fast as you can add servers? Is money piling up? Are you hiring support as fast as you can?
  2. The Sean Ellis 40% gate (Ellis, not Andreessen): do ≥40% of users say they'd be "very disappointed" without you?
  3. Verdict: BEFORE-PMF / APPROACHING-PMF / AFTER-PMF + explicit confidence.
  4. One next move: before PMF → what to change (product/segment/team). After PMF → pour fuel, stop deliberating, feed demand.

Discipline

  • PMF is not subtle. "Approaching" is the honest verdict for warm-but-ambiguous signals; don't inflate it to "after."
  • Retention is the strongest single signal. A leaky bucket means you are before PMF no matter how good acquisition looks.
  • Label the Ellis test as Ellis's, not Andreessen's. Confidence levels mandatory.
  • No capitulation to wishful reads without new evidence.

Workflow

python ../skills/andreessen/scripts/pmf_signal_scorer.py \
  --ellis-pct 45 --retention 8 --organic 7 --demand 8 --frequency 7

Version: 1.0.0