Sender Scaling
A new sender blasting volume into an unproven campaign looks exactly like a spammer to a receiving server: new domain, high volume, no engagement history. This skill sets the ladder, warmup only for weeks 1 to 3, 1 real email a day once warmup completes, 3 a day only when interested replies prove the campaign, and every volume increase past that comes from adding more senders, never raising per-sender limits.
Pipeline Playbooks · Open Source, MIT Licensed
The volume discipline for cold email senders: 1 a day until engagement proves the campaign, then 3, with further growth always coming from more senders, never higher limits.
When to use this
- Setting daily limits on freshly warmed senders
- Deciding "can we send more" in any form
- Planning how many domains and inboxes to buy
- Diagnosing why total volume is lower than expected
- Reviewing sender settings during pre-launch QA
What it covers
- The scaling ladder: warmup only, then 1/day, then 3/day, then more senders
- The unlock for stage 2 is proven engagement, not a calendar date
- Why volume grows through more senders, never higher per-sender limits
- Planning maths table: sends/day to senders and domains needed
- Why warmup stays on forever, even after real sending starts
- Common gotchas: scaling on time, turning off warmup, uneven distribution
Install just this skill
Every skill folder is self-contained. Run this from your project root to pull just this one into .claude/skills/sender-scaling/:
npx degit joelwylie7/cold-email-playbooks/.claude/skills/sender-scaling .claude/skills/sender-scaling
Want the whole system, not just one skill?
Related skills
Domain & Inbox Setup
Takes you from zero to warmed, connected sending infrastructure: generate domains, buy them, route through Zapmail, provision inboxes, and sit through the 2 to 3 week warmup no one should skip.
EmailBison Campaign Launch
Assembles a complete EmailBison campaign end to end, copy, leads, senders, schedule, then deliberately stops at draft so nothing can go live without the QA gate.
Pre-Launch QA
A numbered gate that checks copy, settings, leads, senders, schedule and sequence structure before any campaign launches or resumes, PASS or FAIL, one line of evidence each.