I posted like a founder in launch mode for a week. The useful part was everything after I stopped pitching.
context: i'm the founder of a small AI coding tool and a few other tiny software products. not linking anything here because this is more of a field note than a launch post.
I spent the last week doing the thing a lot of founders do when they are tired: posting the product everywhere and hoping the right people magically appear.
It did not work very well.
The posts that were basically "here is what i built" got some views, a few comments, and a lot of silence. The comments that did better were the ones where i forgot about conversion and just answered the exact problem in front of me.
Tiny sample size, so don't read this as gospel. But the pattern was strong enough that i'm changing the workflow.
What went wrong
- I tried to make launch posts carry too much weight
A launch post is a bad place to explain the whole product, prove the pain exists, build trust, handle objections, and ask for feedback at the same time.
That makes the post read like a pitch deck wearing a hoodie. People can feel it.
My better posts/comments were narrower. One topic, one mistake, one specific thing learned.
For an AI coding product, that meant talking about verification drift, persistent terminal sessions, and why agents need proof gates instead of vague "done" messages. For a VPS deployment product, it means talking about rollback, logs, SSL, and boring server ops instead of "Vercel for VPS" over and over.
The concrete pain works better than the positioning line.
- I was posting from the product's point of view, not the user's moment of pain
This sounds obvious, but i kept catching myself doing it.
Bad version: "my app supports Claude Code, Codex, OpenCode, persistent terminals, remote control..."
Better version: "i keep losing track of which AI agent changed what, which tests actually ran, and whether the terminal state survived after i closed the app. here is the workflow that reduced that chaos."
Same product area. Completely different reader reaction.
The second one gives someone a useful mental model even if they never use my tool. That is the bar i want to hit.
- I underestimated how much Reddit hates founder smell
Not founder honesty. Founder smell.
Founder honesty is: "i built this, i'm biased, here is exactly what broke and what i learned."
Founder smell is: "we're excited to announce a revolutionary platform that empowers builders..."
I had more of the second than i wanted to admit. Even when the wording was casual, the structure was still product-first.
The fix i'm using now
Before posting, i force the idea through this filter:
- would this still be useful if i removed the product name?
- is there one specific mistake or workflow change?
- can a reader copy something from it today?
- am i avoiding links unless the subreddit clearly wants them?
- did i disclose that i'm the founder if the product is mentioned?
If the answer is no, it becomes a draft, not a post.
The new weekly cadence
I'm moving to this:
- 80 percent: useful comments on posts where i can actually help
- 15 percent: founder notes like this, with no links
- 5 percent: product-specific posts, only in communities where that is explicitly allowed
The comments are not a trick. They are research. If i can't be useful in a thread about the problem, i probably don't understand the problem well enough to write a good launch post.
The most useful thing i learned this week
A small, honest comment can tell you more than a polished launch post.
One person asking "but would users come back in week two?" is more valuable than twenty passive upvotes, because now i know what to measure. For my AI coding tool, that means repeat sessions, resumed terminals, projects reopened, and whether people come back to the same agent workflow after the first novelty hit.
That changed the product analytics i care about. Not downloads. Not signups. Repeat project/session resume.
That is the kind of feedback i was hoping launch posts would magically generate, but it came from conversation instead.
My current rule
If a post reads like it was written to extract attention, i don't post it.
If it reads like a useful note i would send to another founder even if there was no product attached, it is probably safe.
Curious how other builders handle this. Do you separate "helpful public notes" from actual launch posts, or do you just post the product directly and let the market judge?
