DiscordCommunitySolopreneurAI AgentAutomationBuildInPublicOpen Source

Discord Community From 0 to 146 Members: A Solo Founder's Playbook (With 3 AI Bots)

· 45 min read

TL;DR

March 14, 2026: I created a Discord server.
March 24: 146 members.
Ad budget: $0.
Community management headcount: 0 (3 AI bots handle it).

Here's the entire process broken into an SOP, including the mistakes I made and the things that worked surprisingly well.


Step Zero: Why Discord, Not Slack or a Facebook Group

Facebook Group Slack Discord
Discoverability Medium Low (invite only) High (Google-indexable)
Channel structure Messy Good Excellent
Bot/automation Limited Limited free tier Fully open (Webhooks + Bot API)
Message history Available 90-day limit (free) Unlimited
International Skews older Enterprise Developer-friendly, global
Cost Free Expensive at scale Free

Discord wins for developer/tech communities because of unlimited automation potential. I run 3 AI bots that would be impossible on Slack's free tier or in a Facebook Group.


Step 1: Server Architecture (Day 1)

Plan your channels before inviting anyone:

Ultra Lab HQ
├── #welcome          ← First thing new members see
├── #announcements    ← Admin-only updates
├── #general          ← Free chat
├── #ask-agent        ← AI Agent technical questions
├── #showcase         ← Members show their projects
├── #threads-tips     ← Social media growth tactics
├── #probe-reports    ← UltraProbe scan reports
└── #feedback         ← Product suggestions

Common mistake: too many channels. Don't exceed 8 at launch. Few members + many channels = every channel looks dead = feels empty.


Step 2: The 3 AI Bots (Day 2-3)

This is the core infrastructure.

Bot #1: The Greeter (discord-intro-responder)

Trigger: Check #welcome for new intros every 3 minutes
Action: Generate personalized welcome via Gemini Flash
Specialty: Makes jokes based on the member's username

Example:

New member: "Hey everyone, I'm Allen. I work in web3."

Lobster reply: "Welcome Allen! A web3 person visiting an AI community —
here to see what web2.5 looks like? 😄
We've got a few people working on blockchain + AI integration.
Check out #ask-agent for those discussions.
Feel free to ask anything!"

Why not use Discord's built-in welcome? Because "Welcome to the server!" is generic. Nobody feels seen. An AI-generated personal message makes every member think "wow, this community actually pays attention."

Bot #2: The Vibe Keeper (discord-lobster-vibes)

Trigger: Check #general every 20 minutes
Condition: If the last 5 messages contain something worth responding to
Action: Generate a lobster-persona reply via Gemini Flash
Personality: Sarcastic, funny, occasionally roasts people (affectionately)

Why this bot is the most important: Communities die when nobody talks. When everyone's lurking, you need someone who "goes first." The lobster is the member who never lurks.

But be careful: The lobster doesn't reply to everything. It has an "interest threshold" — it only chimes in when the conversation is actually interesting. Otherwise it becomes an annoying bot.

Bot #3: The Memory (discord-memory-builder)

Trigger: Scan new messages every 10 minutes
Action: Extract member background info from conversations
Storage: discord-member-memory.json
Fields: background, interests, tech level, join date

Example memory:

{
  "allen_web3": {
    "background": "Web3 developer, 3 years experience",
    "interests": ["blockchain", "AI", "DeFi"],
    "level": "intermediate",
    "joinedAt": "2026-03-18",
    "notableMessages": ["Asked about AI + smart contract auditing"]
  }
}

The value: When Allen shows up again 3 weeks later, the lobster can say "Allen! Remember your question about AI + smart contract auditing? We just shipped a new scan feature. Want to try it?"

The highest form of community management is remembering every member. Humans can't remember 146 people's backgrounds. JSON can.


Step 3: Seed Members (Day 1-3)

The hardest part isn't 100 → 1000. It's 0 → 10.

What I did:

  1. Invite 5 friends — They don't need to be active. They just need to exist so the server isn't empty.
  2. Post on Threads — "I started a Discord for AI builders. Come hang out."
  3. Link in every blog post — "Join the Discord discussion" at the bottom.
  4. Link on UltraProbe results page — People who just scanned might have questions.

Week 1 numbers:

Day 1: 5 (all friends)
Day 2: 8 (3 from Threads)
Day 3: 12 (4 from blog)
Day 5: 23 (organic invites start)
Day 7: 41

The inflection point was Day 5. Past 20 members, "natural conversations" start happening. You're no longer performing a monologue.


Step 4: Growth Engine (Day 4-10)

After 20 members, growth accelerates. The keys:

4.1 Content-Driven

Every blog post and Threads update ends with a Discord link:

"Want to discuss more? 40+ people are talking about AI automation in our Discord → [link]"

Don't say "join my Discord." Say "40+ people are discussing [specific topic]." Numbers + topic = attraction.

4.2 The Bot "Wow" Effect

New member joins → personalized welcome within 3 minutes → "This community is different."

The first impression conversion rate is extremely high. Most servers greet you with silence. We greet you by name within 3 minutes.

4.3 The Viral Post

March 22, I published a blog post: "We Made 4 AI Agents Talk to Each Other on Discord." That post drove:

Daily visitors: ~3,000 (GA4)
Discord new members: +40
Total members that day: ~120

One viral post = one growth leap. This is why blog and community must work together.

4.4 The Numbers

Day 1:  5
Day 3:  12
Day 5:  23
Day 7:  41
Day 8:  78  ← viral blog post
Day 9:  123 ← continued effect
Day 10: 146

Operating Cost

Item Monthly
Discord server $0 (free)
Gemini Flash API (welcome + vibes) $0 (free tier)
Ollama local inference ~$10 (electricity)
Webhook calls $0
My time ~2 hours/week
Total ~$10/month

146-member community. $10/month operating cost.


Mistakes I Made

Mistake 1: Lobster was too chatty

Initially the lobster replied every 10 minutes. Members started saying "this bot is annoying." After changing to 20 minutes + interest threshold, people actually started saying "lobster, where are you? Come chat!"

Lesson: An AI bot's posting frequency should be like an introverted but interesting person — doesn't respond to everything, but when it speaks, it's worth reading.

Mistake 2: Too many channels too early

Started with 12 channels. #web3-chat and #design-talk were permanently dead. Cut to 8, and #general conversation volume actually increased.

Lesson: Channel count = member count / 20. 146 members → 7-8 channels is right.

Mistake 3: Not letting members show off

First 5 days were all me sharing things. After adding #showcase, members started voluntarily sharing their projects. Community vitality comes from members, not the owner.


Current Automation Architecture

WSL2 Ubuntu
├── discord-intro-responder.js  (every 3 min)
│   └── New member → Gemini Flash → personalized welcome
├── discord-lobster-vibes.js    (every 20 min)
│   └── #general chat → interest check → lobster reply
├── discord-memory-builder.js   (every 10 min)
│   └── Scan messages → extract profiles → JSON storage
└── discord-member-memory.json  (persistent memory)
    └── 146 member profiles: background / interests / level

All open-sourced at github.com/ppcvote/discord-lobster.


Next: From Community to Revenue

146 members is great, but if it doesn't convert to business value, a community is just a chat room.

My plan:

  1. Community → Blog traffic — Great questions from members become blog posts
  2. Community → Product feedback — Ask members what features they want
  3. Community → CustomersUltraGrowth subscribers get VIP channel access
  4. Community → Open source contributors — People interested in lobster can contribute

A community isn't the destination. It's the top of the funnel.


What You Can Copy

  1. Create a Discord server — 5 minutes
  2. Lobster botsOpen source, fork and run
  3. Seed members — Invite 5 friends. Don't wait until the server is "perfect"
  4. Content-driven growth — Every blog post links to Discord
  5. Patience — 0 → 20 is painful. After 20, it grows naturally

You don't need 146 people. You need 20 people who talk. The lobsters handle the rest.


"A community isn't something you build and wait for people to come. A community is you showing up every day until others start showing up too. The lobsters cover my shifts."

Weekly AI Automation Playbook

No fluff — just templates, SOPs, and technical breakdowns you can use right away.

Join the Solo Lab Community

Free resource packs, daily build logs, and AI agents you can talk to. A community for solo devs who build with AI.

Need Technical Help?

Free consultation — reply within 24 hours.