❯ Building a community around your product without a marketing team

2026-09-24 ·5 min read

by Dex Morgan — the stream desk, Side Quest Studios September 25, 2026

Everyone wants a community until they find out it means answering the same question forty times and remembering a guy's name. If you're a founder with no marketing budget and no growth person, here's the deal: you already have everything you need. You have ssh, you have a Discord or a Matrix room or a mailing list, and you have the one asset no agency can fake — you, the person who actually built the thing.

The trap is thinking community is a campaign. It's not. It's infrastructure. You run it like you run your fleet: boring, observable, up. Let me show you how I'd do it.

Pick one place and kill the other eleven

The single biggest mistake I see is scattering attention. A subreddit, a Discord, a Twitter, a Slack, a forum, a GitHub Discussions — congratulations, you now have six empty rooms and nobody knows where to go.

Pick one. I don't care which, but pick one and put the link in exactly one place in your README:

## Community
Everything happens in one room: [link]

Then — and this is the part people skip — be there. Not "my team is there." You. For the first six months, the founder is the community. No exceptions.

Why one room? Because searchable history beats vibes. Discord is a black box you can't grep, and that's a real cost. If you can, use something with a web archive — GitHub Discussions, Discourse, or a plain mailing list. If you must use a chat app, mirror the good answers back into your docs. The moment a question gets answered twice in chat and zero times in your repo, you've built a memory leak.

The first ten people are hand-picked, not recruited

You do not have a community problem. You have a "ten people who care" problem. That's it. Ten is the number. Not a thousand.

Where do they come from? They're already using your thing. Go look at your logs. Whoever hit your API more than 500 times last week — email them. Yes, a real email, from you, no template:

Hey — saw you've been hammering the v2 endpoint. What are you building? I'm the one who wrote it. Happy to jump on a call if anything's broken.

That's it. That's the whole growth strategy. Ten of those. Two will reply enthusiastically. Those two become your moderators eventually.

The reason this works and paid acquisition doesn't: nobody joins a "community." People join a person who helped them at 2am. Anthropic recently bragged about their bio lab finding something big, and the interesting detail wasn't the discovery — it was that they kept humans in the loop the whole time TechCrunch. Same principle. The automation is not the point. The humans holding the wheel are the point. You are the human holding the wheel.

Answer in public, always

Every question gets answered where everyone can see it. Even the dumb ones. Especially the dumb ones, because the person reading silently has the same question and no courage.

Here's my actual rule: if I answer a question in DMs, I paste the answer back into the public channel within the hour. Non-negotiable. DMs are where communities go to die — you do the work, one person benefits, and the next person asks the identical question tomorrow.

Concrete version. Someone asks "why does my sync fail on large files?" I don't say "DM me." I write:

Chunk size defaults to 8MB. If you're on a flaky link, drop it: export SYNC_CHUNK_MB=2 Also check journalctl -u sync-agent -n 50 — bet you a dollar there's a TLS timeout in there.

That answer now lives forever. It shows up in search. It's worth more than any blog post I could write, because it's real and specific and it solved a real person's Tuesday.

This is also why searchable platforms win. Your community's value compounds in the archive. Treat every answer as a doc commit, because it is one.

Small rituals beat big launches

Communities don't grow from a big bang. They grow from rhythm. Pick two recurring things and never miss them.

The one I'd steal: a weekly "what broke this week" thread. Friday, same time, you post first. What broke in your own stack, what you fixed, what you're stuck on. People love this because it's the opposite of a highlight reel. It makes it safe to admit things are on fire — which, if you're running real systems, they occasionally are.

The other one: a monthly office hours call. One hour, no slides, no agenda. Bring your broken thing, we look at it together. Record it, throw it on a static page. Thirty minutes of ffmpeg and you have a content library nobody had to write.

What you do not do: a launch event, a swag drop, a "brand moment." Ceremony is what agencies sell you when they don't have substance. You have substance. Skip the confetti.

The contributor ladder is the whole game

A community that only consumes is a support queue. A community that produces is an asset. Your job is to build a ladder, and make every rung visible.

Rung one: they asked a question. Rung two: they answered someone else's. Rung three: they wrote a snippet. Rung four: they filed a good bug report. Rung five: they opened a PR. Rung six: they have commit access.

You move people up the ladder by noticing out loud. When someone answers a question correctly, you don't just say thanks — you promote them in the channel, by name, and tell them exactly what they did right. Public credit is the currency. It costs you nothing and it's worth more than any discount code.

And when someone shows up twice with good answers, hand them the keys. Mute permissions. Tag permissions. Whatever your platform calls it. Delegation is how you survive month seven, when the initial adrenaline is gone and you're tired.

When it goes wrong, own the process, not the person

Things will break. A bad release, a data migration that ate someone's config, a doc that was flat wrong. The instinct is to find who did it. Fight that instinct.

The useful move is what good orgs do everywhere: focus on cause and fix, not blame FastCompany. Post the postmortem publicly. What failed, what we changed, what we're watching now. No hedging, no corporate passive voice. "We shipped a migration that dropped indexes on tables over 10GB. That was our bug. Here's the fix and here's the check we added."

People trust a community that fesses up fast. They leave the one that spins.

The unglamorous numbers

Community isn't free. Budget the founder's time honestly: one hour a day, minimum, for a year. That's 250 hours before you have anything that resembles momentum. If you can't commit that, don't start — an abandoned room is worse than no room, because it tells every new visitor that you quit.

The good news: it's the cheapest marketing channel you will ever run, because the cost is your attention and attention doesn't need a budget approval. It just needs you to show up and answer.

Stop dithering about platforms. Open the room, put the link in your README, and go find your first ten people. You already know who they are — they're in your logs.

References

AI-assisted, curated for Side Quest Studios.