alt Hacker NewsYou seem to have missed the key step. Talk to customers before you build. Build what they need. Then have them talk to you to adjust things until you really nailed down the product that solves their needs, and then have them talk to their friends about how much you rock.
Marketing comes later.
Replies
Strong agree here. I'm a non-technical founder.
I tend to interview 30-50 people initially to find a gap in the market. If I'm into something (strong PMF), a good percentage of those people I interviewed will be future buyers.
I typically have cascading meetings for the following steps:
1 - is this 10X better than what currently exists
2 - does our prototype look 10X better
3 - does our v1 solve the gap we found
4 - what features do we need to build in order to get you to pay for it
5 - what features do we need to get you to refer us to 3 friends
A meeting for each of those goals typically leads to customers (again, if I've found PMF).
I flip this around.
Marketing comes first. Sales second. Product third.
Perhaps in the past. I think the approach now will be to vibe code multiple projects very quickly and see which one has traction even with a low quality product. You will get much better feedback than a discussion with a potential customer who may not even know what they want or have a false idea of what they want. You can always improve a product that has demand and abandon the ones that no one even downloads. Usage and payment are the real test if a product is worth doubling down on.