There's no single-correct way to build a community.
We'll leave the thought leaders to debate strategies on LinkedIn while we get actual work done making sure your users have everything they need to start interacting around your product.
Because if you're in the early stage, that's the best thing you can possibly be doing right now.
Here's the approach we recommend when exploring - it's not rocket science. We're here to help you when you have questions:
Look at your ability to be a curator of this community. You're creating something with the express intent of having people depend on and appreciate it, so it's very important that you're sure you'll be in this for the long-haul. Some communities spring up overnight and some take significantly longer to reach the point where it starts to thrive. And, communities thrive in different ways. We direct early clients to Orbit for ground-zero of getting insights into what's going on.
Look at the product. Is it language-agnostic, or will, say, Python people generally be the only ones wanting to talk to eachother about how they use it? That matters a lot because people already having a shared culture lubricating the social interactions is going to probably jumpstart things, and they quite often decide that they want none of what you've set up for them to interact and would rather you meet them where they hang out. Don't go spinning up a forum when what they really want is a Discord server.
- Monitor the value people get from it, including you! Make sure you don't see tumbleweed rolling by, or a bunch of junk, and make sure people find new content every time they visit.
It's not very much more complicated than that. Sometimes you want to set up things so that when lots of people come rushing in, there's fixtures for folks to cling to, and the hope is we see a bunch of barnicles when the tide pulls out. Other times it's about setting up a much more deliberate path with clear motivators as people trickle in from organic search & social. There's no "best" - you need to develop a sense for what to expect and make sure you have what experience has taught you in place for when people arrive.
There's also outreach to consider when thinking of communities.
If your hot new vulnerability scanner runs particularly well on certain open source automation platforms, well, users of those platforms need to know! Outreach means understanding boundaries and customs and perceptions and optimizing for everyone else's time - which is certainly not anything resembling just posting link spam like so many companies do.
We want you to be in charge of your messaging, and this includes guiding how those that want to evangelize your products pitch it to folks so that they have maximum success. This also means not making an entire subreddit angry, and navigating lots of discord servers can really eat up time - why not leave it to us?
We build a community strategy unique for your product and resources available to you.
The best way to bring people together repeatedly and frequently for a common goal is to host small things that benefit them in some way in a manner that's convenient for them to access, and make sure the space where they'll interact is safe, professional and welcoming. The conversations will happen, once the right ingredients come together. The trick is to make sure these interactions are facilitated often, and pretty soon, they won't stop coming.
We don't really sell a turn-key solution, because we don't think one would be very responsible. Let us learn a little about you, what value you want to deliver to a community, and what value you see in doing that, and we can work on a strategy for you.
We can get started as soon as you click the button down there: 👇👇
There's still room in our private beta!
Ready to sign up? We're still working our magic on the back-end, but you can let us know you're interested in joining our private beta through the link below! Alternatively, we're happy to talk about what a trial or proof of concept together might look like, with no obligation or pesky sales follow-up.