Enovari Community Building Playbook

Additional Info
Discord has become the default gathering place for AI-product communities. Midjourney, Stable Diffusion, LangChain, Cursor, and dozens of other AI tools run their primary communities on Discord. Users already expect to find an AI product's community there. It is free, real-time, supports bots and integrations, and scales from 5 people to 500,000+.

Additional Info
Start minimal. Too many empty channels signal a dead community. Launch with 5-7 channels and expand only when conversation justifies it.

Phase 1 -- Launch (0-50 members)
`` INFORMATION #welcome-and-rules -- Auto-displayed on join. Brief rules, link to docs, what Enovari is. #announcements -- Product updates, releases, blog posts. Read-only for members. COMMUNITY #general -- Open conversation. This is where early life happens. #show-and-tell -- Users share what they built with Enovari. SUPPORT #help -- Questions and troubleshooting. FEEDBACK #feature-requests -- Ideas and votes (use a bot or emoji reactions). ``

Phase 2 -- Growing (50-200 members)
Add channels based on observed demand: `` COMMUNITY #introductions -- New members introduce themselves. #off-topic -- Non-Enovari chat to build social bonds. #ai-news -- Curated AI industry discussion. DEVELOPMENT #api-and-integrations -- Technical integration discussion. #bug-reports -- Structured bug reporting. SPECIAL #beta-testers -- Private channel for early-access users. #contributors -- Private channel for active contributors. ``

Phase 3 -- Scaling (200+ members)
`` #jobs-and-hiring -- AI job board (drives traffic). #tutorials -- Community-written guides. #events -- AMAs, workshops, hackathons. Voice channels for office hours / live demos. ``

Additional Info
Set clear, useful topic descriptions for every channel. These appear at the top of the channel and help new members understand the purpose instantly.

Additional Info
Admin: Enovari team. Manages server, posts announcements, handles escalations. Moderator: Trusted community member who helps keep conversations productive and enforces community guidelines. Beta Tester: Early access to new features. Expected to try builds within 48 hours and report feedback. Contributor: Has contributed code, documentation, tutorials, or integrations to the Enovari ecosystem. Champion: Active advocate who consistently helps others, refers new members, and creates content about Enovari. Founding Member: One of the first 25 people to join the Enovari community. This role is never given again. Member: Verified community member with full access to public channels. New: Just joined. Some restrictions (no links, no embeds) for the first 10 minutes to prevent spam. Require phone verification (Settings > Moderation > Highest) to reduce spam. Slow mode on #general (5-second cooldown) to prevent spam floods early. Disable @everyone and @here for all non-admin roles. Keep #announcements write-locked to admins. Enable Community Features in server settings once you reach 50+ members (unlocks Server Discovery, Welcome Screen, and Membership Screening).

Additional Info
`` Welcome to the Enovari community, {user}! We are building persistent memory for AI -- so your AI assistants remember across sessions, tools, and teams. Here is how to get started: 1. Introduce yourself in #introductions -- tell us what you are building 2. Got a question? Drop it in #help 3. Want to show off something you built? Post it in #show-and-tell 4. Have an idea for the product? Submit it in #feature-requests Useful links: Website: https://enovari.ai Setup Guide: https://enovari.ai/setup-guide.html Start your free trial: https://enovari.ai/signup.html What AI tools are you using today? ` ` Hey {name}, welcome to the Enovari Discord! I'm [your name] from the team. Just wanted to say hi personally. If you have any questions about Enovari or need help getting set up, feel free to ping me here or in any channel. What brought you to Enovari? ``

Carl-bot
Reaction roles, auto-moderation, logging, custom commands, welcome messages | Free | The best all-in-one bot for small servers. Handles moderation, welcome messages, and role assignment without paying for anything.

Suggester
Feature-request voting with upvotes and status tracking | Free | Clean interface for collecting and managing feature requests. Supports statuses: Approved, In Progress, Completed, Declined.

YAGPDB
Custom commands, auto-responders, Reddit/RSS feeds | Free | Good for automating repetitive tasks and feeding external content into Discord.

Ticket Tool
Support ticket system in #help | Free tier available; premium starts at $4/mo for extra features | Free tier covers basic ticket creation. Upgrade only if ticket volume is high.

Dyno
Moderation (auto-ban, word filters), timed mutes | Free tier available; premium at $4.99/mo | Free tier covers basic moderation. The auto-mod is solid for catching spam and slurs.

Correction note on MEE6
MEE6 is frequently recommended for Discord bots, but its free tier has become increasingly limited. Leveling, XP systems, and most useful features now require MEE6 Premium ($11.95/mo). For a $0 budget, Carl-bot is the better choice -- it handles welcome messages, auto-moderation, reaction roles, and custom commands all for free.

Bot Configuration Steps
1. Go to https://carl.gg and click "Invite Carl-bot" -- select your server. 2. Welcome message: Dashboard > Welcome & Leave > Enable welcome message. Paste the welcome message template above. Set the channel to #welcome-and-rules. 3. Auto-moderation: Dashboard > Automod > Enable anti-spam (duplicate messages, mass mentions, invite links from non-admins). Start with moderate settings and tighten later. 4. Reaction roles: Dashboard > Reaction Roles > Create a new reaction role panel. Post it in #welcome-and-rules. Example roles to offer: "I'm a developer" (gives access to dev channels) "I'm an AI enthusiast" (general interest) "Notify me about events" (gets pinged for AMAs, hackathons) 5. Logging: Dashboard > Logging > Enable message edits/deletes, join/leave, and mod actions. Send logs to a private #mod-log channel. 6. Custom commands: Create a !docs command that replies with a link to the setup guide, and a !pricing command that links to the pricing page. 1. Invite Suggester from https://suggester.js.org. 2. Run .setup in your server to start the configuration wizard. 3. Set the suggestions channel to #feature-requests. 4. Set the approved suggestions channel (can be the same channel or a separate #roadmap channel). 5. Configure who can approve/deny suggestions (Admin and Moderator roles). 6. Enable automatic upvote/downvote reactions on new suggestions. 1. Go to Server Settings > Integrations > GitHub. 2. Authenticate with the GitHub account that owns the Enovari repos. 3. Select the repositories to follow (e.g., mcp-server-enovari, enovari-examples). 4. Choose which events to post (recommended: new issues, PRs opened/merged, releases). 5. Set the output channel to #api-and-integrations or a dedicated #github-feed channel.

Additional Info
This is the single hardest problem. An empty Discord is worse than no Discord. 1. Seed conversations yourself. The founding team should post daily in #general -- share what you are working on, ask genuine questions, post interesting AI links. Treat it as a public group chat among the team. 2. Auto-welcome with a question. Configure the welcome bot to ask new members a question: "What AI tools are you using today?" or "What would you build if AI had perfect memory?" This prompts a reply. 3. Post daily content. One post per day minimum: Monday: Product update or changelog Tuesday: AI industry news + your take Wednesday: Tip or tutorial using Enovari Thursday: Community spotlight or question Friday: Casual / fun / meme / off-topic 4. Pin active threads. When a good conversation starts, pin it or create a thread to keep it visible. 5. Use threads aggressively. Threads make a server look busier than it is by multiplying visible activity. 6. Respond to every message within hours. In the early days, zero messages should go unanswered. 7. Cross-post from other channels. Share tweets, blog comments, and emails (with permission) in Discord to create visible activity. 8. Host weekly events. Even with 5 people, a weekly "office hours" voice chat creates rhythm. 9. Create "conversation starters" as a habit. Post open-ended questions that are easy to answer: "What's the most underrated AI tool you've used this month?" or "What's one thing you wish your AI remembered automatically?" These low-friction questions pull lurkers into conversation. 10. React to every message. Even if you do not reply, adding an emoji reaction to a message signals that someone is reading. A message with zero reactions feels ignored.

Pattern to copy
All of these succeed because the founding team is visibly present and responsive, not because of fancy bots or channel structures.

Additional Info
These communities are worth studying for channel structure, tone, and engagement tactics: Cursor (cursor.sh) -- AI code editor. Started tiny, grew by being genuinely useful in their support channel. Devs answer questions fast. Pieces for Developers (pieces.app) -- Small AI dev tool. Very active team presence, daily engagement. Mem.ai -- AI memory/notes product (closest to Enovari's space). Good channel structure for a small team. LangChain (langchain) -- Started as a small open-source project Discord and grew to 50K+. Strong developer focus, good use of forum channels. Ollama (ollama.com) -- Local LLM runner. Rapid growth from a small base. Strong technical help culture. Continue.dev -- AI coding assistant. Small but active Discord with tight developer community. Raycast -- Productivity tool. Not AI-only, but a textbook example of a well-run small product Discord: clean channels, fast responses, genuine team presence.

GitHub Discussions
Free | Integrated with code, familiar to devs, SEO-indexed by Google, zero maintenance | Limited customization, no non-dev audience appeal, tied to GitHub | Developer-first products with open-source components

Circle.so
$49/mo+ (Basic) | Beautiful UI, courses, events, member directory | Expensive, no free tier | Funded startups with community budget

Reddit (own subreddit)
Free | Massive built-in audience, SEO, no maintenance | You do not own it, algorithm-dependent, moderation burden | Supplementary channel, not primary

GitHub Discussions + Discord
Free | Async (GitHub) + real-time (Discord), covers both developer and general audiences | Two platforms to manage | Recommended for Enovari at $0

When to add Discourse
If non-developer users become a significant portion of the community (50%+) and GitHub Discussions feels too technical, spin up a Discourse instance on a $6/mo DigitalOcean droplet.

Additional Info
Discord handles real-time community, support, casual interaction. GitHub Discussions handles long-form technical questions, RFCs, feature proposals that need to be searchable months later. Both are free and familiar to developers. Discord conversations that produce useful answers get summarized and posted to GitHub Discussions as a knowledge base.

Tip
If you do not want Discussions tied to a specific code repo, create a dedicated enovari/community repo specifically for community discussions. This keeps code repos focused on code.

Additional Info
1. Go to your repository (e.g., github.com/enovari/mcp-server-enovari or github.com/enovari/community). 2. Navigate to Settings > General > Features. 3. Check the "Discussions" box. 4. A new "Discussions" tab appears on your repo.

Ideas & RFC
Open | Longer-form proposals and design discussions. For features that need community input before building. | Thought bubble

Additional Info
Pin a "Start Here" discussion in General that covers: ```

Additional Info
Website: https://enovari.ai Setup Guide: https://enovari.ai/setup-guide.html API Docs: [link] Discord: [link] ```

Additional Info
Create a .github/DISCUSSION_TEMPLATE/ directory with templates: ``yaml title: "[Feature Request] " labels: ["enhancement"] body: type: textarea attributes: label: Problem description: What problem does this feature solve? placeholder: "I want to..." validations: required: true type: textarea attributes: label: Proposed Solution description: How do you think this should work? type: textarea attributes: label: Alternatives Considered description: What other approaches have you thought about? type: dropdown attributes: label: Priority to you options: Nice to have Important Critical -- blocking my workflow ``

Additional Info
GitHub Discussions are indexed by Google. Every question-and-answer thread becomes a potential search result. This means: Users searching "how to add persistent memory to Claude Code" might land on your Discussion. Feature request threads with detailed descriptions attract long-tail search traffic. Over time, your Discussions tab becomes an organic traffic source with zero additional effort.

Additional Info
Not every Discord conversation should be duplicated, but high-value ones should be: 1. After resolving a support question in Discord: Summarize the Q&A as a GitHub Discussion in the Q&A category. Link back to the Discord thread. 2. After a productive feature request conversation in Discord: Create a formal Feature Request discussion on GitHub with the refined version. 3. Weekly: Scan #help and #feature-requests in Discord for threads that deserve a permanent home in GitHub Discussions. This bridges the gap between Discord's real-time energy and GitHub's permanent, searchable archive.

Additional Info
The first 25 members should be hand-picked, not acquired through marketing. 1. Personal outreach (highest ROI). Identify 50 people who: Already use AI tools daily Have tweeted/posted about AI memory, context windows, or persistent AI Are building AI agents or LLM-powered apps Are active in adjacent communities (LangChain, CrewAI, AutoGen, etc.) Send each a personal DM (not a mass message): > "Hey [name], I saw your [post/project] about [specific thing]. We're building Enovari -- persistent memory for AI assistants. Just launched our community Discord and would love to have you as an early member. Here's the link: [invite]. No pressure, just thought you'd find the conversation interesting." 2. Invite existing users. Every person who has signed up for Enovari gets a personal invite to Discord. Add the Discord link to: Post-signup email Dashboard/app sidebar Documentation footer API response headers (creative touch: X-Community: https://discord.gg/enovari) 3. Tap your network. Friends, colleagues, Twitter mutuals, people you have met at meetups. Ask 20 people to join and be active for the first two weeks. 4. Founding member badge. Create a special @Founding Member` role for the first 25 people. This is exclusive and never given again. People value being early.