|
|
|
How do you overcome the "build it and they will come" trap?
|
|
4 points
by entreel
55 days ago
|
|
I recently saw a dev tool with great architecture and test coverage sitting at ~30 users after 4 months. It seems like a common structural issue for technical founders. We naturally bias toward optimising code and feature completeness because that's what we are good at, while treating distribution as a secondary problem to be solved "later." For the technical founders here who successfully transitioned from engineering a product to actually distributing it, how did you force that mindset shift? Did you bring on a co-founder, or did you brute-force the marketing yourself? (I wrote up some of my own thoughts on this on Hashnode https://istiaq.hashnode.dev/the-ideas-in-startup-ecosystem, but I'm looking for practical advice from this community). |
|
Completely ignoring customers while you "build it and build it and build it and polish it and polish it some more and get to 100% test coverage and make sure the UX is good enough for for your dog to use and then polish some more" is the trap.
In other words: ship it when it barely works and don't improve it until a customer tells you to improve it.