1 min lesson
Don't pitch in the connection request
Pick two rows from the table in "Don't pitch in the connection request" and explain the choice each one supports.
Step 1 of 3
Don't pitch in the connection request
The connection request earns the right to message, nothing more. A pitch crammed into that 300-character note is the fastest way to get ignored or marked spam. Keep it to genuine relevance and let the reply open the door.
- Touch
- Connection request
- Job
- Earn the connection on relevance
- Tone
- Brief, human, no ask
- Touch
- First message after connect
- Job
- Open a conversation, light value
- Tone
- Conversational, one question
- Touch
- Follow-up
- Job
- Add a new angle or proof point
- Tone
- Helpful, not nagging
| Touch | Job | Tone |
|---|---|---|
| Connection request | Earn the connection on relevance | Brief, human, no ask |
| First message after connect | Open a conversation, light value | Conversational, one question |
| Follow-up | Add a new angle or proof point | Helpful, not nagging |
Each touch does one job; none of them is “close.”
Learn more
Full explanation
Every touch adds something new
Every touch adds something new
If your second message just repeats the first louder, you've taught them to ignore you. A multi-touch effort across email, LinkedIn and a call should feel like one person approaching the problem from different sides, never the same message three times.
Technical buyers research you back before they reply. They'll open your LinkedIn profile and if it's empty, off-brand or contradicts your message, your credibility evaporates. Match the engineer's register - direct, accurate, low-hype - and make sure your profile says the same thing your message does.
Connection note: “Hi Priya - saw the Go monorepo move and your backend hiring push. I work with eng teams scaling fast on Cursor and would love to connect.” No pitch, just a real reason and a clean open.