Outreach,
turned into a system.

Cold outreach has a deserved bad reputation because most of it is templated, untargeted, and obvious. The Studio's outreach is the opposite: targeted, personalized, and patient. The yield-per-email is high because the volume-per-week is low.

Read this end-to-end the first time. After that, the daily reference is §05 (the sequence), §06 (response handling), and §09 (the weekly rhythm). The other sections rarely need re-reading except after a quarterly retro.

This manual does not contain the actual email copy — that lives in umbra-studio-outreach-emails.docx, which is the canonical source. This manual contains the workflow around those emails.

One target enters the loop, four outcomes possible: a held qualification call, a polite no, a request to defer (Nurture), or no response. Every outcome is logged; nothing exits the system without a state.

1. Intake — target name lands from Abe's list. Triage for ICP fit, deduplicate against existing Leads.
2. Personalize — 10 minutes of research per A-tier target. Capture the personalization hook.
3. Send — Touch 1 of the 5-touch sequence. Logged as Outreach + Touchpoint in USI-RB-03.
4. Sequence — Touch 2-5 spaced per §05, contingent on response.
5. Triage — per §06, route Positive, Objection, Silence, or No.
6. Qualify or close — per §07 or §10, depending on triage outcome.

Operational throughput target: 15-25 first touches per week, ~25% reply rate, ~40% of replies converting to a held qualification call. That's roughly 1-2 qualified calls per week from a steady-state operation — enough to keep the pipeline full without overwhelming delivery capacity.

Intake is the gate that protects the rest of the system from drift. A target on the list isn't yet a Lead — it becomes one only after passing the ICP filter and surviving deduplication.

ICP filter (from umbra-studio-icp.docx)

Intake checklist (per target)

1. Run the ICP filter. If A or B, proceed. If C, mark as Nurture-only. If D, decline politely (don't add to base).
2. Search the Leads table in Airtable for the person and the company. If either matches, this is a re-engagement, not a new Lead — route to §10.
3. Create a new Lead row in Airtable. Fill: Name, Company, Role, Source = (whatever Abe specified), Industry, Headcount estimate, Workflow Hint (if Abe surfaced one).
4. Set Stage = Signal. Owner = Abe.
5. Set Next Action = "Personalize and send Touch 1". Date = within 5 business days.

Bulk intake (from a list of 10+)

For a batch from Abe, do not skip the per-target filter. Instead, schedule the batch across two weeks — ~10 targets per week — so the personalization quality stays at A-tier for every send. A list of 30 names processed all in one day produces 30 mediocre emails; the same list spread over three weeks produces 30 good ones.

The single difference between outreach that gets read and outreach that gets deleted is the first sentence. Spend ten minutes per target learning enough to write a first sentence that no template engine could.

Where to look (in this order)

1. LinkedIn — current role, recent posts, recent role change. Recent activity is the highest-yield signal.
2. Company blog / press — any AI/transformation announcement, new initiative, leadership hire in the past 6 months.
3. Earnings call / 10-K (for public companies) — search for "AI", "automation", "operational efficiency". These often surface the budget context.
4. Job listings — if they're hiring an AI lead, an automation engineer, or a transformation PM, the workflow exists.
5. Mutual connections — LinkedIn 2nd-degree path. If a warm-intro pathway exists, switch the touch from Cold Intro to Warm Intro and pause until the intro is requested.

Capture the hook

Whatever you find, distill into a single line that goes into the Lead's Workflow Hint field and becomes the first sentence of Touch 1:

• ▢ "I noticed you posted last week about scaling your claims-triage team without proportional headcount —"
• ▢ "Your team's recent Head of AI hire (J. Smith, looks like she came from X) caught my eye —"
• ▢ "I read your Q3 earnings call — the line about wanting to operationalize AI in policy underwriting stuck with me —"

When the hook isn't there

If 10 minutes of research yields nothing personalizable, don't send. Move the Lead to Nurture and revisit in 90 days when there might be a triggering event. The cost of a generic email is zero opens and a permanent reputation hit; the cost of waiting is just waiting.

Five touches across roughly 30 days. Each touch has a specific purpose; if any earlier touch elicits a response, the sequence pauses and shifts to §06.

Touch 1 — Cold Intro

The hardest one. Pulled from the canonical Cold Intro snippet (;intro in Superhuman) but always personalized. Structure:

1. First sentence: the personalization hook from §04. No throat-clearing, no "I hope this finds you well."
2. Second sentence: what the Studio does. "I run Umbra Studio — we rebuild high-friction workflows with intelligence at the core for mid-market organizations."
3. Third sentence: credibility line. "We've shipped 10 production agents and 14 reusable patterns across our own properties — the systems we sell have been stress-tested on us first."
4. Fourth sentence: the soft ask. "Worth a 30-minute call to see if the workflow you're dealing with is one we can rebuild?"
5. Sign-off: First name, Studio, URL.

Touch 2 — Bump (Day 5)

Two sentences. Reply to Touch 1 thread (don't start a new one). Goal is to surface to the top of the inbox without being needy. Example: "Bumping in case my note got buried — happy to send a one-pager rather than schedule time if that's easier. Either way, no pressure."

Touch 3 — Proof (Day 12)

The first introduction of evidence. Reference one specific Studio outcome that maps to a workflow similar to theirs. Pattern:

"Realized I should be more concrete — here's the kind of thing
we'd be talking about:

For Indietheka (our music publication property), we cut the
content-pipeline cycle from 6h human time to 35min by routing
draft → review → publish through three coordinated agents.
Throughput up 7×, human hours down 90%. The pattern transfers
directly to {their workflow type}.

If a 30-min walkthrough would be useful, here's my Calendly:
{link}. Otherwise, no follow-up after this."

Touch 4 — Reframe (Day 21)

A different angle. If the prior three came at it from the agent-build angle, Touch 4 might come from the team-capacity angle, the AI-investment-ROI angle, or the workflow-specific angle. Often phrased as a question, not a pitch:

"One last note — if your Head of AI has been struggling to move from pilot to production, that's actually the exact gap we live in. Most internal AI teams build great pilots and then hit a brick wall on integration, ownership, and governance. We don't try to replace them; we hand them production systems they can run. Worth 20 minutes for them to compare notes?"

Touch 5 — Graceful close (Day 30)

Three sentences. No ask. Door open. Set the Outreach Outcome = No-reply when this sends, and the Lead Stage = Nurture.

"Last note from me — I'll stop after this. If the timing isn't right or this isn't relevant, I completely understand. If it ever becomes relevant, you have my address. All the best."

Every reply gets one of four labels and a same-day action. Logged in the Touchpoints table from USI-RB-03 §07 with the matching Sentiment.

Positive — what to do

1. Reply same-day, within 4 business hours. Speed signals seriousness.
2. Use the ;qualify snippet. Propose two specific 30-min slots; don't ask "when works for you?"
3. Include a Calendly link as the fallback.
4. In Airtable: log Touchpoint with Sentiment = Positive. Update Lead Stage = Qualify. Set Next Action = "Hold qualify call".

Objection — the most common categories

No — close the loop with grace

Use the ;lost snippet from USI-RB-03 §10. Three sentences max. Move the Lead to Lost with a Lost Reason captured. Resist the urge to respond again — once they say no, the highest-value action is to leave the door open.

The qualify call has one job: decide whether a Discovery engagement is worth proposing. It is not a sales pitch; it is a diagnostic conversation. By the end, both parties should know.

Pre-call (15 min the day before)

1. Re-read the Outreach thread. Note their words verbatim — you'll mirror them in the call.
2. Re-read your personalization research. Update if anything fresh has happened.
3. Pull up the company's most recent earnings/press for any new signals.
4. Block 5 min after the call to log the Touchpoint while it's fresh.

Call structure (30 min)

Questions to ask in minutes 3-15

1. What's the workflow that prompted this call?
2. How is it run today — people, tools, time per cycle?
3. What have you tried before? What worked, what didn't?
4. What would success look like, measurably, in 60 days?
5. Who else inside the org needs to be part of this conversation?
6. What's the budget shape if Discovery returns a strong recommendation?

Honest "no fit" signals

If the workflow is genuinely outside the Studio's pattern library, say so on the call. "I don't think this is one we'd be the best partner for — it sounds like you'd benefit more from {alt}." A clean no-fit ends well, generates referrals, and protects the Studio's reputation. A forced engagement on a bad-fit workflow ends in churn.

Post-call (15 min, same day)

1. Log the Touchpoint with a one-paragraph summary of their workflow in their words.
2. Update Lead's Workflow Hint, ICP Tier, Qualification Score.
3. Move Stage to Scope (good fit) or Lost (no fit) with reason.
4. Send ;scope snippet within 24h if proceeding: 3-paragraph recap of their workflow + proposed Discovery shape + ask for Scope alignment call.

From Stage = Qualify, the rest of the pipeline is mostly mechanical — the work is in the artifacts, not the outreach. This section is the bridge between outreach ops and engagement ops.

If a stage stalls beyond its time-box, it moves to the Stale view in USI-RB-03 §08 and gets one decision in the Monday rhythm: re-engage with a specific reason, move to Nurture, or move to Lost.

Outreach as a system means a fixed weekly rhythm. Most weeks look the same; the cadence is the engine.

Monday — 90 min · Plan & clear

1. Pipeline Kanban walk (USI-RB-03 §08): every card has a Next Action with a date.
2. Stale view: one decision per stale Lead.
3. Outreach Queue: queue this week's bumps and follow-ups (Touch 2-5 due).
4. This week's intake batch: 10 new Leads from Abe's list, ICP-filtered and scheduled.

Tuesday-Thursday — 60 min/day · Send & reply

1. Send 3-5 personalized Touch 1 emails. Each personalized per §04.
2. Send all bumps (Touch 2-5) due that day from the queue.
3. Process replies: Positive within 4h, others within 24h. Triage per §06.
4. Hold qualify calls scheduled this week. Post-call ritual within 15 min of hangup.

Friday — 30 min · Reflect

1. Log this week's send count, reply count, qualify-call count.
2. Note any objection that surfaced more than once — that's a copy iteration to ship next week.
3. Confirm Outreach table reflects all this week's activity (USI-RB-03 §06 discipline).
4. Review next Monday's intake batch: are these still A-tier given anything you learned this week?

Most Leads don't convert on the first sequence. The Nurture lane is where a no-now becomes a yes-later, and the Lost lane is the honest archive of everything that won't.

When to move to Nurture

• ▢ Touch 5 sent, no reply.
• ▢ Objection of "come back in [later month]" received.
• ▢ Held qualify call but timing or budget gap means a 90+ day pause makes sense.
• ▢ ICP-fit but no specific workflow surfaced — revisit when one does.

Nurture rhythm

1. Set the Lead's Stage = Nurture. Note the planned re-engagement date in Next Action Date (typically TODAY+90).
2. At T-90: re-research the target. New role? New initiative? New press? Use one of these as the re-engagement hook.
3. Send the ;reeng snippet from USI-RB-03 §10. Tone: "You may remember — here's what's new on our side, and what made me think of you."
4. If silent for another 90 days after re-engagement, auto-move to Lost (Reason = No-response, after 180d Nurture).

Retiring a Lead to Lost

Lost is honest, not failure. Capture the Lost Reason on every retirement — the Lost Reasons pivot in USI-RB-03 §08 is one of the most decision-relevant artifacts in the system. If >40% of losses are Budget, the pricing conversation is happening too late; if >40% are Fit, the ICP filter is leaking.

Daily · 60 min · Tue-Thu

1. 3-5 personalized Touch 1 sends.
2. All scheduled bumps and follow-ups for the day.
3. Reply triage per §06 SLA.
4. Held qualify calls + 15-min post-call ritual.

Weekly · 90 min Mon + 30 min Fri

1. Monday Plan & Clear walk-through (§09).
2. Friday reflect & log: send count, reply count, qualify count, objection patterns.
3. Confirm Touchpoint discipline: every reply has a same-day log.

Monthly · 60 min

1. Review reply rate by source. Cold <20% = personalization is slipping. Warm intro <50% = referrers need better briefing.
2. Review qualify-call → Scope conversion. <60% = qualify questions are letting bad fits through.
3. Review the Lost Reasons pivot. Adjust ICP filter or pricing surface accordingly.
4. Re-export the Snippet pack from Superhuman to studio-shared.

Quarterly · 2 hours

1. Audit the canonical outreach docx against snippets — flag any drift.
2. Re-tune Qualification Score weights based on which Leads converted (USI-RB-03 §04).
3. Re-evaluate ICP filter with last quarter's converted-vs-rejected data.
4. Run a Nurture re-engagement campaign on Leads that have been quiet 90+ days.