Should I build an audience first and then a product, or the other way around?
The short answer
If you can build an audience first, it is one of the biggest unfair advantages a solo founder can have, because launch day is no longer a cold start. But most people who say build audience first spend two years posting and never ship, so it is only worth it if you genuinely enjoy the medium and can be consistent. The safer middle path: build in public while you build the product, so the audience and the thing grow together.
Go deeper, your way
3 hand-picked resources, 3 link-checked. Pick how you want to dig in.
🎧 Podcast
✓ Link checkedFreeIntermediate
Why we picked it
Arvid Kahl bootstrapped and sold a real business, so this is a founder talking tradeoffs, not theory. He argues for finding an audience and its problems before writing code, and is honest that audience-first only pays off if you genuinely help people first. Useful as a starting point to hear how the audience-first sequence actually plays out.
Why we picked it
This is the clearest argument for why a launch should not be a single spike: if you share the process continuously, every day becomes a small launch and people are already paying attention when the big moment arrives. Kleon reframes building in public as generosity and discovery rather than self-promotion, which is the mindset shift you need before turning one announcement into an ongoing drip. Treat it as a starting point on how to think, not a tactical playbook, and it is short enough to finish in an afternoon.
Why we picked it
This is the canonical argument that you do not need a mass market to build something real, you need a small number of people who deeply want what you make. It is the cleanest way to see that a niche is not the same as being too small, because 1,000 people who buy everything you make is a business, while 100,000 people who half-care is not. Read it as a starting point for reframing what 'big enough' actually means.
