> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://gtm-tools.sh/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://gtm-tools.sh/_mcp/server.

# Outbound

> Outbound as a proper acquisition channel: signal-keyed timing (right time), persona resolution by signal (right person), signal-driven angles (right message). How the three levers compound, channel economics vs. paid + content, hygiene rules that actually matter, and how the outbound-sales skill operationalizes the whole pipeline.

Outbound is the most misunderstood B2B acquisition channel. The default version (buy a list, write a generic intro, blast it through Apollo, refine the subject line) has reply rates under 1% and burns sender reputation faster than it produces meetings. That version is what gives outbound a bad name.

The version that works runs on the same thesis as any high-conversion channel: **the right message reaches the right person at the right time.** Each of those three is a lever. Get one wrong and the math collapses. Get all three right and outbound becomes the cheapest qualified-meeting channel a B2B company has: significantly cheaper than paid, and faster than content.

This guide is about the channel. For the operational pipeline that drafts your outreach end-to-end, install the [`outbound-sales` skill](/skills/outbound-sales); that's the agent that does the job.

## The thesis: three levers, multiplicative

Most "outbound improvement" advice picks one lever and optimizes it. Better subject lines (message). Better list segmentation (person). Better sequencing (time). The actual lift comes from working all three together, because their effects multiply:

| Lever             | Strong version                                                                             | Weak version                                                          | Reply-rate effect |
| ----------------- | ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------- | ----------------- |
| **Right time**    | A buying-intent signal just fired on the account (hiring, churn, growth, tech-stack match) | Generic "we noticed your company" intro with no timing trigger        | \~5–15×           |
| **Right person**  | Decision-maker with budget, in the function the signal implies                             | Anyone with a title that contains "VP"                                | \~2–4×            |
| **Right message** | The message angle IS the signal that fired ("Saw the SDR role got re-listed")              | Same template you sent to 200 others, with `<firstName>` substitution | \~3–6×            |

The arithmetic, conservatively: 5× × 2× × 3× = **30× reply rate** vs. spray-and-pray. That's the difference between 0.5% (delete) and 15% (qualified pipeline). Same channel, same volume, same product. Different system.

The three levers map to three concrete inputs:

* **Right time** = a [signal](/signals-tools) is firing on the domain *now*. Signals are the timing trigger. If no signal fires, the account isn't urgent, so deprioritize it.
* **Right person** = the title to target depends on which signal fired. Hiring SDRs → VP Sales. Negative support reviews → VP CX. Social spike → VP Marketing. Each signal has its own ICP persona.
* **Right message** = the signal that fired also tells you the angle. "Hiring 3 SDRs" → talk about SDR ramp. "Negative Trustpilot support reviews" → talk about ticket resolution. The hook is never generic; it's always the specific reason you're reaching out *today*.

## How signals work as the channel's qualification gate

[Signal detection](/signals-tools) answers two questions at once:

1. **Is this account worth reaching out to *right now*?** (timing)
2. **What specifically do I lead with?** (messaging)

The signals our API surfaces, mapped to the implied pain:

| Signal                                       | Implies                                              | Best angle for                    |
| -------------------------------------------- | ---------------------------------------------------- | --------------------------------- |
| `signal_hiring_sales_rep_repost`             | SDR churned, hiring again                            | SDR ramp / enablement tooling     |
| `signal_trustpilot_negative_support_reviews` | Ticket volume outpaced CX team                       | CX tooling, response-time SLAs    |
| `signal_hiring_support`                      | Scaling CX team                                      | Onboarding / training, deflection |
| `signal_socials_spike`                       | Marketing momentum; operational backbone breaks next | CX, fulfillment, scale-prep       |
| `signal_hiring_sales_leadership`             | Sales motion being rebuilt                           | GTM stack consolidation, training |
| `signal_technologies_identified`             | Tech-stack qualification                             | Migration / integration plays     |

The full mapping (with title filters per signal and the hook structure) is bundled with the [`outbound-sales` skill](/skills/outbound-sales) in `references/signal-to-angle.md`. Run signals **first**, before any people-lookup spend. It's the single biggest credit-savings lever, and the single biggest reply-rate lever.

## The pipeline (channel view)

```
target accounts
   ↓
[detect_signal]            ← Stage 1: qualification gate (free dispatcher)
   ↓ keep only firing-signal accounts
[map signal → angle]       ← Stage 2: which signal fired = which message + which title
   ↓
[find the right person]    ← Stage 3: LinkedIn lookup with title filters
   ↓
[verify the email]         ← Stage 4: SMTP-verified, catch-all flagged
   ↓
[draft email + DM]         ← Stage 5: multi-channel, both keyed to signal
   ↓
[handoff to your platform] ← Stage 6: structured drafts → Apollo / Outreach / Salesloft / Lemlist / Smartlead
```

Two design choices in this pipeline matter at the channel level:

1. **The skill drafts; your platform sends.** B2B teams already pay for an outreach platform (Apollo, Outreach, Salesloft, Lemlist, Smartlead, Instantly, internal CRM). Replacing that surface is hostile to existing workflows. So `outbound-sales` returns structured drafts (`email_subject`, `email_body`, `linkedin_dm`, `signals_fired`, `primary_signal`, `angle`, `ready_to_send: true`) per lead, ready to paste into whatever you already use. The channel responsibility splits cleanly: research + drafting in `outbound-sales`; sequencing + send + tracking in your platform.

2. **Multi-channel from the same angle.** Email and LinkedIn DM both go out keyed to the same signal, but with different registers (email ≤90 words, formal; DM ≤60 words, conversational). Sending only one channel under-uses the signal; sending the same copy on both is a tell that gets flagged. The skill produces a matched pair per lead.

## Channel economics

A single qualified prospect end-to-end:

| Step                                                  | gtm-tools cost            |
| ----------------------------------------------------- | ------------------------- |
| `detect_signal` (5 detectors fire)                    | 25 credits                |
| `get_linkedin_company_url`                            | 2 credits                 |
| `list_linkedin_company_employees` (with title filter) | 30 credits                |
| `get_email` × 3 candidates                            | 15 credits                |
| (optional) `list_user_posts` for personalization      | 5 credits                 |
| **Total per prospect**                                | **\~75 credits = \$0.75** |

At a reply rate of 10–15% on signal-keyed outbound (vs. \<1% generic), that's **\$5–\$7.50 per reply**. Add your outreach platform's per-seat license and your SDR's draft-review time, and a qualified meeting lands in the \$40–\$80 range. That's a fraction of the paid-meeting cost for any B2B SaaS at any reasonable ACV, which is why outbound stays competitive against paid even as paid CACs rise.

The same arithmetic kills outbound when you skip the signals gate. Spray-and-pray at 0.5% reply rate produces meetings at \$150–\$300 even before you factor in deliverability damage. The signals gate is what makes the channel work, not just an efficiency tweak.

## Where outbound fits in the channel mix

Outbound complements rather than replaces other acquisition channels:

| Channel                     | Best at                                                                          | Worst at                                                                               |
| --------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| **Outbound**                | Reaching named accounts on your ICP list; capturing in-market timing via signals | High-volume lead-gen without a list; reaching unknown personas                         |
| **Paid (LinkedIn, Google)** | Bottom-funnel intent capture; volume                                             | ACV efficiency above a certain CAC; narrow ICPs                                        |
| **Content / SEO**           | Long-tail discovery; brand authority                                             | Speed (3–6 month lag); reaching named accounts                                         |
| **Partnerships**            | Warm intro pipeline; trust transfer                                              | Volume and predictability                                                              |
| **Community / Reddit**      | LLM citation + SERP presence + low-cost trust building                           | Direct, named-account targeting (see [Results Ranking Optimization](/results-ranking)) |

The teams getting the best blended CAC run outbound and content in parallel: content/SEO builds the long-tail brand surface so that when outbound lands in an inbox, the recipient half-recognizes the name. Each channel makes the other one work harder.

## Channel hygiene (the boring rules that matter)

The teams that *kill* their outbound usually do so at the infrastructure layer, not the messaging layer:

1. **Deliverability is upstream of every other lever.** A perfect message that lands in spam is worth zero. Warm domains for 4–6 weeks before scaling, use dedicated sending domains for outbound (`get.<yourdomain>` or similar), never the primary corporate domain. Monitor inbox placement weekly via a tool like Glock Apps or MailReach. None of this happens inside `outbound-sales` (drafting only); it happens on your sending platform.
2. **List hygiene > list size.** A 200-account ICP list signal-qualified is worth more than a 20,000-account list sprayed. `outbound-sales` enforces this by refusing to draft for accounts with no signals firing (`SKIP: no signals`). Resist the urge to override.
3. **Multi-channel cadence, not multi-touch on one channel.** Email touch 1, LinkedIn DM touch 2 (day +3), Email touch 3 (day +7, breakup). Don't blast 5 emails in 10 days: recipients pattern-match on volume and report you.
4. **Reply-handling is the conversion step.** A 15% reply rate at 0% reply-handling produces zero meetings. Have a human (or a sequence-aware agent) read replies same-day, classify intent, and route warm replies to a real conversation immediately. `outbound-sales` doesn't handle replies; your outreach platform's classifier or a separate reply-handling skill does.

## The agent that does this

Everything operational lives in the [`outbound-sales` skill](/skills/outbound-sales):

* 6-stage pipeline implementation (signal detection → handoff)
* Signal-to-angle mapping (every gtm-tools signal → hook + pain + title filter + persona)
* 5 cold-email templates (≤90 words, signal-keyed, anti-pattern callouts)
* 5 LinkedIn-DM templates (≤60 words, different register from email)
* Skip-when-no-signals discipline baked in
* Structured handoff output for any outreach platform

Install:

```bash
npx skills add arnaudjnn/gtm-skills --skill outbound-sales
```

The skill is the operator; this guide is the channel context.

## Next steps

#### [Outbound Sales skill](/skills/outbound-sales)

Install the agent that runs this pipeline end-to-end.

#### [LinkedIn Tools](/linkedin-tools)

The 19 LinkedIn tools the skill calls under the hood.

#### [Signals Tools](/signals-tools)

The 13 signal detectors: the qualification gate that makes outbound work.

#### [Results Ranking Optimization](/results-ranking)

The other channel guide: SEO/AEO/GEO via Reddit presence.