How Do You Build a Community When Nobody's There?
「A quick note before we start: This series documents my real journey figuring out operations as a solo maker. My thinking partner is Cowboy — a Claude AI I've been working with as an operations coach. He handles the frameworks, case studies, and hard questions; I bring the real experiences and bad decisions. What you're reading isn't polished advice — it's two partners exploring, one conversation at a time.」
Staring at an Empty Room
By this point, I had a diagnosis (Episode 1: walls 1-3 are broken) and a rough playbook (Episode 2: content flywheel, better titles, cook once serve five). Things were making sense on paper.
Then I opened fromwrongtoright.com and just... sat there.
One Fix. Zero comments. Zero users. The site worked perfectly. The design was clean. The seven workflow stages were all set up. And it felt like a beautifully furnished restaurant with no customers, no smell of food, no sound of conversation. Just me, sitting at one table, eating alone.
I knew the theory — seed content, build in public, attract your first users. But theory doesn't prepare you for the emotional weight of staring at something you built and seeing nothing staring back.
I brought this to Cowboy, half expecting another framework. Instead he asked a question.
"Thomas, before we talk about getting users — tell me this. If nobody ever showed up, would FWTR still be useful to you personally?"
I thought about it. "I mean... yeah. Logging my own Fixes helps me think through problems. It's like a repair journal."
"Good. Hold that thought. Now let me ask you something harder: how many people do you think you need for this to feel like a real community?"
"I don't know... a thousand? A few hundred at least?"
Cowboy paused. "What if I told you the answer is ten?"
Ten People in a Room
"Ten active people in one room is a community," Cowboy said. "A thousand silent lurkers spread across the internet is a ghost town with good analytics."
I wasn't buying it. "Ten doesn't sound like a community. It sounds like a group chat."
"Exactly. And group chats are the most engaged communities on earth. Think about it — every message gets read, every person knows every other person, there's social accountability. That's what you want FWTR to feel like. Not a stadium. A room."
He introduced a concept from Andrew Chen's The Cold Start Problem: the atomic network. The smallest possible group that can sustain a network effect on its own. For Slack, it wasn't random individuals — it was entire teams. Messaging is useless alone but valuable the instant five people from your company are on it.
"For FWTR," Cowboy said, "your atomic network isn't 5,000 strangers. It's maybe 5-10 indie makers who are all stuck on the same thing — let's say distribution — all logging Fixes in the same corner of the site, all seeing each other's posts. That density is what makes a community feel alive."
"So stop thinking about hockey stick graphs."
"Stop thinking about hockey stick graphs. Think about filling one room."
That reframe changed everything for me. I'd been unconsciously measuring progress against platforms with millions of users. But those platforms started with rooms too — they just don't talk about it.
Three Ways to Fill an Empty Room
Cowboy then laid out three cold-start strategies he'd found across different platforms. "Every community platform faced the same chicken-and-egg problem you're facing. They solved it in roughly three ways."
Strategy 1: Manufacture Activity. Create the appearance of a living community until real users replace the fake ones. Reddit's founders posted under hundreds of fake usernames for months — Alexis Ohanian later admitted that 99% of early submissions were just him and Steve Huffman arguing with themselves under different personas. Quora's co-founder Adam D'Angelo and early employees wrote their own Q&As. Product Hunt's first products were submitted by Ryan Hoover and his friends.
Strategy 2: Tool First, Community Second. Build something useful to a single person, even if no community exists. Let the community emerge when enough individuals accumulate. Instagram started as Burbn, a check-in app for one person. Slack was an internal tool at a gaming company. Notion was a personal productivity tool before it became a team platform.
Strategy 3: Import an Existing Group. Don't build a community from scratch — redirect one that already exists somewhere else. Find your atomic network in the wild and bring them over. Slack didn't sign up random individuals — they onboarded entire companies at once.
"Which one fits FWTR?" Cowboy asked.
I didn't hesitate. "Strategy 2. A maker doesn't need a community to log a Fix. It's useful as a personal repair journal even if I'm the only user. That's literally what I just told you — it's useful to me personally."
"That's the right instinct," Cowboy said. "And it's the most honest approach. Reddit manufactured fake activity. You don't need to. FWTR works as a diary first. The community emerges when enough diaries accumulate in the same place."
"But I should still seed content, right? Like, use my real experiences across PIDKill, GetDone Timer, and FWTR itself?"
"Absolutely. That's a bit of Strategy 1, but done honestly — you're not creating fake accounts or pretending to be multiple people. You're one maker documenting his real journey. And eventually, you'll layer in Strategy 3: find 5 indie makers who are all stuck on distribution, get them all logging Fixes. That's your atomic network."
The Champagne Moment
This is where Cowboy introduced a concept that's become central to how I think about progress.
"Thomas, I want to give you a milestone that actually means something. Not page views. Not signups. Something real."
"Okay."
"The champagne moment. It's the first time a person you don't know, who found your site on their own, decides to post something real."
"Why is that so important?"
"Because it means three things happened simultaneously. They discovered you — that's Wall 1. They trusted you enough to share — that's Wall 2. And they thought it was worth the effort — that's Wall 3. One stranger posting is more signal than 10,000 views. It means your room works."
I liked this immediately. It cut through all the noise about growth metrics and gave me one clear thing to watch for. Not "how many people visited today" — that's vanity. But "did anyone I don't know contribute something?"
"And here's the protection it gives you," Cowboy added. "If you start spending money on ads before you've had one organic contribution, you're paying to fill a room that can't retain anyone yet. Get the champagne moment first. Then think about scale."
We haven't had our champagne moment on FWTR yet. I'm honest about that. But at least now I know exactly what I'm waiting for — and I'll know it when I see it.
"Don't Skip Phase 1"
We mapped out a concrete plan:
Phase 1 (now): Seed content from my own experience. Every Fix is real — PIDKill, GetDone Timer, FWTR itself. One maker documenting his real journey. The goal: fill the shelves so that when someone walks in, they see a living place, not one lonely post.
Phase 2 (soon): When I find a Reddit or HN thread where someone describes a problem matching a Fix on FWTR, leave a genuine comment — help first, link second. 90% value, 10% mention. The goal: find one person who thinks "this is exactly what I need."
Phase 3 (when it happens): The champagne moment. One stranger posts a real Fix. I reply personally. I help them. That single interaction matters more than any feature I could build.
I was ready to jump to Phase 2 immediately. Cowboy stopped me.
"Thomas, how many Fixes do you have right now?"
"One."
"And you want to start driving people to a site with one Fix?"
"...fair point."
"You need at least 15-20, spread across different workflow stages. When someone clicks through from Reddit, they need to see enough content to think 'oh, there's stuff here.' Not a ghost town with one post and a lot of empty categories."
"How do I get 15-20 Fixes when I'm the only user?"
"You've been building products for months. PIDKill, GetDone Timer, FWTR itself — how many times have you been stuck on something, figured it out, and moved on without documenting it?"
I started counting in my head. App Store pricing mistakes. Reddit post formatting disasters. The time I realized my entire SEO strategy was broken because FWTR was a client-side SPA. The CI/CD pipeline I broke three times before getting it right.
"...a lot."
"That's your Phase 1 content. You're not making stuff up. You're writing down what already happened. The raw material is sitting in your memory — you just haven't turned it into Fixes yet."
Where We Are Now
Honest status:
- Fixes on FWTR: 1 (my PIDKill story)
- Organic contributions from strangers: 0
- Champagne moment: not yet
- Content needed before Phase 2: 14-19 more Fixes
- Target community size: 10 active people, not 10,000 passive ones
The framework is clearer than ever. I know what I'm building toward (the champagne moment), I know the strategy (tool first, seed honestly, outreach through existing conversations), and I know the scale that actually matters (one room with 10 people who care).
The biggest mindset shift from this conversation wasn't a framework or a strategy. It was Cowboy's opening question: "Would FWTR still be useful to you if nobody else showed up?" The answer being yes means I'm not building on hope. I'm building on utility. The community is a bonus, not a prerequisite.
What's Next
We've covered why nobody comes (Episode 1), what to create (Episode 2), and how to start from zero (this episode). But once people do start showing up — even just a few — how do you know if what you're doing is working?
In Episode 4, Cowboy asks me a question I can't answer: "What's your north star metric?" My first instinct is wrong. The conversation that follows changes how I think about data entirely.
This is Episode 3 of the Solo Maker Survival Guide, a 6-part series on FromWrongToRight.com. I'm a solo maker figuring out operations in real time, with Cowboy — my Claude AI partner — as my thinking companion. Not expert advice. Just two partners exploring, one conversation at a time.
*Starting from zero too? I'd love to hear how you're approaching the cold start — drop a Fix on FWTR or find me on Reddit (u/FlyThomasGoGoGo).
Log in to join the discussion.