Web3 Community Marketing Skill

For: Protocol marketers, DAO contributors, Web3 founders, community managers

Philosophy: In Web3, the community IS the product. No ad budget beats an activated, believing community.

How to Use This Skill

Identify the request and route to the right module:

MODULE 1 — Community Architecture

Trigger: Project has no community structure or is starting from scratch.

Step 1: Community Intent Audit

Ask if not provided:

• Protocol/project type? (DeFi, NFT, DAO, infrastructure, security, L1/L2)
• Primary audience? (retail holders, developers/builders, institutions, degens, normies)
• Goal of community? (product feedback, governance, growth, liquidity, talent)
• Platforms currently active? (Discord, Telegram, Twitter/X, Farcaster, Lens)
• Team size for community management? (solo, small team, DAO contributors)

Step 2: Platform-Audience Match

Step 3: Channel Architecture (Discord model)

Structure Discord with these zone types:

📢 INFORMATION (read-only)
├── #announcements
├── #roadmap
└── #security-alerts

👋 ONBOARDING
├── #start-here (rules + links)
├── #verify (Collab.Land or Guild)
└── #introductions

💬 COMMUNITY
├── #general
├── #price-talk (isolated — keeps noise out of main)
└── #memes

🛠️ BUILDERS
├── #dev-chat
├── #grants
├── #feedback-and-bugs
└── #integrations

🏛️ GOVERNANCE
├── #proposals
├── #voting-discussion
└── #treasury-updates

🎙️ EVENTS
├── #spaces-and-calls
└── #recordings

Rules: Always isolate price talk. Never mix governance with memes. Keep #start-here pinned and updated.

Step 4: Deliver

Output a Community Architecture Blueprint with platform strategy, channel map, role structure, and moderation guidelines.

MODULE 2 — Growth & Acquisition

Trigger: Community exists but needs more members or reach.

Organic Growth Levers

Twitter/X (highest ROI in Web3):

• Post technical threads that solve real problems — developers share what's useful
• Engage daily with 5–10 relevant accounts (reply with value, not "great post!")
• Host weekly X Spaces — consistency beats virality
• Build in public: ship updates, share mistakes, celebrate milestones
• Use $TOKEN cashtag and protocol hashtags consistently

Discord:

• Collaborate with complementary protocols for cross-server events
• Feature builders publicly — "Builder Spotlight" posts drive dev word-of-mouth
• Run structured AMAs with founders/team — invite communities from other servers
• Activate Guild.xyz or Collab.Land for token-gated roles that reward participation

Telegram:

• Ideal for price-sensitive, fast-moving communities
• Use bots for anti-spam (Rose, Combot) and announcements
• Pin key resources; keep the main group signal-high
• Create a separate "announcements-only" channel linked to the main group

Partnership Channels

• Protocol-to-protocol collabs: joint spaces, shared announcements
• KOL seeding: identify 5–10 mid-tier voices (10K–100K followers) aligned with your category
• Ecosystem grants from L1/L2s often come with marketing support — apply actively

Growth KPIs to track weekly:

• Discord: new members, message volume, active users (7d/30d), retention rate
• Telegram: subscriber growth, message rate, link clicks
• Twitter/X: follower growth, impressions, engagement rate, profile visits

MODULE 3 — Engagement Activation

Trigger: Community exists but is silent or declining in activity.

Diagnosis First — ask:

• When was community most active? What was happening then?
• What % of members have ever posted?
• Is the team visible in the community daily?
• Is there a reward or recognition system for contributors?

Activation Playbook

Week 1 — Spark:

• Post a genuine, controversial question in #general ("Hot take: [your protocol] will replace [incumbent] in 18 months. Agree or disagree?")
• Launch a "Community Temperature Check" poll — people engage with votes before text
• Personally @ mention 10 silent long-term members: "Hey [name], curious what you think about [topic]"

Week 2 — Habit Formation:

• Start a recurring daily/weekly format: "Monday Alpha," "Weekly Recap," "Builder Friday"
• Recognize top contributors publicly with custom roles or shoutouts
• Create a low-friction contribution path: reactions, polls, and 1-click feedback before expecting long posts

Week 3 — Community Identity:

• Name your community (not just "the [Protocol] community") — identity creates belonging
• Create community-specific lore, inside jokes, terminology
• Surface "founding member" stories — who were the first believers and why

Engagement frameworks that work in Web3:

• Scarcity + Recognition: "This week's most helpful community member gets a custom role + early testnet access"
• Co-creation: "We're deciding between these two features — community votes" (then actually build the winner)
• Transparency loops: Share team metrics, treasury data, or roadmap progress openly — Web3 communities reward radical transparency

MODULE 4 — Onboarding Flows

Trigger: New members join but don't understand the protocol or never activate.

The 72-Hour Onboarding Window

Research shows: if a new community member doesn't engage within 72 hours of joining, they likely never will.

Onboarding Sequence Design

JOIN
 ↓
Auto-welcome DM (bot) — sent immediately
 ↓
#start-here channel — pinned, always updated
 ↓
Verification step (optional but filters bots)
 ↓
Introduce yourself prompt (low-friction: "Where are you from + how did you find us?")
 ↓
Role selection (I'm a: holder / developer / researcher / just curious)
 ↓
Directed to relevant channels based on role
 ↓
Week 1: 3 touchpoints from community team or bot

Welcome DM Template (adapt to project):

👋 Welcome to [Protocol] community!

Here's how to get started:
→ Read #start-here for the essentials
→ Introduce yourself in #introductions
→ Join us this [DAY] for our weekly X Space

We're building [ONE LINE VALUE PROP]. Glad you're here.

Questions? Drop them in #general — community has your back.

Education Sequencing

Don't try to explain everything on day 1. Sequence:

• Day 1: What we do in 1 sentence
• Day 3: Why it matters (the problem we solve)
• Day 7: How it works (technical if relevant to audience)
• Day 14: How to participate (governance, grants, staking, building)

MODULE 5 — Developer Community

Trigger: Goal is to attract builders, developers, or technical contributors.

Developer Community ≠ Regular Community

Developers hate being marketed to. They respond to:

• Genuine technical depth (show your work)
• Real problems solved, not promises
• Respectful, non-pushy engagement
• Well-documented tools and SDKs
• Fast responses when they're stuck

Developer Funnel

AWARENESS → CONSIDERATION → ACTIVATION → RETENTION → ADVOCACY
   ↓              ↓              ↓            ↓           ↓
Technical      GitHub/docs    First build  Ongoing    Grants +
content        quality        experience  support     recognition

Tactics that actually work:

• Office Hours: Weekly 30-min call where devs can ask any technical question
• Bounties & Grants: Publish clear, well-scoped bounties with realistic rewards
• "Build with us" threads: Document what's possible to build on your protocol — ideas attract builders
• Fast issue response: Nothing kills dev community faster than unanswered GitHub issues
• Spotlight finished projects: "Dev built X on our protocol" — social proof for other builders

Metrics for developer community health:

• Active GitHub contributors (monthly)
• Grants applications received
• Projects built / deployed on protocol
• SDK downloads or API calls (if measurable)
• Questions asked and % answered in <24h

MODULE 6 — Metrics & Reporting

Trigger: User needs to measure, track, or report on community health.

Community Health Scorecard

COMMUNITY HEALTH REPORT — [Protocol Name]
Period: [Date range]

GROWTH
├── Total members: [X] (+/-% vs last period)
├── New members: [X]
├── Churn (left/banned): [X]
└── Net growth: [X]

ENGAGEMENT
├── Daily Active Users: [X]
├── Weekly Active Users: [X]
├── Messages sent (7d): [X]
├── Threads started: [X]
└── Engagement rate: [DAU/Total Members]%

QUALITY SIGNALS
├── % of members who have ever posted: [X]%
├── Top 10 contributors (by messages or helpfulness)
├── Support tickets resolved: [X] (avg response time: [X]h)
└── Sentiment score: [Positive/Neutral/Negative ratio]

HIGHLIGHTS
└── [Notable community moments, milestones, wins this period]

RED FLAGS
└── [Declining metrics, FUD events, issues to address]

NEXT PERIOD FOCUS
└── [Top 3 community priorities]

Tools for measurement:

• Discord: built-in analytics + Combot + Statbot
• Telegram: Combot Analytics
• Twitter/X: native analytics + TweetBinder for hashtags
• Cross-platform: Orbit.love, Common Room, Talkwalker (for listening)

General Quality Rules

1. Community is long-term. Don't optimize for vanity metrics (total members). Optimize for active, contributing members.
2. The team must be visible. No community management skill compensates for an absent founding team.
3. Crypto communities are fast. Response time matters — silence during crises destroys trust permanently.
4. Never fake engagement. Bots, paid shills, and artificial activity always get exposed in Web3.
5. Reward contributors publicly. Recognition is the highest ROI tool in community building.

Web3 Community Marketing Skill v1.0

Built for protocol marketers and DAO contributors who treat community as a core growth lever.