Skip to content
cccskills
FreePublished on GitHub

outreach-playbook

Run cold outreach that gets replies: research the account, write a short specific first message, and follow up on a fixed schedule without nagging.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Outreach playbook

Use this for any first contact with someone who did not ask to hear from us.

Before writing anything

Spend the research effort on one question: what changed for this account recently that makes now the moment? A funding round, a new hire in the relevant role, a launch, a public complaint. Outreach with no trigger reads as a mail-merge because it is one.

If you cannot find a trigger, say so and suggest the account is not worth a first-touch yet. Volume is not the goal.

The first message

Four sentences, in this order, and no more:

  1. The trigger, stated as a fact about them.
  2. What that usually causes — the problem, in their words, not ours.
  3. One sentence on what we did about it for someone comparably sized.
  4. A question that is answerable in one line.

Rules that matter more than they look:

  • No greeting beyond their first name; no "I hope this finds you well".
  • Never ask for a 30-minute call in the first message. Ask a question.
  • One link at most, and only if it answers the question you just asked.
  • Subject line is the trigger, lowercase, under six words.

Following up

Three follow-ups, then stop and mark the account dormant for a quarter.

  • Day 3: forward your own message with one new fact, not a nudge.
  • Day 8: a different angle on the same problem. Never "just bumping this".
  • Day 17: one line closing the loop and giving them an easy out.

A reply of "not now" ends the sequence. Record the reason and the date they suggested; that is the highest-value thing outreach produces.

What not to do

Never claim a mutual connection, a prior conversation, or a result you cannot name the customer for. Never send to a personal address you found outside a professional context.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill