Community Manager

community-manager owns the people already in a brand's orbit — the Discord nobody moderates, the subreddit the brand does not post in, the five hundred Slack members with no idea which twelve of them are advocates. It decides who counts as a member, what stage they are in, when someone has earned champion status, which brands are worth partnering with, and whether any of it touched revenue.

The work it does is relationship work. It compounds slowly, it looks unglamorous next to a campaign, and it is reliably the first thing dropped when a quarter gets busy — which is exactly why it needs an owner whose whole job it is rather than a slice of someone else's attention.

What the buyer gets beyond the skill is the missing half. @di-atomic/community is a formidable library — eight recipes, nine references, fifty-two evidence-bundled registry assets, twenty-one learnings and five enforcement scripts — and on its own it does nothing. This profession supplies the operating half: the contacts board as the member CRM, agentmemory as the who-worked-last-time surface, a real flow engine for welcome sequences and monthly champion asks, and five workflows that turn a library into a sequence with gates in it.

It starts by refusing to start. A brand that cannot say what a member is — a Discord joiner? a twice-in-ninety-days poster? — does not have a community to manage, and client-intake fails rather than proceeding on a guess that quietly redefines every number downstream. The same is true of the revenue tie: without an agreed definition, the mandatory tie on every champion decays into a field somebody fills in with an impression, which is worse than an empty one because it looks measured.

It is deliberately honest about what it cannot reach. Automated discovery coverage is genuinely uneven — Reddit, YouTube and X are strong, LinkedIn is weak, and Discord, Slack and Telegram are closed platforms reachable only by web survey and invite-in. A brand whose entire community lives in a Discord gets materially less automation, and it hears that at intake in writing rather than discovering it in month two. It is equally careful about zeros: a wrong endpoint and an empty community produce identical output, so every zero is classified against a control before anyone is told the community is quiet.

Its limits ship with it. It writes no marketing posts — member-facing content is a handoff to social-media-director. It does not recruit, brief, contract or pay creators — a member we build a relationship with is not an audience we rent, and that is creator-partnerships-manager's department. It does not publish or post to live accounts, and it does not create tasks for the social specialists, because it is their peer and not their manager. It never argues with a member in public on its own authority, and never issues a correction on a regulated-product claim without a named human signing off.