Listen
NEW! Listen to article

Earlier in the Sales Enablement: Good or Bad series, I shared why I'm working to build a community. In this article, I'm going to share a bit more tactically about the how.

First Considerations: The Medium Shapes Your Community

There's an embarrassment of riches when looking to set up an online community these days. Christopher Penn gave a super helpful presentation on private social media communities at B2B Forum last fall. His No.1 suggestion was to pick the medium that makes sense for you and your community.

In many contexts, that is Slack or Discord.

For marketing communities, I've experienced Slack the most often, free and paid versions alike.

The No.1 drawback of a free Slack community? Messages disappear after 90 days like amateur Houdinis. All of them!

The No.1 drawback I've noticed in my limited Discord experience? Interactions devolve into not-great-behavior really quickly.

Other considerations emerge after you make your selection and you're find yourself in the never-ending story of settings. But up front, money is the big consideration. And that brings up another question: Is it sustainable?

Discord has an advantage: It's technically free. (There are also Nitro subscriptions, which are paid. Yes, it's confusing.) But you "pay" in the form of the time it takes to moderate and keep things civil.

Slack is familiar to many; but because it's been adopted by so many companies, it has enterprise-minded pricing for the paid version. If we were to establish even a small, active community of 200 members (including our 100 staff and 100 community folks), how much would that cost?

The lowest Pro paid level is $7.25 per user per month when billed annually and $8.25 per user per month when billed monthly. I have no way of knowing exactly how many people we'd have, and the community would scale over time. So $8.25 per user per month x 200 users would be $1,650 per month. Presumably before taxes. That's really expensive for a small-to-midsize B2B services company's marketing budget.

So, regardless of how those numbers change in the future, Discord and Slack are both resource-intensive.

I started to resign myself to our free version of Slack's turning into a "Sad Panda" community as the messages disappeared into the ether and people stopped participating completely. No joke, that happened to a really cool marketing community in 2022.

Then someone told me about Discourse.

When I started exploring Discourse, I discovered multiple benefits when viewed through the lens of a community focused on people working in and around software development:

  • It's open source.
  • It has both self-hosted and paid options.
  • It allows for scaling to higher levels over time.
  • It's relatively easy to shift from self-hosted to paid, and vice-versa

The best part? The paid version is only $100 a month. That I can live with. That is sustainable.

The Right Answer—For You

Sometimes the answer is to go with the obvious choice. But not an obvious choice for everyone, an obvious choice for you.

I was reminded of that while watching Nicolas Cage in Kick-Ass. I had a moment when I couldn't name which Batman Cage was emulating—because it was so good and so specific. It took me a hot minute, and then I remembered watching Adam West on reruns as a teenager.

Enter your email address to continue reading

Key Considerations When Building an Online Community

Don't worry...it's free!

Already a member? Sign in now.

Sign in with your preferred account, below.

Did you like this article?
Know someone who would enjoy it too? Share with your friends, free of charge, no sign up required! Simply share this link, and they will get instant access…
  • Copy Link

  • Email

  • Twitter

  • Facebook

  • Pinterest

  • Linkedin

  • AI


ABOUT THE AUTHOR

image of Cathy Colliver

Cathy Colliver is the marketing director at Test Double, a software consulting agency. She loves simplifying challenges, and her marketing career spans five industries. Cathy volunteers in arts and education.

LinkedIn: Cathy Colliver

Twitter: @CathyColliver

Threads: @cathycolliver 

Mastodon: @cathycolliver