{"id":"94605d52-0ca9-47fb-b36a-8f4e97e20b37","entityType":"agent","slug":"clawhub-deciqai-pmf-crossing-the-chasm","name":"Product-Market Fit and Crossing the Chasm","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-pmf-crossing-the-chasm","canonicalPath":"/agent/clawhub-deciqai-pmf-crossing-the-chasm","generatedAt":"2026-10-11T05:32:59.679Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:36:41.726Z","emptyReason":null},"description":"Activate when: user says \"PMF,\" \"product-market fit,\" \"crossing the chasm,\" \"early adopter to mainstream,\" \"whole product,\" \"we're stuck after our beachhead,...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:pmf-crossing-the-chasm","sourceUrl":"https://clawhub.ai/deciqai/pmf-crossing-the-chasm","homepage":"https://clawhub.ai/deciqai/skills/pmf-crossing-the-chasm","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/pmf-crossing-the-chasm","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/pmf-crossing-the-chasm","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Product-Market Fit and Crossing the Chasm technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:36:41.726Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:36:41.726Z","emptyReason":null},"stars":null,"forks":null,"downloads":1171,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:36:41.588Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T03:36:41.726Z","lastCrawledAt":"2026-10-11T03:36:41.588Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T03:36:41.588Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T18:10:33.948Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/pmf-crossing-the-chasm.json)","fileCount":6,"zipByteSize":12706},{"version":"1.0.4","createdAt":"2026-07-09T11:20:15.452Z","changelog":"Refresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)","fileCount":6,"zipByteSize":12515},{"version":"1.0.3","createdAt":"2026-07-08T11:14:24.110Z","changelog":"Footer now uses /c/ short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":5,"zipByteSize":8156},{"version":"1.0.2","createdAt":"2026-07-08T00:58:57.540Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":8213},{"version":"1.0.1","createdAt":"2026-07-07T22:31:32.867Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":8066},{"version":"1.0.0","createdAt":"2026-07-01T06:18:33.613Z","changelog":"Initial publish","fileCount":5,"zipByteSize":8146}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:pmf-crossing-the-chasm","setupComplexity":"low","setupSteps":["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":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T05:32:59.676Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-pmf-crossing-the-chasm/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:36:41.726Z","emptyReason":null},"readme":"Skill: Product-Market Fit and Crossing the Chasm\n\nOwner: deciqai\n\nSummary: Activate when: user says \"PMF,\" \"product-market fit,\" \"crossing the chasm,\" \"early adopter to mainstream,\" \"whole product,\" \"we're stuck after our beachhead,...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T18:10:33.948Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/pmf-crossing-the-chasm.json)\n\nv1.0.4 | 2026-07-09T11:20:15.452Z | user\n\nRefresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)\n\nv1.0.3 | 2026-07-08T11:14:24.110Z | user\n\nFooter now uses /c/ short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.2 | 2026-07-08T00:58:57.540Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T22:31:32.867Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-07-01T06:18:33.613Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 6 files, 12706 bytes\n\nFiles: examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md (7962b), examples/salesforce-1999-2007.md (3878b), references/sources.md (1843b), skill-card.md (2921b), SKILL.md (7940b), _meta.json (141b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: pmf-crossing-the-chasm\ndescription: >\n 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.\n 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.\n More: deciqai.com/c/pmf-crossing-the-chasm\n---\n\n# Product-Market Fit and Crossing the Chasm\n\n## Overview\n\nTwo 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.\n\n**Compose:** business-model-canvas · lean-startup · first-principles · probabilistic-thinking\n\n## When to Use\n\nApply 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.\n**Not when:** no users yet (lean-startup); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has data → run the PMF + Chasm Audit directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. 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.\n2. Check fit: no users yet → lean-startup. Already-mainstream business → wrong framework.\n3. Which segment are you selling to today? Name early adopters vs. early majority concretely.\n> **[WAIT — do not advance until user responds]**\n4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.\n> **[WAIT — do not advance until user responds]**\n5. Name the right next move: \"fix product first\" or \"here is the specific whole-product gap blocking the next segment.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **PMF + Chasm Audit**. PMF first; chasm second.\n\n### Part A — Measure PMF\n\n**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).\n**A2.** Ellis Test: *\"How would you feel if you could no longer use [product]?\"* — Very / Somewhat / Not disappointed / N/A.\n**A3.** Score: ≥ 40% Very disappointed = PMF. 25–40% = approaching. < 25% = no PMF.\n**A4.** Follow-ups: who benefits most? main benefit? top improvements?\n**A5.** Retention curve should flatten (smile curve), not decay to zero.\n\n### Part B — If PMF holds, assess Chasm\n\n**B1.** Classify customers on Rogers's curve (Innovators / Early Adopters / Early Majority).\n**B2.** Name chasm geography: selling today to whom; specific next mainstream sub-segment.\n**B3.** Whole-product gap: integrations, references, certs, support, contracts missing.\n**B4.** Pick one beachhead (bowling-pin — not \"the mainstream\" generically).\n**B5.** Build whole-product for that beachhead; shift positioning to \"proven and safe.\"\n\n### Output: PMF + Chasm Audit\n\n```\n# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed\n```\n\n*→ Method in Action: [Salesforce, 1999 → 2007](examples/salesforce-1999-2007.md)*\n*→ 2026 lens: [AI Coding Assistants Crossing the Chasm (2023–2026)](examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md)*\n\n## Adoption Packs\n\nSegment geography differs by domain; PMF measurement and chasm framework are universal. Domain packs cover: adopter profiles, whole-product gap, beachhead segments, positioning shift.\n\n- **Enterprise SaaS:** compliance + ecosystem. **Consumer apps:** UX polish + cross-platform + virality. **Developer tools:** procurement-readiness (SSO/support/CIO). **Healthcare:** regulatory + clinical evidence + EMR.\n\nAdding a pack for your industry is the easiest contribution.\n\n## Applying It Well\n\n- Measure PMF — don't intuit it. Founder gut is famously unreliable. Don't cross the chasm by selling harder to the same segment.\n- Whole-product gap is almost always ecosystem (compliance, integrations, references), not features.\n- Beachhead specificity wins: \"financial services mid-market U.S.\" beats \"going enterprise.\"\n- Positioning shift from \"cool/new\" to \"proven/safe\" is the framework's hardest interpersonal cost.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We have PMF\" — citing NPS or signups only | NPS/signups are vanity-adjacent. Use Ellis Test or comparable retention signal. |\n| [D] Doubling sales team as chasm-crossing strategy | Sells harder to the same early-adopter segment → revenue then stall. Gap is whole-product, not headcount. |\n| [D] Treating \"the mainstream\" as one segment | It's composed of distinct verticals. Pick one beachhead (bowling-pin); \"going mainstream\" loses. |\n| [D] Adding features as the whole-product fix | Mainstream needs compliance, integrations, references, contracts — not features. |\n| [D] Same pitch for early adopters and mainstream | Visionaries buy \"transformative\"; pragmatists buy \"proven safe.\" One pitch fails both. |\n| [D] Confusing pricing/sales-process issues with chasm | Growth sometimes stalls for boring reasons. Diagnose carefully before invoking the chasm. |\n| [D] Skipping PMF → jumping straight to chasm strategy | No PMF in any segment = nothing to cross from. |\n| [D] \"We just need better marketing\" | Mainstream decides by peer references, not marketing. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"We have PMF\" with no Ellis Test or retention signal\n- Doubling sales team proposed as answer to stalling growth\n- \"Going mainstream\" with no specific beachhead named\n- Roadmap = more features when need is compliance/integrations/references\n- Same pitch deck for early adopters and enterprise; no vertical references\n\n## Verification\n\n- [ ] PMF measured on active-user cohort (Ellis Test or equivalent)\n- [ ] Current customers classified on Rogers's curve\n- [ ] Specific beachhead named (not \"the mainstream\")\n- [ ] Whole-product gap enumerated (compliance, integrations, references, contracts)\n- [ ] Positioning shift planned; sales process changes named; reference-customer plan exists\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/pmf-crossing-the-chasm** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/pmf-crossing-the-chasm.json*\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"pmf-crossing-the-chasm\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1784225433948\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — pmf-crossing-the-chasm\n\n> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\n## Sources\n\n- **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**.\n- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.\n- **Andreessen, Marc.** \"The only thing that matters.\" *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.\n- **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**.\n- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.\n- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.\n- **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).**\n- **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.**\n- 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).\"\n\nFile v1.0.5:examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md\n\n# Method in Action: AI Coding Assistants Crossing the Chasm (2023–2026)\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA 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.\n\nBecause the framework separates PMF from chasm, we run Part A first, then Part B.\n\n## Part A — Measure PMF\n\n**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.\n\n**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.\n\n**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.\n\n**A4 — Follow-ups.**\n- *Who benefits most?* Individual developers and small, autonomy-heavy teams writing greenfield or boilerplate-heavy code.\n- *Main benefit?* Speed on well-trodden tasks — scaffolding, tests, boilerplate, unfamiliar-API lookup.\n- *Top improvements requested?* Reliability on large existing codebases, correctness guarantees, and control over what the tool sees and does.\n\n**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.\n\n**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 early adopters does not license the assumption that the pragmatist mainstream will follow on the same product.\n\n## Part B — Assess the Chasm\n\n**B1 — Rogers classification.** Position today's buyers on the diffusion curve:\n- **Innovators / Early Adopters:** individual developers, indie hackers, startups, and forward-leaning teams who adopt for competitive edge and tolerate imperfection.\n- **Early Majority (the mainstream not yet fully crossed):** large enterprise engineering orgs — banks, healthcare, defense, regulated industries — whose adoption is gated by security review, legal, and platform teams rather than by individual developer enthusiasm.\n\n**B2 — Chasm geography (today → next).**\n- *Selling today to:* individual developers and small teams (bottom-up, seat-by-seat).\n- *Next mainstream sub-segment:* regulated-enterprise engineering organizations, where the buyer is a CIO/CISO/platform lead, not the developer who loves the tool.\n\nThe chasm is the gap between \"developers love it\" and \"the enterprise will standardize on it.\" This is the classic Moore chasm: visionaries buy transformation; pragmatists buy proven, safe, complete, referenceable.\n\n**B3 — Whole-product gap.** The gap that stalls the crossing is almost entirely *ecosystem*, not model capability:\n- **Security & data governance:** guarantees about where code goes, whether proprietary code trains a model, and tenant isolation.\n- **IP / licensing indemnity:** enterprises need protection against suggestions that reproduce licensed code — several vendors responded by offering IP indemnification for enterprise tiers, precisely because it was a crossing blocker.\n- **Compliance & certification:** SOC 2, and sector requirements (finance, healthcare, government/FedRAMP-style).\n- **Identity & admin controls:** SSO/SAML, org-wide policy, audit logs, per-repo permissions.\n- **Reliability on large legacy codebases:** the early-adopter win case (greenfield, boilerplate) is not the enterprise pain (millions of lines of existing, idiosyncratic code).\n- **Vertical references:** a bank's platform team buys after peer banks vouch — not after a demo.\n\nNote the pattern the skill predicts: the gap is **not \"the model isn't smart enough.\"** Frontier model capability advanced dramatically over 2023–2025. The stalls are governance, indemnity, references, and integration — the whole product.\n\n**B4 — Beachhead choice (bowling pin, not \"the enterprise\").** The winning move is a specific first pin, not \"go enterprise.\" A defensible beachhead in this period looked like: *one regulated vertical or one workflow where the whole-product case can be completed and referenced* — for example, an enterprise tier hardened for security-conscious software organizations, or an agentic workflow scoped to a narrow, verifiable task (test generation, migration, code review) where correctness can be checked. Land that, reference it, then knock down the next pin.\n\n**B5 — Whole-product plan & positioning shift.**\n- *Build:* enterprise admin/security controls, IP indemnity, compliance certifications, on-prem/VPC deployment options, and audit-grade logging.\n- *References:* named peer-vertical customers, not aggregate usage stats.\n- *Positioning shift:* from the early-adopter pitch (\"10x your speed, the future of coding\") to the pragmatist pitch (\"secure, compliant, governed, and proven at organizations like yours\"). This is the framework's hardest interpersonal cost — the transformational story that won the visionaries actively repels the risk-averse pragmatist buyer.\n\n## What the framework surfaces\n\nThe seductive misread through this period is that the AI-coding race is a *model-capability* race — that whoever has the smartest model crosses. The chasm lens says otherwise: PMF with developers is not PMF with enterprises, and the crossing is won by whoever first completes the **whole product** (security, indemnity, compliance, references, integration into large codebases) for a **specific beachhead** — then shifts positioning from \"transformative\" to \"proven and safe.\" The AI-capex boom funds better models; it does not, by itself, close the whole-product gap that gates the mainstream. A vendor that answers stalling enterprise growth by shipping a bigger model (more features) rather than the governance-and-reference whole product is making exactly the anti-pattern this skill flags.\n\n*Sources: Geoffrey Moore, Crossing the Chasm (1991; 3rd ed. 2014); Everett Rogers, Diffusion of Innovations (1962; 5th ed. 2003); GitHub public statements and blog on Copilot availability, adoption, and enterprise controls (2021–2025); Stack Overflow Annual Developer Survey, AI-tools sections (2023–2025); public reporting on AI-coding tools offering enterprise IP indemnification and security/compliance tiers (2023–2025). Specific figures are stated qualitatively where exact public numbers vary by reporting date.*\n\nFile v1.0.5:examples/salesforce-1999-2007.md\n\n# Method in Action: Salesforce, 1999 → 2007\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.\n\n**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.\n\n**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.\n\n**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.**\n\n**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:\n\n- **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.\n- **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.\n- **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.\n- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.\n\nWalk the audit on Salesforce circa 2001:\n\n- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓\n- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.\n- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.\n- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical references, enterprise support — all missing.\n- **Beachhead choice (B4):** Financial services first (not \"the enterprise\" generically).\n- **Whole-product plan (B5):** Compliance certs, SSO integrations, financial-services case studies, dedicated enterprise sales team.\n- **Positioning shift (B6):** From \"no software, transformative SaaS rebel\" (the early-adopter anti-Siebel pitch) to \"proven, compliant, supported enterprise SaaS\" (the mainstream pitch).\n\nSalesforce did all six. The framework's payoff in this case: **the chasm did not feel like a product problem; it felt like a sales-execution problem.** Diagnosing it as a whole-product + segment-positioning problem is what unlocked the path through. Treating it as a sales problem alone would have produced a bigger sales team selling to the same early-adopter segment, with diminishing returns.\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nGuides agents through a structured product-market fit and crossing-the-chasm audit for teams with early traction, stalled growth, or uncertainty about the next customer segment.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nFounders, product teams, and strategy-focused agents use this skill to separate product-market fit diagnosis from chasm-crossing strategy, choose a concrete beachhead, and identify whole-product gaps such as references, integrations, compliance, support, and positioning.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill's output is business strategy advice and may be wrong or overconfident if the user provides incomplete product, customer, retention, or revenue evidence.\n\nMitigation: Use the audit as decision support; validate conclusions against active-user cohort data, Ellis Test responses or equivalent retention signals, customer references, and internal business review.\n\nRisk: Users may share confidential customer, revenue, roadmap, or adoption data while asking for PMF or chasm analysis.\n\nMitigation: Avoid providing sensitive details unless the agent session is approved for that information; anonymize customer names and commercial metrics where possible.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/pmf-crossing-the-chasm)\n- [deciqAI PMF and Crossing the Chasm page](https://www.deciqai.com/c/pmf-crossing-the-chasm)\n- [deciqAI machine-readable skill metadata](https://www.deciqai.com/s/pmf-crossing-the-chasm.json)\n- [Primary sources](references/sources.md)\n- [Salesforce, 1999 to 2007 example](examples/salesforce-1999-2007.md)\n- [AI Coding Assistants Crossing the Chasm example](examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md)\n- [Marc Andreessen, The only thing that matters](https://pmarchive.com/guide_to_startups_part4.html)\n- [Sean Ellis, The Startup Pyramid](https://web.archive.org/web/20100118091421/http://startup-marketing.com/the-startup-pyramid/)\n- [GitHub Blog](https://github.blog/)\n- [Stack Overflow Annual Developer Survey](https://survey.stackoverflow.co/)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Markdown audit with structured sections, checklists, and step-by-step coaching prompts]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces business-strategy guidance and pauses at explicit wait points when coaching novice users.]\n\n## Skill Version(s):\n\n1.0.5 (source: ClawHub release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 6 files, 12515 bytes\n\nFiles: examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md (7962b), examples/salesforce-1999-2007.md (3878b), references/sources.md (1843b), skill-card.md (2703b), SKILL.md (7783b), _meta.json (141b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: pmf-crossing-the-chasm\ndescription: >\n 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.\n 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.\n---\n\n# Product-Market Fit and Crossing the Chasm\n\n## Overview\n\nTwo 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.\n\n**Compose:** business-model-canvas · lean-startup · first-principles · probabilistic-thinking\n\n## When to Use\n\nApply 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.\n**Not when:** no users yet (lean-startup); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has data → run the PMF + Chasm Audit directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. 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.\n2. Check fit: no users yet → lean-startup. Already-mainstream business → wrong framework.\n3. Which segment are you selling to today? Name early adopters vs. early majority concretely.\n> **[WAIT — do not advance until user responds]**\n4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.\n> **[WAIT — do not advance until user responds]**\n5. Name the right next move: \"fix product first\" or \"here is the specific whole-product gap blocking the next segment.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **PMF + Chasm Audit**. PMF first; chasm second.\n\n### Part A — Measure PMF\n\n**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).\n**A2.** Ellis Test: *\"How would you feel if you could no longer use [product]?\"* — Very / Somewhat / Not disappointed / N/A.\n**A3.** Score: ≥ 40% Very disappointed = PMF. 25–40% = approaching. < 25% = no PMF.\n**A4.** Follow-ups: who benefits most? main benefit? top improvements?\n**A5.** Retention curve should flatten (smile curve), not decay to zero.\n\n### Part B — If PMF holds, assess Chasm\n\n**B1.** Classify customers on Rogers's curve (Innovators / Early Adopters / Early Majority).\n**B2.** Name chasm geography: selling today to whom; specific next mainstream sub-segment.\n**B3.** Whole-product gap: integrations, references, certs, support, contracts missing.\n**B4.** Pick one beachhead (bowling-pin — not \"the mainstream\" generically).\n**B5.** Build whole-product for that beachhead; shift positioning to \"proven and safe.\"\n\n### Output: PMF + Chasm Audit\n\n```\n# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed\n```\n\n*→ Method in Action: [Salesforce, 1999 → 2007](examples/salesforce-1999-2007.md)*\n*→ 2026 lens: [AI Coding Assistants Crossing the Chasm (2023–2026)](examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md)*\n\n## Adoption Packs\n\nSegment geography differs by domain; PMF measurement and chasm framework are universal. Domain packs cover: adopter profiles, whole-product gap, beachhead segments, positioning shift.\n\n- **Enterprise SaaS:** compliance + ecosystem. **Consumer apps:** UX polish + cross-platform + virality. **Developer tools:** procurement-readiness (SSO/support/CIO). **Healthcare:** regulatory + clinical evidence + EMR.\n\nAdding a pack for your industry is the easiest contribution.\n\n## Applying It Well\n\n- Measure PMF — don't intuit it. Founder gut is famously unreliable. Don't cross the chasm by selling harder to the same segment.\n- Whole-product gap is almost always ecosystem (compliance, integrations, references), not features.\n- Beachhead specificity wins: \"financial services mid-market U.S.\" beats \"going enterprise.\"\n- Positioning shift from \"cool/new\" to \"proven/safe\" is the framework's hardest interpersonal cost.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We have PMF\" — citing NPS or signups only | NPS/signups are vanity-adjacent. Use Ellis Test or comparable retention signal. |\n| [D] Doubling sales team as chasm-crossing strategy | Sells harder to the same early-adopter segment → revenue then stall. Gap is whole-product, not headcount. |\n| [D] Treating \"the mainstream\" as one segment | It's composed of distinct verticals. Pick one beachhead (bowling-pin); \"going mainstream\" loses. |\n| [D] Adding features as the whole-product fix | Mainstream needs compliance, integrations, references, contracts — not features. |\n| [D] Same pitch for early adopters and mainstream | Visionaries buy \"transformative\"; pragmatists buy \"proven safe.\" One pitch fails both. |\n| [D] Confusing pricing/sales-process issues with chasm | Growth sometimes stalls for boring reasons. Diagnose carefully before invoking the chasm. |\n| [D] Skipping PMF → jumping straight to chasm strategy | No PMF in any segment = nothing to cross from. |\n| [D] \"We just need better marketing\" | Mainstream decides by peer references, not marketing. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"We have PMF\" with no Ellis Test or retention signal\n- Doubling sales team proposed as answer to stalling growth\n- \"Going mainstream\" with no specific beachhead named\n- Roadmap = more features when need is compliance/integrations/references\n- Same pitch deck for early adopters and enterprise; no vertical references\n\n## Verification\n\n- [ ] PMF measured on active-user cohort (Ellis Test or equivalent)\n- [ ] Current customers classified on Rogers's curve\n- [ ] Specific beachhead named (not \"the mainstream\")\n- [ ] Whole-product gap enumerated (compliance, integrations, references, contracts)\n- [ ] Positioning shift planned; sales process changes named; reference-customer plan exists\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 189 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/pmf-crossing-the-chasm** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"pmf-crossing-the-chasm\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1783596015452\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — pmf-crossing-the-chasm\n\n> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\n## Sources\n\n- **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**.\n- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.\n- **Andreessen, Marc.** \"The only thing that matters.\" *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.\n- **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**.\n- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.\n- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.\n- **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).**\n- **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.**\n- 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).\"\n\nFile v1.0.4:examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md\n\n# Method in Action: AI Coding Assistants Crossing the Chasm (2023–2026)\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA 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.\n\nBecause the framework separates PMF from chasm, we run Part A first, then Part B.\n\n## Part A — Measure PMF\n\n**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.\n\n**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.\n\n**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.\n\n**A4 — Follow-ups.**\n- *Who benefits most?* Individual developers and small, autonomy-heavy teams writing greenfield or boilerplate-heavy code.\n- *Main benefit?* Speed on well-trodden tasks — scaffolding, tests, boilerplate, unfamiliar-API lookup.\n- *Top improvements requested?* Reliability on large existing codebases, correctness guarantees, and control over what the tool sees and does.\n\n**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.\n\n**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 early adopters does not license the assumption that the pragmatist mainstream will follow on the same product.\n\n## Part B — Assess the Chasm\n\n**B1 — Rogers classification.** Position today's buyers on the diffusion curve:\n- **Innovators / Early Adopters:** individual developers, indie hackers, startups, and forward-leaning teams who adopt for competitive edge and tolerate imperfection.\n- **Early Majority (the mainstream not yet fully crossed):** large enterprise engineering orgs — banks, healthcare, defense, regulated industries — whose adoption is gated by security review, legal, and platform teams rather than by individual developer enthusiasm.\n\n**B2 — Chasm geography (today → next).**\n- *Selling today to:* individual developers and small teams (bottom-up, seat-by-seat).\n- *Next mainstream sub-segment:* regulated-enterprise engineering organizations, where the buyer is a CIO/CISO/platform lead, not the developer who loves the tool.\n\nThe chasm is the gap between \"developers love it\" and \"the enterprise will standardize on it.\" This is the classic Moore chasm: visionaries buy transformation; pragmatists buy proven, safe, complete, referenceable.\n\n**B3 — Whole-product gap.** The gap that stalls the crossing is almost entirely *ecosystem*, not model capability:\n- **Security & data governance:** guarantees about where code goes, whether proprietary code trains a model, and tenant isolation.\n- **IP / licensing indemnity:** enterprises need protection against suggestions that reproduce licensed code — several vendors responded by offering IP indemnification for enterprise tiers, precisely because it was a crossing blocker.\n- **Compliance & certification:** SOC 2, and sector requirements (finance, healthcare, government/FedRAMP-style).\n- **Identity & admin controls:** SSO/SAML, org-wide policy, audit logs, per-repo permissions.\n- **Reliability on large legacy codebases:** the early-adopter win case (greenfield, boilerplate) is not the enterprise pain (millions of lines of existing, idiosyncratic code).\n- **Vertical references:** a bank's platform team buys after peer banks vouch — not after a demo.\n\nNote the pattern the skill predicts: the gap is **not \"the model isn't smart enough.\"** Frontier model capability advanced dramatically over 2023–2025. The stalls are governance, indemnity, references, and integration — the whole product.\n\n**B4 — Beachhead choice (bowling pin, not \"the enterprise\").** The winning move is a specific first pin, not \"go enterprise.\" A defensible beachhead in this period looked like: *one regulated vertical or one workflow where the whole-product case can be completed and referenced* — for example, an enterprise tier hardened for security-conscious software organizations, or an agentic workflow scoped to a narrow, verifiable task (test generation, migration, code review) where correctness can be checked. Land that, reference it, then knock down the next pin.\n\n**B5 — Whole-product plan & positioning shift.**\n- *Build:* enterprise admin/security controls, IP indemnity, compliance certifications, on-prem/VPC deployment options, and audit-grade logging.\n- *References:* named peer-vertical customers, not aggregate usage stats.\n- *Positioning shift:* from the early-adopter pitch (\"10x your speed, the future of coding\") to the pragmatist pitch (\"secure, compliant, governed, and proven at organizations like yours\"). This is the framework's hardest interpersonal cost — the transformational story that won the visionaries actively repels the risk-averse pragmatist buyer.\n\n## What the framework surfaces\n\nThe seductive misread through this period is that the AI-coding race is a *model-capability* race — that whoever has the smartest model crosses. The chasm lens says otherwise: PMF with developers is not PMF with enterprises, and the crossing is won by whoever first completes the **whole product** (security, indemnity, compliance, references, integration into large codebases) for a **specific beachhead** — then shifts positioning from \"transformative\" to \"proven and safe.\" The AI-capex boom funds better models; it does not, by itself, close the whole-product gap that gates the mainstream. A vendor that answers stalling enterprise growth by shipping a bigger model (more features) rather than the governance-and-reference whole product is making exactly the anti-pattern this skill flags.\n\n*Sources: Geoffrey Moore, Crossing the Chasm (1991; 3rd ed. 2014); Everett Rogers, Diffusion of Innovations (1962; 5th ed. 2003); GitHub public statements and blog on Copilot availability, adoption, and enterprise controls (2021–2025); Stack Overflow Annual Developer Survey, AI-tools sections (2023–2025); public reporting on AI-coding tools offering enterprise IP indemnification and security/compliance tiers (2023–2025). Specific figures are stated qualitatively where exact public numbers vary by reporting date.*\n\nFile v1.0.4:examples/salesforce-1999-2007.md\n\n# Method in Action: Salesforce, 1999 → 2007\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.\n\n**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.\n\n**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.\n\n**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.**\n\n**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:\n\n- **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.\n- **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.\n- **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.\n- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.\n\nWalk the audit on Salesforce circa 2001:\n\n- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓\n- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.\n- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.\n- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical references, enterprise support — all missing.\n- **Beachhead choice (B4):** Financial services first (not \"the enterprise\" generically).\n- **Whole-product plan (B5):** Compliance certs, SSO integrations, financial-services case studies, dedicated enterprise sales team.\n- **Positioning shift (B6):** From \"no software, transformative SaaS rebel\" (the early-adopter anti-Siebel pitch) to \"proven, compliant, supported enterprise SaaS\" (the mainstream pitch).\n\nSalesforce did all six. The framework's payoff in this case: **the chasm did not feel like a product problem; it felt like a sales-execution problem.** Diagnosing it as a whole-product + segment-positioning problem is what unlocked the path through. Treating it as a sales problem alone would have produced a bigger sales team selling to the same early-adopter segment, with diminishing returns.\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nGuides agents through a PMF + Chasm Audit for early-stage products with traction, separating product-market fit measurement from whole-product strategy for crossing into mainstream adoption.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nProduct leaders, founders, and strategy teams use this skill to diagnose whether stalled growth comes from missing product-market fit or from a chasm between early adopters and a mainstream beachhead. It structures PMF measurement, whole-product gap analysis, beachhead selection, and positioning shifts.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Business examples or framework outputs may be mistaken for current market evidence.
\nMitigation: Treat outputs as advisory and verify market claims, customer segment evidence, and retention metrics against current first-party data.
\nRisk: Strategic recommendations may be unreliable when the user provides incomplete product, cohort, or segment context.
\nMitigation: Collect active-user cohort data, PMF signal, retention evidence, and a named beachhead before acting on recommendations.
\n\n\n## Reference(s):
\n- [Sources - pmf-crossing-the-chasm](references/sources.md)
\n- [Salesforce, 1999-2007 worked example](examples/salesforce-1999-2007.md)
\n- [AI Coding Assistants Crossing the Chasm worked example](examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md)
\n- [Marc Andreessen - The only thing that matters](https://pmarchive.com/guide_to_startups_part4.html)
\n- [Sean Ellis - The Startup Pyramid archive](https://web.archive.org/web/20100118091421/http://startup-marketing.com/the-startup-pyramid/)
\n- [GitHub Blog - Copilot documentation and adoption references](https://github.blog/)
\n- [Stack Overflow Annual Developer Survey](https://survey.stackoverflow.co/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, guidance]
\n**Output Format:** [Markdown coaching response with structured audit sections and questions]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May pause for user input in coach mode before completing the audit.]
\n\n## Skill Version(s):
\n1.0.4 (source: release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.3: 5 files, 8156 bytes\n\nFiles: examples/salesforce-1999-2007.md (3878b), references/sources.md (1382b), skill-card.md (2528b), SKILL.md (7505b), _meta.json (141b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: pmf-crossing-the-chasm\ndescription: >\n 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.\n 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.\n---\n\n# Product-Market Fit and Crossing the Chasm\n\n## Overview\n\nTwo 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.\n\n**Compose:** business-model-canvas · lean-startup · first-principles · probabilistic-thinking\n\n## When to Use\n\nApply when: early traction exists but PMF is unconfirmed; growth stalls after initial good period; deciding next segment; NPS positive but usage flat.\n**Not when:** no users yet (lean-startup); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has data → run the PMF + Chasm Audit directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. 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.\n2. Check fit: no users yet → lean-startup. Already-mainstream business → wrong framework.\n3. Which segment are you selling to today? Name early adopters vs. early majority concretely.\n> **[WAIT — do not advance until user responds]**\n4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.\n> **[WAIT — do not advance until user responds]**\n5. Name the right next move: \"fix product first\" or \"here is the specific whole-product gap blocking the next segment.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **PMF + Chasm Audit**. PMF first; chasm second.\n\n### Part A — Measure PMF\n\n**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).\n**A2.** Ellis Test: *\"How would you feel if you could no longer use [product]?\"* — Very / Somewhat / Not disappointed / N/A.\n**A3.** Score: ≥ 40% Very disappointed = PMF. 25–40% = approaching. < 25% = no PMF.\n**A4.** Follow-ups: who benefits most? main benefit? top improvements?\n**A5.** Retention curve should flatten (smile curve), not decay to zero.\n\n### Part B — If PMF holds, assess Chasm\n\n**B1.** Classify customers on Rogers's curve (Innovators / Early Adopters / Early Majority).\n**B2.** Name chasm geography: selling today to whom; specific next mainstream sub-segment.\n**B3.** Whole-product gap: integrations, references, certs, support, contracts missing.\n**B4.** Pick one beachhead (bowling-pin — not \"the mainstream\" generically).\n**B5.** Build whole-product for that beachhead; shift positioning to \"proven and safe.\"\n\n### Output: PMF + Chasm Audit\n\n```\n# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed\n```\n\n*→ Method in Action: [Salesforce, 1999 → 2007](examples/salesforce-1999-2007.md)*\n\n## Adoption Packs\n\nSegment geography differs by domain; PMF measurement and chasm framework are universal. Domain packs cover: adopter profiles, whole-product gap, beachhead segments, positioning shift.\n\n- **Enterprise SaaS:** compliance + ecosystem. **Consumer apps:** UX polish + cross-platform + virality. **Developer tools:** procurement-readiness (SSO/support/CIO). **Healthcare:** regulatory + clinical evidence + EMR.\n\nAdding a pack for your industry is the easiest contribution.\n\n## Applying It Well\n\n- Measure PMF — don't intuit it. Founder gut is famously unreliable. Don't cross the chasm by selling harder to the same segment.\n- Whole-product gap is almost always ecosystem (compliance, integrations, references), not features.\n- Beachhead specificity wins: \"financial services mid-market U.S.\" beats \"going enterprise.\"\n- Positioning shift from \"cool/new\" to \"proven/safe\" is the framework's hardest interpersonal cost.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We have PMF\" — citing NPS or signups only | NPS/signups are vanity-adjacent. Use Ellis Test or comparable retention signal. |\n| [D] Doubling sales team as chasm-crossing strategy | Sells harder to the same early-adopter segment → revenue then stall. Gap is whole-product, not headcount. |\n| [D] Treating \"the mainstream\" as one segment | It's composed of distinct verticals. Pick one beachhead (bowling-pin); \"going mainstream\" loses. |\n| [D] Adding features as the whole-product fix | Mainstream needs compliance, integrations, references, contracts — not features. |\n| [D] Same pitch for early adopters and mainstream | Visionaries buy \"transformative\"; pragmatists buy \"proven safe.\" One pitch fails both. |\n| [D] Confusing pricing/sales-process issues with chasm | Growth sometimes stalls for boring reasons. Diagnose carefully before invoking the chasm. |\n| [D] Skipping PMF → jumping straight to chasm strategy | No PMF in any segment = nothing to cross from. |\n| [D] \"We just need better marketing\" | Mainstream decides by peer references, not marketing. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"We have PMF\" with no Ellis Test or retention signal\n- Doubling sales team proposed as answer to stalling growth\n- \"Going mainstream\" with no specific beachhead named\n- Roadmap = more features when need is compliance/integrations/references\n- Same pitch deck for early adopters and enterprise; no vertical references\n\n## Verification\n\n- [ ] PMF measured on active-user cohort (Ellis Test or equivalent)\n- [ ] Current customers classified on Rogers's curve\n- [ ] Specific beachhead named (not \"the mainstream\")\n- [ ] Whole-product gap enumerated (compliance, integrations, references, contracts)\n- [ ] Positioning shift planned; sales process changes named; reference-customer plan exists\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/pmf-crossing-the-chasm** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"pmf-crossing-the-chasm\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1783509264110\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — pmf-crossing-the-chasm\n\n> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\n## Sources\n\n- **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**.\n- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.\n- **Andreessen, Marc.** \"The only thing that matters.\" *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.\n- **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**.\n- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.\n- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.\n- 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).\"\n\nFile v1.0.3:examples/salesforce-1999-2007.md\n\n# Method in Action: Salesforce, 1999 → 2007\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.\n\n**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.\n\n**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.\n\n**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.**\n\n**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:\n\n- **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.\n- **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.\n- **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.\n- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.\n\nWalk the audit on Salesforce circa 2001:\n\n- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓\n- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.\n- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.\n- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical references, enterprise support — all missing.\n- **Beachhead choice (B4):** Financial services first (not \"the enterprise\" generically).\n- **Whole-product plan (B5):** Compliance certs, SSO integrations, financial-services case studies, dedicated enterprise sales team.\n- **Positioning shift (B6):** From \"no software, transformative SaaS rebel\" (the early-adopter anti-Siebel pitch) to \"proven, compliant, supported enterprise SaaS\" (the mainstream pitch).\n\nSalesforce did all six. The framework's payoff in this case: **the chasm did not feel like a product problem; it felt like a sales-execution problem.** Diagnosing it as a whole-product + segment-positioning problem is what unlocked the path through. Treating it as a sales problem alone would have produced a bigger sales team selling to the same early-adopter segment, with diminishing returns.\n\nFile v1.0.3:skill-card.md\n\n## Description:
\nGuides agents through a PMF and chasm audit for early-stage products with traction, helping distinguish product-market fit problems from whole-product and beachhead gaps.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nFounders, product leaders, and strategy teams use this skill to assess whether an early-stage product has product-market fit and whether stalled growth reflects a chasm problem. It produces a structured audit covering active-user evidence, Ellis Test interpretation, adoption-curve classification, beachhead choice, and whole-product gaps.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Business-framework advice can be incomplete or misleading if treated as a substitute for current customer evidence, retention data, or expert review.
\nMitigation: Use the skill as structured guidance, verify cited sources independently, and validate recommendations against current product, customer, and market data before consequential decisions.
\nRisk: The skill footer links to the publisher's external site and GitHub repository.
\nMitigation: Review external destinations and publisher trust before following links or using related assets outside the skill package.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/pmf-crossing-the-chasm)
\n- [Sources - pmf-crossing-the-chasm](references/sources.md)
\n- [The only thing that matters](https://pmarchive.com/guide_to_startups_part4.html)
\n- [The Startup Pyramid](https://web.archive.org/web/20100118091421/http://startup-marketing.com/the-startup-pyramid/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, guidance]
\n**Output Format:** [Markdown]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [The skill is markdown-only and produces business-framework guidance; users should verify cited sources and business evidence before relying on recommendations for important decisions.]
\n\n## Skill Version(s):
\n1.0.3 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 5 files, 8213 bytes\n\nFiles: examples/salesforce-1999-2007.md (3878b), references/sources.md (1382b), skill-card.md (2476b), SKILL.md (7617b), _meta.json (141b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: pmf-crossing-the-chasm\ndescription: >\n 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.\n 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.\n---\n\n# Product-Market Fit and Crossing the Chasm\n\n## Overview\n\nTwo 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.\n\n**Compose:** business-model-canvas · lean-startup · first-principles · probabilistic-thinking\n\n## When to Use\n\nApply when: early traction exists but PMF is unconfirmed; growth stalls after initial good period; deciding next segment; NPS positive but usage flat.\n**Not when:** no users yet (lean-startup); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has data → run the PMF + Chasm Audit directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. 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.\n2. Check fit: no users yet → lean-startup. Already-mainstream business → wrong framework.\n3. Which segment are you selling to today? Name early adopters vs. early majority concretely.\n> **[WAIT — do not advance until user responds]**\n4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.\n> **[WAIT — do not advance until user responds]**\n5. Name the right next move: \"fix product first\" or \"here is the specific whole-product gap blocking the next segment.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **PMF + Chasm Audit**. PMF first; chasm second.\n\n### Part A — Measure PMF\n\n**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).\n**A2.** Ellis Test: *\"How would you feel if you could no longer use [product]?\"* — Very / Somewhat / Not disappointed / N/A.\n**A3.** Score: ≥ 40% Very disappointed = PMF. 25–40% = approaching. < 25% = no PMF.\n**A4.** Follow-ups: who benefits most? main benefit? top improvements?\n**A5.** Retention curve should flatten (smile curve), not decay to zero.\n\n### Part B — If PMF holds, assess Chasm\n\n**B1.** Classify customers on Rogers's curve (Innovators / Early Adopters / Early Majority).\n**B2.** Name chasm geography: selling today to whom; specific next mainstream sub-segment.\n**B3.** Whole-product gap: integrations, references, certs, support, contracts missing.\n**B4.** Pick one beachhead (bowling-pin — not \"the mainstream\" generically).\n**B5.** Build whole-product for that beachhead; shift positioning to \"proven and safe.\"\n\n### Output: PMF + Chasm Audit\n\n```\n# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed\n```\n\n*→ Method in Action: [Salesforce, 1999 → 2007](examples/salesforce-1999-2007.md)*\n\n## Adoption Packs\n\nSegment geography differs by domain; PMF measurement and chasm framework are universal. Domain packs cover: adopter profiles, whole-product gap, beachhead segments, positioning shift.\n\n- **Enterprise SaaS:** compliance + ecosystem. **Consumer apps:** UX polish + cross-platform + virality. **Developer tools:** procurement-readiness (SSO/support/CIO). **Healthcare:** regulatory + clinical evidence + EMR.\n\nAdding a pack for your industry is the easiest contribution.\n\n## Applying It Well\n\n- Measure PMF — don't intuit it. Founder gut is famously unreliable. Don't cross the chasm by selling harder to the same segment.\n- Whole-product gap is almost always ecosystem (compliance, integrations, references), not features.\n- Beachhead specificity wins: \"financial services mid-market U.S.\" beats \"going enterprise.\"\n- Positioning shift from \"cool/new\" to \"proven/safe\" is the framework's hardest interpersonal cost.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We have PMF\" — citing NPS or signups only | NPS/signups are vanity-adjacent. Use Ellis Test or comparable retention signal. |\n| [D] Doubling sales team as chasm-crossing strategy | Sells harder to the same early-adopter segment → revenue then stall. Gap is whole-product, not headcount. |\n| [D] Treating \"the mainstream\" as one segment | It's composed of distinct verticals. Pick one beachhead (bowling-pin); \"going mainstream\" loses. |\n| [D] Adding features as the whole-product fix | Mainstream needs compliance, integrations, references, contracts — not features. |\n| [D] Same pitch for early adopters and mainstream | Visionaries buy \"transformative\"; pragmatists buy \"proven safe.\" One pitch fails both. |\n| [D] Confusing pricing/sales-process issues with chasm | Growth sometimes stalls for boring reasons. Diagnose carefully before invoking the chasm. |\n| [D] Skipping PMF → jumping straight to chasm strategy | No PMF in any segment = nothing to cross from. |\n| [D] \"We just need better marketing\" | Mainstream decides by peer references, not marketing. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"We have PMF\" with no Ellis Test or retention signal\n- Doubling sales team proposed as answer to stalling growth\n- \"Going mainstream\" with no specific beachhead named\n- Roadmap = more features when need is compliance/integrations/references\n- Same pitch deck for early adopters and enterprise; no vertical references\n\n## Verification\n\n- [ ] PMF measured on active-user cohort (Ellis Test or equivalent)\n- [ ] Current customers classified on Rogers's curve\n- [ ] Specific beachhead named (not \"the mainstream\")\n- [ ] Whole-product gap enumerated (compliance, integrations, references, contracts)\n- [ ] Positioning shift planned; sales process changes named; reference-customer plan exists\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/pmf-crossing-the-chasm?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=pmf-crossing-the-chasm** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"pmf-crossing-the-chasm\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1783472337540\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — pmf-crossing-the-chasm\n\n> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\n## Sources\n\n- **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**.\n- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.\n- **Andreessen, Marc.** \"The only thing that matters.\" *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.\n- **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**.\n- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.\n- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.\n- 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).\"\n\nFile v1.0.2:examples/salesforce-1999-2007.md\n\n# Method in Action: Salesforce, 1999 → 2007\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.\n\n**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.\n\n**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.\n\n**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.**\n\n**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:\n\n- **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.\n- **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.\n- **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.\n- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.\n\nWalk the audit on Salesforce circa 2001:\n\n- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓\n- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.\n- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.\n- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical references, enterprise support — all missing.\n- **Beachhead choice (B4):** Financial services first (not \"the enterprise\" generically).\n- **Whole-product plan (B5):** Compliance certs, SSO integrations, financial-services case studies, dedicated enterprise sales team.\n- **Positioning shift (B6):** From \"no software, transformative SaaS rebel\" (the early-adopter anti-Siebel pitch) to \"proven, compliant, supported enterprise SaaS\" (the mainstream pitch).\n\nSalesforce did all six. The framework's payoff in this case: **the chasm did not feel like a product problem; it felt like a sales-execution problem.** Diagnosing it as a whole-product + segment-positioning problem is what unlocked the path through. Treating it as a sales problem alone would have produced a bigger sales team selling to the same early-adopter segment, with diminishing returns.\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nGuides agents through a PMF and Crossing the Chasm audit for startups with early traction, stalled growth, or uncertainty about the next customer segment.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and startup operators use this skill to distinguish unproven product-market fit from chasm-crossing problems, then produce a structured PMF + Chasm Audit with segment, retention, whole-product, beachhead, and positioning guidance.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may activate during broad startup discussions that mention PMF or product-market fit even when the framework is not the best fit.
\nMitigation: Confirm the case has existing users or early traction and is not already a mature channel-scaling problem before relying on the audit.
\nRisk: Business strategy guidance may be misleading if treated as a substitute for product, customer, retention, or market evidence.
\nMitigation: Use the skill's verification checks, including an active-user cohort, Ellis Test or comparable retention signal, specific beachhead, and concrete whole-product gaps.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/pmf-crossing-the-chasm)
\n- [Sources - pmf-crossing-the-chasm](references/sources.md)
\n- [Method in Action: Salesforce, 1999-2007](examples/salesforce-1999-2007.md)
\n- [Marc Andreessen, The only thing that matters](https://pmarchive.com/guide_to_startups_part4.html)
\n- [Sean Ellis, The Startup Pyramid](https://web.archive.org/web/20100118091421/http://startup-marketing.com/the-startup-pyramid/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, guidance]
\n**Output Format:** [Markdown audit and coaching responses]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May pause for user input during coach mode before completing the audit.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 5 files, 8066 bytes\n\nFiles: examples/salesforce-1999-2007.md (3878b), references/sources.md (1382b), skill-card.md (2252b), SKILL.md (7536b), _meta.json (141b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: pmf-crossing-the-chasm\ndescription: >\n 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.\n 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.\n---\n\n# Product-Market Fit and Crossing the Chasm\n\n## Overview\n\nTwo 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.\n\n**Compose:** [business-model-canvas](../business-model-canvas/SKILL.md) · [lean-startup](../lean-startup/SKILL.md) · [first-principles](../first-principles/SKILL.md) · [probabilistic-thinking](../probabilistic-thinking/SKILL.md)\n\n## When to Use\n\nApply when: early traction exists but PMF is unconfirmed; growth stalls after initial good period; deciding next segment; NPS positive but usage flat.\n**Not when:** no users yet ([lean-startup](../lean-startup/SKILL.md)); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has data → run the PMF + Chasm Audit directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. 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.\n2. Check fit: no users yet → [lean-startup](../lean-startup/SKILL.md). Already-mainstream business → wrong framework.\n3. Which segment are you selling to today? Name early adopters vs. early majority concretely.\n> **[WAIT — do not advance until user responds]**\n4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.\n> **[WAIT — do not advance until user responds]**\n5. Name the right next move: \"fix product first\" or \"here is the specific whole-product gap blocking the next segment.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **PMF + Chasm Audit**. PMF first; chasm second.\n\n### Part A — Measure PMF\n\n**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).\n**A2.** Ellis Test: *\"How would you feel if you could no longer use [product]?\"* — Very / Somewhat / Not disappointed / N/A.\n**A3.** Score: ≥ 40% Very disappointed = PMF. 25–40% = approaching. < 25% = no PMF.\n**A4.** Follow-ups: who benefits most? main benefit? top improvements?\n**A5.** Retention curve should flatten (smile curve), not decay to zero.\n\n### Part B — If PMF holds, assess Chasm\n\n**B1.** Classify customers on Rogers's curve (Innovators / Early Adopters / Early Majority).\n**B2.** Name chasm geography: selling today to whom; specific next mainstream sub-segment.\n**B3.** Whole-product gap: integrations, references, certs, support, contracts missing.\n**B4.** Pick one beachhead (bowling-pin — not \"the mainstream\" generically).\n**B5.** Build whole-product for that beachhead; shift positioning to \"proven and safe.\"\n\n### Output: PMF + Chasm Audit\n\n```\n# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed\n```\n\n*→ Method in Action: [Salesforce, 1999 → 2007](examples/salesforce-1999-2007.md)*\n\n## Adoption Packs\n\nSegment geography differs by domain; PMF measurement and chasm framework are universal. Domain packs cover: adopter profiles, whole-product gap, beachhead segments, positioning shift.\n\n- **Enterprise SaaS:** compliance + ecosystem. **Consumer apps:** UX polish + cross-platform + virality. **Developer tools:** procurement-readiness (SSO/support/CIO). **Healthcare:** regulatory + clinical evidence + EMR.\n\nAdding a pack for your industry is the easiest contribution.\n\n## Applying It Well\n\n- Measure PMF — don't intuit it. Founder gut is famously unreliable. Don't cross the chasm by selling harder to the same segment.\n- Whole-product gap is almost always ecosystem (compliance, integrations, references), not features.\n- Beachhead specificity wins: \"financial services mid-market U.S.\" beats \"going enterprise.\"\n- Positioning shift from \"cool/new\" to \"proven/safe\" is the framework's hardest interpersonal cost.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We have PMF\" — citing NPS or signups only | NPS/signups are vanity-adjacent. Use Ellis Test or comparable retention signal. |\n| [D] Doubling sales team as chasm-crossing strategy | Sells harder to the same early-adopter segment → revenue then stall. Gap is whole-product, not headcount. |\n| [D] Treating \"the mainstream\" as one segment | It's composed of distinct verticals. Pick one beachhead (bowling-pin); \"going mainstream\" loses. |\n| [D] Adding features as the whole-product fix | Mainstream needs compliance, integrations, references, contracts — not features. |\n| [D] Same pitch for early adopters and mainstream | Visionaries buy \"transformative\"; pragmatists buy \"proven safe.\" One pitch fails both. |\n| [D] Confusing pricing/sales-process issues with chasm | Growth sometimes stalls for boring reasons. Diagnose carefully before invoking the chasm. |\n| [D] Skipping PMF → jumping straight to chasm strategy | No PMF in any segment = nothing to cross from. |\n| [D] \"We just need better marketing\" | Mainstream decides by peer references, not marketing. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"We have PMF\" with no Ellis Test or retention signal\n- Doubling sales team proposed as answer to stalling growth\n- \"Going mainstream\" with no specific beachhead named\n- Roadmap = more features when need is compliance/integrations/references\n- Same pitch deck for early adopters and enterprise; no vertical references\n\n## Verification\n\n- [ ] PMF measured on active-user cohort (Ellis Test or equivalent)\n- [ ] Current customers classified on Rogers's curve\n- [ ] Specific beachhead named (not \"the mainstream\")\n- [ ] Whole-product gap enumerated (compliance, integrations, references, contracts)\n- [ ] Positioning shift planned; sales process changes named; reference-customer plan exists\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"pmf-crossing-the-chasm\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1783463492867\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — pmf-crossing-the-chasm\n\n> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\n## Sources\n\n- **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**.\n- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.\n- **Andreessen, Marc.** \"The only thing that matters.\" *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.\n- **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**.\n- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.\n- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.\n- 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).\"\n\nFile v1.0.1:examples/salesforce-1999-2007.md\n\n# Method in Action: Salesforce, 1999 → 2007\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.\n\n**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.\n\n**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.\n\n**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.**\n\n**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:\n\n- **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.\n- **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.\n- **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.\n- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.\n\nWalk the audit on Salesforce circa 2001:\n\n- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓\n- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.\n- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.\n- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical references, enterprise support — all missing.\n- **Beachhead choice (B4):** Financial services first (not \"the enterprise\" generically).\n- **Whole-product plan (B5):** Compliance certs, SSO integrations, financial-services case studies, dedicated enterprise sales team.\n- **Positioning shift (B6):** From \"no software, transformative SaaS rebel\" (the early-adopter anti-Siebel pitch) to \"proven, compliant, supported enterprise SaaS\" (the mainstream pitch).\n\nSalesforce did all six. The framework's payoff in this case: **the chasm did not feel like a product problem; it felt like a sales-execution problem.** Diagnosing it as a whole-product + segment-positioning problem is what unlocked the path through. Treating it as a sales problem alone would have produced a bigger sales team selling to the same early-adopter segment, with diminishing returns.\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nHelps agents coach startup teams through product-market fit measurement and crossing-the-chasm diagnosis when early traction exists but growth or segment expansion is uncertain.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users, founders, product leaders, and startup operators use this skill to distinguish missing product-market fit from a chasm-crossing problem and produce a concrete PMF + Chasm Audit for a product or segment.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may ask for company, customer, or segment details during business analysis.
\nMitigation: Avoid sharing confidential business data unless the deployment context and data handling rules permit it.
\nRisk: The skill provides advisory strategy guidance that may be incomplete or unsuitable for a specific market context.
\nMitigation: Have qualified product or business stakeholders review the audit before using it for planning or commercial decisions.
\n\n\n## Reference(s):
\n- [Sources - pmf-crossing-the-chasm](references/sources.md)
\n- [Method in Action: Salesforce, 1999-2007](examples/salesforce-1999-2007.md)
\n- [The only thing that matters](https://pmarchive.com/guide_to_startups_part4.html)
\n- [The Startup Pyramid](https://web.archive.org/web/20100118091421/http://startup-marketing.com/the-startup-pyramid/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, guidance]
\n**Output Format:** [Markdown audit with structured questions, verdicts, gap lists, and action plans]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May stop at explicit WAIT checkpoints while coaching novice users.]
\n\n## Skill Version(s):
\n1.0.1 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.0: 5 files, 8146 bytes\n\nFiles: examples/salesforce-1999-2007.md (3878b), references/sources.md (1382b), skill-card.md (2504b), SKILL.md (7536b), _meta.json (141b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: pmf-crossing-the-chasm\ndescription: >\n 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.\n 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.\n---\n\n# Product-Market Fit and Crossing the Chasm\n\n## Overview\n\nTwo 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.\n\n**Compose:** [business-model-canvas](../business-model-canvas/SKILL.md) · [lean-startup](../lean-startup/SKILL.md) · [first-principles](../first-principles/SKILL.md) · [probabilistic-thinking](../probabilistic-thinking/SKILL.md)\n\n## When to Use\n\nApply when: early traction exists but PMF is unconfirmed; growth stalls after initial good period; deciding next segment; NPS positive but usage flat.\n**Not when:** no users yet ([lean-startup](../lean-startup/SKILL.md)); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has data → run the PMF + Chasm Audit directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. 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.\n2. Check fit: no users yet → [lean-startup](../lean-startup/SKILL.md). Already-mainstream business → wrong framework.\n3. Which segment are you selling to today? Name early adopters vs. early majority concretely.\n> **[WAIT — do not advance until user responds]**\n4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.\n> **[WAIT — do not advance until user responds]**\n5. Name the right next move: \"fix product first\" or \"here is the specific whole-product gap blocking the next segment.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **PMF + Chasm Audit**. PMF first; chasm second.\n\n### Part A — Measure PMF\n\n**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).\n**A2.** Ellis Test: *\"How would you feel if you could no longer use [product]?\"* — Very / Somewhat / Not disappointed / N/A.\n**A3.** Score: ≥ 40% Very disappointed = PMF. 25–40% = approaching. < 25% = no PMF.\n**A4.** Follow-ups: who benefits most? main benefit? top improvements?\n**A5.** Retention curve should flatten (smile curve), not decay to zero.\n\n### Part B — If PMF holds, assess Chasm\n\n**B1.** Classify customers on Rogers's curve (Innovators / Early Adopters / Early Majority).\n**B2.** Name chasm geography: selling today to whom; specific next mainstream sub-segment.\n**B3.** Whole-product gap: integrations, references, certs, support, contracts missing.\n**B4.** Pick one beachhead (bowling-pin — not \"the mainstream\" generically).\n**B5.** Build whole-product for that beachhead; shift positioning to \"proven and safe.\"\n\n### Output: PMF + Chasm Audit\n\n```\n# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed\n```\n\n*→ Method in Action: [Salesforce, 1999 → 2007](examples/salesforce-1999-2007.md)*\n\n## Adoption Packs\n\nSegment geography differs by domain; PMF measurement and chasm framework are universal. Domain packs cover: adopter profiles, whole-product gap, beachhead segments, positioning shift.\n\n- **Enterprise SaaS:** compliance + ecosystem. **Consumer apps:** UX polish + cross-platform + virality. **Developer tools:** procurement-readiness (SSO/support/CIO). **Healthcare:** regulatory + clinical evidence + EMR.\n\nAdding a pack for your industry is the easiest contribution.\n\n## Applying It Well\n\n- Measure PMF — don't intuit it. Founder gut is famously unreliable. Don't cross the chasm by selling harder to the same segment.\n- Whole-product gap is almost always ecosystem (compliance, integrations, references), not features.\n- Beachhead specificity wins: \"financial services mid-market U.S.\" beats \"going enterprise.\"\n- Positioning shift from \"cool/new\" to \"proven/safe\" is the framework's hardest interpersonal cost.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We have PMF\" — citing NPS or signups only | NPS/signups are vanity-adjacent. Use Ellis Test or comparable retention signal. |\n| [D] Doubling sales team as chasm-crossing strategy | Sells harder to the same early-adopter segment → revenue then stall. Gap is whole-product, not headcount. |\n| [D] Treating \"the mainstream\" as one segment | It's composed of distinct verticals. Pick one beachhead (bowling-pin); \"going mainstream\" loses. |\n| [D] Adding features as the whole-product fix | Mainstream needs compliance, integrations, references, contracts — not features. |\n| [D] Same pitch for early adopters and mainstream | Visionaries buy \"transformative\"; pragmatists buy \"proven safe.\" One pitch fails both. |\n| [D] Confusing pricing/sales-process issues with chasm | Growth sometimes stalls for boring reasons. Diagnose carefully before invoking the chasm. |\n| [D] Skipping PMF → jumping straight to chasm strategy | No PMF in any segment = nothing to cross from. |\n| [D] \"We just need better marketing\" | Mainstream decides by peer references, not marketing. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"We have PMF\" with no Ellis Test or retention signal\n- Doubling sales team proposed as answer to stalling growth\n- \"Going mainstream\" with no specific beachhead named\n- Roadmap = more features when need is compliance/integrations/references\n- Same pitch deck for early adopters and enterprise; no vertical references\n\n## Verification\n\n- [ ] PMF measured on active-user cohort (Ellis Test or equivalent)\n- [ ] Current customers classified on Rogers's curve\n- [ ] Specific beachhead named (not \"the mainstream\")\n- [ ] Whole-product gap enumerated (compliance, integrations, references, contracts)\n- [ ] Positioning shift planned; sales process changes named; reference-customer plan exists\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"pmf-crossing-the-chasm\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1782886713613\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — pmf-crossing-the-chasm\n\n> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\n## Sources\n\n- **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**.\n- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.\n- **Andreessen, Marc.** \"The only thing that matters.\" *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.\n- **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**.\n- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.\n- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.\n- 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).\"\n\nFile v1.0.0:examples/salesforce-1999-2007.md\n\n# Method in Action: Salesforce, 1999 → 2007\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.\n\n**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.\n\n**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.\n\n**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.**\n\n**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:\n\n- **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.\n- **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.\n- **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.\n- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.\n\nWalk the audit on Salesforce circa 2001:\n\n- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓\n- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.\n- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.\n- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical references, enterprise support — all missing.\n- **Beachhead choice (B4):** Financial services first (not \"the enterprise\" generically).\n- **Whole-product plan (B5):** Compliance certs, SSO integrations, financial-services case studies, dedicated enterprise sales team.\n- **Positioning shift (B6):** From \"no software, transformative SaaS rebel\" (the early-adopter anti-Siebel pitch) to \"proven, compliant, supported enterprise SaaS\" (the mainstream pitch).\n\nSalesforce did all six. The framework's payoff in this case: **the chasm did not feel like a product problem; it felt like a sales-execution problem.** Diagnosing it as a whole-product + segment-positioning problem is what unlocked the path through. Treating it as a sales problem alone would have produced a bigger sales team selling to the same early-adopter segment, with diminishing returns.\n\nFile v1.0.0:skill-card.md\n\n## Description:
\nGuides agents through a PMF and Crossing-the-Chasm audit for startups with early traction, helping distinguish product-market fit gaps from whole-product and beachhead strategy gaps.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nFounders, product leaders, startup operators, and strategy agents use this skill to evaluate whether early traction indicates real product-market fit and, if PMF holds, identify the beachhead and whole-product gaps needed to reach mainstream customers.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Business examples and PMF thresholds may be treated as guaranteed predictors of startup outcomes.
\nMitigation: Use the audit as an advisory framework and validate recommendations against current customer, retention, segment, and market evidence.
\nRisk: The skill can produce misleading strategy if users skip PMF measurement or provide weak cohort data.
\nMitigation: Require an active-user cohort, Ellis Test or equivalent retention signal, and a specific beachhead before acting on chasm recommendations.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/pmf-crossing-the-chasm)
\n- [Sources - pmf-crossing-the-chasm](artifact/references/sources.md)
\n- [Method in Action: Salesforce, 1999-2007](artifact/examples/salesforce-1999-2007.md)
\n- [deciqAI](https://deciqai.com)
\n- [The only thing that matters](https://pmarchive.com/guide_to_startups_part4.html)
\n- [The Startup Pyramid](https://web.archive.org/web/20100118091421/http://startup-marketing.com/the-startup-pyramid/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, guidance, analysis]
\n**Output Format:** [Markdown with structured audit sections and step-by-step coaching prompts]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include hard-stop questions for interactive coaching before completing the audit.]
\n\n## Skill Version(s):
\n1.0.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: Product-Market Fit and Crossing the Chasm Owner: deciqai Summary: Activate when: user says \"PMF,\" \"product-market fit,\" \"crossing the chasm,\" \"early adopter to mainstream,\" \"whole product,\" \"we're stuck after our beachhead,... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:10:33.948Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/pmf-crossing-the-chasm.json) v1.","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed"},{"language":"text","snippet":"# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed"},{"language":"text","snippet":"# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed"},{"language":"text","snippet":"# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed"},{"language":"text","snippet":"# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed"},{"language":"text","snippet":"# PMF + Chasm Audit: \nPart A — PMF: cohort definition | Ellis % → verdict | follow-ups | retention curve\nPart B — Chasm (if PMF held): Rogers classification | chasm geography (today → next) |\n whole-product gap list | beachhead chosen | whole-product plan (refs/integrations/certs/sales/positioning)\n Anti-patterns: ☐ no generic \"mainstream\" ☐ whole-product ≠ features ☐ sales process changed"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: pmf-crossing-the-chasm\ndescription: >\n 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.\n 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.\n More: deciqai.com/c/pmf-crossing-the-chasm\n---\n\n# Product-Market Fit and Crossing the Chasm\n\n## Overview\n\nTwo 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.\n\n**Compose:** business-model-canvas · lean-startup · first-principles · probabilistic-thinking\n\n## When to Use\n\nApply 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.\n**Not when:** no users yet (lean-startup); already-mainstream business scaling proven channels; issue is pricing/sales-process not chasm.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has data → run the PMF + Chasm Audit directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. 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.\n2. Check fit: no users yet → lean-startup. Already-mainstream business → wrong framework.\n3. Which segment are you selling to today? Name early adopters vs. early majority concretely.\n> **[WAIT — do not advance until user responds]**\n4. Run PMF measurement (Ellis Test). Only after PMF confirmed, raise chasm.\n> **[WAIT — do not advance until user responds]**\n5. Name the right next move: \"fix product first\" or \"here is the specific whole-product gap blocking the next segment.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **PMF + Chasm Audit**. PMF first; chasm second.\n\n### Part A — Measure PMF\n\n**A1.** Active-user cohort: ≥ 2 weeks use, multiple sessions (not signups).\n**A2.** Ellis Test: *\"How would you feel if you could no longer use [product]?\"* — Very / Somewhat / Not disappointed / N/A.\n**A3.** Score: ≥ 40% Very disappointed = "},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"pmf-crossing-the-chasm\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1784225433948\n}"},{"path":"references/sources.md","content":"# Sources — pmf-crossing-the-chasm\n\n> *Primary sources for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\n## Sources\n\n- **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**.\n- **Rogers, Everett M.** *Diffusion of Innovations*. Free Press, 1962; 5th ed. 2003. **The adoption-curve foundation**.\n- **Andreessen, Marc.** \"The only thing that matters.\" *Pmarchive*, June 25, 2007. https://pmarchive.com/guide_to_startups_part4.html **Most-cited primary PMF formulation**.\n- **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**.\n- **Benioff, Marc.** *Behind the Cloud*. Jossey-Bass, 2009. **Primary source for the Salesforce 1999–2007 chasm-crossing case**.\n- **Salesforce.com, Form 10-K** (SEC, multiple fiscal years 2005–2007) — primary-source revenue and segment data.\n- **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).**\n- **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.**\n- 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).\""},{"path":"examples/ai-coding-assistants-crossing-the-chasm-2023-2026.md","content":"# Method in Action: AI Coding Assistants Crossing the Chasm (2023–2026)\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA 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.\n\nBecause the framework separates PMF from chasm, we run Part A first, then Part B.\n\n## Part A — Measure PMF\n\n**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.\n\n**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.\n\n**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.\n\n**A4 — Follow-ups.**\n- *Who benefits most?* Individual developers and small, autonomy-heavy teams writing greenfield or boilerplate-heavy code.\n- *Main benefit?* Speed on well-trodden tasks — scaffolding, tests, boilerplate, unfamiliar-API lookup.\n- *Top improvements requested?* Reliability on large existing codebases, correctness guarantees, and control over what the tool sees and does.\n\n**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.\n\n**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"},{"path":"examples/salesforce-1999-2007.md","content":"# Method in Action: Salesforce, 1999 → 2007\n\n> *Example for the [pmf-crossing-the-chasm](../SKILL.md) skill.*\n\nA worked example. Not founder hagiography — primary-source documented in Marc Benioff's autobiography and SEC filings.\n\n**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.\n\n**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.\n\n**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.**\n\n**Salesforce's chasm strategy (2001–2007).** Pick beachhead-by-beachhead in the early majority:\n\n- **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.\n- **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.\n- **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.\n- **By 2007**, Salesforce was a credible enterprise vendor. Revenue: $497M FY2007 (SEC 10-K), up from $176M FY2005. The chasm was crossed.\n\nWalk the audit on Salesforce circa 2001:\n\n- **PMF (Part A):** Strong in SMB sales-team segment. Retention solid. Word-of-mouth high. ✓\n- **Rogers classification (B1):** Mostly Early Adopters in SMB; some Innovators.\n- **Chasm geography (B2):** Selling today = SMB sales teams; next segment = mid-market financial services, then enterprise.\n- **Whole-product gap (B3):** Compliance, audit trails, integrations, vertical refer"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":2096,"uniquenessScore":44,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T03:36:41.726Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T03:36:41.726Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:32:59.679Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}