The Real First Step to Getting Your First Users

The Question I Keep Seeing (and Why It Feels So Heavy)

Over the last day, I’ve seen the same question surface again and again, dressed up in slightly different clothes.

What’s the very first thing you do when you have a product and no audience?

It shows up as a marketing question. Or a customer acquisition question. Or a request for testers. Sometimes it’s framed with optimism (“I’m finally ready to launch”), and sometimes with exhaustion (“Six months in and I still don’t know how to get anyone to care”).

What struck me isn’t the tactics people are debating — Reddit vs. Twitter, private DMs vs. public posts, lurking vs. posting — but the underlying tension. There’s a quiet anxiety beneath all of it:

What if I put this out there… and nothing happens?

As a product manager, I’ve been in enough early-stage rooms to recognize that feeling instantly. It’s not really about marketing. It’s about exposure. About whether this thing you’ve been working on alone will survive contact with real people.

And here’s the deeper insight that keeps crystallizing for me as I watch these conversations: the real first step isn’t distribution. It’s creating a situation where someone can talk back to you — honestly.

Not at scale. Not optimally. Just truthfully.

Early Traction Is a Conversation, Not a Channel

A lot of the questions I’m seeing assume there’s a “right” channel you pick first. As if traction emerges because you chose Reddit instead of TikTok, or public posts instead of private messages.

In practice, early traction looks much messier.

When teams I work with look back at how they got their first 10–50 users, it’s rarely because they nailed a channel strategy. It’s because they found one place where:

A real problem was already being discussed
People recognized themselves in the problem description
The builder showed up as a human, not a pitch

That’s it.

According to a 2023 Indie Hackers survey, over 60% of solo founders said their first users came from direct conversations, not content or ads. That doesn’t mean content doesn’t matter — it means content works after you’ve learned how to talk about the problem in a way that lands.

One founder I worked with built a lightweight budgeting app for freelancers. No brand, no audience, no budget — the exact scenario everyone’s asking about. Their first real traction didn’t come from posting the app. It came from answering questions in a niche Slack group about how they personally tracked unpredictable income.

They didn’t even link the product at first.

When someone eventually asked, “Do you have a template for this?” — that was the opening. Within a week, they had 15 active users. Not because the product was magical, but because the conversation was grounded.

Practical takeaway:

If you’re deciding where to show up first, ask:

Where are people already articulating the problem in their own words?
Can I contribute without mentioning my product at all?
Would I still show up here if I weren’t building anything?

If the answer to the last question is no, people can usually tell.

The Quiet Places Where Your Product Is Already Being Judged

One of the most thoughtful threads I saw asked a slightly unsettling question: Has Reddit ever quietly helped or hurt your product without you noticing?

That question matters more than we admit.

In early stages, we tend to over-index on the feedback we can see clearly:

User interviews
Support tickets
Reviews
Tagged mentions

But communities don’t work like dashboards. Sentiment accumulates sideways.

I’ve seen products struggle not because they were bad, but because an early Reddit thread framed them poorly — and that framing stuck. No one tagged the company. No alert fired. But future users arrived already skeptical.

Research backs this up. A 2022 Nielsen Norman Group study found that people trust peer discussions in forums nearly as much as personal recommendations, especially for unfamiliar tools. When you have no brand, context becomes your brand.

This creates a subtle but important shift in how we think about “marketing” early on. It’s less about amplification and more about participation.

You don’t need to dominate a community. You need to not be absent from the places where your users are making sense of their options.

That doesn’t mean jumping into every thread to defend yourself. It means:

Listening for patterns in how problems are described
Noticing what language people reject
Understanding which tradeoffs people actually care about

The goal isn’t control. It’s awareness.

Testers, First Customers, and the Myth of Readiness

Several of the posts I saw were variations of: “I think I’m ready. How do I get my first users?”

I want to gently challenge the premise.

In my experience, you’re rarely “ready” in the way you imagine. And that’s not a flaw — it’s the point.

The founders who learn fastest treat early users less like customers and more like collaborators. Not in a performative way, but in a structurally honest one.

One AI analytics startup I advised made this explicit. Instead of recruiting “beta users,” they recruited co-investigators. Every tester knew:

What the product could not do yet
What assumptions were still unproven
Where the team was genuinely unsure

It slowed down acquisition. But it dramatically increased signal quality. Out of their first 30 testers, 8 turned into long-term users — not because the product was perfect, but because they felt respected.

There’s data to support this approach. Early-stage SaaS teams that conduct continuous qualitative feedback (not one-off betas) are significantly more likely to reach product-market fit within 12 months, according to First Round Capital’s analysis of early-stage portfolios.

Practical takeaway:

If you’re looking for testers or first customers, be explicit about:

What kind of feedback actually helps you
How much influence early users will have
What you’ll do with what they share

People are surprisingly willing to help — if they believe it matters.

When Traction Doesn’t Turn Into Revenue (and Why That’s Not Always Failure)

One thread that lingered with me came from someone who built a tool out of genuine frustration, got users… and made no money.

This is more common than we like to admit.

It’s tempting to interpret this as a pricing or positioning failure. Sometimes it is. But often, it’s a signal mismatch.

Users might be saying:

“This solves a real annoyance”
“I’m glad this exists”

But what they’re not saying is:

“I would reorganize my budget for this”
“This replaces something critical”

As product people, we have to sit with that discomfort. Especially early on.

A 2024 survey by Paddle found that nearly 40% of products with consistent usage still struggled to convert to paid plans — not because users didn’t like them, but because the product lived in the category of nice-to-have relief rather than meaningful leverage.

The hard work here isn’t growth hacking. It’s judgment.

Asking:

What job does this actually replace?
What risk does it meaningfully reduce?
What happens if this disappears tomorrow?

Those answers rarely come from dashboards. They come from uncomfortable conversations.

The Real First Step (and Why It’s Uncomfortable by Design)

So if I had to answer the question I keep seeing — what’s the very first step you take this week? — my answer would be this:

Create one honest loop where someone can respond to you as a person, not as a metric.

That might look like:

Writing a post that names the problem plainly, without a CTA
DMing five people to ask how they currently solve it
Responding thoughtfully in a thread where someone else is frustrated

Not to convert. To learn.

This step feels small. And it’s easy to dismiss because it doesn’t look like progress in the way we’re used to measuring it.

But in my experience, this is where real products begin — not when you speak, but when someone speaks back and you don’t rush to explain yourself.

Closing: The Human Risk We’re Actually Navigating

What all these conversations reveal isn’t confusion about tactics. It’s uncertainty about belonging.

Early product work asks a deeply human question: Is there a place for this thing — and for me — in other people’s lives?

That question can’t be answered through optimization. Only through contact.

As product managers, designers, and builders, we like frameworks because they give us something solid to hold. But the first phase of traction is intentionally unstable. It asks us to be present before we’re polished, to listen before we scale.

That’s not a marketing problem. It’s a courage problem.

And the good news is: you don’t have to solve it all this week. You just have to start one real conversation — and stay long enough to hear the truth.