Written for the person, in the voice of your own posts.

Last updated 28 September 2026

Every message HeyLead sends is written for one person from their profile, the reason they were chosen and the voice of your own LinkedIn posts: the invitation note, the opening message, up to 2 follow-ups on Free and 5 on Pro, InMail and email as fallbacks. Opening messages and follow-ups wait for your approval until you switch to autopilot.

The four messages in a sequence

MessageWhenWhat it carries
Invitation noteWith the connection request, after a warm-up (a profile view, a follow, a comment on a recent post).One reason you are writing. A selling campaign opens with curiosity and no product name; a job-search campaign may name the company and the role; a buying campaign says you are the buyer.
Opening messageOnce the invitation is accepted, or first for a connections-only campaign.Why them and why now, from a signal when one started the outreach, one proof point, one question. Under approval until autopilot.
Follow-upsUp to 2 per person on Free and 5 on Pro, days apart, 20 to 35 minutes apart on a seat.Written from the thread so far: one new thing, a smaller question. A "not now" reply gets a check-in in 30 days instead.
InMail and emailInMail after an invitation sits unanswered for 14 days, when the seat has credits or the person is an Open Profile member; email to people whose record carries an address, once you connect a mailbox.The same brief, the same voice. InMail as a first touch is off unless you turn it on.

Where the voice comes from

HeyLead reads your own LinkedIn posts and keeps their voice: sentence length, openers, the words you use and the ones you never do. Every draft is written in the voice of your own LinkedIn posts, against that signature, and a grounding validator rejects any claim that is not in the facts of the campaign or the person's profile. Nothing is invented about them, and nothing is promised about you that your brief did not say.

What waits for you

A worked example

Brief: "A webhook debugger for Stripe that replays failed events, for payments engineers at seed-stage fintechs. I answer replies myself."

Note: "Hi Maria, your post on retries failing silently after the settlement migration is the clearest thing I have read on it. I build tooling for exactly that. Would be good to be connected."

Opener, after acceptance: "Thanks for connecting, Maria. We hit the same silent failures and built a debugger that replays every failed webhook with the original payload. Is that still an open problem for the team, or did you solve it in-house?"

Follow-up, a week later: "One more thing since I wrote: we added replay for Stripe Connect webhooks, which was the gap the last two teams asked about. Is Connect in your stack?"

Maria and the messages are an example, written the way the agents write them; the person, the post and the product are invented.

Limits, in numbers

HeyLead is not affiliated with LinkedIn. It reaches LinkedIn through Unipile, which is also not affiliated. The ceilings per plan are on LinkedIn limits explained; the message shapes are on templates; how sending is paced is on scheduling.

Start free, see your personas

Not ready to sign in? See your buyer personas first. Related: Signals · Tool reference · Pricing