What lands in a web developer's inbox
A web developer's inbox is mostly project noise. Recruiters who never name the stack, agencies pitching a redesign, strangers asking for a free review of an entire repository. Email competes with tickets, pull requests and chat, so it gets read in batches, often late.
It helps to know that most cold messages to developers are one of two things: someone hiring, or someone who wants to collaborate on research, a side project, writing or open source. Say which one you are in the first line. A developer reading your message should not have to guess whether you want to hire them, join them or sell to them.
The third thing worth understanding is that their time has a price, and they know it. Median pay for web developers is $44.54 an hour, which makes a considered 15-minute reply about $11.14 of someone's working day. That is why an open-ended request to pick their brain reads less like a compliment and more like an invoice you are handing them.
Good messages survive all three conditions. They are short enough to read between tasks, they state the ask plainly, and they take less time than the recipient expects to give.
Before you write
Decide what you actually want before you open the compose window. A hiring conversation, a collaborator on an open-source project, a second opinion on an architecture choice — these are different messages with different asks. Write your ask as one sentence on a sticky note. If it takes two sentences, it is two asks.
Then spend five minutes looking at something they made. A repository, a package, a conference talk, a written post. You are looking for one detail you can name that is not their job title or their employer. "You build websites" is not a reason. "Your write-up on handling form validation without a library" is.
Next, price the ask in time. A quick question is roughly five minutes, a considered reply fifteen, a review or short call thirty, an hour of advice sixty. At median pay that is $3.71, $11.14, $22.27 and $44.54 of their time. You do not have to pay it, but you should know the number, because it tells you whether your request is small or rude.
Finally, write the subject line first, under 70 characters. If you cannot fit it, you do not yet know what you are asking.
What to say in the first message
Boomerang's analysis of more than 40 million emails found three things that matter here: messages of 50 to 125 words got the most replies, one to three direct questions did better than none, and plain writing beat formal, college-level prose. That is the whole shape of a good first message.
Fill it in this order. One line on who you are. One or two lines on why you are writing to this specific person, with a detail only they would recognize. The ask, with the time it takes attached. One to three questions they can answer from memory. Then stop.
Compare two openings. Weak: "I came across your profile and would love to pick your brain about our stack." That asks for unlimited time and gives no reason. Strong: "Your post on [topic] is the clearest explanation of [problem] I have found. We are choosing between two approaches to [specific thing] and I would value your read on it."
Do not attach a long brief in the first message. Do not ask to jump on a call without saying what the call is about and how long it runs. If you want a call, offer two specific windows and let them pick.
How to follow up
Send one follow-up, about a week later, in the same thread. Reply to your own message so the context travels with it. Most people who meant to answer and did not will appreciate the nudge more than you expect.
Add something small rather than repeating yourself. A narrower question, a result you got since, a link that is actually relevant. "Just bumping this" gives them nothing new to react to. A follow-up that says "we ruled out the first option because of [reason], so the question now is [narrower question]" is easy to answer.
Two follow-ups is the ceiling. If the second one lands in silence, treat it as a no and move on. Chasing a third time costs you more reputation than the reply is worth.
If they say not now, ask one question: when should I come back? A date turns a dead end into a scheduled conversation, and it takes them five seconds to answer.
When a paid message makes sense
Paid messages make sense in one situation: you want a stranger's time, you have no shared context, and the ask is specific enough to be worth paying for. If a mutual contact can introduce you, do that instead. It is free and it carries more weight.
On Introworth, members set a price for messages from people they do not know. Your card is held, not charged, and the payment is captured only if the recipient replies inside the reply window; if they do not, the hold is released. Recipients keep 85%, Introworth's commission is 15%, and the lowest price is $15. A 15-minute reply at median pay is about $11.14 of their time, so the suggested $15 sits close to cost. You are paying for attention, not for an answer you are owed.
The same discipline applies on paid channels. A message coach checks the draft before you pay: length, the number and shape of your questions, whether you gave a reason it is them, the time you are asking for, and whether the wording is plain. Paying does not fix a vague message. It just makes the vague message expensive.
Connections on Introworth message each other with no per-message fee, and a member can ask a mutual connection to forward an introduction with a note. Use the free routes where they exist. Save the paid route for the person you genuinely cannot reach any other way.
Pay figures come from the U.S. Bureau of Labor Statistics and are computed by Introworth's price calculator. The guide text is drafted with AI from those figures and Introworth's product rules, and checked automatically before it is published. It is general guidance, not legal, tax or financial advice.