How to ask a stranger for help — and why 100 handwritten notes got zero replies
Pradyu Prasad's rule is one line: put yourself in the other person's mind. The corollary, learned the hard way by a reader in the thread, is that effort you pour in to look sincere can be the exact thing that buries your ask.
His five moves: prove your work (credentials are the weakest signal), give only the context that matters to them, make saying yes cheap and specific, make saying no easy, and never deceive. Genuine help, he argues, should feel effortless — like holding a door.
The thread's best counter came from someone who ran the experiment. First attempt: 100 painstaking handwritten notes, not a single reply. Second: a few-sentence email with one clear ask — a 15% response rate and real conversations. Less work, more help. Someone on the receiving end of ten requests a week explained why.
The five moves, and the one non-negotiable
Pradyu Prasad's essay treats asking strangers for help as a learnable skill rather than a personality trait, and hangs everything on one instruction: put yourself in their mind. From there, five heuristics. Establish credibility, primarily through proof of work — projects, writing, results — with institutional credentials treated as the weakest signal. Give only relevant context, keeping the ask "so short as to be unsummarizable," because attention is borrowed currency. Minimize the cost of yes: make it specific and bounded — ask for 20 minutes, not a week. Make it easy to refuse, because a pressured, begrudging yes is worse than a no: "A person who helps you with gritted teeth is one who will never help you again." And the one rule with no exceptions: never deceive.
The thread ran the A/B test on itself
The sharpest contribution was an experiment where more effort performed worse:
"The first time I put so much time into handwriting notes and trying to provide my relatable background. 100 notes, not a single response. The second time I sent emails that were a few sentences. I had a much clearer ask… 15% response rate and invaluable conversations. Less overall "work"." — a developer and app founder who ran both versions
From the other side of the inbox, someone who fields the requests confirmed why proof of work beats performance of effort:
"When you get 10 requests for help every week you get very good at being able to tell who has been putting in the work and who thought they could appear like a serious person by putting on a little show… The easiest way to blow it is to ask for someone's help, then ignore it or fail to follow through." — a long-tenured HN member on the receiving end of \~10 asks a week
And a founder-coach added the correction most over-thinkers need:
"your own personal estimation in how willing some group of people is to help is regularly off by several orders of magnitude… Until you get a good baseline figure of how competitive your request for help is, everything else is pre-mature optimization." — a three-time founder who now coaches founders
Put the essay and the thread together and the lesson inverts the instinct: the elaborate, heartfelt, over-prepared ask isn't generous, it's expensive — it makes the reader do the work of finding your actual request. The version that respects their time is the one that gets answered.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
Scott Aaronson and Cynthia Dwork warn: a new order tells the Census to protect privacy like it's 1975
A June directive orders the Census Bureau and BEA to drop modern disclosure methods and revert to 1970s coarsening and suppression — banning the 'noise infusion' that was slated for the 2030 count. The signatories say the old way protects no one.