Community (in GTM30)
The persistent public surface where your users see how your team works, how your product moves, and how you listen — replacing one-way marketing with visible, two-way interaction.
Last updated: December 12, 2025
Definition
The persistent public surface where your users see how your team works, how your product moves, and how you listen — replacing one-way marketing with visible, two-way interaction.
Why it matters
Community is a live input stream into product, content, and GTM decisions; it produces data, trust, and compounding assets.
In practice
- Operate on loops (presence → signal → conversion → reliability → personalization), not on “vibes”.
- Convert repeated questions into durable, linkable assets (docs, templates, pSEO pages).
Common mistakes
- Treating community as a private support hotline rather than a public, indexable knowledge surface.
- Answering the same questions forever instead of building canonical pages.
Related terms
- Canonical page / canonical link — The single page you want threads, content, ambassadors, and internal tools to link to for a topic — so knowledge compacts instead of fragmenting across repeated answers.
- Signal — A meaningful observation from community, ambassadors, support, or content performance (friction, requests, language patterns, objections) that can be tagged, routed, and acted on.
- Signal schema — A minimal, consistent set of fields for capturing signals so Product, Sales, and Support can act without losing context (source, ICP segment, lifecycle stage, tags, severity, status, and link).
- Loops (community operating system) — The repeatable mechanisms that turn community work into a compounding engine: presence loop, signal loop, conversion loop, reliability loop, and personalization loop.
- Conversion engine (if → then rules) — A lightweight ruleset that turns repeated questions and high-signal threads into durable assets (docs, templates, pSEO pages) instead of re-answering forever.
- Expert-operator layer — A non-staff contributor layer with deep problem-solving depth who validate workflows, co-author docs, and host topic sessions — distinct from ambassadors.