Working with a Head of Community

What this role actually does

The Head of Community owns the branded community as a growth surface, a retention surface, and a research surface. The seat is common in developer tools, in SaaS platforms with heavy peer learning components, and in creator economy businesses. It reports to the CMO, the CCO, or the head of product depending on whether community is treated as marketing, content, or product. The seat is measured on active members, engagement quality, and the influence community has on adoption, retention, and pipeline.

A working Head of Community spends real hours with product on user feedback themes surfaced in community, real hours with customer success on peer to peer support that reduces ticket volume, real hours with content on programming and editorial, and real hours with the CFO on the ROI story for a program that carries fixed moderation cost. The seat carries a community manager or two, a moderation lead, a programs manager who runs events and challenges, and often a data analyst for engagement measurement. Team size ranges from two in a mid market org to ten in a mature developer community.

The Head owns platform selection, moderation standards, programming, member growth motions, and the measurement framework. They also own the relationship with the top members, meaning the fifty to two hundred power users whose participation carries the community.

What a functioning Head of Community does not do: moderate every thread personally, run every event, or draft every announcement. They do not own the product roadmap and they do not own the marketing budget outside their programs. They own the operating system of the community. A Head who is answering forum posts at ten at night has a moderation problem below them.

The Head also owns the discipline that keeps the community from becoming a support queue. Members want support answers. Marketing wants brand engagement. Product wants feedback. When each stakeholder pulls the community in a different direction, the members lose the sense of purpose. The Head who does not maintain a written community charter and enforce it every month loses the members to the loudest internal team.

How to brief them well

You brief a Head of Community on the outcome the community produces and the constraint on how it grows. Here is the business outcome. Here is the audience. Here is the platform preference. Here is the constraint on moderation cost and headcount. The Head comes back inside four weeks with a community plan, a programming calendar, and a measurement framework.

Bad briefs look like a platform request. Please launch a Slack community. Please build a Circle community. Please create a Discord. Every platform choice without a strategy produces a community nobody uses. The Head who executes a platform brief either builds the wrong thing well or spends the year explaining why engagement is flat.

Context the Head needs on arrival includes the current member base, the actual engagement distribution, the state of moderation, the platform contract terms, and the political relationship with product, marketing, and support. A Head who does not know which department owns the community line item is going to lose the budget in the first reorg.

The strongest brief pairs an outcome with a hard no. Grow monthly active members to five thousand focused on the mid market operations audience. Do not open the community to prospects who have not signed up for a trial. Do not accept ad spend inside the community. Named nos protect the community from every marketing team that wants to broadcast into it.

The strong brief also names the platform migration the Head will refuse to accept. Every leader who joins the company will propose a new community platform. The Head who does not defend the platform decision spends every year building the same community again on a different stack.

Review cadence + operating rhythm

Weekly rhythm

Weekly at the Head of Community level is a health review and a moderation check. A Monday of about an hour covering active member trends, moderation queue depth, and any incident that needs an escalation. A Wednesday sync with product on feedback themes surfaced in the community. A Friday one on one with the CMO or CCO. Numbers reviewed weekly are daily active members, thread volume, and moderation SLA.

Monthly and quarterly reviews

Monthly is the operating review. Monthly active members, engagement distribution across the base, thread quality, top member roster health, and the ROI story tied to support ticket deflection or pipeline sourced from community members. The Head walks in with proposed programming and defends the moderation staffing.

Quarterly is where the honest conversation happens. The Head presents community health, member growth quality, business outcome attribution, and the plan for the next quarter. This is where programs get retired, platform decisions get revisited, and moderation policy gets updated. If the community is not producing at least one measurable business outcome each quarter, the Head has a problem.

Annual planning

Annual planning at the Head level is a member growth plan, a programming calendar, and a moderation staffing model. A Head who arrives at January without a written attribution model for community is going to lose the budget the first time the CFO does a full stack review.

Between the standing cadences the Head also runs a monthly top member outreach where the leaders on the community are personally thanked, briefed on upcoming programs, and asked for feedback on how the space is running. Top member trust is the moat. The Head who does not maintain the outreach cadence loses the top members without noticing.

Measurement (real KPIs, not vanity)

Four numbers matter at the Head of Community level.

First, engaged monthly active members. Not registered members. Members who posted, replied, or participated in a program in the last thirty days. The engagement distribution is the honest number. A community with ten thousand registered members and one hundred active is a ghost town.

Second, business outcome attribution. Support tickets deflected because peer answers arrived first, pipeline sourced from community members who converted to trial, or product feedback that shipped as a feature. A Head who cannot attribute the community to at least one of these lines is running a hobby.

Third, retention or churn signal by community engagement. Customers who participate in community churn at a lower rate than those who do not. Measuring the differential gives the Head a defensible case for expanding the program.

Fourth, top member health. The top fifty to two hundred power users carry the community. When top member activity declines, the community declines three months later. The Head watches this as a leading indicator.

Vanity metrics that mislead include registered member count, sign up rate, and gross post count. A community with sign ups and no engagement is a marketing liability. A Head who reports registered members without engagement distribution is padding.

The diagnostic layer under monthly active members is the ratio of contributors to lurkers. A healthy community has five to ten percent contributing regularly. When the ratio drops, either the top members have quieted or the moderation posture has scared new voices off. The Head who does not track the ratio is going to be surprised by a member exodus.

Compensation + career path (honest ranges)

Head of Community comp splits into three market bands.

Compensation bands by market

Mid market. Series B to C, ten to fifty million ARR. Base 140 to 190 thousand. Bonus 10 to 20 percent. Equity 0.05 to 0.18 percent. Total cash 160 to 230 thousand. Team size two to four. Often the seat carries developer relations double duty in a developer tools company.

Tech metro. Series C onward, fifty to two hundred million ARR. Base 185 to 255 thousand. Bonus 15 to 25 percent. Equity 0.04 to 0.14 percent. Total cash 215 to 320 thousand. Team size three to seven.

Coastal enterprise. Public or late private, or a mature developer platform. Base 235 to 315 thousand. Bonus 20 to 30 percent. Equity or RSUs 150 thousand to 500 thousand a year. Total comp 425 thousand to 900 thousand. Team size six to twelve.

The typical next step is VP of Marketing at a community led company, head of developer relations at a platform business, or founder of a community focused startup. Some Heads move into product management when the community is the primary source of user research.

Common departures. The two year exit when the community fails to produce a business outcome. The eighteen month exit when the platform choice ages badly and the migration cost is too high. The clean four year run when the Head builds a durable engaged community. A healthy tenure is three to five years.

The negotiation moment for a Head of Community is the reporting line and the platform budget. Reporting into marketing ties the community to acquisition. Reporting into product ties it to feedback and retention. Reporting into CS ties it to support deflection. The offer that leaves the line ambiguous produces a Head who cannot defend the community's purpose to any of the three.

Common ways this seat fails

The Head who confuses sign ups with community. The team runs sign up campaigns. The registered member count grows. Engagement stays flat. Nobody posts. The Head who does not report engagement distribution alongside sign ups loses credibility in the first quarter the CFO reviews the metric.

The Head who cannot manage moderation. A toxic thread lands. The moderation SLA slips. Top members leave. The community loses trust. A Head who does not run a moderation coverage plan with clear SLA and escalation paths is one bad thread away from a mass exit.

The Head who cannot align with product. The community surfaces feature requests. Product ignores them. Members feel unheard and stop posting. The Head who does not build a written feedback loop with product loses the community's engagement inside six months.

The Head who over programs. Every week has a new event, a new challenge, a new AMA. Members burn out. Engagement peaks and collapses. The Head who does not audit programming yield loses the top members inside a year.

The Head who cannot say no to marketing. Every marketing team wants to broadcast into the community. Product wants to run polls. Sales wants to prospect members. The Head who cannot filter for the community loses the community itself.

The seat also fails when the Head cannot resist over programming. Weekly AMAs, monthly challenges, quarterly summits, and daily prompts add up to a community that feels manufactured. Members disengage. A Head who does not audit programming volume against member sentiment ships work that hurts the very outcome the programming was supposed to produce.