Domain Warmup Planner

What it does

Warmup is a scheduling problem more than a technique problem. The question that matters is not how to warm up but whether the domains bought today can carry the volume the campaign needs on its start date. This skill works backward from the campaign date, computes the required ramp, and says plainly whether the date holds.

When to use it

• I bought new domains
• how long does warmup take
• when can I send for real
• adding inboxes
• warmup schedule

What it needs from you

• domains: new domains and their registration dates
• target: the volume the campaign needs per day
• date: the campaign start date

How it works

1. Work backward from the campaign date and the target daily volume to the number of inboxes needed at steady state.
2. Compute the ramp per inbox: a conservative daily increase from a small base, with the increase paused rather than continued whenever a bounce or complaint appears.
3. Add domain age. A domain registered days ago carries reputation risk independent of its warmup volume, so age and volume are two separate clocks.
4. Sum the ramp to the campaign date and compare against the target. State the gap in emails per day, not as a percentage.
5. If the date does not hold, give exactly two options: move the date, or add inboxes, with the number of inboxes and their cost.
6. Set the checkpoints: the dates on which the ramp should be reviewed and the metric that would pause it.

What you get back

A per inbox ramp table to the campaign date, the achievable volume against the target, the gap, the two options if there is a gap, and the review checkpoints.

The quality bar

• Domain age and warmup volume are treated as two separate clocks
• The gap is stated in emails per day
• The pause metric is named and has a threshold
• The options are concrete, with inbox counts and costs

Where it runs

• Claude Code
• Codex CLI
• Cursor
• MCP-compatible agents