AI coding tool founder: pitch posts flopped, problem-specific answers worked
A of a small spent a week actively promoting the product across communities, posting it broadly and hoping the right people would notice. Plain "here's what I built" launch posts got some views but little engagement and mostly silence. Comments and posts that instead answered one specific problem directly, without trying to sell anything, performed much better.
The is small, but the pattern was strong enough to change the posting workflow going forward. The core issue was that launch posts tried to do too much at once — explain the whole product, prove the pain point is real, build trust, handle objections, and ask for feedback all in one post, which ended up reading like a pitch deck dressed down as a casual post, and people could tell. The better-performing posts were narrower: one topic, one mistake, one specific lesson learned.
For an AI coding product specifically, that meant writing about narrow technical topics like and .
Key points
- Plain "here's what I built" launch posts got views but little real engagement
- Posts/comments that answered one specific problem directly performed much better
- Avoid stuffing one post with too many goals (explain + prove + trust + objections + feedback)
- For AI coding products, narrow technical topics like or worked well as content
- is small, but the pattern was strong enough to change the posting workflow