Skip to content

gooseworks-ai/goose-skills / skills/marketing/write-outreach

write-outreach

Verified

Cold outreach a person sends to business buyers: email and LinkedIn sequences, a first line per prospect, reply and objection answers, and a read of replies. Use when the marketer says "write a cold email sequence", "what do I send to this list", "write LinkedIn messages for these leads", "how do I reply to this prospect" or "handle this objection", "reply to this demo request", "win back or reconnect with accounts that churned or went quiet", or "why is nobody replying to my outreach". Drafts only; the marketer sends from their own tool. Not for finding the people — use research-audience; not for emails to subscribers or users, or consumer win-back — use email-lifecycle.

references/angles-by-signal.md

View on GitHub
# Angles by signal — what to say, to whom, when

Load at steps 1–4. A signal tells you **why now**; the angle turns it into a first line and a reason to reply. Every opener rests on the row's dated fact (signal URL and date from research-audience's `list.csv`). No fact → no personal opener.

The test for every angle: "Because <signal>, <company> now needs <outcome>." If you can't write that sentence truthfully, use the segment's default opener instead.

## New leader in the buying role

| Weeks in role | What to say |
|---|---|
| 0–2 | Too early for a pitch — at most a short welcome or a LinkedIn connection; save the sequence |
| **2–8 (best)** | "New in the seat, reviewing what the team uses" — a quick win for their first quarter |
| 8–13 | Direct about value; they're acting on their plan |
| 13+ | Weak — treat as no signal unless something else is fresh |

Use their background: **came from our customer** → "bring what worked to <new company>" (strongest; only if the marketer confirmed it); **came from a rival's customer** → they know the category, compare honestly; **same industry** → name the pains they already know; **different industry** → "what works here is different"; **internal promotion** → "now that you own the budget". An outside hire beats a promotion. Never mention the predecessor. Pitch a first-quarter win, not a six-month project. A public "starting a new role" post and their previous company may be referenced; nothing else from their profile.

## Hiring for a role we replace or support

Set up once per brand (from the fit definition): roles the product **replaces**, **augments**, roles that **buy**, **champion** and **use**.

| The post | Angle | Opener idea |
|---|---|---|
| A role we'd replace, "first hire" / "build from scratch" | Ready before the hire | "Before your new <role> starts…" — to the budget owner it can be cost against salary; to the hiring manager, never "don't hire" |
| Several posts for the role, or "scaling" | Multiply the hire | "Hiring three <roles> usually means <pain> is growing faster than the team" |
| A role we support, recent | Accelerate while you hire | "Your new <role> starts with <outcome>, not a blank page" |

Word it by the post's age: days 1–7 "before you start interviewing"; 7–14 "while you're meeting candidates"; 14+ "before you make an offer". **Who:** the hiring manager first (they own the problem; one level above the role); a separate note on cost against salary to their budget owner a few days later. Never write "you don't need to hire" — say "your new hire is effective from day one" or "complements the hire". Re-check the post is still live the day you send.

## Champion moved (a past user or buyer at a new company)

| They were | Now | Approach |
|---|---|---|
| Buyer | Buyer level | Re-sell: "same problem, new company?" |
| Buyer | Higher | Executive re-sell |
| Champion | Now owns the budget | Upgrade: "you pushed for us — now it's your call" |
| Champion | Same level | Lateral: replicate what worked |
| Power user | Any | Bottom-up: "your team will need <thing> again" |
| Lost-deal contact | Any | Fresh start: "different company, different needs" |

Warm tone, name exactly how you know each other, use what they saw at the old company (only facts the marketer confirms). Best within 30 days of the move; fine to 60. LinkedIn often suits it better than email. Never guess their new email — research-audience finds a route or the marketer has one.

## Switch intent ("alternative to X", "moving off X", "X is too expensive")

Fastest of all: within days of the post. Lead with their own words ("you mentioned <rival> gets expensive past <n> seats" — only what they wrote, linked). Honest about the difference; never bash the rival. Ask one question about what they need instead. A post in a public forum may be referenced only when it was written under their real name; never link a pseudonymous account to a person; don't quote a private group.

## Rival's public customer (case study, testimonial author)

They already buy the category. Don't pretend not to know: "I saw <company> in <rival>'s case study on <topic>". Offer a specific difference that matters to their situation, or a benchmark, not a takedown. Lower urgency than switch intent.

## Event (speaker, sponsor, exhibitor)

Before the event: "Will you be at <event>? Your talk on <topic>…" — offer to meet. After: reference the talk or topic, within a week. Sponsors and exhibitors have budget for the space. Never imply you attended if you didn't.

## News (launch, expansion, acquisition, regulation, a public post about the pain)

**Direct** (the news names our problem) → move fast; the first vendor looks informed, the fifth looks templated. **Adjacent** (the need is implied) → problem → agitate → solve. **Thematic** → awareness only; prefer another signal. Sensitive news: layoffs → empathy only, or skip; a breach, recall or lawsuit → skip unless we fix that exact thing, and never the same day; an earnings miss → never in the subject; wait 48–72 hours after any bad news. Test: would you say it to them face to face at a conference?

## Funding (only with another signal)

Talk about what the money is for (hiring, growth, new markets), **never open on the amount** or "congrats on the raise" — every vendor does. Best within 2–4 weeks of the announcement; cooling after 60 days. Early rounds fit smaller plans; late rounds enterprise.

## Running ads now (selling to marketers)

The ad library is public evidence: "<n> ads live, most started over 60 days ago" is a fact; "your ads are fatigued" is a guess — say it as a question. Link the library page. Never criticise their creative.

## Developer activity (opened issues, contributed to a rival's or a category repo)

Speak to the use case their issue or PR shows, not to their "interest". Three or more people at one company active on the same repos = the company is adopting: write to the buyer (engineering or product lead), and mention the team's activity in general terms, never by naming individual developers. Never use a commit email.

## Win-back (churned business accounts)

In range: left 3–18 months ago. Before writing, know what has shipped since, which churn reasons are fixed, and any offer.

| Why they left | Angle |
|---|---|
| Price | The new plan or price |
| Missing feature | It shipped — show it |
| Too complex | What we simplified |
| Went to a rival | What we've built since; an honest comparison |
| No results | New proof (signed off) |
| Champion left | Find and write to the new owner |
| Downsized | If they're growing again, the timing changed |

**Priority score** = change since they left (1–5) × how fixable the reason is (1–3) × account value (1, 1.5 or 2) ÷ time decay (1 at 3–6 months, 1.2 at 6–12, 1.5 at 12–18). **High ≥ 8:** personal sequence plus a founder note; **medium 4 to under 8:** personal sequence; **low under 4:** a short batch email or skip. High sequence: day 0 an update (one line acknowledging they left, no guilt, then the fix for their reason) · day 7 proof from a similar company (signed off) · day 14 an easy way back · day 28 a polite close with something genuinely useful. Consumer lapsed customers are email-lifecycle's.

## No signal

Use the segment's sharpest pain from the quote bank, said as they say it, with a question. Say "no personal hook" in the row; never fake one.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall