Directory/Skills Directory/Cold Email Pack/Sending Setup Plan

Sending Setup Plan skill

Plans the sending setup before any cold email goes out: works out mailboxes and domains from your weekly volume, keeps your main domain safe with lookalike domains, sets two to three real mailboxes per domain, SPF, DKIM, DMARC and MX, open tracking off, and a warmup and ramp schedule with the earliest safe launch date.

  • Sales and BDcategory
  • No scriptsinstructions only, sends nothing
  • Any AI appupload, or copy and paste

Free, no signup

Upload the file to Claude, ChatGPT Business or Gemini Enterprise. On ChatGPT Plus, the free Gemini app or Grok, copy and paste it instead.

Download the fileCopy with your details

Part of the Cold Email Pack · View on GitHub (opens in a new tab)

What the Sending Setup Plan skill does

Ask it things like:

  • “How many domains do I need for 300 new contacts a week?”
  • “Can we cold email from our main domain?”
  • “Write my warmup and ramp plan”
Best for
Agency owners setting up cold email infrastructure
Author
Work Insiders
Needs
Nothing beyond your AI assistant
License
MIT
Runs in
Claude, Gemini Enterprise, Gemini CLI, Gemini app (as a Gem), ChatGPT, Codex, Grok

How to use Sending Setup Plan in Claude, ChatGPT, Gemini or Grok

Claude upload

  1. In Claude, open Settings (or Customize), then Skills, then Upload.
  2. Upload sending-setup-plan.zip as it is. Don't unzip it.
  3. Check it is switched on.
  4. Test it: start a new chat and type Use sending-setup-plan, then paste what you have.

Team and Enterprise owners may need to allow skills first.

ChatGPT Business, Enterprise or Edu upload

  1. In the sidebar, click Plugins, then the Skills tab.
  2. Click Create, then Upload from your computer, and pick sending-setup-plan.zip.
  3. ChatGPT scans it, then uses it on its own or when you @ mention it.

An admin has to switch skills on for the workspace first.

ChatGPT Plus, Pro or Free paste

  1. Open the copy tool on the pack page, pick ChatGPT and click Copy. It adds your agency profile if you filled it in.
  2. In ChatGPT, click Projects, then New project, and name it after the skill.
  3. Open the project's Instructions and paste.
  4. Start a chat inside that project and paste what you have: your notes, a job order, a pipeline list or a client's email.

These plans have no skill upload. A project keeps the instructions for every chat inside it.

Gemini Enterprise upload

  1. In the Gemini Enterprise web app, click Skills in the menu.
  2. Click +, then Upload skill, pick sending-setup-plan.zip and click Import.
  3. Call it with / in a chat, or let Gemini pick it up on its own.

Standard, Plus and Pay-as-you-go editions can upload. An admin has to switch skills on first.

Gemini app paste

  1. Open the copy tool on the pack page, pick Gemini Gem and click Copy. It adds your agency profile if you filled it in.
  2. In the Gemini app, make a new Gem (a custom assistant) and paste it into the Gem's instructions.
  3. Chat with that Gem whenever you need the skill.

Grok paste

  1. Open the copy tool on the pack page, pick Grok and click Copy. It adds your agency profile if you filled it in.
  2. Paste it into a chat with your Grok Bot. The first line asks it to save the skill with Skill Creator.
  3. Review the draft and save it, then switch it on under Settings, Plugins, Yours. Call it with / in a chat.

Developers folder

  1. Gemini CLI or Antigravity: unzip into .gemini/skills/ in your project, or ~/.gemini/skills/ for every project.
  2. Claude Code: ~/.claude/skills/, or install a whole pack as a plugin from our GitHub repo. Grok Build: .grok/skills/.

Steps follow OpenAI's skills guide and Google's Gemini Enterprise guide. Menu names change, so check there if a label looks different.

The full instruction file (SKILL.md)

Nothing hidden: this is the whole file. Want it with your agency's details filled in, or formatted for ChatGPT, a Gemini Gem or Grok? Use the copy tool on the Cold Email Pack page.

---
name: sending-setup-plan
description: "Plans the sending setup for a recruitment agency's cold email, sized from the campaign's daily volume: separate lookalike domains, mailboxes per domain, SPF, DKIM and DMARC, tracking, warmup and a ramp schedule, so BD email reaches the inbox and the agency's main domain stays safe. Use when a recruiter asks \"how many domains do I need\", \"set up cold email domains\", \"SPF DKIM DMARC for cold email\", \"how many emails per inbox per day\", \"warmup plan\", or \"is it safe to cold email from our main domain\"."
license: MIT
metadata:
  author: Work Insiders
  version: "1.0"
  pack: cold-email-pack
---

# Sending setup plan

You plan the infrastructure before a single cold email goes out. Deliverability is decided here: a perfect email sent from a burned domain lands in spam.

If `references/agency-profile.md` exists, read the Cold email lines: sequencer, existing sending domains and mailboxes, countries emailed.

## 1. Size it from the volume

Ask how many new people the campaign should reach per week, and how many emails in the sequence. Then work it out and show the sum:

- New contacts per working day = weekly contacts / 5.
- Emails per day once follow-ups overlap is roughly new contacts per day x number of emails in the sequence. Plan for that peak, not for day one.
- Mailboxes = peak emails per day / cold emails per mailbox per day. Plan on **about 30 cold emails per mailbox per day** (a practitioner rule of thumb, not a published limit; stay between 20 and 40, lower on new domains and Microsoft mailboxes).
- Domains = mailboxes / 2 or 3 (two to three mailboxes per domain).
- Add one spare domain with its mailboxes so a problem domain can rest.

Example: 300 new contacts a week, 4 emails = 60 new a day, about 240 a day at peak = 8 mailboxes = 3 to 4 domains, plus 1 spare.

## 2. Domains

- **Never send cold email from the agency's main domain** or the domain its staff use for clients and candidates. One bad week can hurt every email the agency sends.
- Buy lookalike domains that are clearly the agency's: `getacmetalent.com`, `acmetalenthq.com`, `tryacmetalent.com`. Prefer .com. Avoid hyphen strings, numbers and spammy words ("jobs", "hiring", "free").
- Point each lookalike domain's website to the agency's real site with a redirect so a curious reader lands somewhere real.
- Register each domain a few days before setting up mail. Brand new domains need the full warmup.

## 3. Mailboxes

- Use real Google Workspace or Microsoft 365 mailboxes, two or three per domain, each with a real person's name, a photo and a signature with name, title, agency name and phone only: no logo, links or website.
- Never use shared inboxes like `info@` or `recruiting@` for cold email.
- Spread mailboxes across Google and Microsoft only if the recruiter wants to; it helps when the list is mostly one provider.

## 4. Authentication (every domain)

- **SPF**: one SPF record listing only the services that send for that domain.
- **DKIM**: turned on and signing in the mail provider and in the sequencer if it sends through its own servers.
- **DMARC**: at least `v=DMARC1; p=none; rua=mailto:[a mailbox you read]`. Move to `quarantine` once reports look clean.
- **MX**: the domain must receive mail, so replies and bounces arrive.
- Check each domain with Work Insiders' free SPF, DKIM and DMARC checker (workinsiders.com/free-tools/spf-dkim-dmarc-checker/) or the provider's own tool, and fix anything missing before warmup.

Gmail, Yahoo and Outlook.com all require SPF, DKIM and DMARC from bulk senders and filter or reject mail without them. Cold senders should meet the same bar at any volume.

## 5. Tracking

- Turn **open tracking off** for cold email, or use a custom tracking domain if the recruiter insists. Opens are unreliable anyway because Apple Mail and others load images automatically.
- No links in the first email; at most one in later emails, on the agency's own domain.
- Plain text. No images, no attachments, no HTML templates.

## 6. Warmup and ramp

- Run warmup on every new mailbox for **at least two weeks, ideally three to four**, before any cold email, and keep it running at a low level during the campaign.
- Ramp cold volume: about 10 a day per mailbox in week one, 20 in week two, then up to the planned level if bounces and replies look healthy.
- During the ramp, cap new contacts per day at (mailboxes x current daily limit) / emails in the sequence. In the example that is about 20 new a day in week one, so 300 a week is only reached in week three. Say this so the recruiter plans the first month honestly.
- Write down the date warmup started and the earliest launch date, and give them to cold-email-start-here for the campaign brief.

## Output

A table of domains, mailboxes, sender names, provider, authentication status (to check), warmup start and earliest launch date, then the volume sum and the ramp plan.

## Rules

- Never suggest buying aged inboxes of unknown history, rotating domains to dodge blocks, or hiding who the sender is.
- Do not choose or recommend a paid tool unless the recruiter asks; work with what they already use.
- If a domain is already in trouble, hand over to deliverability-check.
The agency profile it reads (fill this in so it uses your real details)
# Agency profile

Fill this in once. Every skill in the pack reads it, so every output comes out in your agency's voice with your real terms. Delete any line you do not want the AI to use. Leave a line blank rather than guessing.

## Who we are
- Agency name:
- Recruiter name and title (for sign-offs):
- Phone:
- Mailing address (needed for US commercial email):
- Years in business:
- Specialties (roles we fill):
- Markets (cities, regions or "US remote"):
- Industries we know best:

## Terms
- Direct hire fee basis (e.g. % of first-year base):
- Guarantee period and type (free replacement / pro-rata refund / credit; conditions, e.g. fee paid within terms):
- Contract markup or bill rate approach:
- Exclusive or retained options:
- Payment terms (e.g. net 30 from start date):
- Introduction period (how long a candidate we introduce stays ours):
- Contract-to-hire conversion fee:
- Concessions we allow, and their limits:

## Proof points we can share
- Placements, time to fill, or retention figures we are happy to quote:
- Client names we may mention (only with permission):

## How we work
- ATS:
- Do we text candidates? (yes/no):
- Name the client in first candidate messages? (yes/no):
- Blind profiles: always / new clients only / never:
- Include pay expectation in submittals? (yes/no):
- Job post apply instructions:
- EEO statement:

## Cold email
- Sequencer we use (e.g. Instantly, Smartlead, EmailBison, lemlist, Apollo):
- Sending domains (lookalikes only, never our main domain):
- Mailboxes and the sender names on them:
- Countries we email (sets which email and data laws apply):
- Opt-out line we use (e.g. "Reply 'no' and I won't email again."):
- Booking link (sent only after someone replies yes):
- Where our current clients, opt outs and do-not-contact list are kept:

## Words we never use
-

Tools that pair with this skill

Full directory

Connect the MCP server too, so your assistant can act inside the tool while it follows this skill: Instantly, Smartlead, EmailGuard, EasyDMARC.

Questions

Is the Sending Setup Plan skill free?

Yes. It is part of the free Work Insiders Cold Email Pack, MIT licensed, so you can edit and share it.

Does Sending Setup Plan work in Gemini?

Yes. Upload it in Gemini Enterprise or drop the folder into Gemini CLI's skills folder. In the regular Gemini app, paste its instructions into a Gem.

Can I trust it with my data?

It has no scripts and sends nothing anywhere. Whatever you paste goes only to your AI assistant, under that assistant's own data terms, so remove candidate details you do not need first. It can still steer how the assistant answers, so read it before you use it.

The rest of the pack, and similar skills

Full Skills Directory

Written by Work Insiders for agency recruiters. Fill in the agency profile before you use it so it never invents fees or proof points. How we make money.