How to build an intent-based outbound motion from scratch

Most outbound fails for one boring reason: it goes out to people who had no reason to hear from you today. Intent-based outbound flips that. Instead of blasting a static list, you wait for a signal — a job change, a hiring post, a product launch — and reach out while the reason is still warm.

Here's the motion, end to end.

The 5-step motion

1. Pick signals that mean something

A good signal is specific, recent, and tied to a need you solve. "Follows your company" is weak. "Posted that they're hiring three SDRs" is strong — it implies budget, timing, and a problem.

2. Qualify before you write

Not every signal is a fit. Layer your ICP on top: company size, role, region. The output of this step isn't a yes/no — it's a reason code you can put in the first line of the message.

3. Ground the opener in the signal

This is where most automation breaks: it interpolates the signal into a sentence and ships broken grammar. Don't. Map the signal to a natural, second-person line a human would actually write — and if you can't, fall back to something vague but correct rather than specific but wrong.

4. Send like a human

Volume is the enemy here. Human-paced caps, a working-hours send window, and a hard weekly ceiling keep the account healthy. A few well-aimed messages a day beat a hundred sprayed ones — and they don't get you restricted.

5. Measure replies, not sends

Sends are vanity. The only number that matters is positive replies per week. Optimize the signal and the opener; let the cap protect the channel.

The short version

Wait for a reason. Qualify against your ICP. Ground the opener in the signal. Send at human pace. Count replies. That's the whole motion — everything else is detail.