The Community Manager Role in 2026: What It Actually Is
The operating system of every place a customer talks to another customer about the product. Member journeys, contribution surfaces, and the recognition programs champions defend in public.
By Bell Chen, founder. May 19, 2026.
In his 2019 book The Business of Community, CMX founder David Spinks wrote: "Community is not a marketing tactic. It is a long-term commitment to creating value for a group of people who share a common identity or interest, and the people who manage it are doing one of the hardest cross-functional jobs in modern software." Spinks, who later joined Bevy as VP of Community and ran the CMX Hub as the longest-running practitioner publication in the discipline, was describing a job that, in 2026, has finally settled into a title that boards and CEOs hire for on purpose. As a 2014-era title, community manager scoped down to the Slack moderation queue, the Discord welcome bot, and the swag closet. As a 2026 title, it scopes up to the operating system of every place a customer talks to another customer about the product.
The conflation problem in this role is that the title is being applied to four quite different jobs. The first is the community manager at a developer or technical SaaS company (the Salesforce Trailblazer shape that Erica Kuhl built), who owns a program with named tiers, named champions, and a measurable contribution to product adoption and retention. The second is the community manager at a consumer creator-economy company (Rosieland, Indie Hackers), who runs an open knowledge network and a paid private space simultaneously. The third is the community manager at a brand-led business, who runs community as a brand surface rather than a product surface. The fourth is the agency-side community-of-practice manager who runs a private network of operators or executives. The four jobs share a vocabulary and almost nothing else.
This page is for the operator who already runs a community of meaningful scale (more than 500 active members, a dedicated annual budget above $100K, a measurable product or brand metric the function is responsible for) or is being asked by a CEO or board to professionalize the function. It assumes basic literacy in online community design and skips the genre conventions of a beginner's guide. The point is to document the role as it is actually run.
What this role actually does in 2026
A 2026 community manager, in the senior version of the role, runs six interlocking functions. The conflation of these six (and the founder's tendency to delegate only the easy ones) is most of the reason the role looks chaotic from the outside.
Function one: a written community strategy the company will defend in public. In The Business of Community, Spinks defined the SPACES model (Support, Product, Acquisition, Contribution, Engagement, Success) as the framework most often used to anchor a community's reason for existing inside a company. Spinks wrote: "If you cannot answer in one sentence why your community exists for the company and why it exists for the member, you do not have a community. You have a chat room." The senior community manager's first 90 days produce a written one-pager the CEO, the head of product, and the head of customer success will defend on a board call without notes.
Function two: a member journey the team can run without the operator in the room. Erica Kuhl, who built the Salesforce Trailblazer community from 2008 to 2020 and now runs Erica Kuhl Consulting, said in one CMX Summit talk: "Members do not join your community. They join a stage of their own development, and your community is the place that stage happens." The framing comes back to a line in Get Together (Stripe Press, 2019) by Bailey Richardson and her co-authors: "Communities are not built from the inside out by a brand. They are built from the outside in by the people who already share something in common."
Function three: a contribution surface that serves the member, not the platform. Brian Oblinger, an independent community consultant whose work has been documented at CMX and Higher Logic over more than a decade, has argued in public posts that the contribution surface (the forum thread, the help post, the show-and-tell channel, the office hour) is the operational hub of a community function at scale. The bad version is a Discord with 12 channels nobody reads. The senior version is a surface where members produce questions, answers, tutorials, and showcases that marketing, support, and product teams use without breaking the brand.
Function four: a listening practice that runs continuously. Rosie Sherry, founder of Rosieland and former community lead at Indie Hackers, wrote in a 2024 Rosieland issue: "I do not start a community programme from an idea I had. I start it from a pattern I have heard three times this month from different members in different rooms." Patrick O'Keefe, who has hosted the Community Signal podcast since 2016, has said across more than 300 episodes that the leading indicator of a community's health is the operator's reading hours per week, not the posting hours.
Function five: a community-operations spine. The structural work (the welcome flow, the moderation playbook, the escalation tree, the recognition program, the events calendar, the analytics dashboard) is the unsexy half of the job. Bailey Richardson and her co-authors at People & Company have documented the operations spine in Get Together: "The work of a community is not the moments people remember. It is the operations behind them that nobody sees."
Function six: an honest read of what the model can and cannot do. The Buffer 2026 State of Social Media report, citing a survey of more than 2,000 marketers, found AI tool adoption in social and community workflows climbing from 64 percent in 2025 toward the high-70s in 2026. The senior community manager has a written policy on what the model can draft (welcome messages at scale, first-pass moderation triage, recap digests, event copy) and what it cannot draft (the contested member call, the named-champion shoutout, the apology after an incident). Spinks made the point in a 2024 CMX Hub essay: "An AI-written welcome message is the fastest way to teach a member that nobody is actually paying attention to them."
The named-operator playbook
David Spinks, CMX
Founder; former VP of Community at Bevy; author of The Business of Community (2019)
Spinks's point of view, made explicit in The Business of Community, is that community is a business function with measurable outcomes, not a marketing extra. He wrote: "A community can have rising engagement and falling health at the same time. The engagement is the symptom. The health is the patient."
Erica Kuhl, ex-Salesforce
Built the Trailblazer community 2008 to 2020; founder of Erica Kuhl Consulting
Kuhl's point of view, from her Trailblazer years, is that enterprise community is a product channel that drives certification, adoption, and retention. She said in a CMX Summit talk: "Your champions are not your workforce. They are your peers in the company you are building together. Treat them like a peer, or watch them leave for a community that does." More at her consultancy site.
Brian Oblinger, independent consultant
Enterprise community strategy; work documented at CMX and Higher Logic
Oblinger's point of view is that most community programs are over-platformed and under-programmed. He wrote in a 2023 CMX essay: "The platform is the easiest decision you will make. It is also the decision that fools you into thinking you have started." More at his site.
Rosie Sherry, Rosieland
Founder; former community lead at Indie Hackers
Sherry's point of view is that small intimate communities outperform large open ones on member transformation. She wrote in Rosieland: "When you outsource your community to a moderator who does not love the members, you outsource the only thing that was real."
Patrick O’Keefe, Community Signal
Podcast host since 2016; author of Managing Online Forums (2008)
O'Keefe has argued across his Community Signal episodes that the operators who compound are the ones who read more than they post. The visible community is the tip; the iceberg below it is the work.
Bailey Richardson, People & Company
Co-author of Get Together (Stripe Press, 2019); ex-Instagram early community team
Richardson and her co-authors wrote in Get Together: "When you start a community, you are not creating something out of nothing. You are gathering people who already belong together but did not have a place to meet."
A realistic week
Normalized to a single in-house community manager at a Series B-to-D company with one program ops associate, one part-time community engineer, and one editorial contractor, running a community of roughly 5,000 members with a tiered champion program. Monday is a community team standup (0.5h), member listening (1.5h: 30 threads read, 10 DMs replied, 5 quotes captured), and a moderation review (0.5h). Tuesday is member-journey work (1.5h: welcome flow, first-contribution prompt, recognition email tightened), a one-to-one with program ops (0.5h), and a cross-functional sync with product and support (1h).
Wednesday is a champion or power-user interview (1h), event production review (1h), and distribution planning (0.75h). Thursday is a stakeholder sync (1h), a program experimentation block (1.5h), and an adjacent community teardown (1h). Friday is the community digest publish (0.5h), an analytics and signal read (1h), and a monthly quarterly retrospective slot (0.5h). The total lands at roughly 14 to 15 hours of focused community work, plus the meeting load any senior in-house operator carries. The Thursday program experimentation block is the part most community managers cut first, and the Monday member listening block is the part most under-invested in.
What this role consistently gets wrong
Failure mode 1: confusing community with marketing.A community manager who reports to a CMO with funnel KPIs will optimize for the KPIs. Spinks wrote: "If you treat your community as a top-of-funnel acquisition channel, you will get a top-of-funnel acquisition channel, which is the worst version of a community and the worst version of an acquisition channel." Kuhl made the same point: "The community number that matters is not leads. It is the percentage of your most valuable customers who would be sad if the community disappeared."
Failure mode 2: platforming before programming.The bad version buys a Circle, a Discord, or a Slack and considers the strategy decided. Oblinger wrote in a 2023 CMX essay: "The platform is the easiest decision you will make. It is also the decision that fools you into thinking you have started." I have watched two software companies in 2025 spin up beautiful Circle communities that died inside six months because nobody ran the rituals.
Failure mode 3: outsourcing the load-bearing community work too early. Moderation and event ops are delegable. The judgment about who is welcomed, recognized, and asked back is not. Sherry wrote: "When you outsource your community to a moderator who does not love the members, you outsource the only thing that was real." I watched one DTC brand in 2025 lose two-thirds of its founding members in a quarter after handing the community to an external agency.
Failure mode 4: confusing engagement metrics with health metrics. The senior version reports on the percentage of members who would be sad if the community disappeared, the contribution rate of the top 5 percent, and the member retention curve. Spinks wrote: "A community can have rising engagement and falling health at the same time. The engagement is the symptom. The health is the patient."
Failure mode 5: treating champions as a free volunteer workforce. Kuhl said: "Your champions are not your workforce. They are your peers in the company you are building together. Treat them like a peer, or watch them leave for a community that does." A second-tier trap is the events-driven community: the event is the lagging indicator; the Tuesday-morning thread is the leading one.
Comp, market context, and what to track
- In-house community manager / head of community (Series B to D)
- $110K to $210K base plus equity and a 10 to 20 percent variable component
- Head of community (unicorn-stage or pre-IPO)
- $260K+ base plus meaningful equity
- Independent community consultant / studio
- $150K to seven-figure annual revenue at 70 to 85 percent margins
- BLS adjacent-category anchor (PR and fundraising managers)
- $134,760 median (May 2023), the conservative anchor at lower seniority bands
- Time to measurable lift
- 12 to 24 months from written strategy and journey deployment
Salary.com's published Community Manager band and Glassdoor's Head of Community salary data overlap with these bands and skew slightly lower outside the top metros. The BLS Public Relations and Fundraising Managers profile is the conservative anchor. The reward in 2026 is concentrating at managers who can ship a journey the member moves through, a contribution surface that gets read, and a recognition program the champions defend in public.
Where a planning-first tool fits
Most of the role runs in the community platform (Circle, Discord, Slack, Bevy, Salesforce Experience Cloud), a CRM or member database, a calendar tool, and an analytics stack for member health. The slots where a planning-first tool earns its place are the format-mining pass (which adjacent communities are running which rituals, on which surface, at which cadence) and the cross-surface performance pass (which of the program's last 90 days of rituals, threads, and events beat the median by 3x in contribution rate or member retention).
Both passes are manually expensive. The format-mining version eats four to six hours per month before it produces signal, and the cross-surface performance version takes a senior community manager roughly three hours per month to run rigorously. A planning-first tool that surfaces ritual and contribution archetypes can compress those steps to under an hour each. The tool I work on is one option among several; Common Room, Orbit, a hand-built scraper feeding a Notion board, and a working analyst with a spreadsheet all run the same step. The judgment about which member to welcome and which champion to back is not the tool's job. It is the operator's.
Frequently asked questions
Is a community manager the same as a social media manager?
No. A social media manager owns owned channels (Instagram, TikTok, LinkedIn, X) and the publishing-and-engagement workflow on platforms the company does not own. A community manager owns a space the company does own (a forum, a Slack, a members site, a recurring event series) and the member journey inside it. At smaller companies, one operator does both jobs.
What is the difference between a community manager and a developer relations lead?
A developer relations (DevRel) lead owns the technical content and the developer audience specifically (talks, sample code, SDK adoption, hackathons). A community manager owns the cross-audience program (customers, prospects, partners, champions) and the member journey across roles. At many smaller companies, one operator runs both functions.
Does a community manager need to be a heavy poster?
No. Several of the most successful community managers (Kuhl in her Trailblazer years, Oblinger in his consulting work, Richardson in her People & Company shape) are not the loudest voice in the room. The variable is whether the operator can hold the strategy, the journey, and the contribution surface in one head and defend them cross-functionally. The posting can be hired around or distributed across champions. The judgment cannot.
How long before a community function returns measurable lift?
The Trailblazer, Rosieland, and Indie Hackers timelines suggest 12 to 24 months from the first written strategy and journey deployment to a measurable inflection in member retention, contribution rate, and named-champion behavior. The strategy and journey land in months one through six, the program runs consistently in months six through 12, and the measurable lift becomes legible in months 12 to 24.
Should a community manager report to marketing, product, or customer success?
In 2026, most senior community managers report to customer success, product, or directly to the founder. Reporting to marketing turns the role into a top-of-funnel acquisition function, which is the worst version of community. The senior version lives close enough to the product and customer-success teams to influence the journey, with a direct line to the founder on contested member questions.
Is the community manager role at risk from AI?
Mixed. The structural overhead (welcome messages at scale, first-pass moderation triage, recap digests, event copy) is increasingly AI-tractable, and the managers above the noise floor have integrated the model without ceding the editorial role. The load-bearing thinking (the journey, the contested member call, the named-champion shoutout) is not AI-tractable in a way the members will read as real. Spinks wrote: "An AI-written welcome message is the fastest way to teach a member that nobody is actually paying attention to them."
What is the single biggest mistake a new community manager makes?
Picking the platform before writing the strategy. The supply of empty Slack workspaces and unused Discord servers in 2026 is enormous, and the supply of community programs that produce real member transformation is small. New community managers who spend the first 90 days configuring a platform produce six months of feature-rich emptiness. Spend the first 90 days writing the strategy, the journey, and the program. Then pick the platform.
Disclosure: Superdirector, the brand I work on, is one option in the ritual-mining and cross-surface analytics category alongside Common Room, Orbit, and Notion-based hand-built workflows. The comparison is not the point of this page; the role is.