---
title: "Discussion on \"What I Learned Sending 324 DMs to People Who Asked for Help in Public\" | Hashnode"
description: "Discussion on \"What I Learned Sending 324 DMs to People Who Asked for Help in Public\". Since May I've sent 324 DMs to people who asked for help in public. What the replies taught me, and the filter bug I had to catch."
url: "https://hashnode.com/posts/what-i-learned-sending-324-dms-to-people-who-asked-for-help-in-public/6afa3d5a502bb5b5013899f3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [What I Learned Sending 324 DMs to People Who Asked for Help in Public](https://mariusstiuriuc.hashnode.dev/what-i-learned-sending-324-dms-to-people-who-asked-for-help-in-public?utm_source=hashnode&utm_medium=feed)

Since May I've sent 324 DMs to people who asked for help in public. What the replies taught me, and the filter bug I had to catch.

2d ago · 5 min read · mariusstiuriuc.hashnode.dev  
Read the article

-   [#freelancing](https://hashnode.com/tag/freelancing)
-   [#sales](https://hashnode.com/tag/sales)
-   [#marketing](https://hashnode.com/tag/marketing)
-   [#clients](https://hashnode.com/tag/clients)

## Written by

[Marius Stiuriuc](https://hashnode.com/@mariusstiuriuc)

@mariusstiuriuc

  
[View profile](https://hashnode.com/@mariusstiuriuc)

Building EvenLeads, solo, from Romania

## Responses 2

Markdown supported · ⌘↵ to post

[Charlie from xSquads](https://hashnode.com/@charlie-xsq)

[1d ago](https://hashnode.com/posts/what-i-learned-sending-324-dms-to-people-who-asked-for-help-in-public/6afa3d5a502bb5b5013899f3/comment/6afc2a98a8fc14e8eed29c1a)

Useful distinction between reply rate and actual buyer-fit. One lightweight QA loop that might catch the reversed filter sooner: each week, randomly sample 10 accepted and 10 rejected posts, have a human label “buyer / seller / unclear” without seeing the model score, then compare precision on each side. Keep examples of false positives and false negatives in a small regression set and rerun it whenever the prompt changes. For freshness, log post age at discovery and at outreach, and compare response rates by age band rather than mixing them. That makes it easier to see whether targeting or timing is the real issue. The “same day, not same minute” rule is a good human-signal check too.

[Marius Stiuriuc](https://hashnode.com/@mariusstiuriuc)

[12h ago](https://hashnode.com/posts/what-i-learned-sending-324-dms-to-people-who-asked-for-help-in-public/6afa3d5a502bb5b5013899f3/comment/6afc2a98a8fc14e8eed29c1a#reply-6afce375c5e8adef796a7a08)

the blind 10 + 10 sample every week is a good one, would've caught the reversed filter way sooner than i did. splitting reply rate by post age instead of lumping it all together is going on the list too, thanks
