How to Build LinkedIn Outbound Campaigns Around Real Account Signals
Funding rounds, job posting clusters, and post commenters give you a first line you could not have written last week. Here is how to time and build the campaign.
What is a signal-triggered campaign?
A campaign that starts because something happened at the account, not because it is the first of the month. A company announces a Series A. A company posts six AE roles in three weeks. A VP of Engineering comments on a post about hiring. The event picks the list, sets the clock, and writes your first line.
Braze defines a trigger campaign as one that sends in direct response to a specific action or event, which is the whole mechanic. For LinkedIn outbound, a usable signal has to do three things:
If it fails the third test, you have a list, not a signal.
Which signals are actually worth building a campaign on?
Funding announcements, clustered job postings, leadership changes, and people commenting on a post about the problem you solve. These are public, dated, and specific to one account. Anonymous website visits and aggregated intent scores fail the naming test, so they generate guesses rather than opening lines.
MKT1's guide to signal-based campaigns is worth reading on which signals convert and which just create noise. The ranking that holds up in LinkedIn outbound, strongest first:
1. A person commented on a post about your problem. They raised their hand in public, an hour ago.
2. Six job postings in one function. Someone has budget and a headcount problem right now.
3. Funding announced. Money exists. Priorities are being set in the next 60 days.
4. New VP hired. They will replace tools in their first 90 days.
How fast do you have to move after a funding round?
Start inside 14 days, and expect the window to stay open for about eight weeks. The first 72 hours are crowded because every vendor with a news alert fires at once. Week two to week six is when the new VP is hired, the tool review starts, and the budget actually moves.
Here is the worked example. A 40-person B2B SaaS company announces a $12M Series A on a Tuesday. The founder posts about it. 340 people comment. That post is the richest list in the campaign, and almost nobody uses it.
What does the nine day sequence look like?
Detection on day zero, invites across days one to nine at 20 to 25 a day, first message on acceptance, two follow-ups spaced four and eleven days after that. The people who commented on the announcement post get a different first line from the people pulled from the company page.
| Day | What goes out | Why that timing |
|---|---|---|
| 0 | Signal detected, 180 contacts built from the post's commenters and the company page | The comment thread decays in about 48 hours |
| 0 to 2 | DM to everyone who commented, then a public reply on their comment | They are still watching the thread |
| 1 to 9 | 20 to 25 connection invites a day, no note | Safe volume on a warm account |
| On accept | First message, referencing the round and one specific hiring plan | Reply rate is highest within a day of accepting |
| +4 | Follow-up with one useful thing, no ask | Most people do not reply to the first message |
| +11 | Short close: a yes or no question | Last touch before the list goes cold |
Ramping a new account, drop to 5 to 10 invites a day and stretch the campaign to three weeks. The full mechanics of invite to accept to reply are in how LinkedIn outbound actually works.
What do you actually send on day one?
For a commenter, the DM references their comment and not the round. For an invite, no note, because a bare invite accepts better. The first message after acceptance names the round, names the thing they are about to hire for, and asks one question. Under 60 words.
The commenter version, as sent:
> Saw your note on Dana's Series A post. You mentioned you went through the same thing at 30 people. Curious what broke first for you, the onboarding or the ramp?
No pitch. It exists to open a thread. Gelee's Post Commenters preset does this at volume: it DMs each commenter, then posts the public reply on their comment once the DM is confirmed sent, so the public reply lands second and the DM does not read as a broadcast.
The company-page version, sent after they accept the invite:
> Congrats on the raise. Saw the three AE roles and the enablement lead. Usually the enablement hire lands two months after the AEs and everyone spends that gap building decks. Is that roughly where you are?
How many meetings should 180 invites produce?
Between 5 and 9. At a 20 to 30% accept rate, 180 invites become 36 to 54 connections. At a 12 to 18% first-message reply rate, that is 5 to 10 replies, plus another 2 to 4 from the follow-ups at 5 to 8%. Overall meeting rate on a signal list runs at the top of our 3 to 5% band.
The arithmetic on your time, if you run it yourself. Building the list from the comment thread is about two hours. Writing four message variants is an hour. Sending 25 invites a day for nine days is 15 minutes a day. Answering replies is the part that eats you: 12 threads, most running four or five messages, across three weeks. Call it 14 hours for the campaign. At $100 an hour that is $1,400 of founder time for six meetings.
Does the same thing work for a hiring surge?
Yes, and the list is easier to build because job postings are dated and public. A company posting six AE roles in three weeks is telling you their headcount plan, their timeline, and which function is under pressure. The window is longer than a funding round, roughly the 90 days the roles stay open.
Who you message changes. On a funding signal you go up: founder, VP, head of function. On a hiring surge you go sideways as well, because the hiring manager writing the job description is often the person who feels the problem and rarely the person quoted in the press release. Recruiters run the mirror image of this, messaging the people in the roles rather than the company posting them, which we covered in whether recruiters can use Gelee for candidate outreach.
What breaks these campaigns?
Detection latency and reply lag. A funding signal you notice on day 12 is a worse signal than one you notice on day 1. A reply you answer 30 hours later is a dead thread, because the reason they replied was that the round was on their mind that morning.
Common Room describes the end state as automating the journey from signal to outreach so that pipeline generates while you are away. That is the correct target, and the piece most teams never automate is the reply, not the send.
Who should not run this?
Anyone whose deal size is under $2,000, because 14 hours of work for six meetings does not clear. Anyone selling something a freshly funded company buys in year three rather than year one. And anyone who has not sent 200 cold invites yet, because you do not know which messages work.
Gelee is the wrong tool if you need the detection layer itself. It does not maintain a funding database or scrape job boards. You bring the signal and the list, from a news alert, Crunchbase, or a company page, and Gelee runs everything from the invite onward: the sequence, the replies in your voice, the objection handling, and the booking. If what you actually need is someone to tell you which accounts raised money last week, buy a data tool first.
What makes a signal campaign beat a normal one?
The opening line is true and dated, so the reply rate sits at the top of the band rather than the bottom. A generic invite to 180 CFOs and a signal-triggered invite to 180 CFOs who raised money last month cost the same to send. One of them produces three meetings and the other produces eight.
Before you run one, check the profile people land on after they accept. Roughly a third of accepted invites view your profile before replying, and a headline that does not say what you sell wastes the signal you just spent 14 hours acting on. The LinkedIn headline rewriter is free and takes two minutes. If you are a solo founder deciding whether any of this is worth your week, we worked the numbers through in is Gelee worth it for solo B2B SaaS founders.