Sales & Outreach

Verified against ChatGPT · 2026-08-08

Write a LinkedIn connection request note that earns acceptance without pretending to already know someone

Drafts a short LinkedIn connection request message within the character limit that gives a real, honest reason to connect instead of a vague networking platitude or a disguised pitch that gets read as spam.

ChatGPT (GPT-5.1)4 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

Write me a LinkedIn connection request note. This has a hard character limit and one job: give this person a genuine, honest reason to accept — not a disguised sales pitch and not empty networking language.

WHO I'M CONNECTING WITH
Head of Sales Ops at a company you've been researching as a target account.

MY ACTUAL REASON FOR CONNECTING
I think their team is a strong fit for what we sell and I want to build familiarity before reaching out with anything specific.

ANY SHARED CONTEXT (MUTUAL CONNECTION, GROUP, EVENT)
We're both members of the same 400-person RevOps Slack community and she posted a question I could genuinely speak to.

AM I PLANNING TO PITCH THEM SOON AFTER CONNECTING?
Yes, planning to reach out with a specific offer within 2-3 weeks after connecting.

Write this as a genuinely honest note, not a soft-sell disguised as a networking message — if my real reason for connecting is that I want to sell them something eventually, say something true and non-manipulative rather than pretending this is purely about admiring their work or wanting to "add value." Use the shared context only if it's real and specific enough that they'd recognize it, never a vague "we're both in the same industry" line that could apply to thousands of people. Keep it under 300 characters, since that's LinkedIn's connection note limit, and write it as something a real person would type, not a template with the name swapped in. If I indicated I plan to pitch soon after connecting, do not make a promise in this note about not selling to them ("just want to connect, no pitch!") if that isn't true — a note that lies about intent to get past the first hurdle damages trust the moment the pitch actually arrives. Do not use "I'd love to add you to my network" or "great profile" as the entire content of the message.

Output: the note text with a character count shown, plus one line noting if the stated reason and the stated future pitch intent are consistent with each other or if there's a mismatch I should reconsider.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

The instruction to be honest about pitch intent rather than promising "no pitch" if a pitch is actually planned is the mechanism that keeps this prompt from producing the single most common form of LinkedIn spam: a connection note that explicitly disclaims sales intent, immediately followed by a pitch, which is a pattern experienced LinkedIn users recognize instantly and which damages trust more than an honest, upfront reason ever would — a model asked simply to write a "friendly, non-salesy" connection note will often default to exactly that false disclaimer because it's a common, socially safe-sounding phrase in its training data for this context, regardless of whether it's actually true for this specific outreach. Requiring the shared context to be specific enough that the recipient would recognize it themselves, rather than a generic "we're in the same industry" line, targets the second most common failure: connection notes that gesture at commonality without establishing anything concrete, which reads as templated regardless of how warmly it's phrased, because there's no way to verify the claim is really about this specific person. The hard 300-character constraint matters mechanically because LinkedIn's connection note field actually enforces that limit — a model not explicitly told the constraint will draft a warm, well-reasoned message well over the limit that would get silently truncated or rejected, so the length rule isn't a stylistic preference here, it's a platform mechanical requirement. Flagging a mismatch between the stated real reason and the stated pitch intent gives the user an explicit checkpoint to catch their own inconsistency before sending — if the honest reason given doesn't actually match what's about to happen next, that's worth surfacing before the note goes out, not after the relationship starts on a note that won't hold up.

What you get back

"Hi Maria — saw your question in the RevOps Slack about attribution gaps in multi-touch pipelines, and it's close to a problem I spend a lot of time on. Would like to connect and stay in each other's orbit — I do also work in this space commercially, so full disclosure there, but no pitch in this note." (287 characters) — Consistent: your stated intent to pitch within a few weeks is disclosed honestly rather than denied, so this note should hold up when that follow-up arrives.

Verified against

ChatGPT GPT-5.1 · 2026-08-08

Changelog

  • 2026-08-08 — Initial publish, verified against ChatGPT GPT-5.1.

Need this built into your business?

If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.

EXPLORE GOOGLE ADS MANAGEMENT
All Sales & Outreach prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY