What makes Product-Market Fit and Crossing the Chasm notable?

1.2K downloads. Trust evidence available

How should Product-Market Fit and Crossing the Chasm be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Product-Market Fit and Crossing the Chasm

Activate when: user says "PMF," "product-market fit," "crossing the chasm," "early adopter to mainstream," "whole product," "we're stuck after our beachhead,...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

1.0.5

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.5release · observed Jul 16, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:pmf-crossing-the-chasm

Install using `clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:pmf-crossing-the-chasm` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/deciqai/pmf-crossing-the-chasm before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/snapshot"

Documentation

CLAWHUB

112,921 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: pmf-crossing-the-chasm
description: >
  Activate when: user says "PMF," "product-market fit," "crossing the chasm," "early adopter to mainstream," "whole product," "we're stuck after our beachhead," or "growth stalled after an initial good period"; startup has early traction but can't tell if it's real; team is debating which segment to target next after winning early fans.
  Do NOT activate when: the product has no users yet (use lean-startup instead); the business is already category-mature and the question is about scaling proven channels.
  More: deciqai.com/c/pmf-crossing-the-chasm
---

# Product-Market Fit and Crossing the Chasm

## Overview

Two distinct questions decide early-stage growth: (1) **PMF** — do enough users love the product they'd be very disappointed without it? (2) **Chasm** — can you move from early adopters (tolerate rough edges for novelty) into the early majority (need proven, complete, referenceable products)? Both failures look like "low growth" but differ in cause and cure.

**Compose:** business-model-canvas · lean-startup · first-principles · probabilistic-thinking

## When to Use

Apply when: early traction exists but PMF is unconfirmed; growth stalls after initial good period; deciding next segment; NPS positive but usage flat; an AI-native product loved by developer/early-adopter users stalls at enterprise adoption despite the AI-capex race and frontier-model gains.
**Not when:** no users yet (lean-startup); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** user has data → run the PMF + Chasm Audit directly.
- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. One-line what-it-is: (a) PMF = do users love it enough to be very disappointed without it? (b) Chasm = can you move from early adopters (tolerate rough edges) to early majority (need proven, complete, referenceable)? Solved differently.
2. Check fit: no users yet → lean-startup. Already-mainstream business → wrong framework.
3. Which segment are you selling to today? Name early adopters vs. early majority concretely.
> **[WAIT — do not advance until user responds]**
4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.
> **[WAIT — do not advance until user responds]**
5. Name the right next move: "fix product first" or "here is the specific whole-product gap blocking the next segment."
> **[WAIT — do not advance until user responds]**

## The Process

Run the **PMF + Chasm Audit**. PMF first; chasm second.

### Part A — Measure PMF

**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).
**A2.** Ellis Test: *"How would you feel if you could no longer use [product]?"* — Very / Somewhat / Not disappointed / N/A.
**A3.** Score: ≥ 40% Very disappointed =

_meta.json

{
  "ownerId": "kn754b8sk22s8c6gjxt02bftbn88q7ye",
  "slug": "pmf-crossing-the-chasm",
  "version": "1.0.5",
  "publishedAt": 1784225433948
}

references/sources.md

# Sources — pmf-crossing-the-chasm

> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*

## Sources

- **Moore, Geoffrey.** *Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers*. HarperBusiness, 1991; rev. 3rd ed. 2014. **Canonical primary source for the chasm**.
- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.
- **Andreessen, Marc.** "The only thing that matters." *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.
- **Ellis, Sean.** "The Startup Pyramid." *Startup Marketing* blog, 2009; archived: https://web.archive.org/web/20100118091421/http://startup-marketing.com/the-startup-pyramid/ **The 40% Ellis Test methodology**.
- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.
- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.
- **GitHub.** Public blog and product documentation on GitHub Copilot — general availability (2022), adoption, and enterprise security/admin controls (2021–2025). https://github.blog/ **Primary-source for the AI-coding-assistants chasm case (2023–2026).**
- **Stack Overflow.** *Annual Developer Survey* — AI-tools adoption sections (2023, 2024, 2025). https://survey.stackoverflow.co/ **Widely-cited data on developer AI-tool adoption and sentiment.**
- The popular framing "if you build it they will come" is **not** cited as a source — by this skill's own rule, an aphorism is not evidence. The framework is more precisely "first build it for a beachhead who will love it (PMF), then specifically engineer the ecosystem the next segment needs (chasm)."

examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md

# Method in Action: AI Coding Assistants Crossing the Chasm (2023–2026)

> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*

A worked example applying the PMF + Chasm Audit to a category, not a single company: **AI coding assistants and agents** — GitHub Copilot, Cursor, and the broader wave of AI-native coding tools that emerged after ChatGPT (late 2022) and matured through 2025. The point is not to grade any one vendor but to show *where the chasm sits* for the whole category, and which whole-product gaps stall the crossing from visionary early adopters into a pragmatist mainstream.

Because the framework separates PMF from chasm, we run Part A first, then Part B.

## Part A — Measure PMF

**A1 — Active-user cohort.** The relevant cohort is not "developers who tried an AI autocomplete once," but developers who kept using an assistant across multiple sessions over weeks. GitHub Copilot launched in preview in mid-2021 and became generally available in mid-2022; by the mid-2020s GitHub reported that Copilot had well over a million paying subscribers and was used across a large share of enterprises. Cursor, built on top of the VS Code lineage, grew rapidly through 2024–2025 among developers who adopted an AI-native editor. These are genuine repeat-use cohorts, not signup vanity.

**A2 — Ellis Test (equivalent signal).** No public vendor ran a formal "How would you feel if you could no longer use this?" survey at category scale, so we read the equivalent signal. Two things stand out: (1) developer surveys through 2024–2025 (e.g., Stack Overflow's annual Developer Survey) reported that a large majority of developers were using or planning to use AI tools in their workflow; (2) strong retention and word-of-mouth among the early cohort — developers who adopted assistants overwhelmingly reported they would be reluctant to give them up. By the Ellis proxy, the early-adopter segment clears the bar.

**A3 — Score / verdict.** For the **early-adopter developer segment** — individual engineers and small teams who tolerate rough edges (occasional wrong suggestions, hallucinated APIs) in exchange for speed — the category has clear PMF. The "very disappointed if I lost it" signal is high among daily users.

**A4 — Follow-ups.**
- *Who benefits most?* Individual developers and small, autonomy-heavy teams writing greenfield or boilerplate-heavy code.
- *Main benefit?* Speed on well-trodden tasks — scaffolding, tests, boilerplate, unfamiliar-API lookup.
- *Top improvements requested?* Reliability on large existing codebases, correctness guarantees, and control over what the tool sees and does.

**A5 — Retention curve.** Among daily-active early adopters the curve flattens into a smile — the tool becomes part of the workflow. That is a PMF signal, and it holds specifically for the early-adopter segment.

**Verdict on Part A:** PMF is real — *in the visionary early-adopter segment.* That is exactly the setup the chasm framework warns about: PMF with ea

examples/salesforce-1999-2007.md

# Method in Action: Salesforce, 1999 → 2007

> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*

A worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.

**Salesforce.com** was founded by **Marc Benioff** and three co-founders in March 1999. The product was a CRM application delivered as a *web service* — what would later be called SaaS. The dominant CRM at the time was **Siebel Systems**, sold as enterprise on-premises software with multi-year implementations costing millions.

**The PMF phase (1999–2001).** Salesforce's earliest customers were small-to-medium sales teams who wanted CRM but could not afford Siebel implementations. The Ellis Test wasn't used by name (Ellis published the methodology in 2009), but the equivalent signal was unmissable: monthly subscriptions grew from ~3,000 paying users in early 2001 to >100,000 by mid-2003 (Benioff, *Behind the Cloud*, 2009, ch. 4–5), with retention strong among the early small-team buyers. By any reasonable PMF criterion — the product was loved by its beachhead segment, retention was high, organic word-of-mouth was real — Salesforce had PMF in the small-team segment by ~2001.

**The chasm.** That PMF did not translate to **enterprise CRM sales**, which Siebel dominated. Enterprise buyers required things Salesforce's early-adopter SMB customers had not: SSO integrations with existing identity systems, audit trails for SOX compliance, customizable workflows for industry verticals (financial services, healthcare, pharmaceuticals), 24×7 enterprise support contracts, three-tier reference customers in their own vertical, and a procurement process matched to corporate purchasing. **The product was not the gap; the whole product was.**

**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:

- **2002–2003 financial services** — built compliance, audit, security to a level that won several mid-market financial-services firms; used those as references to win larger ones.
- **2005 AppExchange launch** — third-party application marketplace; solved the "whole product" gap by enabling partners to build the vertical-specific extensions Salesforce itself couldn't build.
- **2006 Service Cloud / customer-service expansion** — extended the platform beyond pure CRM, addressing the "expand into adjacent use cases" pin in Moore's bowling-pin model.
- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.

Walk the audit on Salesforce circa 2001:

- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓
- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.
- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.
- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical refer

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.