Early Product Growth Starts With Exposure, Not Marketing

The Question Beneath the Question

Over the last day, I’ve read a dozen versions of the same question, dressed up in different words.

“What’s the very first thing you’d do to get users?”

Sometimes it’s framed as marketing. Sometimes as distribution. Sometimes as a quiet confession after six months of building alone. But underneath all of them is a deeper tension I recognize well — one I’ve felt myself.

It’s the moment when a product stops being private.

When it moves from something you control — the Figma file, the repo, the roadmap — into something exposed to other people’s judgments, misunderstandings, and indifference. That’s the real threshold founders and designers are standing at in these conversations. Not growth. Exposure.

As a product designer, I’ve learned that the first real feedback never comes from dashboards or campaigns. It comes from watching how people talk about your product when you’re not in the room. And that’s what these threads are circling, whether they realize it or not.

Why “First Users” Is the Wrong Framing

Most of the advice-seeking posts are explicitly about customers: how to get them, where to find them, whether to post or lurk, whether to go public or stay quiet.

But if you read closely, very few of these products are actually ready for customers in the economic sense. What they need first is something more fragile.

They need interpretation.

Early products don’t fail because no one sees them. They fail because the wrong story forms around them before the team understands how people actually perceive the value.

I’ve seen this play out repeatedly:

A founder posts in a subreddit asking for testers
The first few comments frame the product incorrectly
That framing sticks — quietly — and becomes the reference point
Six months later, the team wonders why onboarding is so hard

This connects directly to another thread I saw: someone worrying about Reddit shaping perception of their product without them ever knowing. That fear is justified. Research backs it up.

A 2023 Nielsen Norman Group study showed that users form a mental model of a product within the first 30–60 seconds of exposure, and that model is remarkably resistant to later correction. Once people categorize you incorrectly, every feature gets interpreted through that lens.

So when someone asks, “Do I post early and risk getting roasted?” the design question underneath is:

Have you designed for misinterpretation yet?

Early Traction Is a Design Problem, Not a Marketing One

There’s a pattern I keep seeing across these conversations that worries me.

People talk about channels before they talk about clarity.

But in early-stage products, distribution doesn’t create understanding — it amplifies confusion if the product’s value isn’t legible yet.

This is where design craft matters more than most growth advice admits.

The three things early users are actually reacting to

When someone encounters a brand-new product with no reputation, they are not evaluating your roadmap or your long-term vision. They’re responding to three immediate signals:

Can I tell who this is for? Ambiguity feels like risk. Products that try to stay flexible often read as unfinished.
Do I understand what problem this replaces? “New” is interesting. “Better than what I already use” is what earns time.
Does this feel careful? Not polished — careful. Thoughtful copy. Honest limitations. Clear boundaries.

In one of the threads, a founder described building an alternative to a $29/month subscription tool out of frustration. That origin story is powerful — but only if it’s reflected in the product experience.

If the pricing page, onboarding flow, or export limits recreate the same anxiety that motivated the build, users will feel the irony immediately.

That’s not a marketing miss. That’s a design alignment miss.

The Quiet Role of Communities (And Why Lurking Isn’t Passive)

One question that came up repeatedly was whether it’s better to lurk in communities or post early.

This is where I want to slow things down.

Lurking isn’t avoidance. When done intentionally, it’s contextual research.

Some of the best early product insights I’ve ever gathered came from:

Reading comment threads where no one knew I was a designer
Watching how people described their problems without solution language
Noting which words repeated — and which never appeared

Reddit, Discords, niche forums — these are not marketing channels first. They’re sensemaking environments.

A 2022 Pew Research study found that 64% of users trust peer discussions more than brand-authored content when evaluating new tools. That means your product is being “designed” in conversation long before you participate.

The mistake isn’t lurking.

The mistake is lurking without synthesis.

If you don’t actively document:

The metaphors people use
The frustrations that carry emotional weight
The workarounds they’re oddly proud of

Then posting won’t save you. You’ll just be louder without being clearer.

What I’d Actually Do in the First Week (And Why)

People keep asking for the one thing to do this week. I understand the impulse. When you’re tired and alone, constraint feels comforting.

But the answer isn’t a channel. It’s a posture.

If I were starting from zero — no brand, no audience, no budget — here’s the sequence I’ve seen work, repeatedly, across products and teams.

1. Write the page you’re afraid to publish

Not a landing page. A position page.

A simple document that answers, in plain language:

Who this is not for
What it intentionally doesn’t solve
The thing it replaces today
The tradeoff it makes explicit

This page isn’t for SEO. It’s for you. Because until you can articulate this without hedging, every public conversation will drift.

2. Share it privately with five people who will misunderstand you

Not friends who want to be nice. Not power users.

People adjacent to the problem who will read too quickly and jump to conclusions.

Watch where they get it wrong.

Those misunderstandings are design inputs.

3. Then choose one public surface

Not everywhere. One place where:

The problem already lives
You can respond in real time
Context sticks (threads > feeds)

And show up not as a founder pitching, but as a practitioner asking a careful question.

The goal isn’t traction.

It’s calibration.

The Loneliness Thread We Don’t Name

One of the quieter but most human threads asked: How do you start something without being lonely as hell?

That question matters more than most metrics discussions.

Building alone distorts judgment. You lose your sense of proportion — every comment feels huge, every silence feels like rejection.

This is why early collaboration, even informal, is a design concern. Not for velocity, but for emotional regulation.

Good products come from teams that can sit with ambiguity without panicking. That’s almost impossible to do alone for long.

I’ve seen early founders make irreversible product decisions simply to escape the discomfort of not knowing how something would land.

Loneliness pushes you toward certainty. Certainty pushes you toward rigidity.

And rigidity shows up in products as brittle flows, defensive copy, and over-explained features.

What These Conversations Are Really Teaching Us

If I zoom out on all of this — the marketing questions, the tester requests, the fear of invisible feedback — I see a community grappling with the same design problem from different angles.

How do we let people see our work without losing ourselves in the reaction?

That’s not a growth question. It’s a craft question.

The best early products I’ve worked on didn’t win because they shouted louder. They won because they listened longer — and designed with what they heard, not just what they hoped.

In design, we talk a lot about empathy for users. But early-stage work also requires empathy for the builder — for the very real vulnerability of putting something unfinished into the world.

Growth comes later.

First comes exposure. And whether that exposure sharpens your product or scars it depends less on where you post — and more on how carefully you’ve designed for being misunderstood.

That’s the part I hope we start talking about more.