Build your brand before your product, or launch first and reveal yourself later?

I lean toward revealing early, but with a narrow problem instead of a broad brand.

I am testing a tiny niche around ecommerce sellers who source physical products from Alibaba/China. My first instinct was to publish a free checklist, but the stronger signal came when I reframed it as a specific moment: someone has a supplier quote or sample order in front of them and is not sure if the shipping, MOQ, Incoterm, or sample fee is reasonable.

That changed the product from "download a checklist" to "sanity-check this quote before paying."

So for me, the useful version of "brand before product" is not posting abstract founder content. It is repeatedly showing up around one painful buying moment until the market teaches you the wording.

I would reveal early, but keep the surface area small: one audience, one painful moment, one promise.

I think the best approach today is somewhere in the middle.

Build the product first enough to know the problem is real.
Then start building the founder brand while building publicly.

A strong personal brand helps massively with:

• early feedback

• trust

• distribution

• partnerships

• first users

• investor visibility

But I also agree there’s a danger when the founder becomes “bigger” than the product itself.

I’ve seen products get attention mainly because the founder already had an audience — but once the hype fades, retention exposes the real value.

The healthiest version in my opinion is:
people discover the founder first, but stay because the product genuinely solves something.

Also completely agree on separating business assets early.
One mistake many founders make is mixing:

• personal email

• personal social accounts

• product accounts

• domain ownership

• payment accounts

That becomes painful later during scaling, hiring, or acquisition.

Personally, I’m building my founder presence while building the product at the same time.
As a solo founder, distribution is honestly too hard to ignore anymore.

Product first for me, entirely. I had no audience, no brand, no following. Just a problem I needed to solve and the anger to build something about it.

The brand came from building in public. Posting about what I was making, why I made it, and what went wrong. The personal story became the brand almost by accident.

I'm not sure I could have done it the other way around. I needed the product to exist before I had anything real to say.

Both paths have merit, but I think the decision comes down to your distribution channel. For B2C with social proof mechanics, brand-first gives you a warmer audience at launch — people show up day one because they care about you. For niche B2B, it can actually backfire: you end up with an engaged audience that isn't your ICP. We launched PeakAI (B2B contact finder for India) without any personal brand, got early traction purely from solving the right pain, then started building content around that proof. Shipping first gave us the stories worth sharing.

Learned this the hard way. We launched PeakAI (B2B contact finder for India) on PH last month with zero personal brand build-up — no warm-up, self-hunted, wrong description. Got 10 upvotes.

Now relaunching in a few weeks and the entire prep is different: build the account trust first, engage genuinely in the community for weeks before launch day, find a respected hunter to vouch for the product. The product is the same. The context around it is completely different.

Nika's point about people over-indexing on the founder resonates though. The PH community is sharp — they'll see through founders who brand-build purely as a launch tactic. What seems to work is just being genuinely present in conversations that interest you, not mining for launch day goodwill.

I’m struggling with this now.

My wife and I recently built an Email List Analysis tool, and we’re attempting to build our brand to get exposure around it.

We’ve been hitting LinkedIn and a few other apps pretty hard recently, and while we are seeing some traction, I’m curious if there is a better approach.

I think it depends on what you're building, but trust is much harder to create than features. Building your brand early gives people a reason to care when the product finally launches, while launching first can work if the product itself creates strong word of mouth. The best approach is often doing both in parallel, sharing the journey publicly while validating the product behind the scenes.

但我觉得哪怕用户因为对某个人的信任而去使用或愿意给予更多的耐心，但是用户的留存和活跃 最终还是以来这个产品本身的价值，这一定是唯一影响因素

I'm a product marketer. So, I can give you my perspective. The first approach works well if you are a small, newbie team with an ambitious idea. If you build a good personal brand, it will help you with your launch. Sure, some people might try out your product for you and not the product. But hey, as a small team, if you could get constructive feedback from a tight-knit community, it's a WIN.

The second approach works if you've got good investors or if you're launching a new SaaS app inside an existing enterprise ecosystem. You already have the cushion to show your product to the world and then reveal yourself.

In both cases, building a good product is what matters in the end. If the product runs into issues constantly, the tight-knit community will collapse or the enterprise app might tank. I've witnessed both. So, I think mild personal branding without promoting your product aggressively is a good idea as long as the product is good.

That depends, when opportunity is there, branding can wait (and hold with a mild, clean, basic design), then rebrand before is too late. I am launching right now (literally today at PH) a project that way, registered branding, yes, but it is not perfect, however timing mattered this time.