Module 8: Portfolio and Proof
Community work is invisible when it goes well — nothing caught fire, nobody quit, the month just felt alive. That makes proof harder to show than in almost any other marketing job, and more valuable when you have it. This module builds the three assets that get community managers hired: an audit that diagnoses a real community, a spec launch plan that shows your thinking, and case framing that turns quiet months into numbers an owner can read.
The community audit as proof
The strongest portfolio piece a community manager can own is an audit: a short, structured report on a real community that names what's leaking and what you'd fix first. Pick a community you can actually join — a free Discord server, a public Skool group, a trial week in a paid Circle community in your niche. Spend a few days inside as a member before you write a word. Take the journey a new member takes and write down every point where you got confused, bored, or ignored.
Map five things. Entry: what happens in the first hour after joining — a welcome, a prompt, silence? Structure: do the spaces or channels tell a new member where to go, or is it a wall of rooms? Rhythm: when did the host last post, and is there any weekly pattern? Connection: do members talk to each other, or only to the owner? Leaks: where do people quietly stop showing up — after onboarding, after week two, after the first billing cycle?
Then write it up in three pages or less: what you found, the three leaks that matter most, and the first fix you'd ship for each. Anonymize everything — rename the community, strip member usernames, blur nothing because you took no screenshots of private conversations. An audit like this is exactly the document setup clients pay $800–2,500 to receive, which is why a sharp spec version of one opens doors. It's proof you can see a community the way an owner can't.
You're auditing a paid fitness community. The owner mentions proudly that the welcome post gets updated every month. You join and find: no intro prompt, the last host post in the main space is nine days old, and new members' first messages sit unanswered. What do you lead the audit with?
A spec launch plan for an invented membership
An audit shows you can diagnose. A launch plan shows you can build. Invent a membership that doesn't exist — say, a $49/mo Circle community for freelance bookkeepers, or a Skool group for new dog trainers — and write the plan you'd hand an owner on day one. Label it clearly as a spec plan, your own concept work. Nobody is fooled, and nobody needs to be: hiring managers and clients are judging the thinking, and the thinking is real.
Cover four things. Structure: the spaces or channels, each with a one-line job — a wins space, a questions space, a resource library, an off-topic room — and just as important, what you deliberately left out and why. Onboarding: the first seven days, day by day, ending in a first win a new member can reach on day one. Rhythm: the weekly calendar — Monday prompt, Wednesday live session, Friday wins thread — sized so one person can actually run it. The first 30 days: founding-member handling, the first challenge or event, and the two numbers you'll watch to know if it's working.
Ground it in the math from Module 7. If your invented community targets 200 members at $49, say what 8% churn does to it — 16 members and $784 a month walking out — and which parts of your plan exist specifically to push that number down. A plan that knows its own churn math reads like it was written by someone who has been trusted with revenue before.
Your turn: Draft your spec case study. Invent a membership (niche, platform, price) and write it in case format: the starting point (a new community, zero members, an owner with an audience), the moves (your structure, onboarding sequence, and weekly rhythm), and the results you'd measure — the two or three numbers, like monthly churn and posts per active member, that would prove the plan worked. Keep it labeled as a spec plan; the honesty is part of the proof.
Saved.
A prospective client reads your spec launch plan and asks, "So did this community actually launch? What were the real results?" What's the right answer?
Case framing: baseline, moves, movement
Once you've done real work — a trial, a freelance engagement, even turning around a small free community you moderate — frame it the way owners read. Three parts, always in this order. Baseline: where things stood when you arrived, in numbers. Monthly churn, active members as a share of the total, posts per active member, unanswered first posts. Moves: the specific things you changed, in plain words — rebuilt the onboarding sequence, added a Friday wins thread, started a buddy pairing in week one. Movement: the same numbers, re-measured after a stated window.
The discipline is in what you leave out. No adjectives doing the work of data: "engagement soared" is not a result, "posts per active member went from 1.2 to 2.6 over eight weeks" is. Always name the timeframe — a churn drop measured over one quiet month proves less than one held across a quarter. And report honestly around seasonality and launches: if a big course launch flooded the community during your window, say so. Owners have been burned by cherry-picked screenshots; a case study that volunteers its own caveats reads as the most trustworthy document in the pile.
Keep each case to one page and keep a running file from day one of every engagement. The time to record a baseline is before you change anything — week-three-you cannot reconstruct the churn rate week-one-you inherited. Even two honest cases, plus your audit and spec plan, put you ahead of most applicants, because most community portfolios are a list of servers they were once in.
Which line belongs in a case study?
What you can now do
- Audit a real community from the member's seat — join it, take the new-member journey yourself, then name what's leaking and what you'd fix first.
- Write a spec launch plan for an invented membership, clearly labeled as your own concept work, that shows how you'd build from day one.
- Frame finished work as baseline, moves, movement — the starting numbers, the specific changes you made, and what actually shifted.