Module 3: Platform Craft
Paid communities mostly live in three places: Circle, Skool, and Discord. Each shapes member behavior differently, and each has setup choices that quietly decide whether your foundations from Module 2 hold up. This module teaches the structure of each — and how to choose between them without selling anyone a migration they don't need.
Circle and Skool: structure that guides behavior
Circle is the full-featured option most course and coaching businesses land on: communities are organized into spaces (a feed, a chat, a course, an event list), spaces are grouped under headers, and courses, live events, and member directories live in the same product. Skool is the deliberately simple rival: one community feed, a classroom tab for courses, a calendar, and a points-and-levels game where posting and receiving likes moves members up levels that can unlock courses. Less to configure, less to break.
On both, the same structural rules apply. Keep the space list short enough to read without scrolling — a new member facing fourteen spaces freezes; four to six clear ones ("Start Here," "Wins," "Questions," "Live Sessions," the course itself) get used. Name spaces by what members do there, not by internal categories. Put the start-here space first and make it impossible to miss: it holds the welcome, the rules, and the first step from Module 2's journey. Archive dead spaces without sentimentality; an empty room teaches new members the place is empty.
Use each platform's native engagement mechanics instead of bolting on your own. On Skool, the level system is the retention game — talk about it, celebrate level-ups, and let unlockable courses reward participation. On Circle, events with RSVPs and reminders do that work; a well-run events tab is a rhythm machine. The craft is the same either way: fewer, clearer rooms, and every structural choice pointing a member at their next action.
A coach shows you her new Circle community: 16 spaces, including three for courses she hasn't recorded yet and two topic rooms with zero posts. New members keep asking where to introduce themselves. What's the fix?
Discord: channels, roles, permissions, and bots
Discord is where gaming communities live and where plenty of creator communities end up too. Its power is granularity: channels for every topic, roles that control who sees and does what, and permissions down to the single channel. Its danger is the same granularity. A server with forty channels and roles nobody understands is a moderation incident waiting for its moment.
Set it up in this order. Roles first: a small ladder — owner/admin, moderator, member, and maybe a paid-tier role that unlocks member-only channels. Give each role only the permissions it needs; the classic beginner error is handing a friendly helper a role that can delete channels. Channels second: a welcome/read-first channel new members can't skip past, a handful of discussion channels, one support or questions channel, and voice channels if live sessions run there. Lock posting in announcement channels to staff, so the important stuff never gets buried.
Then the moderation bots, which are standard, named tools of the trade: MEE6 and Carl-bot are the two you'll meet most. Use them for the mechanical layer — auto-assigning the member role on join, greeting new members, flagging spam links, logging deletions, slow mode on heated channels. Configure them conservatively: a bot that auto-deletes borderline posts or publicly shames members for a first link will start a fight you then have to moderate. Bots handle volume; humans handle judgment. Anything involving a person's standing in the community stays with you, every time, no exceptions.
You're setting up a Discord server for a paid fitness community. A trusted longtime member volunteers to help greet newcomers. Which setup is sane?
Choosing honestly: meet members where they are
Sooner or later a client asks the platform question, and the honest answer starts with the members, not the feature list. Where do these people already spend time? A coaching audience that lives on Facebook and email will struggle with Discord no matter how well you build it. Gamers will laugh at a members-only web forum. Business owners paying $99 a month often like Circle's calm, course-attached feel; a younger creator audience may find Skool's game mechanics and single feed more natural. Fit beats features, every time.
Then price the other direction honestly: migration is a tax. Moving a community means some members won't make the trip, habits reset to zero, links and bookmarks die, and the new room starts eerily quiet — which itself triggers cancellations. Communities do migrate successfully, usually for a real reason: outgrowing a free tool, needing courses and community in one place, escaping a platform the audience hates. "The new one has nicer events" is not a real reason. If you recommend a move, say the cost out loud and plan the bridge: announcement runway, founding-member framing, the start-here flow rebuilt before anyone arrives.
Your credibility as a manager depends on this honesty. Owners get pitched platform moves by everyone; the manager who says "stay put, fix the rhythm, here's the two-week plan" stands out — and is usually right. Choose the platform once, for the members in front of you, then spend your energy on the work that actually retains people: onboarding, rhythm, and care, starting in the next module.
A client with a thriving 300-member Discord community for indie game developers wants to move everyone to Circle "because it looks more professional." What's the honest counsel?
What you can now do
- Structure a Circle or Skool community — spaces, headers, classroom, calendar — so the layout itself guides how members behave.
- Set up a Discord server with channels, roles, and permissions a newcomer can actually understand, instead of forty channels waiting for an incident.
- Answer the platform question honestly, starting from where these members already spend their time, not from a feature comparison.