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

  1. I've always been on the personal brand side. More and more founders are building it now (sometimes even before the product is ready – while it's still in development, before seed fundraising). The CEO builds their position so the product sells more easily at the official launch.

  2. But I have experience with people who built the product, scaled it, and only then did we discover who was behind it.

Honestly, with the first approach, I'd be concerned that people invest more in me as a person than in the product. People would idealise the founder and overlook the product's flaws (which could hurt development and constructive feedback).

+ I noticed the most common mistake that many people who started building a personal brand first, connected their product to their personal accounts (emails, social media, etc.) and started having a problem selling these things, because they cannot "give someone keys" to their personal profiles.

Which opens the question:

Which approach brings more advantages in your opinion?

7.6K views

Add a comment

Replies

Best

Just shipped my first SaaS this month after 90 days solo, and

I think the binary framing misses what actually happens.

I "built first" in the sense that I didn't market until I had

a working product. But the brand was forming in private the

whole time — every UX decision, every word on the landing,

the choice of which features to cut.

When I finally went public, the brand didn't need to be

constructed. It needed to be uncovered.

Build your product first. The brand is already happening

whether you notice or not.

  Love this perspective. The idea that the brand doesn't need to be "constructed" but "uncovered" is really powerful. Every product decision you made while building was already shaping how people would perceive you. Congrats on shipping - that 90-day solo journey says a lot about the brand already.

Building a personal brand first can definitely help with early trust, distribution, and faster validation, especially in crowded markets. But as you mentioned, it can also create dependency on the founder’s identity, which becomes a problem later when you want to scale or separate the product from yourself.

On the other hand, building the product first and revealing the team later often leads to stronger product focus and more honest feedback loops, but it can be harder to get initial traction without any visibility.

Personally, I think a balanced approach works best — start with light personal branding to validate the idea and attract early users, then gradually shift focus to the product itself as it matures.

That’s something I’m experimenting with as well while building my own project, including tools like under my brand. It helps keep early awareness while still letting the product speak for itself over time.

For specialist/practitioner products this 'brand vs product' framing breaks down — the product IS the brand statement. A financial model template built from real deal experience signals more credibility than a thousand brand posts ever could, because the buyer (a CFA with a deal on their desk) reads structure, assumption choices, and waterfall logic the way a developer reads source code. They can tell in 90 seconds whether the author has actually sat in the same chair.

What does compound: credentials + shipped artifacts. The CFA charter, FMWC Top-4, and CFI 3rd-place placements get the door open; the Medium pieces and templates on practitioner topics (DSCR sculpting, tax equity, merchant power) are what convert. Cold brand-building without artifacts feels hollow in niche professional markets — and over-investing in personal brand before you have a product to anchor it tends to age badly.

So: build a brand THROUGH the product, not before it. Especially in B2B / specialist fields.

Launched Lumi 8 days ago and wrestling with exactly this. Went product-first, shipped quietly, posted on Reddit and LinkedIn without much personal brand behind it. Got engagement but zero signups in the first 24 hours.

The "can't hand over personal accounts" point hit home. I deliberately kept Lumi's social presence separate from my personal profiles from day one, partly for this reason.

My current take: product-first gives you honest signal, brand-first gives you distribution. At pre-revenue stage I'd rather have honest signal. But I'm starting to think you need at least a minimal personal presence to give people someone to trust, not just something to try.

Still figuring it out, 1 user after 8 days suggests I need more distribution regardless of which approach.

Didn't really plan it as "personal branding" tbh.

12 years ago when I got into XR and AR, there weren't many people in the space. I just started sharing what I knew. Talks, roundtables, conversations.

Over time that became social capital. People I met back then turned into clients or partners years later. Not because of reach, but because of trust.

Small but engaged community beats big and passive any day.

And yeah, keeping personal and product accounts separate from day one is just basic hygiene.

I personally like the idea of putting the product/platform out first, scaling it, and then getting the great reveal because it allows ppl to focus on the product/platform. The platform I'm building is related to combat sports and my experience in combat sports has been with my husband (Coach) and son's. In my opinion, if I were the face of the platform, no one would take it seriously. So I plan to have my husband and the athletes at the gym be the representatives. Or like Nika mentioned, use UGC creators.

From my experience in PR and marketing for founders across different industries, it really depends on the type of product you are launching, as well as the founder(s)' background. A founder who have enjoyed successes and proven track record in their career can ride on brand building first and getting feedback early stage, while a younger founder may do better with building a product first and use good marketing strategies to gain users and obtain feedback to further develop their product.

I'm actually trying to figure out the best approach to this right now. I've always preferred to remain anonymous but I do things in extreme bursts of energy - my most recent burst involved me making an entire app when I've never done that before.

So now I'm trying to figure out how to play the....ceo/developer game?
I think I'm a cool person but I'm not sure how to translate that, or even If I should. I'd like for the product to speak for itself while I remain an afterthought personally.

the 'can't hand over personal accounts' part is underrated, i've seen 2 web3 founders kill acquisition talks bcz the twitter was tied to their face. brand-first works if you treat it like a separate asset from day one, not a side effect. curious if anyone here has actually pulled off the handover cleanly?

I’d say the strongest approach is a hybrid.

A founder’s personal brand is great for trust, distribution, and early momentum. But the product should have its own identity and assets from day one: domain, email, social accounts, community, and customer relationships.

The founder can open doors, but the product must be able to stand on its own.

Otherwise, you’re building attention around a person, not a company — and that can become a problem when you scale, raise, or sell.
But I think this point has already been mentioned earlier

First
Previous
•••
101112
•••
Next