A developer posted on r/SideProject this week. He can build things. He said so without bragging, which is usually the sign it’s true. Give him an idea, enough time, and a problem he believes in, and he’ll figure out how to make the thing.
Then he listed what he doesn’t have. No audience. No following on X or LinkedIn. No email list. No community. No customers. “You’re just one person who can build something.”
The post is a distribution question, and it’s a good one. How do you get the first few hundred people to look at a thing when you’re starting from nothing?
But it’s his last line that stayed with me.
I can spend weeks or months building something, but if I have no idea how I’m going to get even the first 10 real users, I start wondering what the point of building it is in the first place.
r/SideProject, August 2026He opened by asking how to get eyeballs. He closed by asking whether to build at all.
Those are two different questions, and the second one is the real one.
The distribution question is the comfortable one
Not easy. Comfortable. There’s a literature for it. There are courses, threads, playbooks, forty people in any given comment section with a channel strategy. You can spend a productive month reading about SEO and cold outreach and feel, correctly, that you’re learning something.
The other question has no literature, because it isn’t about a method. “Is this worth building” is about a specific thing you made, and the only people who can answer it are people who have the problem it solves. You can’t read your way to it.
So the mind does something reasonable and expensive: it takes the unanswerable question and files it under the answerable one. I’d know this was worth it if I knew how to get users. That sounds like a distribution problem. It’s a conviction problem wearing a distribution problem’s clothes.
The tell is the timing. Distribution anxiety that arrives after launch is a real distribution problem. Distribution anxiety that arrives while you’re still building – the kind that stops you building – is something else.
The thread answered it better than it knew
Two replies in that thread got closer than the rest, and neither was talking about channels. One of them drew a line I hadn’t seen put that cleanly.
You don’t need an audience. You need access.
a reply in the same threadAn audience is people who know you and trust you, which takes years. Access is being able to message one person who has the exact problem you’re solving, which takes an afternoon. They are not the same asset, and only one of them is available to you today.
Another put a test on it: if you can’t name ten real people you could contact today about the problem, you probably don’t understand the market well enough to be building yet.
Ten names. Not ten thousand views, not a channel, not a launch. Ten people you could actually write to before dinner.
The two questions collapse into the same ten messages
Here’s the part worth sitting with. Those ten messages are simultaneously the validation work and the distribution work. You are not choosing between them.
If you write to ten named people who have the problem and a few write back, you’ve learned whether the thing is worth building, and you’ve also got your first users, which is what you were anxious about. If you write to ten and nobody replies, that’s the answer too, and it cost you an afternoon instead of six months.
The question that felt unanswerable turns out to be answerable in a week. Just not by reading.
I’ve been running the wrong one
I know the shape of this because I’ve had it backwards myself.
I build a product whose entire job is to tell a founder whether their idea is worth building. And for months I’ve been growing an audience for it – writing, posting, a newsletter – which is the slow, respectable, years-long asset. Meanwhile the people who had actually used the thing were sitting in a database I could have written to any afternoon.
Audience felt like progress. Access was already there, and I wasn’t using it.
What I’m not saying
I’m not saying distribution is easy or that ten conversations solve it. Getting from ten people to a business is hard, and I’m not going to pretend otherwise from where I’m sitting.
What I’m saying is narrower. If you’re building something and the distribution question has started to feel like a wall, if it’s the thing making you wonder what the point is, check whether you’re actually asking it. The founders I’d worry about aren’t the ones who don’t know which channel to pick. They’re the ones who’ve been researching channels for a month because it’s less frightening than sending the first message.
Ten names. Ten awkward messages. You’ll know more by Friday than another month of reading would tell you.
He opened by asking how to get eyeballs. The better question was the one he asked by accident.
Want more like this? Rick writes about the go/no-go decision, founder counterintuitions, and the business of building ventures worth building.
All writing