Build your brand before your product, or launch first and reveal yourself later?
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.
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?
Replies
I did it the "product first" way — spent 2 years building before telling almost anyone.
Launched Maleu (a life OS app) on PH today and I'm asking myself this exact question. The honest answer? I think it depends on what you're building.
For something like Maleu — where the EXPERIENCE is the product — revealing it before people could use it would've built hype around a ghost. The product had to exist first.
But for tools, for SaaS, for anything where the use case can be described clearly? Building the audience first makes total sense.
Am I biased because I built first? Probably. But I think "build the brand" advice sometimes becomes an excuse to not build the hard thing.
Having operated on both sides of the table as an allocator and a founder, I view this through a different lens. The binary of "personal brand vs. product" is a distraction. The actual prerequisite is Thesis and Positioning.
At askOdin, before we wrote a single line of code for our Deterministic Compiler, we established the exact taxonomy of the market. We identified that the last mile of AI isn't information—it's judgment. So, we defined the category first: AI Judgment Infrastructure™.
A personal brand is fragile and, as you noted, highly difficult to detach from the founder. An architectural thesis, however, is defensible.
If you launch software into an undefined space, you are forced to compete on UI and features. But if you rigorously define the taxonomy and the exact market friction first, you own the space conceptually. Then, the product simply becomes the infrastructure deployed to capture it.
Positioning dictates the outcome. Define the space, then build the architecture.
I think it depends on the type of product you're building, but if I had to choose, I'd lean towards building both at the same time. A personal brand definitely helps build trust, especially in the early days when people are deciding whether to give your product a chance. That said, a strong brand can't make up for a product that doesn't solve a real problem
Approach 2 is more sound ~ there is a big gap between being popular and having a great product.
Approach 1 is for big personal brands with lots to lose who must ensure their products are top-notch.
For the rest of us, trying to mimic some internet personality in Approach 1 risks Vibe-Founding.
I used to think you had to pick one. Now I think the answer is both. Your personal brand tells people why you exist and your product proves you deserve their attention. In AI, trust gets the first click, product quality gets the second. :))
Built Trackly quietly first, no personal brand push until the product had real feedback behind it. Slower distribution, but the early criticism was actually about the product, not softened because people liked me. Also kept personal and business accounts separate from day one, mostly by accident, but glad I did, saves headaches later on ownership.
I think the best approach is to build both in parallel, but at different speeds.
The product needs most of the attention because a personal brand cannot compensate for something that does not solve a real problem. At the same time, waiting until launch to introduce yourself means starting every conversation from zero.
I’m trying to share selected lessons, decisions, and mistakes while building—not to become the product myself, but to give people a reason to understand and trust the person behind it.
Ideally, the founder creates initial trust and the product earns the long-term reputation.
Softorino 💻📲
I think it depends on what you sell. Utilities – product first, nobody buys a file converter because of the founder's posts. But brand compounding is real: our 2nd, 3rd, 14th app each launched easier because the name already meant something. So my vote is product first, brand starting the same week. And your "give someone keys" point is painfully accurate – I've watched friends spend months untangling a product from personal accounts)
How easily do you think a personal brand and people's willingness to try a product recover if the initial launch doesn't match the quality of the person? I'm thinking of the recent influencer/actor launch of Goose (a dating app). The marketting and app were heavily panned within the community, and the associated person with a high profile has already departed from the company. Does this mean the product will die now or is there a chance to recover? Can you think of any instances where a brand has recovered after something like this?
I’d probably go somewhere in the middle.
I like knowing who’s behind a product, but I don’t think the founder should become the product. Build the brand early, but keep the actual product identity separate enough that someone else could eventually run with it.
Also 100% agree on the personal accounts thing. That can get messy really fast.