How to ask strangers for help (and actually get it)

Key Takeaways

• Show proof of work before asking — a trained model, a blog post, or a video log beats institutional credentials
• Make requests specific and bounded; 20 minutes beats 'pick your brain'
• A pressured yes is worse than a no — make it easy to decline

Whether you're chasing funding, recruiting advisors, or landing your first job, you will have to ask strangers for help. Most people get it wrong. A blog post by Pradyu Prasad, now circulating on Hacker News, argues the fix is simple: stop thinking about yourself and start thinking about them.

Prasad's core principle fits in one line: put yourself in their mind. Every heuristic he offers flows from that. The post reads like a checklist for founders and engineers who treat cold emails the way they treat pull requests, full of technical detail but missing the human context.

Why proof of work beats credentials

People help people, not projects. Prasad ranks three ways to establish credibility, in descending order of strength.

1. Proof of work. A trained model, a thoughtful blog post, a vlog of your training. Something that took effort and demonstrates seriousness.
2. Personal connection. 'Steve suggested I reach out' warms the introduction, but you're borrowing Steve's credibility. If the recipient dislikes Steve, or you disappoint, both relationships take damage.
3. Institutional affiliation. Mentioning your university or employer proves you cleared a filter once. It's the weakest signal and can feel like status-signaling. Use sparingly.

This ordering matters. A Stanford MBA cold-emailing a startup founder carries less weight than an anonymous GitHub contributor whose code the founder has already seen. The institution tells them you passed someone else's test. The proof shows you passed your own.

Context: short enough to be unsummarizable

Once you've earned a moment of attention, spend it wisely. Prasad's rule: your description of the situation should be so short it cannot be condensed further. You are spending borrowed attention, and borrowed attention is expensive.

The trick is to connect your context to something they already know. Don't explain your university club's internal politics to a legislator. Do explain how the club's mission aligns with her current bill. Don't tell a scientist you've loved science since childhood. Do tell her you implemented and extended her 2023 paper.

This is harder than it sounds. It requires research. It requires reading their work, not just their bio. But that research is itself proof of seriousness.

Shrink the ask until it's hard to refuse

Prasad treats the request as a product problem. Lower the cost of acceptance. He suggests three tactics:

• Reduce magnitude. Twenty minutes, not a week. A single question, not a 500-page manuscript.
• Be specific. 'Can you recommend one resource on X?' beats 'Can I pick your brain?'
• Bound the commitment. Don't ask them to mentor you for life. Ask them to read one blog post. If it goes well, they'll volunteer more.

And remove friction. If you want an introduction, write the blurb they can forward. If you have a question, write it out rather than requesting a call. The less work they have to do, the more likely they are to do it.

Make it easy to say no

Here's Prasad's counterintuitive move. The worst outcome is not rejection. The worst outcome is a pressured, begrudging yes.

If you guilt someone into helping, two things happen. First, the help will be half-hearted, a minimum effort to discharge an obligation you manufactured. Second, you've poisoned the relationship. They will never help you again.

Help freely given is different. It's effortless for the giver, like holding a door open. It leaves both parties feeling good. And it can become the foundation of something longer.

So when you get a no, thank them and move on. Don't pester. Don't add emotional guilt to your follow-up. The goal is not to win a single battle. The goal is to build a reputation as someone worth helping.

The research backs this up

Prasad's heuristics align with academic findings on persuasion and social capital. Stanford professor Frank Flynn's research found that 70% of people underestimate how willing others are to help. A Boomerang study showed that cold emails demonstrating specific knowledge about the recipient had an 85% higher response rate. Ellen Langer's classic Xerox experiment found people are three times more likely to help when given any reason, even a trivial one.

The implication is clear. Most people don't ask because they expect rejection. And most rejections happen because the ask was poorly framed. Fix the framing, and the odds shift.

Frequently Asked Questions

What's the best way to cold email someone you admire?

Lead with proof of work that's relevant to them, keep the context short, and make a specific, bounded request. Don't ask for mentorship; ask for 15 minutes or a single resource recommendation.

Should I mention my school or company when reaching out?

Only if it's directly relevant. Institutional credentials are the weakest form of credibility because they only show you passed someone else's filter once. Proof of your own work is stronger.

How do I follow up without being annoying?

One polite follow-up after a week is acceptable. If there's still no response, move on. Repeated messages or guilt-tripping will damage your reputation more than silence.

What if the person says no?

Thank them for their time and don't push further. A graceful exit preserves the relationship. They may help you later, or introduce you to someone who can.

Source: Hacker News: Best