BETTER CONVERSATIONS
Write product replies on X that sound like you
A good product reply sounds like a person who read the post. It answers one thing, makes one relevant connection, and leaves the other person free to decide.
Match the language and the actual question
Reply in the language of the original post. If the author mixes languages, follow the main language of the question rather than forcing your website’s language into the conversation.
Read any surrounding context before sending. A question about running a model locally is different from a question about tracking hosted API costs. Relevance comes before tone.
Use a truthful first-person voice
“I built…” clearly identifies you as the maker. Follow it with one verified capability that addresses the question. Do not invent customer results, imply you are an independent reviewer, or claim you personally faced a problem unless it is true.
Keep the sentence simple enough to say aloud. Remove generic openings such as “In today’s fast-paced world” and praise that could be pasted under any post.
Let the joke be optional
A small joke works when it reflects the frustration in the post. It should not distract from the answer or make light of a serious problem. If the wording feels forced, a direct reply is better.
Aim for one or two short sentences and a product URL. Do not bury the link behind a list of features or repeat it several times. The examples on this page use a placeholder URL and must be adapted before sending.
Review the draft, then send it yourself
Start tiny generates a reply when you open a discovered opportunity. The draft uses the original post’s language, your product brief, and your direct product link. You can edit it or request a new version.
Publish reply copies the complete text and opens the original X post. You paste and send there; Start tiny does not post replies automatically or count a copied draft as a published reply. Check factual claims, tone, the URL, and whether a recommendation is welcome before sending.