The coffee-chat script that isn't creepy

Every first-year thinks they should be doing more coffee chats. Most don’t know how to ask for them without it feeling weird. So they either never send the message, or they send the version where they end up copy-pasting a template they found on LinkedIn, and the recipient can tell.

There is a version of the coffee-chat request that works. It’s short, specific, and signals that you’ve actually thought about why you’re asking this person. It’s also not that hard to write.

The script

Here it is, for an internal colleague:

Hi [Name] —

I’m a [role] on the [team] — joined six months ago. I saw your recent [specific thing: write-up, doc, presentation, project launch], and the part about [specific detail] is something I’ve been trying to figure out for my own work.

Any chance you’d have 20 minutes in the next couple of weeks? Happy to come to you, grab coffee, or jump on a video call — whatever works. No agenda beyond asking a couple of questions about [the specific thing].

Thanks, [You]

For an external person (someone you don’t work with, who might be in a different company):

Hi [Name] —

I came across [the specific thing] and it stuck with me, especially the point about [detail]. I’ve been working on [adjacent thing I’m actually working on], and I’d love to ask a couple of questions.

Would you be up for 20 minutes in the next few weeks? Happy to come to you. I’m a [role] at [company] — not trying to sell you anything or pitch a job. Just curious about how you think about [topic].

Thanks, [You]

Both messages share the same structure. Five short paragraphs. One specific reason. One clear ask. One disclaimer when warranted. Sign off.

Why this works

You named a specific thing. The moment you reference a specific doc, post, project, or comment they made, you’ve demonstrated that you aren’t copy-pasting a template. That’s 80% of what makes this not creepy. The recipient’s instinctive read goes from “this is a form letter” to “this person actually paid attention.”

You named what you’re trying to figure out. You gave them a reason to say yes that wasn’t “I’d like to meet you.” People are much more likely to agree to a 20-minute conversation that has a concrete purpose than a vague one.

You asked for a bounded amount of time. Twenty minutes is small. “Pick your brain for an hour” is large. 20 minutes gets yeses that “grab coffee” doesn’t.

You removed the friction. “Happy to come to you” or “jump on a video call” — giving them the cheapest option for their calendar makes yes much easier.

You were honest about why. You didn’t pretend it was a two-way conversation where you have value to trade. You asked a question and said you’d be grateful.

What doesn’t work (and why)

“I’d love to pick your brain” is the most overused phrase in corporate messaging. It’s vague and it also implies you’re the one getting value and they’re the one giving it up. Replace with specifics: “I’d love to ask about how you structured the Q2 rollout.”

“I’d love to hear about your career journey.” Nobody wants to give you their whole career story. If you’re interested in their career, ask one question about one part of it: “how did you end up on [X] team — was that an internal move?” That’s a manageable question. The full journey isn’t.

Flattery openers. “I’ve been a huge fan of your work” lands as pandering unless backed by specifics. If you genuinely respect someone’s work, say what specifically about it affected your thinking. That’s the version that reads as sincere.

Long explanations of yourself. A three-paragraph autobiography about why you’re qualified to deserve 20 minutes of their time is the opposite of what convinces them to say yes. Two lines — your role, how you found them — is the whole intro.

“Let me know when works for you.” Open-ended scheduling from a stranger is a lot to ask. Propose two or three specific windows: “Would Tuesday afternoon or Thursday morning work?” Easier to decline one than to generate one.

Asking for a job or a referral in the first message. The coffee chat is not a job ask. Leading with one kills it. If the chat goes well, you can, much later, mention you’re looking — but that’s not what the request is for.

What to actually do in the 20 minutes

You asked for it. Run it well.

Come with two or three questions, written down. Not twenty. Two or three that are worth the meeting. When in doubt: one specific question about their current work, one question about a decision or tradeoff they made that interested you, one open-ended “anything I’m not asking that I should be?”

Talk less than half the time. A well-run coffee chat is about 25/75 — you talking 25% of the time, them talking 75%. Your role is to ask good questions and listen. If you feel the meeting becoming about you, you’re doing it wrong.

Take notes visibly. It signals respect and helps you remember. “Mind if I jot a couple of things down?” is always fine.

Don’t ask for something at the end. Don’t ask them to introduce you to anyone. Don’t ask them to look at your resume. Don’t ask them to review a project. The meeting is the thing. Extracting more from the meeting cheapens it.

Leave one minute early. Twenty-minute meetings should run 19 minutes. Respecting the clock is a senior signal.

The follow-up note

24 hours later, send a short thank-you. Three lines:

Thanks again for the time yesterday — the specific thing about [detail] has already changed how I’m thinking about [my thing]. I’ll let you know how [next step] goes.

Also wanted to share [one small thing: an article, a tool, a thought] in case useful.

[You]

The “in case useful” line is the reciprocity move. You can’t match them 1-for-1 on experience, but you can share something they’d plausibly find interesting. Even a short article or a tool recommendation. It changes the feel of the relationship from “they did me a favor” to “we had a useful conversation.”

If it doesn’t apply — you have nothing relevant to share — cut that line. Don’t force it.

The medium-term follow-up

Most coffee-chat relationships die in the follow-up. You did the meeting, you sent the thank-you, and then you lost touch. Next thing you know, it’s a year later and the relationship has cooled.

The fix: circle back once, casually, six to eight weeks later with an update. One sentence about how their advice played out, or what you ended up doing. No ask. Just an update.

Hi [Name] — quick update from the conversation a couple of months ago. Ended up doing [X]. Wanted to close the loop since your framing really shaped the approach. Appreciate it.

That update turns a one-off meeting into a relationship. Two or three coffee chats run this way over a year is enough to build a small network that compounds.

Edge cases

• If the person is famously busy (senior leader, public figure): shorten further. Three lines. Specific. Ask for 15 minutes, not 20.
• If the person is your skip-level or a senior manager in your chain: go through your manager first. Not for permission, for context. “I was thinking of asking Deborah for a 20-minute chat about the renewals strategy — any heads-up I should have?” Your manager will often not only be fine with it but will help set it up. Going around your manager to a leader in your chain rarely goes well.
• If you’ve sent the message and been ghosted: wait four weeks, send one short “Hi, bumping this in case it got buried — totally understand if the timing isn’t right.” Then drop it. Two attempts max. Beyond that it’s creepy.

Do this today

Identify one person — internal or external — you’d genuinely like to learn from. Write the message above, adapted to them. Send it before the end of the week. Don’t overthink the phrasing. The specifics about why you chose them do more work than the polish does.

For the adjacent “do I have to network at this conference” question, see the Reader Q on networking at industry events. For the weekly status rhythm that gives you things worth bringing to a coffee chat, see the status update template.