How should the server be structured?
Smaller than you think. Dead channels signal dead community, so launch with a minimal spine — announcements, general, support, one or two topic channels — and add only when an existing channel sustains daily conversation. Every empty channel you close makes the live ones feel busier.
Gate advanced areas behind roles earned through contribution, not just wallet-holding. The gating isn't exclusivity theater; it creates the ladder that gives members something to climb.
- Launch spine: announcements, general, support, 1–2 topics
- Add channels only after sustained demand; merge or archive ruthlessly
- Role-gate depth: contributor and core areas earned by work
What does good onboarding look like?
The first five minutes decide the retention curve. Good flow: verification (bot-gate), a two-question role selector (what brings you here / what do you build), and — critically — one specific first action: introduce yourself with a template, claim a starter task, vote on something live. Members who act in session one return at multiples of the rate of members who only read.
Instrument it: track verification completion, first-action rate and day-7 return. Those three numbers diagnose almost every 'our Discord is dead' complaint.
What keeps a server alive month after month?
Rhythm plus recognition. Rhythm: a predictable weekly calendar — team update, community call, one recurring fun format — so members build the habit of returning. Recognition: contributor spotlights, role promotions announced publicly, and real influence (core members getting genuine input on decisions) as the top rung.
Ops budget honestly: a competently run Web3 Discord costs $2k–8k/month in moderation, event programming and tooling. The projects that skip this spend more re-acquiring the members who left.
Questions we hear about this
Five to seven. Announcements, general, support, and one or two topic channels cover a young community. Expansion should follow sustained conversation density, not org-chart ambition — ten dead channels kill more communities than one crowded channel ever did.
Gate depth, not entry. Public outer rings let curious people evaluate you; token- or contribution-gated inner areas reward commitment. Fully-gated servers strangle their own growth funnel unless the product itself is membership.
A pinned, honest FAQ answer, an auto-responder that links to it, and moderation that redirects rather than punishes curiosity. The volume of wen-token noise is inversely proportional to how much real product news you ship — the fix is cadence, not bans.
Both, with Discord as the structured community home (roles, events, contribution systems) and Telegram as the broadcast-and-sentiment layer. If forced to choose: consumer/degen audiences skew Telegram; builder/DAO audiences skew Discord.