Everyone recognizes it instantly: “I would like to add you to my professional network.” LinkedIn’s default connection note reads like it was generated by a form, because it was — literally, it’s the platform’s placeholder text, and a large share of the people using it never edited it at all. But even when someone does write their own version, non-native speakers often produce something that lands in the same uncanny territory: technically correct English that no one would actually say out loud.
The tell isn’t grammar. It’s usually one of three things: a formal register borrowed from business-letter conventions (“I am writing to you in order to…”), a literal translation of a polite phrase that doesn’t have an English equivalent (“I would be honored if you would kindly accept…”), or a request with no specific reason attached to it — just a generic gesture at “networking.” English-speaking professionals write connection notes the way they’d write a text to a work acquaintance: short, specific, low-ceremony. The fix isn’t more politeness. It’s more specificity.
Here’s what to write instead, for the four situations you’ll actually hit.
After you meet someone at an event
The mistake here is writing a note that could apply to anyone you’ve ever met, when you have the one thing a cold message never has: a shared, specific moment. Use it.
Good to meet you at the SaaStr panel today — I really liked your point about pricing pages doing too much explaining and not enough deciding. Would love to stay in touch.
Notice it doesn’t say “it was a pleasure meeting you” (true, but empty) or restate your job title (they don’t need it — they were just standing next to you). One concrete detail from the conversation does more work than three sentences of politeness. If you didn’t get much of a real exchange — just a badge-scan or a quick handshake — it’s fine to be more modest:
We crossed paths at the Copynote booth at SaaStr — wanted to connect since we’re both in the ESL-tooling space.
Reaching cold into a company you want to work at
This is the one where translated formality shows up hardest, because it’s the highest-stakes version and people compensate by adding ceremony. Drop it. The person reading this gets dozens of these; what earns a reply is showing you did five minutes of homework, not that you’re being deferential.
Hi Daniela — I’ve been following [Company]‘s move into the EU market and noticed your team is building out the localization function. I lead a similar effort at [Your Company] and would like to connect and hear how you’re approaching it.
Compare that to the translated-formal version many non-native speakers reach for by default:
Dear Ms. Rossi, I would like to request the honor of connecting with you, as I am very interested in your esteemed company and would appreciate any opportunity to learn from your valuable experience.
The second one isn’t wrong, exactly — it’s just addressed to nobody in particular. “Esteemed company” and “valuable experience” are phrases that exist in formal correspondence in a lot of languages but read as stiff, almost sarcastic, in English business contexts. If you’re reaching out because you want a job, name it plainly rather than circling it:
I’m exploring a move into [role type] and [Company] is on my short list — would value 15 minutes to hear what the team’s actually working on right now.
Reconnecting with an old colleague
The instinct is to over-explain the gap: why you haven’t talked in three years, why you’re reaching out now. Skip the justification. People don’t need a reason to hear from someone they used to work with — the shared history is the reason.
Hey Marcus — it’s been way too long since [Old Company]. Saw you moved into product at [New Company], congrats. Would be great to catch up sometime.
If there’s a real reason behind the reconnection — you need advice, you’re hiring, you saw something they posted — say that instead of dressing it up as pure nostalgia. People can tell the difference, and a real reason is more welcome, not less:
Hey Marcus — saw your post about the migration you just ran. I’m about to do something similar and would love to pick your brain for 20 minutes if you have time.
Following up on a mutual connection’s intro
Here the job of the note is to make the intro easy to say yes to, which means naming the person who connected you and giving a one-line reason before they even open your profile.
Hi Wei — Priya mentioned we should connect given we’re both building in the developer-tools space. Sending a note ahead of a proper intro.
If the mutual connection already sent a double opt-in intro email, your LinkedIn note can be even shorter — it’s just confirming you saw it, not re-pitching yourself:
Hi Wei — following up on Priya’s intro. Looking forward to connecting.
The rule underneath all four
Every version above follows the same shape: name something specific (the event, the company move, the shared history, the mutual contact), then say plainly what you want (to stay in touch, to hear how they approach something, to catch up, to connect). No throat-clearing, no “I hope this message finds you well,” no stacked politeness. That structure is what native-sounding professional English actually rewards — not formality, specificity.
If you’re drafting these in your head in your first language before translating, that’s usually where the stiffness creeps in — formal registers travel across languages more literally than casual ones do. Copynote’s tone presets exist for exactly this gap: you write the note the way it comes naturally, pick “direct” or “warm,” and it comes back sounding like something a colleague would actually send, not a template neither of you would recognize.
