New customersGet 10% off your first payment on any Prosyo plan.Not available for INR (₹) billing. Valid on your first payment only, for new Prosyo customers.Claim 10% off
Deliverability Open source · MIT v1.0.0

Sending capacity planner Claude skill

Use this when a target meets the limits of safe sending. It answers whether the goal is reachable, what infrastructure it needs, and how long until it runs at full speed.

  • 6-step play
  • 3 guardrails
  • 1 file
  • Human approval built in

Use it when you need to know how many mailboxes, domains and LinkedIn accounts a meeting target requires, or how much a team can safely send.

Then just ask your agent

“We need 30 meetings a month from outbound. How many mailboxes and LinkedIn accounts?”

Watch it work

One request in, expert work out

What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.

Your agentApproval on
You

We need 30 meetings a month from outbound. How many mailboxes and LinkedIn accounts?

Loaded skill sending-capacity-planner
  1. Work backwards
  2. Size email infrastructure
  3. Size LinkedIn
  4. Check the list can feed it
  5. Show ramp and cost
Contacts and sends needed · Mailboxes domains and accounts needed · Ramp timeline

Ready for your review. Nothing is sent or changed until you approve.

  • 6Steps in the play
  • 3Guardrails
  • 1Files in the skill
  • 2 minTo read it all

What good looks like

  • Every rate is labelled measured or assumed.
  • The plan checks list supply, not only sending capacity.
  • The common mistake is solving a 0.5% reply rate with 50 more mailboxes; volume multiplies whatever the conversion is, including burned contacts.

What you bring

  • Meeting goal
  • Current conversion rates
  • Channels and limits

What you get

  • Contacts and sends needed
  • Mailboxes domains and accounts needed
  • Ramp timeline
  • Bottleneck
Raw
name:sending-capacity-planner description:Use this skill when you need to know how many mailboxes, domains and LinkedIn accounts a meeting target requires, or how much a team can safely send: "how many inboxes do I need", "plan…

Use this when a target meets the limits of safe sending. It answers whether the goal is reachable, what infrastructure it needs, and how long until it runs at full speed.

Inputs

  • Monthly meeting goal.
  • Conversion rates from recent campaigns (or the defaults below, labelled as assumptions).
  • Channels in use and per-account safe limits.

The play

1. Work backwards

Meetings needed per month: M
÷ meeting rate from positive replies (default 50%)  = positive replies
÷ positive reply rate per contact (default 1.5%)    = contacts per month
× touches per contact (email steps)                 = emails per month
÷ working days (21)                                 = emails per day

Example: 40 meetings ÷ 0.5 = 80 positive replies ÷ 0.015 = 5,333 contacts × 4 emails = 21,333 emails a month ÷ 21 = about 1,016 emails a day.

2. Size email infrastructure

Mailboxes = daily emails ÷ 30 (a conservative per-mailbox cold volume). Domains = mailboxes ÷ 3. Add 20% spare. Example: 1,016 ÷ 30 = 34 mailboxes → 41 with spare, across about 14 domains.

3. Size LinkedIn

Per account: about 15-25 invitations a day, so roughly 100 a week. If LinkedIn carries part of the load, divide contacts between channels and size accounts accordingly. Each account must belong to a real person on the team.

4. Check the list can feed it

5,333 new contacts a month is about 64,000 a year. Compare with the SAM: if the ICP has 20,000 reachable contacts, the plan exhausts it in four months. That is the real bottleneck, and the fix is better conversion, not more mailboxes.

5. Show ramp and cost

New mailboxes need 4-6 weeks to reach full volume. Show month by month capacity and the monthly cost of domains and mailboxes.

6. Name the bottleneck

Usually one of: list size (SAM), reply rate (copy and targeting), meeting conversion (reply handling speed), or infrastructure. Raising positive reply rate from 1.5% to 3% halves every number above.

Output format

Goal: M meetings/month
Funnel: contacts N → positive replies N → meetings M (rates used, assumed or measured)
Email: N/day → N mailboxes, N domains (incl. spare)
LinkedIn: N accounts (if used)
List check: N contacts/month vs SAM N → months of runway
Ramp: month 1 X%, month 2 Y%, full from week 6
Bottleneck: <one thing to fix first>

What good looks like

  • Every rate is labelled measured or assumed.
  • The plan checks list supply, not only sending capacity.
  • The common mistake is solving a 0.5% reply rate with 50 more mailboxes; volume multiplies whatever the conversion is, including burned contacts.

Rules

  • MUST use conservative per-mailbox and per-account limits.
  • MUST check the plan against the size of the reachable market.
  • NEVER plan LinkedIn capacity on fake or shared profiles.

Example prompts

  • "We need 30 meetings a month from outbound. How many mailboxes and LinkedIn accounts?"
  • "Here are our real conversion rates. Is 60 meetings a month realistic?"
  • "Plan our sending capacity for next quarter and tell me the bottleneck."
Try it

Ask your agent like this

Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.

  • “We need 30 meetings a month from outbound. How many mailboxes and LinkedIn accounts?”

  • “Here are our real conversion rates. Is 60 meetings a month realistic?”

  • “Plan our sending capacity for next quarter and tell me the bottleneck.”

FAQ

Sending capacity planner skill: your questions

What it does, how to install it and how it keeps you in control.

Rather have it done for you? Book a short demo and see Penny run this play on your own market.
Book a demo
Book a demo
What does the Sending capacity planner skill do?

Use this when a target meets the limits of safe sending. It answers whether the goal is reachable, what infrastructure it needs, and how long until it runs at full speed. You get: contacts and sends needed, mailboxes domains and accounts needed, ramp timeline, bottleneck.

When should I use the sending capacity planner skill?

Use it when you need to know how many mailboxes, domains and LinkedIn accounts a meeting target requires, or how much a team can safely send.

How do I install Sending capacity planner in Claude Code?

Run /plugin marketplace add prosyo-ai/gtm-skill and then /plugin install gtm-skills@prosyo to add the whole library, or run npx skills add prosyo-ai/gtm-skill –skill sending-capacity-planner for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.

What do I need to give the agent?

Have these ready: meeting goal, current conversion rates, channels and limits. If something is missing, the skill tells the agent to ask for it rather than guess.

Does it work with ChatGPT, Codex, Cursor or Gemini?

Yes. The skill is a plain SKILL.md file with no vendor lock-in. Agents that load skills natively (Claude Code, Claude.ai, Codex, Cursor, Gemini CLI and others) pick it up automatically; anywhere else, paste the file into the conversation as instructions.

Will it send emails or messages on its own?

No. Every skill in the library drafts, researches and analyses, and waits for a person to approve anything that sends, schedules or changes records in bulk. Your inbox, CRM and accounts stay under your control.

Is it free, and can I change it?

Yes. It is free and MIT-licensed. Copy it, adapt it to your market and voice, and if you improve it, open a pull request so everyone gets the better version.

Open source

Have a play that works? Share it as a skill.

Paste this into Claude, Codex or any agent. It interviews you about your play, writes the skill in the house format, checks it and opens the pull request. Once it is merged, it shows up here with your name on it.

Prompt for your agent

Fetch https://raw.githubusercontent.com/prosyo-ai/gtm-skill/main/AGENTS.md and follow its submission flow. Interview me about my GTM play (the real numbers, rubrics and examples), draft it in their format with reference pages, validate it and open the pull request.

Two ways to run it

Run it yourself, or put it on autopilot

The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.

Free · this skill
You and your agentBest for trying the play and one-off work
  • Your agent follows the sending capacity planner playbook step by step
  • You bring the inputs and run it when you need it
  • Works in Claude, Codex, Cursor and 40+ agents
  • You review every draft before it goes anywhere
Prosyo AI SDR
Penny runs it for youBest for a pipeline that grows every day
  • Finds the right buyers for your ICP every day
  • Writes from what each prospect actually posted
  • Follows up on LinkedIn and email at a safe, human pace
  • Every reply lands in one inbox with an answer drafted
  • You approve what goes out
Meet Penny
Meet Penny
7 days free · no card

Skills draft the play. Penny runs it.

Penny, the Prosyo AI SDR, finds your buyers, writes from what they actually posted, follows up on LinkedIn and email and lands every reply in one inbox with an answer ready. 7 days free, no card.

  • 7 days free
  • No card required
  • Cancel in two clicks