- Sales
- v1.0.0
- outreach
- sales
Cold email inbox warm-up
Use this skill when new sending domains or mailboxes need warming before a cold email campaign: fresh domains, new inboxes on an existing domain, or mailboxes recovering from spam-folder placement. Produces a ramp schedule and a go/no-go check before real volume starts.
SKILL.md
Run this before any new domain or mailbox sends cold email. It produces a ramp schedule and a clear go/no-go decision for opening campaign volume.
The play
- Separate the asset from the brand: cold email runs on secondary domains, never the company's primary domain. The primary's reputation is not a chip to gamble.
- Give a fresh domain two weeks of silence after setup: authentication configured, mailboxes created, signatures and profile pictures in place, zero cold sends. Age is part of reputation.
- Warm for at least three weeks before campaign volume: start at a handful of sends per day per mailbox, grow the daily count a little every few days, and keep replies flowing; a mailbox that only sends and never receives looks like a cannon, not a person.
- Cap real campaign volume per mailbox at 20-30 cold sends per day, and keep warm-up activity running in the background even after campaigns start. Scale by adding mailboxes and domains, not by pushing one inbox harder.
- Go/no-go before launch: spot-check where warm-up messages land. Anything worse than consistent inbox placement means the ramp continues; launching into the spam folder burns the list and the domain together.
- On a placement drop or a bounce spike mid-campaign: cut volume in half, hold for several days, and only ramp back one step at a time: the same discipline as the initial warm-up, at smaller scale.
What good looks like
- Good operators treat sending volume as something a mailbox earns, week by week; the mediocre version buys a domain on Monday and blasts 200 sends on Friday, then wonders why replies stopped.
- The tell that separates experts: they watch placement and bounce rate per mailbox, not per campaign, and they act on the first bad signal instead of the fifth.
- Consistency beats speed here exactly as on social channels: identical, boring, daily behavior is what reputation systems reward.
- Done well, every mailbox reaches campaign volume with steady inbox placement, bounce rates stay low, and a placement incident costs days, not domains.
Rules
- MUST warm every new domain and mailbox before campaign volume; no exceptions for deadlines.
- MUST keep cold volume per mailbox at 20-30 sends per day; scale with more mailboxes, not more pressure.
- MUST keep warm-up activity running after campaigns start.
- NEVER send cold email from the primary company domain.
- NEVER keep sending through a placement drop; cut volume and re-ramp.
Files
1 file ship with this skill. They are installed beside the SKILL.md.
NOTICE1.4 KB
Cold email inbox warm-up
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/imad-badreddine/cold-email-inbox-warmup
at https://github.com/swan-gtm/gtm-skills/commit/5d786aad0c7b2ca59b1abf1f601f9407ca261996. Written by Imad Badreddine (https://www.linkedin.com/in/imad-ngl/).
The skill is shared under the MIT License below; this notice must stay with any copy.
MIT License
Copyright (c) 2026 Swan
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.