{"slug":"strategy/business-strategy/62-community-strategy","title":"62 — Community Strategy","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/62-community-strategy.mdx","bytes":4182,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Founder\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nThe 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.\n\n**Target audience:** Founder; future community/marketing hire; investors (asking about moats).\n\n---\n\n## 1. The Stage Decision\n\nA 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:\n\n**Phase 1 (now → ~50 customers): Community-of-practice _behaviors_ without a community _space_:**\n\n- **The reply network:** newsletter repliers and LinkedIn regulars get real founder relationships ([60 §3](60-newsletter-strategy.md), [59 §3](59-linkedin-strategy.md)) — a community of correspondence, one-to-one, that no empty forum can match.\n- **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](../08-customer-success/44-customer-success-playbook.md)), and early-access standing. Membership is earned (partnership), which is why it works at n=8.\n- **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.\n\n**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).\n\n## 2. The Phase-2 Community (designed now, launched at the gate)\n\n**Name:** **The Continuity Circle** — practitioners of human-AI collaborative work.\n**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.\n**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](63-events-strategy.md) tie-in).\n**Moderation doctrine:** founder-voice rules apply ([57 §3](57-founder-led-marketing.md)); vendor-pitch-free including from us; competitor users welcome (practitioners first — the category grows the company, [05 §5](../02-category-market/05-category-definition.md)).\n\n## 3. Why Community Matters Strategically (the patience rationale)\n\nCategory creation needs a native population: analysts count practitioners, not vendors ([66](../12-corporate/66-analyst-relations.md)) · expansion and renewal correlate with peer-witnessed value (\"the forwarded morning\" at community scale [46 §2](../08-customer-success/46-expansion-strategy.md)) · the practitioner vocabulary the community develops becomes the category's language — written by our members, in our terms ([18](../03-positioning-messaging/18-terminology-guide.md)). Worth doing; worth doing _late_.\n\n**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).\n\n---\n\n**Related:** [60 Newsletter](60-newsletter-strategy.md) · [57 Founder-led](57-founder-led-marketing.md) · [63 Events](63-events-strategy.md) · [44 CS Playbook](../08-customer-success/44-customer-success-playbook.md)\n"}