Community Manager
Your community never sleeps. Now your mod doesn't have to either.

Answers from your own docs
Learns from corrections
Discord + Telegram
The Problem
After running communities at Fermah (0 to 100K) and Irys (5K to 100K), I know firsthand that managing crypto communities is a 24/7 job that never stops. The same questions get asked 50 times a day. Spam is relentless. And good human mods burn out fast because the work is repetitive and the hours are brutal.
I kept thinking: most of these answers already exist somewhere in docs, past messages, or FAQs. Why am I paying people to copy-paste the same response over and over? That's not community management, that's a search engine with a salary.
How It Works
- AI auto-answers community questions by searching a knowledge base you build from your docs, website, and past answers
- Moderation and spam detection powered by Claude, with auto-delete for obvious spam and flagging for edge cases
- Escalation system for questions the AI can't confidently answer, routed to your team with one-click resolution
- Learning loop that improves over time. When a human corrects an answer, the AI learns from it and gets better next time
- Points and leaderboard to reward active community members
- Stripe billing with checkout, usage tracking, and a customer portal
- Team management dashboard with invite system, live stats, and settings for confidence thresholds and moderation toggles
The Build
This was the most structured vibecoding project I've done. 9 phases over multiple sessions, all built with Claude Code.
Phase 1 started with auth and team setup. Phase 2 was knowledge ingestion with pgvector for semantic search. Phase 3 got the Discord bot live and answering questions. From there I layered on escalations, moderation, Telegram support, a points system, and finally the full admin dashboard with Stripe billing.
The architecture is a real SaaS setup: Next.js frontend on Vercel, Supabase for the database, a Fly.io worker running the Discord bot, and Stripe for payments. Each phase was committable and deployable on its own, which saved me multiple times when sessions hit rate limits.
What's Next
All 9 phases are shipped and deployed. The Discord worker is live and connected. Next up is end-to-end testing with a real community: testing the full loop of questions, escalations, spam detection, and dashboard stats. After that, soft launch to a handful of crypto projects I know need this.