What lands in an engineering manager's inbox
An engineering manager spends the day in standup, code review, hiring loops and the occasional incident. The message that gets answered is the one that reads like a colleague's note, not a pitch. Your email competes with a build failure and three recruiter templates, so the first line has to say what this is and why it cost them thirty seconds to open.
Their time has a price, and it helps to know it. The U.S. Bureau of Labor Statistics puts median annual pay for architectural and engineering managers at $171,270, which is about $82.34 an hour. Fifteen minutes of that is roughly $20.59. Nobody does this arithmetic at their desk, but it explains why a vague request for half an hour gets filed under later.
Whatever channel you pick, email, LinkedIn or a paid message, the same three things decide the outcome: whether the reason you chose them is specific and true, whether the ask fits into a reply they can type, and whether they can answer without opening a calendar.
Before you write
Decide what you actually want before you write a line. Most asks fall into four buckets: a quick question, a considered reply, a review or short call, or an hour of advice. Each costs the reader something different, and mixing them, such as burying one specific question inside an invitation to a half-hour call, is the most common reason a note stalls.
Spend ten minutes on them and only them. What does the team ship? What does the job posting ask for? Is there a talk, a post, a commit, a changelog entry you can name? You need one true detail that proves this note was not pasted into forty composer windows. If you cannot find one, you do not have a reason yet, and the message will read that way.
Then write the ask as one sentence in plain words. "Would you look at the two options below and tell me which you would choose?" is an ask. "Would love to connect and learn from your experience" is not, because the reader cannot tell what they are agreeing to do.
What to say in the first message
The shape that works is short and plain. One line on who you are and what you are working on. One line on why you picked this manager, using the detail you found. One to three questions. The time the ask takes. Your name. That is the whole message.
Weak: three sentences about your background and a closing line about being open to a conversation. Strong: "Your posting for a platform engineer mentions a migration off the old scheduler. I am planning the same move for a team of eleven. What made you choose the order you did?" The strong version is answerable from memory in a few sentences.
Boomerang's analysis of more than 40 million emails found that messages between 50 and 125 words got the most replies, that one to three direct questions did better than none, and that plain writing did better than formal, college-level prose. Read your draft aloud. If you would not say a sentence to a colleague in a hallway, cut it or rewrite it.
Close with the cost. "A 15-minute reply is plenty" tells them what they are agreeing to. "A two-line answer works if that is all you have" gives them a small exit that still gets you something. Both beat a message where the ask could be five minutes or five hours.
How to follow up
Send one follow-up, about a week after the first, and make it carry something new. A result, a narrowed question, a decision you made since. A note that only says you are checking in gives the reader nothing to reply to and confirms the first message was low effort.
Keep it shorter than the original and repeat the ask in one line, because they probably read the first message on a phone between meetings. Restate the time cost. If they answered part of it, thank them and ask only what is left.
Then stop. Two messages is a fair limit for someone who has never replied; a third rarely changes the answer and costs you the option of writing again in six months. If they say no, or say now is not the time, take it at face value and leave the door open in one sentence.
When a paid message makes sense
A paid message is worth considering when your ask has a defined time cost and you want to give the person a reason to spend that time. On Introworth, members set a price for messages from people they do not know. Your card is held rather than charged, and payment is captured only if they reply within the reply window; if they do not, the hold is released. The recipient keeps 85% of the price, and Introworth's commission is 15%.
Prices map to time. Introworth's lowest price is $15, which lines up with the roughly $6.86 that five minutes costs at median pay for the role. The suggested price for a 15-minute considered reply is $25, against about $20.59 of their time. Thirty minutes is suggested at $50, against $41.17. An hour of advice is suggested at $100, against $82.34. The gap is deliberate: you are paying for the interruption, not only the minutes.
Use it when you want a considered reply rather than a yes to a call, and when the question is small enough to answer without research. Do not use it to send a longer version of a weak message. The message coach checks drafts privately before you pay, looking at length, questions, why them, the time asked for and plain wording. A warm introduction is the other route: a member can ask a mutual connection to forward the note, and the person accepts, which makes it a free conversation, or passes. Connections message each other with no per-message fee.
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.