You’ve found a live requirement post. The client needs exactly what you do, the post is forty minutes old, and there are only three comments. This is the best position you will ever be in as a freelancer — and it is astonishingly easy to waste it with a reply that reads like everyone else’s.
This is a practical guide to what to write. Templates are included, but read the reasoning first, because a template pasted verbatim is exactly the thing we’re trying to avoid.
What the client is actually doing when they read replies
Picture the person who posted. Within an hour they have eleven replies. Eight say “Interested! Please check DM”. Two are agency boilerplate beginning “Greetings of the day”. One says:
“We’ve built three Shopify subscription stores this year — the recharge migration you mentioned is usually the messy bit. Happy to share how we handled it. DM’d you.”
The client is not carefully evaluating candidates. They are triaging under overwhelm, looking for any signal that lets them ignore ten replies and talk to one person. Your entire job is to be the reply that survives triage. That means three things: show you read the post, show you’ve done this exact thing, and make the next step effortless.
The public comment: two sentences, three jobs
Comment publicly before (or as) you DM. It does three jobs: it timestamps you, it shows the client you’re real, and it markets you to everyone else reading the thread.
Template:
[Specific acknowledgement of their requirement] — we/I [one-line proof of doing exactly this]. Sent you a DM with [concrete thing].
Examples:
Migrating from WooCommerce mid-season is doable without downtime — did this for two retailers last year. DM’d you a rough step-by-step.
Fellow B2B SaaS marketer here — I ran exactly this kind of cold + warm LinkedIn motion for a fintech client. Sent over a couple of results in DM.
Keep it under forty words. Do not pitch your full service list. Do not say “please check your inbox sir”. One specific noun from their post is worth more than five adjectives about yourself.
The DM: the 5-line structure
The DM that wins is short enough to read on a phone lock screen and specific enough that it could not have been sent to anyone else. Five lines:
- Anchor — name the post and the specific requirement, so this is clearly not a broadcast.
- Mirror — restate their core problem in one sentence, ideally sharper than they put it. This is the line that does the persuading.
- Proof — one (1) relevant example with a concrete outcome. A link if you have it. Not a portfolio dump.
- Useful gift — one genuinely helpful observation, question or warning about their project. This separates you from everyone selling.
- Tiny next step — a low-friction call to action with a time-bound offer.
Template:
Hi [name] — saw your post about [specific requirement].
Sounds like the real challenge is [restated problem — e.g. “getting the migration done without losing the subscriptions data”].
I did [almost-identical project] for [client/type of client] — [one concrete result, e.g. “moved 14k subscribers across with zero churn from the switch”]. [Link.]
One thing worth checking before you brief anyone: [genuinely useful question/warning specific to their project].
Happy to talk it through — I have [two specific slots] this week, or I can send a short written plan first if that’s easier.
That’s it. Six to nine sentences. Every line earns its place or gets cut.
The “useful gift” line, expanded
Line four is where most freelancers have nothing, and it’s the highest-leverage sentence in the message. It proves expertise by demonstration rather than assertion. Some patterns:
- The scoping question: “Do you already have the product data in a structured format, or is extraction part of the job? It roughly doubles the timeline if so.”
- The hidden-cost warning: “Worth knowing: the plugin most people use for this hasn’t been updated for the latest API — budget for a workaround.”
- The sequencing tip: “If the deadline is fixed, I’d brief the copywriter before the designer — it’s the usual bottleneck on these.”
You know ten of these for your specialism. Pick the one that fits their post.
The follow-up: once, with new value
If you’ve had no reply in 24–48 hours, follow up exactly once. Never “just bumping this”. Add something:
Hi [name] — following up with something concrete: I sketched [a quick outline / two homepage directions / a rough migration plan] for your [project]. [One-line summary or attachment.] If you’ve already found someone, no worries at all — good luck with the build.
The graceful exit line matters. Clients remember the people who were generous and unpushy; the next requirement they post, you start with credit in the bank.
Five mistakes that get good freelancers ignored
- Leading with your biography. “I have 9 years of experience in…” is about you. The winning reply is about them. Credentials go in line three, compressed to one proof point.
- Asking questions the post already answers. “What’s your budget?” when the budget is in the post tells the client you didn’t read it. Triage: failed.
- Sending a price in the first message. You don’t know enough to price it, and a number without context anchors you as a commodity. Sell the conversation, not the quote.
- Over-formatting. Bullet-pointed, bolded, emoji-studded DMs read like automation. A plain, well-written message reads like a person.
- Being slow because you’re being thorough. The polished reply on day two loses to the specific reply in hour one — we’ve written about why the window closes so fast. Prepare your proof links and slot offers in advance so speed costs nothing.
Build your reply kit once
You should never be writing a reply from scratch at speed. Keep a small kit:
- Three versions of your proof line, one per service you offer, each with a real outcome and link.
- Five useful gift lines for the project types you see most.
- Your availability sentence, updated each Monday.
With the kit ready, a strong public comment plus DM takes under ten minutes — fast enough to land in the window that matters, specific enough to survive triage.
The post you practise on has to come from somewhere, of course. Whether you find it through your own search routine or a service like ours that delivers them verified and timestamped, the reply is the part nobody can automate for you. Write it like the one person in the thread who actually read the post — because from the client’s side, that’s exactly how it looks.