I'm Cands. I write this newsletter every two weeks for people whose work touches community in some way:
founders building something they want their audience to talk back to,
marketers who got handed "community" and aren't sure what to do with it,
operators trying to make engagement compound instead of expire,
and consultants figuring out how to charge for the work.
Last month a prospective client asked me the question I get most often. Is community a product, or is it marketing?
My answer was, and is, neither.
RESOURCES I’D RECOMMEND THIS WEEK:
📌 The Styled Pin Collection by Dana Bahr: One pin can quietly bring you engaged traffic for months. Most people use Pinterest wrong and wonder why. Dana's monthly drop fixes both, check it out.
📊 State of Community Management 2026 by The Community Roundtable: Community is now more strategic to the business than ever, and still the most under-resourced function in the org. Five more findings that should be on your desk before your next budget conversation.
🛍️ State of Loyalty and Retention 2026 by Attentive: Six hundred shoppers were asked what actually brings them back. Most of the answers have nothing to do with discount codes. Worth reading before you defend next year's retention budget.
Community is people. A user base. A group of humans interacting with your business in multiple ways, across the entire marketing flywheel. The operations that hold that network together can sit in marketing ops, product ops, or both, depending on where in your business community is serving and being served. The category isn't fixed because it follows the function.
Thinking community is just vibes is a mistake. Thinking it's just operations is the same mistake from the other direction. Both stop you doing the work that matters, which is building engagements and activations that the people in front of you actually want, interact with, and remember.
Community forms. It isn't built.
Community forms when you create a platform where you aren't just talking at your audience, and they're talking back. The dialogue is the substrate. Everything else, the rhythm, the events, the threads, is the shape the dialogue takes.
This is why community siloed inside one department is such a problem. The dialogue happens across the business. When sales takes a call. When product ships a release. When marketing sends a newsletter. When ops handles a complaint. If only one team can hear the response, the rest of the business is operating blind to its own user base.
Four questions to ask yourself
Before deciding where community sits in your org chart:
What problem is this activation solving for the community and the business?
Where is the community serving the business?
Where is the business serving the community?
What integrated systems make those operations possible?
If one of those is blank, that's where the real work is.
A story I have permission to tell
An enterprise client had this problem at scale. Product ran a beta circle. Marketing ran a content program. Sales ran a regional series. Ops ran a help forum. None of it connected. None of it tracked. Nobody could answer "is community working" because nobody could see all of community at once.
We stopped. We introduced one shared mechanism: a registration system every team had to feed, integrated with the CRM. No new platform, no campaign, no rebrand. Just one shared spine.
Within a quarter, the sales team could see, for the first time, how engaged the customer base actually was. That visibility changed which accounts got prioritised, how the product roadmap got argued, and what marketing was allowed to count as a result.
The community didn't get built. It got seen.
What to do on Monday
Open a doc. List every place in your business where someone is currently running an activation that touches your audience. Every webinar, every Discord channel, every roundtable, every account-management touchpoint.
Then pick one shared mechanism that every one of those has to feed. A registration form, a CRM tag, a shared inbox. Anything that captures who showed up and what they said back.
That single capture point is the start of community as a business function instead of a department. The spine has to come first.
One thing before you go
This newsletter is for people whose work touches community. I'd rather write for the segment you're actually in than guess. The poll below is one click.
Which of these best describes you?
FROM MY FRIENDS AT WISPRFLOW:
Speak the email. Send the email.
Talk through your reply and get polished, professional text ready to paste. Wispr Flow strips filler, fixes grammar, and formats everything. 89% sent with zero edits. Works everywhere.
