How do you actually build genuine relationships with other makers pre-launch?
Building completely in isolation feels like a trap. As a solo builder, I want to spend my early stages connecting with people who are on the same path, rather than just silently working behind closed doors.
I'm curious about how people here cultivate meaningful connections before their big release day.
Exchanging value: How do you approach offering help or sharing unfiltered thoughts on someone else's work without being intrusive?
Community interaction: What are the best practices for starting real conversations in community spaces without sounding like you're trying to push something?
Staying accountable: How do you keep in touch with peers who share similar challenges in tech and design?
For anyone who has navigated this phase successfully: What was the single most effective habit or action that helped you meet great collaborators or peers here?
Would love to hear your personal experiences and advice! 🚀
Replies
I've had better results treating this as two or three useful comments a day, with no networking ask attached. The comments that turned into real maker conversations usually challenged one point and backed it with a mechanism from my own work. That gives the maker something concrete to answer.
I don't link my product or ask to move to DMs. If the maker replies with a real question, I answer it. If they don't, I leave it there. Being useful a second time has done more for the relationship than any follow-up message
The habit that worked for me was picking a narrow problem I actually have and answering other builders' threads about it - I'm deep in the localhost-to-live-URL mess, so when someone posts about a deploy that broke, I can say what specifically bit me instead of cheerleading. That gets replies because it costs me something to write. The second habit: when a maker ships something, use it for ten minutes before commenting, then send one concrete bug or friction point. Nobody forgets the person who found their broken signup flow.