Outbound — Tooling

One principle governs everything below. The constraint on this motion is not reach — it is how many genuinely sharp, signal-backed observations we can write in a week. Every tool is judged against one question: does it help us find and earn the right conversation, or does it just push more mediocre messages out the door? We buy the first kind and pass on the second, even when the second is cheaper.

This is the operating manual for the stack: how to use each tool and how the tools chain together. How we know it's working lives in the companion doc, Outbound — Measurement. Messaging and ICP are settled elsewhere.

The frame: AI-Native is the spine; everything else is a way in

AI-Native is the company-level strategy, not one of two equal lanes. The two motions are not parallel — they sit at different altitudes:

The operating consequence: the tooling does not just book a reply. It chains — land with the champion → expand to the exec on the spine. A reply from a Growth PM that never reaches a Product or Engineering leader is a half-finished motion. The scoreboard measures the expansion, not just the land — see Measurement.

How the stack is organized — the four jobs

Every outbound stack does four jobs. Most teams own three tools that secretly do the same one and call it a stack. We sort by job, and the buy/cut list falls out on its own.

If a new tool doesn't clearly slot into one of these four and beat what already holds that slot, we don't buy it.

How to use each tool

Signal — who, and why now

TheirStack — our single best signal. A company running Pendo Guides, WalkMe, Whatfix, or Appcues is paying the Click Tax in cash. That is the landing trigger.

• Use it to: pull DAP-stack accounts on a standing cadence; tag each account by which DAP it runs (changes the observation).
• Stack a second signal on top before it goes to the writer — DAP signal alone is necessary, not sufficient. The cell that earns a founder touch first is DAP + hiring-for-AI: paying the Click Tax and staffing up to fix it.
• Pipe into Clay, never straight to a sequence.

RB2B — the warm half of signal. Tells us which companies and people showed up after seeing founder content (LinkedIn, webinars, clicktax.ai, the newsletter). Cold turning warm on its own.

• Use it to: identify post-content visitors, fit-check through Clay, and route into a "you stopped by" touch.
• Never treat an RB2B-surfaced, content-engaged account as cold.

Data — the contact record

One finder, via waterfall. This layer answers exactly one question: who is the human and what is their verified email. We do not pay three subscriptions for one job.

• The test: run a 200-row list (US + EU SaaS) through the candidates, keep whichever wins on match rate, let Clay waterfall the remainder. Expectation: keep one strong finder, cut the rest.
• For the expansion motion specifically: the finder must reliably return Product and Engineering leadership contacts at the landed account, not just the champion. Match rate on VP Product / CPO / CTO titles is the acceptance criterion that matters here, because that's who we expand to.

Orchestration — the brain

Clay — the center of the whole operation, and where the next dollar goes. Signal in, enrichment and research in the middle, one sharp observation out the other side. This is where craft scales.

• Use it to: ingest TheirStack + RB2B signal, stack signals, enrich the contact (waterfall), run research, and hand the writer enough to make one sharp observation per account.
• The hold rule: if Clay + the signal layer can't hand the writer enough for a sharp observation, the account is not ready — hold it. No observation, no send. This is the bottleneck working as designed, not a failure.
• Expansion support: Clay also assembles the expansion map for a landed account — the Product/CTO contacts and the AI-Native hook to reach them with — so multi-threading is a prepared move, not an afterthought.
• Spend here first — enrichment credits and a researcher's time — before any new channel.

Execution + system of record — send, and remember

HubSpot — the truth. Non-negotiable. System of record for every account, contact, signal, touch, and reply. Webinar/RB2B/content sources all land here, segmented by source.

Founder LinkedIn + HeyReach — the touch. Mickey's name is the unfair advantage; use it before the email, not just in the signature. Order is presence, then ask:

1. TheirStack / RB2B name the account.
2. Mickey (and Moyses) engage on LinkedIn first — a comment, a thoughtful reply, a relevant share.
3. HeyReach sequences the connection and follow-up at human cadence, with Clay personalization tokens.
4. The email lands warm.

HeyReach discipline is the whole game. It scales the human touch; it does not replace it. Tight daily limits, real Clay tokens, Mickey's face on the profile. The moment it becomes "blast 500 connection requests a week" it stops being founder-led, starts looking like every automated LinkedIn pest our buyers ignore, and LinkedIn throttles the accounts anyway.

Tool decisions (canonical)

The land-and-expand engine (how the tools chain)

This is the sequence the stack exists to run. Each step names the tool that owns it.

1. Trigger (Signal). TheirStack DAP signal (+ a stacked second signal) or RB2B warm visit names the account.
2. Qualify + research (Clay). Stack signals, enrich, research, produce one sharp observation. Hold if thin.
3. Presence (Founder LinkedIn). Mickey/Moyses engage the champion before any ask.
4. Land the touch (HeyReach → email). Warm sequence into the champion on the landing motion (Growth/PLG or CX). Soft CTA: "want me to send it over?" — the reply is the conversion.
5. Record (HubSpot). Log the account, the signal stack, the touch, the reply.
6. Expand (Clay map → Founder LinkedIn → HeyReach). Once landed, multi-thread to Product / CTO with the AI-Native story. This step is the point of the whole motion — it's where the spine shows up and where the deal lives.

A reply that stops at step 5 is landed, not expanded. The scoreboard treats that as incomplete — see Measurement.

Guardrails (what we do not do)

• We do not add send capacity faster than the signal layer can responsibly feed it.
• We do not let the landing motions and the AI-Native spine bleed into one message — signal decides the motion, and the message changes by persona.
• We do not put a webinar attendee or content-engaged visitor into a cold sequence. They aren't cold.
• We do not turn HeyReach into a connection-request cannon.
• We do not adopt burner-domain cold-send infrastructure while the brand sells the opposite of spray-and-pray.
• We do not send a generic email to hit a number. No observation, no send.

Source: derived from the Foldspace Outbound Strategy brief (2026-06-03), owner Mickey Alon. Companion: Outbound — Measurement. Messaging/ICP canon: positioning/gtm-messaging-matrix.md. AI-Native spine: CLAUDE.md.