Ask HN: How do you manage distribution after building?
I built a slack message to code-fix app, so that you just paste the slack message and it figures out what repo is it about (down to which specific branch, worktree), providing a fix or hand off prompt at the end.
My goal is to learn about business by actually doing it and got a hard stop, impostor syndrome, at this step of having it almost ready and looking in the wild without knowing how to find if this is really valuable to someone else than me.
I know this is nothing new, but I'd love some human wisdom! What would you do to get unstuck at this point and validate your idea? Or what do you normally do at this point?
ps: this is my shout for help, frustrated after several hours of working through TOS, payments services and all that stuff. Learned a lot but now I look ahead and I'm shocked. So I need to learn what's next
4 comments
[ 43.7 ms ] story [ 522 ms ] threadHaving said that, if you really want to learn about business you need to do market research before building, which meant knowing this answer before you would've started building.
It's my first time even trying to distribute a product, so I'm kind of a bit bewildered with all the things I have to do manually and get out there.
And by the way, I will subscribe to your tool for HN alerts, as I missed your comment (sorry for that!)