Unclassified

62 — Community Strategy

Status: CANONICAL · Commercial OS
Owner: Founder
Last verified: 2026-07-21

Purpose

The community plan — with the stage-honest core decision up front: we do not launch a community space yet. Empty rooms kill credibility; this document defines what we build instead now, and the explicit gate for when a real community launches.

Target audience: Founder; future community/marketing hire; investors (asking about moats).

1. The Stage Decision

A community is a promise of other people. Pre-launch, we can't keep it — a Slack with 30 lurkers and one founder posting into silence damages the exact trust we're building. So:

Phase 1 (now → ~50 customers): Community-of-practice behaviors without a community space:

  • The reply network: newsletter repliers and LinkedIn regulars get real founder relationships (60 §3, 59 §3) — a community of correspondence, one-to-one, that no empty forum can match.
  • The Design Partner Circle (exists now): the 8-partner cohort is the community seed — monthly group call (shared learnings, roadmap input), a private channel that's genuinely active because it has a job (feedback loop 44 §5), and early-access standing. Membership is earned (partnership), which is why it works at n=8.
  • Guest presence, not owned space: the founder is a useful member of existing CS and RevOps communities (Slack groups, subreddits, practitioner forums) under strict value-first rules: answer questions, share teardowns, never drop links unprompted. We borrow rooms until we can fill one.

Phase 2 gate (all true): 50+ customers · 10+ users who already talk to each other about the product unprompted · a founder-independent host (CS hire or community hire) · a reason to exist beyond marketing (see §2).

2. The Phase-2 Community (designed now, launched at the gate)

Name: The Continuity Circle — practitioners of human-AI collaborative work.
The job (why members come back): not product chat — practice chat: how teams actually divide work with their Twins, approval-policy patterns, signal-tuning recipes, the workbench morning as a discipline. The community's content is the members' operating wisdom; the product is the shared context.
Structure: private space, customer-only core + invited practitioners · programming: monthly practitioner call (a member presents their morning/workflow — not us), quarterly roadmap session (Design Partner Circle tradition, scaled), an annual awards moment ("catches of the year" — celebrated saves, 63 tie-in).
Moderation doctrine: founder-voice rules apply (57 §3); vendor-pitch-free including from us; competitor users welcome (practitioners first — the category grows the company, 05 §5).

3. Why Community Matters Strategically (the patience rationale)

Category creation needs a native population: analysts count practitioners, not vendors (66) · expansion and renewal correlate with peer-witnessed value ("the forwarded morning" at community scale 46 §2) · the practitioner vocabulary the community develops becomes the category's language — written by our members, in our terms (18). Worth doing; worth doing late.

KPIs: Phase 1 — reply-network size (subscribers with ≥ 2 founder exchanges) · Design Partner Circle attendance ≥ 75% · borrowed-room contributions/week ≥ 3. Phase 2 gate readiness reviewed quarterly · post-launch: MAU/member ≥ 40%, member-generated content ≥ 60% of programming, community-attributed retention delta (tracked honestly).

Related: 60 Newsletter · 57 Founder-led · 63 Events · 44 CS Playbook