Blog · Craft
How to reply to a stranger on X without sounding like spam
Finding the conversation is the easy half. The reply is where most founders lose it, and the failure is almost never rudeness — it is that the message reads as an advert, and people have a reflex for adverts that fires before they finish the first line.
What follows is six pairs. Same post, two replies. One starts a conversation, one gets scrolled past, and the difference is usually one sentence.
The rule underneath all of it
A public reply is read by the author and by everyone following the thread. That changes everything. An email is a private transaction; a reply is a small piece of public writing that says something about you to a few hundred strangers. Write for both audiences and you will not be able to write an advert, because adverts embarrass you in public.
Six pairs
1. Someone asks for a recommendation
The post: “Any recs for invoicing software that isn’t QuickBooks? Freelance, UK, mostly EU clients.”
Scrolled past: “Hey! You should check out [product] — we help freelancers invoice without spreadsheets. Free trial here: [link] 🚀”
Gets a reply: “EU clients is the bit that catches people out — are you needing reverse-charge VAT handled on the invoice itself, or just the export for your accountant?”
The rule: answer the hardest part of their question, not the easy part. They said “mostly EU clients” for a reason. Naming it proves you read the post and that you know the domain. You have not mentioned your product and you are now the most useful person in the thread.
2. Someone is leaving a competitor
The post: “We’re finally moving off HubSpot this quarter. Team of six. What are people using that isn’t a second job to configure?”
Scrolled past: “[Product] is perfect for teams your size! Setup takes 10 minutes and we have a HubSpot importer. Happy to hop on a quick call 👋”
Gets a reply: “The configuration tax is the real cost with HubSpot — most teams your size only ever used about four of its objects. Do you need the historical deals migrated, or is this a clean start?”
The rule: the migration question is genuine and it is the thing they have not thought about yet. “Happy to hop on a call” asks for thirty minutes from someone who has given you nothing.
3. Someone is venting, not shopping
The post: “third week in a row the export silently failed. no error, no email, just no file. i’m so tired.”
Scrolled past: “Ugh, that’s rough! We built [product] exactly because of problems like this — never had a silent failure. Might be worth a look?”
Gets a reply: “Silent failures are the worst kind — you only find out when someone downstream asks where the file is. Is it failing on a schedule or only on the big exports?”
The rule: when someone is venting, a recommendation reads as circling. Sympathy plus one diagnostic question reads as a peer. If they want to know what you do, they will look at your profile — and they do, far more often than people expect.
4. Someone is comparing two options, and you are neither
The post: “Notion vs Coda for a docs-heavy team — anyone actually used both properly?”
Scrolled past: “Have you considered [product]? It does everything both of them do but faster and cheaper.”
Gets a reply: “Used both. The real split is whether your docs need to behave like data — Coda if yes, Notion if they are mostly prose. What is the doc count roughly?”
The rule: if you are not one of the two named options, you get one sentence to be useful before you are allowed to exist. Answering their actual question honestly — including recommending a competitor — is what buys that sentence. “Have you considered us” from a stranger who has not helped is the definition of noise.
5. Someone states a budget
The post: “Salesforce quote came back at 4x what we pay now for a five person team. Budget is about $300/month. What are the actual alternatives?”
Scrolled past: “We’re $49/user — that works out well under your budget! DM me and I’ll set you up.”
Gets a reply: “At five seats and that budget you have real options — the thing to check before you commit is whether you need the reporting that made the Salesforce quote expensive in the first place, or whether that was seats. Which was it?”
The rule: a stated budget makes people pitch immediately, which is exactly why nobody stands out. Slowing down and asking what actually drove the price is both more useful and more memorable. And never “DM me” — see below.
6. Someone is hiring for the problem you solve
The post: “Hiring a part-time ops person to sort out our reporting mess. 10 hrs/week, remote.”
Scrolled past: “Or you could just use [product] and save the headcount 😉”
Gets a reply: “Worth deciding up front whether the mess is the reporting or the data underneath it — a person fixes the first, tooling fixes the second, and hiring for the wrong one is expensive either way.”
The rule: never tell someone their hiring decision is wrong. Give them the distinction that lets them decide, and be right about it. If tooling is the answer they will find you.
The tells, listed once
Every scrolled-past example above trips at least one of these. They are worth knowing as a checklist because you will reach for them under time pressure.
- Opening with your product name
- A link before anyone asked for one
- “Happy to hop on a quick call”
- “DM me” — moving a public conversation private, uninvited, is what most people actually mean by spam
- Hashtags in a reply
- A feature list
- Emoji doing the work a sentence should be doing
- Exclamation marks, plural
- “Great question!” and every other opener that could precede any post
- The same sentence you already posted under four other threads today
That last one is the one that actually gets people muted and reported. Your replies are public and one click from your profile. A visible column of near-identical messages turns “helpful founder” into “bot” instantly, and no individual reply can undo it. Our reply check flags most of these before you send, free and without an account.
What to do when you have nothing to add
Do not reply. This is the hardest discipline in the whole channel and the one that protects everything else.
If you cannot name something specific about their situation, or ask something you genuinely do not know the answer to, then the only thing you have to contribute is your product — and that is an advert. Follow them instead. Half the time they post again a week later with more detail, and by then you have something to say.
Two good replies a day beats fifteen. The fifteen version does not just underperform; it actively costs you, because it is visible.
Whether to say you built the thing
Yes, and early — but not first. The order that works is: be useful, then disclose if it becomes relevant. “Full disclosure, I build something in this space, so take this with salt” after a genuinely helpful paragraph reads as honest. The same sentence at the top reads as a pitch with a disclaimer attached.
Hiding it is worse than both. Somebody always checks the profile.
Where this fits
Replies only matter if you are in the right conversations to begin with. The guide to finding buyers on X covers the searching, the operator reference covers the queries, a mention is not a buyer covers which results deserve a reply at all, and why the first useful reply wins covers how little time you have.
Askline drafts the reply in your voice, in three registers, and stops there. You edit it and you send it — from your account, when you decide. Run it on your offer and see what it writes.