What founders should reply on X (and what to leave alone)

Two things go wrong when founders reply. The first is pitching: a reply that ends in "we solve this at Acme" gets muted, and the author's followers learn to skip your name. The second is advice without evidence. "You should raise prices" is a reply anyone can write. "We raised prices in March and lost two of 140 customers" is a reply only you can write, and it is far more persuasive even though it argues the same thing.

So the rule for a founder's reply is simple: a decision, a number and what happened next, in two or three lines. No product name unless someone asks. If you do not have a relevant decision from your own company, the honest move is a sharp question instead, which is what several of the examples below do.

Pricing posts draw the most replies of any founder topic, so a generic one disappears. The replies that stand out carry an exact before and after.

• Someone asks whether to raise prices

  Copy

  We raised from $19 to $29 in March and lost two customers out of 140. Both were on the annual plan and had emailed support more than anyone else. Revenue went up, support load went down. Raise it.

  When:

  A founder is agonising in public over a price increase.

  Why it works:

  A number, a month and a second-order effect nobody expected. It reads like a decision log, not advice.

• A founder posts a new pricing page

  Copy

  The middle plan is doing all the work here, nicely done. One thing I would test: the top plan says "everything in Pro" before it says what is new. People scan for the new thing first.

  When:

  Someone shares a screenshot and asks for thoughts.

  Why it works:

  One compliment about a specific choice, one test to run. It is help they can act on in ten minutes.

• A debate about free plans

  Copy

  Ran a free plan for a year. It brought signups and almost no conversions, and the free users wrote most of the support tickets. Switched to a trial with a card. Signups dropped by half, paying customers went up.

  Why it works:

  Your own case gives the thread a data point it did not have, and nobody can argue with what happened to you.

• Someone asks about annual discounts

  Copy

  We give two months free on yearly and about a third of new customers take it. The cash up front matters more to us than the discount costs. I would not go deeper than two months, it starts to look desperate.

  Why it works:

  A concrete policy, the take rate, and an opinion with a reason. Three things to reply to.

• A founder asks when to make the first hire

  Copy

  Hired my first person at $8k MRR and it was too early. The signal that would have worked for us was turning down work I could have billed. The revenue number did not matter, the no's did.

  When:

  A solo founder is weighing a first hire.

  Why it works:

  Admitting you got it wrong is more credible than a rule, and the alternative signal is something they can check tonight.

• A post about a bad hire

  Copy

  Had one. The tell I missed in the interview: every story was about the team's result and none were about a mistake they had made. I ask for the mistake first now.

  Why it works:

  A specific interview pattern is useful to every founder reading, and it does not name or shame anyone.

• A founder posts an open role

  Copy

  Shared this in a Slack of about two hundred designers I am in. One thing they will ask: is the salary range in the listing? The good ones skip postings without it.

  When:

  You can genuinely help spread the role.

  Why it works:

  You did something before replying, and you add the one fix that improves the listing.

When a founder posts bad news, the replies fill with sympathy and the occasional unsolicited playbook. Be the reply that either helps them look in the right place or simply shows up as a person.

• Someone shares a churn spike

  Copy

  When ours spiked it was one cohort from a single Product Hunt day, people who never set up the integration. Worth checking whether the churned accounts share a signup week. It changed what we fixed.

  Why it works:

  A diagnostic they can run in an afternoon, wrapped in your own story so it does not read as a lecture.

• A founder posts about a rough week

  Copy

  Sorry, that is a hard one. For what it is worth, the week I nearly shut down was the week before my best month. Not a promise, just a thing that happened. Take the weekend.

  When:

  The post is emotional rather than analytical.

  Why it works:

  You offer hope with a disclaimer and a small instruction. It respects the mood of the post.

• A shutdown announcement

  Copy

  Thank you for writing this instead of letting the domain lapse quietly. The part about building for the loudest users is going on my wall. What are you doing next?

  Why it works:

  Quoting the line that landed proves you read it, and the question looks forward instead of dwelling.

• A founder asks whether to raise

  Copy

  We bootstrapped and I have regretted it exactly twice, both times when a competitor outspent us on ads for a quarter. Then they ran out. If the product is bought rather than sold, raising mostly buys speed on marketing you may not need.

  Why it works:

  An honest tally of regrets is rarer and more useful than a position. The reader can weigh it against their own situation.

• Someone announces a round

  Copy

  Congrats. The hard part now is deciding what not to do with it. What is the one thing you are deliberately leaving unbuilt this year?

  When:

  You want to say more than congratulations without pretending to know their business.

  Why it works:

  A question only a founder would ask, and one the author probably wants to answer.

• A founder is upset that a competitor copied them

  Copy

  A competitor cloned our pricing page down to the FAQ order. Six months later they had changed it twice and we had not. Copying the page is easy, copying the reasons is not. I stopped checking.

  Why it works:

  Calm, specific and slightly funny. It also quietly argues against the outrage the thread is full of.

Other founders' launches are the easiest place to be useful, because most replies are a single word. Try the product first, then say what you noticed. There is a whole page of these in replies to launch posts.

• A founder launches

  Copy

  Signed up. First thing I noticed: the empty dashboard tells me what to do next, which most tools get wrong. Second thing: the export button is hidden under settings. I looked for it twice.

  Why it works:

  Proof you used it, one genuine compliment, one usability fix. Founders remember the people who did this.

• Someone shares launch numbers

  Copy

  Twelve paying customers on day one is more than most launches get. The fact that four came from your own replies rather than the launch post is the real lesson in this thread.

  Why it works:

  You read the numbers closely enough to find the interesting one, which is a compliment in itself.

1. 01Read the post twice and find the decision the author is actually facing. Reply to that, not to the headline.
2. 02Pull one episode from your own company that bears on it: a change you made, what it cost, what happened in the following month.
3. 03Write it as past tense fact. "We did, it caused" beats "you should" every time.
4. 04If you have no relevant episode, ask the question you would ask over coffee. Make it answerable in one line.
5. 05Delete your product's name unless the post asked for tools. If they want it, they will click your profile, which is the point.
6. 06Keep it to three lines. Longer replies get collapsed, and founders are skimming between meetings.

Replies are half the job. The other half is having posts on your own profile that confirm what the reply promised, which is covered in post ideas for founders and the wider X growth guide for founders. Keep replies under the limit with the character counter when a story runs long.