Your packages: setup, management, strategy

Package community work in three shapes, because owners buy them in that order. The setup project — platform structure, spaces or channels, onboarding sequence, rules, and an initial moderation framework — runs $800–2,500 depending on size. It's a fixed scope with a fixed end, which makes it an easy first yes. The management retainer is the ongoing work: running the weekly rhythm, engagement, events, and reporting. Ongoing engagement management scopes run $1,500–5,000 a month; pure moderator retainers for timezone coverage sit lower, commonly $800–2,500 a month. The strategy sprint — a retention overhaul, a relaunch, a campaign and events season — is project work at $3,000–10,000 for owners who keep their own day-to-day hand.

Sanity-check any package against the hourly market before you quote it: US community-management freelancers typically bill $30–59 an hour, Circle-focused managers $24–60, and mid-level day rates land at $360–490. If your retainer quietly prices you at $14 an hour once the "quick calls" and event nights pile in, the package is wrong — narrow the scope or raise the price. A 2–4 week project at day rates lands around $3,600–9,800, which is a useful anchor when an owner wants "a few weeks of help" without a scope.

Write each package with its edges showing: hours or coverage windows, what counts as an event, how many live sessions a month, response-time expectations, and what happens when the community grows past the member count you priced for. Growth is the happy version of scope creep, and it still needs a price.

The audit pitch: one real leak, named kindly

The pitch that works for community work is not "I manage communities." It's a specific leak in their community, named with kindness and a visible fix. Which means the outreach starts with homework: join the free tier, sit in the Discord, take the trial. Find the thing an owner can't see from inside — the new-member posts nobody answers, the wins channel silent since March, the onboarding that ends at a welcome emoji. Then say it plainly, without gloating, and offer the audit as the next step.

Example DM (to a business coach running a Skool group): "Hi Dana — I joined your free group last week to study how you run it (the Tuesday teardown thread is genuinely good). One thing I noticed: new members post introductions and most sit unanswered for a day or more, and that's usually where paid groups quietly bleed people later. I manage paid communities for coaches, and the fix is small — a day-one intro prompt plus a reply rota for the first week. Happy to send you a one-page note on what I found in yours, no charge. If it's useful, I also do full community audits that map the whole member journey."

Example email (to a course creator with a Circle community): Subject: "Your members' first week in Foundations Circle." Body: "Hi Priya — I took the trial week of Foundations and went through your onboarding as a new member. The course content is strong, but here's what a new member experiences: a welcome post, then silence. No intro prompt, no first small win, nobody's name used until the live call on day six. For a $49/mo membership, that first week is where churn is decided — at 8% monthly churn, a 500-member community loses 40 people and about $1,960 every month. I run community audits for course businesses: I map the full member journey, flag the leaks in order of cost, and give you the fix list. It's a fixed-fee engagement and you'd have the report in a week. Worth a look? — [Your name]"

Notice what both do: one leak, real numbers, zero insult, and a small paid next step instead of a vague offer to "help with community stuff." Send fewer of these than you think — five well-researched pitches a week beat fifty copies of a template, because the leak has to be real.

The two-week trial: a paid engagement sprint

Owners hesitate to sign a retainer with someone unproven, and you should hesitate to offer free work to find out. The bridge is the two-week trial: a paid, fixed-scope engagement sprint with a hard end date and a report at the end. Price it like the real work it is — at your day rate, a focused sprint across two weeks typically means several working days, and mid-level day rates run $360–490. "Free trial month" is not a smaller version of this; it's a different and worse deal.

Scope the sprint tightly enough to win visibly. The classic shape: week one, you run the audit and take over the daily rhythm — prompts posted, first posts answered within the day, one wins thread launched. Week two, you ship the single biggest fix the audit found (usually the onboarding sequence) and run one live touchpoint — an office-hours session or a member AMA. Throughout, you're baselining as you go: active members, posts per active member, unanswered threads, so the end report can show movement instead of impressions of movement.

The report is the sales document. Two pages: what the numbers were when you arrived, what you did, what moved, what you'd do next month and what it costs as a retainer. Deliver it on a short call, not by email, and ask the plain question: "Want me to keep running it?" By then the owner has watched you work for two weeks, the members have seen the group come alive, and the retainer is a continuation, not a leap of faith. If they pass, you still got paid, and you have an anonymized case for the portfolio.

Onboarding a community: keys, briefing, handoff

Starting inside someone else's community is a trust exercise, and the first week sets the terms. Begin with access levels: get moderator or admin rights through the platform's own role system — a Circle admin seat, a Discord role with named permissions — never the owner's personal login. Write down exactly what your role can do (post, pin, remove, ban) and agree on which actions you take solo and which need the owner's word first. Removal of a paying member almost always belongs in the second column.

Next, the owner briefing, a 45-minute call you run with a list: Who are the superusers, by name? Who are the known difficult members, and what's their history? Which topics are third rails — refunds, politics, a rival's program? What's the escalation path at 9 p.m. on a Sunday, and what's the owner's real response-time expectation for you? Get the answers in a shared doc. Owners assume you know their community's unwritten rules; the briefing is where those rules get written.

Finally, the mod-team handoff. If moderators already exist, meet them before you change anything, learn what they've been doing, and introduce yourself to the community in a pinned post the owner blesses: who you are, what you'll be running, where to reach you. Your first visible acts should be small and additive — answering the unanswered, starting the wins thread — not a redesign. Communities punish strangers who redecorate on day one and reward the ones who show up reliably for a month.