Reply writing
A reply that agrees is a reply nobody reads
Reply writing is the practice of contributing to somebody else conversation in a way that is useful to the readers of that thread, not only to the person who posted it.
A reply has a much harder job than a post. It arrives uninvited, underneath somebody else work, in front of an audience that came for them. The only thing that earns attention in that position is being useful, which is a much narrower target than being agreeable, and it is why most replies are read by nobody.
Agreement is not a contribution
Great point, this, and completely agree are all invisible. They are read as noise even when sincere, because they add nothing a reader can take away. If the only thing you have is agreement, either add the reason you agree from your own experience, or do not reply.
Write for the third reader, not the author
The author will see almost any reply. The value is in the hundred people reading the thread who have never heard of you, and they are only served by something specific: a number, a counterexample, a constraint the post left out. Aim your reply at them and the author benefits anyway.
Specificity is the whole technique
One concrete detail beats three paragraphs of general agreement. What happened when you tried it, what it cost, where it broke, what you would do differently. Specifics are also unfakeable, which is why they read as human even when everything else is being automated.
Disclose, briefly, and only once
If you sell something relevant, say so in a clause and move on. Hiding it is worse than mentioning it, and repeating it in every reply is worse than both. Readers forgive a vendor who is useful; they do not forgive one who is pretending not to be a vendor.
How to do it
Read the whole thread first
Including the replies. Half of bad replies are bad because they repeat a point somebody already made twenty minutes earlier.
Decide what you are adding
Experience, a counterexample, a correction, or a question that opens something up. If you cannot name which, you do not have a reply yet.
Open with the substance
No preamble, no compliment, no restating the post. The first eight words decide whether the rest is read at all.
Keep it short and finish cleanly
Two or three sentences on X, a short paragraph on LinkedIn. Do not close with a question aimed at manufacturing engagement; it is transparent and it reads as a tactic.
Read it as a stranger before sending
If a reader who does not know you would learn nothing from it, it is a like and not a reply.
Common mistakes
- Opening by restating the post, which spends the only line anyone reliably reads.
- Pure agreement with no experience attached, which is invisible even when sincere.
- Pitching in a thread that was not about you, which costs more trust than any single lead is worth.
- Replying to a thread that is days old, where the audience has already moved on.
How Quillen handles reply writing
Quillen drafts replies against a persona built from your own writing and lints each draft against it before the draft reaches your queue, so the generic agreement pattern is what it is built to avoid rather than what it produces. By default nothing posts without you approving it: the exception is an optional autopilot that is Team plan only, off unless you switch it on per LinkedIn campaign, and even then only a draft that passes the voice lint is eligible. On X automatic posting is not available at all. Editing before you approve is the intended workflow, and your edits feed back into the persona.
Common questions
- How long should a reply be?
- On X, two or three sentences. On LinkedIn, a short paragraph. Length is not the point but brevity forces you to lead with the substance, which is.
- Should I mention my product in a reply?
- Only when it directly answers what was asked, and then in a clause rather than a paragraph. If your product is not the answer to the question, mentioning it costs you the reader.
- Is it obvious when replies are AI assisted?
- It is obvious when they are generic, which is the usual failure: no specifics, no experience, an opening that restates the post. A draft written against your own past writing and edited by you before it goes out does not read that way.