A question under your post is the best reply you can get. Someone read the whole thing, wanted more, and gave you a reason to keep talking in front of everyone else who is reading. The usual mistakes are to answer with a link, to answer with a paragraph, or to get defensive when the question has an edge to it.
The replies below cover the four kinds of questions that show up under a post: the genuine how-did-you-do-it, the request for a link or a resource, the skeptical one that is half a challenge, and the one that is off topic or has already been asked three times. Each is short enough to read in the feed and specific enough to be worth reading.
Answer first, then everything else
The structure of a good answer is the structure of a good post: the answer in the first line, the reason or the detail in the second, and an optional door left open in the third. People scan replies the same way they scan the feed. If your first line is "great question!", most of them never reach the answer.
Answer in public even when you could DM. The person who asked is one reader; the people scrolling the replies are the rest. A clear answer under your post is also the cheapest way to show what you know, which is why answering well is one of the habits in how to get more engagement on X. Keep each answer under three lines, and if it needs more, say so and write it as its own post later.
Genuine questions about how you did something
How did you get your first customers?
Cold emails to 40 people who had complained about the old tool on Reddit. 6 replied, 3 paid. The other 34 never answered, which I took personally for about a week.
- Why it works:
- Real numbers in the first line, a human aside at the end. The aside is what people reply to.
Which tool did you use for that?
Figma for the mockup, then hand-coded. Tried two no-code builders first and both broke on the pricing table, so I gave up and wrote it. Took a weekend.
- Why it works:
- Names the tool, admits the detour, gives a time. Three facts in two lines.
How long did it take?
Three weeks of evenings, two of which were spent rewriting the first week. If I did it again: a weekend, because I would skip the admin panel nobody needed.
- Why it works:
- Answers the question and adds the lesson without being asked. Lessons travel further than durations.
Can you share the template?
Sure, it is a Notion page, I will DM it. Fair warning, it is ugly. The useful part is the second column where I score each idea on "would I actually pay for this".
- When:
- Someone asks for a file or a doc you are happy to share.
- Why it works:
- Says yes, sets expectations and gives the public readers the one idea that matters even if they never get the file.
Questions that are really asking for a link
Links in replies do poorly on X, and a reply that is only a link reads like a brush-off. Give the short version in the reply itself and offer the link as the second step. People who want the detail will ask; everyone else got the answer.
Where can I read more?
I wrote it up last month. Short version: the price went up, churn went down, support tickets stayed the same. Happy to send the link if you want the long version.
- Why it works:
- The summary is useful on its own, and offering the link rather than pasting it keeps the reply readable.
Is it live? Where?
Live since September, link in my bio. One thing to know before you try it: imports are slow for accounts with more than a few thousand posts. That is what I am fixing this week.
- Why it works:
- Points to the bio instead of pasting a link, and volunteers a flaw, which makes the whole reply more believable.
Do you have a course on this?
No course, and probably never. Everything I know about this fits in about ten posts, and most of them are already on this profile.
- Why it works:
- A clear no with a reason, plus a quiet invitation to read your other posts.
Skeptical and loaded questions
Some questions are challenges wearing a question mark. The temptation is to defend. The better move is to answer the literal question honestly, concede whatever is true in the challenge, and stop. Readers can tell the difference between someone who is confident and someone who is cornered, and a calm answer to a sharp question is one of the most persuasive things you can post.
Isn't this just the normal composer with extra steps?
Fair. The extra step is the part people pay for: it reads your last 30 posts before suggesting anything. If you do not need that, X's composer is free and good.
- Why it works:
- Concedes the framing, names the one difference, and does not oversell. The last sentence is what earns trust.
Doesn't this break X's rules?
It would if it posted for you. It does not. You write it, you press post, it goes out under your name. I read the automation rules twice before building it because I did not want to find out later.
- Why it works:
- Answers the real worry directly and shows you took it seriously before they asked.
Why would anyone pay for this?
Most people will not, honestly. The ones who do post daily and hate the blank page. Twelve of them pay me right now, which is enough to keep going and not enough to quit anything.
- Why it works:
- Agrees with the premise for most people, then describes the small group it is for, with a real number.
Source?
My own account, 30 days, about 60 posts. So a sample of one. I would love to see someone with a bigger account run the same test, and I will happily share the sheet.
- When:
- Someone demands evidence for a claim you made from your own experience.
- Why it works:
- Names the sample size before they can, and turns the challenge into an invitation.
Off-topic, repeated and clarifying questions
Can you do this for LinkedIn too?
Not yet, and maybe never. I know X and I do not know LinkedIn, and I would rather be good at one. If that changes you will hear about it here first.
- Why it works:
- A no that explains the reasoning, which is more respectful than a vague "maybe someday".
The question four people have already asked
A few people have asked, so once more for everyone: no free plan, a 7-day trial instead. The pinned post has the why. Happy to answer anything it does not cover.
- When:
- The same question keeps arriving under a popular post.
- Why it works:
- Answers it once for everyone, points to where the full answer lives, and stays friendly on the fourth repeat.
Unrelated: what is your stack?
Not what the post is about, but I love this question. Next.js on Cloudflare, SQLite at the edge, no servers I have to think about. Ask me again in a year when it bites me.
- Why it works:
- Acknowledges the detour and answers anyway. Off-topic questions from engaged readers are a gift.
Did you mean A or B?
Good catch, I meant the second one. I cannot edit the post without Premium, so this reply is the correction.
- Why it works:
- Fixes the confusion in one line and explains why the original is not changing, which stops the same question coming again.
Writing your own answers
- 01Put the answer in the first six words. "Three weeks." "Figma, then code." "No, and here is why."
- 02Add one detail that only you have: a number, a name, a mistake, a date.
- 03If the question has an edge, say the true part of the edge out loud before you answer. "Fair." "Partly, yes."
- 04Offer the link, do not paste it. People who want it will ask, and the reply stays readable for everyone else.
- 05Stop at three lines. If the answer needs more, say "this deserves its own post" and write it tomorrow. You just found your next post.
Do
- Answer every genuine question under your own post, even the small ones. It is your post; the replies are your room.
- Repeat yourself gracefully when the same question comes again. New readers did not see the first answer.
- Admit the size of your evidence before someone else does.
Don't
- Do not open with "great question". Open with the answer.
- Do not reply with a bare link. It gets fewer clicks than a two-line summary with an offer.
- Do not argue with a loaded question. Concede what is true, answer what was asked, move on.
Questions under your posts are also a map of what to write next. If three people ask how you did something, that is a post, and the reply you already wrote is its first draft. The shapes that draw good questions in the first place are in question posts that get replies. When an answer runs long, the X character counter will tell you where to cut.
BuzzyX · X growth workspace
Grow on X with posts that sound like you.
Compose in your voice, schedule the week, find posts worth replying to and read real analytics from the X API. $29/mo after the trial, everything included.
Frequently
asked questions
Something else on your mind? Get in touch.
Should I answer questions in the replies or by DM?
In the replies, almost always. The person asking is one reader; the people scrolling the thread are many more. Move to DM only for private details like an email address or a payment issue.
How fast should I answer?
Within the first hour if you can, while the post is still being shown and the asker is still around. A good answer a day later still helps the next person who reads the thread, so answer late rather than never.
What if I do not know the answer?
Say so and say what you would do to find out. An honest "I have not tested that" is more useful than a confident guess, and people respect it. If someone else in the replies knows, thank them and let their answer stand.
Should I answer the same question twice?
Yes, briefly, and point to where the full answer lives. New readers arrive hours after the first answer and never scroll to find it. A short repeat costs you ten seconds and saves them a search.
How do I handle a question that is really an attack?
Answer the literal question calmly, concede any true part of the challenge, and do not take the bait on the rest. If the person has no interest in the answer, one reply is enough and silence after that is fine.