Talk to Users Early
The biggest mistake I made early on was building in isolation. I’d spend months on a product before showing it to anyone. By then, I’d built the wrong thing beautifully.
Now I talk to potential users before writing code. Not surveys — actual conversations. The Mom Test changed how I think about this.
Ship Before You’re Ready
Perfectionism is the enemy of shipping. Your first version will be embarrassing. Ship it anyway.
I’ve learned that users forgive rough edges if you’re solving a real problem. They won’t forgive a product that never launches.
Revenue Validates Everything
Engagement metrics lie. Revenue doesn’t. A product with ten paying customers teaches you more than one with ten thousand free users.
Build something people will pay for, even if it’s a small amount. That’s the strongest signal you have.
Long-Term Thinking Wins
Short-term hacks get short-term results. The founders I admire — PG, Derek Sivers, the Basecamp team — all think in decades, not quarters.
Build something you’d be proud to work on in ten years. That filter eliminates most bad ideas immediately.
Stay Technical
As a technical founder, your superpower is that you can build. Don’t outsource that too early. Stay close to the code, especially in the early days.
The best product decisions come from people who understand both the business and the implementation.