Every founder I talk to has an opinion about community marketing before we've even started, usually formed from watching one Web3 project's Discord blow up or one SaaS company's user conference go viral on LinkedIn. Neither of those is what the day-to-day work looks like. Here's where the gap usually is.
What people think it is: a channel
Most founders slot "community" into the same mental bucket as paid social or email: another channel to staff, another line item to report on. Set it up, post consistently, watch the follower count climb.
What it actually is: infrastructure that touches product, support, and marketing at once
A community that's actually working doesn't sit in a silo. The best feature requests I've routed back to product teams came from community conversations, not support tickets, because members will say things to each other in a community space that they'd never bother writing into a formal feedback form. When Redbelly Network's community flagged friction points, that fed directly into how the team prioritized documentation and product messaging, not just what got posted in the announcements channel.
Treat community as a marketing-only function and you'll staff it like one: someone posts updates, replies to comments, and reports a follower count. Treat it as connective tissue between your users and every other team, and it starts generating the kind of insight paid channels can't.
What people think it is: bigger is better
Member count is the easiest number to put on a slide, so it's the one most people optimize for. A community can hit 10,000 members and still fail on every metric a business actually cares about, if 9,900 of those members joined for a giveaway and never opened the space again.
What it actually is: a retention and referral engine, measured differently
The number that matters isn't total members. It's how many people are still active at 90 days, how many of your best customers came through a referral that started in the community, and how often community conversations surface a problem before it becomes a support escalation. Fifty people who show up every week and refer their peers outperform five thousand who joined once and never came back, on every metric that shows up in a board deck six months later.
What people think it is: a launch tactic
"Let's build a community for the launch" is one of the most common requests I get, and it's almost always the wrong framing. Communities built to hit a launch date are usually abandoned within a month of it, because the team's attention (and budget) moves to the next milestone the second the launch numbers are in.
What it actually is: a long-term system that needs a long-term owner
The communities that last have someone whose job doesn't disappear after launch week: someone accountable for onboarding new members, keeping the feedback loop closing, and adjusting the content cadence as the community's needs change. If nobody owns it past the launch, it dies quietly, and the team usually blames "community marketing" for not working rather than the fact that nobody kept running it.
What people think it is: free
Because there's no ad spend, community marketing gets treated as the budget-friendly option compared to paid acquisition.
What it actually is: a real time and headcount investment, with a different payoff curve
The spend shows up as hours, not ad dollars: someone moderating conversations, someone designing onboarding, someone synthesizing feedback for product. It's not free, it's differently expensive, and it pays off on a longer timeline than a paid campaign does. Founders who go in expecting "free growth" usually pull the plug before the payoff curve bends upward.
If you're trying to figure out which of these gaps your own team is walking into, that's usually the first thing worth talking through before building anything. Book a 15-minute call and I'll tell you honestly whether community is the right move at your stage.
