WHAT'S
ON
DISCORD SERVER SETUP AND MANAGEMENT

The Room That Runs Itself

A Discord that greets people, ranks them, and posts every day without you in it.

The same engine that runs the 2ndBrain Way room, built on your server from a written spec, handed over, and kept working. It welcomes every stranger inside the hour, tells you which door they came through, promotes people for what they actually do, and puts one real post out a day. When there is nothing real to say, it says nothing.

Two ways to buy What you get

The problem, in your words

I have people who like what I do and nowhere to put them. I opened a Discord once and it went quiet in a week because I was the only one in it. I do not have time to greet everybody, set up roles, and post every day.

That is the whole problem, and it is not a Discord problem. It is a hands problem. A room needs somebody at the door, somebody keeping score, and somebody who shows up every morning. This engine is those three people, and it was built because I did not have them either.

What is handed over

Thirteen things, every one of them running today on my own server.

Nothing on this list is a plan. Each item is a working piece of the room at discord.gg/34bwN5XSDN, moved onto your server and pointed at your people.

IN THE ROOM
  • The server, built from a spec. Roles, categories, channels, forum tags, permissions, onboarding prompts and the welcome screen are written in one file. Plan shows the diff, apply builds what is missing and fixes what drifted, audit reports what is there that should not be. The tool never deletes anything; that stays a human's hand.
  • One door per place you post. A never-expiring invite for each source: your site, YouTube, TikTok, LinkedIn, Facebook, Instagram, X, Threads, Reddit, text, local. Every join is attributed to the door it came through, so you know which channel is actually sending people.
  • The welcome, inside the hour. One message to each new member with three doors in it. A nudge on day two if they have not introduced themselves. A reminder for your next live session between day seven and twenty-one. Each sent once, ever. Closed DMs are respected and never retried.
  • The ladder. Guest on the first introduction, then Member, Builder and Superhero, earned by what someone does in a rolling thirty days: a first reply to somebody else, a first thread, three threads or one thing built. Promotion only, never demotion, and a public shout in your wins channel each time.
  • The daily post. One post a day from a four-week bank we write together, with your next session date filled in and a short log of what shipped. Sunday opens the introductions thread. Thursday points at an open build thread. Saturday points at the week's most-reacted thread. Quiet hours ten at night to seven in the morning. Never twice a day.
  • The monthly roll. First Monday of the month, everyone who reached Builder or Superhero the month before, named. If nobody did, nothing is posted.
  • Signage that never drifts. The welcome, the rules, the board explainer and the welcome screen are edited in place by remembered message id, never re-posted, so there are never three versions of the welcome. A lint refuses em dashes, exclamation points and any literal price before anything goes up.
  • One funnel for announcements. Every public post goes through one function that refuses it unless an approval is attached. One exception: the moment you go on air, a fixed template fires to your live-now channel with nobody in the loop. Identical posts are deduped for a day. It can ping one named role and never everyone.
  • The board. One message, edited in place, showing your open capacity this month. If the number cannot be verified inside forty-eight hours it shows no number rather than a stale one.
  • The bridge. Every question in your ask-anything channel gets a written reply in the thread from your assistant, briefed on your business by you and me. While you are live, your live-chat channel is relayed onto the show and answered on air, the Stage opens by itself, and up to three raised hands are approved to speak.
  • Polls, drops and the feed. Native polls with up to ten options. Files and clips dropped into any channel or forum with an optional pin. A feed mirror so anything you ship lands in the room the same minute it lands on your site.
  • Paid roles from Stripe. If you sell a membership through Stripe, an active subscription becomes a role and a cancelled one loses it. A role it cannot explain is reported, never force-removed.
  • The kill switch and the hold. One action stops all posting across the room. Edits, replies and DMs keep working, because a paused room you cannot ask questions of is a room you cannot diagnose.

Day one

Your room exists by the end of the call.

The server is built from the spec while you watch, with you as owner and the bot as an administrator. The invites are minted and written down by source. The signage is pinned. The bridge is answering.

The first stranger who accepts an invite gets the welcome inside the hour, and the join shows up under the door they used.

While you sleep

Every hour, every day, every first Monday.

The welcome and the nudge run hourly. The ladder is recomputed hourly. The daily post goes out inside quiet hours. The roll posts monthly. Joins are attributed as they happen. Questions get answered in-thread.

When you go live, the live-now post fires and the Stage opens. When you are not live, the room still moves. When there is nothing real to say, it stays quiet rather than inventing something.

Handed over, then broken in front of you

THE METHOD

I build it on your server, on a call, in front of you. Not on mine and copied over: on yours, with your names on the channels and your bank in the daily post.

Then I break it while you watch. I close a test member's DMs and show you the welcome skip them without a crash. I put an em dash in the signage and show the lint refuse it. I flip the kill switch and show the room go quiet inside a minute, then bring it back.

You leave with the spec, the bank, the invite table and the recording of it being built. When it breaks later, and it will, you reply to my email and we fix it.

You keep: the spec file, the four-week bank, the invite table by source, the recording, and the bot on your own developer account.

FOR YOU IF
  • A creator with an audience and no hands. People already like what you do. They need a door and a greeting.
  • An owner whose customers ask the same twelve questions. The bridge answers in writing, in public, so the next person finds it.
  • A coach or a teacher with a cohort. The ladder gives people a reason to show up between sessions.
NOT FOR YOU IF
  • You want a bot that fakes activity. Nothing here invents content. If there is nothing real, it posts nothing.
  • You will not write the four-week bank with me. The daily post is your voice or it is nobody's.
  • You want a private group chat. Discord requires a Community server with at least seven channels for the pieces above to work.

Two ways to buy

Buy it once, or have me run it.

Both shapes hand you the same thing. The difference is who fixes it the day a platform changes something. Prices are on the card, and the card is one message away.

one time

Build and handover

Built on your accounts, on a call, in front of you. Then broken on purpose so you see where it fails before it fails on you. You keep everything: the spec, the config, the bank, the recording of it being built.

Price on the card

Ask me for the card

monthly

Run and keep it working

Everything in the build, plus a standing seat of mine on it: the checks every morning, the fix when a platform moves, the refresh of what it posts, and a reply line to me when it breaks. Cancel with 30 days notice and keep the build.

Price on the card

Ask me for the card

Every checkout runs on Stripe: cards, Apple Pay, Google Pay, a receipt in your inbox. Or text (904) 478-0440 and ask for the Room card.

Straight answers, including the limits.

What does the bot need on my server?

Administrator, because setting channel permissions requires it and a bot can only grant what it holds. Plus two privileged intents, Message Content and Server Members, switched on in the Discord developer portal. Both are free and need no Discord review under 10,000 members. The bot lives on your developer account, not mine.

Does it message strangers?

Three messages, ever: the welcome inside the hour, a nudge on day two if they have not introduced themselves, and one reminder for your next live session. Anyone with DMs closed is skipped and never retried.

Will it post when there is nothing to say?

No. The Thursday pick, the Saturday pick and the monthly roll each return nothing when there is nothing real, and the daily post refuses to run twice in a day or inside quiet hours.

Does it work with my paid membership?

If you sell through Stripe, yes. An active or trialing subscription becomes a role, a cancelled or unpaid one loses it. Any other billing system is a build, quoted separately.

Can the assistant say something I have not approved?

Public announcements are refused without an approval id. Replies in your ask-anything channel come from a written brief you and I author. While you are live, a redactor masks prices, phone numbers, email addresses and names from your customer list before anything reaches the screen.

Can it delete a channel by mistake?

No. The builder creates and patches by name and never deletes. Removing a channel is a human's click.

What is not included?

Server boosts, which you buy from Discord. Your art, which is yours or a brand add-on. A live-stream stage with chat on screen, which is the broadcast package. Both together, wired, is the studio solution.

Plug and play with the broadcast package

The Room already knows how to open a Stage, fire a live-now post and relay a live-chat channel onto a show. Add The Booth and those three things light up the moment you go on air, with no second setup.

Both, wired together and run as one, is The Studio Solution.