Agency vs In House Community Management: Who Decides What at Each Size
The staffing question resolves itself once you assign five categories of decision. Three of them should stay internal at every size, and the rest change as the room grows.
The comparison that cannot be answered
Retainer against salary is the version of this question most teams start with, and it has no correct answer, because the two things being priced are not the same work.
Spend thirty minutes on a different exercise first. Write down five categories of decision and put a name beside each. Then look at the quotes again. The answer is usually already on the page.
The categories: identity and voice, safety and enforcement, escalation into the company, programming and calendar, and data and reporting.
Below one thousand
The community is still an extension of the founding team, and members can feel the difference between an answer from someone with authority and an answer from someone relaying one.
One internal person part time, plus outside expertise for the build itself. The external purchase is a one-off: structure, permissions, automation, entry flow. Everything a member reads as personality stays inside.
The characteristic mistake here is outsourcing voice early. A four hundred member community that starts sounding corporate has lost its only real advantage.
One thousand to ten thousand
The binding constraint becomes coverage. Questions land at hours your one person is asleep.
Buying hours externally is the right move, because distributed coverage is expensive and slow to hire internally. What you must not buy is judgement.
Two retentions make this safe. Voice stays inside, expressed practically as internal authorship of response templates plus a weekly sample review. Escalation stays inside, expressed as a written list of what gets handed over immediately, with no interpretation required.
The usual failure at this size is subtle. It is not a wrong answer, it is a right answer delivered with authority nobody granted, resolving something that should have reached product, legal or an account owner.
Ten thousand to one hundred thousand
Programming becomes a role. Events, launches, recognition, contests and weekly rituals require somebody planning their week around them.
The hybrid shape that works: an internal lead owning strategy, voice, escalation and cross-department relationships, with external capacity carrying moderation coverage, event operations and production volume.
The internal lead is structurally necessary now, because the community simultaneously touches support, product and marketing, and someone has to arbitrate. An outside party cannot arbitrate between your departments, no matter how capable, because they cannot call the meeting.
Above one hundred thousand
Volunteers arrive with or without a plan. Members answer each other, informal leaders emerge, and requests for roles follow.
Volunteer management moves internal, because it is fundamentally about trust, access and enforcement. Granting moderation permissions inside your own house, and revoking them, is a decision that belongs to someone employed by you.
External capacity still matters for coverage, specialist events and launch surges. The change is that your internal team now runs a system of people rather than a set of channels.
Permanently internal, at any size
- Who gets banned and on what grounds. This is a customer relationship decision with commercial and sometimes legal weight. External moderators should execute a written policy. Authoring that policy, and ruling on the cases it failed to anticipate, is yours.
- What members are told during an incident. Whatever gets posted becomes the company position within minutes, and it will be screenshotted.
- Who holds server ownership. Ownership sitting outside the company is an outage waiting for a disagreement or a missed renewal.
Three clauses that make a hybrid durable
A written escalation list, naming what must be handed over and within what window. A sampling clause, where an internal person reviews a fixed number of member interactions each week. A documentation clause, so operating knowledge lands in your systems rather than in one contractor's memory.
The third clause is the one that gets dropped and the one that determines whether you can ever change providers. Without it, switching cost grows monthly until the decision is effectively made for you.
A hybrid without a documentation clause is not a hybrid. It is a dependency with a nicer invoice.
Reading your own page
Once the five categories have names beside them, the staffing conversation changes shape. You are no longer comparing a retainer to a salary in the abstract. You are asking who can hold each named decision at your current size, and buying capacity for everything that is left.
Most teams discover they need less external volume than they assumed and more internal authority than they had.
The layers this does not settle
Decision rights sit alongside several other builds: the budget structure that funds whichever model you choose, the real coverage hours your membership needs rather than the ones you assumed, documentation that makes any handover survivable, and the reporting loop that tells the rest of the company what the community produced.
What this layer does is remove the false binary. Agency or in house was never the question. Who holds which decision, at this size, was.
Every staffing argument is a decision rights argument that nobody wrote down. Write it down. More at danieljeong.org.
Want a properly managed community?
Get Your Free Analysis →