What is signal stacking in outbound?

It means requiring more than one dated reason before an account gets your best sequence. A fresh funding round on its own is weak. A funding round plus an open sales role plus a new leader in seat is a much stronger case for writing this week, because each signal narrows the list and gives you more to say.

How many signals should I stack?

Two or three. With more, your list shrinks to a handful of accounts and the build gets slow. A practical shape is two weak signals that qualify the account and one strong, dated trigger that decides when you write.

Does stacking signals improve reply rates?

I have not run a controlled comparison and would not claim it does on my numbers. The way to find out is to split one list into single-signal and stacked tiers, send the same offer, and compare positive replies and meetings held per account contacted.

Which signals are weak and which are strong?

Treat a signal as strong if it is dated, hard to fake and implies a near-term need, such as a role open for 30 or more days or a new VP of Sales. Treat it as weak if it describes the account but not the moment, such as a detected tool or a growing headcount.

Signal stacking: two weak signals plus one strong trigger

Signal stacking means holding back your best sequence until an account has more than one dated reason to hear from you: two weak signals that qualify it, and one strong trigger that says write now. It shrinks the list and sharpens the first line.

I want to be clear about what this post is. It is a method with a scoring rule and a way to test it. It is not a report that stacking beat single signals for me, because I have not run that comparison cleanly.

Why does a single signal fall short?

Because one signal often fits a lot of accounts that will never buy. A funding round tells you there is budget. It does not tell you anyone is looking at your category. I wrote that down in funding announcements as an outbound signal: a round alone is a weak reason to email, and it works better paired with something that shows need.

The same is true of an open role. A company hiring an SDR might be replacing a leaver or building from scratch, as I covered in job postings as a buying signal. The posting is more meaningful when something else points the same way.

What counts as weak, and what counts as strong?

My three tests from 11 buying signals worth building still apply: you can detect it reliably, it carries a date, and it changes the first line. Past that, I sort signals by whether they describe the account or the moment.

Weak: describes the account	Strong: describes the moment
Headcount growing over six months	Role open 30+ days, or reposted
Detected tech stack	New VP or C-level in seat
Hiring in a particular metro	Funding announced in the last few weeks
Company matches an ICP tier	Job ad names a tool you replace or complement

Weak signals are cheap and broad. Strong ones are dated and fade fast, so they are the trigger.

How do I stack them?

Use a simple points rule, kept in a column in your table, in the same spirit as how I classify an ICP:

Gate on fit. If the account is outside your ICP, it scores zero whatever else is true.
One point per weak signal, up to two.
Three points for a strong trigger, only if it is within its freshness window (a few weeks for funding or a new leader, 30 days or more of age for a stale role).
Send rule: an account enters the top sequence only with a strong trigger plus at least one weak signal. Strong trigger alone goes to a lighter sequence. Weak signals alone wait.

That keeps the trigger in charge of timing, and the weak signals in charge of relevance.

What does it look like on a real account?

Imagine a US software company of 80 people. Headcount is up over six months (weak), it uses a CRM that your offer works alongside (weak), and it posted a head of sales role three weeks ago (strong). That is two weak and one strong, so it goes to the top sequence.

The first line can use all of it without sounding like a list: the open role is the hook, and the other facts shape the one useful thing you say. Write the line from table facts only, using the rules in AI first lines that don't sound like AI.

This is an illustration, not a client case.

How do I find out if stacking is worth it for me?

Test it. Do not trust a vendor's before-and-after, and do not trust my intuition either.

Build one list from a single source and score every account with the rule above.
Split it into three tiers: stacked (strong plus weak), strong only, weak only.
Send the same offer to all three, with first lines written from each account's own facts.
Compare positive replies and meetings held per account contacted, not per email.
Check the stacked tier has enough accounts to read. If it has twenty, the result is noise.

What you learn also depends on a clean definition of a positive reply, decided before you send. My own principle on reading results by segment is in the outbound numbers nobody shows you.

Is there a proof point?

My own campaigns give context but not proof. One campaign of 13,708 contacts produced 202 replies, 107 of them positive, and 75 meetings that happened. I did not design or run that campaign as a stacking experiment, so I will not attribute that result to stacking. If you want a signal-versus-no-signal answer, the split test above is how you get it.

Where this advice stops working

Stacking shrinks your list, and sometimes by too much. If your market is small, requiring a strong trigger plus a weak signal can leave you with a few dozen accounts a month, and the right move may be to relax the rule. Signals also go stale quickly, so rescore before every send.

It is also only as good as the detection. A weak signal read wrongly, such as a headcount figure that is out of date, adds a point it should not. Spot-check twenty rows before trusting the score.

For the signals themselves, start with funding and job postings. I'm Malik, and more about how I work is on the about page.