A new community does not die in month six because the theme was wrong. It dies in week one because there was nobody home. The founder published a URL, posted a rules thread, and waited. Three strangers registered, posted into silence, and left. The founder decided “forums are dead” and opened a Discord. The Discord is now an unread firehose with the same three strangers.
This is a founding calendar: what you do in the thirty days around launch. Staff, rules, seed content, a launch week, the first ten humans, and the decision to stay open. It is not the 30-day plan for a member who already joined. That article starts after registration. This one tries to make sure there is a room worth registering for. Read both. Do not run the member plan as a substitute for having staff.
It is also not the Discourse first-week wizard and not the first-month Discourse failure modes. Those are product-specific. The sequence below is the same on XenForo, Discourse, phpBB, or IPS. The buttons differ. “Someone answers on purpose” does not.
If you are relaunching a neglected board, use the same calendar. You are founding again. If you are migrating, finish the destination decision and the import rehearsal before day 0. Do not launch onto a staging mess.
What “launched” actually means
A public URL is not a launch. A launch is a week in which all of the following are true:
- At least two humans who are not the same person will answer a new topic within a day
- A stranger can see where to post in one screen
- There are already conversations to join, not only rules
- Mail or in-app notifications work for a throwaway account
- You know what you will do if ten people show up, and what you will do if one does
If you cannot staff that week, do not announce. Build in private. A quiet private beta with five invited people is a community. A public empty index is an ad for a closed shop.
Days −14 to −1: found it before you publish it
Launch week is too late to invent a team, a map, and a voice.
Name the job, not the vibe
Write one sentence: who is this for, doing what, that they cannot do in the Discord / subreddit / comment thread they already have. If you cannot, you are building a forum because you like forums. That is allowed as a hobby. It is not a launch.
Examples that work:
- “Camera people who want critique that is not a Facebook group.”
- “Customers of Product X who want searchable answers, not a 24-hour Slack.”
- “Players of this server who need LFG and patch notes that still exist next month.”
Examples that do not:
- “A place for everyone to discuss everything.”
- “Like the old forum but modern.”
- “We’ll see who shows up.”
The sentence decides the room map. Broad rooms, not a 40-forum costume.
Hire staff before you hire members
One founder is a blog with comments. A community needs a shift.
Minimum viable staff:
| Seat | Job in month one | Who it cannot be |
|---|---|---|
| Founder / admin | Break-glass, billing, backups, final bans | The only account that posts jokes |
| On-duty greeter | First reply to new topics, 24-hour budget | A title with no calendar |
| Second pair of eyes | Queue when the greeter is away | The founder’s alt “for testing” |
Two humans is the floor. Three is better. They do not need moderator badges on day one. They need a shared private room (staff forum / staff category) and a written “I am on duty these evenings.”
XenForo community practice is specific about accounts, and it applies on every product: do not casually post as the root Admin. The Admin handle stays a neutral, system-like identity for technical notes, official announcements, and structured warnings. Founders and moderators talk like humans on personal profiles without a giant staff badge. Members will not argue with a god. A launch full of god-posts is a press release.
If you expect a larger team later, decide now how junior people cannot ban the founder. On XenForo, community practice names Moderator Panel by Andrew and its Protected Users list so junior mods cannot ban admins. Other products need an equivalent habit (don’t hand out full admin, don’t share the founder password). The large-forum moderation piece is the queue; this is the hiring.
Write rules that fit on one screen
Launch rules are not a legal department. They are:
- Who can post, and what happens if they don’t
- The one or two lines you will actually enforce in week one (harassment, illegal, spam)
- Where applications / NSFW / trading live, if anywhere
- How to contact staff
Everything else is a later FAQ. A 3,000-word covenant on day 0 is how you guarantee nobody reads it and you do not enforce it. Put the long version in a linked page if legal needs it. The index gets one screen.
Build the empty shape
Do this before seed threads, so you do not seed the wrong rooms.
- Five or six rooms, not forty. Announcements, the subject, help if you do help, lounge, meta, staff. The structure article owns the why.
- Markers (prefixes or tags) for the two filters you already know you need. Not twenty.
- Permissions tested with a throwaway. Guest can read what Google should read. Guest cannot read Staff. A brand-new user can post in the obvious room. Discourse people: do not add every trust level to the security table; that is a known month-one outage. XenForo people: do not Never Registered in the main forum.
- Mail. One confirm or welcome that arrives. SPF/DKIM. Discourse people: skipped SMTP is valid, but then you do not have digests — do not pretend you do.
- Backup and restore rehearsal on whatever you actually run. A launch without a restore is a dare.
Do not install a shop, a points economy, or a 40-rung rank plugin. Nobody has earned a rank. A shop rewards people who already post.
Seed content: conversations, not a museum
An empty index is the failure mode. Seed threads exist so the first stranger has something to reply to, not something to admire.
A launch-ready seed set:
| Thread | Room | Who starts it | Why it exists |
|---|---|---|---|
| How this place works | Announcements or Meta | Admin handle | Map + watches + “how to get help.” Short. |
| Introduce yourself | Subject or Lounge | Personal staff profile | First-post magnet. Staff reply to every one. |
| What are you working on this week? | Subject | Personal staff profile | A stranger can answer without lore. |
| Open question of the actual topic | Subject | Personal staff profile | The reason the site exists, as a question |
| Known issues / start here (if support) | Help | Admin or staff | Stops ticket-zero from being “where do I post?” |
| Staff scratchpad | Staff | Admin | Duty roster, not jokes |
That is enough. Do not seed 40 “welcome to this subforum” posts. Do not copy Wikipedia into a knowledge base on day −3. Do not pin everything; pinned walls are how people learn to skip the top of the room.
Quality bar: each public seed thread should be a thread you would reply to as a stranger. If it only works as a broadcast, it is an announcement. Put it in Announcements.
If you are Discourse: write the welcome as how TL0 works (one image, read a bit, the site will promote you). If you are XenForo: write how watches and What’s New work. Product nouns belong in the seed. Product manuals do not replace the seed.
Invite the first ten before you invite the internet
Launch week is not a Product Hunt campaign. It is ten people who already said they would show up.
Pick them on purpose:
- Three who will post, not just lurk
- Two who will answer someone else
- A couple who represent the actual audience, not your staff Discord
- Nobody who only wants a moderator title
Invite them to a private or quiet week if you can (closed registration, or a URL you have not tweeted). Ask them to introduce themselves and to answer the open question. Reply. Fix the two things they trip on (usually mail and “where do I post”). Then you have a launch.
Ten is a number you can greet. A hundred signups on day 0 with one greeter is how you recreate the empty-feeling board with more accounts.
Days 1–7: launch week is a shift
Treat launch week like an event, because it is one.
Publish once, with a duty roster
Pick a 7-day window. Write names against evenings. The greeter is on. The second pair of eyes is backup. The founder does not disappear into CSS.
Announcement copy that works:
- Who it is for (the sentence from day −14)
- Where to start (introduce + open question)
- That staff will answer
- What it is not (not the Discord replacement, not a helpdesk SLA you cannot keep)
Announcement copy that does not: a feature list, a theme screenshot, “we’re finally live!!!”
Answer like the room is listening
The first reply teaches the next visitor whether anyone is home. In launch week, every public first post gets a human reply within 24 hours. A template is allowed (“Welcome — I moved this to Help and tagged 2.3 — related thread here”). A like and silence is not.
Use the personal profile for conversation. Use the Admin handle only if you are announcing or warning. If the founder argues politics as Admin on day 3, you have set the culture and you will not like it.
Do not add rooms
Someone will ask for a subforum. The answer in week one is no, plus a prefix if the request is a real filter. Empty new rooms are how launch week looks dead on Friday.
Do not vanish into the theme
A broken permission is a launch bug. A header font is not. If you are still in extra.less or a Discourse theme component while a first post sits unanswered, you are founding a style demo.
Run the throwaway test every day
Register a new account. Confirm mail. Post in the obvious room. Make sure you can see your own post as a guest if guests should. Discourse: hit the TL0 image cap on purpose so you remember what you promised in the welcome. XenForo: confirm the validating / Registered group can actually post.
Keep Discord in its lane
If you already have a chat room, pick one job for it during launch: bring people to a thread, or don’t mention the forum at all until week two. A Discord that mirrors every forum post and also never links back will eat the launch. Hybrid patterns are a later article. Week one is “here is the thread.”
Days 8–21: the quiet week is the real test
The people who were going to try you have tried you. Now you learn whether a loop exists.
Keep one ritual
The weekly open question continues. Same room, same prefix, new date. Staff starts it even if last week’s died at four replies. Rituals fail when staff skip them, not when members are shy.
Promote work, not titles
If someone is already greeting or writing a useful FAQ reply, give them a job (co-greeter this week, “will you seed Thursday’s question”) before you give them a badge. Early staff badges without a job create politics. You do not have enough people to afford politics.
On XenForo, a promotion to a Trusted group can wait until they have a task. On Discourse, do not gift TL3 as a thank-you; TL3 is a rolling window and a flag weight. Invite-only sites can start people at TL1; that is a documented default for invites, not a medal.
Close the loops you opened
If you asked for introductions, every introduction has a staff reply. If you asked for feedback on the map, you publish what you will and will not change. Unanswered official threads train the first ten people to ignore staff. They will teach the next fifty.
Look at founder metrics, not vanity
In a founding month the useful counts are small and honest:
- Invited vs registered vs first post
- First posts that got a reply from a human
- Second session in seven days (if you can see it)
- Topics with zero replies (your failure list)
- Staff posts vs member posts (if staff is 90% of volume in week three, you still have a blog)
Do not invent industry benchmarks. Do not celebrate 200 registered accounts with four first posts. The member-onboarding article already said registrations are not members. Founding adds: invites are not a community either.
Fix mail and watches before you fix the header
If first posts are fine and second sessions are not, the problem is the first screen and notifications. Point What’s New / Latest at living rooms. Explain watches once. Do not add a drip sequence. Do not add a points shop.
Days 22–30: decide if this is a community
By day 30 you know.
Stay open if at least some of the first ten came back without being poked, staff can still keep the 24-hour reply budget, and you can name next month’s ritual. Then hand new humans to the member 30-day plan — welcome, first-session map, second hook, day-30 review. That plan is their calendar. Yours becomes “keep the shift staffed.”
Stay small on purpose if three people are talking and they are getting value. A 30-person forum that answers is a community. Do not blow it up with an ad campaign to soothe your ego.
Close or archive if the only posts are staff talking to staff, the greeter quit, and you cannot name a replacement. An honest static archive plus a chat room is kinder than a year of “we should post more.” Closing is a founding decision too.
Do not use day 30 to add the 40 forums you deferred. If the map failed, flatten. If the map was fine and the room was silent, the map was not the problem.
A 30-day founding checklist
Paste this into the staff room. Tick it in ink.
Before public:
- One-sentence audience. If you cannot write it, you are not founding.
- Two humans on a duty roster, plus a private staff room.
- Admin handle reserved for official voice. Personal unbadged profiles for conversation.
- Rules on one screen. Long legal page linked, not pinned as the only thread.
- Five or six rooms. Prefixes/tags for real filters only. Throwaway can post in the obvious room.
- Mail works for a throwaway. Backup restore rehearsed.
- Seed: how-it-works, introduce yourself, weekly open question, one real topical question. No museum.
- First ten people invited on purpose. They have posted before the tweet.
Launch week:
- Published announcement with the audience sentence and the two start-here threads.
- Every new public topic answered by a named human within 24 hours.
- No new rooms. No theme rabbit hole. Daily throwaway test.
- Discord (if any) points at threads or stays out.
Weeks two–four:
- Weekly open question posted on schedule.
- Every introduction replied to. Feedback loops closed in public.
- Work offered before badges. No gifted high trust.
- Counts: first post, replied-to, second session, zero-reply topics. Not registration vanity.
- Day-30 call: stay open, stay small, or archive. Then start the member 30-day plan for the people who remain.
What founding will not do
It will not replace a product-fit decision. A tree-shaped game community launched on Discourse will still ask where the last-post column went; that is a destination problem. A support community launched without SMTP will still feel dead on Thursday; that is mail.
It will not replace money. If you need hosted Discourse or XenForo Cloud because nobody on staff can own a VPS, price it in the three-year TCO and buy it before day 0. A launch on a box nobody can restore is a timed deletion.
It will not replace the member plan. Once people join, their first 30 days are a different job: first session, second hook, promote or let go. Link them to that plan. Do not paste this founding checklist into a welcome PM.
Takeaways
- Founding is staff + map + seed + a shift. Publishing a URL is not a launch.
- Two humans with a duty roster beat one founder with a finished theme.
- The Admin account is for announcements. People talk on personal profiles. XenForo community practice is right about this on every platform.
- Seed conversations, not a rules museum. Five rooms. Ten invited humans before the internet.
- Launch week is a 24-hour reply budget. The quiet weeks are whether anyone comes back without being poked.
- Day 30 is a stay-open / stay-small / archive call. Then the member onboarding calendar takes over for the humans who stayed.
If you cannot name who is on duty tonight, you are not launching tomorrow. Write the roster first. The software will wait.